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 388361 - crash in GNOME Commander: I was seeking for file "...
crash in GNOME Commander: I was seeking for file "...
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: 2006-12-21 19:01 UTC by zaborowg
Modified: 2006-12-22 21:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description zaborowg 2006-12-21 19:01:04 UTC 
Version: 1.2.0

What were you doing when the application crashed?
I was seeking for file "incoming"


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

Memory status: size: 64479232 vsize: 0 resident: 64479232 share: 0 rss: 15048704 rss_rlim: 0
CPU usage: start_time: 1166727206 rtime: 0 utime: 817 stime: 0 cutime:702 cstime: 0 timeout: 115 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 -1225562448 (LWP 10124)]
[New Thread -1258771552 (LWP 10409)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 96029

Thread 2 (Thread -1258771552 (LWP 10409))

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






Comment 1


André Klapper





          2006-12-22 21:12:54 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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