Bug#344435: Segmentation fault in gtk_widget_set_sensitive ()
lool at dooz.org
Sun Jan 15 17:28:24 UTC 2006
reassign 344435 bluefish
On Sat, Jan 14, 2006, Daniel Leidert wrote:
> [orginally reported crash in bluefish]
> > Ok. This seems to be a GTK2 bug. So this bug is reassigned to
> > libgtk2.0-0 [..]
> Sorry. Forgot, that I confirmed that bug for bluefish. Removed
> confirmation. A maybe more useful backtrace (also including the bf
> symbols) is attached.
In general, Gtk makes no guarantee not to crash internally after any
critical warning. Your log has two:
(bluefish:5126): Gtk-CRITICAL **: gtk_widget_set_sensitive:
assertion `GTK_IS_WIDGET (widget)' failed
which look like typical programming mistakes in bluefish. Fix them
first, they can be the source of a later crash.
Apart of that, the backtrace you reported is visibly in a callback
handler, and this could typically be a programming mistakes in bluefish
I am not saying that we're sure that there's no Gtk bug, but I'm sure
that you're looking at the wrong backtrace, you'd better get a
backtrace from the point where the first critical warning is thrown.
This can be done with glib's --g-fatal-warnings flag.
Loïc Minier <lool at dooz.org>
Current Earth status: NOT DESTROYED
More information about the Pkg-gnome-maintainers