GNOME Bugzilla – Bug 384680
Renaming a file pressing F2
Last modified: 2009-01-04 02:27:03 UTC
What were you doing when the application crashed? Renaming a file pressing 'F2'. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 85819392 vsize: 0 resident: 85819392 share: 0 rss: 34652160 rss_rlim: 0 CPU usage: start_time: 1165825220 rtime: 0 utime: 1665 stime: 0 cutime:1534 cstime: 0 timeout: 131 it_real_value: 0 frequency: 300 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226692944 (LWP 4363)] (no debugging symbols found) 0xb7f9d410 in __kernel_vsyscall ()
+ Trace 93257
Thread 1 (Thread -1226692944 (LWP 4363))
*** Bug 390155 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 399662 has been marked as a duplicate of this bug. ***
Probably pango. I'll check what I changed around there recently. I know I did? Removing NEEDINFO, so it won't be closed.
*** Bug 408184 has been marked as a duplicate of this bug. ***
*** Bug 412888 has been marked as a duplicate of this bug. ***
*** Bug 421571 has been marked as a duplicate of this bug. ***
*** Bug 421772 has been marked as a duplicate of this bug. ***
*** Bug 423469 has been marked as a duplicate of this bug. ***
*** Bug 422912 has been marked as a duplicate of this bug. ***
*** Bug 428108 has been marked as a duplicate of this bug. ***
*** Bug 432333 has been marked as a duplicate of this bug. ***
*** Bug 433057 has been marked as a duplicate of this bug. ***
*** Bug 476485 has been marked as a duplicate of this bug. ***
No dups for quite a while. Lets close.