Panel encounters a problem while loading applet

Bug #795398 reported by aka
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gnome-panel

Sometimes - every 3rd boot or so (sometimes with normal shutdown, sometimes reset) some applet is reported as failed to load.
Have to killall gnome-panel and all applets are loaded normally.
Saw it happen to clock, language and glipper applets.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gnome-panel 1:2.32.1-0ubuntu6.5
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Fri Jun 10 09:45:32 2011
GConfNonDefault:
 /apps/panel/general/applet_id_list=[applet_0,clock_screen0,notification_area_screen0,indicator_applet_screen0]
 /apps/panel/general/object_id_list=[object_1]
 /apps/panel/general/toplevel_id_list=[top_panel_screen0]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-panel
UpgradeStatus: Upgraded to natty on 2011-04-29 (41 days ago)

Revision history for this message
aka (vangop) wrote :
Revision history for this message
aka (vangop) wrote :
Changed in gnome-panel (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

aka, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install gnome-panel-dbg && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

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.

Please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in gnome-panel (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.