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 400739 - crash in GNOME Commander:
crash in GNOME Commander:
Status: RESOLVED DUPLICATE of bug 378534
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-25 19:19 UTC by mitacekstepan
Modified: 2007-01-25 22:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description mitacekstepan 2007-01-25 19:19:23 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: 143634432 vsize: 143634432 resident: 16678912 share: 10481664 rss: 16678912 rss_rlim: -1
CPU usage: start_time: 1169752746 rtime: 89 utime: 84 stime: 5 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47907809028464 (LWP 17799)]
(no debugging symbols found)
0x00002b9265199eb5 in waitpid () from /lib/libpthread.so.0

+ Trace 105227

Thread 1 (Thread 47907809028464 (LWP 17799))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #4 g_hash_table_insert
    from /usr/lib/libglib-2.0.so.0
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


epiotr





          2007-01-25 22:52:29 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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