Bug 47466 - nautilus setup druid network doesn't mention failures
nautilus setup druid network doesn't mention failures
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: nautilus (Show other bugs)
7.3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Mason
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-07-05 13:05 EDT by Telsa Gwynne
Modified: 2007-04-18 12:34 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-07-05 13:05:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Telsa Gwynne 2001-07-05 13:05:37 EDT
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 13:41:21 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.