PDA

View Full Version : Logging into Desktop is constantly crashing in 10.8




Molto Bene
Dec 5, 2012, 06:15 AM
I wan't sure whether to post this in the ML or ML Server forums, but I think this problem is not specific to the server:

I am running ML Server on a 2011 iMac and this problem surfaced a few days ago: One of the network accounts keeps getting immediately kicked out of the desktop when it attempts to log in.

I have a couple of network accounts and a couple of local accounts on this machine and all other accounts work fine and show no signs of this problem.

I can log into the account via the >console login, as well as ssh'ing into it. So the problem seems to be specific to logging into the desktop.

Comparing the log files between a failed login and a successful one from another account I see the first difference appears at :

successful:
12/3/12 9:58:12.990 AM loginwindow[1596]: Login Window - Returned from Security Agent
12/3/12 9:58:13.061 AM loginwindow[1596]: USER_PROCESS: 1596 console
12/3/12 9:58:13.064 AM apsd[66]: Unable to bootstrap_lookup connection port for 'com.apple.syncdefaultsd.push': Unknown service name

failed:
12/4/12 7:52:04.609 AM loginwindow[1749]: Login Window - Returned from Security Agent
12/4/12 7:52:04.649 AM loginwindow[1749]: ERROR | ScreensharingLoginNotification | Failed sending message to screen sharing GetScreensharingPort, err: 1102
12/4/12 7:52:04.675 AM loginwindow[1749]: USER_PROCESS: 1749 console

and subsequently:
12/4/12 7:52:04.829 AM ReportCrash[1922]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
12/4/12 7:52:05.045 AM ReportCrash[1922]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
12/4/12 7:52:05.046 AM ReportCrash[1922]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
12/4/12 7:52:05.046 AM ReportCrash[1922]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
12/4/12 7:52:05.046 AM ReportCrash[1922]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
12/4/12 7:52:05.046 AM ReportCrash[1922]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
12/4/12 7:52:05.046 AM ReportCrash[1922]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
12/4/12 7:52:05.046 AM ReportCrash[1922]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
12/4/12 7:52:05.046 AM ReportCrash[1922]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
12/4/12 7:52:05.046 AM ReportCrash[1922]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
12/4/12 7:52:05.046 AM ReportCrash[1922]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0


the error messages in the log files go on for a while, and a loginwindow crash report is generated, but alas, this is where I have reached my current depth in system debugging. (I can copy over the crash report if needed).

My operating theory is that my wife (who's account is crashing) was doing something (most likely office word related) and the process did not shut down gracefully when she logged out and left behind something that is causing the crash (but this is just a shot in the dark).

So given that I can ssh into that account, I was hoping that there is some left over tmp or state file somewhere that can be deleted to return life back to normal. Otherwise, the other course of action I can think of is to do a Time Machine restore on that account from Migration Assistant (but a) I don't know what the potential side effects might be, and b) I would be highly irked to remain in the dark as to the cause of the crashes.)

Sorry for the very verbose post, any help is appreciated. Thx.