Sebastien Bacher wrote:
could you try if that's still an issue on hardy?
I am not able to upgrade to hardy yet, due to work reasons. However, could this
be the same bug?
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/187540
Vijay
--
gnome-panel hangs
In my case, both panels (one top, one left) hang, and are completely
unresponsive. I guess you could attach your stacktraces.
--
gnome-panel hangs
https://bugs.launchpad.net/bugs/174088
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Sorry about that, had to install more dbgsym packages of libs gnome-
panel was linking against. Is the following stack trace more useful?
0xe410 in __kernel_vsyscall ()
(gdb) bt
#0 0xe410 in __kernel_vsyscall ()
#1 0xb748d5ab in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7589839
. I have attached the stack traces, there doesn't
seem to be any more info though.
Sample output of top:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
13529 vijayr16 0 73384 46m 10m R 64 2.3 0:32.17 gnome-panel
5312 root 15 0 424m 76m
A couple of other stack traces, this time when a new window was opened,
and tried to shrink the size of the window_list:
(gdb) bt
#0 0xe410 in __kernel_vsyscall ()
#1 0xb74a45ab in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb75a0839 in ?? () from /usr/lib/libX11.so.6
#3 0x080e17d8 in
I'm unable to install the gnome-panel-dbgsym package:
shakti:~$ sudo apt-get install gnome-panel-dbgsym
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible
Hello. This is happening on a development box, I'm loathe to install dbg
packages on it...I've subsequently discovered further information,
hopefully, you may be able to track the bug down now?
I'm using sawfish with viewports:
% cat ~/.sawfishrc
(define-special-variable viewport-dimensions '(3 .
Public bug reported:
After upgrading to 7.10 gutsy, gnome-panel hangs very frequently,
chewing up cpu. It seems to happen when a new window is created, causing
some bad comm loop to happen - possibly with window list applet? That
too started behaving strangely, resizing frequently without any new
