Okay, I've narrowed this down to a problem in .gconf. After playing around with some other machines and upgrading various packages trying to find this, I ended up with another machine fully up-to-date but *without* the problem.
I went back to step zero. This problem showed up after a segfault in gnucash. This segfault occurred while printing checks (uses gtkprint). Subsequent instances of gnucash could no longer print checks. Since I had two machines fully-up-to-date. I decided to try a different user on the broken machine. lo and behold, no problem. :( or :) depending on your perspective. Anyway, moving ~/.gconf out of the way solved the problem. Clearly, the segfault corrupted something in ~/.gconf/* resulting in this behavior. There is probably no way to track down the segfault as it happened in an instance of gnucash that may have been up for many days and may have been up across a variety of upgrades... I have a copy of the problematic ~/.gconf available if you would like. Also, the gnumeric problem appears to be completely unrelated. A
signature.asc
Description: Digital signature
_______________________________________________ pkg-gnome-maintainers mailing list pkg-gnome-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-gnome-maintainers
