GNOME Bugzilla – Bug 552666
crash in Panel: login
Last modified: 2008-09-17 16:48:43 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.26.3-29.fc9.i686.debug #1 SMP Wed Sep 3 03:05:11 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: 60878848 vsize: 60878848 resident: 15650816 share: 11055104 rss: 15650816 rss_rlim: 4294967295 CPU usage: start_time: 1221669219 rtime: 232 utime: 147 stime: 85 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 0xb7fcd760 (LWP 2495)] 0x00110416 in __kernel_vsyscall ()
+ Trace 206897
Thread 1 (Thread 0xb7fcd760 (LWP 2495))
----------- .xsession-errors --------------------- DCOP aborting call from 'kalarmd' to 'kalarm' 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 the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 446183 ***