Bug 401717 – crash in GNOME Commander: SMB-browsing crashes

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 401717 - crash in GNOME Commander: SMB-browsing crashes


Summary:	crash in GNOME Commander: SMB-browsing crashes


Status:	RESOLVED DUPLICATE of bug 349631

Product:	gnome-commander
Classification:	Other
Component:	networking
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-28 15:53 UTC by Martin van der Vlist
Modified:	2007-01-29 09:22 UTC

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

Description Martin van der Vlist 2007-01-28 15:53:28 UTC

Version: 1.2.0

What were you doing when the application crashed?
I clicked the button "SMB" to browse my samba network. I double-clicked the workgroup-name (debianhome) to open it. It asked me to open a remote file, which I cancelled/ignored.


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

Memory status: size: 63414272 vsize: 0 resident: 63414272 share: 0 rss: 14389248 rss_rlim: 0
CPU usage: start_time: 1169998888 rtime: 0 utime: 315 stime: 0 cutime:299 cstime: 0 timeout: 16 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 -1225042256 (LWP 16652)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 105985

Thread 1 (Thread -1225042256 (LWP 16652))

#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 Martin van der Vlist 2007-01-28 16:15:46 UTC

SMB server is Debian Sarge. smbc also crashes. 

I'm sorry, It didn't crash when I opened the file, but when I was clicking around afterwards. I can reproduce it by double-clicking the location bar. 

Typing "cd debianhome" on the commandline does work, but then the computer-name is recognized as a file, with the same problems as the group, and a similar crash occurs when clicking the location bar. "cd linux-server" does also work, and from that point on the share is shown in normal fashion. 

If I type "cd debianhom" instead of debianhome, it also crashes. Very easy to reproduce, so if the crash reports are useful, I can generate some more bugs ;)

Comment 2 epiotr 2007-01-28 23:12:25 UTC

Please upgrade to version 1.2.3 (http://www.nongnu.org/gcmd/download.html#distro).  This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Thanks for the report.

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

Comment 3 Martin van der Vlist 2007-01-29 09:22:12 UTC

Thanks for the quick response :)

And about upgrading: I'll wait for feisty, and in the meantime mount the drives using fstab :)