GNOME Bugzilla – Bug 511769
[KB-Fixed] Poor indication of when network is unavailable
Last modified: 2009-08-30 05:53:17 UTC
Please describe the problem: Versions 2.12.2 and 2.12.13 on Fedora 8 start up in offline mode whereas earlier versions didn't. The shell command is "evolution --component=mail --disable-preview". There appears to be no GUI-level preference option for changing this. Using gconf-editor the apps->evolution->shell->start_offline toggle is unchecked. I've tried it in both positions and the behaviour is the same. Steps to reproduce: 1. Run Evo 2. Notice that it starts Offline 3. Hit the icon in the lower left corner to go online Actual results: Starts offline Expected results: Start online Does this happen every time? Yes Other information: Used to work correctly on every previous version I can remember.
does it work when starting with "-- online"?
No.
Solved. The problem was that NetworkManager thought I was offline when in fact I wasn't. My network config didn't have the "managed by NetworkManager" box checked. This is of course a bug in NM. If it doesn't manage an interface it should just shut up about it. If it doesn't manage any interfaces (as in my case) it shouldn't even be running. However it's *also* a usability bug in Evo. Evo thought I was offline, but allowed me to go online without complaint. If it had said "NM thinks you are offline, are you sure?" I would have spotted the problem a lot sooner.
Bumping version to a stable release.
Fixed on the kill-bonobo branch in: http://git.gnome.org/cgit/evolution/commit/?h=kill-bonobo&id=473f8dca644b3f9f48529daeed44de2097ee311d If NetworkManager things you're offline, the connection button in the lower left corner as well as the File -> Work Online/Offline menu item is grayed out. As I've said before, I still want a noticable banner in the main window that says you're working offline. But this is a marginal improvement.
The "kill-bonobo" branch has been merged into "master" and will debut as Evolution 2.29.1. We believe the branch has addressed the reported issue. If you find the issue still exists in version 2.29 or later please feel free to re-open this bug. Closing as FIXED.