Comment 16 for bug 151536

@Anton Kudris: after you find yourself in such a situation, find out the pid of the offending process, and run:

gdb -p <pid> # where <pid> is the pid you found above

once in gdb, issue "thread apply all bt full" -- this will dump the backtraces for all threads.

So far I have been unable to reproduce it, or to make sense of the stacktraces we have collected so far. Perhaps it would help to go into some cycles of (interrupt, dump stacks, continue), to see if we can dig into whatever is causing this. Still, this seems to happen very early in e-d-s startup.

No matter what, the backtraces will only have value if the debug packages (either the dbgsym or dbg) for e-d-s (*all* of them), glib, libc6, and libbonobo (at least) are installed.