GNOME Bugzilla – Bug 603863
crash in Notification Area: Just after start of Gnom...
Last modified: 2009-12-06 00:36:44 UTC
Version: 2.28.0 What were you doing when the application crashed? Just after start of Gnome desktop Distribution: OpenSolaris Development snv_128a X86 Gnome Release: 2.28.0 2009-11-09 (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: 77856768 vsize: 77856768 resident: 11497472 share: 24576 rss: 11497472 rss_rlim: 0 CPU usage: start_time: 1260042682 rtime: 5 utime: 32575 stime: 18236 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/lib/notification-area-applet' 2456: /usr/lib/notification-area-applet --oaf-activate-iid=OAFIID:GNOME_Noti feef3ee5 waitid (0, 9aa, 8047060, 3) feea3545 waitpid (9aa, 804711c, 0, fed9b601) + 65 fed9ba08 g_spawn_sync (0, 80f4ee8, 0, 4, 0, 0) + 418 fed9be1c g_spawn_command_line_sync (80c1ad8, 0, 0, 0, 804723c) + 5c fd9e1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (806cb00, 998, 0, fd9e1ff2) + f3 fd9e20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 80472c4, feeee8e5, b, 0) + 12e fd9e1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8047378, fee12a00, fef81000, 8047334) + 64 feeee8e5 __sighndlr (b, 0, 8047378, fd9e1a30) + 15 feee183f call_user_handler (b) + 2af feee1a6f sigacthandler (b, 0, 8047378) + df --- called from signal handler with signal 11 (SIGSEGV) --- fecc256d gdk_window_impl_x11_get_colormap (80e30e8, 808c670, 8047608, fec7668c) + 5d fec766b0 gdk_drawable_get_colormap (80e30e8, 808c6d8, 8047628, fec98d04) + 3c fec98d2f gdk_window_real_get_colormap (808fde8, 808c670, 8047648, fec7668c) + 43 fec766b0 gdk_drawable_get_colormap (808fde8, 0, 8047698, fecbc339) + 3c fecbc3a6 _gdk_pixmap_new (808fde8, 1, 3, ffffffff, 1c) + 1c6 fec85f0d gdk_pixmap_new (808fde8, 1, 3, ffffffff) + 39 fec99757 gdk_window_process_updates_internal (808fde8, fec15d74, 0, fec998fd) + 27f fec9993f gdk_window_process_all_updates (fee0d220, fee0c458, 8047798, 0, 0, fecfc8e4) + af fe8fde56 gtk_container_idle_sizer (0, fee0c458, 8047798, fec72d18) + 5a fec72d35 gdk_threads_dispatch (80f4240, fee0c458, 80477c8, fed67514) + 49 fed6752a g_idle_dispatch (80f87c0, fec72cec, 80f4240, 8047820) + 22 fed64eee g_main_context_dispatch (80910a8, 6e, 807e8c8, b) + 262 fed6559f g_main_context_iterate (80910a8, 1, 1, 8078760) + 483 fed65bc9 g_main_loop_run (80d63a0, 80d63a0, 8047918, fd91469e) + 1dd fd9146ef bonobo_main (8047940, fefc47a4, fd990cd0, b, fd912ad6, 80595c0) + 6b fd912b8d bonobo_generic_factory_main_timeout (80d2100, fd848c28, 80d1ca8, 7d0, 80479a8) + b1 fd912ad6 bonobo_generic_factory_main (80d2100) + 26 fd848dc0 panel_applet_factory_main_closure (8059594, 80d2080, 80ce478, fd848e4e) + f4 fd848e7e panel_applet_factory_main (8059594) + 3a 0805692f main (1, 8047a30, 8047a40, 80479ec) + f7 08055a7d _start (3, 8047b3c, 0, 0, 0, 8047bad) + 7d ----------- .xsession-errors --------------------- Warning: could not open module file: /usr/lib/iiim/le/cle/input_methods/newsp_gbk.so Warning: could not open module file: /usr/lib/iiim/le/cle/input_methods/codetable_im.so Warning: could not open module file: /usr/lib/iiim/le/cle/input_methods/codetable_im.so Warning: could not open module file: /usr/lib/iiim/le/cle/input_methods/codetable_im.so Warning: could not open module file: /usr/lib/iiim/le/cle/input_methods/NeiMa.so started. Allow the connection from unknown source. 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). Screen is composited. APPLET : /usr/share/avant-window-navigator/applets/taskman.desktop 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 ***