Gnome3: Cannot set laptop lid close action

I've checked the lid closing sensor with watch /proc/acpi/button/lid/LID/state and the status changes without problems, but i can't set the lid closing action in gnome-tweak-tool or under power options. The laptop suspends only when an external monitor is not connected, i want to change it so it always suspends when the lid is closed.
How can I fix this?
Screenshots
power options
gnome-tweak-tool
Last edited by klingt.net (2014-03-19 20:28:05)

Seems to be a bug in gnome, gnome-tweak-tool outputs the following messages:
INFO : GSettings missing key org.gnome.settings-daemon.plugins.power (key lid-close-battery-action)
INFO : GSettings missing key org.gnome.settings-daemon.plugins.power (key lid-close-ac-action)
INFO : GSettings missing key org.gnome.settings-daemon.plugins.power (key lid-close-suspend-with-external-monitor)
I added the keys manually to the schema but gnome-tweak-tool show this error when i try to start it with the new keys:
GLib-GIO-ERROR **: Settings schema 'org.gnome.settings-daemon.plugins.power' does not contain a key named 'lid-close-battery-action'
There are more people having a similar problem.
Last edited by klingt.net (2014-03-23 10:12:03)

Similar Messages

[SOLVED] Power button and laptop lid close rules not followed (KDE)

I'm using KDE 4.9.1, and the rules I set for the power button and lid close events in the KDE power management settings are not followed.
Currently, I have the power button press event set to trigger hibernation, and the lid close event set to turn off the display. Instead, the power button causes the laptop to power down immediately, as if the 'poweroff' command was issued. Closing the lid causes the system to suspend to ram.
This problem seemed to have started when I installed 'laptop-mode-tools' and 'acpid'. The problem persisted even when I uninstalled the said packages from the system. Most solutions on the internet involve adjusting the contents of files in /etc/acpi/, but that directory does not exist on my system. I also tried deleting the power management configuration files in the ~/.kde4/share/config directory, but that didn't fix the problem either.
Hibernation works if I choose 'hibernate' from the KDE menu.
Thanks for any help.
Last edited by rb3 (2012-09-28 05:46:56)

That's not a good solution.
Changes in systemd default behaviour are reasonable. It guarantees that if your graphical enviroment has no suspend support, it will still suspend when the lid is closed.
For example, closing the laptop lid at KDM login screen will now suspend the laptop. I remember a topic when someone nearly killed his notebook battery with overheat in that situation (the laptop did not suspend when the lid was closed at kdm screen).
This change also brings native (non-acpid) suspend support to lighweight desktop enviroments.
The source of the «double suspend» problem is in acynchronized update of systemd and KDE.
Updating KDE to 4.9.2 (which will be released in several days) will fix this without editing the config file.
Make sure you restore the original logind.conf after updating to KDE 4.9.2.
See:
http://lists.freedesktop.org/archives/s … 06604.html
https://bugs.kde.org/show_bug.cgi?id=307412
https://git.reviewboard.kde.org/r/106533/

[SOLVED] Laptop Lid Close

I've been using arch on my laptop for a while now and have been having problems when I close the lid on my laptop. What I want my a laptop to do is nothing except simply turn the screen off when the lid is shut. However, at the moment when I close the lid, it doesn't suspend or sleep or anything, the screen turns off, but when I open the lid, I am presented with a black screen(lit up). I have to turn my laptop on and off to use it again, or change tty and then restart the x-screen. Any help would be much appreciated. Thanks in advance.
Last edited by compty (2013-12-30 08:15:22)

