Since the 20180312 TW snapshot Dolphin throws an error when attempting to mount media, claiming:
“An error occurred while accessing ‘Wastebin’; the system responded: The device is already mounted: Device /dev/sd(Xn) is already mounted at ‘/run/media/(user)/(device label)’.”
This happens when attempting to mount any device, external USB, internal (unmounted) drive, no matter what.
For example:
Login, Launch Dolphin and insert a USB stick. The USB correctly appears as unmounted in (Dolphin Panel) Devices section, and the Device Notifier plasmoid opens. In Dolphin, click to mount and the following happens:
Additionally, and I don’t know if this previously worked or is related. If instead of attempting to mount the USB from a running instance of Dolphin I select “Open with file manager” from the Device Notifier, that fails with a “Malformed URL” error message.
Looking through the change log for that snapshot, no updates occurred for Dolphin, but there was udisks2 (2.6.5 -> 2.7.6), possibly related?
Probably.
Dolphin (or KDE Frameworks actually) use udisks2 for mounting/unmounting.
I haven’t noticed a problem here on Leap 42.3 with the latest Frameworks 5.43 (and an older udisks2 of course)…
Maybe try to install udisks2 from Leap 42.3 (or 15.0) as a test.
Should be quite unproblematic to replace that. (there are two packages, udisks2 and libudisks2-0, and maybe udisks2-lang)
Well, it’s obviously caused by a change in udisks2 then.
Whether it’s to be considered as bug in udisks2 or KDE Frameworks I cannot tell really.
Apparently KDE Frameworks would need to be adjusted to the latest udisks2, but personally I’d say udisks2 shouldn’t have such incompatible changes in the first place…
Yes, something in udisks2 2.6.5 -> 2.7.6 has broken KDE Frameworks mounting.
Sorry, my “So… where’s the bug then, KDE Frameworks or udisk2.” was badly phrased, it was intended more as where should a bug report be directed.
I’ll file a bug against KDE Frameworks along the lines of udisks2 2.6.5 -> 2.7.6 has broken KDE Frameworks mounting, and let the KDE/udisks2 Developers take it from there.
Thanks.
Edit: Well I would if I knew which Framework component to file it against. Guessing, rather wildly, KIO? (As nothing else seemed to jump out at me).
I temporarily reverted back to udisks2 2.7.6 and indeed the media is actually mounted, despite the warning.
Open Dolphin
Insert USB stick
Click to mount - error displayed
Click elsewhere on a “Places” entry (Home, Downloads, whatever)
Re-Click on the USB device - now shown as mounted and Dolphin displays the contents.
There’s also https://bugs.kde.org/show_bug.cgi?id=391706 that sounds similar.
This suggests that it may in fact be a bug or regression in solid, but maybe only the latest udisks triggers it? AFAIK it cannot be reproduced on KDE Neon, which is based on Ubuntu LTS. (and I don’t see it here on Leap 42.3 with the latest Frameworks either as mentioned) https://marc.info/?l=kde-devel&m=152149245724878&w=2
There are one or two bug reports now, all of which are being marked as a duplicate of https://bugs.kde.org/show_bug.cgi?id=391386 against Dolphin, as indeed was the report I made.
There seems to be a general acknowledgement of a problem so hopefully it will be resolved. On this TW system it was definitely the udisks2 2.6.5 -> 2.7.6 update that caused the bug to manifest itself. However in Comment #3 of this https://bugs.kde.org/show_bug.cgi?id=391290 report the problem appears to present itself also with udisks2 2.1.7.
I very frequently need to mount removable media from Dolphin, so for the moment have locked udisks2 at the 2.6.5 version.
As an aside, the udisks2 2.6.5 → 2.7.6 update also pulls in a lot of new dependent packages…
