Version: (using Devel) OS: Linux Installed from: Compiled sources Starting with KDE 4.4 Beta 2 and continuing through to KDE 4.4 RC2, I only get a blank grey rectangle where the unlock dialog should be, when the screen is locked. This problem occurs whether I lock the screen manually or wait for it to lock with the screen saver. I have tried using different screen-savers including the blank one. Interestingly enough, because the cursor normally appears in the password dialog upon moving the mouse, I can still input my password and unlock the session. I just wait for the grey rectangle to appear, type my password, press enter and hope for the best. If that doesn't work, then Ctrl+alt+backspace gets used. Also, I can change the tone of the blank rectangle when I change the systems color scheme. I can confirm this problem on two separate Fedora 12 installs. My Xeon based work computer has this problem, as does my Duo Core Quad based machine at home. Both have Nvidia cards: A Quadro FX 4600 and a 8500 GT respectively. The commonality between the two is that they are both running the proprietary Nvidia drivers and the problem started when I upgraded both machines to KDE 4.3.85 through the kde-redhat rpm repositories. The problem has continued through 4.4 RC2.
works here. this sounds like a bug in qt (try upgrading that) or - less likely - the x server (obviously not the driver this time).
bah, nonsense - i confused the note about the drivers with another report. in fact, this problem looks pretty much like it would be caused by the nvidia driver. try the nv driver to verify it.
I've actually upgraded the machines GPU and RAM, and went ahead an installed the x86_64 version of FC12. I'm now running the new official KDE 4.4 release version, the latest version of xorg, qt, and the latest proprietary Nvidia driver. This new installation has the same problem, but I've discovered (yesterday actually) that it is related to running glx-dock(openGL version of cairo-dock). When glx-dock is started I begin having the problems. If I kill glx-dock and all its related processes the problem doesn't go away. I have to do a restart to "fix" the problem. For now, I'm using the regular cairo-dock without openGL, until I search out the root cause of this. As for the NV driver, I spent several hours at work yesterday, try to fix problems related to it on a RHEL5 Workstation, before just switching to the proprietary Nvidia driver. For now I'll stick with Nvidia's driver, but I appreciate the suggestion, and It may be worth trying for troubleshooting purposes. I'll have to file a bug report with the cairo-dock people, in French. The good thing about this bug is that I can now attribute it to gnome-centric, gtk+ stuff, so I don't have to change my pro-KDE/anti-Gnome world view ;)
had any success with re-trying the nv driver?
I also used to have this problem. It appears to be fixed in the latest cairo-dock (2.3) I'm running a git (well bzr) version, but I think there's a Beta out too.
(In reply to comment #5) > I also used to have this problem. > > It appears to be fixed in the latest cairo-dock (2.3) > I'm running a git (well bzr) version, but I think there's a Beta out too. Closing WORKSFORME then. Please reopen if this isn't true.