| 2006-06-21 19:15:13 |
antoine |
description |
Binary package hint: gnome-panel
I'm running on 6.06 and gnome 2.14.2 since last updates. And , hum ! ... I'm french, that's why my writing is so bad.
I had a few launchers on my top deskbar. I added most of them by right-clicking on them into the system menu or applications menu.
When I changed their properties (erasing generic name and description for example) I observed on my monitor-system gnome applet that cpu usage reached 100%.
This is confirmed using the top command. (gnome-panel ; nice=0 ; %CPU=80 ; %MEM=4). I can now reproduce this behaviour just by opening properties of 2-3 of my launchers, and closing them without changing anything.
The cpu usage stays at its maximum for an endless time, and I have to killall gnome-panel to reach a normal state. |
Binary package hint: gnome-panel
I'm running on 6.06 and gnome 2.14.2 since last updates. And , hum ! ... I'm french, that's why my writing is so bad.
I have a few launchers on my top deskbar. I added most of them by right-clicking on them into the system menu or applications menu.
When I changed their properties (erasing generic name and description for example) I observed on my monitor-system gnome applet that cpu usage reached 100%.
This is confirmed using the top command. (gnome-panel ; nice=0 ; %CPU=80 ; %MEM=4). I can now reproduce this behaviour just by opening properties of 2-3 of my launchers, and closing them without changing anything.
The cpu usage stays at its maximum for an endless time, and I have to killall gnome-panel to reach a normal state. |
|
| 2006-11-29 22:18:20 |
Sebastien Bacher |
gnome-panel: statusexplanation |
Thanks for your bug. Does it happen with any launcher? Could you get a backtrace of the hang with gnome-panel-dbg installed? Run "gdb -p $(pidof gnome-panel)" after getting the hang and use "thread apply all bt" to get the backtrace. |
no problem, marking as fixed then, thank you for the comment |
|
