Bug 477915 - Can't mount encrypted drives
Summary: Can't mount encrypted drives
Status: CLOSED FIXED
Alias: None
Product: frameworks-solid
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.246.0
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: qt6
: 477877 479261 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-12-02 14:56 UTC by 31113
Modified: 2024-04-16 08:38 UTC (History)
12 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description 31113 2023-12-02 14:56:03 UTC
SUMMARY
When I try to mount an encrypted drive (luks +btrfs) in dolphin, instead of the password prompt, nothing happens, the loading circle is just endlessly spinning. Running dolphin through the terminal it said

kf.solid.backends.udisks2: Failed to call the SolidUiServer, D-Bus said: QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/modules/soliduiserver'")

Which is why I figured this bug report best fits here.

After unlocking the drive with cryptsetup through konsole, I can mount it in dolphin.

I tried this on my arch system as well as on a live boot of neon-unstable-20231126-1118.


STEPS TO REPRODUCE
1. Have an encrypted device plugged in 
2. Open dolphin
3. Click on the encrypted drive in the places panel in the devices section

OBSERVED RESULT
Nothing. 

EXPECTED RESULT
Password prompt pops up, after drive password and user password are entered successfully, drive gets mounted.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.3-arch1-1 (64-bit)
Graphics Platform: Wayland

solid version: 5.246.0-1
solid5 version: 5.112.0-1
udisks2: version 2.10.1-2
Comment 1 Robby Engelmann 2023-12-02 20:23:08 UTC
*** Bug 477877 has been marked as a duplicate of this bug. ***
Comment 2 Nate Graham 2023-12-05 20:58:22 UTC
This is working fine for me, and the error message indicates a setup or configuration problem on the system. I'd recommend contacting your distro folks about it, maybe through their forum.
Comment 3 Fabian Vogt 2023-12-07 21:59:33 UTC
Looking at solid code, I see this:

    // TODO KF6: remove hard dep on Plasma5 here which provides the SolidUiServer kded5 plugin
    QDBusInterface soliduiserver("org.kde.kded5", "/modules/soliduiserver", "org.kde.SolidUiServer");
    QDBusReply<void> reply = soliduiserver.call("showPassphraseDialog", udi, returnService, m_lastReturnObject, wId, appId);
    m_passphraseRequested = reply.isValid();
    if (!m_passphraseRequested) {
        qCWarning(UDISKS2) << "Failed to call the SolidUiServer, D-Bus said:" << reply.error();
    }

That would explain it, kded5 is probably not pulled in by anything currently. I definitely wouldn't expect solid to need it.

Is this actually correct that it needs kded5? I see that plasma-workspace 6 has a soliduiserver module with the showPassphraseDialog method.
Comment 5 Fabian Vogt 2023-12-09 11:33:49 UTC
(In reply to Nicolas Fella from comment #4)
> See https://invent.kde.org/frameworks/solid/-/merge_requests/134

Ok, so FWICT just waiting for a minor change.
Comment 6 Giuseppe Calà 2023-12-17 13:29:27 UTC
I confirm the bug. I'm also on Archlinux with [kde-unstable] enabled

Operating System: Arch Linux 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.7-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 4 × AMD A8-6500 APU with Radeon(tm) HD Graphics
Memory: 7.7 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2

solid 5.246.0
udisks2 2.10.1
(kded5, solid5 not installed)
Comment 7 Alexander Ahjolinna 2023-12-21 03:39:22 UTC
I can also confirm this issue on openSUSE (microOS/Kalpa with kde git repos added), hopefully will get fixed before launch

-------

Operating System: openSUSE MicroOS 20231218
KDE Plasma Version: 5.90.90
KDE Frameworks Version: 5.247.0
Qt Version: 6.6.1
Kernel Version: 6.6.6-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 46.8 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2
Comment 8 Pieter van der Vegte 2023-12-23 23:34:04 UTC
I was trying plasma 6 with openSUSE Krypton and also experienced this.
Comment 9 Fabio 2023-12-29 18:21:39 UTC
I was bitten by this same bug, recompiling Solid with https://invent.kde.org/frameworks/solid/-/merge_requests/134 fixed the issue for me.
Comment 10 Nicolas Fella 2024-01-01 18:00:38 UTC
*** Bug 479261 has been marked as a duplicate of this bug. ***
Comment 11 Pieter van der Vegte 2024-01-07 00:55:36 UTC
Now resolved on openSUSE Krypton after updating today :-)
Comment 12 Robby Engelmann 2024-03-29 17:54:37 UTC
since some days it re-appeared in openSUSEs master builds...
Comment 13 Nicolas Fella 2024-03-29 17:59:19 UTC
Please open a new bugreport
Comment 14 Edmund Laugasson 2024-04-15 19:16:40 UTC
I have to admit, that with newest KDE 6.1.0 we see regression and issue is back. Cannot unlock LUKS-encrypted EXT4 (presumably any other filesystem as well) drive in no way via systray icon. When drive connected, it will open but clicking to unlock and mount says, that not enough permissions.

KDE Plasma: 6.0.3
KDE Frameworks: 6.1.0
Qt: 6.7.0
Kernel: 6.8.5 (64-bit)
Display server: X11 (applies also to Wayland, where that drop-down menu for mounting didn't appear at all!)
solid version: 6.1.0-1
solid5 version: not installed
udisks2 version: 2.10.1-4
Comment 15 Nicolas Fella 2024-04-15 19:18:27 UTC
Please open a new bugreport
Comment 16 Nate Graham 2024-04-15 21:24:24 UTC
FWIW I just encountered the issue this morning. No time to debug it right now as I am boarding a plane in 20 minutes; will comment in the new bug report. Can you file one and mention it here, Edmund?
Comment 17 Nicolas Fella 2024-04-15 21:38:39 UTC
See https://bugs.kde.org/show_bug.cgi?id=485507