On Sat, 29 Jan 2005 19:46:59 -0600, SkeeBall wrote:

> I still think it's something to do with libraries. I did the traceback and
> runlog as requested on the pan bug reporting page and added them to the bug
> so maybe they'll take a look at it.
>
> I used Arch Linux for a while and had the same problems on it after some
> updates - same with Slackware, worked fine and then *bam* something changed
> and it wasn't Pan itself. I don't know how to figure it out using the
> traceback and runlog but I'm hoping it helps the Pan developer(s).
>
> I have a spare box or two so maybe I'll put straight Slackware 10 on and see
> if that has problems - if I have time, maybe I can upgrade one thing at a
> time and see if I can figure out in a brute force way what breaks it.

Someone on the Pan mailing list thinks that the problem shows up with
newer versions of gtk+. I think he's on to something, because after I
downgraded my gtk+ from 2.6.1 to 2.4.3, the problem goes away. A couple of
others have reported the same thing.

Now my question is this: is the problem with Pan, or with gtk+?