Gnome Panel Freeze

Bug #594463 reported by Shibu
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: gnome-panel

I am using Ubuntu 10.04. When I start my machine, the Gnome Panel is getting hung. The Clock, Pidgin indicator, Gmail Notify etc freeze. Then I used to 'killall gnome-panel'. Then it works fine. This bug happens very frequently, but not every time I start my machine.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-panel 1:2.30.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Jun 15 11:35:27 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: gnome-panel

Revision history for this message
Shibu (shibu) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace of the freeze following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-panel (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
vatbier (vatbier) wrote :

Pedro,

how do you run a backtrace on gnome-panel?
If I kill gnome-panel then it is automatically reloaded. I have no idea how to make a backtrace for it.

Revision history for this message
vatbier (vatbier) wrote :

Ok,

I have found the wiki part "ask GDB to attach to a program that's already running."
But gnome-panel is already frozen right after logging in. If I kill gnome-panel it respawns automatically and runs fine from then on.
But the first run when I log in Gnome is the one that freezes. How do backtrace that before it freezes?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Since it's a freeze you need to attach gdb to the gnome-panel process, run the gnome-panel, check what's the PID of it (with ps) and run gdb as: gdb gnome-panel PID then get a backtrace as described on the document i've previously linked, there's also documentation on how to get a backtrace for already running processes here: https://wiki.ubuntu.com/Backtrace#Already%20running%20programs ; thanks vatbier.

Revision history for this message
Shibu (shibu) wrote :

Now the gnome-panel is not freezing. Its working fine. I don't know any update fixed it. The backtrace is attached here.

Revision history for this message
vatbier (vatbier) wrote :

Pedro, thank you for your response.
But I don't understand it. The gnome-panel is frozen from the moment I log into Gnome. Is a backtrace possible on a program that is already frozen? I thought a backtrace only shows debugging code that happens after you run gdb.

Revision history for this message
Ednilton Santos de Oliveira (esdeoliveira) wrote :

Hi,

I also have this issue. It is really annoying because the clock also freezes, and a lost the time! :-/

I have noticed, until now, that this happens only when the panel is in the "not expanded" mode.
However, I will work the next days in the expanded mode to make sure this is true.
I also can reproduce this bug by initiating empathy from the panel (by the small envelop icon).
It is also easy the see what is happening with g-eyes in the panel.

Note, this is a important bug, since I have noticed it is present is the 10.10 (beta) version of Ubuntu.

Best regards.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-panel (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-panel (Ubuntu):
status: Incomplete → Expired
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.