1 |
On Fri, May 1, 2009 at 3:26 PM, Andrew Gaydenko <a@××××××××.com> wrote: |
2 |
> On Saturday 02 May 2009 00:11:50 Paul Hartman wrote: |
3 |
>> On Fri, May 1, 2009 at 2:49 PM, Andrew Gaydenko <a@××××××××.com> wrote: |
4 |
>> > There is a shot of my screen (1.4MB, look at bottom and right panels): |
5 |
>> > |
6 |
>> > http://gaydenko.com/tmp/shot01.png |
7 |
>> > |
8 |
>> > which I get periodically after few hours working under KDE - at some |
9 |
>> > moment crazy things happen :-) There is very long software chain from |
10 |
>> > kernel video driver (intel in my case for on-board G965) to KDE4 itself |
11 |
>> > (~amd64). As a result, I'm not sure where to dig in. |
12 |
>> > |
13 |
>> > Has anybody ideas about a reason of such "beauty" panels? :-) |
14 |
>> |
15 |
>> I had very similar screen corruption when using NX with KDE4. Recently |
16 |
>> when I changed to Qt live ebuilds from qting-edge overlay with the |
17 |
>> "qt-copy" USE flag enabled, these corruptions went away. |
18 |
> |
19 |
> Thanks, I'll try! |
20 |
> Have you noticed any side-effects after adding qting-edge to overlays? |
21 |
|
22 |
Only good side-effects. GUI performance in NX is _much_ faster, and |
23 |
all of the corruption problems are completely gone. It used to a lot |
24 |
of unnecessary redraws which seems to be gone now, too. I have seen no |
25 |
bad side-effects so far. |
26 |
|
27 |
But it is using CVS Qt code so your experience may differ based on the |
28 |
hour or the day that you emerge. :) |