| 2014-10-01 18:05:35 |
Brandon |
description |
Upon launching a game that runs the Unity Game Engine, gnome-system-monitor will segfault 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) |
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) |
|
