Bug 402975 – 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 402975 - 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-01-31 21:01 UTC by mitacekstepan
Modified:	2007-02-09 17:07 UTC

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

Description mitacekstepan 2007-01-31 21:01:02 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: 156344320 vsize: 156344320 resident: 21291008 share: 10977280 rss: 21291008 rss_rlim: -1
CPU usage: start_time: 1170277233 rtime: 201 utime: 117 stime: 84 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 47755139053936 (LWP 23390)]
[New Thread 1082132816 (LWP 23396)]
(no debugging symbols found)
0x00002b6edb8ba7f6 in poll () from /lib/libc.so.6

+ Trace 106932

Thread 2 (Thread 1082132816 (LWP 23396))

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

Comment 1 Marc-Andre Lureau 2007-02-09 17:07:36 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 ***