GNOME Bugzilla – Bug 372648
crash in Computer: changing SELINUX status ...
Last modified: 2006-11-08 20:41:34 UTC
What were you doing when the application crashed? changing SELINUX status to 'user data' Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- subset is whole list! event->keyval: 65364, event->state:0 Not mathced subset is whole list! event->keyval: 113, event->state:0 Not mathced mode: 640x400x32 Window manager warning: Window 0x3400017 (MPlayer) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 400 x 130; this doesn't make much sense. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** (nautilus:18669): WARNING **: file already in tree (parent_ptr: (nil))!!! ** (bug-buddy:24876): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 136400896 vsize: 0 resident: 136400896 share: 0 rss: 32956416 rss_rlim: 0 CPU usage: start_time: 1162938868 rtime: 0 utime: 1224 stime: 0 cutime:1056 cstime: 0 timeout: 168 it_real_value: 0 frequency: 97 Backtrace was generated from '/usr/bin/nautilus' (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 -1208711472 (LWP 18669)] (no debugging symbols found) 0x00b55402 in __kernel_vsyscall ()
+ Trace 84498
Thread 1 (Thread -1208711472 (LWP 18669))
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 362302 ***