No SSL after sleep

I put either my powerbook 12 inch or my Intel Imac to sleep. I go to sleep then wake up in the day and I have no ssl for
www.google.com./ig
mail
aduim
etc
To fix it I have to unplug my cable modem and plug back in.
The Imac did this straight out of the box. My powerbook does this to all accounts. On the new one only the account I used the migration wizard does this.

I guess the problem is when you wake your mac from sleep the router does not give it an ip address.
So the next time you get this problem open your systempreferences-->network-->show built-in ethernet--tcp/ip
does it show that you have an ip address beggingin 192.168.x.x?

Similar Messages

HP SimplePass Reader Does not Work after Sleep

I have only had my laptop for a week - the fingerprint reader stopped working 2 days after I bought it. I have tried everything: removing and re-installing various drivers and software, stopping and starting Credentials Manager, unchecking the box that allows the computer to turn the reader off to save power, etc.
I have gotten it to the point where it functions when the computer is logged in, but not after sleep. It works once if you restart the computer, but after waking it from sleep it does not initialize. (no light or anything) However, if you "lock" the desktop from the start menu, the reader will log it in again. (without closing the lid or putting it to sleep)
Simple Pass version 6.0 (latest downloaded from HP.com)
Envy Dv6 7229wm
Windows 8 64-bit
Thanks

Hello hawvi,
I see that you are having problems with the fingerprint reader not working after returning from sleep mode. I would like to help with this issue but I need some information.
Can you provide the full model and product number of the computer? Here is a link that shows how to find that information.
What operating system are you using?
How long have you had the problem?
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

X1 Carbon Touch Screen stops responding after sleep

Hi,
My X1 Screen does not come back after sleep for several minutes. I've encountered this problem the very fist day I've received it, a reboot solved the problem but after few days it happened again, this time it took 2-3 hours for it to come back after several reboots. After a week it was gone for good, Service replaced the motherboard and just received my X1 back yesterday. Today it happened again. A reboot solved the problem but symptoms are same. Comp goes to sleep, when I try wake it up, X1 works but diplay is totaly gone. I can hear the sounds, see the fingerprint sensor etc is alive but can not wake up the display..
Model is 208A and Win 8.1
Any ideas ?
Thanks

Hey...got your back on this one! I returned a T440s because of this.....tech support had no idea...same problem for the replacement they sent to me, and again they it's a motherboard issue. Nope....trial and error...found the solution. Download and upgrade your fingerprint pro software and it's fixed. Here is the link. Please post if it worked for you too!
http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS031504

HT4279 ATI Radeon HD 5870 screen resets size after after sleeping. Why?

Purchased an ATI Radeon HD 5870. When connected to 1920x1080 it leaves a third of the screen out. However after starting up it fits the screen. Only after sleeping does it reset to this faulty screen size. I have attempted every Mini dv adapter vga,dvi and hdmi. All lead to the same issue or another.
Is this card defective? Is this an issue with the Lion OS?

Ok let me go into more detail for you.
Macpro had 2 Geforce gt 120 video cards. I recently had some blocking issues ( where the screen just over lays a bounch of boxes with random parts of the background and or aps running). Decided to upgrade to the Radeon 5870. Before the upgrade i have been using a Samsung LCD tv and and old Dell monitor. Worked great. Tv res was set to 1920x1080. Instailed the new card. Hooked up the Dell to the DVI output and Tv to a Mini DV at first using the Mini DV to DVI. Ended up with the half the screen issue. Took the back and got the Mini DV to HDMI. I didnt have the size issue but when set to 1080 it was not hidef. Took that back and got the Mini DV to VGA. Now here is where I currently am stuck. When both the TV (Mini to VGA) and the Dell (VGA to DVI) are connected to the 5870 and the harddrive and monitors go to sleep it resets and i lose an 8th of the screen. I currently am just using the TV and everything seems to be fine. Also on the amount i lose there is a dotted line that some times flickers. Not sure if that means anything.

No display after sleep with macmini using DVI - S-video/composite under XP

