Fedora This forum is for the discussion of the Fedora Project. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
07-09-2014, 08:48 PM
|
#1
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
|
Fedora and the KDE Screensaver reset/glitch
I'm following this tutorial in the hope to fix the KDE Screensaver issue. The instruction for KDE is about 1/2 way down the page.
http://www.jwz.org/xscreensaver/man1.html
Each time I boot up Fedora I have to consistently reset the screensaver. (not sure why that's happening)
For some reason (maybe the instruction is old?) Appearance & Themes are not in the KDE Control Module. General, Fonts and stylesheets are the only options. UNchecking "start automatically" doesn't exist.
I also looked in Screensaver under advanced preferences-
Not there either.
BTW, this machine is not mine to make this adjustment so that's one of the reasons I have asked for help.
Aside from following the instructions that don't apply to what I am working with; is there another way to set the screensaver permanently?
Thanks in advance-
|
|
|
07-09-2014, 11:40 PM
|
#2
|
Member
Registered: Dec 2008
Location: Newark Ohio
Distribution: Fedora Core
Posts: 270
Rep:
|
When you say reset do you mean the timeout or type and or both? There may be some screen saver swapping thing that cycles thru them on a cron job but since I haven't played with FC20 yet it's just a guess.
Look at the config file timestamp. If you have to chattr +i the file and it won't be able to even as root.
|
|
|
07-09-2014, 11:54 PM
|
#3
|
LQ Muse
Registered: Aug 2005
Location: A2 area Mi.
Posts: 17,639
|
as i recall for Gnome3 and kde
getting the gtk2 based xscreensaver custom settings to work requires making a custom config file for the ones you want
however it has been some time since i used them
if i leave the machine running and i am away i tend to be running a LONG running program that is using all the CPU cores or all the GPU cores and almost all the ram and swap
and i normally do not want the screen saver eating up cpu/gpu cycles with a 2 to 4 hour long run
|
|
|
07-10-2014, 07:56 PM
|
#4
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
Original Poster
|
Quote:
Originally Posted by kentyler
When you say reset do you mean the timeout or type and or both? There may be some screen saver swapping thing that cycles thru them on a cron job but since I haven't played with FC20 yet it's just a guess.
Look at the config file timestamp. If you have to chattr +i the file and it won't be able to even as root.
|
By reset I mean I have to go to the Applications menu and select 'screensaver'.
Upon doing so, I get a message something like you do not have the screensaver set at this time do you want to set it? I say yes but at the next fresh boot up the screensaver has to be set again.
|
|
|
07-10-2014, 08:08 PM
|
#5
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
Original Poster
|
Quote:
Originally Posted by John VV
as i recall for Gnome3 and kde
getting the gtk2 based xscreensaver custom settings to work requires making a custom config file for the ones you want
however it has been some time since i used them
if i leave the machine running and i am away i tend to be running a LONG running program that is using all the CPU cores or all the GPU cores and almost all the ram and swap
and i normally do not want the screen saver eating up cpu/gpu cycles with a 2 to 4 hour long run
|
I can make a custom config file and maybe name it kde-screensaver and add the names of the screensavers to the file. The problem I have is the argument given in the instruction for the /usr/libexec/kde4/kscreenlocker file and understanding where it belongs.
Code:
#!/bin/sh
xscreensaver-command -lock
At the end or at the beginning?
I went in circle's trying to learn how to make a file executable with chmod a+x.
I read the man pages for chmod and it still alluds me-
Is this the right way to run a file called 'xscreensaver' making it executable via the terminal?
Code:
chmod a+x xscreensaver
I generally just run ./nameofile or use bash-
|
|
|
07-11-2014, 08:46 AM
|
#6
|
Member
Registered: Dec 2008
Location: Newark Ohio
Distribution: Fedora Core
Posts: 270
Rep:
|
Chmod a+x means everyone can execute it and what's odd is I'd think that it should be that way by default.
Either way you are doing it properly by command line. I would use full path in your script though.
|
|
|
07-11-2014, 08:46 PM
|
#7
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
Original Poster
|
Quote:
Originally Posted by kentyler
Chmod a+x means everyone can execute it and what's odd is I'd think that it should be that way by default.
Either way you are doing it properly by command line. I would use full path in your script though.
|
Thanks, I'll try to get it working tomorrow after I make a custom config file.
I know the names of the screensavers that I want should be in that file however, I'm not entirely sure what the arguments or strings should be.
If you could make a suggestion that would be great.
|
|
|
07-25-2014, 02:30 AM
|
#8
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
Original Poster
|
Quote:
Originally Posted by kentyler
Chmod a+x means everyone can execute it and what's odd is I'd think that it should be that way by default.
Either way you are doing it properly by command line. I would use full path in your script though.
|
Unfortunately it's not by default. Agreed it should be.
I'll use /home/ztcoracat/sheena.sh
There is only one screensaver that I want to be used all of the time anyway.
Do you think that a boot time script would be better than creating a custom config file?
|
|
|
08-10-2014, 05:35 PM
|
#9
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
Original Poster
|
Installed CentOS last week and no longer running Fedora.
|
|
|
All times are GMT -5. The time now is 01:12 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|