Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

0 points

Sudden Log-out in Snow Leopard (+ Blue Screen)

Similar posts here show that other people are being spontaneously logged out of 10.6, faced with a blue screen, and then the login window. In my case it is caused by connecting my bluetooth (BT) headphones, as the log below states.

Short of never using my BT headphones or any other peripherals, has anyone found a solution to this terrible bug? Comments like "[Many applications shut down here]" are added to show that the log is just repeating with different applications.

[Console Log Excerpt]
9/4/09 6:11:35 AM BluetoothAudioAgent[2390] Error loading /Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio: dlopen(/Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHD Audio, 262): no suitable image found. Did find:
/Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio: no matching architecture in universal wrapper
9/4/09 6:11:35 AM BluetoothAudioAgent[2390] Cannot find function pointer NewPlugIn for factory C5A4CE5B-0BB8-11D8-9D75-0003939615B6 in CFBundle/CFPlugIn 0x100130990 </Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin> (bundle, not loaded)
9/4/09 6:11:44 AM GrowlHelperApp[5408] CGSShutdownServerConnections: Detaching application from window server
9/4/09 6:11:44 AM Library Books[5402] CGSShutdownServerConnections: .
Detaching application from window server
.
.
[Many applications shut down here]
.
.
Dock[5365] MIG: server died: CGSReleaseShmem : Cannot release shared memory
9/4/09 6:11:44 AM Dock[5365] CGSDisplayServerShutdown: Detaching display subsystem from window server
9/4/09 6:11:44 AM DashboardClient[7864] MIG: server died: CGSReleaseShmem : Cannot release shared memory
.
.
[Message Repeated with other applications]
.
.
DashboardClient[7869] kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
.
.
[Message Repeated with other applications]
.
.
9/4/09 6:11:44 AM com.apple.Dock.agent[5365] Fri Sep 4 06:11:44 [MYNAME]-MacBook-Pro-2.local DashboardClient[7865] <Warning>: CGSDisplayServerShutdown: Detaching display subsystem from window server
.
.
[Many applications shut down here]
.
.

9/4/09 6:11:45 AM Dock[5365] kCGErrorInvalidConnection: CGSSetBackgroundEventMaskAndShape: Invalid connection
.
.
[Many applications shut down here]
.
.
9/4/09 6:11:47 AM com.apple.ReportCrash.Root[2398] 2009-09-04 06:11:47.468 ReportCrash[2398:1407] Saved crash report for loginwindow[5344] version ??? (???) to /Library/Logs/DiagnosticReports/loginwindow 2009-09-04-061147localhost.crash
9/4/09 6:11:49 AM com.apple.SecurityServer[25] Session 0x34b085 created
9/4/09 6:11:49 AM com.apple.SecurityServer[25] Session 0x34b085 attributes 0x30
9/4/09 6:11:51 AM loginwindow[2406] Login Window Started Security Agent
9/4/09 6:11:52 AM WindowServer[2408] kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
9/4/09 6:11:52 AM com.apple.WindowServer[2408] Fri Sep 4 06:11:52 [MYNAME]-MacBook-Pro-2.local WindowServer[2408] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
9/4/09 6:11:55 AM com.apple.SecurityServer[25] Session 0x234edb dead
9/4/09 6:11:55 AM com.apple.SecurityServer[25] Killing auth hosts
9/4/09 6:11:55 AM com.apple.SecurityServer[25] Session 0x234edb destroyed
9/4/09 6:11:56 AM com.apple.ReportCrash.Root[2398] 2009-09-04 06:11:56.175 ReportCrash[2398:2b03] Saved crash report for DashboardClient[7867] version ??? (???) to /Library/Logs/DiagnosticReports/DashboardClient 2009-09-04-061156localhost.crash
9/4/09 6:11:56 AM SecurityAgent[2414] Showing Login Window
9/4/09 6:11:57 AM com.apple.notifyd[11] EV_DELETE failed for file watcher 295
9/4/09 6:11:57 AM com.apple.notifyd[11] EV_DELETE failed for file watcher 292
.
.
[Message Repeated]
.
.
9/4/09 6:11:58 AM com.apple.loginwindow[2406] 2009-09-04 06:11:58.519 loginwindow[2406:107] Error loading /Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio: dlopen(/Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHD Audio, 262): no suitable image found. Did find:
9/4/09 6:11:58 AM com.apple.loginwindow[2406] /Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio: no matching architecture in universal wrapper
9/4/09 6:11:58 AM com.apple.loginwindow[2406] 2009-09-04 06:11:58.521 loginwindow[2406:107] Cannot find function pointer NewPlugIn for factory C5A4CE5B-0BB8-11D8-9D75-0003939615B6 in CFBundle/CFPlugIn 0x100151fc0 </Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin> (bundle, not loaded)
9/4/09 6:11:59 AM SecurityAgent[2414] User info context values set for [MYNAME]
9/4/09 6:11:59 AM authorizationhost[2413] Failed to authenticate user <[MYNAME]> (tDirStatus: -14090).
9/4/09 6:12:03 AM SecurityAgent[2414] User info context values set for [MYNAME]
9/4/09 6:12:03 AM SecurityAgent[2414] Login Window Showing Progress
.
.
[Login window showed up]
.
.
[End Console Log Excerpt]

