monitors not disconnected after undocking

[Jochen Schroeder]

I have a Lenovo X1 Carbon (4th gen) and using the Lenovo one-link+ docking station. The laptop is connected through the docking station to 2 external monitors when docked. When undocking the laptop, the laptop does not detect that the monitors have been disconnected (leaving X in a somewhat unworkable state). Even worse, when undocking with thelid closed (which would previously have resulted in suspend) the laptop now starts working hard and the fan starts spinning up (which is particularly bad when forgetting about this and placing the laptop in a bag). The laptop also becomes very unresponsive to X actions, e.g. xrandr --query takes a a couple of seconds, switching to the console takes > 10s.
This seems to be related to the following Fedora bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1392885
which reports almost identical issues. I have not been able to try a new kernel yet to see if issues are fixed.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-30-generic 4.8.0-30.32
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jschrod 2726 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Jan 10 21:28:42 2017
HibernationDevice: RESUME=UUID=de3940cc-d877-44b6-9b33-16a8abd6701c
InstallationDate: Installed on 2016-10-01 (101 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:5248 IMC Networks
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20FB006AMS
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed root=UUID=a43e313c-5c49-4859-a1aa-4446f2b9c455 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-30-generic N/A
 linux-backports-modules-4.8.0-30-generic N/A
 linux-firmware 1.161.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET43W (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FB006AMS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB006AMS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB006AMS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20FB006AMS
dmi.product.version: ThinkPad X1 Carbon 4th
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 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.10-rc3

[Jochen Schroeder (cyco)]

This happened after upgrade to 16.10 I believe (unfortunately I am not 100% sure about this). I can confirm that this is fixed using 4.9.2-040902-generic from mainline kernels.

[Jochen Schroeder (cyco)]

Also confirmed fixed on 4.10.0-041000rc3-generic