Console events while lid closed

Hi
Recently I noticed on my MacBook Air console (late 2012, running Yosemite) some
events during a very short period of 3 hours when the lid was closed and I was not using it.
I was actually out, but when I came back just out of interest noticed several events
during 30 second period within these three hours:
06/12/2014 18:53:41.000 kernel[0]: Wake reason: EC.SleepTimer (SleepTimer)
06/12/2014 18:53:41.000 kernel[0]: Previous sleep cause: 5
06/12/2014 18:53:41.000 kernel[0]: AppleThunderboltNHIType2::prePCIWake - power up complete - took 2 us
06/12/2014 18:53:41.000 kernel[0]: AppleThunderboltGenericHAL::earlyWake - complete - took 1 milliseconds
06/12/2014 18:53:41.000 kernel[0]: IOThunderboltSwitch<0xffffff802c8b6400>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
06/12/2014 18:53:41.000 kernel[0]: IOThunderboltSwitch<0xffffff802c8b6400>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0
06/12/2014 18:53:41.000 kernel[0]: TBT W (2): 0x0100 [x]
06/12/2014 18:53:41.229 sharingd[237]: 18:53:41.228 : SDStatusMonitor::kStatusWirelessPowerChanged
06/12/2014 18:53:41.310 sandboxd[285]: ([441]) VPN Shield(441) deny mach-lookup com.apple.airportd
06/12/2014 18:53:41.330 sandboxd[285]: ([441]) VPN Shield(441) deny system-socket
06/12/2014 18:53:41.000 kernel[0]: AirPort: Link Up on awdl0
06/12/2014 18:53:41.352 VPN Shield[441]: en0 status changed: current ssid is (null), security is 9223372036854775807
06/12/2014 18:53:41.373 sandboxd[285]: ([441]) VPN Shield(441) deny mach-lookup com.apple.airportd
06/12/2014 18:53:41.397 VPN Shield[441]: en0 status changed: current ssid is (null), security is 9223372036854775807
06/12/2014 18:53:41.400 sandboxd[285]: ([441]) VPN Shield(441) deny system-socket
06/12/2014 18:53:41.000 kernel[0]: IO80211AWDLPeerManager::setAwdlOperatingMode Setting the AWDL operation mode from AUTO to SUSPENDED
06/12/2014 18:53:41.000 kernel[0]: IO80211AWDLPeerManager::setAwdlSuspendedMode() Suspending AWDL, enterQuietMode(true)
06/12/2014 18:53:41.000 kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
06/12/2014 18:53:41.428 hidd[69]: MultitouchHID: device bootloaded
06/12/2014 18:53:41.428 sandboxd[285]: ([441]) VPN Shield(441) deny mach-lookup com.apple.airportd
06/12/2014 18:53:41.448 sandboxd[285]: ([441]) VPN Shield(441) deny system-socket
06/12/2014 18:53:41.000 kernel[0]: en0: 802.11d country code set to 'GB'.
06/12/2014 18:53:41.000 kernel[0]: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
06/12/2014 18:53:41.000 kernel[0]: ARPT: 10506.747903: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
06/12/2014 18:53:41.535 networkd[148]: +[NETLedBelly stopFastFail] Clearing ledbelly failure cache
06/12/2014 18:53:41.537 configd[25]: network changed: v4(en0-:192.168.0.3) DNS- Proxy-
06/12/2014 18:53:41.538 UserEventAgent[17]: Captive: CNPluginHandler en0: Inactive
06/12/2014 18:53:41.539 discoveryd[49]: Basic Bonjour stop listening on en0
06/12/2014 18:53:41.541 discoveryd[49]: Basic WABServer NetResolverEvent no resolvers, resetting domains
06/12/2014 18:53:41.562 VPN Shield[441]: Network not reachable
06/12/2014 18:53:41.585 netbiosd[648]: network_reachability_changed : network is not reachable, netbiosd is shutting down
06/12/2014 18:53:41.606 VPN Shield[441]: en0 status changed: current ssid is (null), security is 9223372036854775807
06/12/2014 18:53:41.607 sharingd[237]: 18:53:41.606 : SDStatusMonitor::kStatusWirelessPowerChanged
06/12/2014 18:53:41.000 kernel[0]: ARPT: 10506.899969: MacAuthEvent en0 Auth result for: 7c:4c:a5:38:87:e1 MAC AUTH succeeded
06/12/2014 18:53:41.000 kernel[0]: AirPort: Link Up on en0
06/12/2014 18:53:41.000 kernel[0]: en0: BSSID changed to 7c:4c:a5:38:87:e1
06/12/2014 18:53:41.000 kernel[0]: en0::IO80211Interface::postMessage bssid changed
06/12/2014 18:53:41.000 kernel[0]: en0: BSSID changed to 7c:4c:a5:38:87:e1
06/12/2014 18:53:41.636 sharingd[237]: 18:53:41.635 : SDStatusMonitor::kStatusWirelessPowerChanged
06/12/2014 18:53:41.000 kernel[0]: Sandbox: VPN Shield(441) deny mach-lookup com.apple.airportd
06/12/2014 18:53:41.000 kernel[0]: Sandbox: VPN Shield(441) deny system-socket
06/12/2014 18:53:41.663 VPN Shield[441]: en0 status changed: current ssid is SKYAB961, security is 4
06/12/2014 18:53:41.000 kernel[0]: AirPort: RSN handshake complete on en0
06/12/2014 18:53:41.684 sandboxd[285]: ([441]) VPN Shield(441) deny mach-lookup com.apple.airportd
06/12/2014 18:53:41.752 sandboxd[285]: ([441]) VPN Shield(441) deny system-socket
06/12/2014 18:53:41.000 kernel[0]: Sandbox: VPN Shield(441) deny mach-lookup com.apple.airportd
06/12/2014 18:53:41.000 kernel[0]: Sandbox: VPN Shield(441) deny system-socket
06/12/2014 18:53:41.916 VPN Shield[441]: en0 status changed: current ssid is SKYAB961, security is 4
06/12/2014 18:53:42.000 kernel[0]: Sandbox: VPN Shield(441) deny mach-lookup com.apple.airportd
06/12/2014 18:53:42.000 kernel[0]: Sandbox: VPN Shield(441) deny system-socket
06/12/2014 18:53:42.147 VPN Shield[441]: en0 status changed: current ssid is SKYAB961, security is 4
06/12/2014 18:53:43.000 kernel[0]: IO80211AWDLPeerManager::setAwdlOperatingMode Setting the AWDL operation mode from SUSPENDED to AUTO
06/12/2014 18:53:43.000 kernel[0]: IO80211AWDLPeerManager::setAwdlAutoMode Resuming AWDL
06/12/2014 18:53:43.457 networkd[148]: +[NETLedBelly stopFastFail] Clearing ledbelly failure cache
06/12/2014 18:53:43.459 configd[25]: network changed: DNS* Proxy
06/12/2014 18:53:43.461 UserEventAgent[17]: Captive: [CNInfoNetworkActive:1709] en0: SSID 'SKYAB961' making interface primary (cache indicates network not captive)
06/12/2014 18:53:43.463 UserEventAgent[17]: Captive: CNPluginHandler en0: Evaluating
06/12/2014 18:53:43.468 discoveryd[49]: Basic Sockets,Warn UDS FD=37 ERROR: Send failed errno=32
06/12/2014 18:53:43.468 UserEventAgent[17]: Captive: en0: Not probing 'SKYAB961' (cache indicates not captive)
06/12/2014 18:53:43.469 UserEventAgent[17]: Captive: CNPluginHandler en0: Authenticated
06/12/2014 18:53:43.474 networkd[148]: +[NETLedBelly stopFastFail] Clearing ledbelly failure cache
06/12/2014 18:53:43.476 configd[25]: network changed: v4(en0!:192.168.0.3) DNS+ Proxy+ SMB
06/12/2014 18:53:43.000 kernel[0]: en0: BSSID changed to 7c:4c:a5:38:87:e1
06/12/2014 18:53:43.497 sharingd[237]: 18:53:43.497 : SDStatusMonitor::kStatusWirelessPowerChanged
06/12/2014 18:53:46.587 discoveryd[49]: None ClientIPC DNSServiceRemoveRecord: registrationId is 0 Client[netbiosd(648)]
06/12/2014 18:54:01.702 loginwindow[65]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
06/12/2014 18:54:09.000 kernel[0]: PM response took 28003 ms (26, powerd)
06/12/2014 18:54:09.000 kernel[0]: ARPT: 10534.833404: AirPort_Brcm43xx::powerChange: System Sleep
06/12/2014 18:54:09.000 kernel[0]: ARPT: 10534.833413: wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.
06/12/2014 18:54:11.000 kernel[0]: hibernate image path: /var/vm/sleepimage
06/12/2014 18:54:11.000 kernel[0]: efi pagecount 65
06/12/2014 18:54:11.000 kernel[0]: hibernate_page_list_setall(preflight 1) start 0xffffff808c149000, 0xffffff808c1d0000
06/12/2014 18:54:11.000 kernel[0]: hibernate_page_list_setall time: 111 ms
06/12/2014 18:54:11.000 kernel[0]: pages 666741, wire 124010, act 238391, inact 5, cleaned 0 spec 60, zf 17177, throt 0, compr 83330, xpmapped 40000
06/12/2014 18:54:11.000 kernel[0]: could discard act 102780 inact 26371 purgeable 17042 spec 57575 cleaned 0
06/12/2014 18:54:11.000 kernel[0]: WARNING: hibernate_page_list_setall skipped 25529 xpmapped pages
06/12/2014 18:54:11.000 kernel[0]: hibernate_page_list_setall preflight pageCount 124010 est comp 51 setfile 288358400 min 1073741824
06/12/2014 18:54:11.000 kernel[0]: AppleThunderboltNHIType2::prePCIWake - power up complete - took 2 us
06/12/2014 18:54:11.000 kernel[0]: AppleThunderboltGenericHAL::earlyWake - complete - took 0 milliseconds
06/12/2014 18:54:11.000 kernel[0]: [0xdcb1b0000, 0x15555000]
06/12/2014 18:54:11.000 kernel[0]: [0xb8165f000, 0xbe79000]
06/12/2014 18:54:11.000 kernel[0]: [0xa0ffcd000, 0x593d000]
06/12/2014 18:54:11.000 kernel[0]: [0x10eeee000, 0x58ce000]
06/12/2014 18:54:11.000 kernel[0]: [0xc87b12000, 0x55f8000]
06/12/2014 18:54:11.000 kernel[0]: [0xd47712000, 0x42f000]
06/12/2014 18:54:11.000 kernel[0]: [0x687263000, 0x509d000]
06/12/2014 18:54:11.000 kernel[0]: [0xd47b41000, 0x4cc4000]
06/12/2014 18:54:11.000 kernel[0]: [0xcaf772000, 0x429f000]
06/12/2014 18:54:11.000 kernel[0]: [0x0, 0x0]
06/12/2014 18:54:11.000 kernel[0]: kern_open_file_for_direct_io(0) took 3 ms
06/12/2014 18:54:11.000 kernel[0]: Opened file /var/vm/sleepimage, size 1073741824, partition base 0x0, maxio 2000000 ssd 1
06/12/2014 18:54:11.000 kernel[0]: hibernate image major 1, minor 0, blocksize 4096, pollers 5
06/12/2014 21:21:13.000 kernel[0]: IOThunderboltSwitch<0xffffff802c8b6400>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
Could someone please explain how it is possible for the computer to generate a wake message if the lid is closed? Is it possible that someone was trying to use the computer or attempted to use it either directly or indirectly?
Thanks

