GNOME Bugzilla – Bug 547780
crash in Panel: login
Last modified: 2008-08-15 23:48:39 UTC
Version: 2.22.2 What were you doing when the application crashed? login Distribution: Fedora release 9 (Sulphur) Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.25.11-97.fc9.i686.debug #1 SMP Mon Jul 21 00:59:37 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10499905 Selinux: No Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 60506112 vsize: 60506112 resident: 15896576 share: 11079680 rss: 15896576 rss_rlim: 4294967295 CPU usage: start_time: 1218725442 rtime: 236 utime: 157 stime: 79 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 0xb80d2760 (LWP 2443)] 0x00110416 in __kernel_vsyscall ()
+ Trace 205150
Thread 1 (Thread 0xb80d2760 (LWP 2443))
----------- .xsession-errors --------------------- Could not find the frame base for "IA__g_spawn_command_line_sync". Could not find the frame base for "gtk_rc_clear_realized_style". Could not find the frame base for "IA__gtk_rc_reset_styles". Could not find the frame base for "gtk_settings_notify". Could not find the frame base for "IA__g_cclosure_marshal_VOID__PARAM". Could not find the frame base for "g_type_class_meta_marshal". Could not find the frame base for "IA__g_signal_emit". Could not find the frame base for "g_object_dispatch_properties_changed". Could not find the frame base for "g_object_notify_dispatcher". Could not find the frame base for "_gtk_settings_handle_event". Could not find the frame base for "IA__gtk_main_do_event". Could not find the frame base for "gdk_event_dispatch". Could not find the frame base for "g_main_context_iterate". Could not find the frame base for "IA__g_spawn_sync". --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 475065 ***