CentOS 5 :: What Program Runs The Session Lock And Screen Saver For Gnome And KDE On 5.5
Jul 27, 2011
what program runs the Session lock and the screen saver for gnome and KDE on centos 5.5. But most importantly id like to know what the config file for the screensaver/session lock is called and where its most likely located.
I have 2 servers, I set the first one up so that I can remote to it and connect with VNC over ssh by following:[URL]ServerThe 2nd server I did the same, but I cannot connect! When I do, vncviewer prompts for a password and then opens a window of the correct size, but it is all white and then my ssh session is locked! I can't enter any more commands, I have to kill the session.
When I hit Alt+Ctrl+L my system is starting the ScreenSaver but not locking the screen. The keybinding is correctly set. This is happening in only root account but in another user account it works perfect !
What happens is that I resorted to deleting my .kde directory after my kid destroyed my profile where title bar, menu, konsole get broken. After deleting, I login again thus regenerating the .kde directory. To avoid my kid from messing my desktop, I tried to lock it. It does not lock.
It just need a KDE full restart perhaps since when I login the other day, it now works.
I'm updated to Slackware current for almost a month already and have not played a lot on KDE desktop (busy programming stuff).
However, on day I tried to lock the desktop in KDE to avoid the kid from destroying my cool desktop setting, but it didn't lock. Cool, so I tried screen saver and add an option to lock the screen.
When I test screen saver, it displays. But when I wait for 1 minute(I set it that way), it doesn't fire up. Not even after 15 minutes which I think the default.
It usually work before (several months ago) using the lower version of KDE. It is just last Saturday that I noticed it.
I tried to dig the profile management but I could not find anything relevant there.
I have a new install of xubuntu 10.10, everytime I try to choose a screensaver the user session crashes back to the user login screen? The video card is an onboard ATI Savage on a Gigabyte motherboard.
So I have a laptop that I built and installed 10.10 on.
The laptop is used by a minor who needs to be off it at a certain time but can't seem to keep track of time.
I have installed that Nanny program called "Parental Control" through the software center but its not quite what I want. It says it locks out the session...but it seems pretty much useless.
So what I'm looking for is software that would not just lock the session and require them to lock the computer but to literally lock the laptop so they won't be able to use it at all until the time lapses or the admin password is entered.
On my 11.3 desktop I was annoyed by what I thought was the screen saver locking my session after an idle period, requiring my password to unlock. Well, I didn't want this behaviour and it wasn't supposed to do that, I had disabled every place in the desktop configuration that seemed to be related. I even looked into the KDE4 rc files with a text editor and they all seemed to be in order.
Eventually after some searching I found the answer: It's the setting "lock screen on resume" in the advanced settings > power daemon. Once I turned it off, it was fine; this desktop doesn't need suspend+resume anyway.
It seems that this is not a case of counterintuitive naming; it seems that in some configurations there is a bug where a stray event can trigger a screen lock by the powersaved (?). I don't really understand it, but you can start your investigation here if you are interested:
I am running a SLC 5.2 with a Gnome 2.16 desktop setup for all the class room terminals. Where can I determine the status of the screensaver. The value could then be periodicaly tested within a "cron" script. If screen saver was running then a "skill" could then be called to force a complete logout releasing the terminal for another student.
My Gnome screensaver doesn't work, although it once did.
I have searched for a solution to this problem but no luck. I am running FC 11 and out-of-the-box gnome. At first the screensaver worked normally, shutting off the screen after 5 mins. Now it does not do so. I found the following command line suggestion in the forums, and it looks like it may point to a problem -- the screensaver is inactive, but how to make it active? I may be misunderstanding the term inactive, of course. Logically, the screensaver would have to be inactive if I am typing a command.
In any case, the query command shows:
Just in case the screensaver really was not running, I tried this command (which I found in another post):
But the query returns the same thing as before.
The only thing I can think of that might be an issue is that using the "appearances" background facility I added a couple dozen pictures that I thought I might use as screen background. Not long after that I discovered that my screen did not go black after 5 mins as expected. Not sure this correlation has any causal meaning, however. I then tried various things, finally returning to the plain (blue) default. That seemed to fix it for a short while, then after a couple of days, the bad or non-behavior returned -- the screensaver does not work.
(update -- I removed all the extra background pics and it makes no difference.)
My system runs all the time, but I don't want the screen to be on all the time.
I installed openSUSE 11.4 on HP elitebook 2560p few days ago (using KDE live CD). In general system is working fine, but steel I cannot resolve couple of really annoying issues: 1. I've created encrypted partitions for swap and home during OS installation. As result the system keep asking for passwords for each of encrypted partitions before show login screen. That leads to situation when I have to type 3 passwords during each boot/reboot. I was using the same configuration (swap and home were encrypted) on Ubuntu 11.04 and there both encrypted partitions were mount automatically with no password typing after login to the system. Could you please tell how I can configure the same behavior on openSUSE 11.4 ?
2. I've enabled auto screen lock after 5 mins being inactive. As result when I going back to laptop and to unlock the screen the system shows login screen (default login screen with user selection). But when user and password filled in I click login it creates entire new KDE session. Therefore all staff that was open before screen lock is gone. However old session is still in the system (it appears in output from 'w' command).
If I remain 'connected' (with the KVM) to the linux machine the gnome screen saver cuts in and the system remains 'as is' until 'woken up' with the mouse or keyboard. However, if I switch to another machine using the KVM, within a short time (maybe even minute or two) the linux machine goes dead. Now it has not crashed, as I can log in from a remote machine and do anything I need from a terminal, but the machine seems not to respond. I can't even use ctrl-alt-fn to switch to a console screen.
I initially tried entering telinit 3 from a remote machine but it made no apparent difference. However, if after telinit 3 I then killed the Xorg process and later issued a telinit 5 the X server restarted, but with a curious black 'notch' at the top of the screen. I am using an NVIDIA GeForce 7600 GS graphics card. I am now adding the backtrace from Xorg.0.log. It seems that when the KVM switches to another machine for more than a very short time the X server crashes.
USB driver bug exposed as "Linux plug&pwn" or this link.Two choices [GNOME, Fedora 14]:
1 - use the gnome-screensaver
2 - use the "switch user" function [gnome menu -> log out -> switch user]
So the question is: which one is the safer method to lock the screen, if a user leaves the pc? Is it true, that using the  method is safer?Why do i think this? - The gnome-screensaver is just a "process", it could be killed. But if you use the log out/switch user function, it's "something else". Using the "switch user" function, could there be a problem like with the gnome-screensaver? Could someone "kill a process" and presto...the lock is removed?Could the GDM [??] "login windows process" [e.g.: a picture of it] get killed and the "lock" gets owned?
p.s.: if the  method is safer, then how can i put an icon on the GNOME panel, to launch the "switch user" action by 1 click?
This is regarding the 'screen' utility. I use an utility called 'HummingBird Exceed' to get the XSession of a linux client on my windows desktop (basically it uses XDMCP). But the pain is that at the end of the day, when I close Exceed, the session gets destroyed. I did lot of searching on the web to know how the save and restore session in Exceed, but failed. However, I found that 'screen' is the utility which keeps the session intact even when you logout. So, I did the following:
a. Logged into the machine using Putty (terminal emulator).
b. Started 'screen'.
c. Issued the command: /usr/bin/gnome-session
I got the XSession on the Exceed and started working. I opened three or four gnome-terminals. But when I logout of exceed(and detach from the screen), the screen displayed a message saying that 'Connection to XServer was lost". Hence I could not restore to this session when I reattached to the screen. how do I use 'screen' so that when I attach to the screen on which I had started gnome-session, it attempts to connect to the Xserver and open the session as it was before detaching?
when i want to opening lock screen and after entering password take too long time to open lock scrren and i can not find what is the problem.i can not find any clue in my logs, so this is some of syslog :
Code: Select allDec 17 21:19:34 ali-deb gnome-session: (gnome-shell:2421): Gtk-WARNING **: Symbolic icon /firstname.lastname@example.org/icons/numlock-disabled-symbolic.svg is not in an icon theme directory Dec 17 21:19:34 ali-deb gnome-session: (gnome-shell:2421): Gtk-WARNING **: Symbolic icon /email@example.com/icons/capslock-disabled-symbolic.svg is not in an icon theme directory Dec 17 21:19:34 ali-deb gnome-session: (gnome-shell:2421): GLib-GObject-WARNING **: /tmp/buildd/glib2.0-2.42.1/./gobject/gsignal.c:2579:
I've googled for the answer to this but every thread has the same answer "don't log in as root". For once I'd like an actual answer to the question if possible. All of the jobs that I run are all through the root account and I'm constantly using ssh into other workstations and servers to change config files or whatnot. I'd like to be able to lock the screen when I take short breaks or head out for the day while being able to leave jobs running. For example I am currently backing up a server onto another one and would prefer not having to stop the jobs when I leave for the day(there's over 400GB to move).
Is it just me, or has 'lock screen' stopped working in a recent update? I updated my install today and after rebooting I can't lock the screen... the screen saver doesn't lock it and if I select 'lock screen' manually from the menu then... nothing happens.
I even created a new user in case there was something weird in my configuration, but logged in as them I can't lock the screen either.
This is obviously a bit of an issue in an office environment as I don't want to have to log out every time I leave my desk.
For the sake of security, I want the screen to be locked after the system is resumed from suspend or hibernation. Now the only way I can do this is to check the options "Lock screen when screen saver is active." in the screensaver preference. But this method is annoying since I have to type the password to quit the screensaver. Is there other way to do this? Thanks.
The above subject was one of the options I was given on the boot up of Ubuntu 11.04 (natty) after the message 'Your screen graphics card and input device could not be detected correctly'
I OK'd the message to run in low graphics mode.
The question is: What's causing this? I've had a look through previous posts with (apparently) the same problem, but the methods used were inconclusive, even though in some cases the problem was resolved.
Nvidia was mentioned - about deleting all references to it in Packet manager. Would this work? And if so, why?
This was one of the lines of an LSPCI command in terminal...
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility U1
I tried to install Ubuntu in my P3 computer so i can play with it, everything works fine but not after i reboot it. Now i got the user and password window on the desktop and drop-down-list of sessions, language, keyboard, date & Time and Shutdown button at the bottom.
Drop-down-list session: Recovery Console Ubuntu Desktop Edition Ubuntu Desktop Edition (Safe Mode) User Defined Session
With these 4 options, the third one which is the safe mode is the only option I was able to get through. Others are just desktop without toolbar or anything, right click with folder option are working though. Recovery console is just the CLI window but I don't know anything about Linux commands.
I have recently installed 11.04 natty on Intel Core i3-2100 3.1 GHZ using its own graphic accelerator. When the screen is idle for a long time, more than 1 hour, I get a black screen with the mouse arrow but nothing else. the mouse moves the cursor and Ctl+Alt+F1 does work. How to fix this problem?
I've been a Linux user for years but just recently I decided to take the plunge and use Ubuntu Linux as my primary OS (with Windows on the side for any games that don't run well in CrossOver Games).
Anyway, one thing I was curious about was whether or not I could get some of my Windows screen savers to work on Linux. Specifically I had been using "Blue Screen", a cute little ss made by SysInternals that emulates various versions of Windows BSODs.
The file comes as a .scr file (like all Windows screen savers). I wanted to know if there was any program that converted .scr files into Linux compatable screen savers. If not, that's still OK as I've now been rocking "Electric Sheep"!
I'm running Ubuntu Linux 8.10 on a HP DV9000 with an 1.7GHz Intel Centrino Duo processor, 2GB ram, and an nVidia GeForce Go 7600 graphics card.
I'm using 10.04, and gnome-terminal GNOME Terminal 2.30.2 . I have irssi running on screen session on remote host. And I've been struggling for quite many days to configure it to produce either visual feedback or ring terminal's bell when I receive a private message or one of those that are highlighted.
My compiz settings window in General tab has 'Audible bell' checked.
My GNOME terminal has 'Terminal bell' checked.
I also added 'set bell-style audible' to my ~/.inputrc
And I also tried to manually load pcspkr module into my kernel.
No of the above helped or at least I haven't been able to notice any difference.
I also used some commands for irssi to produce bell sign.
When I logout Gnome session, the whole system reboots. I found this command, "gnome-session-save --kill", it restarts the system, too.That's what is happening with two of my Dell destops(CentOS 5.6). How could this happen?