GNOME Bugzilla – Bug 609906
crash in Window Selector:
Last modified: 2010-02-15 03:35:47 UTC
Version: 2.28.0 What were you doing when the application crashed? Distribution: OpenSolaris Development snv_130 X86 Gnome Release: 2.28.0 2009-12-07 (Sun Microsystems, Inc.) BugBuddy Version: 2.28.0 X Vendor: Sun Microsystems, Inc., based on X.Org Foundation sources X Vendor Release: 10703000 Selinux: No Accessibility: Disabled GTK+ Theme: SmoothGNOME Icon Theme: Mist GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 82059264 vsize: 82059264 resident: 16044032 share: 2789376 rss: 16044032 rss_rlim: 0 CPU usage: start_time: 1266146351 rtime: 35 utime: 274278 stime: 78690 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/lib/wnck-applet' 1799: /usr/lib/wnck-applet --oaf-activate-iid=OAFIID:GNOME_Wncklet_Factory - feef48f7 waitid (0, 925, 8046b50, 3) feea3e65 waitpid (925, 8046c0c, 0, fed9b601) + 65 fed9ba08 g_spawn_sync (0, 80ab888, 0, 4, 0, 0) + 418 fed9be1c g_spawn_command_line_sync (812dc90, 0, 0, 0, 8046d2c) + 5c fdad1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (806dd98, 707, 0, fdad1ff2) + f3 fdad20d6 __1cMcheck_if_gdb6F_v_ (80, fef82000, 8046dbc, feeefd85, 8, 0) + 12e fdad1a94 __1cUbugbuddy_segv_handle6Fi_v_ (8, 0, 8046e70, ffbffeff, ffff, fee12a00) + 64 feeefd85 __sighndlr (8, 0, 8046e70, fdad1a30) + 15 feee2cef call_user_handler (8) + 2af feee2f1f sigacthandler (8, 0, 8046e70) + df --- called from signal handler with signal 8 (SIGFPE) --- 08058a42 applet_scroll (80961f8, 80958b0) + 62 fe981692 _gtk_marshal_BOOLEAN__BOXED (80e4c10, 8047200, 2, 80d9050, 8047228, 0) + 76 fec0f63a g_closure_invoke (80e4c10, 8047200, 2, 80d9050, 8047228, 1) + d6 fec25c2c signal_emit_unlocked_R (8087ad8, 0, 80961f8, 8047370, 80d9050, 14) + d94 fec24882 g_signal_emit_valist (80961f8, 23, 0, 804741c) + 7c2 fec24c89 g_signal_emit (80961f8, 23, 0, 80958b0, 804743c, 80bfc60) + 25 fea9b116 gtk_widget_event_internal (80961f8, 80958b0, 8047468, fea9acc4) + 246 fea9ad59 gtk_widget_event (80961f8, 80958b0, 80474a8, fe9800cd) + ad fe98014a gtk_propagate_event (80e2830, 80958b0, 80474d8, fe97ec3a) + 9a fe97efb2 gtk_main_do_event (80958b0, 0, 8047528, fecb356a) + 386 fecb35ba gdk_event_dispatch (8096fe8, 0, 0, fed64d28) + 5a fed64eee g_main_context_dispatch (8097030, 0, 80bee78, b) + 262 fed6559f g_main_context_iterate (8097030, 1, 1, 807b558) + 483 fed65bc9 g_main_loop_run (80bf4e0, 80bf4e0, 8047678, fd9b469e) + 1dd fd9b46ef bonobo_main (80476a0, fefc47a4, fda10858, b, fd9b2ad6, 805b55d) + 6b fd9b2b8d bonobo_generic_factory_main_timeout (80ba668, fe4f8c28, 80ba260, 7d0, 8047708) + b1 fd9b2ad6 bonobo_generic_factory_main (80ba668) + 26 fe4f8dc0 panel_applet_factory_main_closure (805b540, 80ba1e0, 80b8df0, fe4f8e4e) + f4 fe4f8e7e panel_applet_factory_main (805b540) + 3a 0805671f main (1, 8047784, 8047794, 805600f) + f7 0805606d _start (3, 80478c4, 0, 0, 0, 8047919) + 7d ---- Critical and fatal warnings logged during execution ---- ** Wnck **: file screen.c: line 850: assertion `WNCK_IS_SCREEN (screen)' failed ** Wnck **: file workspace.c: line 212: assertion `WNCK_IS_WORKSPACE (space)' failed ** Wnck **: file screen.c: line 1051: assertion `WNCK_IS_SCREEN (screen)' failed ----------- .xsession-errors (8 sec old) --------------------- (nautilus:1749): Gtk-CRITICAL **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed (nautilus:1749): Gtk-WARNING **: About JDS: missing action About JDS (emacs-gtk:1750): Gtk-WARNING **: Unable to locate theme engine in module_path: "smooth", (emacs-gtk:1750): Gtk-WARNING **: Unable to locate theme engine in module_path: "smooth", (emacs-gtk:1750): Gtk-WARNING **: Unable to locate theme engine in module_path: "smooth", (emacs-gtk:1750): Gtk-WARNING **: Unable to locate theme engine in module_path: "smooth", (emacs-gtk:1750): Gtk-WARNING **: Unable to locate theme engine in module_path: "smooth", (emacs-gtk:1750): Gtk-WARNING **: Unable to locate theme engine in module_path: "smooth", --------------------------------------------------
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 527666 ***