GNOME Bugzilla – Bug 375704
crash in GNOME Commander: Regel im Tool zu Mehrfac...
Last modified: 2008-01-06 22:56:32 UTC
Version: 1.2.0 What were you doing when the application crashed? Regel im Tool zu Mehrfachumbenennen geändert Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 55713792 vsize: 0 resident: 55713792 share: 0 rss: 14749696 rss_rlim: 0 CPU usage: start_time: 1163625647 rtime: 0 utime: 76 stime: 0 cutime:72 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-commander' (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 -1225296208 (LWP 6041)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 86777
Thread 1 (Thread -1225296208 (LWP 6041))
*** Bug 380115 has been marked as a duplicate of this bug. ***
*** Bug 381934 has been marked as a duplicate of this bug. ***
confirming as per duplicates
*** Bug 383163 has been marked as a duplicate of this bug. ***
*** Bug 383164 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug. You'll also need to add a stack trace with debug information (of gtk+ 2, glib 2 at least); please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance!
grrr, setting to NEW again
*** Bug 383904 has been marked as a duplicate of this bug. ***
*** Bug 387243 has been marked as a duplicate of this bug. ***
*** Bug 389034 has been marked as a duplicate of this bug. ***
*** Bug 401024 has been marked as a duplicate of this bug. ***
*** Bug 402114 has been marked as a duplicate of this bug. ***
*** Bug 410591 has been marked as a duplicate of this bug. ***
*** Bug 411991 has been marked as a duplicate of this bug. ***
*** Bug 415107 has been marked as a duplicate of this bug. ***
*** Bug 415451 has been marked as a duplicate of this bug. ***
*** Bug 415992 has been marked as a duplicate of this bug. ***
*** Bug 416602 has been marked as a duplicate of this bug. ***
*** Bug 416603 has been marked as a duplicate of this bug. ***
*** Bug 418262 has been marked as a duplicate of this bug. ***
*** Bug 418264 has been marked as a duplicate of this bug. ***
*** Bug 418268 has been marked as a duplicate of this bug. ***
*** Bug 421538 has been marked as a duplicate of this bug. ***
*** Bug 426747 has been marked as a duplicate of this bug. ***
*** Bug 441574 has been marked as a duplicate of this bug. ***
*** Bug 446200 has been marked as a duplicate of this bug. ***
*** Bug 453103 has been marked as a duplicate of this bug. ***
*** Bug 393635 has been marked as a duplicate of this bug. ***
@epiotr: looks like bug 412031 has a nice stacktrace for this one
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 407418 ***