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 124990 - "nautilus-server-connect" crashes when setting up a new network server
"nautilus-server-connect" crashes when setting up a new network server
Status: VERIFIED DUPLICATE of bug 100709
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.4.x
Other FreeBSD
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-10-19 22:12 UTC by Lock
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Attachments
Bug Buddy File (3.97 KB, text/plain)
2003-10-19 22:12 UTC, Lock
Details

Description Lock 2003-10-19 22:12:23 UTC
Description of Problem:
When attempting to create a new network sever
under Nautilus, the "nautilus-server-connect"
program crashes.  

Steps to reproduce the problem:
1. Open Applications->Network Servers
2. Double-click on "New Server" icon
3. CPU will goto 100%
4. After 1-2 minutes, it crashes:
   Application "nautilus-server-connect" 
   (process 1) has crashed due to a fatal 
   error. (Abort trap)

Actual Results:
   Application "nautilus-server-connect" 
   (process 1) has crashed due to a fatal 
   error. (Abort trap)

Expected Results:
I would expect Nautilus to return an error dialog
if it does not find the server, or proceed with
the process if it does find it.  (Never having
seen this work, I am not sure what the next step
should be).

How often does this happen? 
Every time

Additional Information:
Comment 1 Lock 2003-10-19 22:12:57 UTC
Created attachment 20801 [details]
Bug Buddy File
Comment 2 Martin Wehner 2003-10-19 23:22:10 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 100709 ***
Comment 3 Lock 2003-10-20 05:31:31 UTC
Parent bug notes this to be due to a change in FreeBSD ABI.
Has this been reported against FreeBSD?  Is there a work-around or
resolution, either in nautilus or FreeBSD that's known?  Is the
FreeBSD (to your knowledge) working on fixing this?  Is there anything
I can do further to help?  
Comment 4 Matthew Gatto 2004-02-10 21:15:22 UTC
Lock: you may want to look at my comment at the end of bug 100709. In
short, this bug was filed a duplicate of 100709 based on misleading
information from the reporter of that bug. If you want to help further
you might want to test out whether this is still happening in 2.5
(it's probably fixed). The stacktrace included in your bug-buddy
report was not useful. Look here for more info on getting a useful
stacktrace: http://bugzilla.gnome.org/getting-traces.cgi

Re-opening and changing State -> NEEDINFO.
Comment 5 Martin Wehner 2004-09-16 20:36:08 UTC
No new info -> closing.