gnome-system-monitor crashes when Unity3D games are launched.

Bug #1376057 reported by Brandon
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
New
Undecided
Unassigned
gnome-system-monitor (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Upon launching a game that runs the Unity Game Engine, gnome-system-monitor will SIGTRAP with the following output:

brandon@Desktop:~$ gnome-system-monitor

** (gnome-system-monitor:6342): WARNING **: SELinux was found but is not enabled.

(gnome-system-monitor:6342): Gdk-ERROR **: The program 'gnome-system-monitor' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 68264 error_code 8 request_code 62 (core protocol) minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)

Revision history for this message
Brandon (brandon-lee-mcanally) wrote :

Added attachment.

Revision history for this message
Brandon (brandon-lee-mcanally) wrote :
Download full text (4.0 KiB)

gdb output follows:

Starting program: /usr/bin/gnome-system-monitor
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffeba2c700 (LWP 6472)]
[New Thread 0x7fffea9ef700 (LWP 6473)]

** (gnome-system-monitor:6471): WARNING **: SELinux was found but is not enabled.

(gnome-system-monitor:6471): Gdk-ERROR **: The program 'gnome-system-monitor' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 2298 error_code 8 request_code 62 (core protocol) minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Program received signal SIGTRAP, Trace/breakpoint trap.
0x00007ffff487fc13 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) next
Single stepping until exit from function g_logv,
which has no line number information.
0x00007ffff487fd72 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) bt
#0 0x00007ffff487fd72 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x00007ffff66f5351 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#2 0x00007ffff66fdab1 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#3 0x00007ffff2f0354b in _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#4 0x00007ffff2f005e7 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#5 0x00007ffff2f00695 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#6 0x00007ffff2f01578 in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#7 0x00007ffff2efd0cd in XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#8 0x00007ffff5b8e0ef in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#9 0x00007ffff5b8ed90 in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#10 0x00007ffff5b8be6a in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#11 0x00007ffff5b5deaf in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#12 0x00007ffff5b29348 in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#13 0x00007ffff5b29bfa in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#14 0x00007ffff5b5ac48 in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#15 0x00007ffff5b5b09e in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#16 0x00007ffff5b5b116 in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#17 0x00007ffff5b19929 in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#18 0x00007ffff5b5e30c in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#19 0x00007ffff5b20f94 in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#20 0x00007ffff5b148e1 in cairo_mask ()
   from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#21 0x00007ffff5b14966 in cairo_mask_surface ()
---Type <return> to continue, or q <return> to quit---
   from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#22 0x00007ffff79b355f in ?? () from /usr/lib/x86_64-linux-gnu/libwnck-3.so.0
#23 0x00007ffff79b4...

Read more...

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

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-system-monitor (Ubuntu):
status: New → Confirmed
Revision history for this message
Michael Gratton (mjog) wrote :

Same thing happens to Epiphany.

Seems to be a Cairo bug/issue?

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

Other bug subscribers

Bug attachments

Remote bug watches

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