Spontaneous logout while in Snow Leopard

This happened to me too, i think i made a typing on the keyboard and dragging the mouse at the same time,don't remember what letters, hmm, that caused this logout!

Had the same problem, twice. Logs out all logged in accounts, goes back to login screen.

I did an upgrade of Leopard, installed Rosetta at that time.

This is what I got last time:

xxx java[23131] <Error>: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store
Oct 13 09:56:56: --- last message repeated 6 times ---
Oct 13 09:56:52 xxx java[23131]: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store
Oct 13 09:56:56: --- last message repeated 8 times ---
Oct 13 09:56:52 xxx [0x0-0x3c63c6].org.netbeans.ide[22892]: Tue Oct 13 09:56:52 xxx java[23131] <Error>: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store
Oct 13 09:56:56: --- last message repeated 15 times ---
[ more of the same ]
Oct 13 09:56:56: --- last message repeated 107 times ---
Oct 13 09:56:54 xxx login[24175]: DEAD_PROCESS: 24175 ttys004
Oct 13 09:56:54 xxx /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[26930]: Login Window Application Started
Oct 13 09:56:54 xxx login[24196]: DEAD_PROCESS: 24196 ttys005
Oct 13 09:56:55 xxx java[23131]: HIToolbox: received notification of WindowServer event port death.
Oct 13 09:56:55 xxx java[23131]: port matched the WindowServer port created in BindCGSToRunLoop
Oct 13 09:56:55 xxx java[23131]: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store
Oct 13 09:56:56: --- last message repeated 100 times ---
Oct 13 09:56:56 xxx login[24147]: DEAD_PROCESS: 24147 ttys003
Oct 13 09:56:56 xxx login[263]: DEAD_PROCESS: 263 ttys000
Oct 13 09:56:57 xxx login[22772]: DEAD_PROCESS: 22772 ttys001
Oct 13 09:56:57 xxx com.apple.ReportCrash.Root[26927]: 2009-10-13 09:56:57.726 ReportCrash[26927:2903] Saved crash report for WindowServer[62] version ??? (???) to /Library/Logs/DiagnosticReports/WindowServer 2009-10-13-095657localhost.crash
Oct 13 09:56:58 xxx java[23131]: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store
Oct 13 09:56:59: --- last message repeated 100 times ---
Oct 13 09:56:59 xxx SecurityAgent[26870]: __CFServiceControllerBeginPBSLoadForLocalizations received error 268435459 from bootstrap lookup2
Oct 13 09:56:59 xxx SecurityAgent[26820]: __CFServiceControllerBeginPBSLoadForLocalizations received error 268435459 from bootstrap lookup2
Oct 13 09:56:59 xxx java[23131]: __CFServiceControllerBeginPBSLoadForLocalizations received error 268435459 from bootstrap lookup2
Oct 13 09:57:02 xxx loginwindow[26930]: Login Window Started Security Agent
Oct 13 09:57:02 xxx WindowServer[26931]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Oct 13 09:57:02 xxx com.apple.WindowServer[26931]: Tue Oct 13 09:57:02 xxx WindowServer[26931] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Oct 13 09:57:10 xxx hdiejectd[26556]: quitCheck: calling exit(0)
Oct 13 09:57:10 xxx SecurityAgent[26938]: NSSecureTextFieldCell detected a field editor ((null)) that is not a NSTextView subclass designed to work with the cell. Ignoring...
Oct 13 09:57:10 xxx loginwindow[26930]: Login Window - Returned from Security Agent
Oct 13 09:57:11 xxx loginwindow[26930]: USER_PROCESS: 26930 console
Oct 13 09:57:11 xxx com.apple.launchd.peruser.25181[488] (com.apple.ReportCrash): Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self

Couple of interesting things here:

