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 131302 - crash when attempting to open (view) link to a windows 2k computer on same subnet
crash when attempting to open (view) link to a windows 2k computer on same su...
Status: RESOLVED DUPLICATE of bug 107741
Product: nautilus
Classification: Core
Component: Views: All
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-01-13 03:25 UTC by jmwincn
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description jmwincn 2004-01-13 03:25:37 UTC
Package: nautilus
Severity: normal
Version: 2.2.1
Synopsis: crash when attempting to open (view) link to a windows 2k computer on same subnet
Bugzilla-Product: nautilus
Bugzilla-Component: View as (Icons or List)
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
when i try to view folders and directories in a windows machine on this
same subnet (small network), nautilus crashes.  it then restarts, and i
can successfully view folders and directories on the other machine.

Steps to reproduce the problem:
1. boot machine, login, Main-NetworkServers, choose machine icon, open
directory, close window
2. wait a few minutes (something like 15 - 20)
3. try Main-NetworkServers, Nautilus displays message "cannot display
contents of..."
4. close "cannot display" window, try Main-NetworkServers again

Actual Results:
Nautilus crashes, then restarts.

Expected Results:
Nautilus should just re-open a window with file and folder/directory
icons.

How often does this happen?
i can repeat the sequence indefinately.

Additional Information:
Nautilus v2.2.1-5, RH9 2.4.20-28.9
Dell PW410, two CPUS, 38GB HD, 1GB Ram
Belkin KVM
other machine: Dell PW410, Win2K, 100GB HD, 1GB Ram



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 1087968960 (LWP 2397)]
[New Thread 1116957488 (LWP 2411)]
[New Thread 1099651888 (LWP 2410)]
(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 1099651888 (LWP 2410))

  • #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 2004-01-12 22:25 -------

The original reporter (jmwincn@earthlink.net) 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 Matthew Gatto 2004-01-13 03:36:33 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 107741 ***
Comment 2 jmwincn 2004-01-13 15:55:09 UTC
i don't understand the comment about 'no account'.  i'm not familiar
with the bugzilla procedure, but i do have an account at Red Hat. 
should i register in some other?

i know this is an older version of Nautilus, i believe it was a part
of the Shrike distribution.  do Nautilus v2.5.4 and eel v2.5.5 have a
fix for this?  at least one bugzilla link mentions "gnome-vfs-extras
0.99.11".  should i go find that and install it?
Comment 3 Matthew Gatto 2004-02-18 07:39:05 UTC
jmwincn@earthlink.net: yes this is fixed in 2.5 and yes upgrading to
the latest stable GNOME.org releases of gnome-vfs2/gnome-vfs2-extras 
should fix the problem. If it DOES NOT, please report this along with
the versions of the releveant packages you're using and any other
relevant information to bug 107741 in a comment. All further
discussion should continue there.

You can register for an account (which you'll need to add comments and
participate in other bugs) here:
http://bugzilla.gnome.org/createaccount.cgi
Comment 4 Matthew Gatto 2004-02-18 07:44:17 UTC
If you upgrade to gnome-2.4.2 it should be fixed. if not, file a new
bug report :)