GNOME Bugzilla – Bug 455788
crash in Window Selector: moving email to another ...
Last modified: 2007-07-11 09:23:09 UTC
Version: 2.18.2 What were you doing when the application crashed? moving email to another window Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 34349056 vsize: 34349056 resident: 12218368 share: 10465280 rss: 12218368 rss_rlim: 4294967295 CPU usage: start_time: 1184126883 rtime: 206 utime: 187 stime: 19 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/wnck-applet' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209125152 (LWP 3252)] (no debugging symbols found) 0x00bd7402 in __kernel_vsyscall ()
+ Trace 147176
Thread 1 (Thread -1209125152 (LWP 3252))
----------- .xsession-errors (2097 sec old) --------------------- (gnome-panel:3222): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkMenuShell' (gnome-panel:3222): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (gnome-panel:3222): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkMenuShell' (gnome-panel:3222): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed error getting update info: Cannot open/read repomd.xml file for repository: fedora ** Message: <info> You are now connected to the wireless network 'copper'. Loading "installonlyn" plugin CalDAV Eplugin starting up ... ** (evolution:3379): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3379): DEBUG: mailto URL program: evolution --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 420713 ***