This looked like the same thing as when Bug #1477574 and Bug #1477566 happened just now. I had Chrome, Terminal & Eclipse open on my Ubuntu PC and was focused on using my laptop via Synergy. In my Synergy setup the Ubuntu PC is the server and the laptop is the client.
As in the two bugs I mentioned, the Ubuntu machine seemed to reset back to the login screen. Unlike the last time nothing complained about out of date packages this time. I had not run the upgrade when this bug happened. I have now updated however.
Yesterday there was a power cut to this building. I am starting to worry about my hardware integrity. The previous software update I did was at 2015-07-22 08:15:01, some 29 hours before the first time I saw an issue and now I have hit the login screen twice in about 2 hours.
Start-Date: 2015-07-22 08:13:51
Commandline: aptdaemon role='role-commit-packages' sender=':1.712'
Upgrade: mysql-server-core-5.5:amd64 (5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), mysql-server-5.5:amd64 (5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), mysql-client-core-5.5:amd64 (5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), mysql-client:amd64 (5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), google-chrome-stable:amd64 (43.0.2357.134-1, 44.0.2403.89-1), thunderbird-locale-en-us:amd64 (31.7.0+build1-0ubuntu0.14.04.1, 31.8.0+build1-0ubuntu0.14.04.1), thunderbird:amd64 (31.7.0+build1-0ubuntu0.14.04.1, 31.8.0+build1-0ubuntu0.14.04.1), thunderbird-locale-en:amd64 (31.7.0+build1-0ubuntu0.14.04.1, 31.8.0+build1-0ubuntu0.14.04.1), mysql-client-5.5:amd64 (5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), mysql-common:amd64 (5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), thunderbird-gnome-support:amd64 (31.7.0+build1-0ubuntu0.14.04.1, 31.8.0+build1-0ubuntu0.14.04.1), libmysqlclient18:amd64 (5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), libmysqlclient18:i386 (5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), mysql-server:amd64 (5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1)
End-Date: 2015-07-22 08:15:01
Having said that the power-cut was bout 24 hours before the problem was first seen.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
Uname: Linux 4.1.0-040100rc8-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.14.1-0ubuntu3.11
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: Thu Jul 23 15:30:26 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
InstallationDate: Installed on 2015-03-12 (132 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100rc8-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-DS2V
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: H81M-DS2V
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Jul 23 15:27:58 2015
xserver.configfile: default
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 26053
vendor NEC
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2
Thomas A. F. Thorne, thank you for reporting this and helping make Ubuntu better. As per http://
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:/
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, and the information above is provided, then please mark this report Status New.
Thank you for your understanding.