Thanks,
I'm using acpid to handle the event and in the /etc/systemd/logind.conf I have only the following line uncommented:
HandleLidSwitch=ignore
Which to my understanding should prevent systemd from controlling the event yes?
And at the moment I currently have the default acpi setup,
so the anything event:
# Pass all events to our one handler script
event=.*
action=/etc/acpi/handler.sh %e
And the following hander.sh:
#!/bin/bash
# Default acpi script that takes an entry for all actions
case "$1" in
button/power)
case "$2" in
PBTN|PWRF)
logger 'PowerButton pressed'
logger "ACPI action undefined: $2"
esac
button/sleep)
case "$2" in
SLPB|SBTN)
logger 'SleepButton pressed'
logger "ACPI action undefined: $2"
esac
ac_adapter)
case "$2" in
AC|ACAD|ADP0)
case "$4" in
00000000)
logger 'AC unpluged'
00000001)
logger 'AC pluged'
esac
logger "ACPI action undefined: $2"
esac
battery)
case "$2" in
BAT0)
case "$4" in
00000000)
logger 'Battery online'
00000001)
logger 'Battery offline'
esac
CPU0)
*) logger "ACPI action undefined: $2" ;;
esac
button/lid)
case "$3" in
close)
logger 'LID closed'
open)
logger 'LID opened'
logger "ACPI action undefined: $3"
esac
logger "ACPI group/action undefined: $1 / $2"
esac
# vim:set ts=4 sw=4 ft=sh et:
I know I need to add the commands etc to perform the various functions, but I thought that this handler.sh would do nothing?
I'm also using xfce. My laptop is a Dell Inspiron 7720.
Any advice on what I might be doing wrong?

Internet Connection off when Laptop Lid Closes

Hi. I just bought my first Mac. A macbook pro. I like to leave my AIM or Ichat on but would like to close the lid to my laptop. Everytime I do, it logs me off. I think this is because of the sleep function. Is there a way to configure so that it doesnt lose my internet everytime???

nope, it is a physical hardware switch that disables the internet when the lid is closed. the only way to disable it is to use your computer in clamshell mode, which means you need an exteral moniter, keyboard, and mouse

[SOLVED] KDE4: No sleep on laptop lid close while screensaver active

I've been trying to figure this out for a while now, and it turns out it's an upstream bug with PowerDevil: https://bugs.kde.org/show_bug.cgi?id=205453
A patch was just posted on that bug report within the last couple days. I rebuilt kdebase-workspace with this patch and it's now working.
I've filed a bug report in the Arch bug tracker (http://bugs.archlinux.org/task/19426) making note of the solution. Anyone who doesn't want to wait for an updated package, and is familiar with ABS, can modify the PKGBUILD to include the patch from the KDE bug report.

Poof, new package already. Nice!
This is why I love Arch.

How to trigger lid close programatically?

Is there a way to trigger the lid close action programmatically with a script or through terminal? I can achieve this by placing a small magnet near the SD slot on my macbook pro, but obviously magnets and hard drives don't mix.
Thanks guys.

I see, in that case you don't want to sleep your Mac. Can you not simply turn down the brightness on the internal display?
If you use an external keyboard you can use your MacBook Pro in "Clamshell mode": Mac notebooks: How to use your computer in closed clamshell (display closed) mode with an external display. The requirement is to have an external keyboard, and its power adapter must be connected.

[SOLVED] Run xscreensaver when I close the laptop lid

I have xscreensaver running in my archlinux, and with a systemd service, I can start it after waking up my laptop.
The problem is that I like to keep my laptop running when I close the lid (for example, to go to bed while I'm downloading a file, I like to simply close my lid), but I want to lock my computer.
In the /etc/systemd/logind.conf, there is a nice option called HandleLidSwitch, which specifies which action is invoked when the lid is closed, and there is a lock option, but It doesn't work for me.
The option suspend works fine.
Here is my /etc/systemd/logind.conf:
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# See logind.conf(5) for details
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
HandlePowerKey=suspend
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
HandleLidSwitch=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#IdleAction=ignore
#IdleActionSec=30min
Any help?
Last edited by alomsimoy (2013-09-10 18:08:33)

I would say that you should just have logind ignore the LidSwitch altogether. So if it is set to ignore the lid switch, then it obviously isn't going to be entering the suspend.target (or is it the sleep.target, I can't remember). Therefore, you are going to have to have some other way of triggering actions in response to these events.
The lid switch sends an event to udev, so you have the option of having a udev rule that responds to this, or using acpid to start this for you. I would recommend using acpid, as it is much more flexible in what it can allow you to do.
Edit: acpid is not necessarily more flexible than a udev rule, as it relies on the udev events. But it is a much easier method of setup since it simply relies of basic scripting in order to make it work. It can allow for one central script (or collection of scripts) to handle all the different events that udev sends. To see what kinds of things trigger a udev event, you can use udevadm monitor or if you install acpid, there is the acpi_listen option.
Edit2: BTW, what is it you mean by not working? Does it still suspend on lid close, or is your xscreensaver not started? You need to be more explicit there. If it is still suspending, have you rebooted or restarted logind after making those changes to logind.conf? You can't just edit the file and have the changes implemented right away, as the configuration is parsed and the settign implemented on the service start.
Last edited by WonderWoofy (2013-09-10 17:28:05)

