Version: (using KDE 4.0.83)
Installed from: Ubuntu Packages
Compiler: gcc (GCC) 4.2.3 (Ubuntu 4.2.3-2ubuntu7)
Some OpenGL screensavers (such as Solar Winds, Particle Fountain, Gravity, but not KPendulum) only make use of the upper left quadrant of the screen (see attached photograph for details). I am using the Nvidia driver version 96.43.05.
Created attachment 25783 [details]
Photograph showing the issue
I forgot to mention that this issue does *not* occur when using KDE 3.5.9 using the same graphics drivers.
I had the same problem with another KDE4 OpenGL screensaver.
My guess is that the QGLWidget needs to specify KScreenSaver as its parent, or it sometimes doesn't resize itself when it runs fullscreen. KPendulum and KRotation didn't have that problem because they were already doing that.
Created attachment 26113 [details]
Actually, I now doubt that it's the right fix. kscreensaver.h says:
You cannot create a new widget with this widget as parent, since this
widget may not be owned by your application. ...
which is exactly what that patch did. I'll see if I can come up with something better.
Moving but to kscreensaver.
I have a little more info.
When the screensaver starts, the embedded QGLWidget gets a single resizeGL() call. This first call always gets the correct size. However on occasion the widget will get a second resizeGL() call a few milliseconds after the first. This tells it to resize to 640x480.
What's odder is that this second call almost always happens when the screensaver is run in demo mode.
I finally got kdeartwork-kde4-4.1.1 to compile on my machine including John's patch (from comment #4) and can confirm that it solves the problem for me.
I'm using kde 4.2 RC with nvidia-drivers 180.22 and I'm having this bug.
*** Bug 181234 has been marked as a duplicate of this bug. ***
i use kde-4.2.0 and this problem still isn' solved more i have to add that when i move my cursos login window pops up and screensaver disappear and some wallpaper shows up... what is very strange for me and i'm a little confused...
This bug looks very much like a dup of bug #66492.
Indeed, this is a duplicate of bug # 66492, so am changing the status accordingly.
*** This bug has been marked as a duplicate of bug 66492 ***