GNOME Bugzilla – Bug 359614
crash in Terminal: I pressed Ctrl-Shift-T i...
Last modified: 2009-11-07 17:45:31 UTC
Version: 2.16.0 What were you doing when the application crashed? I pressed Ctrl-Shift-T in gnome-terminal to open a new tab. Distribution: Debian testing/unstable Gnome Release: 2.16.0 2006-09-12 (Debian) BugBuddy Version: 2.16.0 Memory status: size: 148680704 vsize: 148680704 resident: 19046400 share: 11329536 rss: 19046400 rss_rlim: -1 CPU usage: start_time: 1159964311 rtime: 810 utime: 744 stime: 66 cutime:2960 cstime: 775 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47867403417280 (LWP 4377)] [New Thread 1082132832 (LWP 4381)] 0x00002b88fc09100f in waitpid () from /lib/libpthread.so.0
+ Trace 74505
Thread 1 (Thread 47867403417280 (LWP 4377))
The following appeared in .xsession-errors: (gnome-terminal:4377): Gtk-CRITICAL **: gtk_style_detach: assertion `GTK_IS_STYLE (style)' failed (gnome-terminal:4377): GLib-GObject-WARNING **: gsignal.c:2180: invalid object type ` (gnome-terminal:4377): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gnome-terminal:4377): Gtk-CRITICAL **: _gtk_style_peek_property_value: assertion `GTK_IS_STYLE (style)' failed
*** Bug 364807 has been marked as a duplicate of this bug. ***
FWIW: This are OK up to the 10th frame, in gtk_box_forall: note that its local ‘child’ is NULL: this is bad. I guess this is why the call to widget_add_child_draw_rectangle is getting 0x3 as a widget... (The callback argument to gtk_box_forall is here 0x30, which can't be right, but widget_add_child_draw_rectangle does get called, which is fine; probably something went amiss with the stacktrace.) I'd love to know what box is it that this is happening: we are in the middle of a notebook_forall, so the box is either one of the hboxes we use for the tabs or the hbox which contains the terminal and the scrollbar... The exact same observations apply to the stack in the dup.
I'd discount |child == 0| in #10 as gdb fuzziness. If it really had been NULL, gtk_box_forall would have crashed right there on a NULL-dereference. I think the warnings are much more informative: there's a widget in the hierarchy somewhere which has widget->style == NULL, and thus gtk_style_get (widget, "draw-border",...) crashes on this line in gtkwidget.c:gtk_widget_style_get_valist: peek_value = _gtk_style_peek_property_value (widget->style, G_OBJECT_TYPE (widget), pspec, (GtkRcPropertyParser) g_param_spec_get_qdata (pspec, quark_property_parser)); G_VALUE_LCOPY (peek_value, var_args, 0, &error); |peek_value| will be NULL, and G_VALUE_LCOPY dereferences it. The other warning: (gnome-terminal:4377): Gtk-CRITICAL **: gtk_style_detach: assertion `GTK_IS_STYLE (style)' failed shows that there's almost certainly a mismatched gtk_style_attach/gtk_style_detach somewhere.
*** Bug 361477 has been marked as a duplicate of this bug. ***
*** Bug 404294 has been marked as a duplicate of this bug. ***
*** Bug 381993 has been marked as a duplicate of this bug. ***
*** Bug 391250 has been marked as a duplicate of this bug. ***
*** Bug 416165 has been marked as a duplicate of this bug. ***
*** Bug 395528 has been marked as a duplicate of this bug. ***
*** Bug 479318 has been marked as a duplicate of this bug. ***
The latest duplicate happened in Epiphany, moving this to GTK.
This crash report was submitted against version 2.9 or 2.10 of GTK. This version is no longer maintained, which means that it will not receive any further security or bug fix updates. The current stable GTK version is 2.16 and include in recent GNOME distributions. Can you please check again whether this issue still happens in GTK 2.14 or 2.16 and update this report by adding a comment and changing the "Version" field? Thanks a lot. Again thank you for reporting this bug and we are sorry it could not be fixed for the version you originally used here.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!