Unmounting an encrypted disk crashes kded #32

Open
opened 3 years ago by MicheleC · 3 comments
MicheleC commented 3 years ago
Owner

TDE version: R14.1.0 dev

  1. Follow setup in #31
  2. Modify /etc/pmount.allow, to allow the disk to be mounted
  3. mount the disk by clicking on it from Konqueror storage media
  4. try to unmount the disk: nothing happens but in .xsession-errors a KDED crash is detected
  5. in Konqueror treeview, click on Storage Media again. An error dialog box inform that MediaManager is not running.
  6. Open TCC -> TDE Components -> Service manager. An error is displayed sayd that KDED can not be contacted. After pressing ok, all controls on the page are grayed out.

NOTE: kded can be safely restarted from Alt+F2 dialog

TDE version: R14.1.0 dev 1. Follow setup in #31 2. Modify /etc/pmount.allow, to allow the disk to be mounted 3. mount the disk by clicking on it from Konqueror storage media 4. try to unmount the disk: nothing happens but in .xsession-errors a KDED crash is detected 5. in Konqueror treeview, click on Storage Media again. An error dialog box inform that MediaManager is not running. 6. Open TCC -> TDE Components -> Service manager. An error is displayed sayd that KDED can not be contacted. After pressing ok, all controls on the page are grayed out. NOTE: kded can be safely restarted from Alt+F2 dialog
MicheleC added this to the R14.1.0 release milestone 3 years ago
Poster
Owner

There are two problems with current code in master.

  1. 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.

  2. 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,

There are two problems with current code in master. 1. 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. 2. 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,
Poster
Owner

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:

  1. understand why a bad dbus call crashes kded
  2. as per point 2. in above comment. This will be addressed in R14.1.0 through PR #111 and PR TDE/tdebase#35
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: 1. understand why a bad dbus call crashes kded 2. as per point 2. in above comment. This will be addressed in R14.1.0 through PR #111 and PR TDE/tdebase#35
Poster
Owner

Issue 2 has been fixed by the mentioned PRs, which have now been merged to master.

The only thing left here is to understand why a bad dbus call crashes kded.

Issue 2 has been fixed by the mentioned PRs, which have now been merged to master. The only thing left here is to understand why a bad dbus call crashes kded.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.