Apple has a feature called Power Nap which allows the computer to wake periodically to perform certain tasks. I've included a link to Apple's knowledgebase article about it.

Similar Messages

Wakes from sleep while lid closed

I got my MBP three weeks ago and I have noticed that when I have the lid closed and it is sleeping and I set it down it begins to make noise and when I open the lid I see that has already come out of sleep mode. I know that the MBP's have a motion sensor that shuts off the hard drives when it senses that the computer is falling or something. When I'm putting it down and it does this, it is always on a hard surface but it's not like I'm dropping the computer down, I'm gently placing it. Any thoughts?

That's cool.. It's good to see they fixed it on the latest revision. The college ordered these right before apple's last upgrade to the MBP. These are the 2.33 GHZ Core 2 Duo machines. The tech did mention that I could take these to the nearest Apple store.. a 2 hour drive, and one of the people at the store could evaluate them and then decide if they should be fixed. No guarantee they would.. and according to him and my description.. "the behaviour is expected.."
While it would be worth popping them into a fedex shipper to know they'd get fixed.. I guess I have to decide if it's worth a two hour drive to maybe get it fixed. The sleep sensor is such a simple and small part.. I'm reasonably confident I can fix it. I'll weigh my options in the next couple of days. Now that I know what's causing it.. I'm not as worried about it as I was. I had envisioned bare wires shorting out in the lid or something.
I will contrast Apple's support with Dell's though. I really despise Dell.. but, when the college has a problem with a machine, they send a part out no questions asked. The college has it's own tech support team and Dell will either send a tech immediately, or send the part to one of our team members. I'd really like to see the college choose more apple products. But, their response to our repair request has hurt that effort. Can you see us with a lab full of macs driving them two hours to an Apple store because of some hardware problem? We don't pay any extra for the Dell support, it's part of the product warranty. Apple could learn a thing or two...
I may stew on this a few days and call tech support again..

