After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 552985 - Uncomprehensible and useless message when waiting to enter LUKS passphrase
Uncomprehensible and useless message when waiting to enter LUKS passphrase
Status: RESOLVED FIXED
Product: gvfs
Classification: Core
Component: udisks2 volume monitor
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2008-09-20 09:38 UTC by freggy1
Modified: 2012-12-10 16:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description freggy1 2008-09-20 09:38:36 UTC 
I logged in in a GNOME session with my external disk with LUKS encrypted volume plugged in. While it was logging in, I went away for a few minutes.

Because of the LUKS volume, probably a dialog popped up asking me for its passphrase, while I was away.

When I came back, this dialog was gone and the following message was shown:

Unable to mount 50.0 GB Encrypted Data

DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

This message is totally incomprehensible by and actually useless for normal users. Either just remove the dialog asking for the LUKS passphrase after some time, after which the user can still mount it by opening it in Nautilus, either  just don't remove at all the dialog asking the passphrase and let the user choose whether he wants to mount it or cancel it (like was done in previous GNOME versions).
Comment 1 David Zeuthen (not reading bugmail) 2012-12-10 16:23:26 UTC 
The udisks2 volume monitor does not pop up any message dialogs of its own and, nowadays, the component responsible for automounting (including at login time) is gnome shell (this would be the component popping up the dialog). Since this was filed in 2008 a lot of things have changed and since it works fine for me (just tested it), I'm going to close this as FIXED. Feel free to reopen and reassign to gnome-shell if the issue still exists.