PDA

View Full Version : Errors in console mode


Julin Maloof
04-05-2002, 06:04 PM
Hello,

When I start up in console mode (">console") from the login screen,
I get 4 errors repeatedly. These occur even before I login. Any ideas about what these mean and what I can do to fix the problem?

The errors are:

local host open: (ipc/send) invalid destination port: initCGDisplayState: cannot map display interlocks

local host open: kCGError Failure:CGSNewConnection cannot connect to server

localhost open: kCGErrorInvalidConnection : CGSGetEventPort: Inavlid connection

If I do log in and look at what is going on using top, "open" and "mach_init" are eating a lot of CPU power.


Thanks,

Julin

WillyT
04-06-2002, 08:53 PM
The CG part of the prefix would seem to point to CoreTechnologies Graphics as an origin. I can't yet find these specific functions in the docs so they may be private to Quartz. The k part of the prefix "may" mean kernal or kernal extention.

The names of the functions would seem to refer to a monitor or display. The server would probably be a display server and if you can't connect to the server you wont have a valid port.

So I would suggest checking your display prefs. Maybe you could tell us more about your system. Also open the Console after you've logged in and see if the messages are in the Console.log.

So far this is just speculation on my part.

mervTormel
04-06-2002, 09:54 PM
Originally posted by WillyT
The k part of the prefix "may" mean kernal or kernal extention.
the k is a convention to designate a pre-processor constant value in c programming, like

define kCGSomeError 128

e.g., see file: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Headers/CGError.h

but, i agree with willy about the coregraphics business. seems that your login is doing something that assumes and is dependent on a valid quartz environment running (?)

more speculation: what is it in your login scriptage that may try to open a display?

Julin Maloof
04-07-2002, 06:21 PM
Thanks for the tips.

It turns out that it is due to an item in my /Library/StartupItems folder. Specifically something that was placed there by "Now Up-To-Date and Contact" when I installed it.

(I'll have to see if I can get them to fix it).

Thanks again,

Julin