gdm-x-session crash: glamor_composite_largepixmap_region: Assertion `0' failed.

Bug #1773665 reported by Hans Deragon on 2018-05-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Undecided
Unassigned

Bug Description

Whenever as root in a terminal, I start 'gvim', the whole windows system crashes and the user find himself on the gdm login screen. Windowing session has been lost.

It only occurs with gvim. I tried xterm, terminator and gthumb as root and these graphical application do not cause the crash.

Ubuntu 18.04 Bionic Beaver, all packages up to date as of 2018-05-27 11:26:45 EDT.

Following is the trace found under /var/log/syslog:

May 27 10:43:45 demloka gnome-shell[21426]: g_array_unref: assertion 'array' failed
May 27 10:43:45 demloka gnome-shell[21426]: message repeated 2 times: [ g_array_unref: assertion 'array' failed]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: Xorg: ../../../../glamor/glamor_largepixmap.c:1449: glamor_composite_largepixmap_region: Assertion `0' failed.
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) Backtrace:
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5619d46e58ad]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 1: /usr/lib/xorg/Xorg (0x5619d452d000+0x1bc649) [0x5619d46e9649]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f4c99632000+0x12890) [0x7f4c99644890]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xc7) [0x7f4c9927fe97]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x141) [0x7f4c99281801]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (0x7f4c99241000+0x3039a) [0x7f4c9927139a]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f4c99241000+0x30412) [0x7f4c99271412]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (0x7f4c95ec3000+0x21e21) [0x7f4c95ee4e21]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 8: /usr/lib/xorg/modules/libglamoregl.so (0x7f4c95ec3000+0x16362) [0x7f4c95ed9362]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 9: /usr/lib/xorg/Xorg (0x5619d452d000+0x13d896) [0x5619d466a896]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 10: /usr/lib/xorg/Xorg (0x5619d452d000+0x13312c) [0x5619d466012c]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 11: /usr/lib/xorg/Xorg (0x5619d452d000+0x52e98) [0x5619d457fe98]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 12: /usr/lib/xorg/Xorg (0x5619d452d000+0x56ee0) [0x5619d4583ee0]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x7f4c99262b97]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2a) [0x5619d456db8a]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: Fatal server error:
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) Caught signal 6 (Aborted). Server aborting
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: Please consult the The X.Org Foundation support
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: #011 at http://wiki.x.org
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: for help.
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) Please also check the log file at "/home/hans/.local/share/xorg/Xorg.0.log" for additional information.
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (II) AIGLX: Suspending AIGLX clients for VT switch
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) Server terminated with error (1). Closing log file.
May 27 10:43:49 demloka update-notifier[22815]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Hans Deragon (deragon) wrote :
tags: added: crash gdm3
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your bug report is missing crash details. In order to debug a crash we will need a crash report. To create one, please follow these steps:

1. If you are not running a future development release of Ubuntu then apply the workaround from bug 994921.
2. If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport.
3. If the crash is in Xorg then uncomment this option from /etc/gdm3/custom.conf:
   # Additionally lets the X server dump core if it crashes
   #Enable=true
4. Reboot.
5. Reproduce the crash.
6. Look in /var/crash for crash files and when found, run:
   ubuntu-bug /var/crash/YOURFILE.crash
7. Add a comment here telling us the ID of the new bug that was created in step 6.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments, and doing so is also a security risk for yourself.

Changed in gdm3 (Ubuntu):
status: New → Incomplete
Daniel van Vugt (vanvugt) wrote :

Alternatively, just look up previous crash reports from your system here:

  https://errors.ubuntu.com/user/ID
  where ID is the contents of /var/lib/whoopsie/whoopsie-id

If you find relevant crashes there then please send us links to them.

Daniel van Vugt (vanvugt) wrote :

Thanks.

Now tracking in bug 1773873 and bug 1773875.

Daniel van Vugt (vanvugt) wrote :

Although it sounds like this crash pre-dates and triggers bug 1773875.

If you can then please look for more crash reports.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers