Session exits when removing external monitor

[Szilard Novaki]

I use a dual monitor setup at work (notebook monitor + external). When I remove the external monitor, my gui session exits and I have to login again. It happens all the time now.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
Uname: Linux 3.13.0-77-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Feb 15 20:35:30 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.36, 3.13.0-76-generic, x86_64: installed
 virtualbox, 4.3.36, 3.13.0-77-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:10fd]
InstallationDate: Installed on 2014-06-22 (603 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: ASUSTeK COMPUTER INC. S400CA
PlymouthDebug: Error: [Errno 13] Engedély megtagadva: '/var/log/plymouth-debug.log'
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic.efi.signed root=UUID=3e4b447b-c8f7-4f5f-90bb-7fb707fbb116 ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/05/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: S400CA.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: S400CA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS400CA.208:bd02/05/2013:svnASUSTeKCOMPUTERINC.:pnS400CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS400CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: S400CA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Feb 15 20:34:28 2016
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 12348
 vendor AUO
xserver.version: 2:1.15.1-0ubuntu2.7

[Szilard Novaki (novaki)]

Thank you for your help, I've updated the BIOS.

novaki@novaki-S400CA:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
S400CA.210
01/27/2014

[Szilard Novaki (novaki)]

There was a change. My session exits on reconnecting the the external monitor, not on disconnection. I consider this a small improvement, but there's some more to go :)

[penalvch (penalvch)]

Szilard Novaki, to clarify, after you log back in from the ended session, is there a crash file in /var/crash?

[Szilard Novaki (novaki)]

I've tried again and again. It also happened on external monitor disconnect now (kind of random).

There isn't any new crash files.

Do you have some guidelines how to track down this problem? It really annoys me now. I debug, recompile, anything you need, just to get it fixed. Thank you.

[penalvch (penalvch)]

Szilard Novaki, to confirm, apport is enabled as outlined in https://help.ubuntu.com/community/ReportingBugs#Reporting_an_application_crash_in_the_stable_release ?

[Szilard Novaki (novaki)]

Yes, just like that. I also tried the "Reporting a system crash" part, but the X debugging link to wiki (https://wiki.ubuntu.com/X/Debugging) does not work now.

[penalvch (penalvch)]

Szilard Novaki, after the log out happens, could you please attach your /var/log/Xorg.0.log file?

It should contain a backtrace that correlates to the time when you are logged out.

[Szilard Novaki (novaki)]

I've attached my Xorg.0.log after the session exited and I saw the new login screen (switched to console CTRL-ALT-F1, and copied the /var/log/Xorg.0.log* to a safe location).

Imho, this is the log of the new Xorg instance. I suspect that as there is a file Xorg.0.log.old with the same timestamp as the new one.

Unfortunately there is no backtrace, it detects that the monitor is removed:
[ 33982.721] (II) intel(0): resizing framebuffer to 1366x768
[ 33982.724] (II) intel(0): switch to mode 1366x768@60.1 on LVDS1 using pipe 0, position (0, 0), r
otation normal, reflection none
[ 33983.053] (II) config/udev: removing device Atmel Atmel maXTouch Digitizer
[ 33983.074] (II) evdev: Atmel Atmel maXTouch Digitizer: Close
[ 33983.075] (II) UnloadModule: "evdev"
[ 33983.696] (II) config/udev: Adding input device Atmel Atmel maXTouch Digitizer (/dev/input/even
t10)

Whats worse it seems that the server terminated successfully:
$ tail -10 Xorg.0.log.old
[ 33987.674] (II) UnloadModule: "evdev"
[ 33987.674] (II) evdev: ASUS USB2.0 Webcam: Close
[ 33987.674] (II) UnloadModule: "evdev"
[ 33987.674] (II) evdev: Sleep Button: Close
[ 33987.674] (II) UnloadModule: "evdev"
[ 33987.674] (II) evdev: Power Button: Close
[ 33987.674] (II) UnloadModule: "evdev"
[ 33987.674] (II) evdev: Video Bus: Close
[ 33987.674] (II) UnloadModule: "evdev"
[ 33987.714] (EE) Server terminated successfully (0). Closing log file.

However there isn't any crash files in /var/crash. Any ideas? Should I start a session from command line?

[penalvch (penalvch)]

Szilard Novaki, to see if this is already resolved, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

[Szilard Novaki (novaki)]

Finally, I made some progress, hope it helps you.

I've checked the daily image, this is what I've found:
 * In the default config, there removal of default external monitor is handled correctly.
 * Then I arranged my displays as I use it every day (see attached image)
 * The unity-settings-daemon has crashed after disconnecting the external monitor (apport popped up, but I did not file a new bug).

So I thought that I have the same thing with 14.04 too, but maybe I have disabled reporting errors for settings-daemon earlier. I've found a file called ~/.apport-ignore.xml, and yes, it contained the settings daemon. I removed it from ignore and now I have crash file around the time of monitor removal, and its the crash of settings daemon.

[Szilard Novaki (novaki)]

I forgot to mention that the xenial session did not end after the crash of settings daemon, but the 14.04 one did.

[penalvch (penalvch)]

Szilard Novaki, please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open a terminal, navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and file the crash report via:
sudo ubuntu-bug /var/crash/FILENAME.crash

Where FILENAME is the actual name of the file found in the folder.

However, this report is being closed since the process outlined above will deal with this issue more efficiently.

Also, please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs