Bug 360626 – crash in GNOME Commander: trying to connect to win...

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 360626 - crash in GNOME Commander: trying to connect to win...


Summary:	crash in GNOME Commander: trying to connect to win...


Status:	RESOLVED DUPLICATE of bug 349631

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

Importance:	High critical
Target Milestone:	1.2.1
Assigned To:	Assaf Gordon
QA Contact:	epiotr

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-08 12:27 UTC by olinko
Modified:	2006-10-08 12:46 UTC

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

Description olinko 2006-10-08 12:27:52 UTC

Version: 1.2.0

What were you doing when the application crashed?
trying to connect to windows computer via samba, a text file only showed instead of computer, I think I was clicking a few times on that file


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 45162496 vsize: 0 resident: 45162496 share: 0 rss: 14098432 rss_rlim: 0
CPU usage: start_time: 1160310334 rtime: 0 utime: 218 stime: 0 cutime:208 cstime: 0 timeout: 10 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 -1225210192 (LWP 15939)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 75223

Thread 1 (Thread -1225210192 (LWP 15939))

#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 ??
#5 ??
#6 ??
#7 ??
#8 g_value_peek_pointer
from /usr/lib/libgobject-2.0.so.0
#9 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#10 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#14 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#17 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#18 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#20 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#21 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
#23 ??
#24 ??
#25 _IO_stdin_used
#26 ??
#0 __kernel_vsyscall

Comment 1 Elijah Newren 2006-10-08 12:46:25 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.

Matches the stack trace in bug 358124, which has been marked as a duplicate of 349631

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