Description of problem: Evolution use NetworkManager to enable and disable send/receive functionality, but this doesn't work very well. For one thing, it completely ignores connections not managed by NetworkManager. And sometimes doesn't pick up when connected via NetworkManager Version-Release number of selected component (if applicable): All recent How reproducible: Steps to Reproduce: 1. Connect using some means other than NetworkManager Actual results: Unable to send/receive messages Expected results: Able to send/receive messages Additional info:
Created attachment 309344 [details] Screenshot showing disabled send/receive when clearly connected
The little icon in the bottom left corner indicates Evolution is in offline mode. Try clicking it to force Evolution into online mode, and I think the Send/Receive button should enable itself.
*** Bug 453279 has been marked as a duplicate of this bug. ***
Ah, thanks that did re-enable the send/receive button. Obviously Evolution got a disconnect event from Network Manager, so went offline, then didn't then pick up a reconnection. An easy way to show the behaviour is to: 1) Switch networks using Network Manager - sends Evolution into offline mode. 2) Close Evolution before Network Manager manages to connect. 3) Network manager connects. 4) Restart Evolution - will still be in offline mode, and will remain in offline mode until it is manually told to be in online mode. I think for some reason a similar series of events happened during a system update, which lead to my confusion. Thanks, Paul
I think I recall something like this getting fixed recently. What version of Evolution are you running? (rpm -q evolution)
I'm running evolution-2.22.2-2.fc9.i386.
Paul, any objection to me closing this or is there still an outstanding issue?
I think this sequence: 1) Switch networks using Network Manager - sends Evolution into offline mode. 2) Close Evolution before Network Manager manages to connect. 3) Network manager connects. 4) Restart Evolution - will still be in offline mode, and will remain in offline mode until it is manually told to be in online mode. still is an error, though I haven't checked. I think treating a network manager event the same as a request for offline mode is fundamentally flawed, and will continue to lead to bug reports like this. However, I would say this is an upstream issue, rather than something Fedora-specific. Just one of many things that don't work properly.
Evolution distinguishes Network Manager events from user-initiated offline mode while it's running, but only stores a single online/offline flag in GConf. That flag is used to decide the initial mode on the next startup. You're right, it needs to act smarter than that.
I'm seeing this problem in evolution-2.24.3-1.fc10 (Fedora 10 update as of Feb. 14).
Is still still a problem or is there a fix that can be done inside Fedora or closed and fixed upstream? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I haven't found a workaround yet. I upgraded to 2.24.5-1.fc10 and not only does it still insist on starting in offline mode, but the SSL connection to my ISP's SMTP server wouldn't work any more. I had to switch it to TLS.
Forget that comment about the SMTP connection. It must have been a glitch on the remote server. I just encountered the same error, and it worked again after switching back from TLS to SSL.
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Moving this to rawhide as I still mean to follow up on comment #9.
This is fixed now in Evolution 2.27.4.