Internal display not disabled for a docked Toshiba Portege Z30-A with closed lid and external monitor attached

[Vincent Fortier]

A grey background appears on the external monitor attached to the docking station of a (docked) Toshiba Portege Z30-A after booting up the system even when the lid is closed. After opening the lid it turns out that the login manager is actually shown on the internal display which should have been turned off altogether.

This bug is similar to this one in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1430259
More info was also found here:
https://bugzilla.redhat.com/show_bug.cgi?id=1447402

As per https://bugzilla.redhat.com/show_bug.cgi?id=1430259#c3 it seems that commit 77e9a4aa9de10cc1418bf9a892366988802a8025 may be the culprit as of kernel 4.10.10.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-generic 4.10.0.24.26
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC3: fortierv 4262 F.... pulseaudio
 /dev/snd/controlC2: fortierv 4262 F.... pulseaudio
 /dev/snd/controlC1: fortierv 4262 F.... pulseaudio
 /dev/snd/controlC0: fortierv 4262 F.... pulseaudio
CurrentDesktop: XFCE
Date: Wed Jun 28 05:56:01 2017
HibernationDevice: RESUME=UUID=5dac600d-b269-4c43-8afe-29a64fc9c65a
InstallationDate: Installed on 2015-04-16 (804 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: TOSHIBA PORTEGE Z30-A
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=7a8b097c-cbe0-4fff-bb5f-633f0e625cef ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-24-generic N/A
 linux-backports-modules-4.10.0-24-generic N/A
 linux-firmware 1.164.1
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-01-28 (150 days ago)
dmi.bios.date: 09/02/2015
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 4.20
dmi.board.asset.tag: 0000000000
dmi.board.name: PORTEGE Z30-A
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:bvrVersion4.20:bd09/02/2015:svnTOSHIBA:pnPORTEGEZ30-A:pvrPT241C-02L002:rvnTOSHIBA:rnPORTEGEZ30-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: PORTEGE Z30-A
dmi.product.version: PT241C-02L002
dmi.sys.vendor: TOSHIBA

[Joseph Salisbury (jsalisbury)]

This change was made by a bot.

[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.12 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.12

[Vincent Fortier (th0ma7)]

Confirmed, fixed upstream.

whoami@locahost:~$ uname -a
Linux eclipse 4.12.0-041200-generic #201707022031 SMP Mon Jul 3 00:32:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
whoami@locahost:~$ cat /etc/issue
Ubuntu 17.04 \n \l