Summary: | udev-187-2: dolphin fails to mount LUKS encrypted devices | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sebastian Rose <sebastian.rose> |
Component: | [OLD] Core system | Assignee: | udev maintainers <udev-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | cybertec.systems, kde |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sebastian Rose
2012-08-03 09:34:15 UTC
Please report this upstream and link back here. Yes, /dev/mapper/LINK is created and luksOpen has happend. Only misses the mount of the decrypted device ... This the only bug I have encountered I am really happy with Kde-4.9.0 ! Thanx to maintainers for your effort! And Kde-overlay users talking back. Do you have unmasked the udisks2 use flag in kdelibs? It dosn't help anything! See Bug 424157 I added my additional info to Sebastians upstream bug: https://bugs.kde.org/show_bug.cgi?id=304540 qlist -Iv udisk #gives my installed udisks packages: sys-fs/udisks-1.0.4-r2 sys-fs/udisks-1.99.0 emerge udisks These are the packages that would be merged, in order: Calculating dependencies .... done! [ebuild U ] sys-fs/udisks-1.99.0-r1 [1.99.0] USE="crypt gptfdisk -debug -introspection -systemd" ----- should I update with introspection enabled? I thought this wasn't Kde related? Bug is solved for me by the next Gentoo revisions, Changelog was: "Use udev.pc pkg-config file to determine udevhelperdir and udevrulesdir. Dummy revision bump for UDisks2 because it has the same logic for --with-udevdir= in configure.ac." sys-fs/udisks-1.0.4-r3 sys-fs/udisks-1.99.0-r1 (At least solved me only using device notifier) Though I don't know which udisks-1 or udisks-1.99 is really needed for Kde. It doesn't matter to not have -intorspection... This surely was related to me using unstable sys-fs/udev-187-r1 This is solved by updating to udisks sys-fs/udisks-1.0.4-r3 Okay, this one is back from the dead. (In reply to comment #8) > This surely was related to me using unstable sys-fs/udev-187-r1 I thought it was fixed by updating udisks but it seems that you are right. The bug came back with udev-187-r2. (In reply to comment #10) > Okay, this one is back from the dead. > > (In reply to comment #8) > > This surely was related to me using unstable sys-fs/udev-187-r1 > > I thought it was fixed by updating udisks but it seems that you are right. > The bug came back with udev-187-r2. Re-assigning then. - After upgrading to -r1, -r2, or -r3 one needs to rebuild udisks: # emerge -1 udisks:0 udisks:2 - -r3 has a patch to search udev helpers also in /usr/lib/udev/ So if according to Comment #10 the bug remanifested when moving from -r1 to -r2, then this is solved now by -r3 and propably duplicate of bug 430412. (In reply to comment #12) > - After upgrading to -r1, -r2, or -r3 one needs to rebuild udisks: > # emerge -1 udisks:0 udisks:2 > > - -r3 has a patch to search udev helpers also in /usr/lib/udev/ meant /lib/udev/ here... I can confirm it is solved by udev-187-r3. Thanks. |