GNOME Bugzilla – Bug 433923
crash in System Log: Trying to add new virtua...
Last modified: 2007-06-17 23:40:36 UTC
Version: 2.16.0 What were you doing when the application crashed? Trying to add new virtual host from xen kernel Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.20-1.2944.fc6 #1 SMP Tue Apr 10 17:27:49 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 83582976 vsize: 0 resident: 83582976 share: 0 rss: 13103104 rss_rlim: 0 CPU usage: start_time: 1177695637 rtime: 0 utime: 17 stime: 0 cutime:12 cstime: 0 timeout: 5 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/sbin/gnome-system-log' (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 -1208457520 (LWP 3262)] (no debugging symbols found) 0x00539402 in __kernel_vsyscall ()
+ Trace 130937
Thread 1 (Thread -1208457520 (LWP 3262))
----------- .xsession-errors --------------------- closing closing closing (nautilus:2909): Eel-WARNING **: Trying to add a callback for preferences/background_set that already exists. (nautilus:2909): Eel-WARNING **: Trying to add a callback for preferences/background_color that already exists. (nautilus:2909): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00003 (Open conne) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** (bug-buddy:3062): WARNING **: Couldn't load icon for Open Folder ** (bug-buddy:3264): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
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 366458 ***