PB battery drained overnight while lid closed....any thoughts?

This was the first time I've experienced any problems with my PB. Last night I left the office and closed my lid as always. My PB was unplugged from land power. I watched, as I always do, the Apple light go off and my standby light come on, then I went home.
This morning I came in, opened it, logged in and immediately got a notice that the battery was low. I attached the power cord and noticed I had about 2% battery life left. Now, the only thing I can think of, since all known applications were closed, was that I connected to my network via CAT5 and not wifi. I'm wondering if something was going on over the ethernet??? I have no idea why my battery would have been drained overnite with the lid closed. I searched the logs and nothing strange pops up.
Any thoughts?
Tom

In general there is always a trickle drain happening even with the lid closed. Some applications may leave the Powerbook on, or wake it from sleep on a timed schedule. Turn off the lights to see if the Apple logo is lit to verify it did indeed shut off the screen. There have been known applications to be open that force the machine to keep the screen on even when the lid is closed.
The battery is technically known to last 5 hours on limited charge, that closed as you surmised is able to last longer. But how much longer varies depending on just how full the battery was before you unplugged it. The reading on the menubar of it being full is not necessarily accurate.
I would not leave it on Energy Saver overnight all the time. At least once a month leave it on screen saver instead. Unattended someone could also steal the machine in the middle of the night. I would not leave it unattended. Especially in an office environment it shouldn't be unattended unless under lock and key.

