GNOME Bugzilla – Bug 94987
gnome-panel has crashed
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-panel Severity: normal Version: 2.0.6 Synopsis: gnome-panel has crashed Bugzilla-Product: gnome-panel Bugzilla-Component: Panel BugBuddy-GnomeVersion: 2.0 (2.0.3) Description: Description of Problem: as soon as I log in, either locally or remotely with winaxe, I get the message that gnome-panel has crashed, so I choose the close button, the task-bar disappears then reappears, and the same error pops up again. I don't really know what's going on as I'm a nix noobie. Are there any logs I can send you which may helkp you see what's going on? I can be reached at anthony@area.net.au Steps to reproduce the problem: 1. Boot my machine 2. Log in 3. watch it crash Actual Results: Expected Results: How often does this happen? Every tiome I boot Additional Information: The machine worked fine for about the first six or so boots after installing (This is the second install today - same problem with the last install). Then this starts happening. I don't think I've changed any settings, apart from allowing telnet and the like, nothing gnome or graphics related. I am installed RedHat8. As I said above, if there are any logs I can send you, please let me know. I'll leave the box alone for a couple of days, just in case, then I'll reinstall again. Please feel free to contact me at anthony@area.net.au Thanks, and sorry I can't provide any further info. Anthony. Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...(no debugging symbols found)...[New Thread 8192 (LWP 906)] 0x40973789 in wait4 () from /lib/libc.so.6
+ Trace 28332
Thread 1 (Thread 8192 (LWP 906))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-10-06 06:51 ------- The original reporter (anthony@area.net.au) 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.
*** This bug has been marked as a duplicate of 94625 ***