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 379645 - crash in GNOME Commander: searching using GNOME Co...
crash in GNOME Commander: searching using GNOME Co...
Status: RESOLVED DUPLICATE of bug 376909
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other All
: High critical
: 1.2.2
Assigned To: epiotr
epiotr
Depends on:
Blocks:
 
 
Reported: 2006-11-27 01:12 UTC by rlaggart
Modified: 2006-11-27 21:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description rlaggart 2006-11-27 01:12:41 UTC
Version: 1.2.0

What were you doing when the application crashed?
searching using GNOME Commander


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

Memory status: size: 60891136 vsize: 0 resident: 60891136 share: 0 rss: 13582336 rss_rlim: 0
CPU usage: start_time: 1164589870 rtime: 0 utime: 89 stime: 0 cutime:74 cstime: 0 timeout: 15 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 -1224890704 (LWP 11567)]
[New Thread -1256088672 (LWP 11584)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread -1256088672 (LWP 11584))

  • #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-11-27 21:00:52 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 ***