Scheduled system wakeup from a Sleep state while lid closed

I'm wanting to backup my Ti Power Book data using the .Mac Backup 3 (BU3) application at 2am each day.
On my desktop system which is a Power Mac G5 I perform a BU3 every day at around 2am. The Energy Saver is configured to wake my Power Mac from a sleep state at 2am and not go back to sleep until some 1 hr of inactivity. Shortly after 2am I have various scheduled BU3 Plans that execute. This is working flawlessly for me.
I now want to do the same thing for my Power Book - but with its lid/screen closed. I've tried the same setup as for my Power Mac and the Power Book will wakeup at 2am but very quickly returns to sleep mode because its lid is closed which stops the BU3 from executing. I do not want to leave the Power Book's lid open at night time.
Is there a way to meet my requirements ?

Hi, Barry. No, there isn't — unless you connect an external monitor, keyboard and display to the Powerbook as described in this article.

How to keep file sharing on while MacBook lid closed?

would like to keep file sharing on while lide closed on macbook...so i can access files with other device.

i really dont want to be needing to buy a extra screen just to get something working that i had going before...
i do have a bluetooth mouse attached and everytime i move it..the macBook seems to start up but then immediatly goes back to sleep..playing dead
all i want is that file sharing continues when i close the lid...
Do you think that it might be a hardware problem?
Or maybe software...because since I downloaded Lion...screensaver has been jumping in randomly too...I know it's nothing special since many people have encountered this issue and i just reinstalled lion and it seems to be fine so far....
anyhow... still hoping to find the right solution...
But thanks for the help..really appreciate it...

[SOLVED] Laptop resumes from suspend while lid is still closed

Hi all,
I'm having some weird issue ever since I installed arch on my new laptop (Haswell).
When I put my computer to suspend by closing the lid, all goes well.
But the computer resumes by itself after a while. I have no idea why, WoL is disabled on both ethernet and wifi.
Can someone help figure out what is causing the computer to resume?
For example here is a magic wake up after 1 hour asleep.
Feb 15 00:37:15 jitte systemd[1]: Starting TLP suspend/resume...
Feb 15 00:37:15 jitte tlp[24682]: grep: /sys/devices/platform/dock.?/type: No such file or directory
Feb 15 00:37:15 jitte systemd[1]: Started TLP suspend/resume.
Feb 15 00:37:15 jitte systemd[1]: Starting Sleep.
Feb 15 00:37:15 jitte systemd[1]: Reached target Sleep.
Feb 15 00:37:15 jitte systemd[1]: Starting Suspend...
Feb 15 00:37:15 jitte systemd-sleep[24748]: Suspending system...
Feb 15 00:37:15 jitte kernel: PM: Syncing filesystems ... done.
Feb 15 00:37:15 jitte kernel: PM: Preparing system for mem sleep
Feb 15 00:37:15 jitte kernel: bbswitch: enabling discrete graphics
Feb 15 01:34:26 jitte kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Feb 15 01:34:26 jitte systemd[1]: Time has been changed
Feb 15 01:34:26 jitte kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Feb 15 01:34:26 jitte kernel: PM: Entering mem sleep
Feb 15 01:34:26 jitte kernel: Suspending console(s) (use no_console_suspend to debug)
Feb 15 01:34:26 jitte kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 15 01:34:26 jitte kernel: sd 0:0:0:0: [sda] Stopping disk
Feb 15 01:34:26 jitte kernel: mei_me 0000:00:16.0: suspend
Feb 15 01:34:26 jitte kernel: PM: suspend of devices complete after 220.139 msecs
Feb 15 01:34:26 jitte systemd[607]: Time has been changed
Feb 15 01:34:26 jitte kernel: PM: late suspend of devices complete after 0.115 msecs
Feb 15 01:34:26 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
Feb 15 01:34:26 jitte kernel: PM: noirq suspend of devices complete after 66.764 msecs
Feb 15 01:34:26 jitte kernel: ACPI: Preparing to enter system sleep state S3
Feb 15 01:34:26 jitte kernel: PM: Saving platform NVS memory
Feb 15 01:34:26 jitte kernel: Disabling non-boot CPUs ...
Feb 15 01:34:26 jitte kernel: smpboot: CPU 1 is now offline
Feb 15 01:34:26 jitte kernel: smpboot: CPU 2 is now offline
Feb 15 01:34:26 jitte kernel: smpboot: CPU 3 is now offline
Feb 15 01:34:26 jitte kernel: ACPI: Low-level resume complete
Feb 15 01:34:26 jitte kernel: PM: Restoring platform NVS memory
Feb 15 01:34:26 jitte kernel: Enabling non-boot CPUs ...
Feb 15 01:34:26 jitte kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Feb 15 01:34:26 jitte kernel: Intel pstate controlling: cpu 1
Feb 15 01:34:26 jitte kernel: CPU1 is up
Feb 15 01:34:26 jitte kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Feb 15 01:34:26 jitte kernel: Intel pstate controlling: cpu 2
Feb 15 01:34:26 jitte kernel: CPU2 is up
Feb 15 01:34:26 jitte kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Feb 15 01:34:26 jitte kernel: Intel pstate controlling: cpu 3
Feb 15 01:34:26 jitte kernel: CPU3 is up
Feb 15 01:34:26 jitte kernel: ACPI: Waking up from system sleep state S3
Feb 15 01:34:26 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 15 01:34:26 jitte kernel: PM: noirq resume of devices complete after 130.807 msecs
Feb 15 01:34:26 jitte kernel: PM: early resume of devices complete after 0.108 msecs
Feb 15 01:34:26 jitte kernel: i915 0000:00:02.0: setting latency timer to 64
Feb 15 01:34:26 jitte kernel: mei_me 0000:00:16.0: irq 57 for MSI/MSI-X
Feb 15 01:34:26 jitte kernel: snd_hda_intel 0000:00:03.0: irq 61 for MSI/MSI-X
Feb 15 01:34:26 jitte kernel: ehci-pci 0000:00:1d.0: setting latency timer to 64
Feb 15 01:34:26 jitte kernel: ahci 0000:00:1f.2: setting latency timer to 64
Last edited by jtheoof (2014-03-16 19:15:02)

