[SOLVED] how to prevent suspending/sleeping when closing laptop lid

Hi all,
My laptop, a Lenovo Thinkpad T430u, suspends whenever I close the lid. It's been doing this since I first installed Arch.  I want to turn this feature off.  How can I do it?
Relevant information:
acpid is installed
the configuration file /etc/acpi/handler.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
case $(cat /proc/acpi/button/lid/LID0/state | awk '{print $2}') in
closed) XAUTHORITY=$(ps -C xinit -f --no-header | sed -n 's/.*-auth //; s/ -[^ ].*//; p') xset -display :0 dpms force off ;;
open) XAUTHORITY=$(ps -C xinit -f --no-header | sed -n 's/.*-auth //; s/ -[^ ].*//; p') xset -display :0 dpms force on ;;
esac
logger "ACPI group/action undefined: $1 / $2"
esac
# vim:set ts=4 sw=4 ft=sh et:
dmesg output:
[ 1530.790532] PM: Syncing filesystems ... done.
[ 1530.805678] PM: Preparing system for mem sleep
[ 1530.844445] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 1530.856658] Freezing remaining freezable tasks ... (elapsed 0.10 seconds) done.
[ 1530.963435] PM: Entering mem sleep
[ 1530.963572] Suspending console(s) (use no_console_suspend to debug)
[ 1531.123543] iwlwifi 0000:03:00.0: iwl_pcie_cmdq_reclaim: Read index for DMA queue txq id (9), index 207 is out of range [0-256] 208 208.
[ 1531.124216] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 1531.124579] sd 0:0:0:0: [sda] Stopping disk
[ 1531.360682] mei 0000:00:16.0: suspend
[ 1531.440517] ahci 0000:00:1f.2: power state changed by ACPI to D3hot
[ 1531.687309] PM: suspend of devices complete after 722.490 msecs
[ 1531.687784] PM: late suspend of devices complete after 0.469 msecs
[ 1531.688232] pcieport 0000:00:1c.3: System wakeup enabled by ACPI
[ 1531.714222] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
[ 1531.727619] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
[ 1531.754015] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
[ 1531.767422] PM: noirq suspend of devices complete after 79.565 msecs
[ 1531.768301] ACPI: Preparing to enter system sleep state S3
[ 1531.797647] PM: Saving platform NVS memory
[ 1531.799282] Disabling non-boot CPUs ...
[ 1531.900721] smpboot: CPU 1 is now offline
[ 1532.004162] smpboot: CPU 2 is now offline
[ 1532.107554] smpboot: CPU 3 is now offline
I have pmutils and tlpinstalled
tlp config
# tlp - Parameters for power save
# Hint: some features are disabled by default, remove the leading # to enable them
# Set to 0 to disable/1 to enable TLP
TLP_ENABLE=1
# Seconds laptop mode has to to wait after the disk goes idle before doing a sync.
# Non-zero value enables, zero disables laptop mode.
DISK_IDLE_SECS_ON_AC=0
DISK_IDLE_SECS_ON_BAT=2
# Dirty page values (timeouts in secs).
MAX_LOST_WORK_SECS_ON_AC=15
MAX_LOST_WORK_SECS_ON_BAT=60
# Select a cpu frequency scaling governor: ondemand/powersave/performance/conservative
# Important:
# - You *must* disable your distribution's governor settings or conflicts will occur
# - ondemand is sufficient for *almost all* workloads, you should know what you're doing!
#CPU_SCALING_GOVERNOR_ON_AC=ondemand
#CPU_SCALING_GOVERNOR_ON_BAT=ondemand
# Set the min/max frequency available for the scaling governor.
# Possible values strongly depend on your cpu. For available frequencies see
# tlp-stat output, Section "+++ Processor".
# Hint: Parameters are disabled by default, remove the leading # to enable them,
# otherwise kernel default values are used.
#CPU_SCALING_MIN_FREQ_ON_AC=0
#CPU_SCALING_MAX_FREQ_ON_AC=0
#CPU_SCALING_MIN_FREQ_ON_BAT=0
#CPU_SCALING_MAX_FREQ_ON_BAT=0
# Set the cpu "turbo boost" feature: 0=disable / 1=allow
# Requires an Intel Core i processor and kernel 3.7 or later.
# Important:
# - This may conflict with your distribution's governor settings
# - A value of 1 does *not* activate boosting, it just allows it
#CPU_BOOST_ON_AC=1
#CPU_BOOST_ON_BAT=0
# Minimize number of used cpu cores/hyper-threads under light load conditions
SCHED_POWERSAVE_ON_AC=0
SCHED_POWERSAVE_ON_BAT=1
# Kernel NMI Watchdog
# 0=disable (default, saves power) / 1=enable (for kernel debugging only)
NMI_WATCHDOG=0
# Change CPU voltages aka "undervolting" - Kernel with PHC patch required
# Freq:voltage pairs are written to /sys/devices/system/cpu/cpu0/cpufreq/phc_controls
# CAUTION: only use this, if you thoroughly understand what you are doing!
#PHC_CONTROLS="F:V F:V F:V F:V"
# Hard disk devices, separate multiple devices with spaces (default: sda).
# Devices can be specified by disk id too (lookup with: tlp diskid).
DISK_DEVICES="sda sdb"
# Hard disk advanced power management level: 1(max saving)..254(off)
# Levels 1..127 may spin down the disk.
# Separate values for multiple devices with spaces.
DISK_APM_LEVEL_ON_AC="254 254"
DISK_APM_LEVEL_ON_BAT="128 128"
# Hard disk spin down timeout:
# 0: spin down disabled
# 1..240: timeouts from 5s to 20min (in units of 5s)
# 241..251: timeouts from 30min to 5.5 hours (in units of 30min)
# (see 'man hdparm' for details)
#DISK_SPINDOWN_TIMEOUT_ON_AC="0 0"
#DISK_SPINDOWN_TIMEOUT_ON_BAT="0 0"
# Select io scheduler for the disk devices: noop/deadline/cfq (Default: cfq)
# Separate values for multiple devices with spaces.
#DISK_IOSCHED="cfq cfq"
# SATA aggressive link power management (ALPM):
# min_power/medium_power/max_performance
SATA_LINKPWR_ON_AC=max_performance
SATA_LINKPWR_ON_BAT=min_power
# PCI Express Active State Power Management (PCIe ASPM):
# default/performance/powersave
# Hint: needs kernel boot option pcie_aspm=force on some machines
PCIE_ASPM_ON_AC=performance
PCIE_ASPM_ON_BAT=powersave
# Radeon graphics clock speed (profile method): low/mid/high/auto/default
# auto = mid on BAT, high on AC; default = use hardware defaults
# (Kernel >= 2.6.35 only, not with fglrx driver!)
RADEON_POWER_PROFILE_ON_AC=high
RADEON_POWER_PROFILE_ON_BAT=low
# WiFi power saving mode: 1=disable/5=enable
# (Linux 2.6.32 and later, some adapters only!)
WIFI_PWR_ON_AC=1
WIFI_PWR_ON_BAT=5
# Disable wake on lan: Y/N
WOL_DISABLE=Y
# Enable audio power saving for Intel HDA, AC97 devices (timeout in secs).
# A value of 0 disables / >=1 enables power save.
SOUND_POWER_SAVE=1
# Disable controller too (HDA only): Y/N
SOUND_POWER_SAVE_CONTROLLER=Y
# Set to 1 to power off optical drive in UltraBay (ThinkPads only)
# when running on battery. A value of 0 disables this Feature (Default).
# Drive can be powered on again by releasing (and reinserting) the
# eject lever or by pressing the disc eject button on newer models.
# Note: an UltraBay hard disk is never powered off.
BAY_POWEROFF_ON_BAT=0
# Optical drive device to power off (default sr0)
BAY_DEVICE="sr0"
# Runtime Power Management for pci(e) bus devices
# (Kernel >= 2.6.35 only): on=disable/auto=enable
RUNTIME_PM_ON_AC=on
RUNTIME_PM_ON_BAT=auto
# Runtime PM for *all* pci(e) bus devices: 0=disable / 1=enable
# Warning: experimental option, could cause system instabilities
RUNTIME_PM_ALL=0
# Set to 0 to disable/1 to enable usb autosuspend feature
USB_AUTOSUSPEND=1
# Devices from the following list are excluded from usb autosuspend
# (separate with spaces). Use lsusb to get the id's.
# Note: input devices (usbhid) are excluded automatically
#USB_BLACKLIST="1111:2222 3333:4444"
# Set to 1 to disable autosuspend before shutdown/0 to do nothing
# (workaround for usb devices that cause shutdown problems)
#USB_AUTOSUSPEND_DISABLE_ON_SHUTDOWN=1
# Restore radio device state (bluetooth, wifi, wwan) from previous shutdown
# on system startup: 0=disable/1=enable
# Hint: the parameters DEVICES_TO_DISABLE/ENABLE_ON_STARTUP/SHUTDOWN below
# are ignored when this is enabled!
RESTORE_DEVICE_STATE_ON_STARTUP=0
# Radio devices to disable on startup: bluetooth wifi wwan
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
# Radio devices to enable on startup: bluetooth wifi wwan
#DEVICES_TO_ENABLE_ON_STARTUP="wifi"
# Radio devices to disable on shutdown: bluetooth wifi wwan
# (workaround for devices that are blocking shutdown)
#DEVICES_TO_DISABLE_ON_SHUTDOWN="bluetooth wifi wwan"
# Radio devices to enable on shutdown: bluetooth wifi wwan
# (to prevent other operating systems from missing radios)
#DEVICES_TO_ENABLE_ON_SHUTDOWN="wwan"
# Radio devices to enable when wireless radio switch is turned on:
# bluetooth wifi wwan (Ubuntu + ThinkPad only)
#DEVICES_TO_ENABLE_ON_RADIOSW="wifi wwan"
# Battery charge thresholds (ThinkPad only, tp-smapi or acpi-call kernel module required)
# Charging starts when the remaining capacity falls below the START_CHARGE_TRESH
# value and stops when exceeding the STOP_CHARGE_TRESH value.
# Main battery (values in %)
#START_CHARGE_THRESH_BAT0=75
#STOP_CHARGE_THRESH_BAT0=80
# Ultrabay or slice battery (values in %)
#START_CHARGE_THRESH_BAT1=75
#STOP_CHARGE_THRESH_BAT1=80
# Set to 1 to disable use of tpacpi-bat on Sandy Bridge or newer Thinkpads
# and force usage of tp-smapi instead
#DISABLE_TPACPIBAT=1
# tlp-rdw - Parameters for the radio device wizard
# Possible devices: bluetooth/wifi/wwan
# Hint: parameters are disabled by default, remove the leading # to enable them
# Radio devices to disable on connect
DEVICES_TO_DISABLE_ON_LAN_CONNECT="wifi wwan"
DEVICES_TO_DISABLE_ON_WIFI_CONNECT="wwan"
DEVICES_TO_DISABLE_ON_WWAN_CONNECT="wifi"
# Radio devices to enable on disconnect
DEVICES_TO_ENABLE_ON_LAN_DISCONNECT="wifi wwan"
#DEVICES_TO_ENABLE_ON_WIFI_DISCONNECT=""
#DEVICES_TO_ENABLE_ON_WWAN_DISCONNECT=""
# Radio devices to enable/disable when docked
#DEVICES_TO_ENABLE_ON_DOCK=""
#DEVICES_TO_DISABLE_ON_DOCK=""
# Radio devices to enable/disable when undocked
#DEVICES_TO_ENABLE_ON_UNDOCK="wifi"
#DEVICES_TO_DISABLE_ON_UNDOCK=""
thanks guys
I love arch
Last edited by beitme (2013-06-08 10:05:37)

