not working anymore on Xperia X with SailfishOS 3.4 about crypto-sdcard HOT 13 CLOSED

@fuchsmich, thank you for your report.
I am not on SFOS 3.4.0 yet (v3.4.0.24 has been released as "General Availability (GA)" yesterday), but I suspected from its release notes and changelog, that user nemo is not member of the group system anymore (since SFOS 3.4.0). So this is a general issue. Altering the polkit rule is the right thing to do. As your solution works fine, don't worry. I will check, if there is an alternative to setting the polkit rule to a user or if this is the best solution, when I upgraded one of my devices to SFOS 3.4.0 (likely this weekend).

• WRT systemd-escape: Thanks, will correct that.
• WRT lazytime: Oops, thank you! Will fix that, too.

from crypto-sdcard.

@fuchsmich, please download the crypto-sdcard-1.3.1-1.sfos340.noarch.rpm preferably in /tmp (e.g. per,
cd /tmp && curl -LO https://github.com/Olf0/crypto-sdcard/releases/download/1.3.1-1.sfos340/crypto-sdcard-1.3.1-1.sfos340.noarch.rpm) and install it per
devel-su pkcon install-local crypto-sdcard-1.3.1-1.sfos340.noarch.rpm (or per Storeman, Section "Local RPMs").
Finger crossed, that I did not miss anything this time.

from crypto-sdcard.

• systemd-escape moved from /bin to /usr/bin in SFOS 3.4.0 704d63c
• WRT lazytime: See 5cd9937 and 188e250

from crypto-sdcard.

@fuchsmich, after some analysis, I think

I changed the polkit rule to the user sailfish-system

meant "changed the polkit rule to the group sailfish-system" or (equivalent, but simpler) "altered the group from system to sailfish-system in the polkit rule", right?

Anyway, I did not like the group sailfish-system, because it also contains the user sailfish-mdm, and the old, but previously unpopulated (before some SFOS release between v2.2.1 and v3.2.1) group media_rw, which now contains only the primary user, IMO fits much better (WRT what it is for).

from crypto-sdcard.

Hopefully crypto-sdcard 1.3.0 (and crypto-sdcard_sbj 1.3.0) installs and works fine on SFOS 3.4.0; both are also uploaded to Openrepos, so Storeman should offer them as updates on SFOS >= 3.4.0.
Can you please check that it is also working well on your device.

from crypto-sdcard.

"altered the group from system to sailfish-system in the polkit rule", right?

Yes, sorry for my gibberish.

from crypto-sdcard.

I guess sth went wrong with the build of 1.3.0. The rpm on openrepos still contains the lazytime option.

...or the tag 1.3.0 points to the wrong commit?

from crypto-sdcard.

Argh, worse than that: I lost track of what I committed to which branches!
"No lazytime" is in the master branch, but I forgot to push that to the sfos340 branch.
Then tagging, packaging and deploying is a straight-forward process.

Sorry, I am currently (still ongoing) reorganising this github repo's structure, due to the new need of different, OS version dependent releases. I am not used to the adapted commit processes this requires, yet.

And thanks again for testing. My only device on SFOS 3.4.0 has no SD-card, so I just install-tested.

from crypto-sdcard.

You can count on me with testing, just send me a rpm.

from crypto-sdcard.

The rpm works. sdcard mounts on startup. All fixes are included.

from crypto-sdcard.

Well, thank you very much @fuchsmich for your analysis and testing.

Unfortunately there are still a few hurdles ahead:

• Let us see, if the correct updates are offered, when I built and uploaded the "qcrypto" variants to Openrepos. You see them on a different page (https://openrepos.net/content/olf/crypto-sdcard-sbj-edition), but in reality all packages are in the same repository there. I did some local testing and it looks fine, but a test at Openrepos can only be done by publishing the new RPMs there (hence this is a "live test", unfortunately).
• Jolla's udisksctl-user script cannot be forced into unmounting correctly, AFAICS (I tried hard). I am considering to abandon its use, but then my startup and mounting process for SD-cards (and USB-attached storage) will differ significantly from Jolla's, making it more likely to be broken by SailfishOS upgrades.
  But tackling this is on a longer time scale and needs much pondering and testing.

from crypto-sdcard.

Thanks for your work! 👍

I'm not sure, if I understand correctly. Every user has one repo on openrepos, which contains all uploaded programs. Yours is https://sailfish.openrepos.net/olf/

from crypto-sdcard.

Yes, exactly.

That is why Bluetooth OBEX Filter off is published by a different user name, because only this way a separate repository at Openrepos is created and used.

from crypto-sdcard.