So here's the update for today: sudo journalctl -amb.
Feb 25 13:39:00 jitte kernel: ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event
Feb 25 13:39:00 jitte kernel: ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event
Feb 25 13:39:00 jitte systemd-logind[276]: Lid closed.
Feb 25 13:39:00 jitte systemd-logind[276]: Suspending...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> sleep requested (sleeping: no enabled: yes)
Feb 25 13:39:00 jitte NetworkManager[273]: <info> sleeping or disabling...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): deactivating device (reason 'sleeping') [37]
Feb 25 13:39:00 jitte dhcpcd[22409]: received SIGTERM from PID 273, stopping
Feb 25 13:39:00 jitte dhcpcd[22409]: wlp2s0: removing interface
Feb 25 13:39:00 jitte dhcpcd[22409]: exited
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 22409
Feb 25 13:39:00 jitte NetworkManager[273]: <info> Removing DNS information from /usr/bin/resolvconf
Feb 25 13:39:00 jitte kernel: wlp2s0: deauthenticating from 00:24:d4:5f:dc:d8 by local choice (reason=3)
Feb 25 13:39:00 jitte kernel: cfg80211: Calling CRDA to update world regulatory domain
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): cleaning up...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): taking down device.
Feb 25 13:39:00 jitte NetworkManager[273]: <info> NetworkManager state is now ASLEEP
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (enp3s0f1): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (enp3s0f1): cleaning up...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (enp3s0f1): taking down device.
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte dbus[278]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Feb 25 13:39:00 jitte systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte dbus[278]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 25 13:39:01 jitte systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 25 13:39:01 jitte gnome-session[1672]: Window manager warning: Log level 16: gsignal.c:2593: instance '0x15b1e20' has no handler with id '468541'
Feb 25 13:39:05 jitte systemd-logind[276]: Delay lock is active but inhibitor timeout is reached.
Feb 25 13:39:05 jitte systemd[1]: Starting Sleep.
Feb 25 13:39:05 jitte systemd[1]: Reached target Sleep.
Feb 25 13:39:05 jitte systemd[1]: Starting Suspend...
Feb 25 13:39:05 jitte systemd-sleep[22893]: Suspending system...
Feb 25 13:39:05 jitte kernel: PM: Syncing filesystems ... done.
Feb 25 13:39:05 jitte kernel: PM: Preparing system for mem sleep
Feb 25 13:39:05 jitte kernel: bbswitch: enabling discrete graphics
Feb 25 17:22:59 jitte kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Feb 25 17:22:59 jitte systemd[1]: Time has been changed
Feb 25 17:22:59 jitte systemd[1666]: Time has been changed
Feb 25 17:22:59 jitte kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Feb 25 17:22:59 jitte kernel: PM: Entering mem sleep
Feb 25 17:22:59 jitte kernel: Suspending console(s) (use no_console_suspend to debug)
Feb 25 17:22:59 jitte kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 25 17:22:59 jitte kernel: sd 0:0:0:0: [sda] Stopping disk
Feb 25 17:22:59 jitte kernel: PM: suspend of devices complete after 1098.028 msecs
Feb 25 17:22:59 jitte kernel: PM: late suspend of devices complete after 0.504 msecs
Feb 25 17:22:59 jitte kernel: pcieport 0000:00:1c.3: System wakeup enabled by ACPI
Feb 25 17:22:59 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
Feb 25 17:22:59 jitte kernel: PM: noirq suspend of devices complete after 66.728 msecs
Feb 25 17:22:59 jitte kernel: ACPI: Preparing to enter system sleep state S3
Feb 25 17:22:59 jitte kernel: PM: Saving platform NVS memory
Feb 25 17:22:59 jitte kernel: Disabling non-boot CPUs ...
Feb 25 17:22:59 jitte kernel: kvm: disabling virtualization on CPU1
Feb 25 17:22:59 jitte kernel: smpboot: CPU 1 is now offline
Feb 25 17:22:59 jitte kernel: kvm: disabling virtualization on CPU2
Feb 25 17:22:59 jitte kernel: smpboot: CPU 2 is now offline
Feb 25 17:22:59 jitte kernel: kvm: disabling virtualization on CPU3
Feb 25 17:22:59 jitte kernel: smpboot: CPU 3 is now offline
Feb 25 17:22:59 jitte kernel: ACPI: Low-level resume complete
Feb 25 17:22:59 jitte kernel: PM: Restoring platform NVS memory
Feb 25 17:22:59 jitte kernel: Enabling non-boot CPUs ...
Feb 25 17:22:59 jitte kernel: x86: Booting SMP configuration:
Feb 25 17:22:59 jitte kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Feb 25 17:22:59 jitte kernel: kvm: enabling virtualization on CPU1
Feb 25 17:22:59 jitte kernel: Intel pstate controlling: cpu 1
Feb 25 17:22:59 jitte kernel: CPU1 is up
Feb 25 17:22:59 jitte kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Feb 25 17:22:59 jitte kernel: kvm: enabling virtualization on CPU2
Feb 25 17:22:59 jitte kernel: Intel pstate controlling: cpu 2
Feb 25 17:22:59 jitte kernel: CPU2 is up
Feb 25 17:22:59 jitte kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Feb 25 17:22:59 jitte kernel: kvm: enabling virtualization on CPU3
Feb 25 17:22:59 jitte kernel: Intel pstate controlling: cpu 3
Feb 25 17:22:59 jitte kernel: CPU3 is up
Feb 25 17:22:59 jitte kernel: ACPI: Waking up from system sleep state S3
Feb 25 17:22:59 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 25 17:22:59 jitte kernel: PM: noirq resume of devices complete after 132.766 msecs
Feb 25 17:22:59 jitte systemd[1666]: Service bluetooth.target is not needed anymore. Stopping.
Feb 25 17:22:59 jitte systemd[1]: Service bluetooth.target is not needed anymore. Stopping.
Feb 25 17:22:59 jitte systemd[1666]: Stopping Bluetooth.
Feb 25 17:22:59 jitte systemd[1666]: Stopped target Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Stopping Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Stopped target Bluetooth.
Feb 25 17:22:59 jitte systemd[1666]: Starting Bluetooth.
Feb 25 17:22:59 jitte systemd[1666]: Reached target Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Starting Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Reached target Bluetooth.
Feb 25 17:22:59 jitte kernel: PM: early resume of devices complete after 0.347 msecs
Feb 25 17:22:59 jitte kernel: hpet1: lost 2539 rtc interrupts
Feb 25 17:22:59 jitte kernel: mei_me 0000:00:16.0: irq 58 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: usb usb1: root hub lost power or was reset
Feb 25 17:22:59 jitte kernel: usb usb2: root hub lost power or was reset
Feb 25 17:22:59 jitte kernel: snd_hda_intel 0000:00:03.0: irq 61 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: irq 62 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: snd_hda_intel 0000:00:1b.0: irq 63 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: pcieport 0000:00:1c.3: System wakeup disabled by ACPI
Feb 25 17:22:59 jitte kernel: dpm_run_callback(): pnp_bus_resume+0x0/0xa0 returns -19
Feb 25 17:22:59 jitte kernel: PM: Device 00:07 failed to resume: error -19
Feb 25 17:22:59 jitte kernel: usb 3-1: reset high-speed USB device number 2 using ehci-pci
Feb 25 17:22:59 jitte kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd ef/10:09:00:00:00:b0 (SET FEATURES) succeeded
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 25 17:22:59 jitte kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd ef/10:09:00:00:00:b0 (SET FEATURES) succeeded
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 25 17:22:59 jitte kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
Feb 25 17:22:59 jitte kernel: ata1.00: configured for UDMA/133
Feb 25 17:22:59 jitte kernel: sd 0:0:0:0: [sda] Starting disk
Feb 25 17:22:59 jitte kernel: usb 1-5: reset high-speed USB device number 2 using xhci_hcd
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af174f00
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af174f40
Feb 25 17:22:59 jitte kernel: usb 1-6: reset full-speed USB device number 3 using xhci_hcd
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af143780
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af1437c0
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af143800
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802320b0900
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802320b0940
Feb 25 17:22:59 jitte kernel: usb 1-7: reset full-speed USB device number 5 using xhci_hcd
Feb 25 17:22:59 jitte kernel: [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88022dc25300
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88022dc25340
Feb 25 17:22:59 jitte kernel: usb 1-7: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes
Feb 25 17:22:59 jitte kernel: PM: resume of devices complete after 1355.352 msecs
Feb 25 17:22:59 jitte kernel: PM: Finishing wakeup.
Feb 25 17:22:59 jitte kernel: Restarting tasks ...
Feb 25 17:22:59 jitte kernel: iwlwifi 0000:02:00.0: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: rtsx_pci 0000:03:00.0: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: r8169 0000:03:00.1: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: pci 0000:04:00.0: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: done.
Feb 25 17:22:59 jitte kernel: video LNXVIDEO:00: Restoring backlight state
Feb 25 17:22:59 jitte kernel: video LNXVIDEO:01: Restoring backlight state
Feb 25 17:22:59 jitte kernel: bbswitch: disabling discrete graphics
Feb 25 17:22:59 jitte kernel: ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
Feb 25 17:22:59 jitte kernel: Bluetooth: hci0: read Intel version: 370710018002030d00
Feb 25 17:22:59 jitte kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Feb 25 17:22:59 jitte kernel: Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
Feb 25 17:22:59 jitte bluetoothd[272]: Failed to set mode: Blocked through rfkill (0x12)
Feb 25 17:22:59 jitte systemd-sleep[22893]: System resumed.
Feb 25 17:22:59 jitte systemd[1]: Started Suspend.
Feb 25 17:22:59 jitte systemd[1]: Requested transaction contradicts existing jobs: File exists
Feb 25 17:22:59 jitte systemd[1]: Service sleep.target is not needed anymore. Stopping.
Feb 25 17:22:59 jitte systemd[1]: Stopping Sleep.
Feb 25 17:22:59 jitte systemd[1]: Stopped target Sleep.
Feb 25 17:22:59 jitte systemd[1]: Reached target Suspend.
Feb 25 17:22:59 jitte systemd-logind[276]: Operation finished.
Feb 25 17:22:59 jitte NetworkManager[273]: <info> wake requested (sleeping: yes enabled: yes)
Feb 25 17:22:59 jitte NetworkManager[273]: <info> waking up and re-enabling...
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): bringing up device.
Feb 25 17:22:59 jitte kernel: iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
Feb 25 17:22:59 jitte kernel: iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
Feb 25 17:22:59 jitte kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): preparing device.
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): deactivating device (reason 'managed') [2]
Feb 25 17:22:59 jitte NetworkManager[273]: <info> NetworkManager state is now DISCONNECTED
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): bringing up device.
Feb 25 17:22:59 jitte kernel: r8169 0000:03:00.1 enp3s0f1: link down
Feb 25 17:22:59 jitte kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0f1: link is not ready
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): preparing device.
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): deactivating device (reason 'managed') [2]
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0) supports 5 scan SSIDs
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0): supplicant interface state: starting -> ready
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Feb 25 17:23:00 jitte NetworkManager[273]: <warn> Trying to remove a non-existant call id.
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0): supplicant interface state: ready -> disconnected
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0) supports 5 scan SSIDs
Feb 25 17:23:02 jitte kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
Feb 25 17:23:02 jitte kernel: atkbd serio0: Use 'setkeycodes e00d <keycode>' to make it known.
What's really odd is that the laptop woke up at the exact same time as yesterday. What could be causing that?
I'm using gnome-shell v3.10.3-1, linux-mainline v3.14rc3-1.

