Bug 437155 – crash in GNOME Commander:

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 437155 - crash in GNOME Commander:


Summary:	crash in GNOME Commander:


Status:	RESOLVED DUPLICATE of bug 376909

Product:	gnome-commander
Classification:	Other
Component:	application
Version:	1.2.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	1.2.4
Assigned To:	epiotr
QA Contact:	epiotr

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-05-09 14:09 UTC by made-it
Modified:	2007-05-12 19:46 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description made-it 2007-05-09 14:09:01 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: 79585280 vsize: 0 resident: 79585280 share: 0 rss: 28393472 rss_rlim: 0
CPU usage: start_time: 1178719715 rtime: 0 utime: 1326 stime: 0 cutime:741 cstime: 0 timeout: 585 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 -1225111888 (LWP 26140)]
[New Thread -1261024352 (LWP 26164)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 133261

Thread 2 (Thread -1261024352 (LWP 26164))

#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 Susana 2007-05-12 19:46:04 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 ***