eats up all CPU time and still refuses to load after switch from a dual screen setup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Panel |
Expired
|
Medium
|
|||
gnome-panel (Ubuntu) |
Fix Released
|
Medium
|
Ubuntu Desktop Bugs | ||
Karmic |
Fix Released
|
Medium
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: gnome-panel
Gnome panel had issues when I moved to using a dual monitor set up. It would half load, then fail. I would kill it, and then it would load correctly. Eventually, I removed the second monitor and now my system is unusable. On log in, gnome panel quickly monopolizes my quad core machine (CPU: 75%, from top) and grinds the entire GUI to a halt. If I switch VTs though, my console session is completely responsive. Killing gnome panel from the console (I have to because Gnome is too busy locking up) quickly spikes X to 50% CPU usage, although the panel eventually respawns and just doesn't do anything, although the GUI is responsive again.
Stack trace grabbed from GDB:
#0 0x00000033c240de20 in __write_nocancel () from /lib/libpthread
#1 0x00000033c4043df4 in IA__g_log_
#2 0x00000033c4044109 in IA__g_logv (log_domain=<value optimized out>, log_level=<value optimized out>, format=<value optimized out>, args1=<value optimized out>) at /build/
#3 0x00000033c40444c3 in IA__g_log (log_domain=<value optimized out>, log_level=<value optimized out>, format=<value optimized out>) at /build/
#4 0x000000000045c8a1 in panel_multiscre
#5 0x00000000004513b8 in panel_toplevel_
#6 0x0000000000459b7e in panel_toplevel_
#7 0x00000033c480d27d in IA__g_closure_
#8 0x00000033c4822723 in signal_
#9 0x00000033c4824432 in IA__g_signal_
#10 0x00000033c482474c in IA__g_signal_
#11 0x0000003de7ba1588 in _gtk_size_
#12 0x000000000045533d in panel_toplevel_
#13 0x00000033c480d27d in IA__g_closure_
#14 0x00000033c4822b1e in signal_
#15 0x00000033c4824432 in IA__g_signal_
#16 0x00000033c4824953 in IA__g_signal_emit (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>) at /build/
#17 0x0000003de7ab7d30 in gtk_container_
#18 0x0000003de881e04b in gdk_threads_
#19 0x00000033c403a20a in IA__g_main_
#20 0x00000033c403d8e0 in g_main_
#21 0x00000033c403ddad in IA__g_main_loop_run (loop=<value optimized out>) at /build/
#22 0x0000003de7b35bc7 in IA__gtk_main () at /build/
#23 0x00000000004221d0 in main (argc=1, argv=<value optimized out>) at main.c:147
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/
NonfreeKernelMo
Package: gnome-panel 1:2.26.0-0ubuntu7 [modified: usr/bin/gnome-panel usr/bin/
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/zsh
SourcePackage: gnome-panel
Uname: Linux 2.6.28-15-generic x86_64
Related branches
summary: |
- gnome panel eats up all CPU time and still refuses to load. + [PATCH] gnome panel eats up all CPU time and still refuses to load after + switch from a dual screen setup |
Changed in gnome-panel: | |
status: | Unknown → New |
Changed in gnome-panel (Ubuntu): | |
status: | New → Triaged |
Changed in gnome-panel (Ubuntu): | |
importance: | Low → Medium |
Changed in gnome-panel (Ubuntu Karmic): | |
milestone: | none → ubuntu-9.10 |
Changed in gnome-panel (Ubuntu Karmic): | |
status: | Triaged → Fix Committed |
Changed in gnome-panel: | |
status: | New → Invalid |
Changed in gnome-panel: | |
importance: | Unknown → Medium |
status: | Invalid → Expired |
When run from the command line, it prints the following reatedly (nonstop):
** (gnome- panel:12617) : CRITICAL **: panel_multiscre en_x: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome- panel:12617) : CRITICAL **: panel_multiscre en_y: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome- panel:12617) : CRITICAL **: panel_multiscre en_width: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome- panel:12617) : CRITICAL **: panel_multiscre en_height: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed