Hide Forgot
Description of problem: Specto never checks the state of its monitored sites Its status bar permanently indicates: "The network connection seems to be down, networked watches will not check until then." Version-Release number of selected component (if applicable): Specto 0.3.1 Network Manager 0.9.2 How reproducible: 100% Steps to Reproduce: 1. Launch specto 2. Define some locations to monitor if none exist already Actual results: Status bar permanently indicates: "The network connection seems to be down, networked watches will not check until then." Expected results: Specto accesses entered locations to save original content / check for differences Additional info: see below an extract of the output of grep NetworkManager /var/log/yum.log Oct 08 23:21:35 Updated: 1:NetworkManager-glib-0.8.5.92-1.git20110927.fc14.i686 Oct 08 23:22:05 Updated: 1:NetworkManager-0.8.5.92-1.git20110927.fc14.i686 Oct 08 23:25:22 Updated: 1:NetworkManager-gnome-0.8.5.92-1.git20110927.fc14.i686 Dec 13 09:33:29 Erased: 1:NetworkManager-gnome-0.9.2-1.fc16.i686 Dec 13 09:41:30 Erased: 1:NetworkManager-vpnc-0.9.0-1.fc16.i686 Dec 13 09:41:35 Erased: 1:NetworkManager-pptp-0.9.0-1.fc16.i686 Dec 13 09:42:31 Erased: 1:NetworkManager-openvpn-0.9.0-1.fc16.i686 Dec 13 09:47:34 Erased: 1:NetworkManager-gtk-0.9.2-1.fc16.i686 Dec 13 09:48:27 Erased: NetworkManager-openconnect-0.9.0-3.fc16.i686 Dec 13 14:49:10 Installed: 1:NetworkManager-gtk-0.9.2-1.fc16.i686 Dec 13 14:49:33 Installed: 1:NetworkManager-gnome-0.9.2-1.fc16.i686 Dec 13 14:49:43 Installed: 1:NetworkManager-openvpn-0.9.0-1.fc16.i686 Dec 13 14:49:47 Installed: 1:NetworkManager-pptp-0.9.0-1.fc16.i686 Dec 13 14:49:49 Installed: 1:NetworkManager-vpnc-0.9.0-1.fc16.i686 Dec 13 14:49:54 Installed: NetworkManager-openconnect-0.9.0-3.fc16.i686 The last change recorded by my Specto installation was on December 12th I found this relation because it has already been discussed on the specto forum https://code.google.com/p/specto/issues/detail?id=327 It implies the upstream is already fixed so hopefully just needs to be packaged for the Fedora repository
This looks to be the same as bug 691676 - as far as I can tell the fix has been built but not yet pushed out. *** This bug has been marked as a duplicate of bug 691676 ***