GNOME Bugzilla – Bug 96976
Panel Crashed
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-panel Severity: normal Version: 2.0.6 Synopsis: Panel Crashed Bugzilla-Product: gnome-panel Bugzilla-Component: Panel BugBuddy-GnomeVersion: 2.0 (2.0.3) Description: Description of Problem: Well I am a bit new to linux and I only know a little bit of C++ so I might sound a litte dumb. I tried to complie new Mesa plugins to get GLUT because the RedHat Cd's didn't have them. Well it seems like my NVIDIA driver didn't support GLU 1.3 yet. So I decided to reinstall my GLU library that came with redhat. Steps to reproduce the problem: 1. I removed the GLU library that came with redhat using rpm -e --nodeps 2. I installed the GLU library that came with redhat using rpm -ivh 3. I loged in using gnome as my GUI Actual Results: Well, i get to tho point after the RedHat loading dialog and the panel applets are starting to appear on it when suddenly I get a panel error. Expected Results: Panel loading and no error message indicating that it crashed or having the panel crash. How often does this happen? Every time when I try to start gnome-panel Additional Information: Atleast my libGLU is compatible now. I tried to do a rpm -ivh --replacepkgs to reinstall the gnome-panel, but it didn't help. The gnome window manager isn't having any problems. Now I don't know what this means but if I launch gnome-panel though the command prompt; it gives me: system-tray-applet-ERROR **: file obox.c: line 107 (get_class): should not be reached aborting... Again, I am fairly new and I don't really understand much in linux yet. Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...(no debugging symbols found)...[New Thread 8192 (LWP 988)] 0x420ae169 in wait4 () from /lib/i686/libc.so.6
+ Trace 29487
Thread 1 (Thread 8192 (LWP 988))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-10-27 10:19 ------- Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
*** This bug has been marked as a duplicate of 94625 ***