[systemd] Toggle whether lid close makes laptop sleep

Before migrating to systemd, I had a nice setup using laptop-mode where I would use the laptop "Sleep key" as a toggle for whether closing the lid put the laptop into sleep mode or not. This was just a few lines reading/writing to a file ~/.lidsleep, which I hacked into the laptop-mode shell scripts. Having switched to systemd, and wanting to do the same the "systemd way", I've come up short.
What I have managed to do is temporarily disable the "lid -> sleep" action, with this command:
# systemd-inhibit --what=handle-lid-switch cat
where the function of the final `cat` is to be a program that does not return until I type ^C.
I basically have two questions:
1) How can I make systemd perform an arbitrary command when I press the "Sleep key"?
2) Short of something like running `pgrep systemd-inhibit && pkill systemd-inhibit || systemd-inhibit --what=handle-lid-switch cat`, what is the best way to setup a toggle like this?
Final bonus question, if these two are answered:
My previous setup also included restoring the toggle to its default state (lid -> sleep : yes) when resuming from hibernate (not suspend). How would I do this using systemd?

As WonderWoofy suggests, why not just tell systemd to not handle lid close or the sleep key (not sure it does that but if it does) and continue to use your existing solution with laptop mode tools?
systemd is not, that I know of, supposed to handle stuff like key presses and it is deliberately designed so that you can have a more sophisticated system hand events such as lid closing and so on. Moreover, it doesn't replace the remaining functionality of laptop-mode tools so assuming you used that for other things too, you'll need it anyway. That is, I can't even see how this would let you uninstall laptop-mode tools if you've been using it without giving up a bunch of other stuff. Could you explain why you want to do it without laptop-mode tools etc.?

Set the command "close" in an action to answer "no" to save changes. (CS5)

I am using a command now which I want to at the end of the command close the new file it opened.
I tried recording the action and clicking 'no' while recording but this is not carried over into the action.
How can I solve this?

If you do not want to close a document, then I am not sure why you desire a close action with status of no. Can you elaborate, as I am not understanding that.
I would say to try using toggle dialog on/off (2nd column), but for close that is not even available. You can though remove the check in the first column.

Acpid no longer shutsdown on lid close

Previous to some recent updates acpid and the event I had would shutdown my laptop when I closed the lid. It no longer works. I have acpid running always as a daemon.
My /etc/acpi/handler.sh:
#!/bin/sh
# Default acpi script that takes an entry for all actions
minspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq`
maxspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`
setspeed="/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed"
set $*
case "$1" in
button/power)
#echo "PowerButton pressed!">/dev/tty5
case "$2" in
PBTN|PWRF) logger "PowerButton pressed: $2" ;;
*) logger "ACPI action undefined: $2" ;;
esac
button/sleep)
case "$2" in
SLPB) echo -n mem >/sys/power/state ;;
*) logger "ACPI action undefined: $2" ;;
esac
My /etc/acpi/events/lid file:
event=button/lid (LID0)
action= sudo /sbin/shutdown -h now
Any ideas greatly appreciated.

Easiest way I found to suspend the system to memory (to make it sleep) is by using /sys/power/state (this doesn't work with all the machines).
$ cat /sys/power/state
will tell you the supported modes and what you are looking for is "mem". For example "disk" will do a hibernation but to recover you need to modify boot time kernel options.
If your system supports "mem" state, then all you need to do is
$ echo -n mem >/sys/power/state
and it should go to sleep, pressing power button or opening the lid should power it back on.
Now if that worked fine you can script it into the /etc/acpi/handler.sh:
button/lid)
case "$3" in
close)
#echo "LID closed!">/dev/tty5
echo -n mem >/sys/power/state
open)
#echo "LID opened!">/dev/tty5
esac
Note that we don't actually do anything on lid "open", since recovery is taken care by "BIOS".

Enable Lid Closed action delay

