The KDE screen savers will only blank out the screen though most of them test ok when you hit the test button in the Control Center.
The Gnome screen savers work ok.
My system has a Radeon 9200SE video card and I have a ViewSonic A70f monitor.
Does anyone have a fix for this?
BRUCE STANLEY wrote on Wednesday, 17 August 2005 4:55 PM:
The KDE screen savers will only blank out the screen though most of them test ok when you hit the test button in the Control Center.
The Gnome screen savers work ok.
My system has a Radeon 9200SE video card and I have a ViewSonic A70f monitor.
Does anyone have a fix for this?
Are you logging in as root, by any chance?
-- Trevor Hammonds
--- "Trevor G. Hammonds" trevor@skyhost.net wrote:
BRUCE STANLEY wrote on Wednesday, 17 August 2005 4:55 PM:
The KDE screen savers will only blank out the screen though most of them test ok when you hit the test button in the Control Center.
The Gnome screen savers work ok.
My system has a Radeon 9200SE video card and I have a ViewSonic A70f monitor.
Does anyone have a fix for this?
Are you logging in as root, by any chance?
-- Trevor Hammonds
No, as a normal user
--- BRUCE STANLEY bruce.stanley@prodigy.net wrote:
The KDE screen savers will only blank out the screen though most of them test ok when you hit the test button in the Control Center.
The Gnome screen savers work ok.
My system has a Radeon 9200SE video card and I have a ViewSonic A70f monitor.
Does anyone have a fix for this?
Is anyone out there using screensavers under KDE ?
I have not been able to get them to work.
They work fine on my system when using FC2, FC3, or FC4, but not in Centos 4.1.
On 8/18/05, BRUCE STANLEY bruce.stanley@prodigy.net wrote:
Is anyone out there using screensavers under KDE ?
I have not been able to get them to work.
They work fine on my system when using FC2, FC3, or FC4, but not in Centos 4.1.
Come to think of it, I changed my SS from slideview to Matrix a couple weeks back and it ended up just blanking the screen. I didnt give it much thought back then. I'll try anohter one and see what happens.
PS: I was on FC2 and copied over my home directory so its not a new CentOS4 account.
On 8/18/05, Dave wintermutecx@gmail.com wrote:
Come to think of it, I changed my SS from slideview to Matrix a couple weeks back and it ended up just blanking the screen. I didnt give it much thought back then. I'll try anohter one and see what happens.
PS: I was on FC2 and copied over my home directory so its not a new CentOS4 account.
Looks like some work and some dont here. In FC I only used slideshow and on occasion Matrix. Now matrix no longer works and some others.
Here are the errors I got. X error in xmatrix: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 3 (X_GetWindowAttributes) Resource id in failed request: 0x7 Serial number of failed request: 701 Current serial number in output stream: 702 SetGrabKeysState - enabled
X error in bsod: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 3 (X_GetWindowAttributes) Resource id in failed request: 0x7 Serial number of failed request: 702 Current serial number in output stream: 703 SetGrabKeysState - enabled
HTH
--- Dave wintermutecx@gmail.com wrote:
On 8/18/05, Dave wintermutecx@gmail.com wrote:
Come to think of it, I changed my SS from slideview to Matrix a couple weeks back and it ended up just blanking the screen. I didnt give it much thought back then. I'll try anohter one and see what happens.
PS: I was on FC2 and copied over my home directory so its not a new CentOS4 account.
Looks like some work and some dont here. In FC I only used slideshow and on occasion Matrix. Now matrix no longer works and some others.
Here are the errors I got. X error in xmatrix: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 3 (X_GetWindowAttributes) Resource id in failed request: 0x7 Serial number of failed request: 701 Current serial number in output stream: 702 SetGrabKeysState - enabled
X error in bsod: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 3 (X_GetWindowAttributes) Resource id in failed request: 0x7 Serial number of failed request: 702 Current serial number in output stream: 703 SetGrabKeysState - enabled
HTH
Hi Dave! Don't know if you caught my last post on this so just in case I'll re-post it here. In a nutshell, I bypassed KDE for running Screen savers.
From prior post:
I found a work-around that allows most of the screen savers to work. Some of the GL savers are still a little slugish or buggy.
I installed the latest KDE updates in the Centos 4.1 update repository but that did not solve the problem.
I ran man xscreensaver and found out a way to run xscreensaver that bypasses KDE and this got around the problem.
I did the following:
1). ran control-center and turned screensavers off in KDE.
2). created a file named xscreensaver.desktop and placed it in by ~.kde/Autostart directory.
The file contains the following lines:
[Desktop Entry] Exec=xscreensaver Name=XScreensaver Type=Application X-KDE-StartupNotify=false
3). then I created a program launcher on my desktop that runs xscreensaver-demo when I want to change to different screen savers.
Now xscreensaver startups when I login and my screen savers work!
Le Jeudi 18 Août 2005 23:45, BRUCE STANLEY a écrit :
--- BRUCE STANLEY bruce.stanley@prodigy.net wrote:
The KDE screen savers will only blank out the screen though most of them test ok when you hit the test button in the Control Center.
The Gnome screen savers work ok.
My system has a Radeon 9200SE video card and I have a ViewSonic A70f monitor.
Does anyone have a fix for this?
Is anyone out there using screensavers under KDE ?
Yes, I guess I am, "rpm -qa | grep saver" gives me xscreensaver-4.18-5.rhel4.2 and I use KDE as desktop manager (with nvidia binary driver).
In KDE Control Center, I see the setup is to start a random screensaver automatically after 5mn, which works for me (checkbox for notifying screen of energy-saving is unchecked). I also have the "dpms" option in my monitor section in /etc/X11/xorg.conf, and "xdpyinfo | grep -i saver" gives me MIT-SCREEN-SAVER.
I have not been able to get them to work.
They work fine on my system when using FC2, FC3, or FC4, but not in Centos 4.1.
I don't know the cause of your problem, but perhaps you could look in /var/log/Xorg.0.log if there's any insteresting related error message. Also you could tell us which driver you're using for your gfx card (DRI or ATI fglrx binary driver).
Now, after writing all this, I just launched "xscreensaver" on the command-line, and by choosing "Settings", I can see the default setting is to have "Blank screen only". Perhaps there's some priority wrong between your KDE and xscreensaver installs ? Looking at https://bugzilla.redhat.com/bugzilla/buglist.cgi?bug_status=NEW&bug_stat... (that is, searching "screensaver" in RedHat's bugzilla), it seems there are some known issues, in particular https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=160529
--- Vincent Knecht vknecht@club-internet.fr wrote:
Le Jeudi 18 Août 2005 23:45, BRUCE STANLEY a écrit :
--- BRUCE STANLEY bruce.stanley@prodigy.net wrote:
The KDE screen savers will only blank out the screen though most of them test ok when you hit the test button in the Control Center.
The Gnome screen savers work ok.
My system has a Radeon 9200SE video card and I have a ViewSonic A70f monitor.
Does anyone have a fix for this?
Is anyone out there using screensavers under KDE ?
Yes, I guess I am, "rpm -qa | grep saver" gives me xscreensaver-4.18-5.rhel4.2 and I use KDE as desktop manager (with nvidia binary driver).
In KDE Control Center, I see the setup is to start a random screensaver automatically after 5mn, which works for me (checkbox for notifying screen of
energy-saving is unchecked). I also have the "dpms" option in my monitor section in /etc/X11/xorg.conf, and "xdpyinfo | grep -i saver" gives me MIT-SCREEN-SAVER.
I have not been able to get them to work.
They work fine on my system when using FC2, FC3, or FC4, but not in Centos 4.1.
I don't know the cause of your problem, but perhaps you could look in /var/log/Xorg.0.log if there's any insteresting related error message. Also you could tell us which driver you're using for your gfx card (DRI or ATI fglrx binary driver).
Now, after writing all this, I just launched "xscreensaver" on the command-line, and by choosing "Settings", I can see the default setting is to
have "Blank screen only". Perhaps there's some priority wrong between your KDE and xscreensaver installs ? Looking at
https://bugzilla.redhat.com/bugzilla/buglist.cgi?bug_status=NEW&bug_stat...
(that is, searching "screensaver" in RedHat's bugzilla), it seems there are some known issues, in particular https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=160529 _______________________________________________
Hi Vincent & Dave!
I have looked at some of the bugs for xscreensaver in bugzilla, and none of them seem to quite fit my the conditions of my setup.
More info: the xorg.conf file says that I am using the 'radeon' driver. the standard driver provided by Redhat/Centos.
I looked at the /var/log/xorg.o.log file and did not see any errors that were pointing to video or screen saver issues.
Running xscreensaver from a command window showed the screen saver set up in my Gnome login (they work there), not the one configured in KDE.
After running xscreensaver manually, I was able to get the GL Fireworks 3D screen saver to work (sort of), but it was kinda jurkey and it locked up the system (had to do a hard reset) after about 30 minutes or so.
I can get the simple banner screen saver to work now, but that is about the only one so far. All of the others (I have tried most of them) simply test fine, but only blank out the screen when invoked normally.
I looked at ~.xscreensaver, and did not see any kind of 'Blank only' setting in there.
Any ideas?
BRUCE STANLEY wrote:
--- Vincent Knecht vknecht@club-internet.fr wrote:
Le Jeudi 18 Août 2005 23:45, BRUCE STANLEY a écrit :
--- BRUCE STANLEY bruce.stanley@prodigy.net wrote:
The KDE screen savers will only blank out the screen though most of them test ok when you hit the test button in the Control Center.
The Gnome screen savers work ok.
My system has a Radeon 9200SE video card and I have a ViewSonic A70f monitor.
Does anyone have a fix for this?
Is anyone out there using screensavers under KDE ?
Yes, I guess I am, "rpm -qa | grep saver" gives me xscreensaver-4.18-5.rhel4.2 and I use KDE as desktop manager (with nvidia binary driver).
FYI, xscreensaver < 4.21 is buggy (under KDE), for reference, see: http://bugs.kde.org/95187 and (I believe, can't load it right now to check): http://bugs.kde.org/63949 -- Rex
--- Rex Dieter rdieter@math.unl.edu wrote:
BRUCE STANLEY wrote:
--- Vincent Knecht vknecht@club-internet.fr wrote:
Le Jeudi 18 Août 2005 23:45, BRUCE STANLEY a écrit :
--- BRUCE STANLEY bruce.stanley@prodigy.net wrote:
The KDE screen savers will only blank out the screen though most of them test ok when you hit the test button in the Control Center.
The Gnome screen savers work ok.
My system has a Radeon 9200SE video card and I have a ViewSonic A70f monitor.
Does anyone have a fix for this?
Is anyone out there using screensavers under KDE ?
Yes, I guess I am, "rpm -qa | grep saver" gives me xscreensaver-4.18-5.rhel4.2 and I use KDE as desktop manager (with nvidia binary driver).
FYI, xscreensaver < 4.21 is buggy (under KDE), for reference, see: http://bugs.kde.org/95187 and (I believe, can't load it right now to check): http://bugs.kde.org/63949 -- Rex
Hi Rex!
I looked at both of those bug reports. The first one is closed: INVALID. The second one is closed: WORKSFORME.
Does this mean that there is noone working on this problem? No work around? Nor any updates for xscreenserver or KDE to fix the problem?
BRUCE STANLEY wrote:
FYI, xscreensaver < 4.21 is buggy (under KDE), for reference, see: http://bugs.kde.org/95187 and (I believe, can't load it right now to check): http://bugs.kde.org/63949 -- Rex
Hi Rex!
I looked at both of those bug reports. The first one is closed: INVALID. The second one is closed: WORKSFORME.
Does this mean that there is noone working on this problem? No work around? Nor any updates for xscreenserver or KDE to fix the problem?
INVALID -> Not a KDE bug WORKSFORME -> Not a KDE bug
Did you miss the replies on the kde-redhat list? We have (fixed) kdeartwork/xscreensaver packages.
-- Rex
--- Rex Dieter rdieter@math.unl.edu wrote:
BRUCE STANLEY wrote:
FYI, xscreensaver < 4.21 is buggy (under KDE), for reference, see: http://bugs.kde.org/95187 and (I believe, can't load it right now to check): http://bugs.kde.org/63949 -- Rex
Hi Rex!
I looked at both of those bug reports. The first one is closed: INVALID. The second one is closed: WORKSFORME.
Does this mean that there is noone working on this problem? No work around? Nor any updates for xscreenserver or KDE to fix the problem?
INVALID -> Not a KDE bug WORKSFORME -> Not a KDE bug
Did you miss the replies on the kde-redhat list? We have (fixed) kdeartwork/xscreensaver packages.
-- Rex
Ahh.. I see what you are talking about now...
I checked the Centos Dowload server from where I got the orininal Centos 4.2 ISOs from, and I did no see a new version of xscreensaver or kdeartwork in the updates tree.
Maybe I'm on the wrong server.
Where can I pick up the new rpms from? I don't use yum at home due to slow dial up line. I burn them on CD here at work and then I do rpm installs.....living on the edge I guess ... :-)
BRUCE STANLEY wrote:
--- Rex Dieter rdieter@math.unl.edu wrote:
BRUCE STANLEY wrote:
FYI, xscreensaver < 4.21 is buggy (under KDE), for reference, see: http://bugs.kde.org/95187 and (I believe, can't load it right now to check): http://bugs.kde.org/63949 -- Rex
Hi Rex!
I looked at both of those bug reports. The first one is closed: INVALID. The second one is closed: WORKSFORME.
Does this mean that there is noone working on this problem? No work around? Nor any updates for xscreenserver or KDE to fix the problem?
INVALID -> Not a KDE bug WORKSFORME -> Not a KDE bug
Did you miss the replies on the kde-redhat list? We have (fixed) kdeartwork/xscreensaver packages.
Ahh.. I see what you are talking about now...
I checked the Centos Dowload server from where I got the orininal Centos 4.2 ISOs from, and I did no see a new version of xscreensaver or kdeartwork in the updates tree.
Maybe I'm on the wrong server.
Where can I pick up the new rpms from? I don't use yum at home due to slow dial up line. I burn them on CD here at work and then I do rpm installs.....living on the edge I guess ... :-)
There are no fixed "stock" RHEL packages that I'm aware of. If you using packages from kde-redhat, ours are fixed. (-:
-- Rex
--- Rex Dieter rdieter@math.unl.edu wrote:
BRUCE STANLEY wrote:
--- Rex Dieter rdieter@math.unl.edu wrote:
BRUCE STANLEY wrote:
FYI, xscreensaver < 4.21 is buggy (under KDE), for reference, see: http://bugs.kde.org/95187 and (I believe, can't load it right now to check): http://bugs.kde.org/63949 -- Rex
Hi Rex!
I looked at both of those bug reports. The first one is closed: INVALID. The second one is closed: WORKSFORME.
Does this mean that there is noone working on this problem? No work around? Nor any updates for xscreenserver or KDE to fix the problem?
INVALID -> Not a KDE bug WORKSFORME -> Not a KDE bug
Did you miss the replies on the kde-redhat list? We have (fixed) kdeartwork/xscreensaver packages.
Ahh.. I see what you are talking about now...
I checked the Centos Dowload server from where I got the orininal Centos 4.2 ISOs from, and I did no see a new version of xscreensaver or kdeartwork in the updates tree.
Maybe I'm on the wrong server.
Where can I pick up the new rpms from? I don't use yum at home due to slow dial up line. I burn them on CD here at work and then I do rpm installs.....living on the edge I guess ... :-)
There are no fixed "stock" RHEL packages that I'm aware of. If you using packages from kde-redhat, ours are fixed. (-:
-- Rex
What is the link to the kde-rehat server?
What would be the mininum rpm files that I would need to update kdeartwork?
Would I need to update kdelibs and kdebase also?
Le Vendredi 19 Août 2005 23:39, BRUCE STANLEY a écrit :
--- Rex Dieter rdieter@math.unl.edu wrote:
BRUCE STANLEY wrote:
--- Rex Dieter rdieter@math.unl.edu wrote:
BRUCE STANLEY wrote:
[...]
Where can I pick up the new rpms from? I don't use yum at home due to slow dial up line. I burn them on CD here at work and then I do rpm installs.....living on the edge I guess ... :-)
There are no fixed "stock" RHEL packages that I'm aware of. If you using packages from kde-redhat, ours are fixed. (-:
Well, my local mirror of CentOS updates shows me there were a few updates to kde some weeks ago: Aug 10 09:53 kdegraphics-3.3.1-3.4.i386.rpm Aug 10 09:53 kdegraphics-devel-3.3.1-3.4.i386.rpm Jul 27 19:44 kdelibs-3.3.1-3.11.i386.rpm Jul 27 19:44 kdelibs-devel-3.3.1-3.11.i386.rpm Jul 22 13:55 kdenetwork-3.3.1-2.3.i386.rpm Jul 22 13:55 kdenetwork-devel-3.3.1-2.3.i386.rpm Jul 22 13:55 kdenetwork-nowlistening-3.3.1-2.3.i386.rpm
Perhaps using kde-redhat is not mandatory to fix screensaver behaviour.
What is the link to the kde-rehat server?
What would be the mininum rpm files that I would need to update kdeartwork?
Would I need to update kdelibs and kdebase also?
Here's the list of kde packages installed on my machine: kdepim-3.3.1-2.1 kdemultimedia-3.3.1-2 kde-i18n-French-3.3.1-2.1 kdeadmin-3.3.1-2 kdeutils-3.3.1-2 kdelibs-3.3.1-3.11 kdeaddons-3.3.1-2 kdenetwork-3.3.1-2.3 kdegraphics-3.3.1-3.4 kdebase-3.3.1-5.5 kdeartwork-3.3.1-2
Bruce, I guess you should check if you're up-to-date with regular CentOS update repository, update if you are not, then check if you still suffer screensaver issue.
--- Vincent Knecht vknecht@club-internet.fr wrote:
Le Vendredi 19 Août 2005 23:39, BRUCE STANLEY a écrit :
--- Rex Dieter rdieter@math.unl.edu wrote:
BRUCE STANLEY wrote:
--- Rex Dieter rdieter@math.unl.edu wrote:
BRUCE STANLEY wrote:
[...]
Where can I pick up the new rpms from? I don't use yum at home due to slow dial up line. I burn them on CD here at work and then I do rpm installs.....living on the edge I guess ... :-)
There are no fixed "stock" RHEL packages that I'm aware of. If you using packages from kde-redhat, ours are fixed. (-:
Perhaps using kde-redhat is not mandatory to fix screensaver behaviour.
What is the link to the kde-rehat server?
What would be the mininum rpm files that I would need to update kdeartwork?
Would I need to update kdelibs and kdebase also?
Here's the list of kde packages installed on my machine: kdepim-3.3.1-2.1 kdemultimedia-3.3.1-2 kde-i18n-French-3.3.1-2.1 kdeadmin-3.3.1-2 kdeutils-3.3.1-2 kdelibs-3.3.1-3.11 kdeaddons-3.3.1-2 kdenetwork-3.3.1-2.3 kdegraphics-3.3.1-3.4 kdebase-3.3.1-5.5 kdeartwork-3.3.1-2
Bruce, I guess you should check if you're up-to-date with regular CentOS update repository, update if you are not, then check if you still suffer screensaver issue.
I found a work-around that allows most of the screen savers to work. Some of the GL savers are still a little slugish or buggy.
I installed the latest KDE updates in the Centos 4.1 update repository but that did not solve the problem.
I ran man xscreensaver and found out a way to run xscreensaver that bypasses KDE and this got around the problem.
I did the following:
1). ran control-center and turned screensavers off in KDE.
2). created a file named xscreensaver.desktop and placed it in by ~.kde/Autostart directory.
The file contains the following lines:
[Desktop Entry] Exec=xscreensaver Name=XScreensaver Type=Application X-KDE-StartupNotify=false
3). then I created a program launcher on my desktop that runs xscreensaver-demo when I want to change to different screen savers.
Now xscreensaver startups when I login and my screen savers work!
Rex has a set of RPMs from redhad-kde that also fix the problem. I wonder if Rex could make them available on the Centos 4.1 updates repository?
On Sun, 2005-08-21 at 14:54 -0700, BRUCE STANLEY wrote:
--- Vincent Knecht vknecht@club-internet.fr wrote:
Le Vendredi 19 Août 2005 23:39, BRUCE STANLEY a écrit :
--- Rex Dieter rdieter@math.unl.edu wrote:
BRUCE STANLEY wrote:
--- Rex Dieter rdieter@math.unl.edu wrote:
BRUCE STANLEY wrote:
[...]
Where can I pick up the new rpms from? I don't use yum at home due to slow dial up line. I burn them on CD here at work and then I do rpm installs.....living on the edge I guess ... :-)
There are no fixed "stock" RHEL packages that I'm aware of. If you using packages from kde-redhat, ours are fixed. (-:
Perhaps using kde-redhat is not mandatory to fix screensaver behaviour.
What is the link to the kde-rehat server?
What would be the mininum rpm files that I would need to update kdeartwork?
Would I need to update kdelibs and kdebase also?
Here's the list of kde packages installed on my machine: kdepim-3.3.1-2.1 kdemultimedia-3.3.1-2 kde-i18n-French-3.3.1-2.1 kdeadmin-3.3.1-2 kdeutils-3.3.1-2 kdelibs-3.3.1-3.11 kdeaddons-3.3.1-2 kdenetwork-3.3.1-2.3 kdegraphics-3.3.1-3.4 kdebase-3.3.1-5.5 kdeartwork-3.3.1-2
Bruce, I guess you should check if you're up-to-date with regular CentOS update repository, update if you are not, then check if you still suffer screensaver issue.
I found a work-around that allows most of the screen savers to work. Some of the GL savers are still a little slugish or buggy.
I installed the latest KDE updates in the Centos 4.1 update repository but that did not solve the problem.
I ran man xscreensaver and found out a way to run xscreensaver that bypasses KDE and this got around the problem.
I did the following:
1). ran control-center and turned screensavers off in KDE.
2). created a file named xscreensaver.desktop and placed it in by ~.kde/Autostart directory.
The file contains the following lines: [Desktop Entry] Exec=xscreensaver Name=XScreensaver Type=Application X-KDE-StartupNotify=false
3). then I created a program launcher on my desktop that runs xscreensaver-demo when I want to change to different screen savers.
Now xscreensaver startups when I login and my screen savers work!
Rex has a set of RPMs from redhad-kde that also fix the problem. I wonder if Rex could make them available on the Centos 4.1 updates repository? _______________________________________________
Need to be fixed in RHEL-4 before they will be be fixed in CentOS-4.