plymouth does not ask for password for crytsetup disks - after upgrade from 12.04 to 12.10

[Johannes Rohr]

After upgrading to quantal, plymouth has stopped asking for passwords for my crypto disks (cryptsetup), I have to resort to manual recovery by running service cryptdisks restart as root. After the first time of doing so, the devices show up in /dev/mapper, but still, after I exit the console, plymouth complains that my /home partitition is not ready yet. So I have to choose manual recovery a second time and run the same command once again. This time, when I exit the console, the boot process continues normally.
---
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
DistroRelease: Ubuntu 12.10
Lsusb:
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
MachineType: Dell Inc. Latitude E6420
NonfreeKernelModules: btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 usb_storage uas lp rfcomm bnep bluetooth binfmt_misc joydev snd_hda_codec_hdmi snd_hda_codec_idt rndis_wlan arc4 rndis_host cdc_ether usbnet ppdev dell_wmi sparse_keymap dell_laptop dcdbas coretemp kvm_intel kvm snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi microcode snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd psmouse lpc_ich serio_raw iwlwifi mac80211 soundcore snd_page_alloc cfg80211 parport_pc parport mei mac_hid dm_crypt vesafb ghash_clmulni_intel aesni_intel cryptd aes_x86_64 sdhci_pci i915 sdhci drm_kms_helper drm e1000e i2c_algo_bit video wmi
Package: ubuntu-release-upgrader
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic root=UUID=e62ab5dc-18df-4b86-8f3c-9651a16a758f ro vga=791 quiet splash vga=791
ProcFB:
 0 inteldrmfb
 1 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic root=UUID=e62ab5dc-18df-4b86-8f3c-9651a16a758f ro vga=791 quiet splash vga=791
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Tags: quantal running-unity
TextPlymouth: /lib/plymouth/themes/kubuntu-text/kubuntu-text.plymouth
Uname: Linux 3.5.0-16-generic x86_64
UpgradeStatus: Upgraded to quantal on 2012-10-04 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev pulse sambashare video
dmi.bios.date: 05/11/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0K0DNP
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6420
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

[Sasa Paporovic (melchiaros)]

When I understand correct the problem occure with the very first start of the upgraded system.

Would you please run

apport-collect 1062754

from terminal.

It will give us the log files of the upgrade process for investigating what went wrong.

Maybe apport is unsatisfied by the default libraries that are on Quantal. In this case please install liblaunchpad and when requested by the system associated libraries.

If apport bring not up the needed logs here, please attach them manually one by one from

var/log/dist-upgrade

Thank you in advance

melchiaros

[Johannes Rohr (jorohr)]

apport information

[Johannes Rohr (jorohr)]

apport information

[Johannes Rohr (jorohr)]

apport information

[Johannes Rohr (jorohr)]

apport information

[Johannes Rohr (jorohr)]

apport information

[Johannes Rohr (jorohr)]

apport information

[Johannes Rohr (jorohr)]

apport information

[Johannes Rohr (jorohr)]

apport information

[Johannes Rohr (jorohr)]

apport information

[Johannes Rohr (jorohr)]

apport information

[Johannes Rohr (jorohr)]

apport information

[Johannes Rohr (jorohr)]

apport information

[Sasa Paporovic (melchiaros)]

Thank you so far!

Unfortunally apport has not collected the

var/log/dist-upgrade

files.

May I ask you for attaching them (one by one) manually? Than we would be fine.

[Sasa Paporovic (melchiaros)]

If you feel unconfortable with the time that need this, you can compress the folder and attach it as whole.

Than I do attaching the single files.

[Johannes Rohr (jorohr)]

Thanks! the tar.gz is attached.

2012/10/7 melchiaros <email address hidden>:
> If you feel unconfortable with the time that need this, you can compress
> the folder and attach it as whole.
>
> Than I do attaching the single files.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1062754
>
> Title:
> plymouth does not ask for password for crytsetup disks - after upgrade
> from 12.04 to 12.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1062754/+subscriptions

[Sasa Paporovic (melchiaros)]

Hmpf,

I have hoped...

o.K I do.

[Sasa Paporovic (melchiaros)]

In the var/log/distupgrade.tar.gz
are two more folders(not files). They are named with calendar dates.

Seems to be that they are from previous upgrading attemps?!

I have not copied them out, because I think that they are not of primary interest.

[Johannes Rohr (jorohr)]

Hi, it seems that the issue is actually different: There is actually an old entry in /etc/fstab that goes
tmpfs /dev/shm tmpfs defaults 0 0

Somehow, mounting this tmpfs fails, obviously because, I have noticed /dev/shm is now a symlink to /run/shm

[Johannes Rohr (jorohr)]

so this bug should be retitled and reassigned accordingly. During the upgrade process, existing /dev/shm entries in fstab need to be taken care of.

[Steve Langasek (vorlon)]

This is a low priority to fix because there was never a need for an fstab entry for /dev/shm: the system would always mount it automatically. So very few users will be affected.