Luks encrypted partitions are not recongnized and not mountable

Martin, could bug 29364 be the fix for this?

 status needsinfo

Hi Clemens,

ClemensBier [2006-04-11 21:49 -0000]:
> Plugging a removable device such as a USB stick with a LUKS
> encrypted partition will cause no reaction from the system. The
> Breezy release recongized the encrypted and prompted the user via
> dialog to enter the password to decrypt the partition. In dapper,
> there is no feedback of this kind any more. When using the disk
> mounter applet in GNOME, the LUKS partition appears and you can
> click on the context menu entry "Mount device" but nothing happens.

It works fine for me, so it's not generally broken. Can you please do
the steps in http://wiki.ubuntu.com/DebuggingRemovableDevices to help
me finding out why it's not working for you? Thanks!

@Daniel: no, pmount doesn't use mount.crypt, it calls cryptsetup directly.

udev.log created as described in https://wiki.ubuntu.com/DebuggingRemovableDevices

I seem to have a bigger problemwith the gvm. It is not running properly. Thus my gvm.log is an empty file.

ubuntu:~$ killall gnome-volume-manager
gnome-volume-manager: no process killed
ubuntu:~$ gnome-volume-manager -n 2>&1 | tee gvm.log
ubuntu:~$ ps ax | grep gnome-volume
 8398 pts/0 S+ 0:00 grep gnome-volume
ubuntu:~$

I also attach a screenshot of the session applet. As stted in the inital post I did a dist-upgrade yesterday. Maybe I missed something?

lshal.log created as described in https://wiki.ubuntu.com/DebuggingRemovableDevices

dmesg.log created as described in https://wiki.ubuntu.com/DebuggingRemovableDevices

Hi Matt,
in order to help you find the problem, I did a complete reinstall with today's nightly build install CD. Installation went fine and I dig the nice little dialog that pops up telling me to install the cryptsetup package to mount my LUKS partition.

I observe the following situation: Mounting of the LUKS partition works nicely with a fresh user account/home directory. When I mount now my regular home directory from a separate partition, I can reproduce the bug. Thus, I assume that I have sort of a configuration problem which got created by the Breezy ==> dapper update 3 days ago. Can you point to the interesting config files so that a can attach a diff files of the interestng ones?

Thanks ,
Clemens

Hi Clemens,

thanks for checking with a new user. Maybe the output of g-v-m's configuration yields something interesting:

  gconftool -a /desktop/gnome/volume_manager

although g-v-m should at least run. If

  killall gnome-volume-manager
  gnome-volume-manager --no-daemon

immediately returns, then there's definitively something wrong. Maybe you can do

  gconftool --dump /desktop/gnome/volume_manager > gvm.xml

and attach gvm.xml here? Maybe I can use it to reproduce the issue here.

Last GVM.xml file used by the Breezy release and the upgraded Dapper installation

<entry name="automount_drives" mtime="1144921709" type="bool" value="false">
        </entry>
<entry name="automount_media" mtime="1144921708" type="bool" value="false">
        </entry

That makes it pretty clear; these settings were done manually. Can you please re-enable them in System -> Settings -> Removable Devices and check again?

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.