GNOME Bugzilla – Bug 601941
crash in Notification Area: Started Rhythmbox.
Last modified: 2009-11-15 15:34:29 UTC
Version: 2.28.0 What were you doing when the application crashed? Started Rhythmbox. 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: nimbus Icon Theme: nimbus GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 77123584 vsize: 77123584 resident: 10805248 share: 0 rss: 10805248 rss_rlim: 0 CPU usage: start_time: 1258082017 rtime: 127 utime: 928798 stime: 343214 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/lib/notification-area-applet' 8095: /usr/lib/notification-area-applet --oaf-activate-iid=OAFIID:GNOME_Noti feef3d65 waitid (0, 2443, 8046000, 3) feea3335 waitpid (2443, 80460bc, 0, fed9b60d) + 65 fed9ba14 g_spawn_sync (0, 8090978, 0, 4, 0, 0) + 418 fed9be28 g_spawn_command_line_sync (80f8848, 0, 0, 0, 80461dc) + 5c fda81e4f __1cNrun_bug_buddy6Fpkclp0_b_ (806cf80, 1f9f, 0, fda81ff2) + f3 fda820d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8046264, feeee765, b, 0) + 12e fda81a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046318, fee12a00, fef81000, 80462d4) + 64 feeee765 __sighndlr (b, 0, 8046318, fda81a30) + 15 feee161f call_user_handler (b) + 2af feee184f sigacthandler (b, 0, 8046318) + df --- called from signal handler with signal 11 (SIGSEGV) --- fecc256d gdk_window_impl_x11_get_colormap (80c4610, 8089868, 80465a8, fec7668c) + 5d fec766b0 gdk_drawable_get_colormap (80c4610, 80898d0, 80465c8, fec98d04) + 3c fec98d2f gdk_window_real_get_colormap (80f9800, 8089868, 80465e8, fec7668c) + 43 fec766b0 gdk_drawable_get_colormap (80f9800, 0, 8046638, fecbc339) + 3c fecbc3a6 _gdk_pixmap_new (80f9800, 1, 1d, ffffffff, 1c) + 1c6 fec85f0d gdk_pixmap_new (80f9800, 1, 1d, ffffffff) + 39 fec99757 gdk_window_process_updates_internal (80f9800) + 27f fec99a94 gdk_window_process_updates (80f9800) + 90 fec99ae5 gdk_window_process_updates (80f9b48) + e1 fec99ae5 gdk_window_process_updates (808fbf0) + e1 fec99ae5 gdk_window_process_updates (808fb48) + e1 feaac23f gtk_window_check_resize (80e0800, 0, 0, fe9b0914) + 6ff fe9b0939 gtk_plug_check_resize (80e0800, 80a5538, 0, fec26e9e) + 31 fec26eef g_cclosure_marshal_VOID__VOID (80bf6e0, 0, 1, 80f6490, 8046a38, fe9b0908) + 5f fec0f92a g_type_class_meta_marshal (80bf6e0, 0, 1, 80f6490, 8046a38, 174) + 46 fec0f63a g_closure_invoke (80bf6e0, 0, 1, 80f6490, 8046a38, 8091880) + d6 fec26551 signal_emit_unlocked_R (80bfb90, 0, 80e0800, 0, 80f6490, 80e0800) + 16b9 fec24a88 g_signal_emit_valist (80e0800, 52, 0, 8046c2c) + 9c8 fec24c89 g_signal_emit (80e0800, 52, 0, fe8fe048) + 25 fe8fe06e gtk_container_check_resize (80e0800, fee0c460, 8046c68, fe8fde0a) + 3e fe8fde49 gtk_container_idle_sizer (0, fee0c460, 8046c98, fec72d18) + 4d fec72d35 gdk_threads_dispatch (80f8320, fee0c460, 8046cc8, fed67514) + 49 fed6752a g_idle_dispatch (80c4018, fec72cec, 80f8320, 8046d20) + 22 fed64eee g_main_context_dispatch (8091fe8, 6e, 80f45b8, b) + 262 fed6559f g_main_context_iterate (8091fe8, 1, 1, 8078720) + 483 fed65bc9 g_main_loop_run (80d83e8, 80d83e8, 8046e18, fd9b469e) + 1dd fd9b46ef bonobo_main (8046e40, fefc47a4, fda30cd0, b, fd9b2ad6, 80595c0) + 6b fd9b2b8d bonobo_generic_factory_main_timeout (80d3970, fd8f8c28, 80d3570, 7d0, 8046ea8) + b1 fd9b2ad6 bonobo_generic_factory_main (80d3970) + 26 fd8f8dc0 panel_applet_factory_main_closure (8059594, 80d34e8, 80d2cf0, fd8f8e4e) + f4 fd8f8e7e panel_applet_factory_main (8059594) + 3a 0805692f main (1, 8046f24, 8046f34, 8055a1f) + f7 08055a7d _start (3, 8047070, 0, 0, 0, 80470e1) + 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 ***