When I try to check the "Enable Lid Closed action delay" checkbox in Power Manager, I receive a dialog box instructing me to:
Please enable "Active System Protection" before enabling Lid Closed action delay
However, the Active System Protection checkbox is greyed-out and cannot be selected. Is this because my X300 has a solid-state HDD? If so, is there a way to use the Enable Lid Closed action delay functionality?
Thanks.

This terminal command will disable lid sleep, a 0 is off, 1 is on.
Disable Lid Sleep
sudo pmset -a lidwake 0
Enable Lid Sleep
sudo pmset -a lidwake 1
Check Staus, look for the Lid Wake value
pmset -g
http://www.mactricksandtips.com/2008/06/changing-sleep-setting-on-mac-laptop.htm l

ProBook 4710s - sound disabled after lid close

Hello, I have a problem: When I connect headphones to the laptop, it works fine, until I close the lid. Then the sound stops working. I have tried to find it in Windows Control Panel (I have Windows 7), but there wasn't such an option. The sound is disabled only when it runs from battery; when I connect it to the electricity, I can use it with an external monitor and speakers and it works fine (even if the lid is closed). I have set "No action" after lid close, so the laptop doesn't go to sleep mode. It just stops playing sound.

Hi,
Download audio driver from here.
Intructions how to install it in XP.
Extract this driver with Winrar.
Open Device manager and expand the Sound, video and game controllers section.
Right click on Either the High Definition Audio Device if you have the generic Microsoft drivers, or the Conexant High Definition SmartAudio 221 if you have older Conexant drivers and choose "Update Driver Software..."
Click Browse my computer for driver software, then click "Let me pick from a list of device drivers on my computer"
Click "Have Disk..." then Browse to the folder where the drivers were extracted .......\XP32 for 32-bit XP. Click OK.
Select one of the "Conexant High Definition SmartAudio 221" models in the list, there will be multiple identical entries.
Click Next, and you're done.
I'm not sure which one from the list will work for You. On CQ60 few users confirmed then first one worked for them.
** Say thanks by clicking the "Thumb up" icon which is on the left. **
** Make it easier for other people to find solutions, by marking my answer with "Accept as Solution" if it solves your issue. **

Time machine disk failure after closing laptop lid

I have a Seagate 1.5 TB disk that I'm using for a time machine backup (USB). For a long time, I had the disk formatted wrong and had this problem, but I re-formatted it (per Apple's instructions) and have been trying again. Now, with it correctly formatted, I still have the same problem.
This is a laptop, so I don't leave the Time Machine application on, nor do I leave the TM disk connected all the time. If I plug in the drive, run TM, and eject the disk before closing the laptop lid, I do not have any issues. If, however, the laptop lid is shut at any point after TM completes, I have can never seem to eject nor unmount the TM disk. For example, last night I ran TM and left the machine open overnight. In the morning, the machine was used and shut per usual routine, except the drive was still connected. Now there is a critical failure on the drive (Disk Utility can do nothing to repair the drive and suggests re-formatting). Last night, the computer was plugged in and went to sleep after 15 minutes. I have changed no settings regarding what the computer does on lid shutdown.
What used to work to eject/unmount the drive is to shutdown the computer. Then I would unplug the drive before re-starting. Now, however, I had errors with the drive (Disk Utility) and went ahead with a force eject. That worked, and the drive still had errors that Disk Utility could not address.
I have a Macbook Pro (13-inch, mid 2012) running Mac OS X Version 10.9.2 (13C64); processor 2.9 GHz Intel Core i7 with 8 GB 1600 MHz DDR3 memory. My main drive is 750 GB (Macintosh HD). I also backup a firewire 400 drive to this TM drive, capacity 250 GB.
So, first question: why is this happening over and over and over? Is there anything I can do, apart from immediate removal of the TM drive after the backup completes, to ensure that it doesn't happen in the future? Should I be concerned that the disk is failing mechanically?
Thanks

