Segmentation fault (core dumped) at feisty

Happens on my feisty too

#0 0xb7dc2e03 in gtk_notebook_draw_focus (widget=0x80d6000, event=0x812cb70)
    at gtknotebook.c:2971
#1 0xb7dc31fa in gtk_notebook_expose (widget=0x80d6000, event=0x812cb70)
    at gtknotebook.c:2026
#2 0xb7da5180 in _gtk_marshal_BOOLEAN__BOXED (closure=0x80ac848,
    return_value=0xbf8646c0, n_param_values=2, param_values=0xbf86479c,
    invocation_hint=0xbf8646ac, marshal_data=0xb7dc2ee0) at gtkmarshalers.c:84
#3 0xb79c9e49 in ?? () from /usr/lib/libgobject-2.0.so.0
#4 0x080ac848 in ?? ()
#5 0xbf8646c0 in ?? ()
#6 0x00000002 in ?? ()
#7 0xbf86479c in ?? ()
#8 0xbf8646ac in ?? ()
#9 0xb7dc2ee0 in ?? () at gtknotebook.c:2989 from /usr/lib/libgtk-x11-2.0.so.0
#10 0xb79cb2db in g_closure_unref () from /usr/lib/libgobject-2.0.so.0
#11 0xb79cb70d in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#12 0xb79dc733 in ?? () from /usr/lib/libgobject-2.0.so.0

This is just a guess but there is a patch in current gnome cvs:

if (GTK_WIDGET_HAS_FOCUS (widget) && GTK_WIDGET_DRAWABLE (widget) &&
- notebook->cur_page->tab_label->window == event->window &&
- notebook->show_tabs && notebook->cur_page)
+ notebook->show_tabs && notebook->cur_page &&
+ notebook->cur_page->tab_label->window == event->window)

And it has comment:

"(gtk_notebook_draw_focus): fix potential crasher if cur_page is NULL"

So is it possible in this case that cur_page is NULL?

My guess was right, I tester that patch and pcmanx doesn't crash anymore.

Orinal patch can be found from here here: http://cvs.gnome.org/bonsai/cvsquery.cgi?branch=&dir=gtk%2B&who=carlosg&date=explicit&mindate=2006-12-28%2011:37&maxdate=2006-12-28%2011:39

Fixed in SVN head.

Here is the fixlet attached.

Now we have two fixes for this. I thinkt the main culprit is still libgtk2 gtknotebook.c. This fixlet from jser is more like workaround for this.

That gtknotebook.c bug can cause other segfaults too, so I think it should be fixed as well.

Here's a debdiff for gtk bug.

We have gtk 2.10.9 in feisty now. Could you confirm that it fixes the bug, and close the bug? Thanks.

This bug have been fixed... thanks

This bug has been fixed... thanks

marking fixed then