Why I consider this behaviour wrong: When I set a program offline, be it Evolution, Gnus, Opera, or any other network application, it means "go offline and stay that way because I know better than you when it's time to switch you online again".
If you look at bug #120730 you will see that Evolution gets terribly confused if it's switched online, before it can connect to the server, and the only way to unconfuse it is to kill it, including all server processes, open a VPNC connection, and start it again. This gets tedious if I just wish to switch from wired LAN to WLAN in my house, without Evolution going online at all. I want it to run, and run in offline mode, so that I can read cached email messages. I don't want it to go online, be confused, have to be killed, open a VPNC connection, start Evolution, switch it offline, close the VPNC connection, just to be able to read the cached email again. And in any case, this is new behaviour with the Evolution distributed with Feisty. The Evolution distributed with both Breezy and Dapper, stayed offline until I switched it online. I used network-manager with Dapper, and it didn't affect Evolution at all (nor should it). -- Evolution doesn't remember online/offline mode in Feisty https://bugs.launchpad.net/bugs/120728 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
