Bug 99725 – Panel crashed at login following battstat applet crash.

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 99725 - Panel crashed at login following battstat applet crash.


Summary:	Panel crashed at login following battstat applet crash.


Status:	RESOLVED DUPLICATE of bug 99205

Product:	gnome-panel
Classification:	Other
Component:	panel
Version:	2.0.x
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2002-11-27 17:17 UTC by Elijah Newren
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.0

Description Elijah Newren 2002-11-27 17:17:30 UTC

I was trying to reproduce a different bug (94422), by repeatedly
removing the redhat icon, logging out, then logging back in.  One of the
times, as soon as the panel appeared, bug-buddy appeared saying the
battstat applet had crashed (but no stacktrace was obtained, so I'm not
submitting that bug report).  As soon as I finished typing in the
information for that bug report, I received notification that the panel
itself had crashed.  This time bug-buddy got me a stack trace.

I'm on a Redhat 8.0 system (which uses gnome-panel-2.0.6-9 and
gnome-applets-2.0.1-6).

I remember triaging a bug a little while ago about the panel crashing
after the battstat applet did, so I'm fairly sure this is a duplicate.

Steps to reproduce the problem:
1.  Who knows--repeatedly logging in and out and hoping something goes
wrong?


Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...[New
Thread 8192 (LWP 2042)]

0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 30983

Thread 1 (Thread 8192 (LWP 2042))

#0 wait4
from /lib/i686/libc.so.6
#1 __DTOR_END__
from /lib/i686/libc.so.6
#2 waitpid
from /lib/i686/libpthread.so.0
#3 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#4 __pthread_sighandler
from /lib/i686/libpthread.so.0
#5 <signal handler called>
#6 ORBit_RootObject_duplicate
from /usr/lib/libORBit-2.so.0
#7 CORBA_Object_duplicate
from /usr/lib/libORBit-2.so.0
#8 bonobo_ui_component_set_container
from /usr/lib/libbonoboui-2.so.0
#9 bonobo_control_frame_get_popup_component
from /usr/lib/libbonoboui-2.so.0
#10 panel_applet_frame_construct
#11 panel_applet_frame_new
#12 panel_applet_frame_load
#13 panel_applet_frame_load_from_gconf
#14 panel_applet_load_idle_handler
#15 g_idle_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 main
#22 __libc_start_main
from /lib/i686/libc.so.6
#0 wait4
from /lib/i686/libc.so.6

Comment 1 Elijah Newren 2002-12-02 18:50:33 UTC

Bug 99205 was the one I was thinking of, but the stack traces do seem
a little different (functions at levels 6-9 here don't match functions
at level 6-7 there, otherwise this stacktraces are the same).

Comment 2 Vincent Untz 2002-12-05 20:28:07 UTC

Looks similar to bug #99205.

Comment 3 Vincent Untz 2002-12-15 19:22:31 UTC

Arvind confirmed this is a dup.

*** This bug has been marked as a duplicate of 99205 ***