Hello Ralf,
Fedora 18 ships with Evo 3.6.4.
This combination is very stable for me. The only crashes I have are when
Evolution is open for 6 or more weeks. I receive a lot of e-mail and
restarting Evolution is required after a couple of weeks. Otherwise the
mail client works well for me.
HTH
Th
Hi All,
I was facing similar issues of evolution timeout. My Evolution version was
3.10.2 from git source. Even I have observe that evolution was throwing
timeout very intermittently. Thus I have decided to investigate it further.
I could find that eds has implemented a "camel-network-service" whi
> >
> > Almost certainly from your network stack; and my $$$ would be on your
> > ISP/customer router.
> >
> So it's this way?
> -the router (Linksys WRT350N) is creating the time out (or something
> else in the "subsystem")
> -it aborts the mission and somehow signals Evolution, which then pops
On Sat, 2013-11-30 at 17:13 -0500, Adam Tauno Williams wrote:
> On Sat, 2013-11-30 at 11:49 -0500, Eric Beversluis wrote:
> > On Mon, 2013-10-28 at 11:00 -0400, Adam Tauno Williams wrote:
> > > On Mon, 2013-10-21 at 18:58 -0400, Eric Beversluis wrote:
> > > > I now have Evo 3.8.5 on Fedora 19. So e
On Mon, 2013-10-28 at 11:00 -0400, Adam Tauno Williams wrote:
> On Mon, 2013-10-21 at 18:58 -0400, Eric Beversluis wrote:
> > I now have Evo 3.8.5 on Fedora 19. So everything's up to date in Kansas
> > City. The problem persists. I'm doing 'send/receive' on three accounts,
> > all the same domain,