Can't use external display w/o magsafe connected while lid is closed

I've got the latest 15" MBP with Retina Display. At work I connect it to a 23" Cinema Display and at home I us a 20" Cinema Display in my studio.
The desk I'm using isn't big enough to host my MBP with the lid up with my 20" display side-by-side , so I have to keep my MBP folded all the time. When it is folded I have noticed that I need the MagSafe adapter connected all the time, or else it will not let me use my 20" display or the USB ports. This means that I can't use my Apogee Duet via USB either, if I don't connect the MagSafe adapter.
Now you might think "well, you're at your desk, just connect the adapter and be happy". I would love to, but the thing is that I record lots of guitars in my home studio and when my computer is powered by the magsafe and I've got a guitar amp running I get lots of humming noises in the signal. I've tried different power outlets and stuff, and I can't do anything but unplug the magsafe to get rid of the problem.
Is there any one else out there with this problem, that you can't use an external display (or your USB ports) with the lid closed without Magsafe adapter?

Well the official document, posted by CT, on clamshell mode doesn't support your theory that it worked with your older/pervious macbook pro and it certainly doesn't work like that with your newer mac.
So you are either mistaken or your older/pervious mac was broken in some way to allow it to work without a AC adapter connected.
henkeblomqvist wrote:
No it hasn't. My previous MacBook Pro handled that just fine.
And I do have trackpad and keyboard connected, both via bluetooth.