Message was edited by: chacha22

MBP Late 08, Mac OS X (10.6), upgraded from leopard, spontaneous, logout, sudden, blue screen

Posted on Sep 4, 2009 3:34 AM

94 replies

Davert

Level 1

12 points

Sep 21, 2009 7:10 AM in response to Vail Ski Bum

FWIW, while it ALWAYS happens for me during Rosetta usage, I have neither dual displays nor Bluetooth. (2006 Mac Pro though.)

I mentioned in the other thread some things that reduced frequency dramatically: updated Samsung drivers. Updated Canon scanner drivers (!!). Deleted duplicate fonts from Microsoft font folder. Ran FontDoctor and got rid of other fonts.

Didn't help but probably was a good idea: went through all startup folders and such and used Lingon and Diablotin to remove old rubbish like retro.run, various backup and synch stuff long unused, etc.

I'd be very interested to hear if anyone has any ideas on other things that could help.

I am still getting this error in Console which might be an issue:

9/21/09 8:41:00 AM Eudora[230] * __NSAutoreleaseNoPool(): Object 0x2335e170 of class NSCFArray autoreleased with no pool in place - just leaking

I've finally moved from Office 2004 to 2008 (I bought it pre-release, Home and Student version -- three licenses for what worked out to $30 as I recall) and that helps. But I rely on Eudora until MailForge gets there - which the writer claims will be on Tuesday 😉 (I love the idea of MailForge, and I applaud Matt Milano for keeping at it, but I'm guessing I'll be using Eudora into 2010. I do intend to switch to MailForge AS SOON AS I CAN.)

PS> The last crash to actually knock out the system was:

Thread 2 Crashed:
0 libobjc.A.dylib 0x00007fff8697e340 objc_msgSend + 44
1 com.apple.CoreFoundation 0x00007fff863e057a CFNumberCompare + 90
2 com.apple.print.notification 0x000000010038403d 0x100383000 + 4157
3 com.apple.CoreFoundation 0x00007fff863d6a78 __CFRunLoopRun + 5480
4 com.apple.CoreFoundation 0x00007fff863d503f CFRunLoopRunSpecific + 575
5 com.apple.CoreFoundation 0x00007fff863d4dc6 CFRunLoopRun + 70
6 configd 0x0000000100003c5b plugin_exec + 1440
7 libSystem.B.dylib 0x00007fff860aaf66 pthreadstart + 331
8 libSystem.B.dylib 0x00007fff860aae19 thread_start + 13

Message was edited by: Davert

chacha22 Author

Level 1

0 points

Sep 22, 2009 5:29 AM in response to chacha22