@ Karol, done
@ 65kid, here's my logind.conf
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
#HandleLidSwitch=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#IdleAction=ignore
#IdleActionSec=30min

Similar Messages

  • Sets into sleep when closing le lid, even with the display connected

    I have the problem, that when I close the lid of my MacBook, it goes to sleep mod. This even happens when I connect the display. Even following the steps on the Apple.com page, it still goes into sleep mode.
    Please help me avoid this sleep mode problem, I want to use my display instead of my computers screen. (yes, I have a wireless keyboard and mouse, paired all of them)
    Thanks

    Welcome to the Apple Discussions!
    You can't avoid it. This is the way it's supposed to work.
    If you have the AC adapter plugged in, an external display plugged in and an external mouse and keyboard (USB or Bluetooth), you can WAKE the computer after it's gone to sleep with the lid closed. But it will go to sleep when you close it. This is detailed here:
    http://support.apple.com/kb/HT3131
    -Doug

  • Hard lockup when closing laptop lid (Linux 2.6.23)

    I just found this out a few days ago, telling my laptop to shut down a few hours later, and still finding it running half a day later, severely overheated (!).
    I am running a custom kernel (2.6.23.1 with some of the kamikaze broken out patches). I get this:
    - I unplug the laptop USB mouse
    - I close the lid
    - I reopen the lid, only to find my system completely locked up (no screen refresh anymore, no possibility to switch to a virtual terminal, no possibility to restart X or restart the system (Ctrl+Alt+Del/Backspace aren't working at all).
    I have no action specified for closing the lid (I plan on making it do suspend to RAM as soon as this issue is cleared up). Now if I leave the USB laptop mouse plugged in all works fine. I can close the lid, open it up again, and my system remains fully usable.
    To make sure this wasn't just me being clumsy and compiling a bad kernel, I tried the 2.6.23-ARCH kernel from testing. It exhibits exactly the same behaviour. 2.6.22-ARCH works just fine.
    Are there people having the same issue?
    Last edited by B (2007-10-21 12:16:32)

    Okay guys . I got some goodies up . For those interested:
    - 2.6.22.12 kernel with CFS v22, hrtimers, powertop, Reiser4 and default CPU frequency governor 'ondemand'
    - iwlwifi 1.1.21
    - Authentec fingerprint reader driver
    I guess that should get you going pretty much  . The iwlwifi drivers have been built out-of-tree since my efforts to merging in the newer mac80211 stack & latest iwlwifi drivers amounted to nothing but a boatload of patch errors :-( (yes i can hack up patches to work but I felt like not doing it, since iwlwifi builds just fine out-of-tree). This kernel is tailored to the 6510 hardware, I cannot tell what is different in the 6170b lineup, but you definitely should not try this kernel on just any machine .
    If you have any questions, drop me a line.
    Credit of course to waninkoko for his kamikaze patchset, from which most of the patches come.
    Update: to the latest 2.6.22.12 kernel + corresponding driver packages
    Last edited by B (2007-11-11 16:39:48)

  • How to prevent standby/sleep when charging

    I need to use an app on my phone constantly to enter data but I cannot find any way of preventing the phone from switching the screen off and going into standby mode.
    When I resume I have to navigate my way back into the app which is very frustrating.
    In WM6.5 it was possible to prevent sleep mode on mains power.  Surely something like this is available in WP7?

    There are options to change the lock screen timeout to a maximum of 5 mins. There is no option to disable it though. This is specific to Nokia phone's as other wp7's allow you to disable the lock screen completely. Nokia phones don't, they have made that decision in their design.. I believe this is a bad limitation as it is very frustrating to have to unlock the phone manually every 5 mins.
    This is incredibly annoying when using GPS in the car. Bing maps locks out every 5 mins making the navigation feature unusable in a car. Nokia Drive works fine though. It is also frustrating if using music when driving.
    It is up to the app developer to enable code that prevents the screen locking.
    I contacted Nokia about this and they have no plans to change it. They have done this to extend battery life, but that's irrelevant whilst charging.
    I wish i could just disable it like every other phone in existence.

  • [Solved] preventing standby when closing laptop lid and more.

    To be blunt, I'm on the verge of insanity at this point. I'm no newcomer to Arch, but this has me beat.
    In short I'm not using my asus eepc 1015pem anymore, so I decided to make it a folding machine.
    Everything works as intended except when I close the lid, it automatically goes to sleep and I haven't had any luck finding a solution.
    All in all I have little use for any sort of power management, and things like CPU scaling and such, should obviously not be active.
    So please do let me know where I can find the information I need.
    My arch installation is completely basic and brand new, should that information matter
    Best regards.
    Last edited by zacariaz (2012-10-21 00:37:00)

    2ManyDogs wrote:
    zacariaz wrote:
    WonderWoofy wrote:
    You need to look into the powers of logind.conf (by that I mean the man page). 
    Also, I don't know why you would want to turn frequency scaling off.  If it makes the cpu go full speed, so be it, but if not, it would be nice to not use quite as much power.
    First of all, I want to thank you for the quick reply and secondly mention that this is a very low power device which will be running at full capacity 14/7, thus these think are not needed.
    If it's running at "full capacity" cpu frequency scaling will allow the CPU to run at its top speed. There is no need to remove it. If at any point full speed is not required, even a low-power device will use less power with cpu scaling, and it allows the CPU to rest and cool off a little.
    But hey, it's your box.
    The reason it's important is only due to the doubt that the cpu might somehow be inhibited. If that's not the case, then it doesn't matter obviously.

  • How to prevent saving edits when closing Adobe

    I have several blank forms saved on my tablet and I need to use the same blank form for different jobs. Every time I fill the form it gets automatically saved and I no longer have my original blank form.
    Is there a way to disable this feature.
    Thank You

    Adobe Reader for iOS automatically saves any changes to a currently viewed PDF document when you close the document by going back to the home screen (showing the file browser).  There is no preference or option to disable/turn off the "Auto Save" feature.
    You can make a copy of your blank form before you open it.
    In the home screen, tap Documents.
    Long press (press & hold) the document that you want to make a copy of.
    Tap the overflow icon (with small three squares) in the upper right corner.
    Tap Duplicate.
    Open the newly duplicated PDF document (instead of the original one).

  • IPod disconnected from iTunes when closing laptop lid

    I recently received a new iPod Classic 120 Gb after the old one's battery died. When i connect the new one to my Macbook Pro and close the lid it disconnects from iTunes (it is still connected, it appears in Finder, just not in iTunes).
    I got the latest version of iTunes and the iPod software. This never happened with the old iPod. Is there a fix for this?

    Okay guys . I got some goodies up . For those interested:
    - 2.6.22.12 kernel with CFS v22, hrtimers, powertop, Reiser4 and default CPU frequency governor 'ondemand'
    - iwlwifi 1.1.21
    - Authentec fingerprint reader driver
    I guess that should get you going pretty much  . The iwlwifi drivers have been built out-of-tree since my efforts to merging in the newer mac80211 stack & latest iwlwifi drivers amounted to nothing but a boatload of patch errors :-( (yes i can hack up patches to work but I felt like not doing it, since iwlwifi builds just fine out-of-tree). This kernel is tailored to the 6510 hardware, I cannot tell what is different in the 6170b lineup, but you definitely should not try this kernel on just any machine .
    If you have any questions, drop me a line.
    Credit of course to waninkoko for his kamikaze patchset, from which most of the patches come.
    Update: to the latest 2.6.22.12 kernel + corresponding driver packages
    Last edited by B (2007-11-11 16:39:48)

  • KDE: Laptop only sleeps when closing lid every other time

    Hello all,
    I'm running KDE 4.14.1 on an older Toshiba Satellite laptop. In the KDE System Settings, I've told it to sleep when closing the lid and this works - but strangely only every other time I close the lid. It will work once, then I open the lid and it powers up just fine. Then I close it again and the screen just turns off but the laptop stays fully powered.
    Any ideas what might be going on? It consistently only sleeps every other time when I close the lid (the other times it just turns the screen off).

    Take a look at /etc/systemd/logind.conf
    Is systemd also trying to manage this?

  • [SOLVED] Laptop doesn't suspend anymore when closing lid [GNOME 3]

    Hi there!
    Since I upgraded to GNOME 3 recently, my laptop (Acer Aspire TimelineX 3820TG) doesn't suspend anymore when I close the lid. Instead, it just turns off the screen. If I choose suspend from the menu, it does suspend properly.
    I googled a bit and found out that the option what to do on closing the lid was dropped in GNOME 3, setting suspend as default action. That's exactly what I want...
    Also, I checked that option via gnome-tweak-tool and dconf-editor, and (surprise!) it was set to 'suspend'.
    Anyone got an idea what to do to make it suspend again on closing the lid?
    Last edited by perpetrator (2011-10-17 14:25:26)

    Sorry to bother you again, but for some reason it doesn't work anymore...
    Somehow it can't lock the GNOME session, because when I enter the above line from /etc/acpi/handler.sh manually as root in TTY1, I get this error:
    ** Message: Failed to get session bus: Befehlszeile »dbus-launch --autolaunch=c9375f4ea0008d92177b28db000009ae --binary-syntax --close-stderr« brach mit von Null verschiedenem Beenden-Status 1 ab: No protocol specified\nAutolaunch error: X11 initialization failed.\n
    If I enter this command inside GNOME, everything works just fine, it locks the screen and suspends.
    EDIT:
    Setting the XAUTHORITY environment variable properly did the trick. Therefore, I borrowed some lines from here: https://wiki.archlinux.org/index.php/Su … losing_lid
    Thread marked as SOLVED again.
    Last edited by perpetrator (2011-10-17 14:25:11)

  • Macbook pro not turning on after SMC reset. I have the following problem. Yesterday I noticed that my mbp 2011does not sleep when closing the screen. smc due loud fan and an X on battery symbol

    Yesterday I noticed that my mbp 2011 dos not sleep when closing the screen cover. Today I Turner my laptop in. However the fan was working loudly and stayed loud. After Start I noticed an X on Battery symbol. Clicking on it, it showed 'no battery.' I found out that a potential solution for this problem was SMC reset. I also noticed that the leds on magsafe was not lightning. Despite this I tried to execute the smc reset as described on apple support site. Switching off, plugin the magsafe connector, pushed the buttons shift + alt+ ctrl + power. Then i pushed the power button, but my mbp is not turning on. I pushed several times on the power button but nothing works. The magsafe is also dark meaning the leds not lightning. Can anyone here help me on this ?

    Problem solved by my own. But do not how :) magsafe again working and the laptop tooo

  • MBP (13-inch, early 2011) goes into hibernation instead of safe sleep upon closing the lid (only when using battery power)

    MBP details
    13-inch MacBook Pro, early 2011 (model identifier: MacBookPro8,1)
    Running Yosemite, OS X 10.10.1 (however, problem started while using Mavericks)
    2.5 GHz Intel Core i5
    4 GB memory
    Symptoms
    * the MBP goes into hibernation instead of sleep upon closing the lid on battery power (i.e.,  when AC adapter is NOT connected)
      -- problem does not occur when AC adapter is connected
    * putting the computer to sleep by other means does not induce the problem; these other means include:
      -- [i] option+command+Power,
      -- [ii] Apple Icon --> Sleep,
      -- [iii] in Terminal: pmset sleepnow
    * the battery is NOT getting drained at all; if I close the lid on 87%, the battery is still at about 87% when I get the MBP back up and running
    To be as clear as possible:
    (1) MBP is on and in use  (power source: battery); battery is at X%
    (2) the lid is then closed
    (3) the battery indicator light glows bright for about 10 seconds, then shuts off, and with it so does the MBP (all fans and sounds cease)
    (4) opening the lid and pressing any key on the keyboard does nothing (the computer is not sleeping)
    (5) to turn the MBP back on, I must hit the power button once; this brings up  and the gray screen and loading bar indicative of returning from hibernation
    (6) log in; battery is still at X%
    Attempted Solutions / Fixes
    There are Apple Discussions addressing similar MBP issues, many of which at least have work-arounds, if not full-blown solutions. However, I have tried many of the proposed work-arounds and solutions; nothing has solved my problem. Such attempted solutions include:
      * made sure EFI/SMC firmware was up to date
      * updated all software
      * logged in as a different user
      * booted in Safe Mode
      * reset the PRAM
      * repaired disk permissions using Disk Utility
      * repaired additional disk permissions in recovery mode (a la this chron.com advice)
      * ran the Apple Hardware Test multiple times (short test while plugged in, short test on battery, extended test while plugged in, extended test on battery)
      * booted from an external known-good OS on USB drive
      * reseated the RAM
      * used MemTest to test the RAM's health (it was good)
      * tested my battery's health with the app Battery Health (it is healthy!)
      * booted my computer with one stick of the MBP's original RAM at a time (figured "why not?")
      * booted my computer using other sticks of RAM
      * checked my power management settings using PMSET in the terminal (e.g., pmset -g); tried various hibernation modes (e.g., sudo pmset -a hibernationmode X, where X=0,1,3, etc)
      * searched/grepped through my power management logs and Console messages to look for googleable items (e.g., pmset -g log | grep WORD, where WORD=failure, sleep, etc);  still have not found help online
      * brought the MBP to a Mac Genius
    -- he ran some further tests, but found nothing;
    -- he re-installed my OS as a hopeful-hail-mary-just-maybe-last-ditch effort; the problem persisted!
    -- we both agreed that we had ruled out a software cause
    -- he offered me to leave my MBP to get fixed for a flat fee of $300.00 (which after a couple weeks of trying to figure this out is starting to sound more and more reasonable)
    Given that it is likely not a software issue, what hardware might it be? By booting from an OS on an external drive, I think I've ruled out a bad hard drive or hard drive cable. Also, given that inducing sleep in any way other than closing the MBP's lid does not cause the problem, it seems there might be a wire (or something) in the hinge section of the MBP that gets moved when the lid is closed possibly causing some kind of short circuit...or something.
    If someone with more experience interpreting Console messages, for example, can help, I'd be happy to provide some logs, or any additional information.
    Thank you for your time and consideration.

    Ok, this is a crazy-simple, quasi-embarrassing fix, but I'll post it anyway just in case anyone is having a similar problem (for example, this guy: Changes to pmset being ignored).
    Some time around late last August / early September (2014) this issue began happening for me (specifically, issue = closing lid while on battery power induces hibernation / shut down instead of sleep --- independent of hibernation mode). Maybe it was when I upgraded to Yosemite (not sure what the exact date of that was). As detailed in my original post, I frantically tried everything I could think of... At that time, however, I had quite a few presentations and posters to create and present at meetings and conferences, so I held off fixing it for a couple of months and returned to it this past week, where I tried a few more things listed above, but again to no avail...
    This morning, I simply tried fudging around with all my power management settings again (via pmset in Terminal). The simplicity of the fix surprised me. But now that I understand it, I know it is likely the same fix for other threads I've read, such as the one above:
                                        (TLDR in bold)
    (1) Take note of your power management settings (Terminal:  pmset -g custom)
    (2) Is the "standby" flag set to 0? If so, set it to 1. Wa-la! Done.
    This fix is crazy and embarrassing b/c I was so close to it for so long. I tried changing my hibernation modes multiple times (sudo pmset -a hibernatemode X, where X=0,1,3,25,etc). I read about manipulating other PMSET settings that helped other people with newer MBPs, like "autopoweroff" and "autopoweroffdelay" --- settings that I do not have on the MBP early 2011 (check your settings: pmset -g cap). And most amazingly of all, I even messed with the "standbydelay" setting, trying to make it so long that my computer should never go into hibernation... Yet, from what I can tell by looking over my notes, I never simply set "standby" from 0 to 1.
    There are interesting questions that arise due to this fix. For example, why did this problem persist on clean installs of OS Yosemite? Is "standby" being set to 0 the Yosemite default? I'm not sure. If it is, then Kappy was right: this was normal behavior... It just wasn't always the normal behavior...at least not for my MBP. Normal behavior (hibernatemode 3) used to be (and now is again) that the MBP goes into safe sleep, and then only after an allotted amount of time will it go into full-blown hibernation.
    NOTE: the "standby" and "standbydelay" PMSET settings are not available in some earlier MBP models (e.g., my brother has a 2010 and does not have these settings); so if you're having a similar problem with an earlier model, this fix might not be of any help to you.

  • How to prevent re-login when switching in the application between different module in 6.1.1.1.11?

    How to prevent re-login when switching in the application between different module in 6.1.1.1.11?
    Please help me to figure out this or resolve this issue?

    Be sure to check that your Remoting Container service is running. If it is not, restart the service, and if it goes down again, check the event logs.
    Make sure that the AuthenticationBridgeService is enabled in your EnvironmentSettings.config, and the remoting container user is configured using the SetupAssistant.
    <RemotingContainer>
             <ConfigInfo configChildKey="key">
                   <add key="UserID" value="@@VAR:Prodika.RemotingContainer.SysUser@@" />
             </ConfigInfo>      
            <!-- Set the following services isActive flag to 'true' or 'false' -->
             <RemoteServices configChildKey="name">
                 <Service
                     name="AuthenticationBridgeService"
                     port="@@VAR:Prodika.AuthenticationBridge.Port@@"
                     isActive="true" />
    If the Remoting Container Service fails, please contact Support with details from the event logs.

  • No sleep when closing

    Hi,
    after installing Lion my late 2007 MacBook does not go to sleep when closing anymore. Anyone with same problem? Suggestions?
    Regards,
    czery

    I have the same thing in Macbook Air 2010. When I choose the shut down ant the sleep option the is no result, Lion does not execute this. Please help. I don't like to shut it down each time.

  • PowerBook G4 not going to sleep when closed???

    My 15-inch 1.67 GHz PowerBook doesn't go to sleep when closed. The Apple on the back on the display stays lit and the display doesn't go dark either. Anyone have any ideas???

    Check that your sleep magnet hasn't fallen. Take something made of steel like a paperclip, and see if it sticks to the outside of the case above the Apple logo. If not, the magnet inside may have moved. When the cover is closed, the magnet is directly over and affects the trackpad area. If you have a magnet (like on your refrigerator), wave it over the trackpad and it should go to sleep.

  • How to show a confirmation when closing browser window in jdeveloper11g

    Hi
    I'm Using Jdev 11g
    How to show a confirmation when closing browser window in jdeveloper11g
    Regards
    Abhilash

    Abhilash,
    My goodness...
    Didn't search the forum, eh? In fact, didn't even look at the last 5 or 6 posts - this was posted by another user within the past few hours.... Giving a message while closing a jspx page.
    John

Maybe you are looking for