> I get it most (75%+) of the time. The workround is to find the process
> using top and then attach gdb to it!
> This means you can't use evolution, but it gives you your computer
> back..
Or to issue (from a terminal in the X session):
evolution --force-shutdown
Or to simply (not really that different) kill the offending process.
The weirdest of it all is that most people have this behaviour once in
a long while, and Caroline has it most of the time (and, as she told me,
while she was already connected to a PPP session). Hum. Network-Manager
does not really work or recognise PPP as a network connection. Hum.
It may well be that something related to network, or its absence, plays
a role here, but we have been unable to identify what/how.
All I can see from the backtraces is that E-D-S itself is looping *very*
early in the E-D-S startup... so early that I wonder if this is a Evo
issue, or Gnome.
Anyway, once you stop it, everybody (so far) reports it can be restarted
without being hit by the loop.
> I get it most (75%+) of the time. The workround is to find the process
> using top and then attach gdb to it!
> This means you can't use evolution, but it gives you your computer
> back..
Or to issue (from a terminal in the X session):
evolution --force-shutdown
Or to simply (not really that different) kill the offending process.
The weirdest of it all is that most people have this behaviour once in
a long while, and Caroline has it most of the time (and, as she told me,
while she was already connected to a PPP session). Hum. Network-Manager
does not really work or recognise PPP as a network connection. Hum.
It may well be that something related to network, or its absence, plays
a role here, but we have been unable to identify what/how.
All I can see from the backtraces is that E-D-S itself is looping *very*
early in the E-D-S startup... so early that I wonder if this is a Evo
issue, or Gnome.
Anyway, once you stop it, everybody (so far) reports it can be restarted
without being hit by the loop.