[I'm the thread OP, and in my second post I said that the sudden logouts had ceased]

Unfortunately, it happened again (yes, when I was connecting a BT device) even though I moved the HAL plugin. The console output gives me no indication of the cause.

gunner 1

Level 1

5 points

Sep 25, 2009 7:16 AM in response to chacha22

I too have experienced this problem but for me it seems to occur most often when my screen saver is activated (which I do when I leave the office to lock my macbook pro). When I get back I noticed that the computer logged me out and went back to the login screen.

I initially thought it was related to the energy settings or the screen saver but this morning I noticed the same thing happen when I tried to log back in. I have an iPod touch connected so it tried to open iTunes on login. After a second or two the screen went blue and it logged me out. I re-logged in and have been using it now for about 30 min. without a logout.

I am not using Rosetta for iTunes and that was the only app open at the time. At this point it has not occured while I was working on a doc.

Davert

Level 1

12 points

Sep 25, 2009 7:19 AM in response to gunner 1

FWIW, I filed an official bug report. Not a bad idea.

gunner, did you check Console to make sure it IS the same crash and not a different one?

Sep 26, 2009 11:40 PM in response to chacha22

This has happened to me a few times at least. Until I saw this and similar posts I never put it together. Now it makes since. Hopefully this won't increase in frequency before it's fixed.

gbs

bob4gets

Level 1

0 points

Sep 29, 2009 2:33 PM in response to chacha22

I hope I have solved the problem. See MacFixit:

http://reviews.cnet.com/8301-13727_7-10361888-263.html?tag=mncol;title

I re-installed 10.6 over my existing 10.6.1 system from the install DVD. This time I checked the Rosetta box in the custom install options. My original install did not have this option checked and Rosetta installed/launched the first time I opened a Rosetta app. Then I upgraded the 10.6.1 and so far haven't had a random logout for the last 4 days. I'm keeping my fingers crossed but so far so good. What a relief!

emillio

Level 1

0 points

Oct 4, 2009 5:17 PM in response to bob4gets

Just for the record, I've been working in Excel 2004 for several hours this afternoon, and have gotten the blue screen not less than 6 times. I'm having lots of other funky problems since I installed SL that I won't go into on this thread. I read in another thread that installing 10.6 over 10.6.1 is not a good idea, and neither is trying to revert to Leopard. This sure is a disappointing "upgrade" -- unlike Apple.

macnoel

Level 4

2,624 points

Oct 4, 2009 7:47 PM in response to jaystrom

Yes it is "Windowsy" - not by coincidence, a large number of these sudden logout incidents are related to a 5 year-old version of MS Office.

I know that many are "forced" to use MS Office. So don't take my comment personally - it's clear there are a lot of smart, savvy posts on this thread.

The two most common fixes I've seen so far are:
1. Check fonts with Font Book (it's in Utilities Folder) - delete found duplicates, turn off questionable fonts, trash font flagged as defective.

2. Revert to Leopard - because it seems to be the last version of "X" capable of reliably running MS Office 2004 edition.

Davert

Level 1

12 points

Oct 5, 2009 6:14 AM in response to macnoel

Let's be fair, it's affecting Office 2004 users mainly because there are so many of them. I went to Office 2008 and now it only affects me in Eudora. Someone else here had to use a science program in Rosetta and had the same result. Fixing font issues sure helps reduce the incidence but it doesn't eliminate blue screens.

macnoel

Level 4

2,624 points

Oct 5, 2009 10:49 AM in response to Davert

Yep, fairness and a sympathetic attitude is in order here.

I also have friends who are "stuck" with either MS Office (older versions) or are "stuck" with Windows PCS (according to them) because their scientific or literary work demands it.

Overall, I have nothing against Snow Leopard and made sure to be prepared. Bought the 10.6 install disk too. But I backed off and remained at 10.5.8 because I have one old (mission critical) image editor that won't work at all with Snow Leopard. When I find a suitable substitute (testing some now), I'll certainly want to upgrade to Snow Leopard.

I also understand that it sometimes takes spending additional money which some people just can't afford to do "at the moment." So while upgrading MS Office is the preferred and simplest answer, I think these people can wait a bit and temporarily back off from Snow Leopard. In the above example, I got a great deal on that old image editor but it looks like I'll have to spend 5X for a suitable replacement.

Davert

Level 1

12 points

Oct 5, 2009 10:56 AM in response to macnoel

Sticking with 10.58 is the best bet. I should have waited a month to upgrade but I didn't. The initial reports were very positive...

I will say that the Home and Student deals on Office 2008 are very attractive. Office 2008 itself is not. If I could, I'd stick with X or 2004 indefinitely. But then, if I could, I'd still use 5.1a.

Here's hoping Apple figures it out.

lisaski4

Level 1

0 points

Oct 9, 2009 10:58 PM in response to Davert

I received the blue screen as well while using Photoshop Elements 3. I did install Snow Leopard when it was released onto my 6-month old iMac. I was concerned it was hardware problem when I found this thread.

A few nights ago my computer shut down on it's own while the screensaver was going as well.

Oct 10, 2009 6:50 PM in response to chacha22

I'm having the same problem running Photoshop CS2 with Rosetta. Haven't looked at any of the mentioned fixes yet, but it has happened three or four times over the past week.

loeribas

Level 1

18 points

Oct 11, 2009 3:26 AM in response to jaystrom

The same thing here. Until now it only happens when working in Office...

macnoel

Level 4

2,624 points

Oct 11, 2009 10:45 AM in response to loeribas

Hello loeribas,
You don't say so I am just asking: have you tried this?--

Check fonts with Font Book (it's in Utilities Folder) - delete found duplicates, turn off questionable fonts, trash font flagged as defective.

I should add that MS Office fonts are a different kind of font file from those used in OS X. The OS X fonts are True Type. You can tell the difference between the two by looking at the file extensions. It may be that 10.6 doesn't work well with the MS fonts at all. But that may not be the case. So I would suggest only that people who use Office and are experiencing this automatic logout try sorting through the Office fonts as suggested. It HAS worked for some Mac users.

Message was edited by: macnoel

Sudden Log-out in Snow Leopard (+ Blue Screen)