[Breezy] gnome-panel frequently crashes after today's updates

Bug #20101 reported by Daniel Robitaille
22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Fix Released
Medium
Sebastien Bacher

Bug Description

After today's Breezy update (August 19), gnome-panel is suddently very unstable.
 Every few minutes gnome-panel will crash. If I select "restart the
application", it will complain maybe half-dozen times that another panel is
running. Then it will run fine until the next crash a few minutes later. Here
is the debugging output I get from bug-buddy:

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1223915840 (LWP 8463)]
[New Thread -1226212432 (LWP 8472)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb77ad4ab in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7f05498 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 0xb77c25c3 in gmenu_tree_directory_make_path ()
   from /usr/lib/libgnome-menu.so.2
#5 0xb77476e0 in g_child_watch_add () from /usr/lib/libglib-2.0.so.0
#6 0xb774547e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#7 0xb7748486 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#8 0xb7748773 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#9 0xb7b65fb6 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#10 0x080653b7 in main ()

Thread 2 (Thread -1226212432 (LWP 8472)):
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb76b12d4 in poll () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0xb77482d8 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#3 0xb7748773 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#4 0xb785837e in link_thread_io_context () from /usr/lib/libORBit-2.so.0
No symbol table info available.
#5 0xb77616c4 in g_static_private_free () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#6 0xb77a7361 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#7 0xb76badbe in clone () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.

Thread 1 (Thread -1223915840 (LWP 8463)):
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb77ad4ab in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#2 0xb7f05498 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
No symbol table info available.
#3 <signal handler called>
No symbol table info available.
#4 0xb77c25c3 in gmenu_tree_directory_make_path ()
   from /usr/lib/libgnome-menu.so.2
No symbol table info available.
#5 0xb77476e0 in g_child_watch_add () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#6 0xb774547e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#7 0xb7748486 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#8 0xb7748773 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#9 0xb7b65fb6 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#10 0x080653b7 in main ()
No symbol table info available.
#0 0xffffe410 in __kernel_vsyscall ()

Revision history for this message
Vincent Untz (vuntz) wrote :

It looks like it's a gnome-menus bug... Was libgnome-menus also update?

Revision history for this message
Daniel Robitaille (robitaille) wrote :

(In reply to comment #1)
> It looks like it's a gnome-menus bug... Was libgnome-menus also update?

from what I can see, both gnome-menus and libgnome-menus were last upgraded
(2.11.91-0ubuntu2) on August 11th (9 days ago). I would have noticed if they
would have generated these crashes for that long.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. Could you rebuild a debug version of gnome-menus to get a
backtrace with it? My panel works fine and there is no other such bug.
gnome-panel and gnome-menus have not changed for a week.

Revision history for this message
Guillermo Gutiérrez (capitanterrex) wrote :

Yes, I get the same issue from yesterday. Maybe related to a new applet added in
panel: emifreq-applet; i don't know. Anyway, applications in systray are closed
if there is no window open of that proccess; for example xchat2 (with systray
plugin from breezy repos) and gaim, but if their main windows are maximized, and
the panel crashes, they are not closed but disappeared their icons from systray.

Revision history for this message
Vincent Untz (vuntz) wrote :

Guillermo: the applications using the systray that disappear/crash when the
panel crash is caused by a bug in those applications :-)

Revision history for this message
Guillaume Desmottes (cassidy) wrote :

I have the same bug.

Backtrace with libgnome-menu2 debug builded:

Backtrace was generated from '/usr/bin/gnome-panel'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1224132928 (LWP 2495)]
[New Thread -1226867792 (LWP 3209)]
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb77784ab in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7ed2498 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 emit_events_in_idle () at menu-monitor.c:83
#5 0xb77126e0 in g_idle_dispatch (source=0x82f1ca8,
    callback=0xb778db00 <emit_events_in_idle>, user_data=0x0) at gmain.c:3813
#6 0xb771047e in IA__g_main_context_dispatch (context=0x80ee560)
    at gmain.c:1934
#7 0xb7713486 in g_main_context_iterate (context=0x80ee560, block=1,
    dispatch=1, self=0x80c12e8) at gmain.c:2565
#8 0xb7713773 in IA__g_main_loop_run (loop=0x8205a20) at gmain.c:2769
#9 0xb7b31fb6 in IA__gtk_main () at gtkmain.c:974
#10 0x080653b7 in main (argc=0, argv=0x0) at main.c:90

Thread 2 (Thread -1226867792 (LWP 3209)):
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb767d2d4 in poll () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0xb77132d8 in g_main_context_iterate (context=0x82238e0, block=1,
    dispatch=1, self=0x8129230) at gmain.c:2867
 max_priority = 2147483647
 timeout = -1
 some_ready = #0 0xffffe410 in __kernel_vsyscall ()

Revision history for this message
Björn Röder (overgee) wrote :

