Crypt password screen not responding

[Piotr Piwonski]

Hi,

During booting of system when the password screen for a encrypted device is presented there is no response.
The screen is not accepting any input.
I can switch to another screen using ctrl+alt+F# key and see blinking cursor.
Switching back to ctrl+alt+F7 is showing message and all entered keys on screen.

Rebooting by ctrl+alt+del or power button causes that the system boots to a text version of that screen where I can enter the password and system boots to OS.

Not sure what could be gathered during this event to assist in identifying the problem since I have no possibility to get any logs and decrypt the disk :(

Regards,
Peter

Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message:
starting version 219

The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible
---
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ppiwonsk 1929 F.... pulseaudio
 /dev/snd/controlC1: ppiwonsk 1929 F.... pulseaudio
DistroRelease: Ubuntu 15.04
InstallationDate: Installed on 2015-06-03 (122 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: TOSHIBA TECRA Z40-B
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic root=/dev/mapper/ubuntu--vg-root ro
ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-30-generic N/A
 linux-backports-modules-3.19.0-30-generic N/A
 linux-firmware 1.143.3
Tags: vivid
Uname: Linux 3.19.0-30-generic x86_64
UpgradeStatus: Upgraded to vivid on 2015-08-02 (62 days ago)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 04/10/2015
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 3.1A
dmi.board.asset.tag: 0000000000
dmi.board.name: TECRA Z40-B
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.1A:bd04/10/2015:svnTOSHIBA:pnTECRAZ40-B:pvrPT45GE-06S03C0V:rvnTOSHIBA:rnTECRAZ40-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: TECRA Z40-B
dmi.product.version: PT45GE-06S03C0V
dmi.sys.vendor: TOSHIBA

[Piotr Piwonski (bbrowaros)]

More details about my system:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.04
DISTRIB_CODENAME=vivid
DISTRIB_DESCRIPTION="Ubuntu 15.04"
NAME="Ubuntu"
VERSION="15.04 (Vivid Vervet)"

3.19.0-30-generic #33-Ubuntu

[Ubuntu Foundations Team Bug Bot (crichton)]

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/1502055/+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.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1502055

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Piotr Piwonski (bbrowaros)]

I'm unable to run apport-collect 1502055

[Piotr Piwonski (bbrowaros)]

I've applied workaround and till now the issue did not appear.
I've removed from /etc/default/grub options spash and quiet from the GRUB_CMDLINE_LINUX_DEFAULT.
used: # sudo update-grub to apply changes and now the "nice" screen promping for password is not showing up. The issue also is not appearing.

I've notice that when I removed that option temporary by editing GRUB options during start (via e) I did not hit this issue.

This would indicate that the problem is with the graphical env for the crypt screen. Not sure if this will help anyone but this is what I've got.

Regards,
Peter

[Piotr Piwonski (bbrowaros)]

Hi Christopher,

Problem is that when I run the apport-collect I get:
"ERROR: connecting to Launchpad failed: [Errno 13] Permission denied: '/home/ppiwonsk/.cache/apport/launchpad.credentials'"
Not this file does not exists. When I run this as root I got a infinite loop on my new firefox window. I'm using proxy connection so I'm not sure if this has something in common.

Let me know if you have any idea how to change this?

Regards,
Peter

[Mark Adams (kramsmada)]

I'm experiencing the same issue running after upgrading to 3.19.0-30-generic.
If I downgrade to 3.19.0-28-generic, the password prompt for my encrypted disk behaves normally and I'm able to boot.

[penalvch (penalvch)]

Mark Adams, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Pascal Schwarz (iso-thinktux)]

This problem also started happening since updating to 3.19.0-30. I'm running Ubuntu 15.04 on a Lenovo X1 Carbon 3rd generation.

Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, integrated graphics.

[Mark Adams (kramsmada)]

@penalvch: As requested, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502598

[penalvch (penalvch)]

Pascal Schwarz, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Piotr Piwonski (bbrowaros)]

Hi,

I've got problem, when starting from live cd I cannot run apport-collect. It is saying that I'm missing python-apport package. Now since this is live env attempt of installing it will fail with no space on device.
The current env when attempting to run apport-collect is reporting some problems.

I'm still investigating this.

Regards,
Peter

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

apport information

[Piotr Piwonski (bbrowaros)]

OK manage to start this and upload all the data.
Hope that this will help.

Regards,
Peter

[penalvch (penalvch)]

Piotr Piwonski, as per http://www.toshiba.co.uk/innovation/download_bios.jsp?service=UK an update to your computer's buggy and outdated BIOS is available (3.20). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid.

Thank you for your understanding.