No opengl screensavers after KDE4.8.3 upgrade(Answered)

[Xenaflux]

most people just read what i write and do the opposite

Well, in future, write the wrong thing, maybe they do the opposite (=right thing)
 

[Cris70]

"There is no problem with your (or other's) opinion, as long as you don't force it on everyone"

i can share my opinion or ideas and support them with pros and cons but how could i force anyone to believe what i write?  each one decides what to do on their pc and rarely i can help at all, at best

most people just read what i write and do the opposite

T6, I don't know if you're part of the "development team". What I meant is that IF (note the IF, I'm not saying they did it) developers decide to drop support for a package because they don't like it (e.g. because it hurts their sense of "wasting resources") than they're forcing their opinion onto others.
The same holds true even if they just decide to drop the ball on a faulty package because in their opinion it is not a worthy package, unless obviously their feeling is shared by the majority of the user base, in which case I'd say it is best to simply remove the package from the repo.

Bye
Cris

[T6]

i am not a developer

remember that pclinux developers and kde  developers are two different groups of people, no relation

pclinux offers what kde is at the moment

if the kde developers already said gheir reasons to drop support or remove features we can't do more than make a requesto to put those parts back, but in kde forum, not in pclinux

enough energy has been wasted talking about a extremely diminute and meaningless piece of software, each one can do what see is best, if jump to another distro to have screensavers is what someone needs, good luck, if you can patch the problem and share that solution on repos that is great too but if you decide to lock desktop and turn off screen when required saving electricity better for you

[Archie]

No, the development team did not drop support for (opengl) xscreensaver. It just happened that way. We package applications (KDE) the way they were meant to be used ... with a few modification. If KDE still has support for xscreensaver, it will be there but unfortunately the support were obviously removed. As for other distros on KDE platform, I can only guess that they must have done some serious modifications if they were able to support xscreensaver. PCLinuxOS atm do not have the resources to do what other distros had accomplished but that does not mean we are any lesser.

Peace out!

[Cris70]

T6, Archie, first of all: thank you for your answers.
Unfortunately, it seems you both still fail to grasp what I'm saying (I know, it's a lengthy thread and difficult to read through). I'll try to state it once more:
I'm NOT looking for xscreensaver compatibility (I've already removed every reference to xscreensaver from my system). OpenGL screen saver modules are NOT an exclusive feature of xscreensaver. There are NATIVE KDE OpenGL screensaver modules (when I say native I mean built for Kscreensaver, not for Xscreensaver). Those native modules fail to work, and they shouldn't.

Facts are as follows:
1) kscreensaver OpenGL modules fail to work on PCLinuxOS
2) various OpenGL features in other packages fail to work on PCLinuxOS (see "Digikam advanced slideshow" thread)
3) one kscreensaver opengl module I compiled myself DO work
4) some programs using OpenGL DO work

So, there definitely is something wrong on PCLinuxOS and OpenGL, and it is not related to xscreensaver compatibility and/or KDE. This is what needs addressing.

Hope it is clearer now.

Maybe this should be properly separated from this thread about screensavers, and put into a topic of its own about generic OpenGL problems?

Bye
Cris

[Archie]

Heya Cris70,

I suppose I can only provide you with half an answer, KDE on PCLOS's side of your query. I did not package the OpenGL libraries for PCLOS so I will not be able to provide you with an acceptable (full) explanation ... or even an excuse.

However, when you mean NATIVE KDE OpenGL screensavers, were you referring to the KDE user-contributed/posted modules at kde-look and/or kde-apps? I can vouch that some of them would work whilst others won't even compile; and in my experience, the ones I've tried slows down the system. Please note that I am not (yet) attributing the performance decrease to our OpenGL libs.

[frazelle09]

Yea!!!  i got my Bouncin' Betty back again!  Everybody gets a kick outa her!

Have a great evening!  

[gandy]

Yea!!!  i got my Bouncin' Betty back again!  Everybody gets a kick outa her!

Have a great evening!  

Could you explain what you mean by this? Is this a screensaver?

[frazelle09]

Hi, gandy!  Yes, it's a really cute screensaver of a bouncing cow.  But the cow doesn't just bounce up and down, but does flip-flops and summersaluts, all the while looking just like...

a cow.

Have a great morning! 

[gandy]

So, this is something you downloaded?

[frazelle09]

No, it's just one of the opengl screensavers that this thread is about and which i have been unable to use since the newer versions of KDE.

Have a wonderful morning! 

[frazelle09]

Dear George... i found this on this very thread.  It's what i used to get my Bouncing Betty working again.

