GNOME Bugzilla – Bug 105578
gnome-panel (process 2980)
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-panel Severity: normal Version: 2.0.6 Synopsis: gnome-panel (process 2980) Bugzilla-Product: gnome-panel Bugzilla-Component: clock applet BugBuddy-GnomeVersion: 2.0 (2.0.3) Description: "gnome-panel" (process 2980) has chrashed... Description of Problem: Steps to reproduce the problem: 1. Connect (Internet) 2. Add new button ("modem lights...?", or something) 3. Right click on it Actual Results: Not a pretty thing, but I don't care... :-) Expected Results: I don't know. Maybe to see some modem lights... :-))) How often does this happen? 1-st time. (This is my 3-rd day on Linux.) Additional Information: No big deal I hope! Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...(no debugging symbols found)...[New Thread 8192 (LWP 2980)] 0x420ae169 in wait4 () from /lib/i686/libc.so.6
+ Trace 33623
Thread 1 (Thread 8192 (LWP 2980))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-08 08:03 ------- The original reporter (imravic@inet.hr) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
Thanks for the bug report. You needn't worry about the crashes. You can safely continuing to do other things and when you log back in everything should be set up correctly. It just means that the gnome-panel temporarily failed. Logging back in restarts it as if nothing had ever happened. From what I have been able to determine, this crash only happens around 5% of the time you try to modify the XEMBED-based system tray. I always got it a little while after playing with the RedHat Network icon. We would definitely like to fix this bug, however. This problem seems to have been reported before, but it is somewhat difficult to track down. You may be able to help. Can you see if you can get this crash again repeatably? If so, can you tell us the exact steps you take to get the crash? Also, if you would really like to help track this down, it may be helpful to read bug 94422 where I (and some others) described the work done to try to get this crash. See if you can get it the same way, and also let us know if you got the crash by doing something different. I'm going to mark this as a duplicate of 94422, but add myself to the cc list so that if any extra information is added, I'll know about it. *** This bug has been marked as a duplicate of 94422 ***