Bug 154637 - Black screen when logging into KDE4
Summary: Black screen when logging into KDE4
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 4.0
Platform: Mandriva RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 155380 163313 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-12-26 19:50 UTC by AAW
Modified: 2008-06-11 12:59 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
.xsession-errors file when starting kde4, compressed with bzip2 (50.49 KB, application/x-bzip2)
2008-01-04 15:34 UTC, AAW
Details
my .xsession-errors (bzip2 compressed) (2.58 KB, application/x-bzip2)
2008-01-06 21:55 UTC, Stefan Majewsky
Details
kwin output (16.79 KB, text/plain)
2008-01-09 15:18 UTC, Bernd Steinhauser
Details
kwinrc with disabled compositing (1.04 KB, text/plain)
2008-01-11 00:37 UTC, Bernd Steinhauser
Details
.xsession-error in case of black login screen (2.01 KB, application/x-bzip2)
2008-02-20 15:09 UTC, Julien Bigot
Details
My Xorg.conf (2.13 KB, text/plain)
2008-02-24 11:15 UTC, Vincenzo Di Massa
Details
My kwinrc (1.66 KB, text/plain)
2008-02-24 11:17 UTC, Vincenzo Di Massa
Details
The output of kwin when black screen is shown (371.03 KB, text/plain)
2008-02-24 11:27 UTC, Vincenzo Di Massa
Details
My glxinfo output (9.19 KB, text/plain)
2008-02-24 11:29 UTC, Vincenzo Di Massa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description AAW 2007-12-26 19:50:54 UTC
Version:            (using KDE KDE 3.97.0)
Installed from:    Mandriva RPMs
Compiler:          gcc-4.2.2-2mdv2008.1 
OS:                Linux

When logging into KDE4 (from kdm 3.5.8) the entire screen is black. KTips appears normally. I can hear system sounds in response to key presses (changing desktops, etc.). Alt-F2 brings up the run dialog and Ctl-Alt-Del brings up the logout dialog.

This happened after upgrading my Mandriva cooker system with the latest Mandriva packages as of 2007-12-24. I had no problem before that.

