After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 395265 - crash in GNOME Commander: renombrando masivamente ...
crash in GNOME Commander: renombrando masivamente ...
Status: RESOLVED DUPLICATE of bug 467058
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other All
: High critical
: 1.2.4
Assigned To: epiotr
epiotr
Depends on:
Blocks:
 
 
Reported: 2007-01-11 03:27 UTC by rigel.vera
Modified: 2008-01-06 22:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description rigel.vera 2007-01-11 03:27:32 UTC 
Version: 1.2.0

What were you doing when the application crashed?
renombrando masivamente archivos de imagen


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 65224704 vsize: 0 resident: 65224704 share: 0 rss: 16564224 rss_rlim: 0
CPU usage: start_time: 1168485649 rtime: 0 utime: 2381 stime: 0 cutime:2267 cstime: 0 timeout: 114 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 -1224767824 (LWP 29976)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 101158

Thread 1 (Thread -1224767824 (LWP 29976))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #0 __kernel_vsyscall 






Comment 1


epiotr





          2008-01-06 22:50:50 UTC
        



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 467058 ***