@Markus Birth, from your description it seems you have a different bug.
Besides, I can confirm the bug in this report has been fixed.
If it was not an incident and you can reproduce the bug, you should try
to find a bug report that is identical to yours, or else submit a new
bug report.
--
You
It never really hung for me. What happened was that the ubiquity tread
used all the CPU it could get and start eating up all the memory. After
almost an hour of unresponsiveness the last bit of memory and swap was
gobbled up and the ubiquity thread was killed (by 'kswap0' or something
with a
2 matches
Mail list logo
