gnome-panel crashes on startup in jaunty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-panel (Ubuntu) |
Fix Released
|
Medium
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: gnome-panel
when starting jaunty, gnome-panel crashes after login, that is, most areas are grey and only two applets (user switcher and cpu freq applet) stay responsive. this happens on every startup.
when trying to logout, i do get the message that gnome-panel is still running and not responding. when opening a terminal and doing gnome-panel --replace all is fine until this command is quit.
strange thing is: i've tried jaunty first a couple of days ago, when this bug did NOT occur. however, on that first install, i installed "over" previous ubuntu intrepid, without formatting the partition, therefore using my old intrepid home folder. today, i did a clean install of jaunty, that is, formatting the drive. now, this crash all of a sudden occurs.
please let me know how i can help debugging.
cheers,
roots.
lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04
gnome-panel:
Installed: 1:2.26.0-0ubuntu3
Candidate: 1:2.26.0-0ubuntu3
Version table:
*** 1:2.26.0-0ubuntu3 0
500 http://
100 /var/lib/
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.
If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.
If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/ apport/ apport- qt --crash- file=/var/ crash/_ my_crash_ report. crash in a terminal - where _my_crash_ report. crash is the crash you would like to report.
I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.