Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Mac OS X > Can you explain this log?

Can you explain this log?
Thread Tools
Fresh-Faced Recruit
Join Date: Aug 2002
Status: Offline
Reply With Quote
Dec 26, 2002, 01:53 PM
 
Can you explan this console log and if so, could it cause the problems I have described in http://discussions.info.apple.com/we...0@.3bbcee8d/14

Mac OS X Version 10.2.3 (Build 6G30)
Dec 26 14:32:11 Pathogen WindowServer[170]: CGXDisableUpdate: Updates disabled by connection 0x4a07 for over 1.000000 seconds

Dec 26 14:32:17 Pathogen WindowServer[170]: CGXDisableUpdate: Updates disabled by connection 0x4e07 for over 1.000000 seconds

2002-12-26 14:32:21.157 loginwindow[366] CFLog (0):
CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
Contents/PkgInfo -- file://localhost/System/Library/Extensions/IomegaSAM.kext/Contents/Resources/IomegaDriver.app/
The parser will retry as in 10.1, but the problem should be corrected in the plist.
2002-12-26 14:32:21.238 loginwindow[366] CFLog (0):
CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
<plist resource in resource fork> of bundle: /Applications/Utilities/ATI Utilities/ATI Monitor/
The parser will retry as in 10.1, but the problem should be corrected in the plist.
Device Appeared
Found a device...
Activating the message port
Activiating timer port
<CFURL 0x495c0 [0xa01303fc]>{type = 15, string = Contents/PlugIns/,
base = <CFURL 0x49710 [0xa01303fc]>{type = 15, string = file://localhost/System/Library/Extensions/IomegaSAM.kext/Contents/Resources/IomegaDriver.app/, base = (null)}}
<CFArray 0x4c520 [0xa01303fc]>{type = mutable-small, count = 2, values = (
0 : <CFUUID 0x4a830> 6489D402-14F7-11D6-96CE-00306557676C
1 : <CFUUID 0x4aed0> 21ED6942-3C86-11D6-BC93-00306557676C
)}
2002-12-26 14:32:22.192 ATI Monitor[401] CFLog (0):
CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
<plist resource in resource fork> of bundle: /Applications/Utilities/ATI Utilities/ATI Monitor
The parser will retry as in 10.1, but the problem should be corrected in the plist.
2002-12-26 14:32:22.226 ATI Monitor[401] CFLog (0):
CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
<plist resource in resource fork> of bundle: /Applications/Utilities/ATI Utilities/ATI Monitor
The parser will retry as in 10.1, but the problem should be corrected in the plist.
2002-12-26 14:32:22.447 ATI Monitor[401] CFLog (0):
CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
<plist resource in resource fork> of bundle: /Applications/Utilities/ATI Utilities/ATI Monitor
The parser will retry as in 10.1, but the problem should be corrected in the plist.
before CFRunLoopRun
2002-12-26 14:32:26.670 pbs[390] CFLog (0):
CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
<plist resource in resource fork> of bundle: /Users/pathogen/Applications/Internet/iCab/iCab
The parser will retry as in 10.1, but the problem should be corrected in the plist.
2002-12-26 14:32:37.289 pbs[390] CFLog (0):
CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
<plist resource in resource fork> of bundle: /Applications/Utilities/ATI Utilities/ATI Monitor
The parser will retry as in 10.1, but the problem should be corrected in the plist.
Dec 26 14:36:07 Pathogen /Applications/Microsoft Office X/Microsoft Entourage: *** Warning: Line option kATSLineIsDisplayOnly has been deprecated. ***

Dec 26 14:36:07 Pathogen /Applications/Microsoft Office X/Microsoft Entourage: *** Warning: ATSUMeasureText has been deprecated. Use ATSUGetUnjustifiedBounds instead. ***
     
Mac Elite
Join Date: Nov 2001
Location: Trafalmadore
Status: Offline
Reply With Quote
Dec 26, 2002, 02:00 PM
 
Originally posted by pathogen67:
Can you explan this console log
Dec 26 14:36:07 Pathogen /Applications/Microsoft Office X/Microsoft Entourage: *** Warning: ATSUMeasureText has been deprecated. Use ATSUGetUnjustifiedBounds instead. ***
I get these when starting any Office App. Office needs to be updated as the older APIs have been deprecated. The others seem like driver issues with incorrectly formatted plists which I cannot explain. I have seen similar messages, but not the ones you are seeing.
I am seeing the ATI monitor message as well.
     
Fresh-Faced Recruit
Join Date: Aug 2002
Status: Offline
Reply With Quote
Dec 26, 2002, 02:45 PM
 
I am seeing the ATI monitor message as well. [/B]
What exactly does ATI monitor do? Both it and the Iomega thing installed themselves as login items. MS Database Daemon used to be as well but is no longer since movign to 10.2.2.
     
Ambrosia - el Presidente
Join Date: Sep 2000
Location: Rochester, NY
Status: Offline
Reply With Quote
Dec 26, 2002, 03:16 PM
 
What exactly do you want explained? There's nothing fatal or problematic in the log, just normal warning messages...
Andrew Welch / el Presidente / Ambrosia Software, Inc.
     
Admin Emeritus
Join Date: Oct 1999
Location: Zurich, Switzerland
Status: Offline
Reply With Quote
Dec 26, 2002, 05:55 PM
 
Basically, if you don't know what to look for in the log, you shouldn't be opening the Console.

tooki
     
Fresh-Faced Recruit
Join Date: Aug 2002
Status: Offline
Reply With Quote
Dec 26, 2002, 07:31 PM
 
Originally posted by moki:
What exactly do you want explained? There's nothing fatal or problematic in the log, just normal warning messages...
What the results of incorrect text encodings in the Plists could or could not do to overall system stability and how they possibly came to be incorrectly encoded. I find nothing normal in things listed as "problems." Only the "deprecated" messages are warnings...
     
Fresh-Faced Recruit
Join Date: Aug 2002
Status: Offline
Reply With Quote
Dec 26, 2002, 07:32 PM
 
Originally posted by tooki:
Basically, if you don't know what to look for in the log, you shouldn't be opening the Console.

tooki
A completely unhelpful comment.
     
Mac Enthusiast
Join Date: Oct 2001
Status: Offline
Reply With Quote
Dec 26, 2002, 07:37 PM
 
I agree. that reply is completely unhelpful. how unfortunate that its author is an administrator.
     
Addicted to MacNN
Join Date: Apr 2001
Location: europe
Status: Offline
Reply With Quote
Dec 26, 2002, 07:48 PM
 
Originally posted by pathogen67:
What the results of incorrect text encodings in the Plists could or could not do to overall system stability
Nothing.
how they possibly came to be incorrectly encoded.
They were saved as plain text.
I find nothing normal in things listed as "problems."
It doesn't say "problem" anywhere.
Nasrudin sat on a river bank when someone shouted to him from the opposite side: "Hey! how do I get across?" "You are across!" Nasrudin shouted back.
     
Fresh-Faced Recruit
Join Date: Aug 2002
Status: Offline
Reply With Quote
Dec 26, 2002, 08:06 PM
 
Originally posted by Developer:
It doesn't say "problem" anywhere.
Actually, it says it seven times...

The parser will retry as in 10.1, but the problem should be corrected in the plist.
They were saved as plain text.
By whom, ATI? What can or should I do about them? And what of the Iomega error?
     
Professional Poster
Join Date: Sep 2002
Location: New York, NY
Status: Offline
Reply With Quote
Dec 26, 2002, 08:38 PM
 
The parser will retry as in 10.1, but the problem should be corrected in the plist.
10.2 updated the format of plist files. This warning is a result of programs still using 10.1-style plists. It just means that the system was unable to parse the plist using the new 10.2 style. Thus, it is going to try parsing them as 10.1 plists.
Vandelay Industries
     
Fresh-Faced Recruit
Join Date: Aug 2002
Status: Offline
Reply With Quote
Dec 26, 2002, 08:51 PM
 
Originally posted by Art Vandelay:
Thus, it is going to try parsing them as 10.1 plists.
Thanks Art! Do you see anything in the log that could cause the problems I am having?
     
Ambrosia - el Presidente
Join Date: Sep 2000
Location: Rochester, NY
Status: Offline
Reply With Quote
Dec 27, 2002, 12:13 AM
 
Originally posted by pathogen67:
What the results of incorrect text encodings in the Plists could or could not do to overall system stability and how they possibly came to be incorrectly encoded. I find nothing normal in things listed as "problems." Only the "deprecated" messages are warnings...
No, that won't be causing any problems -- those errors are really meant for the programmers of the applications that are generating them.
Andrew Welch / el Presidente / Ambrosia Software, Inc.
     
Addicted to MacNN
Join Date: Apr 2001
Location: europe
Status: Offline
Reply With Quote
Dec 27, 2002, 05:25 AM
 
Originally posted by pathogen67:
By whom, ATI? What can or should I do about them? And what of the Iomega error?
Yes, by ATI. You do nothing. ATI will update the plist before a future OS version stops parsing the old format (or their stuff will simply stop working). The same with Iomega.
Then there's someone showing the contents of an URL and an array, most likely as an debugging aid. That should have been removed for the shipping version, but its harmless.
There's nothing unusual inside these logs.
Nasrudin sat on a river bank when someone shouted to him from the opposite side: "Hey! how do I get across?" "You are across!" Nasrudin shouted back.
     
Addicted to MacNN
Join Date: Mar 2000
Location: London, UK
Status: Offline
Reply With Quote
Dec 27, 2002, 08:17 AM
 
Programs spew out things from time to time for debugging/development purposes. I'm with tooki on this one: if you don't know what it means, and you aren't experiencing any problems, just ignore it.
     
Fresh-Faced Recruit
Join Date: Aug 2002
Status: Offline
Reply With Quote
Dec 27, 2002, 08:57 AM
 
There's nothing unusual inside these logs. [/B]
Thanks for the info, Developer
     
Fresh-Faced Recruit
Join Date: Aug 2002
Status: Offline
Reply With Quote
Dec 27, 2002, 09:00 AM
 
Originally posted by Angus_D:
Programs spew out things from time to time for debugging/development purposes. I'm with tooki on this one: if you don't know what it means, and you aren't experiencing any problems, just ignore it.
Shipped versions are NOT supposed to spew out debug messages. Tooki's comment was unhelpful and smacked of arrogance. It also directly contradicts the reason for these message boards- so people can ask questions about things they don't know about. Finally, as I indicated in my first posting, I AM having problems. That is why I looked in the console log.
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 12:10 PM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2