Safely removing encrypted USB media not locked with luksClose

Bug #1175045 reported by Robert Tari
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This applies to Ubuntu 13.04
Tested with 2 different external USB hard disks.

After selecting "Safely Remove" (either from the launcher or nautilus), all LUKS encryped ext4 external media is unmounted, but not locked. This prevents the drive showing up at all, thus unlocking when it is connected again.

This behaviour is always reproducible following the steps below:

- connect an encrypted extrnal usb disk containing an ext3/4 file system
- the drive shows up properly
- depending on the keyring, the drive is automatically unlocked or you get an unlock prompt
- the drive is now unlocked and works as expected
- select any method of removal from the Ubuntu GUI
- the drive is removed from the GUI as expected
- disconnect the drive
- plug the drive back again
- it does not show up (at this point this can only be resolved by a reboot)

Reason:

- when the user asks the system to remove the drive, umount is called but luksClose either fails or is not called at all

Current workaround:

- ask the system to remove the drive, then manually call: sudo luksClose udisks-luks-uuid-...

summary: - Safely removing encrypted USB media not doing luksClose
+ Safely removing encrypted USB media not locked with luksClose
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1175045/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → nautilus (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.