GNOME Bugzilla – Bug 617808
crash in Notification Area: I was doing nothing whic...
Last modified: 2010-05-06 04:28:14 UTC
Version: 2.28.0 What were you doing when the application crashed? I was doing nothing which should have generated notification icons. Distribution: OpenSolaris Development snv_129 X86 Gnome Release: 2.28.0 2009-11-24 (Sun Microsystems, Inc.) BugBuddy Version: 2.28.0 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: nimbus GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 77156352 vsize: 77156352 resident: 12193792 share: 0 rss: 12193792 rss_rlim: 0 CPU usage: start_time: 1273087936 rtime: 13 utime: 98539 stime: 36960 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/lib/notification-area-applet' 1779: /usr/lib/notification-area-applet --oaf-activate-iid=OAFIID:GNOME_Noti feef53a5 waitid (0, 980, 8046aa0, 3) feea3e75 waitpid (980, 8046b5c, 0, fed9b601) + 65 fed9ba08 g_spawn_sync (0, 80f3b50, 0, 4, 0, 0) + 418 fed9be1c g_spawn_command_line_sync (80c4fa0, 0, 0, 0, 8046c7c) + 5c fda81e4f __1cNrun_bug_buddy6Fpkclp0_b_ (806cf80, 6f3, 0, fda81ff2) + f3 fda820d6 __1cMcheck_if_gdb6F_v_ (fef83000, fef83000, 8046d04, feeefda5, b, 0) + 12e fda81a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046db8, fee12a00, fef83000, 8046d74) + 64 feeefda5 __sighndlr (b, 0, 8046db8, fda81a30) + 15 feee2cff call_user_handler (b) + 2af feee2f2f sigacthandler (b, 0, 8046db8) + df --- called from signal handler with signal 11 (SIGSEGV) --- fecc256d gdk_window_impl_x11_get_colormap (80c3a48, 8087bc8, 8047048, fec7668c) + 5d fec766b0 gdk_drawable_get_colormap (80c3a48, 8087c30, 8047068, fec98d04) + 3c fec98d2f gdk_window_real_get_colormap (80f9348, 8087bc8, 8047088, fec7668c) + 43 fec766b0 gdk_drawable_get_colormap (80f9348, 0, 80470d8, fecbc339) + 3c fecbc3a6 _gdk_pixmap_new (80f9348, 1, 18, ffffffff, 1c) + 1c6 fec85f0d gdk_pixmap_new (80f9348, 1, 18, ffffffff) + 39 fec99757 gdk_window_process_updates_internal (80f9348) + 27f fec99a94 gdk_window_process_updates (80f9348) + 90 fec99ae5 gdk_window_process_updates (80f92a0) + e1 fec99ae5 gdk_window_process_updates (808f3f0) + e1 fec99ae5 gdk_window_process_updates (808f348) + e1 feaac23f gtk_window_check_resize (80df000, 0, 0, fe9b0914) + 6ff fe9b0939 gtk_plug_check_resize (80df000, 8095c98, 0, fec26e9e) + 31 fec26eef g_cclosure_marshal_VOID__VOID (80bf148, 0, 1, 80f0578, 80474d8, fe9b0908) + 5f fec0f92a g_type_class_meta_marshal (80bf148, 0, 1, 80f0578, 80474d8, 174) + 46 fec0f63a g_closure_invoke (80bf148, 0, 1, 80f0578, 80474d8, 80f2058) + d6 fec26551 signal_emit_unlocked_R (80be868, 0, 80df000, 0, 80f0578, 80df000) + 16b9 fec24a88 g_signal_emit_valist (80df000, 52, 0, 80476cc) + 9c8 fec24c89 g_signal_emit (80df000, 52, 0, fe8fe048) + 25 fe8fe06e gtk_container_check_resize (80df000, fee0c458, 8047708, fe8fde0a) + 3e fe8fde49 gtk_container_idle_sizer (0, fee0c458, 8047738, fec72d18) + 4d fec72d35 gdk_threads_dispatch (80f1570, fee0c458, 8047768, fed67514) + 49 fed6752a g_idle_dispatch (80f8f58, fec72cec, 80f1570, 80477c0) + 22 fed64eee g_main_context_dispatch (80917f8, 6e, 80f3560, b) + 262 fed6559f g_main_context_iterate (80917f8, 1, 1, 8078720) + 483 fed65bc9 g_main_loop_run (80d6ef0, 80d6ef0, 80478b8, fd9b469e) + 1dd fd9b46ef bonobo_main (80478e0, fefc47a4, fda30cd0, b, fd9b2ad6, 80595c0) + 6b fd9b2b8d bonobo_generic_factory_main_timeout (80d24c8, fd8f8c28, 80d20b0, 7d0, 8047948) + b1 fd9b2ad6 bonobo_generic_factory_main (80d24c8) + 26 fd8f8dc0 panel_applet_factory_main_closure (8059594, 80d2040, 80caff0, fd8f8e4e) + f4 fd8f8e7e panel_applet_factory_main (8059594) + 3a 0805692f main (1, 80479d0, 80479e0, 804798c) + f7 08055a7d _start (3, 8047ae8, 0, 0, 0, 8047b59) + 7d ----------- .xsession-errors (211 sec old) --------------------- ERROR: Unable to remove old X config backup file '/etc/X11/xorg.conf.backup'. ERROR: Unable to remove old X config backup file '/etc/X11/xorg.conf.backup'. Client shut down the connection owned by im_id(1). ** (gnome-settings-daemon:1699): WARNING **: Call to screen_info_new is too frequent, skipping... Client shut down the connection owned by im_id(1). Client shut down the connection owned by im_id(1). Client shut down the connection owned by im_id(1). Client shut down the connection owned by im_id(1). --------------------------------------------------
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 bug 600280 ***