Bug 359820 – gnome-commander: Crash on viewing smb network

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 359820 - gnome-commander: Crash on viewing smb network


Summary:	gnome-commander: Crash on viewing smb network


Status:	RESOLVED DUPLICATE of bug 349631

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-05 08:22 UTC by ksup
Modified:	2006-10-05 08:34 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description ksup 2006-10-05 08:21:40 UTC

Distribution: Debian testing/unstable
Package: gnome-commander
Severity: Normal
Version: GNOME2.14.3 1.2.0
Gnome-Distributor: Debian
Synopsis: Crash on viewing smb network
Bugzilla-Product: gnome-commander
Bugzilla-Component: application
Bugzilla-Version: 1.2.0
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Crash on viewing smb network

Steps to reproduce the crash:
1. Click on "SMB" buttom (right from "Home" buttom)
2. Double click on string beggining with "\\"

Debugging Information:

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 -1491560768 (LWP 18510)]
[New Thread -1496036432 (LWP 18513)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 74638

Thread 1 (Thread -1491560768 (LWP 18510))

#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





------- Bug created by bug-buddy at 2006-10-05 08:22 -------


Unknown version 1.2.0 in product gnome-commander.  Setting version to "1.2.x".

Comment 1 André Klapper 2006-10-05 08:34:46 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 349631 ***