On Sat, 2008-04-05 at 04:22 -0500, Robert G. (Doc) Savage wrote: > On Sat, 2008-04-05 at 01:10 -0400, Ric Moore wrote: > > On Fri, 2008-04-04 at 20:39 -0600, dsavage@xxxxxxxxxxx wrote: > > > Does anyone know what would cause my Evolution client to suddenly lose its > > > ability to send/receive mail from my ISP? The "Send/Receive" button on the > > > upper tool bar is grayed out. So are the File -> Send/Receive and F9 > > > options. > > > > I've done that. Just look in the lower left hand corner and there is an > > icon that looks like two electrical plugs. If there is a red X between > > them, then it's in offline mode. Just click on it, and the plugs will > > close, putting you back into online mode, where you can send and receive > > stuff. I've done that more times than I can count! Embarrassing, > > especially after I raised hell on the list about evolution being > > broke. :) Ric > > Ahhh... That was it. The thorn in the paw of the lion. Thank you! (Why > on earth doesn't 'evolution --help-all' mention that little nugget?) A while back I complained on the Evolution list because suddenly Evo decided to start up in offline mode, even though I specifically requested it not to (via a Preference option). After some discussion it turned out that the problem was <drum roll .................> NetworkManager! I was running NM (without ever consciously deciding to -- it just ran without asking) but NM wasn't actually managing my wired connection, so it thought I wasn't connected. Evo took its word for it and thought "hmmm, he's not connected, better start up offline". It would sort itself out when I clicked the icon to go online, until the next time. The solution was to let NM manage the connection. I suppose an alternate solution would be to remove NM completely. I mention all this because it's a startling example of how two apparently independant universes (Evo and NM) interact. This is not a Good Thing (tm). poc