Hi guys, I have installed XP on my mini. I have CRT TV so I'm using
DVI -> S-video/composite to output to my TV.
The problem is after sleep - there is no display (it's woking only after reset).
I installed the latest drivers from the mac os 10.5 DVD & updated the graphics driver from Intel.
Please help

Unfortunately, no answer, as I'm having the similar problem with a Samsung SyncMaster 215tw and a G4 Mini. It works with the DVI-VGA adapter and the VGA cable into the montor's VGA port. However, connecting with the G$ Mini's DVI port with the monitor's DVI port using a DVI cable doesn't work. I cannot figure out why this doesn't work.
The DVI cable is good and the monitor's DVI port is good, as the connection does work using my friend's Intel Mini's DVI port connected to the monitor's DVI port using the DVI cable.
The monitor is new, too, and otherwise works fine with my other Macs connected with the VGA port. (I've not tried the additional ports as yet.)
Although the monitor is supposed to synchroize automatically, I also tried manually presetting the G4 Mini to different resolutions, but that didn't make any difference. The screen remains black when it should be showing the booting Apple icon.
Any idea what is going wrong here, please, as it sounds as if this same thing occurs with various monitors?

Crashing at start up...then after sleep, two problems, same reason?

new macbookpro 2.2. Since purchase it has been crashing at first start up every morning -long lines with pixels and smal squares with piwels in the background- Once it starts the 2nd time works wonderfully until I put it to sleep. Then wakes up normally and a few minutes later (it varies) it freezes totally again -small squares, pointer spinning- and I have too shut down with power button (force quit never works in this situations).
I reinstalled Leopard 3 times by now without success, then took it to the official service. They run tests and the new HD gave a problem under the SMART protocol. I told them I replaced the original 120gb for a 250gb Samsung, but the problem existed from the very beginning, still under the situation I opted for a new 250gb hard drive which they installed. They also installed a fresh leopard and told me the MBP worked fine.
Took it home and migrated from time machine again, the problem persisted.It crashes first thing in the morning and again when after sleep.
I also noticed that any applications may start-crash the first time I try. The second time is generally fine and works well.
I am thinking to take it back to the shop but believe they only will run standardized test and nothing will happen.
It could be something I do when migrating from time machine?
It could be some hardware (graphic card GeForce 8600M GT)?
I had reseted PRAM, run test with techtool (the only problem that shows is when tests the video card), run test with cocktail.
I never used the console but I am willing to start doing it.
Anybody has a clue?
Thanks!
here is the last application crash from this morning,
The freezes I don't know if they get registered anywhere.
Mail2008-02-20-075948macbook-pro-de-javier-gomez.crash
Process: Mail [912]
Path: /Applications/Mail.app/Contents/MacOS/Mail
Identifier: com.apple.mail
Version: 3.2 (919)
Build Info: Mail-9190000~3
Code Type: X86 (Native)
Parent Process: launchd [136]
Date/Time: 2008-02-20 07:59:48.762 +0100
OS Version: Mac OS X 10.5.2 (9C31)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x00000000967b4b28
Crashed Thread: 22
Application Specific Information:
-[MessageRouter routeQueuedMessages]
-[POPAccount fetchSynchronously]
-[POPAccount fetchSynchronously]
-[MailApp _synchronouslyTellSyncServicesToRegisterAndSync]
Thread 0:
0 libSystem.B.dylib 0x9678debc OSAtomicCompareAndSwapPtrBarrier + 0
1 ...ple.CoreServices.CarbonCore 0x924ff71f TSAcquireReader + 101
2 ...ple.CoreServices.CarbonCore 0x92506e2a AllocateHandleFromPool + 32
3 ...ple.CoreServices.CarbonCore 0x92509c59 CSMemNewHandle + 16
4 ...ple.CoreServices.CarbonCore 0x9252943f RegisterComponentResourcePtr + 491
5 ...ple.CoreServices.CarbonCore 0x92527a4d registerSystemComponents + 317
6 ...ple.CoreServices.CarbonCore 0x925276b5 FindNextComponentInternal(ComponentRecord*, ComponentDescription*) + 95
7 ...ple.CoreServices.CarbonCore 0x9252763f FindNextComponent + 53
8 com.apple.AppKit 0x9414809e _initializeCA + 991
9 com.apple.AppKit 0x94147bea -[NSSound _postInitialization] + 348
10 com.apple.AppKit 0x941479d9 -[NSSound initWithContentsOfURL:byReference:] + 269
11 com.apple.MessageFramework 0x003c02f7 +[NSSound(MessageAdditions) _playNextSound] + 454
12 com.apple.Foundation 0x922bdfce __NSFireDelayedPerform + 382
13 com.apple.CoreFoundation 0x91a07b5e CFRunLoopRunSpecific + 4494
14 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
15 com.apple.HIToolbox 0x929e66a0 RunCurrentEventLoopInMode + 283
16 com.apple.HIToolbox 0x929e64b9 ReceiveNextEventCommon + 374
17 com.apple.HIToolbox 0x929e632d BlockUntilNextEventMatchingListInMode + 106
18 com.apple.AppKit 0x93f497d9 _DPSNextEvent + 657
19 com.apple.AppKit 0x93f4908e -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
20 com.apple.AppKit 0x93f420c5 -[NSApplication run] + 795
21 com.apple.AppKit 0x93f0f30a NSApplicationMain + 574
22 com.apple.mail 0x000fa206 0x1000 + 1020422
Thread 1:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 com.apple.CoreFoundation 0x91a070de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x922bdb15 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 213
5 com.apple.Foundation 0x922c9c34 -[NSRunLoop(NSRunLoop) run] + 84
6 com.apple.MessageFramework 0x0047e0a0 -[RSSInterchange _runManager] + 2140
7 com.apple.Foundation 0x922895ad -[NSThread main] + 45
8 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
9 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
10 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 2:
0 libSystem.B.dylib 0x967ed5c6 _workqops + 10
1 libSystem.B.dylib 0x967ed5f6 start_wqthread + 30
Thread 3:
Thread 4:
0 libSystem.B.dylib 0x96783a46 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x967b5daf pthread_condwait + 1244
2 libSystem.B.dylib 0x967b7633 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x922cf4fc -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x922cf310 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.MessageFramework 0x00480154 -[InvocationQueue _drainQueue] + 317
6 com.apple.Foundation 0x922895ad -[NSThread main] + 45
7 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
8 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
9 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 5:
0 libSystem.B.dylib 0x9678abce _semwaitsignal + 10
1 libSystem.B.dylib 0x967b58cd pthreadcondwait$UNIX2003 + 73
2 com.apple.QuartzCore 0x96188121 fefragmentthread + 54
3 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
4 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 6:
0 libSystem.B.dylib 0x96783a46 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x967b5daf pthread_condwait + 1244
2 libSystem.B.dylib 0x967b7633 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x922cf4fc -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x922cf310 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.MessageFramework 0x00480154 -[InvocationQueue _drainQueue] + 317
6 com.apple.Foundation 0x922895ad -[NSThread main] + 45
7 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
8 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
9 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 7:
0 libSystem.B.dylib 0x96783a46 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x967b5daf pthread_condwait + 1244
2 libSystem.B.dylib 0x967b7633 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x922cf4fc -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x922cf310 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.MessageFramework 0x00480154 -[InvocationQueue _drainQueue] + 317
6 com.apple.Foundation 0x922895ad -[NSThread main] + 45
7 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
8 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
9 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 8:
0 libSystem.B.dylib 0x96783a46 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x967b5daf pthread_condwait + 1244
2 libSystem.B.dylib 0x967b7633 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x922cf4fc -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x922cf310 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.MessageFramework 0x00480154 -[InvocationQueue _drainQueue] + 317
6 com.apple.Foundation 0x922895ad -[NSThread main] + 45
7 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
8 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
9 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 9:
0 libSystem.B.dylib 0x96783a46 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x967b5daf pthread_condwait + 1244
2 libSystem.B.dylib 0x967b7633 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x922cf4fc -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x922cf310 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.MessageFramework 0x00480154 -[InvocationQueue _drainQueue] + 317
6 com.apple.Foundation 0x922895ad -[NSThread main] + 45
7 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
8 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
9 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 10:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 com.apple.CoreFoundation 0x91a070de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
4 com.apple.CFNetwork 0x9328b6cc CFURLCacheWorkerThread(void*) + 396
5 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
6 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 11:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 com.apple.CoreFoundation 0x91a070de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x922ecac0 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 320
5 com.apple.Foundation 0x922895ad -[NSThread main] + 45
6 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
7 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
8 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 12:
0 libSystem.B.dylib 0x96783a46 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x967b5daf pthread_condwait + 1244
2 libSystem.B.dylib 0x967b7633 pthreadcond_timedwait_relativenp + 47
3 ...apple.AddressBook.framework 0x96d96ab5 -[ABRemoteImageLoader workLoop] + 193
4 com.apple.Foundation 0x922895ad -[NSThread main] + 45
5 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
6 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
7 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 13:
0 libSystem.B.dylib 0x967d3b3a select$DARWIN_EXTSN + 10
1 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
2 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 14:
0 libSystem.B.dylib 0x96783a2e semaphorewait_signaltrap + 10
1 libSystem.B.dylib 0x9678b505 pthreadmutexlock + 569
2 libobjc.A.dylib 0x9366d688 cachefill + 65
3 libobjc.A.dylib 0x9366bba0 logand_fillcache + 141
4 libobjc.A.dylib 0x9366c576 classlookupMethodAndLoadCache + 206
5 libobjc.A.dylib 0x9367c736 objc_msgSend + 102
6 com.apple.MessageFramework 0x004e5351 -[POPAccount fetchSynchronously] + 337
7 com.apple.CoreFoundation 0x91a86b7d _invoking__ + 29
8 com.apple.CoreFoundation 0x91a86568 -[NSInvocation invoke] + 136
9 com.apple.MessageFramework 0x00480739 -[MonitoredInvocation invoke] + 409
10 com.apple.MessageFramework 0x0048031b -[InvocationQueue _drainQueue] + 772
11 com.apple.Foundation 0x922895ad -[NSThread main] + 45
12 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
13 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
14 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 15:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 com.apple.CoreFoundation 0x91a070de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
4 com.apple.MessageFramework 0x003a7a6a _handleRequestWithTimeout + 2163
5 com.apple.MessageFramework 0x003ac32d -[_NSSocket readBytes:length:error:] + 154
6 com.apple.MessageFramework 0x003abeb7 -[Connection _readBytesFromSocketIntoBuffer:amount:requireAllBytes:error:] + 89
7 com.apple.MessageFramework 0x003abd72 -[Connection _fillBuffer:] + 853
8 com.apple.MessageFramework 0x003ab938 -[Connection _readLineIntoData:error:] + 70
9 com.apple.MessageFramework 0x004b1196 -[POP3Connection(PrivateCommands) _readMultilineResponseWithMaxSize:intoMutableData:informDelegate:] + 542
10 com.apple.MessageFramework 0x004b033a -[POP3Connection _retrieveMessage:ofSize:informDelegate:] + 327
11 com.apple.MessageFramework 0x004b0428 -[POP3Connection retr:] + 174
12 com.apple.MessageFramework 0x004b0c3c -[POP3Connection fetchMessages:] + 342
13 com.apple.MessageFramework 0x004b42f3 -[POP3FetchStore fetchSynchronously] + 3406
14 com.apple.MessageFramework 0x004e5351 -[POPAccount fetchSynchronously] + 337
15 com.apple.CoreFoundation 0x91a86b7d _invoking__ + 29
16 com.apple.CoreFoundation 0x91a86568 -[NSInvocation invoke] + 136
17 com.apple.MessageFramework 0x00480739 -[MonitoredInvocation invoke] + 409
18 com.apple.MessageFramework 0x0048031b -[InvocationQueue _drainQueue] + 772
19 com.apple.Foundation 0x922895ad -[NSThread main] + 45
20 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
21 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
22 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 16:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 com.apple.CoreFoundation 0x91a070de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x922bdb15 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 213
5 com.apple.Foundation 0x922c9c34 -[NSRunLoop(NSRunLoop) run] + 84
6 com.apple.MessageFramework 0x003a4871 +[_NSSocket _runIOThread] + 98
7 com.apple.Foundation 0x922895ad -[NSThread main] + 45
8 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
9 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
10 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 17:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 com.apple.CoreFoundation 0x91a070de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x922bdb15 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 213
5 com.apple.syncservices 0x96cb1d8c -[ISyncConcreteSession _waitForTransitionFromPhase:untilDate:] + 527
6 com.apple.syncservices 0x96caff1a +[ISyncSession _sessionWithClient:entityNames:beforeDate:clientHasTruthForEntityNames:quietlyP ushTruth:target:selector:anchors:] + 1695
7 com.apple.syncservices 0x96caf872 +[ISyncSession beginSessionWithClient:entityNames:beforeDate:] + 95
8 com.apple.syncservices 0x96caf740 -[ISyncConcreteSessionDriver _beginSyncSession:] + 1251
9 com.apple.syncservices 0x96cac631 -[ISyncConcreteSessionDriver _preSync] + 95
10 com.apple.syncservices 0x96d44b2b -[ISyncConcreteSessionDriver startAsynchronousSync:] + 273
11 com.apple.Mail.Syncer 0x10f14acc 0x10f00000 + 84684
12 com.apple.Mail.Syncer 0x10f13c6d 0x10f00000 + 81005
13 com.apple.mail 0x00037fbd 0x1000 + 225213
14 com.apple.CoreFoundation 0x91a86b7d _invoking__ + 29
15 com.apple.CoreFoundation 0x91a86568 -[NSInvocation invoke] + 136
16 com.apple.MessageFramework 0x00480739 -[MonitoredInvocation invoke] + 409
17 com.apple.MessageFramework 0x004815fb +[WorkerThread _execute:] + 144
18 com.apple.Foundation 0x922895ad -[NSThread main] + 45
19 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
20 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
21 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 18:
0 libSystem.B.dylib 0x9678abce _semwaitsignal + 10
1 libSystem.B.dylib 0x9678a996 usleep$UNIX2003 + 61
2 com.apple.AppKit 0x93fafcf9 -[NSUIHeartBeat _heartBeatThread:] + 2042
3 com.apple.Foundation 0x922895ad -[NSThread main] + 45
4 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
5 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
6 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 19:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 com.apple.CoreFoundation 0x91a070de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x922bdb15 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 213
5 com.apple.syncservices 0x96cb1d8c -[ISyncConcreteSession _waitForTransitionFromPhase:untilDate:] + 527
6 com.apple.syncservices 0x96cc07c9 -[ISyncConcreteSession prepareToPullChangesForEntityNames:beforeDate:] + 99
7 com.apple.syncservices 0x96cbfc3b -[ISyncConcreteSessionDriver _pullPhaseOfSession] + 1755
8 com.apple.syncservices 0x96cac2fb -[ISyncConcreteSessionDriver _sync:] + 223
9 com.apple.syncservices 0x96d449cd -[ISyncConcreteSessionDriver _startAsynchronousSyncWorker] + 425
10 com.apple.Foundation 0x922895ad -[NSThread main] + 45
11 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
12 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
13 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 20:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 libSystem.B.dylib 0x967b8464 threadgetstate + 173
3 libobjc.A.dylib 0x9366d467 cache_collectfree + 334
4 libobjc.A.dylib 0x9366d829 cachefill + 482
5 libobjc.A.dylib 0x9366bba0 logand_fillcache + 141
6 libobjc.A.dylib 0x9366c576 classlookupMethodAndLoadCache + 206
7 libobjc.A.dylib 0x9367c736 objc_msgSend + 102
8 com.apple.Foundation 0x922d9134 -[NSUndoManager removeAllActionsWithTarget:] + 52
9 com.apple.CoreData 0x91d0bbe2 -[NSManagedObjectContext(_NSInternalNotificationHandling) _stopObservingUndoManagerNotifications] + 114
10 com.apple.CoreData 0x91d5ca24 -[NSManagedObjectContext(_NSInternalNotificationHandling) _unregisterForNotifications] + 68
11 com.apple.CoreData 0x91d5c8b5 -[NSManagedObjectContext dealloc] + 69
12 com.apple.Foundation 0x92284d9f NSPopAutoreleasePool + 431
13 com.apple.MessageFramework 0x0049d931 -[MessageRouter routeQueuedMessages] + 1081
14 com.apple.CoreFoundation 0x91a86b7d _invoking__ + 29
15 com.apple.CoreFoundation 0x91a86568 -[NSInvocation invoke] + 136
16 com.apple.MessageFramework 0x00480739 -[MonitoredInvocation invoke] + 409
17 com.apple.MessageFramework 0x004815fb +[WorkerThread _execute:] + 144
18 com.apple.Foundation 0x922895ad -[NSThread main] + 45
19 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
20 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
21 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 21:
0 libSystem.B.dylib 0x96783a46 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x967b5daf pthread_condwait + 1244
2 libSystem.B.dylib 0x967b7633 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x922cf4fc -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x922cf310 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.MessageFramework 0x00480154 -[InvocationQueue _drainQueue] + 317
6 com.apple.Foundation 0x922895ad -[NSThread main] + 45
7 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
8 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
9 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 22 Crashed:
0 ??? 0x117eec0d 0 + 293530637
1 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
2 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 22 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x967b4b28 ecx: 0xb09dee9c edx: 0x96783b06
edi: 0x00000000 esi: 0xb09df000 ebp: 0xb09def78 esp: 0xb09def40
ss: 0x0000001f efl: 0x00010282 eip: 0x117eec0d cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0x967b4b28

No one had this problem or similar that could hint a different solution that to take the machine to the shop? Does it look like hardware?
Thanks again

Safari 2.0.4 problems after sleep

I've searched a bit for problems with Safari 2.0.4 after sleep and can't find much that relates to my specific problems so I'll ask for your help. On my Powerbook G4 15" when Safari is running and it goes into sleep mode I get the following problems:
1. After heavy sleep, when I awaken the computer Safari says that the application has quit.
2. After a short time away from the computer Safari is unresponsive with a spinning beachball and a lot of disk activity. After 3-5 minutes it seems to return to normal.
Is this a known or common problem? Are there any fixes? The issue has been going on for many months, but I thought I might see if there's a cure. Resetting Safari and clearing cache don't appear to help out.
Thanks for your help.

No, everything else appears to work fine. When there is this beachball activity there's a lot of hard disk activity taking place. I have 1.5GB of RAM, but this happens when I have 2 applications open or 5. It just appears that when I leave the computer unattended for 5 minutes or so some sort off background activity is taking place.

After sleep, retina MacBook Pro (Mid 2014) does not recognize usb connected mouse movement

After sleep, retina MacBook Pro (Mid 2014, on 10.9.4) does not recognize usb connected mouse movement. I have tried a generic usb mouse and my Razer Deathadder usb mouse. Both mice work before sleep; but after sleep, the computer no longer recognizes mouse movement while still recognizing the mouse buttons when pressed. Any idea why this is occurring?

Hello, chocotac0.
Thank you for visiting Apple Support Communities.
Here are some troubleshooting steps that I would recommend when experiencing this issue.
OS X Mavericks: Reset your computer’s PRAM
http://support.apple.com/kb/ph14222
Intel-based Macs: Resetting the System Management Controller (SMC)
http://support.apple.com/kb/ht3964
OS X Mavericks: If a USB device isn’t working
http://support.apple.com/kb/PH13876
Cheers,
Jason H.

Users on network home directories hang after sleep

Hi,
I have the following problem: I have a 10.5 server with network home directories. I can login from Snow Leopard (10.6.1) however whenever the machine goes to sleep and comes back from sleep, the user hangs then if you wait a bit then it will come with the message that the share has been disconnected and it asks you to manually unmount. It will stay there forever. When you click disconnect, the system will unmount and remount the home directory but in the mean time, Mail will have reported disk i/o errors in the logs and throw errors (ranging from type in your password to 'rebuild index').
Going through the log files (and verbosity high) it seems that when going to sleep, the system doesn't unmount the network home directory. After it wakes up from sleep it attempts to unmount the home directory share which off course fails because it's in use and then it locks up, after you click disconnect, it says "spins reported" in the logs and goes on with remounting the shares.
The issue doesn't happen if the user is local. If anybody has an idea as to how this works or if they have it working, please let me know. I have tried just about anything. AFP shares, NFS shares, I have tried with or without the intr, nolocks, locallocks mount options - they all have the same issue. I have even tried another Mac Mini with a fresh install of Snow Leopard.

I found a possible cause and solution.
This has been on 10.6.1 with Mac Mini's. Then we got a new Mac Pro with 10.6 out of the (Apple) factory which I updated to 10.6.1, same issue. What I didn't think about is that by default I install a heap of software (including XCode, Adobe CS4 and Office 2008) with customized packages and workgroup manager preferences.
So I was mucking around with Cocktail (the tool to clean up caches etc.) and I noticed Snow Leopard hung every time after cleaning & recreating some caches. Now that I had a reliable way to hang Snow Leopard I investigated what could cause it.
I noticed during a PackageMaker session that Adobe CS4 installs a Version Cue startup script in /etc/machinit_peruser.d. I deleted it, rebooted, used Cocktail again and it went all the way through without hanging. Rebooted again, according to the logs it pre-linked & cached the kernel and several kernel extensions and that was it, no more hangs, no more issues logging in after sleep or screensaver.
So possible causes:
- VersionCue installs itself as a kernel module or something (the location says "mach" which is the kernel after all) which is not compatible with Snow Leopard.
- The caches and kernel extensions were 'dirty' out of the box but VersionCue (or something else that interacts with it) blocked my or Snow Leopard's automated attempts to clean them.
- VersionCue reinitializes (it sits on the network after all) after a sleep or screen saver timeout in a way that gives issues with Snow Leopard

Recovered files in trash after sleeping

Upgraded to Tiger 10.4.11 from Panther about 4 weeks ago using Erase & Install, then restoring apps, files, etc. with Migration Assistant from a clone. Flawless & painless--whew! However, I'm now having one minor but annoying issue--after playing Burning Monkey Solitaire, quitting, logging out & putting Mac to sleep, find recovered files in trash on next log in, specifically a couple of BMS text files. The Freeverse support folks are still working with me on this issue (suggesting doing a Secure Empty Trash, which didn't prevent the files from returning). I'm posting here, however, because today there was also an iPhoto folder (empty) in the Recovered files folder in the Trash. Any ideas on why this may be happening and how to stop it? I've used iPhoto since the OS upgrade without this occurring and, so far at least, no other apps (Word, Excel, other games, etc.) have been leaving orphan files on quit/sleep/logout that wind up recovered in the trash.
As I said, it's a minor annoyance, but hope it's not a symptom of something more serious. Thanks!

Thanks, but that's not quite what's happening here . . . first, neither Burning Monkey nor iPhoto unexpectedly quit--always were quit normally. Second, recovered files folder shows up after sleeping, not just after restarting.

After sleeping my macbook pro 15.4" mid 2012 model for overnight and pass 24 hours time, on wake -- the dock background is white for a few seconds and then it turns back to normal color. . .

After sleeping MacBook Pro 15.4" mid 2012 model (running Mac OS X 10.10.2 Yosemite) for overnight and pass 24 hours time, upon wake from sleep-- the dock background is white for a few seconds and then it turns back to the normal color.
Is this normal? Should I be worried? Is my GPU defective?
My specs:
MacBook Pro 15.4" Mid 2012 model, Ivy Bridge Quad core i7 2.3Ghz CPU w/ hyperthreading,
16GB RAM, Nvidia 650M 512MB VRAM/Intel 4000 HD 1GB VRAM, 500GB HD
Running Mac OSX 10.10.2 Yosemite.
Thanks to all in advanced.

It doesn't happen all the time but sometimes and i tried zapping the PRAM and it still happens!

Yosemite upgrade: function keys no longer work, no keyboard lights and have to sign in twice after sleep mode. Anybody else having these problems?

Hi,
Since I did the Yosemite 'upgrade' last week I have been having problems with my MacBook Pro that never happened before. The most frustrating problems involve my keyboard which doesn't light up (checked my settings and they are correct) and the top row of function keys don't do anything so I can't adjust the volume, brightness, etc. Then if my screen goes into sleep mode, when I wake it back up I have to sign back in twice - I never had to sign in at all after sleep mode before.
I'm finding that in order to get it working properly I am having to completely shut down and start up again but when the keyboard problems are happening I can't get anything on the apple dropdown to work either (i.e. shut down, restart, etc) so I can only shut down by pressing and holding the on/off button.
I've never had problems with my Macbook before and feel like Apple have completely ruined it in one update! I've had a look through other posts on here but can't find anybody else having these problems so I would be really grateful if anyone could help me and offer me some advice on how to sort it out.
Thanks!

Reset PRAM. http://support.apple.com/kb/PH18761
Reset SMC. http://support.apple.com/kb/HT3964
Choose the method for:
"Resetting SMC on portables with a battery you should not remove on your own".
Best.

Hello. My mac pro early 2008 restarts after sleep mode and it works slower. I tested it with apple hardwear test and it seems to be ok. Thank you.

Hello. My mac pro early 2008 restarts after sleep mode and it works slower. I tested it with apple hardwear test and it seems to be ok. Thank you.

Try this:
clone your system and repair it with Disk Warrior instead
Or try a clean test system install on another drive
A must: SmcFanControl 2.2 - a mere 400 rpm extra to keep air cooling up
Try to run w/o externals. MyBook included.
Is that a 7200.11 1TB? they had a lot of issues.
Run AHT off your OEM DVD.
2008 had to have EFI and SMC updates to deal with freezes on wake from sleep, and like all models, high inrush current. Hopefully you have a UPS and is 1500VA unit.
When you do hard restart from power button, you almost certainly add more directory errors and to files requiring immediate attention to repair and rebuild the directory; and to scan and repair and delete cache and temp files and folders. A must. Invest in bootable backups SuperDuper along with Disk Warrior (or TechTool Pro 6, maybe Drive Genius 3 but I'd rate that #3).
TimeMachine has its own bad habits, especially with Green drives and some externals.
Try to rule out everything and then add back one at a time.
And it may just be time to replace the 8800, very common, a couple threads this week, and it is 3 yrs old. Might want ATI 5870 or 5770.

Screen does not turn on after sleep - ProBook 4530s - Windows 8.1 (64bit)

Hi everyone,
Not sure if this had to be posted in notebook display and video section, or laptop lockups, freezes and hangs. Anyway, I have a problem, where everything is fine with the computer, it's running smoothly, but whenever I make it go to sleep, after it does it instantly, the signals are of a regular laptop sleep - power buton flashing, no other signs of computer being on.
However, the problem appears when turning the computer back on after sleep. After pressing the power button, the computer straight away starts working - you can hear the fan turned on, etc, just that pretty much nothing changes with the screen. Sometimes, with some particular light directed towards the screen, you can even see, that the computer is on (seeing the clock on the display), just like the brightness was set down to 2% or something. And there is nothing that helps from what I have tried to do (tried reinstalling both AMD drivers and Intel HD drivers). I researched this problem extensively but could not find a solution, however, as I have noticed that this is quite an old problem (assuming from the date of the posts this problem first showed up), there might be a solution for it, to which I just have not noticed the answer?
If anyone can help me, please do, the sleep function is essential and extra important function when living on campus at university, I just cannot operate like this.
Hopefully someone will know, thank you in advance.
Dinas

Hi @dindanas,
Your ProBook 4530s is a commercial product and to get your issue more exposure I would suggest posting in the commercial forums. Here is a link to the Commercial Notebook forum.
Please click “Accept as Solution ” if you feel my post solved your issue.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Thank you,
BHK6
I work on behalf of HP

Mac Keeps Crashing after sleep

I have a brand new iMac.
It works perfectly, except that it crashes after waking it from sleep. Not always, but frequently enough to be quite annoying. I initially thought this was due to network hardware I had installed for a network storage drive, but I have since uninstalled it, and it did not fix the problem.
I will wake if from sleep, it will work for about 30 seconds, then the screen will turn pink (or white, or gray) and it will freeze. Sometimes this will happen when I have pressed no keys. Sometimes this will happen when I go to start a program.
I called the support line, and they had me do a hardware reset (holding Command, Option, P, R while starting.) But this did not fix the problem.
If I set my computer never to sleep, I have no problems.
I am trying to avoid bringing my iMac back to the Apple store. I read a post once where a person said this occurred because of a wireless router problem. Has anyone heard of this as a cause? I am using a Lynksys, but was thinking of getting Apple's Time Capsule anyway, and will do so now if this would fix the problem. Does anyone know if this might fix the problem?
If it is any help, this is the error message I always get in Console Messages:
12/19/10 11:05:10 AM apsd-ft[146] <APSCourier: 0x100609db0>: Stream error occurred for <APSTCPStream: 0x102f02bf0>: Error Domain=NSPOSIXErrorDomain Code=57 UserInfo=0x102f01480 "The operation couldn’t be completed. Socket is not connected"
12/19/10 11:05:10 AM apsd-ft[146] <APSCourier: 0x100609db0>: Stream error occurred for <APSTCPStream: 0x102f02bf0>: Error Domain=kCFErrorDomainCFNetwork Code=2 UserInfo=0x102e29c10 "The operation couldn’t be completed. (kCFErrorDomainCFNetwork error 2.)"
Any advise appreciated, thanks.
-Lee

I could not find any kernal panics in the console list, but I did figure out the problem.
Apparently, network storage devices can be problematic if the iMac sleeps, and they do not support sleep. I have since purchased a Time Capsule as my router, and now have my network storage device plugged into this. Actually, my router could have been the problem also, as it does also serve as network storage.
For anyone who reads this who has problems with the iMac crashing after sleep, consider what network storage devices might be connected.
-Lee

No SSL after sleep

Similar Messages

Maybe you are looking for