Greetings,
I recently upgraded to 1.2.0 from 1.0.8. I'm noticing an annoying
problem where if I start evolution after a system reboot, close it and
try to re-open it, it takes about 5 minutes to re-open. The splash
screen comes up, no cpu/mem/hdd activity can be seen and the splash
scree
On Wed, 2002-12-04 at 10:12, Jason Lixfeld wrote:
> Greetings,
>
> I recently upgraded to 1.2.0 from 1.0.8. I'm noticing an annoying
> problem where if I start evolution after a system reboot, close it and
> try to re-open it, it takes about 5 minutes to re-open. The splash
> screen comes
No, it doesn't.
On Wed, 2002-12-04 at 15:46, Mark Gordon wrote:
> On Wed, 2002-12-04 at 10:12, Jason Lixfeld wrote:
> > Greetings,
> >
> > I recently upgraded to 1.2.0 from 1.0.8. I'm noticing an annoying
> > problem where if I start evolution after a system reboot, close it and
> > try to r
One other thing I should mention now realize I failed to do is that it
only happens after the system has been suspended and resumed.
If I start evolution after a reboot, i can shut it down and open it up
no problem. If I suspend the machine and resume it again, that's when
it has the pause (aswel
It may be worth starting various components in terminal windows, as well
as the shell, in order to figure out from their output what's having
problems.
-Mark Gordon
On Wed, 2002-12-04 at 16:06, Jason Lixfeld wrote:
> No, it doesn't.
>
> On Wed, 2002-12-04 at 15:46, Mark Gordon wrote:
> > On Wed,
Good idea. Will try that.
Did you get my previous msg about the fact that it happens only after
suspend (like right now it's happening :) )? Does that help any?
In the meantime, I'll give the terminal window thing a whirl.
On Wed, 2002-12-04 at 16:22, Mark Gordon wrote:
> It may be worth start
It's been suggested that perhaps you have a bad /tmp/orbit-
directory. If you exit X and rm -rf that directory from the console,
that may fix your problem.
-Mark Gordon
On Wed, 2002-12-04 at 16:09, Jason Lixfeld wrote:
> One other thing I should mention now realize I failed to do is that it
> on
I got the message. I don't know why suspending would cause problems.
-Mark Gordon
On Wed, 2002-12-04 at 17:02, Jason Lixfeld wrote:
> Good idea. Will try that.
>
> Did you get my previous msg about the fact that it happens only after
> suspend (like right now it's happening :) )? Does that he