Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

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

chacha22 Author

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

Oct 11, 2009 11:22 AM in response to macnoel

I did that myself and it helped to cut the blue-screens down to two per day. (That's JUST from Eudora!)

... I removed all of the Office fonts. I believe the Office fonts are also TrueType but use Microsoft extensions.

macnoel

Level 4

2,624 points

Oct 11, 2009 12:25 PM in response to Davert

Davert,

I'm glad to see you got at least some relief from this problem. As for font file types, I probably should have stuck with standard nomenclature: Indeed, the MS and OS X fonts have different file extensions. Which is the "operative" difference. Sorry if I misspoke.

Regards,
Macnoel

Oct 12, 2009 3:21 PM in response to chacha22

Hi, just to say this is happening to me also. It has only happened when I have been using Office 2004 and therefore Rosetta. It seems to happen following using of the return key but as others report, is not reproducible. All accounts get logged out - no favouritism!.

Oct 13, 2009 1:50 AM in response to chacha22

Same symptoms here as well, also while running Photoshop CS2 under Rosetta.

Oct 13, 2009 10:34 AM in response to chacha22

What's a HAL plug-in and where is it?

Oct 14, 2009 5:21 PM in response to Guy Rhodes

Same here. Sudden account logout happens to me when running Excel 2004. I hate it when that happens ...

Oct 15, 2009 4:25 AM in response to cvilledave

Ok. Me too. I'm glad to find this thread and at least get some vague idea of what's happening. And to know that it's not a hardware issue.

I was working on Excel 2004 last night for a couple of hours and crashed 3 times (blue screen, then log-out). I feel like I'm back in the days of OS 9. Or Windows whatever. Basically it *****.

It sure would be helpful if someone from Apple were here on this thread to let us know that either this glitch would be fixed or that it isn't and we just need to upgrade Office. I suppose there's Open Office in the meantime.

Davert

Level 1

12 points

Oct 15, 2009 5:39 AM in response to Davdgtown

If Office is the only Rosetta program you use, then by all means, replace it!! If I COULD replace Eudora, I would!

rrnowell

Level 1

4 points

Oct 15, 2009 6:07 AM in response to chacha22

The blue screen logout/crash has happened regularly during my use of MS Office 2004. Fortunately I have multiple partitions and maintain a copy of 10.5.8 so I can reboot to it and run safely there.

However, Apple has faltered on Snow Leopard in that they should have caught and fixed this BEFORE they released SN. They had to know a large number of their users are using MSO 2004. They have increased sales for MSO 2008 and damaged their reputation as well as reduced sales of iWork by this faux pax.

Furthermore, it raises many questions about support. There is never any indication that a report of the event is sent to Apple for analysis. As users we are left to forums to try to find work arounds... that is not quality support. They seem 'slow' in acknowledging problems and in addressing them.

This also raises questions as to the "crash" protection built into the OS. OS 9 was a cooperative multi-tasking system and application crashes affected other apps as well as the OS. The move to Unix was supposed to end these events because it is a pre-emptive multi-tasking OS. How effective is the isolation of the application from the OS if the application spawn an even that logs the user out (affects ALL the users activities). Whatever you call it the effect upon the user is to place them back in an environment where they experience the same annoyances or should I say 'crashes" that cooperative multi-tasking was notorious for. The user is NOT protected from a single app disrupting the use of their system.

Questions: Was Snow Leopard rushed out the door to "beat" MS W7? Does Apple even checkout the appls their users use? Do they check them out adequately?

Solutions:

1) Fix SN and get rid of this problem ASAP. Additionally put in place policies that prevent a re-occurrance.
2) Now that the damage is done how can they regain what they have lost. This is a difficult problem. I, who have been using Mac for 13+ years, have lost confidence in the OS. I do not align myself with companies. I am a user and want a product that works. Whereas before I was happy with my OS, now I am questioning it and the corporate policies that allowed these problems to reach end users.

