GNOME Bugzilla – Bug 478047
crash in GNOME Commander: renaming files
Last modified: 2008-01-06 22:54:39 UTC
Version: 1.2.4 What were you doing when the application crashed? renaming files Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 42913792 vsize: 42913792 resident: 22351872 share: 12902400 rss: 22351872 rss_rlim: 4294967295 CPU usage: start_time: 1190131876 rtime: 784 utime: 730 stime: 54 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-commander' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227364672 (LWP 19282)] (no debugging symbols found) 0xb7fb07f2 in ?? () from /lib/ld-linux.so.2
+ Trace 163759
Thread 1 (Thread -1227364672 (LWP 19282))
----------- .xsession-errors (14 sec old) --------------------- (gnome-commander:19282): Gtk-CRITICAL **: gtk_window_resize: assertion `width > 0' failed ** (gnome-commander:19282): CRITICAL **: void gnome_cmd_dir_file_deleted(GnomeCmdDir*, const gchar*): assertion `GNOME_CMD_IS_FILE (finfo)' failed ** (gnome-commander:19282): CRITICAL **: void gnome_cmd_dir_file_deleted(GnomeCmdDir*, const gchar*): assertion `GNOME_CMD_IS_FILE (finfo)' failed ** (gnome-commander:19282): CRITICAL **: void gnome_cmd_dir_file_deleted(GnomeCmdDir*, const gchar*): assertion `GNOME_CMD_IS_FILE (finfo)' failed ** (gnome-commander:19282): CRITICAL **: void gnome_cmd_dir_file_deleted(GnomeCmdDir*, const gchar*): assertion `GNOME_CMD_IS_FILE (finfo)' failed fixme:heap:RtlCompactHeap stub fixme:heap:RtlCompactHeap stub fixme:heap:RtlCompactHeap stub fixme:heap:RtlCompactHeap stub fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 --------------------------------------------------
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 ***