TDE version: R14.1.0 dev
NOTE: kded can be safely restarted from Alt+F2 dialog
There are two problems with current code in master.
an encrypted disk is mapped to something like /dev/dm-0 or similar. udisks2 displays the device as dm_2d0, that is with the ‘-’ changed to its ascii code. As a result of that, when unmounting the device an invalid dbus call is made. This aborts and as a result of that, dcop call is aborted and later kded crashed (for reasons still unknown). This is the problem described in this issue.
when trying to lock an unlocked encrypted disk, the mapped device is used instead of the original device (for example /dev/dm-0 instead of /dev/sdd). This again causes an invalid udisks2 call, with the same result as point 1), e.g. crashing kded,
The commits referenced above make sure kded is not crashed when using udisks/udisks2 to operate on a device.
The issue remains open since there are still things to do:
Žádný termín dokončení.
Tento úkol momentálně nemá žádné závislosti.
Smazání větve je trvalé. NEMŮŽE být vráceno zpět. Pokračovat?