| 1 |
Theo Chatzimichos <tampakrap@g.o> posted |
| 2 |
200908072307.28361.tampakrap@g.o, excerpted below, on Fri, 07 Aug |
| 3 |
2009 23:07:28 +0300: |
| 4 |
|
| 5 |
> Since all packages were keyworded properly and bug 280312 doesn't affect |
| 6 |
> amd64 architecture, we unmasked it for amd64. Thanks to the amd64 Arch |
| 7 |
> Team for permitting us. |
| 8 |
> Also the Gentoo KDE Guide [1] is properly updated with |
| 9 |
> installation/upgrade |
| 10 |
> steps, and upgrade troubleshooting tips. |
| 11 |
> |
| 12 |
> [1]http://kde.gentoo.org/kde4-guide.xml |
| 13 |
|
| 14 |
Thanks. I'm running it, and tonite after sync I can move the kde.unmask |
| 15 |
file out of package.unmask and verify. =:^) |
| 16 |
|
| 17 |
FWIW, I've still some bugs, but they were all there with 4.2.4 as well, |
| 18 |
and appear to be upstream. 4.3.0 fixed several of them, and otherwise |
| 19 |
seems faster and more stable. =:^) |
| 20 |
|
| 21 |
The most irritating bug has been a multi-pronged beast that has already |
| 22 |
had several prongs fixed upstream, but still appears here. It's the |
| 23 |
infamous kde (including plasmoids, not just konqueror) doesn't connect |
| 24 |
well to local proxies bug, timing out immediately (well before the |
| 25 |
timeout settings). For konqueror I have a bookmark set for the proxy |
| 26 |
config itself (privoxy toggle), and going to it directly works, after |
| 27 |
which I can hit the back button and it'll normally load (or at least |
| 28 |
partially load) the site I'm after. If set it to connect direct, it |
| 29 |
works fine, but (when it's using the proxy) it just doesn't seem to see |
| 30 |
the proxy on a new connection until I visit the proxy itself, after which |
| 31 |
it knows it's there and sort of works, tho I still have to do a lot more |
| 32 |
refreshing than usual. |
| 33 |
|
| 34 |
As I said, there's multiple bugs on this filed upstream, with, it |
| 35 |
appears, dozens of dups. Several prongs of the bug were traced and fixed |
| 36 |
and it appears fixed the problem for some, but I still have it. Since I |
| 37 |
just started seriously running kde4 (which I've had installed since the |
| 38 |
pre-4.0 rcs), and I knew 4.3.0 was coming out soon and that several |
| 39 |
prongs of the bug had been fixed even before 4.2.4, I waited until 4.3.0 |
| 40 |
and haven't yet filed my own bug on it. |
| 41 |
|
| 42 |
Do you know if there are still active versions of this bug being |
| 43 |
tracked? After about 10 similar symptom bugs, I quickly became confused |
| 44 |
trying to sort the already fixed prongs and dups from any remaining |
| 45 |
active ones. If there's still open activity, I'll not file a new one and |
| 46 |
would prefer to CC the appropriate open bug, but if not, I need to open |
| 47 |
one right away, and hopefully work with them to trace the problem down |
| 48 |
and get this prong fixed for 4.3.1. |
| 49 |
|
| 50 |
Also, any idea which bits of kde and dependencies I should compile with |
| 51 |
debugging, etc, and suggested debugging flags? It'll be much simpler if |
| 52 |
I have at least part of it done before I actually file the (or CC an |
| 53 |
active) bug. I assume at least kdelibs... probably qt, which |
| 54 |
components?, probably konqueror for tracing altho it's bigger than |
| 55 |
konqueror itself. |
| 56 |
|
| 57 |
firefox and kde3 don't have the issue, and if I set it to connect direct, |
| 58 |
kde doesn't either, but thru the proxy it does. But I use the proxy for |
| 59 |
junk filtering, etc, so need it. |
| 60 |
|
| 61 |
-- |
| 62 |
Duncan - List replies preferred. No HTML msgs. |
| 63 |
"Every nonfree program has a lord, a master -- |
| 64 |
and if you use the program, he is your master." Richard Stallman |
Archives