pan-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Pan-users] Pan crashes on every reply sent.


From: Duncan
Subject: Re: [Pan-users] Pan crashes on every reply sent.
Date: Sat, 10 Dec 2011 18:45:40 +0000 (UTC)
User-agent: Pan/0.135 (Tomorrow I'll Wake Up and Scald Myself with Tea; GIT 5a56aa9 /st/portage/src/egit-src/pan2)

fredbezies posted on Sat, 10 Dec 2011 16:22:36 +0100 as excerpted:

> I will suscribe and report the problem. Thanks for the tip ;)

Well, what I was trying to say is that since the problem was posted here 
already, that should be enough (no need to repost there), and indeed, 
post to whichever list you want when it's a git issue... just that you 
might want to subscribe there too, in ordered to keep up with 
developments that might be posted to only one list or the other, not both.

An example would be hmueller's announcement that this pan tree, formerly 
on github as judgefudge/pan2, was now moved to the official gnome pan 
repo, as the testing branch.  Originally he posted that announcement to 
the dev list only... and a few days later we had someone asking here what 
happened as he couldn't reach the judgefudge repo on github any longer.  
Several answers pointed him at the new gnome repo, testing branch, but 
had he been following both lists, he'd have known that already, as he'd 
have seen the announcement on the dev list.

So my point was, follow both if you're doing live-git builds, so as to 
avoid missing stuff like that.  But you can post to either group (well, 
list, but it's newsgroup to those like me reading it on gmane).

But I guess I didn't get that clearly conveyed and you posted there too, 
which is fine as well, just a bit of unnecessary duplication.


Oh, BTW, you mentioned that you're running gnome3, so of course have gtk3 
and perhaps built pan against that instead of gtk2.  It's worth noting 
that while the pan gtk3 support code is there and it's possible to build 
pan against gtk3, that's rather less stable and tested than the gtk2 
code.  So unless you want to specifically test the gtk3 code, it's 
recommended that you build against gtk2 instead, at this point.  It'll be 
more stable.  It's possible that's what was triggering your crashes.  

FWIW, I don't have gtk3 on my system at all, only gtk2.  I expect things 
to get interesting when firefox builds against gtk3 as well as it does 
against gtk2, as at that point the pressure will be on to get everything 
else switched over to gtk3 as well, but until firefox switches, that's 
not going to happen so there's little pressure for anything else.  And 
last I checked probably a couple months ago, firefox had some major work 
to do before it was fully gtk3 compatible.  Perhaps sometime next year, 
which means that by 2H2012 the pressure could be building for other apps 
as well, and leading edge distros will likely be starting to drop gtk2-
only apps in 2013, but I don't seriously expect it much before that.


-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




reply via email to

[Prev in Thread] Current Thread [Next in Thread]