The opengl screensavers do still work. What has changed is the ability to start them from the KDE Control Panel. Archie kindly provided a workaround in this thread.
Quote
Xscreensaver to working normally? I am quite happy without it. Xscreensaver waste unnecessary CPU cycles. I'd rather just use the Lock Screen. But yes, there is a way. Follow the instructions explicitly.

(A) You should at minimum have the following installed:

    xscreensaver
    xscreensaver-base
    xscreensaver-common


(B) Open Konsole and type,
Code:

[user@localhost ~] $ xscreensaver-demo


When Warning: The XscreenSaver daemon doesn't seem to be running on display ":0". Launch it now? Click OK.

On the Display Modes tab, set your preferences accordingly. Do the same with the Advanced tab (if you have anything to set). Once done, select File > Quit.

(C) Test your xscreensaver module selection with the following command:
Code:

[user@localhost ~] $ xscreensaver-command --activate


Xscreensaver should display your selected module

(D) Still on the konsole, type,
Code:

[user@localhost ~] $  xset s on


This should be OK for your session and launch xscreensaver on its designated timeout ... but when you shutdown and bootup, you will need to restart the daemon, etc. again. To make it permanent, do the following:

First,  repeat the instructions on (B).

You should also disable KDE screensaver if you have it turned on. Open SystemSettings > Hardware > Display and Monitor > Screen Saver. Uncheck everything on the Settings.

Next, use your favorite text editor to create an xscreensaver.desktop file in your ~/.config/autostart directory that contains the following five lines:

Quote
[Desktop Entry]
Exec=xscreensaver
Name=XScreenSaver
Type=Application
X-KDE-StartupNotify=false

Then save the file and exit. The next time you reboot, xscreensaver will autostart.

As an added bonus, the following is how you'd change the right-click of your mourse button and selecting Lock Screen.

Open your konsole and su to root.

Quote
# cp /usr/lib/kde4/libexec/kscreenlocker /usr/lib/kde4/libexec/kscreenlocker.kde
# touch /usr/lib/kde4/libexec/kscreenlocker
# cat > /usr/lib/kde4/libexec/kscreenlocker << EOF
#!/bin/sh
xscreensaver-command -lock
EOF

When you are returned to the # prompt, type chmod a+x /usr/lib/kde4/libexec/kscreenlocker .

You should be able to use the right-click > Lock Screen with xscreensaver. The Unlock screen is pretty ugly!

Repeated warning:  In my own personal experience, xscreensaver WILL waste a terrible amount of CPU cycles which can cause CPU temperature to rise. Blank your screen after 5 or 10 minutes of xscreensaver. Use at your own risk.

 
i'm not sure what "blaster" is, but if it is one of these it probably should...

Hope this helps.  Have a great evening! 

[kjpetrie]

You can set the screensaver in xscreeensaver-demo (eg pipes or whatever) and use the Kscreen saver window to choose the timeout etc, as long as the screen saver is activated. I'm going to test a bit further. It seems setting up in SystemSettings is not enough to get it to run, even if the desired program is listed there, but by combining the advice in this thread almost anything can be made to work.

Edit: it seems whether you select xscreensaver or kscreensaver, you have to set the other one to "blank screen only" with a very long time delay to stop it interfering. All very messy, though.

[GOTHBITES]

hello yall

i still can't get my PAC-man going,   not found.

[ancients]

This was from a previeous post:

{ I'm NOT looking for xscreensaver compatibility (I've already removed every reference to xscreensaver from my system). OpenGL screen saver modules are NOT an exclusive feature of xscreensaver. There are NATIVE KDE OpenGL screensaver modules (when I say native I mean built for Kscreensaver, not for Xscreensaver). Those native modules fail to work, and they shouldn't.

Facts are as follows:
1) kscreensaver OpenGL modules fail to work on PCLinuxOS
2) various OpenGL features in other packages fail to work on PCLinuxOS (see "Digikam advanced slideshow" thread)
3) one kscreensaver opengl module I compiled myself DO work
4) some programs using OpenGL DO work

So, there definitely is something wrong on PCLinuxOS and OpenGL, and it is not related to xscreensaver compatibility and/or KDE. This is what needs addressing. }

As far as that they dont workin PclinuxOS, for what ever reason they should, they work on other distros with plasma ect...
My question is why would you drop something that clearly does work, ( obviously not here, ) and that people would actually want in a desktop system, A SCREENSAVER. When I began with PCLinuxOS ( early 2007 ) everything clearly worked, but now somethings dont,  desktop screensavers, stellerarium, chokok drops connections when people log on, ect. is this the great distro I fell in love with, or is this a distro only for the command line geeks.
Sorry this has been building since the end of the 2010 version when everything worked