Bug 96570 – Removing Notification area from panel causes 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 96570 - Removing Notification area from panel causes crash


Summary:	Removing Notification area from panel causes crash


Status:	RESOLVED DUPLICATE of bug 94625

Product:	gnome-panel
Classification:	Other
Component:	notification area
Version:	unspecified
Hardware:	Other Linux

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2002-10-23 04:36 UTC by Dave Barron
Modified:	2004-12-22 21:47 UTC

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

Description Dave Barron 2002-10-23 04:36:46 UTC

Description of Problem:


Steps to reproduce the problem:
1. Add Notification Area to panel
2. Remove Notification Area from panel
3. 

Actual Results:
gnome-panel crashes

Expected Results:
Notification Area is removed from panel

How often does this happen? 
Approx 50% of attempts to remove Notification Area

Additional Information:
- Redhat 8.0 with stock 2.4.19 kernel
-

Comment 1 Vincent Untz 2002-10-23 22:15:27 UTC

Unfortunately, without a stack trace, this bug is not really useful.
Could you please try to get a stack trace (bug-buddy should be
launched when the bug happens).
Thanks

Comment 2 Dave Barron 2002-10-24 01:20:59 UTC

OK here is a stack trace:

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

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

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

+ Trace 29308

Thread 1 (Thread 8192 (LWP 1052))

#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 g_type_check_instance
from /usr/lib/libgobject-2.0.so.0
#7 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#9 egg_tray_manager_window_filter
from /usr/lib/system-tray-applet/libsystem-tray-applet.so
#10 gdk_event_apply_filters
from /usr/lib/libgdk-x11-2.0.so.0
#11 gdk_event_translate
from /usr/lib/libgdk-x11-2.0.so.0
#12 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#13 gdk_event_dispatch
from /usr/lib/libgdk-x11-2.0.so.0
#14 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#15 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#17 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#18 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#19 main
#20 __libc_start_main
from /lib/i686/libc.so.6
#0 wait4
from /lib/i686/libc.so.6

Comment 3 Arvind S N 2002-10-24 05:19:50 UTC


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

Comment 4 Vincent Untz 2002-10-24 15:07:58 UTC

In fact, this is a duplicate of bug #94514...

Comment 5 Dave Jenkins 2003-05-20 11:48:31 UTC

I installed gnome-panel-2.0.6-9.1.i386.rpm from
ftp://people.redhat.com/hp/testing/ but this bug still occurs, exactly
as described by the reporter. This is on RedHat 8.0 .
----------------------------------------------------------
$ ls -l /usr/bin/gnome-panel
-rwxr-xr-x    1 root     root       484812 Nov 23 21:27
/usr/bin/gnome-panel
$ rpm -qf /usr/bin/gnome-panel
gnome-panel-2.0.6-9.1
----------------------------------------------------------

Comment 6 Elijah Newren 2003-07-26 16:01:06 UTC

Dave Jenkins: We tend to not notice comments added to bugs that are
already closed unless they're reopened--thus the reason that no one
caught your comment before (I only did because I'm trying to check to
see if a certain bug is a duplicate of anything).  If you received the
same crash as Dave Barron, then as Vincent said, this would be a
duplicate of bug 94514.  Bug 94514 was marked as fixed as of 2.2.0. 
So you'll need to upgrade to a newer version to get this fixed.