I don't think you quite understand how Time Machine really works. But then hardly anyone does. Time Machine is intended to be left enabled always whether a backup drive is connected or not. What Time Machine cannot handle properly is a situation where the backup drive loses power for whatever reason. Time Machine treats this, as does the OS, as an improper disconnect of an external drive without being properly ejected. This in turn throws Time Machine a little bit of a loop.
For you I would suggest not using Time Machine. Instead use a third-party backup utility that you can either schedule or run manually as you wish. They will work with the same drive you have used for Time Machine, but you will need to first erase the Time Machine drive using Disk Utility. Please DO NOT try dragging the Time Machine backups to the Trash.
Here are some good backup utilities you can try:
Suggested Backup Software
1. Carbon Copy Cloner
2. Get Backup
3. Deja Vu
4. SuperDuper!
5. Synk Pro
6. Tri-Backup
Others may be found at MacUpdate. Each one can be used for a trial period. No need to pay for one until you've decided on which one you like best. I, for example, use Carbon Copy Cloner but please don't take that as a recommendation over the others. It's just my preference. All can be operated manually or can be set up to backup on a schedule you determine. Some can even be set up to backup as soon as the backup drive is connected.
Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files.

Getting Arch to pm-suspend on lid close [SOLVED]

Hello,
I want Arch to suspend to RAM when I close my laptop lid. Here is what I did:
I installed pm-utils. I also followed the wiki and set it up so that I can just say
sudo pm-suspend
and the computer suspends with the need to type in your password.
Then, I installed acpid to have a way to capture acpi events.
Now, from what I read on the wiki and in these forums, I had to edit /etc/acpi/handler.sh
Here is the pertinent code that I edited:
button/lid)
#echo "LID switched!">/dev/tty5
logger "ACPI lid switched $1 $2"
if [ -n "`grep close /proc/acpi/button/lid/LID/state`" ]; then
/usr/sbin/pm-suspend
logger -s "ACPI lid closed";
elif [ -n "`grep open /proc/acpi/button/lid/LID/state`" ]; then
logger -s "ACPI lid opened"
else
logger -s "Couldn't detect Lid state"
fi
but the problem is that when I close the lid, it writes "ACPI lid closed" to the logfile, but instead of suspending the laptop, it just blanks the screen. Here is what it says in the log file
Apr 18 11:02:45 Treadstone logger: ACPI lid closed
Apr 18 11:02:45 Treadstone acpid: client connected from 4790[0:1000]
Apr 18 11:02:45 Treadstone acpid: 1 client rule loaded
Apr 18 11:02:47 Treadstone acpid: client 4790[0:1000] has disconnected
Apr 18 11:02:47 Treadstone logger: ACPI lid switched button/lid LID
Apr 18 11:02:47 Treadstone logger: ACPI lid opened
Any help will be greatly appreciated.
Last edited by mgangav (2009-04-18 19:46:01)

