Bug 691676

Summary: Specto thinks it's offline with NetworkManager 0.9
Product: [Fedora] Fedora Reporter: Theodore Lee <theo148>
Component: spectoAssignee: Xavier Lamien <lxtnow>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: andrew.jones11235, jones.peter.busi, lxtnow
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-05 09:23:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 716256    
Bug Blocks:    
Attachments:
Description Flags
Gets Specto to use the NM 0.9 state values none

Description Theodore Lee 2011-03-29 08:49:37 UTC 
Description of problem:
After the NM 0.9 update, Specto doesn't seem to know when there's an Internet connection available. As a result, network watches don't work.

Version-Release number of selected component (if applicable):
specto-0.3.1-3.fc15.noarch

How reproducible:
This problem is consistently reproducible on Fedora 15, after updating to NM 0.9

Steps to Reproduce:
1. Connect to the Internet.
2. Start Specto.
3. Add watches for a few web pages in Specto.
4. Click 'Refresh All'.
  
Actual results:
None of the watches refresh, and a message in Specto's status bar explains that networked watches won't work without an Internet connection.

Expected results:
All of Specto's watches refresh, picking up any changes in the watched web pages.

Additional info:
I'm running NetworkManager-0.8.997-4.git20110325.fc15.x86_64
Comment 1 Theodore Lee 2011-04-05 04:17:25 UTC 
I think this is probably related to the new connection states in NM 0.9. Pidgin has a patch to handle them correctly[1], but after messing with spectlib/networkmanager.py I'm still not sure how to fix this.

[1] http://developer.pidgin.im/attachment/ticket/13505/nm09-pidgin.patch
Comment 2 Theodore Lee 2011-04-06 03:30:02 UTC 
Created attachment 490123 [details]
Gets Specto to use the NM 0.9 state values

I think I've got a working patch for this bug, based on the NM 0.9 D-Bus interface info[1]. Specto only works with NM 0.9 with this patch applied however - I haven't figured out how to detect which version of NM is running yet.

I've also filed this bug upstream[2], with the same patch attached.

[1] http://projects.gnome.org/NetworkManager/developers/migrating-to-09/spec.html#org.freedesktop.NetworkManager
[2] http://code.google.com/p/specto/issues/detail?id=327
Comment 3 Theodore Lee 2011-11-04 11:10:31 UTC 
Specto 0.4 has the complete fix for this bug.
Comment 4 Theodore Lee 2012-01-13 14:08:17 UTC 
*** Bug 781452 has been marked as a duplicate of this bug. ***