Bug#452162: hmmm... solved but maybe it's still a bug?
andrew at farwestbilliards.com
Sun Nov 25 20:14:58 UTC 2007
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
Also, the gnumeric problem appears to be completely unrelated.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20071125/85965121/attachment.pgp
More information about the pkg-gnome-maintainers