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 417173 - crash in GNOME Commander: system wystartował
crash in GNOME Commander: system wystartował
Status: RESOLVED DUPLICATE of bug 376909
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-03-11 18:32 UTC by dudaj
Modified: 2007-03-15 14:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description dudaj 2007-03-11 18:32:01 UTC 
Version: 1.2.3

What were you doing when the application crashed?
system wystartował


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

Memory status: size: 112549888 vsize: 0 resident: 112549888 share: 0 rss: 61743104 rss_rlim: 0
CPU usage: start_time: 1173636530 rtime: 0 utime: 2569 stime: 0 cutime:1916 cstime: 0 timeout: 653 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 -1225398608 (LWP 6311)]
[New Thread -1260573792 (LWP 6337)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 117767

Thread 2 (Thread -1260573792 (LWP 6337))

  • #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 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #5 g_hash_table_insert
    from /usr/lib/libglib-2.0.so.0
  • #6 ?? 






Comment 1


Susana





          2007-03-15 14:20:32 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 376909 ***