I suppose they could offer iWork competitive upgrades to MSO 2004 users or even give it away to them... but I don't think this would be helpful as I have yet to encounter a user intervention free change of Word processors or spreadsheets. I have considered converting to iWork, but I can't imagine the work involved in modifying all my legacy MSO 2004 documents to print correctly under iWork. This could involve hundreds of man hours. Still this would move MS customers to Apple unless iWork faltered in the translation and printing of the MS documents. Even if this was an option it is not the best. The best is to insure the user has a truly protected application environment where one bad appl cannot affect the whole barrel (I couldn't resist the metaphor).

Bottom line is the "blue screen" calls into question the assertion that Snow Leopard is the most advanced OS in the world at a time when many challenges to a supreme OS are raising their heads.

One problem (providing it is resolved) will not sink an OS, but this one is beginning to hurt the Apple OS's reputation.

Hopefully they will quash it with the 10.6.2 update and will be able to assure users that they indeed have them once again protected for rogue applications. Even, so the thousands of lost man hours on this "bug" are the obvious result of a need for increased diligence in the vetting of their OS BEFORE it is released.

Davert

Level 1

12 points

Oct 15, 2009 6:11 AM in response to rrnowell

{quote:title=rrnowell wrote:} There is never any indication that a report of the event is sent to Apple for analysis. As users we are left to forums to try to find work arounds... that is not quality support. They seem 'slow' in acknowledging problems and in addressing them.{quote}

The contact that we do get is informal, and it would be great to have some clue as to where the problem is, what action they are taking, timeframes, etc.

{quote}This also raises questions as to the "crash" protection built into the OS. OS 9 was a cooperative multi-tasking system and application crashes affected other apps as well as the OS.{quote}

To be fair, Rosetta is not a typical program, and that's what's crashing or causing the crash.

{quote}Was Snow Leopard rushed out the door to "beat" MS W7? Does Apple even checkout the appls their users use? Do they check them out adequately?{quote}

I think the answers are obvious.

In my opinion, what they could to now to recover is TELL US WHAT'S GOING ON and if they know ANYTHING about the causes, TELL US so we can try to avoid the crash situations. It's all anecdotal now.

Replacing Office 2004 would be great but pointless for ME, because for me it's Eudora. Lots of people are running other special apps that are not easy to replace. Really, the only fix is a fix - but in the meantime, some words of wisdom would be good.

rrnowell

Level 1

4 points

Oct 15, 2009 6:32 AM in response to Davert

We agree except I think Rosetta is no excuse. Rosetta should also run as a appl and be isolated. From a user's perspective the applications they run should not be able to affect their interaction with other appls or their basic user interface. Whether it is called a crash or an event or a reset or whatever... the user's session should not be reset by the failure of an appl. Only that appl should be affected and not the user's session. It isn't about fairness to Apple or to MS or Linux or Unix... it is about the user's experience. I suppose it is possible that Apple didn't know about this problem before releasing SN, but that in itself is a problem. If they did know, they did not warn the MSO 2004 users, which raises even greater concerns. Don't get me wrong. I purchased the SN upgrade as soon as it was available because I want it to succeed. I believe the move to 64 processing is important, even so, protecting users is fundamental and I as a user consider fairness to the user before I consider allegiance to or fairness to the vendor. Perhaps with all of the endeavors/efforts (iPhone, iTunes, new hardware, etc.) Apple let this principle be compromised.. once... hopefully is it not a harbinger of things to come. I prefer to think not... but as a user I will be more cautious next time and more open to alternatives than I was before as a more fully satisfied customer. After all it is about meeting the customer's needs from the customer's perspective and not about the corporate entities whether they be MS or Apple and neither is it about the OS whether it be Windoze or X or Unix or Linux or Chrome or whatever. Whatever OS and whatever company best serves the needs of the customers... let it win and if it should falter in serving them best and not turn around let another which better serves the customer win.

Oct 15, 2009 7:21 AM in response to rrnowell

I've had a few problems with Microsoft Office 2004, but my big problem is Photoshop CS2. Does anyone know if that uses Rosetta. I haven't upgraded to CS4, but I will if that solves the problem for me.

I've been booting from my backup HD which still has 10.5.8. (Thankfully, I haven't backed up.)

Thanks.

Rich Green

macnoel

Level 4

2,624 points

Oct 15, 2009 11:43 PM in response to Richard Green2

Hello Richard,
My solution to the Photoshop question, if you're interested, is to stick with 10.5.8. If PS CS2 is running well for you under 10.5 - then stick with it. I've got CS3 Extended and don't intend to throw money at Adobe for an upgrade to that. Photoshop runs blazing fast on my Mac Pro with 10.5. So if that's the heaviest app you've got running, then you'll probably gain little from moving to 10.6.

Lets remember: Apple has said that they introduced 10.6 with 64-bit computing and Open CL (for recruiting graphics card capacity) "to be ready for future developments." That's the same as saying they introduced it "for the future," period. There are few apps today written to run with 64-bit. Open CL works only with the latest (or upgrade) graphics cards. Which means that the majority of Mac users will only gain from the leaner Snow Leopard's "native" speed boost. That's one out of three possible sources of performance enhancement. The question to ask yourself : Is coping with Snow Leopard worth that single gain - especially if key applications won't run with it "as is."

The same applies with regard to Office 2004: most people use it because it does all they need or they would have upgraded to '08 already. We should keep in mind: Apple doesn't demand that we all go to Snow Leopard right now. And it's fair to guess there won't be many apps which are 64-bit capable until next year.

Finally, I notice this thread on sudden log-outs has been active for some time. That's w/o an answer to the problem from either expert advisors on Apple Discussions or from Apple themselves. Doesn' this tell us something? It's becoming more apparent with every passing day that this issue won't be solved right away. That too argues for backing off 10.6, at least temporarily.

That's just my 2¢, others may want to hang on.

Oct 16, 2009 4:07 AM in response to macnoel

MacNoel,

Thank you very much for your response. I was thinking the same thing - that I should have stuck with 10.5.8. The question is, how do I backtrack now? I have 10.6 on my main HD and I have a backup HD - I use SuperDuper for cloning/backup - but if I simply reverse the clone, I'll erase all my new stuff. I waited on backing up in case I had a problem and I'm sure glad that I did. However, how do I take a step backward?

Rich Green

Davert

Level 1

12 points

Oct 16, 2009 5:54 AM in response to Richard Green2

PErsonally, I'm just waiting for new stuff. When the crash happens, I clear the font cache and reboot. That spaces it out to once or twice a day under heavy usage. Only happened once on the laptop so far.

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