B wrote:You need check the pm-suspend log for pointers .
Ok, I checked the pm-suspend.log Here are it's contents:
Initial commandline parameters:
Sat Apr 18 11:45:03 EDT 2009: Running hooks for suspend.
/usr/lib/pm-utils/sleep.d/00auto-quirk suspend suspend: Adding quirks from HAL: --quirk-dpms-on --quirk-dpms-suspend --quirk-vbe-post --quirk-vbemode-restore --quirk-vbestate-restore --quirk-vga-mode-3
success.
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: Linux Treadstone 2.6.28-ARCH #1 SMP PREEMPT Sun Mar 8 10:18:28 UTC 2009 i686 Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz GenuineIntel GNU/Linux
Module Size Used by
ipv6 260340 10
i915 58372 2
drm 83880 3 i915
fuse 53020 2
joydev 11712 0
snd_seq_oss 31872 0
snd_seq_midi_event 8192 1 snd_seq_oss
snd_seq 49968 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 8204 2 snd_seq_oss,snd_seq
snd_pcm_oss 40192 0
uvcvideo 57736 0
compat_ioctl32 3072 1 uvcvideo
videodev 34176 1 uvcvideo
v4l1_compat 15364 2 uvcvideo,videodev
snd_mixer_oss 16512 1 snd_pcm_oss
arc4 3712 2
ecb 4608 2
b44 28560 0
ssb 40964 1 b44
pcmcia 35532 1 ssb
sdhci_pci 9088 0
sdhci 17028 1 sdhci_pci
container 5248 0
mii 6528 1 b44
iwl3945 91128 0
mmc_core 46876 1 sdhci
uhci_hcd 24592 0
yenta_socket 25996 1
rsrc_nonstatic 13056 1 yenta_socket
pcmcia_core 34452 4 ssb,pcmcia,yenta_socket,rsrc_nonstatic
snd_pcsp 11048 0
sg 26804 0
mac80211 161184 1 iwl3945
snd_hda_intel 412980 0
snd_hwdep 9092 1 snd_hda_intel
psmouse 55828 0
ehci_hcd 36876 0
video 18704 0
output 4608 1 video
snd_pcm 70020 3 snd_pcm_oss,snd_pcsp,snd_hda_intel
snd_timer 21384 2 snd_seq,snd_pcm
snd_page_alloc 10120 2 snd_hda_intel,snd_pcm
snd 50852 10 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcsp,snd_hda_intel,snd_hwdep,snd_pcm,snd_timer
soundcore 8160 1 snd
cfg80211 31760 2 iwl3945,mac80211
serio_raw 7172 0
usbcore 136848 4 uvcvideo,uhci_hcd,ehci_hcd
i2c_i801 10896 0
i2c_core 22804 1 i2c_i801
intel_agp 27836 1
agpgart 31572 3 drm,intel_agp
iTCO_wdt 12836 0
iTCO_vendor_support 4996 1 iTCO_wdt
acer_wmi 16320 0
rfkill 11596 4 iwl3945,acer_wmi
led_class 5508 2 iwl3945,acer_wmi
wmi 7848 1 acer_wmi
evdev 11296 7
thermal 17180 0
processor 41388 3 thermal
fan 6276 0
button 7824 0
battery 12036 0
ac 6020 0
rtc_cmos 12332 0
rtc_core 17564 1 rtc_cmos
rtc_lib 4480 1 rtc_core
ext3 127112 2
jbd 46996 1 ext3
mbcache 8708 1 ext3
sr_mod 16708 0
cdrom 35360 1 sr_mod
sd_mod 26904 5
pata_acpi 6016 0
ata_piix 23300 4
ata_generic 6788 0
libata 157856 3 pata_acpi,ata_piix,ata_generic
scsi_mod 102164 4 sg,sr_mod,sd_mod,libata
total used free shared buffers cached
Mem: 2065460 482372 1583088 0 60728 194692
-/+ buffers/cache: 226952 1838508
Swap: 2931852 0 2931852
success.
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: /bin/stty: standard input: Inappropriate ioctl for device
success.
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: success.
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/90chvt suspend suspend: success.
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
/usr/lib/pm-utils/sleep.d/95led suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video suspend suspend: success.
/etc/pm/sleep.d/99lock suspend suspend: xscreensaver-command: warning: $DISPLAY is not set: defaulting to ":0.0".
No protocol specified
xscreensaver-command: can't open display :0.0
Returned exit code 1.
Sat Apr 18 11:45:05 EDT 2009: Inhibit found, will not perform suspend
Sat Apr 18 11:45:05 EDT 2009: Running hooks for resume
/usr/lib/pm-utils/sleep.d/98smart-kernel-video resume suspend: success.
/usr/lib/pm-utils/sleep.d/95led resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
/usr/lib/pm-utils/sleep.d/90clock resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/90chvt resume suspend: success.
/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
/usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend: success.
/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/11netcfg resume suspend: /bin/stty: standard input: Inappropriate ioctl for device
success.
/usr/lib/pm-utils/sleep.d/01grub resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
/usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
/usr/lib/pm-utils/sleep.d/00auto-quirk resume suspend: success.
From what I can tell, it seems that xscreensaver doesn't want to start for some reason. By the way here are the contents of my /etc/pm/sleep.d/
#!/bin/bash
case $1 in
suspend)
xscreensaver-command -l
resume)
echo "Coming out of sleep mode"
echo "Doing something else"
esac
I wonder if xscreensave has anything to do with this?

Lumia 2520 Power Keyboard - running with lid close...

Hi,
I have a 2520 and Power Keyboard. When I am at home at my desk I would like to plug it into my KVM switch to use my full size keyboard, mouse and large monitor. If I leave the 2520 in the power keyboard and close it up, the screen blanks and I can't do anything.
Is there a setting somewhere to enable me to treat it more like a docking station?

go to windows power options. (right click the battery charge icon)
select change plan settings
select change advanced power settings
expand power buttons and lid
expand lid clos action
select do nothing in pluged in field
done

Gnome3: Cannot set laptop lid close action

Similar Messages

Maybe you are looking for