GNOME Bugzilla – Bug 390261
crash in Computer: moving a php extension f...
Last modified: 2007-01-02 19:04:39 UTC
Version: 2.16.2 What were you doing when the application crashed? moving a php extension from the moduels folder to another folder 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.2868.fc6 #1 SMP Fri Dec 15 17:32:54 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- Loading "skip-broken" plugin Loading "installonlyn" plugin Loading "priorities" plugin Loading "protectbase" plugin 0 packages excluded due to repository priority protections 0 packages excluded due to repository protections Loading "skip-broken" plugin Loading "installonlyn" plugin Loading "priorities" plugin Loading "protectbase" plugin 0 packages excluded due to repository priority protections 0 packages excluded due to repository protections Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x3c00035 (README (/u); these messages lack timestamps and therefore suck. ** (bug-buddy:5234): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 90238976 vsize: 0 resident: 90238976 share: 0 rss: 26673152 rss_rlim: 0 CPU usage: start_time: 1167286197 rtime: 0 utime: 1181 stime: 0 cutime:1094 cstime: 0 timeout: 87 it_real_value: 0 frequency: 0 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 -1209156864 (LWP 2761)] [New Thread -1285436528 (LWP 5232)] [New Thread -1274946672 (LWP 5231)] (no debugging symbols found) 0x005b1402 in __kernel_vsyscall ()
+ Trace 97469
Thread 2 (Thread -1285436528 (LWP 5232))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 368608 ***