[Bug 18719] Completly unresponsive panel and 100% CPU-utilization after ...

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Mon Jan 9 00:42:15 UTC 2006


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=18719
Ubuntu | gnome-panel





------- Additional Comments From mnemnonic at t-online.de  2006-01-09 00:42 UTC -------

Ok, I realize that my description is not sufficent enough to reproduce the bug.

I spent some time to discover what makes the difference ...

It is step 1 in my original description, where I have to give more details:

1.0 Create a new menu in Applications. (Here it is located under -but not
within- "System Tools")
1.1 Move the new menu down, to be at the bottom (The starter "Add Applications"
should then be above the newly created menu.) 
1.2 Create a new starter withing the new menu. (Not sure if this does matter ...
I created a new one and did not drag an existing one into it!)
1.3 Close smeg.

This way I can always reproduce it and then the stacktrace is stable and looks
like this:

#0  0xb7e411f9 in gmenu_tree_item_get_type () from /usr/lib/libgnome-menu.so.2
#1  0xb7e45a3a in gmenu_tree_get_directory_from_path () from
/usr/lib/libgnome-menu.so.2
#2  0x0808972c in panel_menu_button_popup_menu ()
#3  0x0808977c in panel_menu_button_popup_menu ()
#4  0x08089a1a in panel_menu_button_set_custom_icon ()
#5  0xb7785447 in g_cclosure_marshal_VOID__OBJECT () from
/usr/lib/libgobject-2.0.so.0
#6  0xb7778d75 in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0
#7  0xb77793a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#8  0xb7787769 in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0
#9  0xb7789150 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#10 0xb77894c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#11 0xb7b74db1 in gtk_widget_set_parent () from /usr/lib/libgtk-x11-2.0.so.0
#12 0xb7a4a07b in gtk_fixed_put () from /usr/lib/libgtk-x11-2.0.so.0
#13 0x08068e62 in panel_widget_add ()
#14 0x080732e2 in panel_applet_register ()
#15 0x0808a0ca in panel_menu_button_load_from_gconf ()
#16 0x08071f5d in panel_applet_on_load_queue ()
#17 0xb7715750 in g_child_watch_add () from /usr/lib/libglib-2.0.so.0
#18 0xb77134ee in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb77164f6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#20 0xb77167e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#21 0xb7a8ae65 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#22 0x080655f7 in main ()


To fix the damaged account, one has to:

1. 'kill -TERM <pidof users gconfd> 
2. remove the directory ~/.gconf/apps/panel/objects/object_<X> where <X> is some
number (if there are ore than one of these, most probably the highest number is
the damaged one)
3. killall gnome-panel


Hopefully this helps you. If there is anything more I could do tell me.


-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the desktop-bugs mailing list