2012-03-27 17:18:38 |
Tom |
bug |
|
|
added bug |
2012-03-27 17:25:04 |
Ubuntu QA Website |
tags |
precise |
iso-testing precise |
|
2012-03-28 02:16:28 |
Colin Watson |
affects |
debian-installer (Ubuntu) |
cryptsetup (Ubuntu) |
|
2012-03-28 02:24:06 |
Steve Langasek |
affects |
cryptsetup (Ubuntu) |
plymouth (Ubuntu) |
|
2012-03-28 02:25:36 |
Steve Langasek |
plymouth (Ubuntu): status |
New |
Incomplete |
|
2012-03-28 14:32:16 |
Tom |
tags |
iso-testing precise |
apport-collected iso-testing precise |
|
2012-03-28 14:32:18 |
Tom |
description |
When installing the lubuntu image as part of the iso testing (lubuntu/daily/20120327/precise-alternate-amd64.iso) using the alternate installer from the daily builds for March 27, 2012, I attemted to make a full-disk encrypted setup using LVM. I used the instructions from the isotesting testcase: http://testcases.qa.ubuntu.com/Install/AlternateEncryptedLvm
The install went perfectly. However, when I rebooted, the system hung on a blank screen. I left it for over half an hour, and no response. At this point, I simply typed in the password for the LVM encryption, and the system then continuted to boot normally.
After getting into the system, I tested it (everything was working fine) then rebooted. I experienced the same symptoms (just a blank screen) after each boot.
I believe that there is supposed to be a screen prompting the user for the password for the LVM encryption instead of just a blank screen. |
When installing the lubuntu image as part of the iso testing (lubuntu/daily/20120327/precise-alternate-amd64.iso) using the alternate installer from the daily builds for March 27, 2012, I attemted to make a full-disk encrypted setup using LVM. I used the instructions from the isotesting testcase: http://testcases.qa.ubuntu.com/Install/AlternateEncryptedLvm
The install went perfectly. However, when I rebooted, the system hung on a blank screen. I left it for over half an hour, and no response. At this point, I simply typed in the password for the LVM encryption, and the system then continuted to boot normally.
After getting into the system, I tested it (everything was working fine) then rebooted. I experienced the same symptoms (just a blank screen) after each boot.
I believe that there is supposed to be a screen prompting the user for the password for the LVM encryption instead of just a blank screen.
---
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
DefaultPlymouth: /lib/plymouth/themes/lubuntu-logo/lubuntu-logo.plymouth
DistroRelease: Ubuntu 12.04
InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Beta amd64 (20120328)
Package: plymouth 0.8.2-2ubuntu28
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-20-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
ProcEnviron:
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-20-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Tags: precise
TextPlymouth: /lib/plymouth/themes/lubuntu-text/lubuntu-text.plymouth
Uname: Linux 3.2.0-20-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 12/23/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: RQG4110H.86A.0013.2009.1223.1136
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DG41RQ
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE54511-205
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrRQG4110H.86A.0013.2009.1223.1136:bd12/23/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-205:cvn:ct3:cvr: |
|
2012-03-28 14:32:20 |
Tom |
attachment added |
|
BootDmesg.txt https://bugs.launchpad.net/bugs/966403/+attachment/2955186/+files/BootDmesg.txt |
|
2012-03-28 14:32:22 |
Tom |
attachment added |
|
BootLog.gz https://bugs.launchpad.net/bugs/966403/+attachment/2955187/+files/BootLog.gz |
|
2012-03-28 14:32:24 |
Tom |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/966403/+attachment/2955188/+files/CurrentDmesg.txt |
|
2012-03-28 14:32:26 |
Tom |
attachment added |
|
Dependencies.txt https://bugs.launchpad.net/bugs/966403/+attachment/2955189/+files/Dependencies.txt |
|
2012-03-28 14:32:27 |
Tom |
attachment added |
|
EtcDefaultGrub.txt https://bugs.launchpad.net/bugs/966403/+attachment/2955190/+files/EtcDefaultGrub.txt |
|
2012-03-28 14:32:29 |
Tom |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/966403/+attachment/2955191/+files/Lspci.txt |
|
2012-03-28 14:32:31 |
Tom |
attachment added |
|
Lsusb.txt https://bugs.launchpad.net/bugs/966403/+attachment/2955192/+files/Lsusb.txt |
|
2012-03-28 14:32:33 |
Tom |
attachment added |
|
ProcCpuinfo.txt https://bugs.launchpad.net/bugs/966403/+attachment/2955193/+files/ProcCpuinfo.txt |
|
2012-03-28 14:32:35 |
Tom |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/966403/+attachment/2955194/+files/ProcInterrupts.txt |
|
2012-03-28 14:32:37 |
Tom |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/966403/+attachment/2955195/+files/ProcModules.txt |
|
2012-03-28 14:32:40 |
Tom |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/966403/+attachment/2955196/+files/UdevDb.txt |
|
2012-03-28 14:32:44 |
Tom |
attachment added |
|
UdevLog.txt https://bugs.launchpad.net/bugs/966403/+attachment/2955197/+files/UdevLog.txt |
|
2012-03-28 15:46:06 |
Phill Whiteside |
bug |
|
|
added subscriber Phill Whiteside |
2012-03-28 16:22:54 |
Brian Murray |
plymouth (Ubuntu): importance |
Undecided |
High |
|
2012-03-29 00:58:43 |
Tom |
attachment added |
|
plymouth-debug.log https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/966403/+attachment/2957870/+files/plymouth-debug.log |
|
2012-03-29 04:21:58 |
Steve Langasek |
affects |
plymouth (Ubuntu) |
linux (Ubuntu) |
|
2012-03-29 04:21:58 |
Steve Langasek |
linux (Ubuntu): status |
Incomplete |
New |
|
2012-03-29 04:30:10 |
Brad Figg |
linux (Ubuntu): status |
New |
Confirmed |
|
2012-03-29 05:34:00 |
Joseph Salisbury |
tags |
apport-collected iso-testing precise |
apport-collected iso-testing kernel-da-key kernel-key precise |
|
2012-03-29 05:36:17 |
Joseph Salisbury |
tags |
apport-collected iso-testing kernel-da-key kernel-key precise |
apport-collected iso-testing kernel-da-key needs-upstream-testing precise |
|
2012-03-31 00:30:31 |
Brad Figg |
linux (Ubuntu): status |
Confirmed |
Incomplete |
|
2012-03-31 00:30:35 |
Brad Figg |
tags |
apport-collected iso-testing kernel-da-key needs-upstream-testing precise |
apport-collected iso-testing kernel-da-key kernel-request-3.2.0-21.34 needs-upstream-testing precise |
|
2012-03-31 14:44:43 |
Tom |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
2012-04-05 00:30:31 |
Brad Figg |
linux (Ubuntu): status |
Confirmed |
Incomplete |
|
2012-04-05 00:30:34 |
Brad Figg |
tags |
apport-collected iso-testing kernel-da-key kernel-request-3.2.0-21.34 needs-upstream-testing precise |
apport-collected iso-testing kernel-da-key kernel-request-3.2.0-21.34 kernel-request-3.2.0-22.35 needs-upstream-testing precise |
|
2012-04-10 20:53:56 |
Tom |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
2012-04-11 12:31:25 |
Brad Figg |
linux (Ubuntu): status |
Confirmed |
Incomplete |
|
2012-04-11 12:31:29 |
Brad Figg |
tags |
apport-collected iso-testing kernel-da-key kernel-request-3.2.0-21.34 kernel-request-3.2.0-22.35 needs-upstream-testing precise |
apport-collected iso-testing kernel-da-key kernel-request-3.2.0-21.34 kernel-request-3.2.0-22.35 kernel-request-3.2.0-23.36 needs-upstream-testing precise |
|
2012-04-12 00:55:57 |
Tom |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
2012-04-12 00:56:52 |
Tom |
linux (Ubuntu): status |
Confirmed |
Incomplete |
|
2012-04-12 14:25:20 |
Tom |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
2012-04-13 15:06:37 |
Joseph Salisbury |
linux (Ubuntu): status |
Confirmed |
Incomplete |
|
2012-04-16 21:24:09 |
Tom |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
2012-04-16 21:24:46 |
Tom |
tags |
apport-collected iso-testing kernel-da-key kernel-request-3.2.0-21.34 kernel-request-3.2.0-22.35 kernel-request-3.2.0-23.36 needs-upstream-testing precise |
apport-collected iso-testing kernel-da-key kernel-fixed-upstream kernel-request-3.2.0-21.34 kernel-request-3.2.0-22.35 kernel-request-3.2.0-23.36 precise |
|
2012-04-17 18:05:24 |
Joseph Salisbury |
linux (Ubuntu): status |
Confirmed |
Triaged |
|
2012-04-18 23:01:14 |
Tom |
description |
When installing the lubuntu image as part of the iso testing (lubuntu/daily/20120327/precise-alternate-amd64.iso) using the alternate installer from the daily builds for March 27, 2012, I attemted to make a full-disk encrypted setup using LVM. I used the instructions from the isotesting testcase: http://testcases.qa.ubuntu.com/Install/AlternateEncryptedLvm
The install went perfectly. However, when I rebooted, the system hung on a blank screen. I left it for over half an hour, and no response. At this point, I simply typed in the password for the LVM encryption, and the system then continuted to boot normally.
After getting into the system, I tested it (everything was working fine) then rebooted. I experienced the same symptoms (just a blank screen) after each boot.
I believe that there is supposed to be a screen prompting the user for the password for the LVM encryption instead of just a blank screen.
---
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
DefaultPlymouth: /lib/plymouth/themes/lubuntu-logo/lubuntu-logo.plymouth
DistroRelease: Ubuntu 12.04
InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Beta amd64 (20120328)
Package: plymouth 0.8.2-2ubuntu28
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-20-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
ProcEnviron:
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-20-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Tags: precise
TextPlymouth: /lib/plymouth/themes/lubuntu-text/lubuntu-text.plymouth
Uname: Linux 3.2.0-20-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 12/23/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: RQG4110H.86A.0013.2009.1223.1136
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DG41RQ
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE54511-205
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrRQG4110H.86A.0013.2009.1223.1136:bd12/23/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-205:cvn:ct3:cvr: |
Workarounds for this bug:
1) When you land at the blank screen (it is waiting for your LVM encryption password) just type your password. Alternatively, hit one of the up/down arrow keys to get to the GUI and enter your password (you will need to hit backspace twice to remove the two characters that were put in by the one arrow key press)
2) Edit your /boot/grub/grub.cfg file. In the menu entry for the kernel you wish to boot, add the text "plymouth:force-drm" (without the quotes) to the end of the line that starts with "linux /boot/vmzlinux-3.2.....". If you do this workaround, you will need to re-apply this fix anytime the kernel package is updated or grub is otherwise modified as the file is completely re-written each time.
3) Use the un-modified kernel. Read: https://wiki.ubuntu.com/KernelMainlineBuilds to manually download a mainline kernel and install on your system.
---original bug follows---
When installing the lubuntu image as part of the iso testing (lubuntu/daily/20120327/precise-alternate-amd64.iso) using the alternate installer from the daily builds for March 27, 2012, I attemted to make a full-disk encrypted setup using LVM. I used the instructions from the isotesting testcase: http://testcases.qa.ubuntu.com/Install/AlternateEncryptedLvm
The install went perfectly. However, when I rebooted, the system hung on a blank screen. I left it for over half an hour, and no response. At this point, I simply typed in the password for the LVM encryption, and the system then continuted to boot normally.
After getting into the system, I tested it (everything was working fine) then rebooted. I experienced the same symptoms (just a blank screen) after each boot.
I believe that there is supposed to be a screen prompting the user for the password for the LVM encryption instead of just a blank screen.
---
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
DefaultPlymouth: /lib/plymouth/themes/lubuntu-logo/lubuntu-logo.plymouth
DistroRelease: Ubuntu 12.04
InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Beta amd64 (20120328)
Package: plymouth 0.8.2-2ubuntu28
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-20-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
ProcEnviron:
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-20-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Tags: precise
TextPlymouth: /lib/plymouth/themes/lubuntu-text/lubuntu-text.plymouth
Uname: Linux 3.2.0-20-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 12/23/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: RQG4110H.86A.0013.2009.1223.1136
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DG41RQ
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE54511-205
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrRQG4110H.86A.0013.2009.1223.1136:bd12/23/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-205:cvn:ct3:cvr: |
|