Bug 252175

Summary:	"Could not mount the following device" when trying to mount previously opened LUKS usb drive (ntfs)
Product:	[Applications] dolphin	Reporter:	Daniel Hahler <kde-bugzilla>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED WAITINGFORINFO
Severity:	normal
Priority:	NOR
Version:	16.12.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Daniel Hahler 2010-09-23 22:25:09 UTC

Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

After attaching a removable USB device, I can use the device notifier to open its cryptsetup/LUKS container.
After entering the passphrase, another device turns up in the device list, having 3 actions attached like normal USB sticks.

But when trying to mount the device (using the "mount" icon), or trying to invoke any of the associated actions, I get the error:
"Could not mount the following device: X GiB External Hard Drive"

My guess is that it's related to missing PolicyKit configuration/permissions.

However, this is probably supposed to work without any configuration from my side.

(I can mount this manually using an existing fstab entry, via sudo)

Reproducible: Always

Steps to Reproduce:
1. Attach USB drive (LUKS container)
2. Click on the unlock icon
3. Enter passphrase
4. Containing drive gets displayed in Device Notifier
5. Click the mount/open action

Actual Results:  
Trying to open/mount this fails.

Expected Results:  
The drive should get mounted.

Apparently this happens for ntfs only (have not tested it myself though, but was told so in #kubuntu-devel IIRC).

This is using ntfs-3g 2010.8.8-0ubuntu1 (Ubuntu Maverick).

Launchpad/Ubuntu bug: https://launchpad.net/bugs/629840

Comment 1 Daniel Hahler 2010-09-23 22:27:16 UTC

I was told that at least the error message should provide more details/information.

IIRC when trying to mount the unlocked drive via Dolphin, the error was similar, but not exactly the same; for one it was ending in ":" - I can verify this, if this would help.

Comment 2 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:19:38 UTC

Resetting assignee to default as per bug #305719

Comment 3 Frank Reininghaus 2013-04-30 12:32:54 UTC

Does this still happen in KDE 4.10 or later?

Comment 4 Frank Reininghaus 2013-05-24 08:28:06 UTC

No response -> I assume it works now.