Description of problem: NetworkManager integration in Fedora 15 does not work. Version-Release number of selected component (if applicable): evolution-3.0.1-1.fc15.x86_64 NetworkManager-0.8.999-3.git20110526.fc15.x86_64 How reproducible: always Steps to Reproduce: 1. Start evolution 2. Disconnect from your network 3. Connect again Actual results: Nothing happens, evolution doesn't pick up the changes. Expected results: When disconnecting, evolution should go offline. When connecting again, it should go online and check for new mail.
Make sure evolution-NetworkManager is installed.
Could you check the suggestion from comment #1 and report back, please? Thanks in advance.
It works. But as app people upgrading will have this problem, I think needs to be documented, either in the release notes or at https://fedoraproject.org/wiki/Common_F15_bugs
I'm wondering whether there is any way of installing the evolution-NetworkManager by default, but do not depend on it, because the rationale behind this change was to allow people to not have in installed, because there are still occasions when the network manager cannot be used (I was told so).
It's already installed by default via comps, it just doesn't get pull in via "yum upgrade". I'm not aware of a good way to do that through rpm spec files.
Ah... thanks very much for this bugreport. Until now I thought Evolution in Fedora 15 is just broken. Does it mean it doesn't affact new installs of Fedora 15? Is there any way to fix it for people that don't know this and just think Fedora's Evolution package is screwed up, like I did?
I just installed evolution-NetworkManager and it works only partially. The good part is that it now react to NM connects. But the bad part is that on disconnect: 1) A yellow error message box appears with „Evolution is currently offline due to a network outage.“, which is plain false. There was no network outage at all, but intentional disconnect. 2) Evolution doesn't switch to offline mode before it realizes it's offline (that means, before the yellow box appears). It looks like it doesn't respond to NM disconnect at all!
Another example: Manually go to offline mode. Disconnect the network. Now evolution claims to go offline because there is no internet connection. This is wrong: It was already offline and it was offline because I told it so. When you go online again evolution still claims to be offline because the network was unreachable. From the moment the user tells evolution to go offline it should not care about NetworkManager any longer. It should not complain when MN goes offline and it should no longer complain or not automatically re-connect when NM goes online again. Basically what I want to see is the behavior of the evolution 2.x series. It worked perfectly.
Thanks for your ideas. Could we discuss these ideas in an upstream bugzilla (I can move it upstream for you, if you wish), because I do not feel like this being a Fedora issue, it's rather evolution issue, thus belonging to upstream bugzilla? The initial problem with not installed package was fedora specific, there is no doubt about it.
I have opened https://bugzilla.gnome.org/show_bug.cgi?id=655753 and added some more thoughts there.
Thanks. Thus this is kept opened only for the part of the evolution-networkmanager not being installed by default with "yum update", though, as mentioned in comment #5, it's possible it's not that easy to do.
Evolution NetworkManager integration works for me on Fedora 16.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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