entering crypto passphrase while notebook is mounted to docking station results in sleep state

[Hauke Bruno]

After upgrading to the current kernel (4.4.0-34-generic) I am not able to log in to my Kubuntu 16.04 at a Lenovo T430 while it is mounted to a docking station.

Ubuntu boots until I need to enter the passphrase for my crypted disk, but anyhow the system then enters a sleep state (small moon icon is blinking). Inside the docking station I am not able to leave that state.

Outside the docking station the problem doesn't occur.

While using the 4.4.0-31-generic kernel, everything works fine.

I am not sure how to debug that behavior, so if some more information is needed please leave me a note.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Aug 9 10:31:09 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-05-12 (88 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

[Paul White (paulw2u)]

Hauke, as you're saying that the kernel is the cause of your problems I'm reassigning this bug against the kernel.

You also say that using your laptop in a docking station is when problems occur, another reason to reassign against the kernel - see https://wiki.ubuntu.com/Bugs/FindRightPackage#Hardware_Malfunctions

[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 1611283

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.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1

[Joseph Salisbury (jsalisbury)]

Comment #4 should have said the "latest v4.8 kernel"

[Hauke Bruno (haukebruno)]

Thanks Paul, I don't know where that xorg tag came from.

I finally installed the latest 4.8rc1 and rc2 kernels and will be able to update this bug tomorrow. Unfortunately I can't create the missing logs via apport-collect, due to some missing python qt module.

[Hauke Bruno (haukebruno)]

So sadly neither 4.8.0-040800rc1.201608072231 nor 4.8.0-040800rc2.201608142332 resolves the problem. Is there any kind of log or debugging output I can send you?

[Joseph Salisbury (jsalisbury)]

Just to confirm, if you select the Ubuntu 4.4.0-31 kernel from the GRUB menu, this bug does not exist? If that is the case, we can perform a kernel bisect to identify the commit that introduced this regression.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]