Bug 204519 - Slow repainting of plasma desktop
Summary: Slow repainting of plasma desktop
Status: RESOLVED DUPLICATE of bug 197505
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: 2009-08-20 13:40 UTC by Miroslav Bendik
Modified: 2009-08-26 18:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miroslav Bendik 2009-08-20 13:40:54 UTC
Version:            (using Devel)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Compiled sources

While manipulating with windows, the performance of plasma is very slowly in comparision with another desktops. This video is showing a whole different performance behaviour between Plasma and KDesktop from KDE3: http://mireq.linuxos.sk/kde4/bugs/plasma_repaint.avi

System:
CPU: Intel Core2 Duo, 1.5GHz
RAM: 2GB
Graphics card: Intel X3100
X.org: 1.6.3
Mesa: 7.5
Intel drivers: 2.8.0
Kernel: 2.6.30
Comment 1 Beat Wolf 2009-08-20 15:29:42 UTC
I know there is a duplicate of that bug, but i can't find it (was it closed?)

I had the opinion back then that it is a driver problem, but i don't know what the conclusion was.

My laptop does not have this problem (nvidia card), but ive seen it in a kde installation that was running in virtualbox under windows.
Comment 2 Dario Andres 2009-08-21 16:37:18 UTC
I think your are talking about bug 197505.
Comment 3 Beat Wolf 2009-08-21 16:39:34 UTC
So do you agree to mark this as a duplicate?
Comment 4 Miroslav Bendik 2009-08-22 11:43:51 UTC
Yes, it seems to be the duplicate bug. But the problem is not only with intel drivers, but also with other open source drivers such as nvidia. When problems like this will be hold over, the KDE loose many of users.
Comment 5 Dario Andres 2009-08-26 18:19:34 UTC
Merging with bug 197505 Thanks

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