GNOME Bugzilla – Bug 375528
crash in Computer: First tried to change na...
Last modified: 2006-11-16 01:22:37 UTC
What were you doing when the application crashed? First tried to change name of Kingston Data Traveler Failed Tried to change to Personal 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:39:22 EDT 2006 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- hpssd (pid 2470) is running... hidd hidd (pid 2420) is running... hidd hidd (pid 2420) is running... (nautilus:3016): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Unknown tag 'B' on line 1 char 12 ** (nautilus:3016): CRITICAL **: nautilus_file_get_internal: assertion `uri != NULL' failed ** (nautilus:3016): CRITICAL **: nautilus_file_get_internal: assertion `uri != NULL' failed ** (nautilus:3016): WARNING **: Hit unhandled case 24 (İşleme izin verilmiyor) in fm_report_error_setting_permissions ** (bug-buddy:7352): WARNING **: Klasör Aç için simge yüklenemedi -------------------------------------------------- Memory status: size: 480120832 vsize: 480120832 resident: 43642880 share: 22728704 rss: 43642880 rss_rlim: -1 CPU usage: start_time: 1163603422 rtime: 1696 utime: 1148 stime: 548 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912519074656 (LWP 3016)] [New Thread 1115699520 (LWP 4476)] (no debugging symbols found) 0x0000003a81a0d96f in waitpid () from /lib64/libpthread.so.0
+ Trace 86665
Thread 1 (Thread 46912519074656 (LWP 3016))
*** Bug 375530 has been marked as a duplicate of this bug. ***
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 362302 *** *** This bug has been marked as a duplicate of 362302 ***