CentOS 5 :: Lock Screen After System Resume From Suspend / Hibernation?
Mar 21, 2009
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.
i dont know why my system dosnt resume from suspend sstate.i it goes in suspend state.it doesnt resume .i have to poweroff then restart it again.and when i get logged in it gives me Following Error: Resume problem: Your system did not appear to resume correctly from Suspend/Hibernate. This may be a driver problem or a hardware problem. Check the GNOME Power Manager Manual for common problems.
do you think it is because of batterry.i have a problem in my By Battery .IN DOS operating system.when i check my battery icon . A red Cross constantly blink on lower right side of the battery and it says (your Battery consider Replacing).i have notice one thing .And My battery timing hias become Decreased. Do you think this Resume problm is cause of battery problm.Or there is some problm in my Os software.
My computer have ATI X600 graphics card installed, and I installed CentOS5.3.
Every time I suspend my computer and then resume it, it seem the graphics card can't resume and the monitor says 'no signal', but the system still responses, I can use keyboard.
Is there any configuration I can't do to make it resume normally? I've searched a lot in Google but can't find out any one else run into the same problem.
My laptop beeps three times during the resume from hibernation. How can I disable this beeping. I use CentOS 5.3. Interestingly, this issue did not occur when I used CentOS 5.2 on the same laptop last year.
i am trying to write a script that switches the system to hibernation automatically at a particular time and again wakeup after some fixed amount of time. I found that at /etc/acpi there is a hibernate.sh but i cudn't find resume.sh .
I am using Ubuntu 9.10 on an Acer Aspire 5050 (5052AWXMi model) and I am experiencing some problems of system Hibernation and Suspend.When I put my laptop to sleep mode (suspend) then after pressing a button system tries to open but what I get it is only a black screen.The same problem appears also when I am trying to hibernate my system. After opening my laptop again I am getting a message < waking up. Please wait > but then I get again a black screen.
When I close my laptop lid (it goes into suspend mode). When I open it again, I can't see anything but a black screen. I have to reset the computer manually to accessUbuntu again.On a related note probably.. for 'some' screensavers, when I click to re-access my desktop, the screensaver freezes, but I can't see the unlock dialogue. I can however still type my password and it will unlock, I just can't see what I'm doing
Up until a couple days ago, my computer had no problems suspending to ram. However, now when I suspend, and later hit a key on the keyboard (usually space) to resume, all I see is an illuminated black screen. I can't even open a tty via Ctrl+Alt+F1. I can however ssh into the machine.he only possibility I can think of is that I am no longer running kdm. I just use "startx" to star an openbox-session.
I've been trying to find an answer to the following problem : whenever my PC is put in Suspend/Hibernate mode, it fails to recover when pushing the power button. This happens both with automatic suspend or manual suspend. I've been reading this problem, and mine is quite similar, but no solution is given.
uname -rmi 2.6.18-194.11.4.el5 x86_64 x86_64 PS: this computer is not connected to Internet, no update possible.
I am having a problem with suspend in F15. While the computer enters and resumes from suspend extremely fast (basically instantaneous), the whole system seems sluggish and unresponsive afterwards. The mouse cursor is lagging and some key strokes are omitted when typing. The animations in Gnome 3 are also very non-fluid compared to how they were before suspend. The only way I have found to return to normal operation is to reboot the computer. I have tried 32 and 64-bit versions of Fedora 15 with the problem existing in both. I also tried the latest version of openSuse (Gnome 2.32) just to see if this problem persisted and I can confirm that it did. Perhaps this indicates a kernel-related problem that should be reported as a bug somewhere else?
lspci: Code: 00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11) 00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11) 00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11) 00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11) 00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11) 00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11) .....
Title says it all. I close my laptop lid. It goes into suspend mode. I open it up again, the computer powers up... and I see a black blank screen. No key combinations seems to bring anything back.
I have an ati 2600 mobile. I am running fedora 10 64 bit. If I have compiz enabled when I resume from suspend I just get a black screen with some garbed colors and I have to hold the power button to shut it off. I have tried turing sync to vblank off. It works fine with no compiz. Is there anyway I can get resume working with compiz enabled?
I'm running Debian Squeeze on a Dell Studio 1558 laptop, and I have my laptop set to suspend when my lid is closed. Resuming from suspend seems to work but the screen remains blank, forcing me to hard reboot every time. Upon reading this thread
Code: Tue Jun 21 23:07:12 AKDT 2011: performing suspend Tue Jun 21 23:07:28 AKDT 2011: Awake.
Lately I upraded my Debian using aptitude update/aptitude upgrade - including installing a new kernel (3.0). Since this upgrade I have strange problem with networking. When I suspend my computer and resume it, I do not have connectivity with network:
$ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. From 192.168.1.1 icmp_seq=1 Destination Host Unreachable
I upgraded to latest 10.04 live x64 desktop today. Clean, fresh install.Before I was using 9.04 and had the same issue at first.I don't want the password lock screen when resuming from suspend.I disabled everything, lock in screensaver settings, all lock entries in gconf-editor. I also tried setting LOCK_SCREEN in /etc/default/acpi-support to false.Nothing helps Is this maybe a bug, since it's still beta? I don't know what else to do
I'm running Debian Squeeze on a Dell Studio 1558 laptop, and I have my laptop set to suspend when my lid is closed. Resuming from suspend seems to work but the screen remains blank, forcing me to hard reboot every time. Upon reading this thread:
Tue Jun 21 23:07:12 AKDT 2011: performing suspend Tue Jun 21 23:07:28 AKDT 2011: Awake. Tue Jun 21 23:07:28 AKDT 2011: Running hooks for resume
I recently upgraded to Lucid (x86_64) on an HP dv2 laptop, and after doing so, the system will not resume after a suspend (with fglrx installed from the "official" repositories). After reading a lot about the problem, I have seen that updating to the latest ATI driver had fixed this issue for some, so I would like to try that.
I am following the guide at at cchtml.
First, I tried installing the Ubuntu-X team's drivers. However, after (successfully) adding their repository, an update does not fetch their packages:
Code:
It looks like both the xorg-edgers and ubuntu-x-swat repositories are being ignored? (If I'm reading that correctly.) If I open the window System->Administration->Software Sources, I can see that the ubuntu-x-swat repository is checked, so I'm confused why it's being ignored.
If I try to demand the fglrx-installer package, I get an error that it cannot find this package.
Code:
I have the same issues for xorg-edgers and ubuntu-x-swat.
Finally, if I try to build the official ATI v10.7 drivers myself, I get an error that Linux is an unrecognized architecture!
Code:
I have installed all preliminary packages suggested in the guide:
Code:
I really can't understand why I'm unable to build the package from ATI myself.
I have a desktop system (P55-USB3 + Core i7 + Ubuntu 10.10) that fails to suspend/resume from memory. So I'm trying to diagnose the problem. The first obstacle was easy enough --- when I put the system to sleep to memory, the computer comes back alive right away. A look at /var/log/kern.log revealed that one USB device (usb10) failed to suspend, and from there I was able to pin it down to the USB3 controller in the BIOS. Disabled that and this problem disappeared.
Now, I'm stuck with the second obstacle. The computer successfully goes into the suspend mode, but it hangs during resume. The monitor doesn't get any video signal, and it fails to respond to ping (netconsole doesn't work either.) After a forced reboot (that involves unplugging the power cable), /var/log/kern.log doesn't contain any interesting entries. All the pm_test modes from freezer to core succeed (I followed [URL] I've also tried pm_trace (https://wiki.ubuntu.com/DebuggingKernelSuspend) but again kern.log nor dmesg contains anything after the suspend. Either the write didn't survive the forced power off, or the resume is failing even before that. The motherboard doesn't have a serial port nor firewire, so getting kernel logs through them is not a possibility, either.
I have set up minimal debian installation with pekwm, tint2, xscreensaver and friends. When I press Fn+F4 on my thinkpad or run pm-suspend from root terminal, it suspends just fine (yay), but when I resume, I get instantly logged in into my account. What I'd like to have, is that xscreensaver locks my session after suspend, so that I have to type in my password in order to continiue working.
PS. In /etc/default/acpi-support I have LOCK_SCREEN=true
I recently upgraded from Lucid to Maverick I can't seem to disable screen lock after resume from suspend. It's a minor annoyance, but still a considerable annoyance to have to enter my password every time the computer wakes up.
I've thusfar
1 - changed screensaver preferences to not lock
2 - set the gnome_keyring_hibernate, gnome_keyring_suspend, hibernate, and suspend, values all to false in gconf-editor
3 - commented out the line LOCK_SCREEN=true in /etc/default/acpi-support
BUT am still being prompted for a password every time the computer wakes up from suspend. I'm stumped, what could I be forgetting?
I am using uswsusp / s2disk and it hibernates fine. Then, on resume, it apparently completes the resume (reaches 100%) but it never progresses to the actual resumed system and gets stuck on this screen: Before upgrading from 9.04 to 10.04 it worked fine. It does not anymore.
I'm having trouble resuming from hibernation. The splash screen loads up with "Resuming from /dev/sda6" (this is the correct partition) and the HDD light shows it's reading the drive. It then stops reading and the loading animation starts up (I'm running Lucid). Then nothing, just the animation. I recently updated initramfs-tools to 0.98ubuntu2~lucid as hibernation wouldn't work at all with the old version (see [URL]). I've also installed this script because of errors on hibernation.
Running Opensuse 11.1 on an HP laptop. When I resume from hibernation or standby, I usually have to wait for about a minute for the wireless card to find my router. Is there any way to speed up this time to connect process ?
Interestingly when I boot from cold, the wireless connection is most times ready to go as soon as the boot has finished. So just wondering how I can make things quicker for resume from standby or hibernation
ASUS P5Q Deluxe, Intel Core 2 Duo, GeForce 8800, 4GB RAM, USB keyboard and mouse never had problems with suspend and hibernation in Ubuntu. Until the latest version 10.10. Both before and after installing the proprietary Nvidia drivers, the system enters the sleep and hibernate but I can not wake up properly. Specifically, while it looks as it starts up, but not fires up the X server. Oddly - operate only CTRL + ALT + F1-12. You can switch to the text cosole, see the "incentive" to sign but other keys do not work and nothing can be entered. Not working CTRL + ALT + DEL as well, so you need to turn off the system power.
I just installed openSUSE 11.3 but cannot get hibernation (or suspend to disk) working. It does not go to hibernation but instead it just locks the screen. The relevant error in /var/log/pm-suspend.log looks like below.
According to /usr/lib/pm-utils/sleep.d/30s2disk-check '/dev/dm-1' must be the swap partition. What i don't understand is that why the error says swap partition is not active. There is no error for swap partition during boot time. Boot message says that swap partition is activated.
/usr/lib/pm-utils/sleep.d/06autofs hibernate hibernate:Shutting down automount ..done success. /usr/lib/pm-utils/sleep.d/30s2disk-check hibernate hibernate:INFO: checking for suspend-to-disk prerequisites... ERROR: resume partition '/dev/dm-1' not active, can not suspend
[code]...
Below is fdisk -l information for the disk which has swap partition.
/dev/dm-0p1 1 2089 16779861 82 Linux swap / Solaris Partition 1 does not start on physical sector boundary. /dev/dm-0p2 2090 3395 10482431+ 83 Linux
Using 64Bit Ubuntu 10.04 on a VAIO VGN-FW373J. ATI Mobility Radeon HD 3650. This relates to Bug 451282. If I install the ATI 3D Drivers, the dimming problem goes away, but a host of other bugs crop up. After a resume from screen lock, suspend, or hibernation, the screen is reduced to graphical chaos. There are also hibernation errors. This bug is worse than the dimming bug, so I've uninstalled the 3d ATI drivers. If I can't find a workaround, I may have to look for a different Linux Distro or be content with Windows 7 on this particular laptop.
My suspend-to-disk and suspend-to-RAM stopped working months ago. I've grasped at straws about why ever since, but I really don't think it's a software problem, because I've reinstalled my system (MEPIS) repeatedly. What sort of hardware failures could cause this? What should I be looking for? I notice that at boot, Linux always says "no resume image found," even if I left the system in suspension or hibernation. I can post parts of the dmesg if someone tells me what to look for; I can't display the whole thing because it's too long to fit here.
When i log in as root, and try to click the lock screen button, lock screen doesnt work? Is it disabled by default?is there anyway to lock screen when logged in as root