- something froze for so long that time appears to go backwards in the logs
- could not find com.apple.ReportCrash.Self (so Apple isn't getting reports of this?)
-

Message was edited by: mnot

So does anyone have any indication whether Apple will be releasing any sort of update or fix soon? I'm pretty close to needing to either upgrade all my PPC apps, or revert to Leopard. Any thoughts? Thx.

I am having the same issue on a macbook unibody with Flash 8 pro. No office installed. I didn't install Rosetta from the snow leopard DVD, I did it when I tried to open Flash and the system asked me to install it. Everything is up to date.

I have an iMac 2.8 GHz, Intel Core 2 Duo with 4GB ram and SL 10.6.1. Aside from the fact that my 7 year old HP DeskJet 990cm no longer prints double-sided or borderless prints and WAS working fine until the SL update, it also logs me out OVER NIGHT. Even if I keep Safari open, in the morning I have to log in again. It has not logged me out while I am using it. I have checked everywhere that I can think of to see if I have something set that logs me off, but can't find anything. I've checked Tinker Tool, Preferential Treatment, and Cocktail, but don't see anything. Am I missing it? I find this EXTREMELY annoying since I am the ONLY one who uses this computer.

I WISH that companies like HP and APPLE could TRY to work together to resolve some of these issues BEFORE we have to get involved. Up to my SL "update", my HP printer has been a JEWEL. NEVER one problem until now! HP says it will NOT support an "aging" computer and the GREEN($$$) company tells me to get rid of it and buy new! Some solution. Apple can't be let off the hook either because they OBVIOUSLY dropped something to make my printer react this way. This Gutenberg driver ***** in plain English!

Can anyone help? Thanks!

I am experiencing the exact same problem as pointed out by poiuty1. Snow Leopard 10.6.1 and Excel 2004 don't like each other....

I filed a but report and this was the response:

"After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 6465069."

I have been driven to distraction with the spontaneous logouts, but only using Filemaker Pro Advanced 8.0. I seemed to have solved the problem by changing the schedule of auto-saving the cache from "during idle time" to "every 10 minutes" (Filemaker Pro Advanced>Preferences...>Memory). It may be that Filemaker doesn't recognize when the system is idle under Snow leopard and is trying to save when their is a read or write by the system. This might be the source of the problems with other software as well, i.e. performing auto-save functions at inappropriate times. It's only been a day since I made the change, but I have not had a logout in about 8 hours of continuous use, and it was happening at least once an hour, if not every 15 minutes, before.

Hi all,
I've been having similar problems with Office 2004 and 2008. I removed 2008, since I was having problems with the blue screen, followed by my computer logging out, and back in. I'm starting to experience the same problems with Word 2004. Very frustrating when you're, say, writing a large NSF proposal, or trying to finish writing an exam. I've just downloaded OpenOffice; hopefully I'll make some progress there.
FYI-I've tried cleaning caches; running all log-rotation maintenance scripts; rebuilding launch databases; and tracking things down from Console. But from the rest of the posts, it seems like Word-especially under Rosetta-is the problem.

Jason

This happened to me this morning while running Appleworks. Snow Leopard required that Rosetta be installed in order to open Appleworks. The moment it happened I had clicked my Apple wireless mouse.

I have NEVER had a problem with my mac mini prior to installing Snow Leopard 2 days ago.

While I understand that this is probably very difficult to fix, I sure hope Apple is making this a top priority.

As no "crash report" was generated to send to Apple I wonder if they are fully aware of the extent. Fortunately the document was automatically recovered when I logged in again.

Macs rock.

This happened to me while adding an account in Quicken 2007 (PPC), just updated to R3. I believe I had just added an account, made the account type selections, and was at a point where I was about to import a .qif file. The open file dialog I think was up. Then suddenly boom, blue screen, and back to login.

Weird -- and glad I wasn't doing anything mission critical. On "re-login" iTunes had to run though restoring the genius info which took a long time.

edit: obviously rosetta is installed. the only MS app running was Entourage 2008 (I think -- however it is possible Word 2008 was also open.)

Also Have this problem when using word from office 2004. Console reports 10/19/09 10:27:28 PM com.apple.launchd[1] (com.apple.WindowServer[60]) Job appears to have crashed: Segmentation fault
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: (ipc/send) invalid destination port: CGSSetMagicMirror: server didn't like your request
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: (ipc/send) invalid destination port: CGSSetMagicMirror: server didn't like your request
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: (ipc/send) invalid destination port: CGSSetMagicMirror: server didn't like your request
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: (ipc/send) invalid destination port: CGSSetMagicMirror: server didn't like your request
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: (ipc/send) invalid destination port: CGSSetMagicMirror: server didn't like your request
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: (ipc/send) invalid destination port: CGSSetMagicMirror: server didn't like your request
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: (ipc/send) invalid destination port: CGSSetMagicMirror: server didn't like your request
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: (ipc/send) invalid destination port: CGSSetMagicMirror: server didn't like your request
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: (ipc/send) invalid destination port: CGSSetMagicMirror: server didn't like your request
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: (ipc/send) invalid destination port: CGSSetMagicMirror: server didn't like your request
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: (ipc/send) invalid destination port: CGSSetMagicMirror: server didn't like your request
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: (ipc/send) invalid destination port: CGSSetMagicMirror: server didn't like your request
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: (ipc/send) invalid destination port: CGSSetMagicMirror: server didn't like your request
10/19/09 10:27:29 PM com.apple.Dock.agent[186] Mon Oct 19 22:27:29 nn.local Dock[186] <Error>: (ipc/send) invalid destination port: CGSSetMagicMirror: server didn't like your request
10/19/09 10:27:29 PM com.apple.launchd.peruser.502[182] (com.apple.Dock.agent[186]) Exited with exit code: 1
10/19/09 10:27:29 PM com.apple.ReportCrash.Root[335] 2009-10-19 22:27:29.896 ReportCrash[335:2903] Saved crash report for WindowServer[60] version ??? (???) to /Library/Logs/DiagnosticReports/WindowServer 2009-10-19-222729localhost.crash
10/19/09 10:27:32 PM com.apple.WindowServer[337] Mon Oct 19 22:27:32 nn.local WindowServer[337] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
10/19/09 10:27:48 PM com.apple.launchd.peruser.502[182] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
10/19/09 10:27:53 PM com.apple.launchd.peruser.502[182] (com.apple.Kerberos.renew.plist[374]) Exited with exit code: 1

We are having the same problem with a new MBP that shipped with SL. Designer is using it and it is randomly logging out with no warning from creative suite.

Hi,

I thought it was just me! I'm the same as all you users - Mac through and through, always up to date with software - I get the same blue screen/login window situation using MS Excel 2004 sometimes once a day sometime 3 times in 10 minutes! This happens whether I'm attached to a variety of external monitors or just on the in built screen.

I'm running 10.6.1 and now away for 3 weeks on business and unable to get back to my 10.5 install disks to downgrade - so many advances in SL and but at the cost of the trusted Mac stability! I've never owned a PC in my 15 years on computers and neither to I wish to go over to the dark side, but I need Excel for work more than I need Photoshop (which is still run via Rosetta). Please Apple get your finger out and sort this - The greater Mac community choose your machines for many reasons, but your deafening us with the sound you shooting yourself in the foot!!!

I've had a forced log out three time just today. I occasionally use Photoshop or Illustrator CS. I know I always had Firefox running. I can tell you I was told to erase down to zeroes, reinstall, and move files over. The good news is I went from 20 GB free space to 200 GB. I'm only moving stuff over as I need it. The bad news is I'm still having problems under SL.

Console lists a *Segmentation Fault* at the time of crash. What exactly is that? Sounds like some sort of directory error.

In the crash log reports, the logs always starts out with:
Process: WindowServer [####]
Path: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/WindowServer
Identifier: WindowServer

The beginning of the log has:
Exception Type: EXC BADACCESS (SIGSEGV)
Exception Codes: KERN INVALIDADDRESS at 0x00000001747ed03a
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 ...ple.CoreServices.CarbonCore 0x00007fff85dd82a6 UCKeyTranslate + 464
1 com.apple.CoreGraphics 0x00007fff87c1ad79 CGSUniCodeForKeyAndFlags + 161
2 com.apple.CoreGraphics 0x00007fff87c9088b CGXCheckForHotKey + 3184


The problem is not with our apps. We all know what the problem is. *Snow Leopard*. It's the most unstable OS I've seen, and I've been a Mac user since at least OS 6. Get the bugs out Apple.