How do I use my macbook pro lid closed

How do I use my macbook pro lid closed?

Well what i'm trying to do is keep file sharing on while macBook is closed so i can access files through "newtwok" (Back to my mac) with my imac...
Ideally i would then control my macBook with screen sharing on my imac while the MacBook is stored behind my iMac...
Somehow it worked before but now it stopped...and everytime i close the lid ..mac book pro goes black screen and completly disconnects from the newtwork...
Everything works fine with lid open..
I am trying to do this because i have a new imac with thunderbold and an older macbook pro with mini display port..and as you might already know...you canot connect these thow devices using thunderbolt cable...which really *****....there is also no adaport enabling this...and i really dont need to buy another mac book that just has one more hole in it >.<
Anyway..hope there is a solution somewhere to keep file sharing going while lid down..
regards remo

Front Row - Lid Closed - Blank Videos (but with audio)

I hooked my computer up to my TV last night to watch some videos through front row (stupid quicktime and the pro lockout on full screen - talk about penny pinching from Apple!). Front row worked fine if I set it up so that the TV mirrored my laptop display. However, if I tried to run the laptop in lid closed mode with the TV as my main/only monitor everything would work except for the videos. They would be black while retaining the audio. For example, the little preview movies shown in the selection menu were black as was the movie when you played it.
Is this a known bug? Is there a fix? (Obviously I can run it more or less similarly with mirroring and my main screen dimmed as I did.)

