Bug 113691

Summary: weather applet looses connectivity after system moved to a different network (DHCP in both locations)
Product: [Fedora] Fedora Reporter: Norbert Roma <norbert>
Component: gnome-vfs2Assignee: Jonathan Blandford <jrb>
Status: CLOSED UPSTREAM QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 1CC: alex, ddumas
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-08-04 08:36:11 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 Norbert Roma 2004-01-16 16:06:29 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114

Description of problem:
The weather applet in the panel looses connection to the weather
server after the system (laptop) is moved from one private netowrk,
say 192.168.2.0/24, (bhind a NAT firewall) to another private subnet,
say 10.100.0.0/24 (behind another firewall).  All other components
retain full network connectivity on both networks.  The applet works
on both networks when located on the network that it was connected to
when first started (ie, it will work when first started in either
location, and it will resume working when brought back to the original
location after having been elsewhere).


Version-Release number of selected component (if applicable):
weather report 2.4.1 (gnome-applets-2.4.1-1)

How reproducible:
Always

Steps to Reproduce:
1.Log in and make sure you have the applet in the panel.
2.Disconnect from your network
3. Connect to a different network and try to update the weather report
    

Actual Results:  Reports "Retrieval failed" in step 3 above

Expected Results:  Should report weather conditions

Additional info:

Comment 1 Mark McLoughlin 2004-07-19 13:48:46 UTC
Do you still see this problem with Fedora Core 2?

Comment 2 Alex Lancaster 2004-07-29 11:31:27 UTC
I still get this problem in Fedora Core 2 (with updates).  It seems to
be related to this upstream bug, which has been open since March 2002!

http://bugzilla.gnome.org/show_bug.cgi?id=76283

Comment 3 Mark McLoughlin 2004-08-04 08:33:16 UTC
Okay, seems to be a gnome-vfs bug - moving there, but closing as
resolved UPSTREAM.

Comment 4 Mark McLoughlin 2004-08-04 08:35:37 UTC
The fix is in gnome-vfs 2.7.90 and, as such, will appear soon in FC3.