GNOME Bugzilla – Bug 78372
panel did not appear in login
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-panel Severity: major Version: 1.5.15 Synopsis: panel did not appear in login Bugzilla-Product: gnome-panel Bugzilla-Component: Panel BugBuddy-GnomeVersion: 2.0 (1.114.0) Description: Description of Problem: I had modified the panel yesterday to include a mail, cpu and memory monitor on the main panel. When I logged in this morning, there was a message saying that I did not have any panel in my configurations, do I want to create one (with OK being the only choice). When I hit Ok the main top panel was recreated (without any of my applets) and there was no bottom panel. Additional Information: I will play with this some more, see if I can recreate the crash... Debugging Information: [New Thread 1024 (LWP 5009)] 0x40929ca9 in __wait4 () from /lib/i686/libc.so.6
+ Trace 20692
Thread 1 (Thread 1024 (LWP 5009))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-04-11 09:21 ------- The original reporter (bailey@jupiter.utias.utoronto.ca) 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.
I had also added the gweather applet to the menu panel, which after relogging in would crash (bug #78373). As I am not sure if the problem lies with the panel or the applet, I have two bugs opened on this. Also, the icons in the drop-down menus do not appear anymore. (This happened after the recreation of the menu panel.) If I try to put a new gweather applet on the panel, the panel goes into an endless loop of crashing.
Is stack trace this at all useful, Mark?
I think if you got bug #78373 that indicates your gconf setup is somewhat hosed. You might try gconftool-2 --shutdown; rm -rf ~/.gconf/apps/panel to clear the panel setup.
Yeah, I think the problem is probably caused by a stale gconf setup. I haven't seen that problem in a long time, pretty sure it was fixed by the gconf re-work I did ...
*** Bug 81055 has been marked as a duplicate of this bug. ***
*** Bug 80768 has been marked as a duplicate of this bug. ***
*** Bug 81639 has been marked as a duplicate of this bug. ***
That would not explain why I get it reliably with a fresh, pristine, adduser'd account - cf. bug 81639
*** Bug 81722 has been marked as a duplicate of this bug. ***
No, no it doesn't. Marking 2.0.0.
*** Bug 81987 has been marked as a duplicate of this bug. ***
This should be fixed in CVS The bug had nothing to do with gconf. The original gconf stuff I was talking about had to do with the "message saying that I did not have any panel in my configurations" syptom, not the crash itself - which as what all the other reports were about.
*** Bug 82285 has been marked as a duplicate of this bug. ***
Ah. Sorry I misunderstood.
*** Bug 83024 has been marked as a duplicate of this bug. ***