When I plug in any USB mass storage device, or put a disc in my DVD drive, the Device Notifier widget appears, but it never shows me an eject button for any item. It mounts without prompting for password (as expected unless I plug in an encrypted disk). This was working a few days ago. I last updated my system on the 15th. I rebooted to ensure all latest libs are loaded. Reproducible: Always Steps to Reproduce: 1. Plug in/insert removable storage device 2. View Device Notifier appear with no eject button Actual Results: Does not show eject button. Expected Results: Should show eject button. These items are installed regarding Plasma: kde-base/kdeplasma-addons kde-base/libplasmaclock kde-base/libplasmagenericshell kde-base/plasma-apps kde-base/plasma-runtime kde-base/plasma-workspace Except for kde-base/kdeplasma-addons, all versions are 4.11.14. kdeplasma-addons is 4.14.3. From log (journalctl and dmesg): Feb 21 17:05:11 limelight udisksd[924]: Mounted /dev/sr0 at /media/HEY_ARNOLD_S3_01 on behalf of uid 1000 relevant ~/.xsession-errors: "/org/freedesktop/UDisks2/block_devices/sr0" has new interfaces: ("org.freedesktop.UDisks2.Filesystem") * MEDIA CHANGED in "/org/freedesktop/UDisks2/block_devices/sr0" ; size is: 8152416256 * Disc in /dev/sr0 is a Video DVD MEDIA CHANGED in "/org/freedesktop/UDisks2/block_devices/sr0" ; size is: 8152416256 * kded(916)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: MEDIA CHANGED in "/org/freedesktop/UDisks2/block_devices/sr0" ; size is: 8152416256 * file:///usr/share/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:333: Unable to assign [undefined] to bool mounted kded(916)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: kio_file(31345) kdemain: Starting 31345 plasma-desktop(1348)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: plasma-desktop(1348)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application **** This really sticks out: file:///usr/share/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:333: Unable to assign [undefined] to bool mounted devicenotifier.qml is owned by the plasma-workspace-4.11.14 package.
I think I finally figured this out but I cannot say why it happens. Basically, if I log in with my iPhone plugged in, KDE tries to mount or use some mechanism to mount but it cannot (iPhone 6 Plus; I do not think this has worked via PTP or any other mechanism for a long time if it ever worked). The IPhone is recognised as a camera but has never worked with anything for me (it is not standard PTP I am guessing). Then, because of that failure, all other items fail to show an eject button even after I unplug my failing device. So this is the scenario that fails: 1. Boot up system and log in with iPhone plugged in (rebooting is not necessary) 2. Plug in flash drive 3. Notifier does not show Eject button 4. Remove iPhone 5. `umount the flash drive`; remove and re-plug in flash drive 6. Notifier still does not show Eject button (due to previous failure?) This is what works: 1. Boot up system with or without a mountable removable media 2. Plug in if necessary 3. Eject button shows 4. Plug in iPhone; gets recognised as camera, does not mount but this does not make further items fail So is this a bug? It seems one failure at login time can cause this subsystem to fail, but not after D-Bus has already started. Current workaround: do *not* log in with a device connected that exposes a FS somewhere but also cannot be mounted, such as an iPhone. Also, is there a way to block a device (which exposes an FS somewhere, even if non-functional) from being recognised by D-Bus completely? If so I would like to just block any iPhone (and iPad) from being detected as a camera because that functionality really does not work and seems to cause this issue.
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham