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 111892 - Crash while trying to navigate into smb file system
Crash while trying to navigate into smb file system
Status: RESOLVED DUPLICATE of bug 107741
Product: nautilus
Classification: Core
Component: Navigation
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-04-30 02:03 UTC by stormer2000
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description stormer2000 2003-04-30 02:05:26 UTC
Package: nautilus
Severity: normal
Version: 2.2.1
Synopsis: Crash while trying to navigate into smb file system
Bugzilla-Product: nautilus
Bugzilla-Component: Navigation
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:


Steps to reproduce the problem:
1. Build a samba system with 2 computers (winXP + redhat 9)
2. Add Redhat shared
3. Try navigating in a directory ex. smb:///servername/directory

Actual Results:
Crash on fatal error

Expected Results:
Seing my shared group

How often does this happen?
Since I changed my smb config using Swat


Additional Information:




Debugging Information:

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1087967552 (LWP 3496)]
[New Thread 1184091440 (LWP 3506)]
[New Thread 1175698736 (LWP 3505)]
[New Thread 1167306032 (LWP 3504)]
[New Thread 1158913328 (LWP 3503)]
[New Thread 1150520624 (LWP 3502)]
[New Thread 1142127920 (LWP 3501)]
[New Thread 1133735216 (LWP 3500)]
[New Thread 1125342512 (LWP 3499)]
[New Thread 1116949808 (LWP 3498)]
[New Thread 1099955504 (LWP 3497)]
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0xffffe002 in ?? ()

Thread 3 (Thread 1175698736 (LWP 3505))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 _init
    from /usr/lib/gnome-vfs-2.0/modules/libsmb.so
  • #4 _init
    from /usr/lib/gnome-vfs-2.0/modules/libsmb.so
  • #5 get_file_type
    from /usr/lib/gnome-vfs-2.0/modules/libsmb.so
  • #6 get_file_type
    from /usr/lib/gnome-vfs-2.0/modules/libsmb.so
  • #7 get_file_type
    from /usr/lib/gnome-vfs-2.0/modules/libsmb.so
  • #8 gnome_vfs_get_file_info_uri_cancellable
    from /usr/lib/libgnomevfs-2.so.0
  • #9 _gnome_vfs_job_go
    from /usr/lib/libgnomevfs-2.so.0
  • #10 _gnome_vfs_job_execute
    from /usr/lib/libgnomevfs-2.so.0
  • #11 _gnome_vfs_job_queue_shutdown
    from /usr/lib/libgnomevfs-2.so.0
  • #12 _gnome_vfs_thread_pool_init
    from /usr/lib/libgnomevfs-2.so.0
  • #13 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #14 start_thread
    from /lib/tls/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-04-29 22:05 -------

The original reporter (stormer2000@hotmail.com) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 Elijah Newren 2003-04-30 20:15:30 UTC
Quite a few are getting this.  I just recently (late last night) found
some good steps to reliably reproduce this and obtained a slightly
better stack trace.  The maintainer says that should be enough to
discover the problem and fix it, so hopefully this will be resolved
before long...

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