GNOME Bugzilla – Bug 485801
"evolution --online" does not work, still offline
Last modified: 2009-06-24 07:18:47 UTC
If the program is ever exited with work-offline selected, there is no way to change it back to start up with work-online. This is not documented and this is not acceptable. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1
of course there is and it IS documented in the user documentation. you just start it with "evolution --online".
Not true. Adding --online to the command in the main menu of ubuntu 7.04 has no effect. Evolution simply will not start up on line. This is not resolved, this is a bug.
hmm, my command here (fedora 7) to start evo 2.12 is "/home/andre/opt-gnome/bin/evolution --online" and it works perfectly after quitting evolution in offline mode... so you have to choose "file -> work online" everytime after starting evolution? strange. i haven't heard of this problem before. if you close evolution in offline mode, and then explicitly start evolution by opening a gnome-terminal window and entering "evolution --force-shutdown" and then "evolution --online" there, does it work?
Correct. Regardless of how it is started, it will not ever come up on line and start receiving mail. Every time, I either have to click File->Work Online, or click the broken pipe icon in the lower left. Whether I start it from a command line, from the menu or from browsing to the executable and double clicking it.
i wonder if evolution gathers the network state from NetworkManager, perhaps there is a bug in the communication so Evolution always receives an "offline" from NetworkManager when getting started. just a wild guess though, perhaps somebody in an ubuntu forum has a better idea. :-/
I can confirm this. The problem is NetworkManager is running but not connected, cause not used for wired connections. Evolution asks then for the status and gets: dude we are offline - and Evolution takes this as truth. --online should override the stupid assumption of NetworkManager. see also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447167
Bug 518103 should help
Could you please confirm if this bug is still happening at your end ? Please try in 2.24.x / 2.26.x and report back, thanks.
Thanks for taking the time to report this bug; however, closing due to lack of response of the reporter, sorry. if you still see this issue with a current release of evolution (2.26.2 or later), please reopen. thanks in advance.