similar to: screen saver unlock dialog window is not visible in clone mode

Hi all, I am using centos 5. I need the screen to always be on. I have gone into System -> Preferences -> Screen saver and then I unchecked the "Activate screen saver when computer is IDLE" setting. I also edited the xorg.conf and commented out the dpms line. However, my screen is still going into some kind of screen saver. What else is there to disable? Thanks, Jerry

I have a user who freshly installed CentOS on their desktop. They also installed VMWare 6.02. When they click the mouse on their Linux desktop, the screen saver properly activates. But, when they click the mouse in their VMWare session, the Linux screen saver never activates. This has been tried for both VMWare Player and Workstation. I don't know if it makes any difference, but the

My dell 8200 has centos 4.1 installed. Everything works great except the X screen saver. when it kicks in my screen goes WHITE and not what ever the selection is for the screen saver (star field, blank screen, etc..) When I do Applications, preferences, screen saver it says "The XScreenSaver daemon doesnt seem to be running on display 0:0? Launch it now?" Cancel/ Ok After that it

In Centos 4.1 I am having to user the Xscreen saver as a work around due to the KDE screen saver not working properly. Has the KDE screen saver been fixed/updated in Centos 4.3, or do you still need to use xscreensaver instead? -------------- next part -------------- An HTML attachment was scrubbed... URL:

How does one access the properties associated with the blanking CentOS does at init3? How would I disable this for example? Thanks! jlc

I have installed Centos 6.2 on: 1) Tyan S2892 with ATI on board Rage XL graphics ( Centos x86_64 version), 8GB memory, 3ware Raid array 2) Supermicro Dual Xeon Single core, old machine, with ATI onboard Rage XL graphics (Centos i386 version), 12GB memory, 3ware Raid array Both machines exhibit the same error. While trying to select a screen saver (clock or blank screen) the application seg

I am running: Samba 2.2.4 client On my workstation Red Hat version 7.2 KDE desktop Connecting to our Microsoft network. This works fine. However when I turn on the screen saver with password and the screen locks I cannot get back in (none of my passwords work, including the root password and I must use the power switch to restart the workstation). Does anyone know what password the screen

I know this is a little off topic but I know a lot of people use Samba to authenticate pcs and this may be useful. I was wondering if anyone has written a screensaver for Win95/98 that is password protected based on the current user, who has already been authenticated through Samba. So that if a user forgets to log out of the machine the screen saver comes on and can only be disabled by the user

My screen saver crash both in gnome and kde X windows when open the screen saver. I guess that some package needed is not installed. I reinstall the gnome-screen but it still crashs. How can I check which package is not installed? -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello all, this mail is related to a post by Axel Schöner that I found at http://article.gmane.org/gmane.comp.emulators.xen.user/40621 when I was searching the WEB about solutions to my problem. I would like to confirm that VT-d with XEN 3.3 kernel 2.6.18.8 on mainboard Intel DQ45CB seems to be broken. Survey (details are down below) --------------------------------------- Whenever I boot my

Hi Friends, I am trying to configure screensavers settings on Gnome and KDE running Centos 5.x 32-bit environment. I need to prepare a script which will be push by Puppet and this script should be able to change settings like idle_delay, set customized password-protected screen saver, enabling lock etc.. I have tried below commands for Gnome and somehow the settings are not taking place. The

I started a yum update this afternoon and there were lots of updates (182) so I presume it's the 4.5 update. Now I can't unlock the session with my password! Any ideas? (no caps lock is not on!) -- Peter Crighton

There is an error path in ocfs2_quota_write() that doesn't unlock &gqinode->i_mutex(). That seems unintentional. Found by smatch (http://repo.or.cz/w/smatch.git). Compile tested. regards, dan carpenter Signed-off-by: Dan Carpenter <error27 at gmail.com> --- orig/fs/ocfs2/quota_global.c 2009-04-07 19:34:22.000000000 +0300 +++ devel/fs/ocfs2/quota_global.c 2009-04-07

Author: mec Repository: /hg/zfs-crypto/gate Revision: a0fbe099c4f0d3056d650d09bac1da2e8b3db277 Log message: 6337677 segdev_softunlock fails to unlock Files: update: usr/src/uts/common/vm/seg_dev.c

We should unlock here and also decrement the number of &map->users. Signed-off-by: Dan Carpenter <error27 at gmail.com> --- I'm not very familiar with this code. Please review carefully. diff --git a/drivers/xen/gntdev.c b/drivers/xen/gntdev.c index 017ce60..b0f9e8f 100644 --- a/drivers/xen/gntdev.c +++ b/drivers/xen/gntdev.c @@ -662,7 +662,7 @@ static int gntdev_mmap(struct

We should unlock here and also decrement the number of &map->users. Signed-off-by: Dan Carpenter <error27 at gmail.com> --- I'm not very familiar with this code. Please review carefully. diff --git a/drivers/xen/gntdev.c b/drivers/xen/gntdev.c index 017ce60..b0f9e8f 100644 --- a/drivers/xen/gntdev.c +++ b/drivers/xen/gntdev.c @@ -662,7 +662,7 @@ static int gntdev_mmap(struct

We should unlock here and also decrement the number of &map->users. Signed-off-by: Dan Carpenter <error27 at gmail.com> --- I'm not very familiar with this code. Please review carefully. diff --git a/drivers/xen/gntdev.c b/drivers/xen/gntdev.c index 017ce60..b0f9e8f 100644 --- a/drivers/xen/gntdev.c +++ b/drivers/xen/gntdev.c @@ -662,7 +662,7 @@ static int gntdev_mmap(struct

We recently added locking in fill_balloon() but there was one error path which was missed. Signed-off-by: Dan Carpenter <dan.carpenter at oracle.com> --- Only needed in linux-next. diff --git a/drivers/virtio/virtio_balloon.c b/drivers/virtio/virtio_balloon.c index f70151b..1c50e98 100644 --- a/drivers/virtio/virtio_balloon.c +++ b/drivers/virtio/virtio_balloon.c @@ -153,9 +153,10 @@

We recently added locking in fill_balloon() but there was one error path which was missed. Signed-off-by: Dan Carpenter <dan.carpenter at oracle.com> --- Only needed in linux-next. diff --git a/drivers/virtio/virtio_balloon.c b/drivers/virtio/virtio_balloon.c index f70151b..1c50e98 100644 --- a/drivers/virtio/virtio_balloon.c +++ b/drivers/virtio/virtio_balloon.c @@ -153,9 +153,10 @@

* Greg KH <gregkh at linuxfoundation.org> wrote: > > >It's: > > > > > > d6abfdb20223 x86/spinlocks/paravirt: Fix memory corruption on unlock > > > > Yes, This is the original patch. Please note I have taken out the > > READ_ONCE changes from the original patch to avoid build warnings > > mentioned below. > > (Those READ_ONCE