Bug 311616

Summary:	After connecting an encrypted volume, kde should try available credentials before prompting again
Product:	[Unmaintained] solid	Reporter:	sparhawk <kdebugs>
Component:	libsolid-frontend	Assignee:	Lukáš Tinkl <lukas>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	lukas
Priority:	NOR
Version:	4.9.3
Target Milestone:	4.11
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	kde-runtime patch kdelibs patch

Description sparhawk 2012-12-13 05:50:01 UTC

When plugging in an external hard drive encrypted with lukscrypt, I get a dialogue box popping up saying "Password – KDE Dæmon: 'WD My Book 1130' needs a password to be accessed. Please enter a password." The password field already contains my password, so I just have to hit enter.

KDE should automatically attempt the saved password, and only show the popup window if that fails (this is how gnome does it).

The problem for me is that I use udev to trigger a backup script. This popup window means my script requires user input before it'll run.

Reproducible: Always

Steps to Reproduce:
1. Connect encrypted hard drive.
Actual Results:  
KDE asks to confirm password.

Expected Results:  
KDE should automatically submit the saved password.

Comment 1 Alex Fiestas 2013-03-03 15:02:20 UTC

 Will fix for 4.11 and if easy backport to 4.10

Sorry for the delay on replying.

Comment 2 sparhawk 2013-03-03 21:04:38 UTC

No worries. Thank you for the fix.

Comment 3 Alex Fiestas 2013-03-06 22:44:26 UTC

Created attachment 77818 [details]
kde-runtime patch

Comment 4 Alex Fiestas 2013-03-06 22:44:38 UTC

Created attachment 77819 [details]
kdelibs patch

Comment 5 Alex Fiestas 2013-03-06 22:45:20 UTC

Lukas, can you check if these patches are correct? They will also need porting to udisk2 (I only have udisk1 in this machine).

Thanks !

Comment 6 Lukáš Tinkl 2013-03-09 14:17:28 UTC

The patches look good but I'd prefer actual testing by the reported before pushing this into git (and also porting it to udisks2 :)

Comment 7 sparhawk 2013-03-09 20:42:23 UTC

Am I the "reported"? I'm happy to test it, but I'm not sure how. If you could point me in the right direction, I'm happy to give it a try. Thanks.

Comment 8 Lukáš Tinkl 2013-03-10 08:39:19 UTC

Yes, I meant "reporter" of course, nasty typo :) Patches are included for you to try out

Comment 9 sparhawk 2013-03-10 09:30:56 UTC

No problem! :) I was also unsure as to what you meant, because I'm new to the bug-fix–testing process. I meant to ask if you could point me in the right direction of how to apply these patches? Thanks.

Comment 10 Alex Fiestas 2013-03-10 16:17:01 UTC

Which distribution are you using?

You will need to compile software (in this case kdelibs and kde-runtime), so first thing you have to do is install the basics.

In case you are on debian based distribution you can try

apt-get build-dep kdelibs
apt-get build-dep kde-runtime

Also you may want to install git.

Comment 11 sparhawk 2013-03-11 11:23:10 UTC

I'm using Kubuntu. But I fear I need (much) more information than that. Is there a webpage that can take me through the whole process step by step? Cheers.

Comment 12 Jonathan Riddell 2015-03-11 19:07:09 UTC

This bug is reported on libsolid which is the kdelibs4 version of the solid library.  It is now in maintenance mode.  If you think it should still be fixed in the KDE Frameworks 5 version of solid please move it to or report a bug on frameworks-solid.

Comment 13 sparhawk 2015-03-12 04:42:30 UTC

I'm not using encryption any more, so I'll just close this as invalid.