Bug#303341: cannot reproduce

[Matt Draisey]

On Thu, 2005-04-14 at 00:42, Gustavo Noronha Silva wrote:
> Hello,
> 
> I'm not able to reproduce this bug...  could be caused by an earlier
> version of GTK+ than I have installed, maybe... would you mind trying to
> upgrade your system and trying to reproduce this again?
> 
> We will go for a backtrace if you can...
> 
> Thanks!

apt-get installing the latest versions of glade-2 and libgtk2.0-0 made
no difference but I managed to identify the problem as being a result of
an out-of-date version of libgail-common [1.6.6b-1].  glade-2 works
properly with libgail-common (1.8.2-1 Debian:testing).

Matt

P.S.	This marks my first and only use of a debugger.

> $ gdb glade-2
> 
> (gdb) run
> 
> (glade-2:3864): Gtk-CRITICAL **: gtk_container_foreach: assertion
> `GTK_IS_CONTAINER (container)' failed
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 3864)]
> 0x409d4e1e in gail_scrolled_window_new () from
> /usr/lib/gtk-2.0/modules/libgail.so
> 
> $ dpkg-query --search /usr/lib/gtk-2.0/modules/libgail.so
> libgail-common: /usr/lib/gtk-2.0/modules/libgail.so
> 
> # apt-get install libgail-common -s
> Reading Package Lists... Done
> Building Dependency Tree... Done
> The following held packages will be changed:
>   libgail-common
> The following packages will be upgraded:
>   libgail-common
> 1 upgraded, 0 newly installed, 0 to remove and 925 not upgraded.
> Inst libgail-common [1.6.6b-1] (1.8.2-1 Debian:testing)
> Conf libgail-common (1.8.2-1 Debian:testing)