Comment 22 for bug 395190

It would be useful for other people who experience this problem to post thread stacktraces, so we can confirm similar behaviour.

Again, for those who didn't notice the first time: to do this, you should log in, confirm that Do is exhibiting this behaviour, then issue the command: "killall -SIGQUIT gnome-do" in a terminal. This will drop a stacktrace into ~/.xsession-errors, which you should attach here.

Don't do this after you've been logged in for a long time; the xsession-errors logfile will only grow to a certain size, then ignore everything else. If it's already too big, the stacktrace won't be included.