i'm having the same issue. The video i tried was purchased from the iTunes music store. i see no preview of the video and no video is played on screen however audio is present. the same problem also occurs when trying to watch a movie trailer via movie trailer front row interface. All Front Row graphics are seen, only video is a problem. I can open and play back the video without problems in Quicktime Pro. (fullscreen)
The video output is 1280x720 sent to a samsung tv using a built in profile with overscan disabled.
Macbook (white) Mac OS X (10.4.6) 2.0Ghz Core Duo - 2GB RAM

How to work on external monitor with lid closed?

I have an external monitor connected to my MB Pro and would like to work with the lid closed. When I shut it, the monitor also goes to sleep. Yesterday I did something right and the monitor woke but I was able to keep the computer closed. Today it's not working. I use a wireless keyboard that also goes to sleep when the lid closes.
What's the procedure to keep the monitor awake while the laptop is closed?
System 10.6.8

Yes, I have done that and tried it over and over and it still won't work. The monitor went on for a few seconds and then went black again.
Is it possible to do this with a wireless keyboard? I do press the power key to try to wake to keyboard but nothing happens.

Operating with lid closed

I'm intending to use my MBP as a desktop machine for much of the time. I anticipate connecting to a 24" screen and probably using a mouse & keyboard while on the desk. I'm a bit pressed for space would really like to operate the MBP with its lid closed.
I understand that there are third party utilities that prevent lid closure from activating sleep mode, but am concerned that the machine might get a bit hot.
What's the view of the panel on this issue?

What you're asking for is very common and the machines are designed to do it. The ventilation system doesn't really care whether the lid is closed or not, because the vents are out the back. The only danger of overheating is if it somehow runs while it's all sealed up in a bag.

Lid Closed Mode on an 867?

I am surethis has been covered in these forums somewhere, but I must be using the wrong search terms, b/c I can't seem to find a conclusive answer. So here it goes:
Can I run my 12" aluminum 867MHz Powerbook with the lid closed while attached to an external display? Or is that an option only on the newer (newest) PBs? I know iBooks need the keyboard clear to help dissapate heat. Is that an issue with my PB as well?
Thanks!

Hi,
I've been using my 867 Mhz PowerBook with the lid closed and connected to an external display, keyboard, and mouse ever since I bought it in March, 2003. I've had no heat-related problems at all. However, whenever I have a chance, I prop up the back end of the PowerBook on somethat that will raise the rear of the machine off the table about an inch or so to allow for better air circulation underneath it, where it seems to get the hottest. I didn't do this as a response to any problem, but when I realized how warm the underside of the machine gets, I figured it was a prudent thing to do.
Ken

Macbook sleep wake up with lid closed

Hi everybody. Since 10.9 I had a strange issue with sleep on my MBP 15. If I put it in sleep with the button and I close the lid, it will wake up closed waiting for the password.
Also, if it is in sleep while charging, or charged, and I plug off the magsafe, it will wake up again....even with lid closed.
Already resetted PRAM, SMC, all the basics, any idea?
Thnx in advance

Sleep - Why your Mac might not sleep or stay in sleep mode
Sleep - Won’t

How to keep unplugged macbook awake with lid closed

My macbook would stay awake while its plugged in with its lid closed, but it won't stay awake once its unplugged.
any suggestions?
thx!

Requirements for closed display mode:
Power adapter
External keyboard, mouse, or trackpad
External display
If any of these conditions are missing, then the closed MBA will sleep. So, unplugging the power will sleep the system.

Using MBA connected to iMac with lid closed

Just purchased my 11" MBA and its working a great replacement for my 15" MBP, especially for travel.
One thing I haven't been able to do yet though is work with the MBA closed while connected to my iMac (like using an external Studio Display). I do this all the time with the MBP. I can plug it in (power and mini-display) keep the lid closed, and wake it with my BT keyboard an mouse.
Unfortunately, the MBA is not waking with the keyboard or mouse.
Any ideas? Is anyone else using their MBA like this?

Performed an SMC reset and it works like a charm.
This 11" MBA is a great replacement for my old 15" MBP. Runs on the 27" iMac fantastic (although no sound is coming through).

Console events while lid closed

Similar Messages

Maybe you are looking for