gnome-panel crashed with SIGSEGV in idle_populate_func()

[James Deibele]

Binary package hint: gnome-panel

I'm not sure what this program is. Nothing visible changed. Sorry I can't be of more help.

ProblemType: Crash
Architecture: i386
Date: Sun Jul 1 22:36:02 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gnome-panel
NonfreeKernelModules: nvidia
Package: gnome-panel 1:2.19.4-0ubuntu1
PackageArchitecture: i386
ProcCmdline: gnome-panel --sm-client-id default1
ProcCwd: /home/jamesd
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
Title: gnome-panel crashed with SIGSEGV
Uname: Linux jamesd-desktop 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:gdk_threads_dispatch (data=0x869b590) at /build/buildd/gtk+2.0-2.11.4/gdk/gdk.c:470
g_idle_dispatch (source=0x865d048, callback=0xbfb2d84c, user_data=0x869b590) at /build/buildd/glib2.0-2.13.5/glib/gmain.c:4131
IA__g_main_context_dispatch (context=0x80f09d8) at /build/buildd/glib2.0-2.13.5/glib/gmain.c:2061
g_main_context_iterate (context=0x80f09d8, block=1, dispatch=1, self=0x80c5588) at /build/buildd/glib2.0-2.13.5/glib/gmain.c:2694
IA__g_main_loop_run (loop=0x84d8bd0) at /build/buildd/glib2.0-2.13.5/glib/gmain.c:2898

[Sebastien Bacher (seb128)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=453033

[Sebastien Bacher (seb128)]

the bug should be fixed in gutsy

[Matti Lindell (mlind)]

According to apport, I somehow managed to get similar stack trace using up-to-date (alpha2) Hardy in Bug #179080. Should this be reopened?

[William Pitcock (nenolod)]

No, the current round of crashes is due to a recursion bug. See bug 180463 for details.