(In reply to comment #5)
> Guillermo: the applications using the systray that disappear/crash when the
> panel crash is caused by a bug in those applications :-)

I've been experiencing the same kind of error since I updated "Breezy" this
morning. First I thought Gaim (1:1.4.0-5ubuntu1) would cause Gnome-Panel
(2.11.91-0ubuntu2) to stall since Gaim would get closed automatically when the
error occured.

I have ubuntu installed on two computers and the problem would just appear on
one of them. It's got the kernel 2.6.12-7-686 installed. The other one
Gnome-Panel is running smoothly on has got the 2.6.12.686-smp kernel installed.

Revision history for this message
Vincent Untz (vuntz) wrote :

It looks like it's http://bugzilla.gnome.org/show_bug.cgi?id=313232 (which is
FIXED in HEAD). Not sure, though.

Revision history for this message
Björn Röder (overgee) wrote :

I just found out the problem would only appear if another application was working.

Revision history for this message
Gabriel Wicke (lists-wikidev) wrote :

I only get panel crashes using the latest 2.6.12-7-686 kernel with some system
load, while there are no crashes on 2.6.12-6-686. Tested this with running
updatedb to produce some i/o activity.

Revision history for this message
Daniel Robitaille (robitaille) wrote :
Download full text (5.7 KiB)

(In reply to comment #3)
> Thanks for your bug. Could you rebuild a debug version of gnome-menus to get a
> backtrace with it? My panel works fine and there is no other such bug.
> gnome-panel and gnome-menus have not changed for a week.

After rebuilding gnome-menus with debug on and installing it, here is what I got:

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224034624 (LWP 21157)]
[New Thread -1228039248 (LWP 21351)]
[New Thread -1227711568 (LWP 21350)]
[New Thread -1226478672 (LWP 21178)]
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb77904ab in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7eea498 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 0xb77a72c5 in invoke_notifies (monitor=0x826cfd8,
    event=MENU_MONITOR_EVENT_DELETED,
    path=0x83212f0 "/usr/share/gnome/apps/Multimedia") at menu-monitor.c:83
#5 0xb77a73cb in emit_events_in_idle () at menu-monitor.c:129
#6 0xb772a6e0 in g_child_watch_add () from /usr/lib/libglib-2.0.so.0
#7 0xb772847e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#8 0xb772b486 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#9 0xb772b773 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#10 0xb7b4bfb6 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#11 0x080653b7 in main ()

Thread 4 (Thread -1226478672 (LWP 21178)):
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb76942d4 in poll () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0xb772b2d8 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#3 0xb772b773 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#4 0xb783e37e in link_thread_io_context () from /usr/lib/libORBit-2.so.0
No symbol table info available.
#5 0xb77446c4 in g_static_private_free () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#6 0xb778a361 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#7 0xb769ddbe in clone () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.

Thread 3 (Thread -1227711568 (LWP 21350)):
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb778cc96 in pthread_cond...

Read more...

Revision history for this message
Ross Burton (ross) wrote :

Also seeing with a fresh Breezy.

#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb77be4ab in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7f15498 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 0xb77d35c3 in gmenu_tree_directory_make_path ()
   from /usr/lib/libgnome-menu.so.2
#5 0xb77586e0 in g_idle_dispatch (source=0x833fe28,
    callback=0xb77d354f <gmenu_tree_directory_make_path+13775>, user_data=0x0)
    at gmain.c:3813
#6 0xb775647e in IA__g_main_context_dispatch (context=0x80eea60)
    at gmain.c:1934
#7 0xb7759486 in g_main_context_iterate (context=0x80eea60, block=1,
    dispatch=1, self=0x80c12e8) at gmain.c:2565
#8 0xb7759773 in IA__g_main_loop_run (loop=0x8208b40) at gmain.c:2769
#9 0xb7b76fb6 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#10 0x080653b7 in main ()

Revision history for this message
Thomas Butter (tbutter) wrote :

It is somehow related to notifications from update-notifier. After killing
update-notifier or directly after an update it does not crash again.

Revision history for this message
Vincent Untz (vuntz) wrote :

Note that it should be fixed with the next gnome-menus release (if it's really
http://bugzilla.gnome.org/show_bug.cgi?id=313232)

Revision history for this message
Sebastien Bacher (seb128) wrote :

This upload fixes the issue:

 gnome-menus (2.11.92-0ubuntu1) breezy; urgency=low
 .
   * New upstream version:
     - Fix memory corruption crasher handling notifies (Ubuntu: #13861).
     - Fix python syntax warning.
     - Fix build when FAM isn't found.
     - Fix crasher when a <AppDir> references a subdir of another <AppDir>.
     - Fix duplicate entries after updating.
     - Fix infinite loop.
     - Make <LegacyDir> with prefix work again.

Revision history for this message
Gabriel Wicke (lists-wikidev) wrote :

Latest package seems to have fixed the issue for me, using any kernel version.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.