GNOME Bugzilla – Bug 547429
crash in Terminal:
Last modified: 2008-08-14 19:33:42 UTC
Version: 2.18.4 What were you doing when the application crashed? Distribution: Fedora release 8 (Werewolf) Gnome Release: 2.20.3 2008-01-08 (Red Hat, Inc) BugBuddy Version: 2.20.1 System: Linux 2.6.25.11-60.fc8 #1 SMP Mon Jul 21 02:06:29 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: ClearlooksClassic Icon Theme: Clearlooks Memory status: size: 76984320 vsize: 76984320 resident: 19406848 share: 12181504 rss: 19406848 rss_rlim: 4294967295 CPU usage: start_time: 1218548020 rtime: 10 utime: 8 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-terminal' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1075369280 (LWP 5562)] [New Thread 1123244944 (LWP 5569)] 0x40000416 in __kernel_vsyscall ()
+ Trace 205029
Thread 1 (Thread 1075369280 (LWP 5562))
----------- .xsession-errors --------------------- To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... Gdk-ERROR **: The program 'gnome-terminal' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 1188 error_code 8 request_code 72 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 --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
I installed the debug info packages and am pasting the new output below: Also, a bit of troubleshooting info, when I run gnome-terminal as root it doesn't crash. -Marise Distribution: Fedora release 8 (Werewolf) Gnome Release: 2.20.3 2008-01-08 (Red Hat, Inc) BugBuddy Version: 2.20.1 System: Linux 2.6.25.11-60.fc8 #1 SMP Mon Jul 21 02:06:29 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: ClearlooksClassic Icon Theme: Clearlooks Memory status: size: 77172736 vsize: 77172736 resident: 19415040 share: 12185600 rss: 19415040 rss_rlim: 4294967295 CPU usage: start_time: 1218563378 rtime: 10 utime: 7 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-terminal' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1075369280 (LWP 6998)] [New Thread 1123294096 (LWP 7005)] 0x40000416 in __kernel_vsyscall ()
+ Trace 205040
Thread 1 (Thread 1075369280 (LWP 6998))
Can you run gnome-terminal with the --sync option (make sure there's no terminal process already running) and break on "gdk_x_error" in gdb to get a better trace?
I'm not sure how I'm supposed to execute gnome-terminal with the --sync option unless I do it from the command line which precludes my being able to make sure there's no terminal process already running. Also, I'm not sure what you mean by break on "gdk_x_error" but assuming you mean to only show you the output from lines with gdk_x_error in them, here it is:
+ Trace 205050
-Marise
You can use an xterm to start gnome-terminal: gdb --args `which gnome-terminal` --sync (gdb) b gdk_x_error now answer the question in the affirmative (gdb) run .... then after reproducing the crash the breakpoint should be hit: (gdb) where
Here's the output per your instructions: (gdb) run Starting program: /usr/bin/gnome-terminal --sync [Thread debugging using libthread_db enabled] Breakpoint 2 at 0x2729246: file gdkmain-x11.c, line 614. Pending breakpoint "gdk_x_error" resolved [New Thread 1075369280 (LWP 8027)] [Detaching after fork from child process 8033. (Try `set detach-on-fork off'.)] [Detaching after fork from child process 8034.] [New Thread 1123416976 (LWP 8036)]
+ Trace 205052
Thread 1075369280 (LWP 8027)
Thanks! It does look like the crash occurs in the libcairo library, https://bugs.freedesktop.org/show_bug.cgi?id=4618 which is a duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=10250 which is fixed since cairo version 1.4.2 [https://bugs.freedesktop.org/show_bug.cgi?id=10250#c13]. You will need to upgrade to this or a later version.
I just updated to cairo 1.6.4 and the crash is still occurring.
I've added a notice of that to the upstream bug at https://bugs.freedesktop.org/show_bug.cgi?id=10250 .
*** Bug 547507 has been marked as a duplicate of this bug. ***