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 344161 - Nautilus crashes on attempting to connect to a Windows Share
Nautilus crashes on attempting to connect to a Windows Share
Status: RESOLVED DUPLICATE of bug 314730
Product: nautilus
Classification: Core
Component: general
2.12.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-06-07 14:43 UTC by jagdeep.addagarla
Modified: 2006-06-07 15:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description jagdeep.addagarla 2006-06-07 14:43:54 UTC
Distribution: Unknown
Package: nautilus
Severity: Normal
Version: GNOME2.12.0 2.12.0
Gnome-Distributor: SUSE
Synopsis: Nautilus crashes on attempting to connect to a Windows Share
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.12.0
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:
Nautilus crashes on attempting to connect to a Windows Share

Steps to reproduce the crash:
1. Open a Nautilus Window, go to menu, click on "Connect to Server"
2. In the dialog box that appears, choose "Windows Share" and type in
the details of the share you want to connect to.
3. Watch the system crash as you attempt to make the connection.

Expected Results:

An open window to the Share I was trying to get to.

How often does this happen?

Every time.

Additional Information:

No.  Just fix this.


Debugging Information:

Backtrace was generated from '/opt/gnome/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1092587744 (LWP 20102)]
[New Thread 1137769392 (LWP 20109)]
[Thread debugging using libthread_db enabled]
[New Thread 1092587744 (LWP 20102)]
[New Thread 1137769392 (LWP 20109)]
[Thread debugging using libthread_db enabled]
[New Thread 1092587744 (LWP 20102)]
[New Thread 1137769392 (LWP 20109)]
[New Thread 1137503152 (LWP 20108)]
[New Thread 1137236912 (LWP 20107)]
[New Thread 1136970672 (LWP 20106)]
[New Thread 1136704432 (LWP 20105)]
[New Thread 1136438192 (LWP 20104)]
[New Thread 1132850096 (LWP 20103)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 1092587744 (LWP 20102))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 stpcpy
    from /lib/tls/libc.so.6
  • #5 g_stpcpy
    from /opt/gnome/lib/libglib-2.0.so.0
  • #6 g_strconcat
    from /opt/gnome/lib/libglib-2.0.so.0
  • #7 nautilus_connect_server_dialog_get_type
  • #8 g_cclosure_marshal_VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #10 g_signal_stop_emission
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #13 gtk_dialog_response
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #14 gtk_dialog_response
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #17 g_signal_stop_emission
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #20 gtk_button_clicked
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #21 gtk_button_get_alignment
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #22 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #23 g_cclosure_new_swap
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #24 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #25 g_signal_stop_emission
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #28 gtk_button_released
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #29 gtk_button_set_relief
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #30 gtk_marshal_VOID__UINT_STRING
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #31 g_cclosure_new_swap
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #32 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #33 g_signal_stop_emission
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #34 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #35 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #36 gtk_widget_activate
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #37 gtk_propagate_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #38 gtk_main_do_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #39 gdk_screen_get_setting
    from /opt/gnome/lib/libgdk-x11-2.0.so.0
  • #40 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #41 g_main_context_check
    from /opt/gnome/lib/libglib-2.0.so.0
  • #42 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #43 gtk_main
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #44 main
  • #0 __kernel_vsyscall




------- Bug created by bug-buddy at 2006-06-07 14:43 -------


Unknown version 2.12.0 in product nautilus.  Setting version to "2.12.x".

Comment 1 Elijah Newren 2006-06-07 15:05:38 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 343828, which has been marked as a duplicate of 314730.

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