For some years now, pan has been known not to get along well with the
gnome accessibility daemon (IDR what it's called, exactly), and ever
since we found out that was the problem, the recommendation has been to
turn it off, at least when running pan. But while that's the gnome
accessibility app, it seems nearly all reported issues with it have been
on ubuntu. I could speculate that ubuntu activates accessibility by
default, thus all the problem reports from there, but it's pure
speculation.
Anyway, it seems someone finally traced down the root problem -- it has
been a known issue with one of the gtk widgets (treeview), apparently,
there's a non-pan (rythmbox) bug on it too -- and has devised a
workaround patch for the problem.
The judgefudge/hmueller repo has the patch in it now, after pkovar ask
him to test it, but I'm not sure whether it's in khaley or the official
gnome repo (pkovar's bailiwick) yet, but as I said, pkovar's aware of it,
so it should hopefully hit with the next official release. =:^)
Here's the judgefudge git commit header; the comment being just a link to
the bug with the discussion and patch, which basically sets the treeview
widget that's triggering the issue to null while updating, thus avoiding
all that traffic over corba/dbus to the accessibility daemon (a11y, based
on the bugs):
commit 8e092ff555a6a156534d151d3fc1fccd05fe66b1
Author: Heinrich Müller<address@hidden>
Date: Mon Nov 28 12:43:05 2011 +0100
* https://bugzilla.gnome.org/show_bug.cgi?id=660030 (Jindrich
Makovicka)