Description of problem: Whenever I log in, the gnome-panels are missing. I have to open a terminal from my desktop, find the process, and give a kill command to the PID for gnome-panel. Upon killing it, the gnome-panel then loads itself properly. Version-Release number of selected component (if applicable): gnome-panel-2.30.0-1.fc13.x86_64 How reproducible: Consistent Steps to Reproduce: 1. Log in 2. 3. Actual results: Everything behaves normally except the gnome-panel fails to display. Expected results: Gnome-panel is displayed. Additional info: I began noticing that it the panel failed to load after installing accountsdialog and accountsservice. Also, when the panel comes back, the "Weather Report" applet fails to load. I have no idea if that is relevant to the problem.
I have gnome-panel-2.30.0-4.fc13.i686 . I see a similar problem intermittently (every couple of days, or so, with a dozen starts each day. In my case, the menus at the top and bottom of the screen never appear. The icons in the desktop behave normally, but I can't launch any apps without the menus. I can use CTRL-ALT-DEL, or jab the Power button to get a shutdown menu. If I select Shutdown, I see a panel saying "Panel is not responding". If I select "Shutdown Anyway", the system shuts down, and the next start is usually normal. This morning, however, I had to go through the shutdown/restart twice. Tried Google search for "gnome-panel tracing", and found a more severe case in Ubunto at https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/482690 . Several gdb strategies and workarounds are mentioned there, but I haven't tried any as yet. I do have the weather report app installed. Usually, I have no trouble with it.
Created attachment 435092 [details] .xsession-errors fille
The icons at the top of the screen were displayed after startup, but did not respond to the mouse. The desktop did function; I was able to "Clean Up by Name", for instance. Based on my reading above, I tried CTRL-F2, and found myself in a login screen. I logged in, and tried "ps -flu <username>" | grep gnome, and found a gnome-panel running. I noted its PID, and typed "kill -USR1 <pid>". Using CTRL-F1 to return to the full-screen session, I found it to be operationg normally! (Just a stroke of intuition; I'd like to find documentation with a proper unfreezing procedure.) Searching for "gnome-panel documentation" led me to gnome-panel source code, but not a man page.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.