GNOME Bugzilla – Bug 527344
crash in Panel: Ich habe auf meinen eige...
Last modified: 2008-04-11 09:38:35 UTC
Version: 2.22.0 What were you doing when the application crashed? Ich habe auf meinen eigenen Standort geklickt, damit dieser auf der Weltkarte 3 mal aufblinkt. Während des Blinkens habe ich auf die Uhr im Panel geklickt, damit das Fenster sich wieder schliesst. Folgt man diesen Schritten, so kommt es reproduzierbar zu einem Absturz das Panels Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Nuvola Memory status: size: 74256384 vsize: 74256384 resident: 24690688 share: 14880768 rss: 24690688 rss_rlim: 4294967295 CPU usage: start_time: 1207834009 rtime: 135 utime: 126 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6de2720 (LWP 15195)] [New Thread 0xb5b80b90 (LWP 15237)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 194840
Thread 1 (Thread 0xb6de2720 (LWP 15195))
----------- .xsession-errors --------------------- (gnome-panel:14937): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80efd58 (gnome-panel:14937): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80efd58 Desktop-Datei /usr/local/share/applications/easytag.desktop konnte nicht für Panel-Starter : geöffnet werdenDatei oder Verzeichnis nicht gefunden (gnome-panel:14937): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' (gnome-panel:15195): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80efd58 (gnome-panel:15195): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80efd58 (gnome-panel:15195): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 Desktop-Datei /usr/local/share/applications/easytag.desktop konnte nicht für Panel-Starter : geöffnet werdenDatei oder Verzeichnis nicht gefunden (gnome-panel:15195): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
after install the package gnome-dbg and some other debug packages the stacktrace is as follows. But there are still a lot of "No symbol table info available." messages in there. Hope it did clear some things up. Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Nuvola Memory status: size: 48218112 vsize: 48218112 resident: 24293376 share: 14823424 rss: 24293376 rss_rlim: 4294967295 CPU usage: start_time: 1207844805 rtime: 88 utime: 82 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' [Thread debugging using libthread_db enabled] [New Thread 0xb6e2b720 (LWP 17089)] [New Thread 0xb59ffb90 (LWP 17199)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 194861
Thread 1 (Thread 0xb6e2b720 (LWP 17089))
----------- .xsession-errors --------------------- (gnome-panel:16942): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80efd58 (gnome-panel:16942): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80efd58 Desktop-Datei /usr/local/share/applications/easytag.desktop konnte nicht für Panel-Starter : geöffnet werdenDatei oder Verzeichnis nicht gefunden (gnome-panel:16942): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' (gnome-panel:17089): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80efd58 (gnome-panel:17089): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80efd58 (gnome-panel:17089): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 Desktop-Datei /usr/local/share/applications/easytag.desktop konnte nicht für Panel-Starter : geöffnet werdenDatei oder Verzeichnis nicht gefunden (gnome-panel:17089): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' --------------------------------------------------
Please install the gnome-panel, glib and gtk+ debug packages to get a useful stack trace. Thanks!
well. i installed around 130mb worth of -dbg packages and still dont get any significant change in my stack trace. seems like i wont be able to supply sufficient information so the only thing left to do is leaving a howto on reproducing the behaviour: step 1: click on the clock applet in the panel to make it pop up. step 2: click on the big analog clock at the bottom. (the corresponding location on the map will blink 3 times) step 3: while the location is still blinking repeat step 1 in order to make the popped up clock applet disappear this results in a crash of the gnome-panel. note: if you execute step 3 after it blinked 3 times then the gnome-panel wont crash. sorry that i cant be of any more help. :(
Ah, that's bug 519493. It's fixed in gnome-panel 2.22.1. *** This bug has been marked as a duplicate of 519493 ***