Description of problem: When KDE has been up and running for some time, minimizing a window does not update the portion of the background that was occupied by the window (see attached screenshot). This is independent of the application the window belongs to. The only way to get the background back is to go change the background to something else and change it back. I have Intel 865G integrated graphics running at 1280x1024 on a 19" LCD display. Version-Release number of selected component (if applicable): kdebase-workspace-4.0.5-3.fc9.i386 How reproducible: Most of the time, once KDE has been up and running for some time and there are at least 3 to 4 windows. Steps to Reproduce: 1. Minimize the windows and check if the desktop background is alright Actual results: See attached screenshot Expected results: Additional info:
Created attachment 312456 [details] Screenshot of the mangled desktop background
I can confirm this, I've seen it happen myself. Unfortunately, that's all I know about this bug.
Hopefully, the KDE 4.1 updates that will be available soon will fix this problem. I still don't see 4.0.99 in updates-testing. Does anyone know when 4.1 will be available via updates? $ sudo yum -y update kdebase Loaded plugins: fastestmirror, refresh-packagekit Loading mirror speeds from cached hostfile * updates-testing: astromirror.uchicago.edu * livna: rpm.livna.org * fedora: mirror.steadfast.net * adobe-linux-i386: linuxdownload.adobe.com * updates: mirror.steadfast.net Setting up Update Process Could not find update match for kdebase No Packages marked for Update $
fyi, https://admin.fedoraproject.org/updates/F9/FEDORA-2008-6743
Thanks, is there a single group command with yum that I can use to get all of them?
yum --enablerepo=updates-testing update
I installed 4.0.99 and the problem seems to have almost resolved with it. However, some times, when a large window or a maximized window is minimized with many other windows also around, the screen stays garbled for usually 1-3 seconds after which it becomes fine. So, I've never noticed it last.
The problem still exists with 4.1.0-3, but clicking once on the background redraws it and cleares all the mangling. So the mangling is no longer irreversible.
The problem is not i386-specific, I've seen it on x86_64 too.
What video hw/driver are you using? (My hunch is that it is a driver issue). Oh, and are you using kwin/desktop-effects?
Nevermind, re-reading initial comment: Intel 845G Fwiw, Intel 945G here, cannot reproduce.
I see it with Intel GM965.
And it isn't always reproducible, it only happens sometimes (but relatively often).
I'm using Intel 865G (In reply to comment #10) > What video hw/driver are you using? (My hunch is that it is a driver issue). > > Oh, and are you using kwin/desktop-effects? I have Intel 865G integrated graphics. No, I'm not using desktop-effects. Enabling desktop effects crashes my KDE and takes me back to the login screen.
I do see this problem on my laptop with Intel Mobile GM965/GL960 controller. I do not see it on my PC with nVidia GeForce 7300 LE.
Thanks for the report. I checked upstream and could not find a matching bug.Please file a bug report in the the upstream bugzilla located at http://bugs.kde.org for the particular component involved. Once you've filed your bug report to the upstream bugzilla, please add the upstream info to this report. We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates. Setting status to NEEDINFO, and awaiting upstream bug report URL for tracking. Thanks in advance.
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance.