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 411991 - crash in GNOME Commander:
crash in GNOME Commander:
Status: RESOLVED DUPLICATE of bug 375704
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-02-25 19:04 UTC by Paweł Widera
Modified: 2007-02-25 20:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Paweł Widera 2007-02-25 19:04:12 UTC 
Version: 1.2.0

What were you doing when the application crashed?



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

Memory status: size: 59883520 vsize: 0 resident: 59883520 share: 0 rss: 15581184 rss_rlim: 0
CPU usage: start_time: 1172430194 rtime: 0 utime: 256 stime: 0 cutime:238 cstime: 0 timeout: 18 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 -1225345360 (LWP 5741)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 113836

Thread 1 (Thread -1225345360 (LWP 5741))

  • #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


Paweł Widera





          2007-02-25 20:06:54 UTC
        



I sent this dup accidentally from bug buddy, sorry.

*** This bug has been marked as a duplicate of 375704 ***