gnome-panel hangs w/ 100%CPU when running Gimp, Inkscape

[Dave M.]

Binary package hint: gnome-panel

I have an Alienware laptop w/"Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz" proc running Hardy Heron 8.04.2, Linux voodoo 2.6.24-23-generic #1 SMP Thu Feb 5 14:30:38 UTC 2009 x86_64 GNU/Linux. Sometimes gnome-panel pegs a CPU at 100% and is unresponsive until being killed and (automatically) restarted. This occurs most often when I'm using Gimp or Inkscape, although I believe I've seen it at other times. If I leave gimp / inkscape running during a kill/restart cycle, sometimes gnome-panel enters the same state immediately on restart. This may be related to bug#92293.

I can try to acquire an strace of gnome-panel if that will be of use.

dhm@voodoo$ lsb_release -rd
Description: Ubuntu 8.04.2
Release: 8.04
dhm@voodoo$ apt-cache policy gnome-panel
gnome-panel:
  Installed: 1:2.22.2-0ubuntu1.1
  Candidate: 1:2.22.2-0ubuntu1.1
  Version table:
 *** 1:2.22.2-0ubuntu1.1 0
        500 http://us.archive.ubuntu.com hardy-updates/main Packages
        500 http://archive.ubuntu.com hardy-updates/main Packages
        100 /var/lib/dpkg/status
     1:2.22.1.2-0ubuntu3 0
        500 http://us.archive.ubuntu.com hardy/main Packages
dhm@voodoo$ apt-cache policy gimp
gimp:
  Installed: 2.4.6-1ubuntu1~hardy1
  Candidate: 2.4.6-1ubuntu1~hardy1
  Version table:
 *** 2.4.6-1ubuntu1~hardy1 0
        500 http://us.archive.ubuntu.com hardy-backports/main Packages
        100 /var/lib/dpkg/status
     2.4.5-1ubuntu2 0
        500 http://us.archive.ubuntu.com hardy/main Packages
dhm@voodoo$ apt-cache policy inkscape
inkscape:
  Installed: 0.46-0ubuntu2
  Candidate: 0.46-0ubuntu2
  Version table:
 *** 0.46-0ubuntu2 0
        500 http://us.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status
     0.45.1-1ubuntu4~feisty1 0
        500 http://us.archive.ubuntu.com feisty-backports/main Packages
dhm@voodoo$

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace of the hang http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Closing this bug because no further information has been provided.

[Dave M. (ubuntu-mersenne)]

I found that designer-qt4 causes the same problem consistently when starting up, so I was able to get a backtrace of gnome-panel. I'd like to re-open this report.

[Dave M. (ubuntu-mersenne)]

Steps to reproduce: log into Gnome desktop running gnome-panel. Start designer-qt4. Gnome-panel process takes 100% CPU.

[Dave M. (ubuntu-mersenne)]

root@voodoo# apt-cache policy gnome-panel
gnome-panel:
  Installed: 1:2.22.2-0ubuntu1.1
  Candidate: 1:2.22.2-0ubuntu1.1
  Version table:
 *** 1:2.22.2-0ubuntu1.1 0
        500 http://us.archive.ubuntu.com hardy-updates/main Packages
        500 http://archive.ubuntu.com hardy-updates/main Packages
        100 /var/lib/dpkg/status
     1:2.22.1.2-0ubuntu3 0
        500 http://us.archive.ubuntu.com hardy/main Packages
root@voodoo# apt-cache policy qt4-designer
qt4-designer:
  Installed: 4.4.0-1ubuntu5~hardy1
  Candidate: 4.4.0-1ubuntu5~hardy1
  Version table:
 *** 4.4.0-1ubuntu5~hardy1 0
        500 http://us.archive.ubuntu.com hardy-backports/main Packages
        100 /var/lib/dpkg/status
     4.3.4-0ubuntu3 0
        500 http://us.archive.ubuntu.com hardy/main Packages

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!