http://bugzilla.suse.com/show_bug.cgi?id=927677 http://bugzilla.suse.com/show_bug.cgi?id=927677#c43 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kde-maintainers@suse.de Flags| |needinfo?(kde-maintainers@s | |use.de) --- Comment #43 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Rosanne DiMesio from comment #42)
Created attachment 726574 [details] monitor.out
Attaching the requested file.
Hm, no information is send to the udisks2 dbus path (/org/freedesktop/UDisks2) Instead a kde path (/org/kde/solid/) is used. Obviously udisks2 cannot react if it doesn't get a notification. I did a test with a kde desktop running tumbleweed and there it was working correctly. The dbus monitor showed: signal time=1496394512.528399 sender=:1.15 -> destination=(null destination) serial=690 path=/org/freedesktop/UDisks2; interface=org.freedesktop.DBus.ObjectManager; member=InterfacesAdded object path "/org/freedesktop/UDisks2/drives/USB_Flash_Disk" The log didn't show any path like /org/kde/solid/. It seems that solid is a kind of kde internal hardware library (https://techbase.kde.org/Development/Tutorials/Solid/Introduction) kde-maintainers, is it possible that solid is blocking the udisks2 functionality in order to process the usb stick internally? -- You are receiving this mail because: You are on the CC list for the bug.