GNOME Bugzilla – Bug 45582
Can't browse web or FTP if disconnected when nautilus starts
Last modified: 2004-12-22 21:47:04 UTC
I can't browse the web or FTP with nautilus if I connect to the web after Nautilus is started. I'm still using a dial-up modem and this is annoying because I have Nautilus automatically start when I log in and after that I connect to the internet at which point I have to restart Nautilus in order to browse with it. I get a "Can't display location" error dialog when I try. ------- Additional Comments From eli@eazel.com 2001-01-12 09:37:20 ---- *** Bug 45583 has been marked as a duplicate of this bug. *** ------- Additional Comments From mikef@praxis.etla.net 2001-01-12 13:32:49 ---- I have absolutely no idea why this might be.... ------- Additional Comments From kfv101@psu.edu 2001-01-13 10:12:13 ---- Don't know if this helps, but evolution does the same thing. Perhaps this is a gnome-vfs thing - isn't that how both applications do their network queries? ------- Additional Comments From don@eazel.com 2001-01-14 22:21:02 ---- This is heinous and I would like to fix it for 1.0. Putting on that milestone until I can see how bad this is compared to some of our other mozilla bugs ... ------- Additional Comments From mikef@praxis.etla.net 2001-01-15 18:29:22 ---- kfv's description of the bug makes it sound like perhaps a problem with his network configuration...esp if it happens to evolution too. (kfv--AFAIK, evolution does not use gnome-vfs for most of its network activity, so its probably something else.) ------- Additional Comments From kfv101@psu.edu 2001-01-17 18:14:21 ---- A little more poking around - This problem happens with galeon and gftp also, however with a slight twist. If I start those apps up but don't try to go to a web page or ftp site they will later work when I dial in. If I do try to go to a web site before I have dialed in, then the applications will not work afterwards. Old Netscape 4.7 does not exhibit any of these behaviors so I don't think it is a setup problem for me. I only really notice this with nautilus since I have it start at login to manage the desktop ------- Additional Comments From mjs@noisehavoc.org 2001-01-26 03:50:51 ---- I suspect it's a DNS issue. I've seen other apps have similar problems where once a DNS lookup fails for lack of connection, they are scrod forever. kfv: do you get this if you try to browse to sites by IP address? ------- Additional Comments From kfv101@psu.edu 2001-01-26 04:55:39 ---- Exactly right mjs. Both web and ftp work if I type in the ip address. ------- Additional Comments From mjs@noisehavoc.org 2001-01-30 16:24:00 ---- We think this might be fixable later, but since this DNS problem comes up for many other apps, I don't think Nautilus has to do a better job than these other apps for 1.0. ------- Additional Comments From kfv101@psu.edu 2001-03-08 16:37:39 ---- Okay, I just learned tonight that this IS a problem with my dial-up application. I use xisp and it was doing something funny with /etc/resolve.conf. Putting in the proper DNS entries has fixed the problem. I suspect then that this would be a very uncommon problem and might not be worth fixing. ------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 20:51 -------
Changing to "old" target milestone for all bugs laying around with no milestone set.
I'm fairly certain this is still relevant. There is an active bug on mozilla http://bugzilla.mozilla.org/show_bug.cgi?id=63564 that deals with the same issue. I have no way to test this as i'm on a cable modem, but i'm fairly certain it's still a problem, Probably should mark gnome2 and needinfo.
Verified in 2.0.7: Start gnome/nautilus with an invalid resolv.conf file. Nautilus won't access web/ftp sites. Create a valid resolv.conf file. In the *same* nautilus window that you tried to access a web/ftp site with, try again. It will still fail. At this point, I got mixed behaviour - I believe there were some cases where I could get new windows to access web/ftp sites and other times when I couldn't (and would have to restart nautilus) in order to get them to work. The solution (like borodley mentions) will be to re-read resolv.conf (see http://bugzilla.gnome.org/show_bug.cgi?id=45582 for a discussion regarding this issue in mozilla). Adding GNOME2 keyword.
Changing priority to low and severity to minor
Old bug alert. Is this still a problem? I can't reproduce using the resolv.conf method. Closing as FIXED.