1i5t5.duncan at cox
Aug 7, 2009, 4:31 PM
Post #2 of 2
Theo Chatzimichos <tampakrap [at] gentoo> posted
200908072307.28361.tampakrap [at] gentoo, excerpted below, on Fri, 07 Aug
2009 23:07:28 +0300:
> Since all packages were keyworded properly and bug 280312 doesn't affect
> amd64 architecture, we unmasked it for amd64. Thanks to the amd64 Arch
> Team for permitting us.
> Also the Gentoo KDE Guide  is properly updated with
> steps, and upgrade troubleshooting tips.
Thanks. I'm running it, and tonite after sync I can move the kde.unmask
file out of package.unmask and verify. =:^)
FWIW, I've still some bugs, but they were all there with 4.2.4 as well,
and appear to be upstream. 4.3.0 fixed several of them, and otherwise
seems faster and more stable. =:^)
The most irritating bug has been a multi-pronged beast that has already
had several prongs fixed upstream, but still appears here. It's the
infamous kde (including plasmoids, not just konqueror) doesn't connect
well to local proxies bug, timing out immediately (well before the
timeout settings). For konqueror I have a bookmark set for the proxy
config itself (privoxy toggle), and going to it directly works, after
which I can hit the back button and it'll normally load (or at least
partially load) the site I'm after. If set it to connect direct, it
works fine, but (when it's using the proxy) it just doesn't seem to see
the proxy on a new connection until I visit the proxy itself, after which
it knows it's there and sort of works, tho I still have to do a lot more
refreshing than usual.
As I said, there's multiple bugs on this filed upstream, with, it
appears, dozens of dups. Several prongs of the bug were traced and fixed
and it appears fixed the problem for some, but I still have it. Since I
just started seriously running kde4 (which I've had installed since the
pre-4.0 rcs), and I knew 4.3.0 was coming out soon and that several
prongs of the bug had been fixed even before 4.2.4, I waited until 4.3.0
and haven't yet filed my own bug on it.
Do you know if there are still active versions of this bug being
tracked? After about 10 similar symptom bugs, I quickly became confused
trying to sort the already fixed prongs and dups from any remaining
active ones. If there's still open activity, I'll not file a new one and
would prefer to CC the appropriate open bug, but if not, I need to open
one right away, and hopefully work with them to trace the problem down
and get this prong fixed for 4.3.1.
Also, any idea which bits of kde and dependencies I should compile with
debugging, etc, and suggested debugging flags? It'll be much simpler if
I have at least part of it done before I actually file the (or CC an
active) bug. I assume at least kdelibs... probably qt, which
components?, probably konqueror for tracing altho it's bigger than
firefox and kde3 don't have the issue, and if I set it to connect direct,
kde doesn't either, but thru the proxy it does. But I use the proxy for
junk filtering, etc, so need it.
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