Evolution not aware of network changes
Bug #151316 reported by
Matthew Tighe
This bug report is a duplicate of:
Bug #19388: Evolution hang (hibernate/network interface/subnet change?).
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| evolution (Ubuntu) |
Invalid
|
Low
|
Ubuntu Desktop Bugs | ||
Bug Description
Evolution has some great speed improvements for Exchange connectivity in this version, but there is still a big issue with detecting network connectivity changes, even before running the client.
Evolution launches some background processes on startup. Firing up a VPN client and then the client module causes the background processes not to be able to find the exchange server. I have worked around this be creating a script that kills the running processes and then fires up the client (which relaunches the background processes). However, I think evolution should be able detect these changes without killing and restarting (which is really a kludge).
Revision history for this message
| Sebastien Bacher (seb128) wrote | #1 |
| Changed in evolution: | |
| assignee: | nobody → desktop-bugs |
| importance: | Undecided → Low |
| status: | New → Invalid |
To post a comment you must log in.
Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.