On a hunch, I removed package libkwinnvidiahack4-3.97.1-1.752045.1mdv2008.1 (using rpm's nodeps option). The black effect didn't occur, but I still don't get a functioning
desktop, just the blue Mandriva background used by KDM.

Machine is Intel P4 with 500MB RAM. Video card is Nvidia GeForce2 MX/MX 400 (using x11-driver-video-nvidia96xx-96.43.01-2mdv2008.1 from Mdv's non-free repository).

I can find nothing out of the ordinary in Xorg or system logs. I did notice a few errors in my ~/.xsession-errors file, but I have no idea whether they're related; I can send the file to you if it would be helpful.

KDE4 Packages installed (probably not complete list):
kde4-dolphin-3.97.1-2.752228.1mdv2008.1
kde4-filesharing-3.97.1-0.752200.1mdv2008.1
kde4-kappfinder-3.97.1-2.752228.1mdv2008.1
kde4-kcalc-3.97.1-0.752255.1mdv2008.1
kde4-kcharselect-3.97.1-0.752255.1mdv2008.1
kde4-kdepasswd-3.97.1-2.752228.1mdv2008.1
kde4-kdessh-3.97.1-0.752255.1mdv2008.1
kde4-kdf-3.97.1-0.752255.1mdv2008.1
kde4-kdialog-3.97.1-2.752228.1mdv2008.1
kde4-kdnssd-3.97.1-0.752200.1mdv2008.1
kde4-keditbookmarks-3.97.1-2.752228.1mdv2008.1
kde4-kfind-3.97.1-2.752228.1mdv2008.1
kde4-kfloppy-3.97.1-0.752255.1mdv2008.1
kde4-kget-3.97.1-0.752200.1mdv2008.1
kde4-kgpg-3.97.1-0.752255.1mdv2008.1
kde4-khexedit-3.97.1-0.752255.1mdv2008.1
kde4-kinfocenter-3.97.1-2.752228.1mdv2008.1
kde4-kjots-3.97.1-0.752255.1mdv2008.1
kde4-kmag-3.97.1-0.751521.1mdv2008.1
kde4-kmilo-3.97.1-0.752255.1mdv2008.1
kde4-kmousetool-3.97.1-0.751521.1mdv2008.1
kde4-kmouth-3.97.1-0.751521.1mdv2008.1
kde4-knewsticker-3.97.1-0.752200.1mdv2008.1
kde4-konqueror-3.97.1-2.752228.1mdv2008.1
kde4-konsole-3.97.1-2.752228.1mdv2008.1
kde4-kopete-3.97.1-0.752200.1mdv2008.1
kde4-kppp-3.97.1-0.752200.1mdv2008.1
kde4-krdc-3.97.1-0.752200.1mdv2008.1
kde4-kregexpeditor-3.97.1-0.752255.1mdv2008.1
kde4-krfb-3.97.1-0.752200.1mdv2008.1
kde4-ktimer-3.97.1-0.752255.1mdv2008.1
kde4-kttsd-3.97.1-0.751521.1mdv2008.1
kde4-kwallet-3.97.1-0.752255.1mdv2008.1
kde4-kwrite-3.97.1-2.752228.1mdv2008.1
kde4-lanbrowsing-3.97.1-0.752200.1mdv2008.1
kde4-superkaramba-3.97.1-0.752255.1mdv2008.1
kde4-sweeper-3.97.1-0.752255.1mdv2008.1
kdeaccessibility4-3.97.1-0.751521.1mdv2008.1
kdeaccessibility4-core-3.97.1-0.751521.1mdv2008.1
kdebase4-runtime-3.97.1-1.752237.1mdv2008.1
kdebase4-workspace-3.97.1-1.752045.1mdv2008.1
kdelibs4-core-3.97.1-0.751982.1mdv2008.1
kdenetwork4-3.97.1-0.752200.1mdv2008.1
kdenetwork4-core-3.97.1-0.752200.1mdv2008.1
kdeplayground4-plasma-3.97.1-0.752113.2mdv2008.1
kdeutils4-3.97.1-0.752255.1mdv2008.1
kdeutils4-core-3.97.1-0.752255.1mdv2008.1
libkde3support4-3.97.1-0.751982.1mdv2008.1
libkdecorations4-3.97.1-1.752045.1mdv2008.1
libkdecore5-3.97.1-0.751982.1mdv2008.1
libkdefakes5-3.97.1-0.751982.1mdv2008.1
libkdesu5-3.97.1-0.751982.1mdv2008.1
libkdeui5-3.97.1-0.751982.1mdv2008.1
Comment 1 AAW 2007-12-31 17:35:34 UTC
A suggestion has been made on the Mandriva Bugzilla (http://qa.mandriva.com/show_bug.cgi?id=36192) that KDE4 is now checking the machine's capabilities to determine whether to activate or deactivate 3D features and may have incorrectly decided my video card supports those features.

1. Is this plausible? The problem appeared with Mandriva's latest KDE4 updates, which I believe are RC2.

2. If it is plausible, is there any way to force deactivation of 3D features (command line or config files)?
Comment 2 Lubos Lunak 2008-01-04 12:05:13 UTC
Compositing now does not activate automatically. Can you attach your ~/.xsession-errors for the problem?
Comment 3 AAW 2008-01-04 15:34:52 UTC
Created attachment 22834 [details]
.xsession-errors file when starting kde4, compressed with bzip2

As requested in Comment #2
Comment 4 Bernd Steinhauser 2008-01-05 23:51:20 UTC
I had this, too, on both my two computer, one of them is running desktop effects and one is not (AIGLX etc. deactivated).
Comment 5 Evan Micheal Goers 2008-01-06 19:07:10 UTC
I have this problem too. I have an NVIDIA Geforce 7800GT, which can handle the 3D effects easily.
Comment 6 Stefan Majewsky 2008-01-06 21:09:34 UTC
I have encountered this problem too, with openSUSE 10.2 and "RC2++" packages (KDE version 3.97.2). My graphics card is a NVidia Geforce 7800 Go with the nvidia driver.

When starting KWin inside a KDE 3 session (using the --replace command) a black screen appears so that I can only see the mouse. I can, however, open my Yakuake and type /opt/kde3/bin/kwin --replace which solves the problem. It is like KWin produces a root window placed in the foreground.
Comment 7 Stefan Majewsky 2008-01-06 21:16:37 UTC
P.S.: Everything worked fine with an earlier 3.97 version (could be 3.97.1 or an earlier 3.97.2) until I updated yesterday (my first update since 22-12-2007 as I had only a dialup connection).
Comment 8 Stefan Majewsky 2008-01-06 21:55:00 UTC
Created attachment 22877 [details]
my .xsession-errors (bzip2 compressed)

This is my .xsession-errors after logging into a KDE 4 session from KDM 3. The
desktop is functional but everything but the splash screen is invisible.
Comment 9 Stefan Majewsky 2008-01-08 17:35:20 UTC
For me, the problem is solved by changing the render type from OpenGL to XRender.
Comment 10 Mike 2008-01-08 17:45:58 UTC
I also get this problem, but only sometimes.

I think it can be tracked down to the blur or transparency options.  If I enable these then they work until I log back in.  I can always fix it by removing .kde.

I am using nvidia 169.07 drivers which should be free of the black window bug.
Comment 11 Bernd Steinhauser 2008-01-08 17:49:56 UTC
> I can always fix it by removing .kde. 
Removing .kde/share/config/kwinrc is more than sufficient. ;)
Comment 12 Bernd Steinhauser 2008-01-09 12:58:36 UTC
Ok, i did a litle bit of testing, the setting, that does definitely trigger this is:
kwin4_effect_blurEnabled=true

The other settings, as far as I tested them, don't seem to have anything to do with it. It even happens, if all other settings are set to false (except Composite of course), although Blur without transparency doesn't really make sense.

Nvidia drivers are 100.14.23 (the latest ones, afaik).

Video card is (shouldn't be relevant I guess):
07:00.0 VGA compatible controller: nVidia Corporation G80 [GeForce 8800 GTS] (rev a2)
Comment 13 Bernd Steinhauser 2008-01-09 13:28:11 UTC
Actually I just found out, that it does also not work, when there are no effects set at all.
I did now track it down to this:

kwin4_effect_blurEnabled=false
kwin4_effect_fadeEnabled=true
--> ok

kwin4_effect_blurEnabled=false
kwin4_effect_fadeEnabled=false
--> bug (I'm not entirely sure about this one, but 90%)

kwin4_effect_blurEnabled=true
--> bug (other settings don't change anything here)

Hope others can reproduce it.
Comment 14 Bernd Steinhauser 2008-01-09 13:48:43 UTC
> For me, the problem is solved by changing the render type from OpenGL to XRender. 

Well, the reason is quite simple: With XRender Blur is not supported, KWin tells you that.
There is another reason. When starting KDE4 with XRender it will deactivate all effects on startup. You have to go to the effects menu and press apply, then they are activated.
But it can be tested with kwin --replace and it shows, that with XRender the problem with fade seems to be gone.

Back to OpenGL. The behaviour is also reproducable with kwin --replace. At least on my computer. ;)
Comment 15 Bernd Steinhauser 2008-01-09 15:18:45 UTC
Created attachment 22915 [details]
kwin output

It seems to be not that much, is there a higher debug level, that can be
activated?
Comment 16 AAW 2008-01-09 17:54:11 UTC
Re: Comments #10-#15
None of that works for me.

Re: Comment #9
Pardon the dumb question, how do you change the render type to XRender?
(I did check X and related man pages, nvidia README, googled, etc. before asking.)
Comment 17 Stefan Majewsky 2008-01-09 17:56:18 UTC
AAW: In System Settings, at "Workspace > Workspace effects" (or how it is called in English), open the advanced options and change the compositing type.
Comment 18 Bernd Steinhauser 2008-01-09 18:02:22 UTC
AAW: You get this with the default config for kde4?
Then we are really talking about different issues here.
Comment 19 AAW 2008-01-09 18:55:56 UTC
Re: Comment #17
Unfortunately I can't access the KDE4 menu from the keyboard. Does anyone happen to know what to enter in which config file?

Re: Comment #18
That is correct. Ever since the last KDE4 release (RC2, I guess), it happens even with a brand new user. I had no problem prior to the update.
Comment 20 Bernd Steinhauser 2008-01-09 19:08:14 UTC
Hm, then it is a different problem.
I've compiled a lot of sources after RC2 and got this only since a few days (though I didn't do a recompile from 19.12. to approx 29.12).

But with a fresh config I don't have this.

What happens if you disable Composite and AIGLX in xorg.conf?

Section "Extensions"
        Option          "Composite" "false"
EndSection

Section "ServerFlags"
        Option          "AIGLX" "off"
EndSection
Comment 21 AAW 2008-01-10 01:11:56 UTC
Re: Comment #20
With Composite off, the black screen is replaced by the KDM background. Everything else is the same as my initial report.

With Composite and AIGLX off, I also lose all window decorations (title bar, ability to resize, etc.)
Comment 22 Bernd Steinhauser 2008-01-10 01:54:35 UTC
That means, that kwin crashed.

Does it work, if you then open a konsole (Alt+F2) and run kwin manually?
Comment 23 Aaron J. Seigo 2008-01-10 09:06:41 UTC
*** Bug 155380 has been marked as a duplicate of this bug. ***
Comment 24 AAW 2008-01-10 14:52:40 UTC
Re: Comment #22
Yes, "kwin --replace" works. Not only that, kwin no longer crashes on subsequent logins. The original problem remains however.
Comment 25 Bernd Steinhauser 2008-01-11 00:31:44 UTC
Did you try to run kde4 via startkde directly instead of kdm?
Did you try with a kwinrc file, that is known to be sane?

BTW: There is another bug report (bug 155417) with the same issue (I guess), he has got a Intel card, too, but I think he has the problem, that we Nvidia users face when we enable blur and not yours.
Comment 26 Bernd Steinhauser 2008-01-11 00:37:36 UTC
Created attachment 22949 [details]
kwinrc with disabled compositing

Could you try with this kwinrc?
It has explicitly disabled compositing and it should work.
Comment 27 AAW 2008-01-12 14:34:58 UTC
Re: Comment #25
Starting kde4 from init 3 command line gives same result as starting from KDM.

I haven't made any changes to Mandriva's default kwinrc, which is:
   [Style]
   BorderSize=1
   ButtonsOnLeft=MS
   ButtonsOnRight=HIAX
   CustomButtonPositions=false
   PluginLib=kwin3_oxy
   ShowToolTips=true

Re: Comment #26
Tried with kwinrc from attachment 22949 [details]. No change.

General Comment:
I'm now in the process of upgrading to Mandriva's packaging of KDE 4.0.0. Packages are still showing up on the mirrors, resulting in some (hopefully) temporary phonon library mismatches, but so far the original problem remains.
Comment 28 AAW 2008-01-14 19:24:58 UTC
After this morning's updates (Mandriva cooker, the development branch), I have a visible desktop. The only KDE4 packages I installed were extragear-plasma-4.0.0-1mdv2008.1 and libplasma1-4.0.0-1mdv2008.1
which replaced kdeplayground4-plasma-3.97.1-0.752113.2mdv2008.1 and libplasma1-3.97.1-1mdv2008.1 respectively. 

I'm going to hold off closing this for a few days, just to be certain the problem is solved.
Comment 29 Lukas Appelhans 2008-01-14 19:40:51 UTC
I think this bug is because of KWin and not of Plasma, so un/installing plasma packages shouldn't help. Didn't you turn off an effect (blur?)?

Lukas
Comment 30 AAW 2008-01-15 01:27:16 UTC
Re: Comment #29
I turned off blur, composite, AIGLX, and followed every other suggestion anyone has made on this bug report. All of them were greatly appreciated, but they didn't cure the problem. After my daily update this morning, that problem went away. The two packages I mentioned in Comment #28 were the only KDE4 packages installed. I'm not advancing any theories, just reporting what happened.
Comment 31 Andrea Iudiciani 2008-01-15 10:26:49 UTC
I had this problem too but, following the suggestion about turning off the blur effect, the problem (in my case) was solved. 
Don't know if can help, but I got an Nvidia video card (8600M GS, driver version: 169.07).
Comment 32 markuss 2008-01-15 11:08:43 UTC
I have the same problem, but with an ATI graphics card (Radeon 9200SE, using the "radeon" driver). It appears every time with OpenGL as renderer -- no matter which effect is selected.
Comment 33 Lubos Lunak 2008-01-17 17:41:48 UTC
- If somebody has a problem caused by the blur effect, please file a separate bugreport for that - blur is definitely not enabled by default, so this is not that problem.
- Please see http://techbase.kde.org/Projects/KWin/4.0-release-notes for KWin's 4.0 release notes that include information on setting up and troubleshooting - if something there helps to prevent this problem, please say what is was. If not, I'll need 'glxinfo' output.
Comment 34 Bernd Steinhauser 2008-01-17 18:24:11 UTC
I opened bug 156018 for the blur effect issue.
Comment 35 Luca Gambetta 2008-01-18 08:51:57 UTC
Yesterday I disabled the fade effect (blur is always disabled), then compiled the latest branch (svn rev r762910). This morning every time I tryed to login, I got a black screen, with only the mouse. Just pressing ctrl-f8 (enabling the Desktop Grid), made the complete desktop appear and completely usable.
I'm on a NVIDIA 7600GS 256mb driver 169.07. It used to work flawlessy before with fade enabled, but was slow.
This is my actual kwinrc:

[$Version]
update_info=kwin3_plugin.upd:kde3.2,kwin_on_off.upd:kwin_on_off,kwin_focus2.upd:kwin_focus2,kwin.upd:kde3.0r1,kwin.upd:kde3.2Xinerama,kwin_focus1.upd:kwin_focus1

[Compositing]
Backend=OpenGL
Enabled=true
GLDirect=false
GLMode=TFP
GLTextureFilter=2
GLVSync=false
HiddenPreviews=0
XRenderSmoothScale=false

[Desktops]
Name_1=
Name_2=
Name_3=
Name_4=
Number=4

[Plugins]
kwin4_effect_blurEnabled=false
kwin4_effect_boxswitchEnabled=true
kwin4_effect_desktopgridEnabled=true
kwin4_effect_dialogparentEnabled=true
kwin4_effect_diminactiveEnabled=false
kwin4_effect_explosionEnabled=false
kwin4_effect_fadeEnabled=false
kwin4_effect_fallapartEnabled=false
kwin4_effect_invertEnabled=false
kwin4_effect_loginEnabled=true
kwin4_effect_logoutEnabled=true
kwin4_effect_lookingglassEnabled=false
kwin4_effect_magnifierEnabled=false
kwin4_effect_maketransparentEnabled=false
kwin4_effect_minimizeanimationEnabled=false
kwin4_effect_mousemarkEnabled=false
kwin4_effect_presentwindowsEnabled=true
kwin4_effect_scaleinEnabled=false
kwin4_effect_shadowEnabled=true
kwin4_effect_sharpenEnabled=false
kwin4_effect_showfpsEnabled=false
kwin4_effect_showpaintEnabled=false
kwin4_effect_taskbarthumbnailEnabled=true
kwin4_effect_thumbnailasideEnabled=false
kwin4_effect_trackmouseEnabled=true
kwin4_effect_zoomEnabled=true

[Style]
BorderSize=0
ButtonsOnLeft=MS
ButtonsOnRight=HIA__X
CustomButtonPositions=false
PluginLib=kwin3_oxygen
ShowToolTips=true
Comment 36 John Miller 2008-02-04 14:44:16 UTC
*** This bug has been confirmed by popular vote. ***
Comment 37 Julien Bigot 2008-02-20 15:09:43 UTC
Created attachment 23634 [details]
.xsession-error in case of black login screen
Comment 38 Julien Bigot 2008-02-20 15:10:09 UTC
First, some informations perhaps worth mentioning, xorg & nvidia-driver version :

$ dpkg -l xserver-xorg nvidia-kernel-2.6.24-1-686
ii  nvidia-kernel-2.6.24-1-686                  169.09-1+2.6.24-4
ii  xserver-xorg                                1:7.3+10


1. this appens whatever the konsole size is (usually resizing from ~1600x1000 -> ~1000x600, but same appens when I do ~200x200 -> ~300x300)

2.
 - if I fully disable desktop effects Enabled=false in the [Compositing] section, there is not more slowdown (but no more transparency too)
 - if I disable all effects, I get a black screen on login, as reported by someone else in bug #154637 (see attached xsession-error, even if I don't think there's much interesting here, I'll also post it on #154637)
 - if I just enable the fade effect, then the behaviour is the same as with all effects enabled.
Comment 39 Julien Bigot 2008-02-20 15:12:37 UTC
opps, I'm really sorry, I posted the above message on the wrong bug ...
The attached .xsession-error is relevant tough
Comment 40 Vincenzo Di Massa 2008-02-24 11:12:32 UTC
I just spend one night investigating this bug...
I think people are referring to different problems inside this bug report.

The problem I'm addressing below is "black screen with ati 8.0{1,2} drivers and composite enabled".

The problem is (in my case) somehow triggered by the deactivation of the kwin4_effect_fadeEnabled (setting it to flase). This is always reproducible.

On the other hand sometimes the problem occurs even without disabling the Fade Effect. In this case the only fix is to respawn a new Xorg.

I tried all sort of kwin config options (even brute force using "divide et impera") to track thi problem. I hope my guesses are useful to someone else.
Comment 41 Vincenzo Di Massa 2008-02-24 11:15:07 UTC
Created attachment 23692 [details]
My Xorg.conf

This is the Xorg.conf that is working for me using for fglrx 8.0{1,2}.
Comment 42 Vincenzo Di Massa 2008-02-24 11:17:01 UTC
Created attachment 23694 [details]
My kwinrc

This how my kwinrc is set to make things work.
Comment 43 Vincenzo Di Massa 2008-02-24 11:27:15 UTC
Created attachment 23696 [details]
The output of kwin when black screen is shown

.xession-errors is clean:
$ rm .xsession-errors
$ kwin
#kill kwin
$ ls .xession-errors
ls: .xsession-errors No such fileor directory
Comment 44 Vincenzo Di Massa 2008-02-24 11:29:11 UTC
Created attachment 23697 [details]
My glxinfo output

Finally here it is what glxinfo outputs :-)
Comment 45 Adrian 2008-03-13 12:27:36 UTC
I have the same problem on yesterday's KDE-SVN. I have blur and composite desiabled. I use nvidia card with the newest drivers installed.
Comment 46 Saurabh Asthana 2008-03-28 21:06:57 UTC
I had the same problem today - kwin started up as a black screen. My compositing section in kwinrc looked like this:
[Compositing]
Enabled=true

Merely changing 'true' to 'false' restored kwin as normal. Using the XRender backend works okay, though with some unrelated bugs. No black screen, though.

My card is an ATI radeon that doesn't support AIGLX - no direct rendering, no 3D acceleration at all.
Comment 47 Arnout Boelens 2008-04-07 15:47:46 UTC
I had the same problem, but just solved it. I followed the directions of a Gentoo howto on how to enable AIGLX (http://gentoo-wiki.com/HOWTO_AIGLX). I am using the fglrx driver version 8.47.3-3 with x.org 7.3+10 on Debian unstable.
Comment 48 Jeroen Tietema 2008-04-22 18:24:51 UTC
An upgrade to hardy fixed the problem for me.
Comment 49 Lubos Lunak 2008-05-13 23:30:03 UTC
Can somebody still reproduce this problem after r807454 (r807453 in 4.0 branch)?
Comment 50 Monkey 9 2008-05-14 11:23:30 UTC
The effects work, no black desktop, but Both browser and Mailclient (FF and TB) are invisible when desktop effects are active.
Besturingssysteem:  Linux 2.6.25.3-2-default x86_64
  Current user:  oddball@AMD64x2-sfn1
  System:  openSUSE 11.0 (x86_64) Beta3
  KDE:  4.0.4 (KDE 4.0.4 >= 20080505) "release 8.1"
Comment 51 Lubos Lunak 2008-05-14 11:49:34 UTC
Please don't hijack bugreports (-> bug #160393).
Comment 52 Monkey 9 2008-05-14 12:45:08 UTC
Sorry, not my intention.;)
I was never able to get this far..!
Trying to reproduce, as you asked, made this side-effect visible...
(i was told by You not to use the effects until the bugs were fixed, remember?)
Thnx for pointing me to the other one, it matches my bug.
Comment 53 Lubos Lunak 2008-05-23 00:06:27 UTC
Closing as fixed unless somebody can still confirm the problem.
Comment 54 Bart Kelsey 2008-05-28 23:40:01 UTC
I can confirm that this bug is still happening, at least to me.  I'm running KDE 4.0.4 on Fedora Core 9 (with fedora 8's Xorg server installed) with an nvidia Quadro video card.  When I have blur enabled, the screen starts up black, but pressing control-F8 will show me my desktop and it will work after that (note that fade and blur effects work just fine after that).  
Comment 55 Lubos Lunak 2008-06-06 17:31:03 UTC
*** Bug 163313 has been marked as a duplicate of this bug. ***
Comment 56 Christophe Marin 2008-06-11 10:57:51 UTC
*** Bug 163734 has been marked as a duplicate of this bug. ***