GNOME Bugzilla – Bug 610430
crash in Notification Area: nothing
Last modified: 2010-02-19 08:53:39 UTC
Version: 2.28.0 What were you doing when the application crashed? nothing Distribution: Solaris Express Community Edition snv_127 X86 Gnome Release: 2.28.0 2009-10-26 (Sun Microsystems, Inc.) BugBuddy Version: 2.28.0 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: blueprint Icon Theme: blueprint GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 77344768 vsize: 77344768 resident: 10801152 share: 24576 rss: 10801152 rss_rlim: 0 CPU usage: start_time: 1266565542 rtime: 16 utime: 103903 stime: 57133 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/lib/notification-area-applet' 2865: /usr/lib/notification-area-applet --oaf-activate-iid=OAFIID:GNOME_Noti feef3d65 waitid (0, c15, 80462f0, 3) feea3335 waitpid (c15, 80463ac, 0, fed9b60d) + 65 fed9ba14 g_spawn_sync (0, 8086328, 0, 4, 0, 0) + 418 fed9be28 g_spawn_command_line_sync (80e4348, 0, 0, 0, 80464cc) + 5c fda61e4f __1cNrun_bug_buddy6Fpkclp0_b_ (806cb00, b31, 0, fda61ff2) + f3 fda620d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8046554, feeee765, b, 0) + 12e fda61a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046608, fee12a00, fef81000, 80465c4) + 64 feeee765 __sighndlr (b, 0, 8046608, fda61a30) + 15 feee161f call_user_handler (b) + 2af feee184f sigacthandler (b, 0, 8046608) + df --- called from signal handler with signal 11 (SIGSEGV) --- fecc256d gdk_window_impl_x11_get_colormap (80ce530, 8083c90, 8046898, fec7668c) + 5d fec766b0 gdk_drawable_get_colormap (80ce530, 8083dc0, 80468b8, fec98d04) + 3c fec98d2f gdk_window_real_get_colormap (80e08a8, 8083c90, 80468d8, fec7668c) + 43 fec766b0 gdk_drawable_get_colormap (80e08a8, 0, 8046928, fecbc339) + 3c fecbc3a6 _gdk_pixmap_new (80e08a8, 1, 20, ffffffff, 1c) + 1c6 fec85f0d gdk_pixmap_new (80e08a8, 1, 20, ffffffff) + 39 fec99757 gdk_window_process_updates_internal (80e08a8) + 27f fec99a94 gdk_window_process_updates (80e08a8) + 90 fec99ae5 gdk_window_process_updates (80e0950) + e1 fec99ae5 gdk_window_process_updates (80883f0) + e1 fec99ae5 gdk_window_process_updates (8088348) + e1 feaac23f gtk_window_check_resize (80c9800, 0, 0, fe9b0914) + 6ff fe9b0939 gtk_plug_check_resize (80c9800, 8091288, 0, fec26e9e) + 31 fec26eef g_cclosure_marshal_VOID__VOID (80a8d48, 0, 1, 80db630, 8046d28, fe9b0908) + 5f fec0f92a g_type_class_meta_marshal (80a8d48, 0, 1, 80db630, 8046d28, 174) + 46 fec0f63a g_closure_invoke (80a8d48, 0, 1, 80db630, 8046d28, 80daf80) + d6 fec26551 signal_emit_unlocked_R (80a95d0, 0, 80c9800, 0, 80db630, 80c9800) + 16b9 fec24a88 g_signal_emit_valist (80c9800, 52, 0, 8046f1c) + 9c8 fec24c89 g_signal_emit (80c9800, 52, 0, fe8fe048) + 25 fe8fe06e gtk_container_check_resize (80c9800, fee0c460, 8046f58, fe8fde0a) + 3e fe8fde49 gtk_container_idle_sizer (0, fee0c460, 8046f88, fec72d18) + 4d fec72d35 gdk_threads_dispatch (80dc4c0, fee0c460, 8046fb8, fed67514) + 49 fed6752a g_idle_dispatch (80d4b40, fec72cec, 80dc4c0, 8047010) + 22 fed64eee g_main_context_dispatch (808aa40, 6e, 80c1488, b) + 262 fed6559f g_main_context_iterate (808aa40, 1, 1, 8076f08) + 483 fed65bc9 g_main_loop_run (80c1df0, 80c1df0, 8047108, fd9a469e) + 1dd fd9a46ef bonobo_main (8047130, fefc47a4, fd970018, b, fd9a2ad6, 80595c0) + 6b fd9a2b8d bonobo_generic_factory_main_timeout (80bc7e8, fd8d8c28, 80bc0d8, 7d0, 8047198) + b1 fd9a2ad6 bonobo_generic_factory_main (80bc7e8) + 26 fd8d8dc0 panel_applet_factory_main_closure (8059594, 80bc768, 80bb250, fd8d8e4e) + f4 fd8d8e7e panel_applet_factory_main (8059594) + 3a 0805692f main (1, 8047220, 8047230, 80471dc) + f7 08055a7d _start (3, 8047350, 0, 0, 0, 80473c1) + 7d
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 ***