Version: (using KDE 4.0.83) Installed from: Ubuntu Packages On kde startup, during desktop initialization, it is showed a garbage image. That image reproduces the desktop as it was right before the last system shutdown.
exactly on what stage it appears? as the first thing before even starting the splash screen right? there are good chances it's a video driver problem
The splash screen runs without problems until the desktop icon is displayed. Right after that the whole splash screen is replaced by the garbage image. That image remains on the screen for a "moment" than the splash screen reappears right before the kde icon becomes to be visible. My graphics card is an Ati Radeon Mobility 9200 with the open source Ati driver.
this is with kwin's desktop effects turned on? if so, then this is activation of those effects, and this report should be re-assigned to kwin.
Aaron, you are right! If desktop effects are disabled that issue disappears. Maybe this is not the better place to say it, but you and all the community of kde developers have done a really great work with plasma and kde4.
SVN commit 837331 by lunakl: No initial overlay window contents. BUG: 166514 M +4 -0 composite.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=837331
Hmm, I'm actually not sure this really fixes it. Are you able to test the patch linked above?
I've got the same problem after upgrading from X.org 7.3 to 7.4 today When it appear: (in my OpenSUSE 11.0 case) 1. Boot from GRUB 2. OpenSUSE splash appear first, press Esc key to show console output 3. SUSE splash disappear, X-Server started, "garbaged" screen visible for a moment, then kdm logon screen appear normally 4. Select User, enter password, "garbaged" screen appear again for a moment, then KDE splash appear normally I have i855GM integrated videocard using 'intel' driver. If Composite extension disable, I can see "previous session desktop" instead "color garbage". There is no such problem on X.org 7.3, so I do the rollback. I'm not sure that is a KDE bug
Pavel Zheltobryukhov, comment #7: Your problem is due to a driver issue and not KDE as it occurs before KDE is running.
X/driver problem.