Bug 158904 - Plasma panel painting problem
Summary: Plasma panel painting problem
Status: RESOLVED DUPLICATE of bug 158824
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-07 12:43 UTC by Alexey Chernov
Modified: 2008-03-07 20:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot on the bug (38.93 KB, image/png)
2008-03-07 12:46 UTC, Alexey Chernov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Chernov 2008-03-07 12:43:43 UTC
Version:            (using KDE 4.0.2)
Installed from:    Compiled From Sources
Compiler:          GCC 4.1.2 Target: x86_64-unknown-linux-gnu Configured with: ../gcc-4.1.2/configure --prefix=/usr --libexecdir=/usr/lib --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++ --disable-multilib Thread model: posix
OS:                Linux

I've recently switched to KDE 4.0.2 and noticed that plasma panel doesn't paint itself right as it has visual artifacts on left and right side (screenshot will be attached). This problem occurs only with compositing is on. When all the 'enable graphic effects' box is off, it's ok. I use NVIDIA GeForce 8600 card with proprietary drivers v. 169.09. I also have KWIN_NVIDIA_HACK=1, but i tried to unset it and there were no effect, the problem persisted.
Comment 1 Alexey Chernov 2008-03-07 12:46:41 UTC
Created attachment 23822 [details]
Screenshot on the bug
Comment 2 Sebastian Sauer 2008-03-07 19:16:09 UTC
Hi Alexey,

I am afraid to say, that this is a Qt-bug that got fixed in Qt4.4 which KDE4.1 will be based on. So, there is nothing we can do there for the 4.0.x-branch :-/

Thank you very much for your feedback!
Comment 3 Sebastian Sauer 2008-03-07 20:08:16 UTC
and just a second ago I did note, that there is another report that deals with that issue. So, let's go the correct way...

step 1 of 2: reopen the report
Comment 4 Sebastian Sauer 2008-03-07 20:08:43 UTC
step 2 of 2: mark it as dup of bug #158824 


*** This bug has been marked as a duplicate of 158824 ***