Xorg crash

Bug #1803583 reported by AdrianChallinor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This bug is happening approximately every 24 hours. Any changes to open files are lost (DATA LOSS BEING EXPERIENCED).

System is a clean install of Ubuntu 18.10 (XUbuntu). System is up to date with all publish updates.

System has two graphics card:
1) NVidia GK208B [GeForce GT 710]
2) NVidia GT218 [GeForce 210]

I am reluctant to switch to nvida drivers as google searches indicate that they do not support dual head systems.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Nov 15 16:18:02 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
 virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b]
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:852d]
InstallationDate: Installed on 2018-11-07 (7 days ago)
InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=9d341c90-212b-47c2-b0f0-a7e607ee860b ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/04/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2901
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH 990FX R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2901:bd05/04/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.sku: SKU
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2018-11-11T15:48:31.589269
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

Revision history for this message
AdrianChallinor (adrian-challinor) wrote :
Revision history for this message
AdrianChallinor (adrian-challinor) wrote :

To confirm: The bug being experienced is that the main screen goes black for three seconds, then is replaced by the greeter. The current session is killed, with no attempt at a clean shutdown.

The bug results in an Xorg Crash log, see above.

I have searched for solutions, but most seem to revolve around removing the nouveau drivers and installing the NVidia driver. However, there are other reports that this does not support dual screens unless xinerama is used.

Happy to try the nvidea driver provided
a) Someone lets me know definitively how to get back! or
b) Someone lets me know that dual screen will work.

You may assume that I am technically competent and willing to try most things that do not destroy my box!

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks for the bug report.

The backtrace in your log may not be completely accurate:

[ 83021.728] (EE) Backtrace:
[ 83021.730] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x560581eab229]
[ 83021.731] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f3cc6de2e1f]
[ 83021.731] (EE) 2: /usr/lib/xorg/modules/libglamoregl.so (glamor_get_pixmap_texture+0x7d) [0x7f3cc557244d]
[ 83021.732] (EE) 3: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x7b08) [0x7f3cc5584988]
[ 83021.732] (EE) 4: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x7f3c) [0x7f3cc558512c]
[ 83021.732] (EE) 5: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x854e) [0x7f3cc55858ce]
[ 83021.732] (EE) 6: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0xa54c) [0x7f3cc558952c]
[ 83021.733] (EE) 7: /usr/lib/xorg/Xorg (DamageRegionAppend+0x6af) [0x560581e2d79f]
[ 83021.733] (EE) 8: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x1137e) [0x7f3cc559787e]
[ 83021.734] (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x41a5) [0x560581e260c5]
[ 83021.734] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x35e) [0x560581d4c97e]
[ 83021.734] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3b6) [0x560581d50906]
[ 83021.734] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f3cc6c0409b]
[ 83021.734] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x560581d3a67a]

so we will need a better stack trace. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

affects: xorg (Ubuntu) → xorg-server (Ubuntu)
Changed in xorg-server (Ubuntu):
status: New → Incomplete
Revision history for this message
AdrianChallinor (adrian-challinor) wrote : Re: [Bug 1803583] Re: Xorg crash

sudo ubuntu-bug _usr_lib_xorg_Xorg.0.crash

After updating /etc/apport/crashdb.conf as per bug 994921new bug created:

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1803694

On 16/11/2018 01:58, Daniel van Vugt wrote:
> Thanks for the bug report.
>
> The backtrace in your log may not be completely accurate:
>
> [ 83021.728] (EE) Backtrace:
> [ 83021.730] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x560581eab229]
> [ 83021.731] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f3cc6de2e1f]
> [ 83021.731] (EE) 2: /usr/lib/xorg/modules/libglamoregl.so (glamor_get_pixmap_texture+0x7d) [0x7f3cc557244d]
> [ 83021.732] (EE) 3: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x7b08) [0x7f3cc5584988]
> [ 83021.732] (EE) 4: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x7f3c) [0x7f3cc558512c]
> [ 83021.732] (EE) 5: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x854e) [0x7f3cc55858ce]
> [ 83021.732] (EE) 6: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0xa54c) [0x7f3cc558952c]
> [ 83021.733] (EE) 7: /usr/lib/xorg/Xorg (DamageRegionAppend+0x6af) [0x560581e2d79f]
> [ 83021.733] (EE) 8: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x1137e) [0x7f3cc559787e]
> [ 83021.734] (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x41a5) [0x560581e260c5]
> [ 83021.734] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x35e) [0x560581d4c97e]
> [ 83021.734] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3b6) [0x560581d50906]
> [ 83021.734] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f3cc6c0409b]
> [ 83021.734] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x560581d3a67a]
>
> so we will need a better stack trace. To help us find the cause of the
> crash please follow these steps:
>
> 1. Look in /var/crash for crash files and if found run:
> ubuntu-bug YOURFILE.crash
> Then tell us the ID of the newly-created bug.
>
> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
> ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
> Do you find any links to recent problems on that page? If so then please
> send the links to us.
>
> 3. If step 2 also failed then apply the workaround from bug 994921,
> reboot, reproduce the crash, and retry step 1.
>
> Please take care to avoid attaching .crash files to bugs as we are
> unable to process them as file attachments. It would also be a security
> risk for yourself.
>
> ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
>
> ** Changed in: xorg-server (Ubuntu)
> Status: New => Incomplete
>
--
Adrian Challinor (FRAS)
m: +44-7860-290-883
e: <email address hidden>
w: https://www.osiris.co.uk

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg-server (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.