Bug 47466

Summary: nautilus setup druid network doesn't mention failures
Product: [Retired] Red Hat Linux Reporter: Telsa Gwynne <hobbit>
Component: nautilusAssignee: David Mason <dcm>
Status: CLOSED NOTABUG QA Contact: Aaron Brown <abrown>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-07-05 17:05:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Telsa Gwynne 2001-07-05 17:05:37 UTC
Description of Problem:

Started Gnome before I had set up networking. Met the nautilus
setup druid for the first time. It wanted to test the networking
by connecting to Eazel services (should this be the RH page or
something now?).

I said yes, test it, despite having no network. It said it couldn't
establish a connection and that perhaps I had a proxy or needed one?
I said no and it flipped to the next screen without telling me whether
it had tried again and whether it had been successful or not. Then it
said it would start a window with my home directory in it. And nothing
happened. Later I found a nautilus core there. I suspect it occurred
then.

Steps to Reproduce:
1. Remove ~/Nautilus. Stop networking.
2. Start up Gnome.
3. Go through druid.

Comment 1 David Mason 2001-07-05 17:41:21 UTC
Eazel services are gone now - the package that adds this was inadvertantly added
to the beta. We are removing it so this will never appear.