Comments
-
Greg Hurrell
Status changed:
- From: new
- To: open
-
Greg Hurrell
Can you give me a complete example path for one of the plist files that appears in the log?
-
Greg Hurrell
Summary changed:
- From: Synergy
- To: CFPropertyListCreateFromXMLData() "plist parse failed" messages in console
-
anonymous
Created
,
edited
Here's a few of the most recent console log entries. Each entry is followed by a version check failure. Perhaps connected in some way ? Curious that the "suggested" file name is not always the same. A google search of "CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8." produces many hits.
2009-05-27 03:31:17.442 Synergy[339] CFLog (0): CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be: /Users/foo/Library/Autosave Information/org.wincent.Synergy.plist The parser will retry as in 10.2, but the problem should be corrected in the plist. 2009-05-27 03:31:17.448 Synergy[339] Error while attempting automatic version check 2009-05-27 21:00:47.339 Synergy[228] CFLog (0): CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be: /Users/foo/Library/Cookies/Cookies.plist The parser will retry as in 10.2, but the problem should be corrected in the plist. 2009-05-27 21:00:47.345 Synergy[228] Error while attempting automatic version check 2009-06-01 06:27:29.820 Synergy[228] CFLog (0): CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be: /Users/foo/Library/Autosave Information/org.wincent.Synergy.plist The parser will retry as in 10.2, but the problem should be corrected in the plist. 2009-06-01 06:27:29.826 Synergy[228] Error while attempting automatic version check 2009-06-02 06:27:29.876 Synergy[228] CFLog (0): CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be: /Users/foo/Library/Autosave Information/org.wincent.Synergy.plist The parser will retry as in 10.2, but the problem should be corrected in the plist. 2009-06-02 06:27:29.883 Synergy[228] Error while attempting automatic version check 2009-06-03 00:16:28.218 Synergy[293] CFLog (0): CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be: /Users/foo/Library/Cookies/Cookies.plist The parser will retry as in 10.2, but the problem should be corrected in the plist. 2009-06-03 00:16:28.223 Synergy[293] Error while attempting automatic version check 2009-06-05 09:13:22.290 Synergy[562] CFLog (0): CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be: /Users/foo/Library/Cookies/Cookies.plist The parser will retry as in 10.2, but the problem should be corrected in the plist. 2009-06-05 09:13:22.301 Synergy[562] Error while attempting automatic version check 2009-06-06 09:13:22.391 Synergy[562] CFLog (0): CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be: /Users/foo/Library/Cookies/Cookies.plist The parser will retry as in 10.2, but the problem should be corrected in the plist. 2009-06-06 09:13:22.402 Synergy[562] Error while attempting automatic version check
-
Greg Hurrell
Interesting. Both of the paths mentioned — the "autosave" one and the "cookies" one — are managed by the system and are never explicitly manipulated by Synergy itself.
Can I suggest quitting Synergy, deleting both of those files, and seeing what happens?
-
anonymous
Even stranger:
The "Autosave Information" file does not exist. Did it ever ? I wonder "who" makes it ? Since 6 June no further console messages.
I'll delete the "Cookies" file, relaunch as suggested, and report back one way or the other. After an appropriate elapse of time, reboot, etc.
-
anonymous
Created
,
edited
Well, didn't take too long. Console message reappeared :-)
Before deleting file and restarting Synergy:
2009-06-09 21:02:42.788 Synergy[562] CFLog (0): CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be: /Users/foo/Library/Application Support/Synergy/Album Covers/Artist-BBCRadio4,Album-ReithLectures2009.plist The parser will retry as in 10.2, but the problem should be corrected in the plist. 2009-06-09 21:02:42.795 Synergy[562] Error while attempting automatic version check And first time we restart Synergy: 2009-06-09 22:32:38.066 Synergy[5023] CFLog (0): CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be: /Users/foo/Library/Autosave Information/org.wincent.Synergy.plist The parser will retry as in 10.2, but the problem should be corrected in the plist. 2009-06-09 22:32:38.073 Synergy[5023] Error while attempting automatic version check Restart Synergy again: 2009-06-09 22:34:55.232 Synergy[5028] CFLog (0): CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be: /Users/foo/Library/Autosave Information/org.wincent.Synergy.plist The parser will retry as in 10.2, but the problem should be corrected in the plist. 2009-06-09 22:34:55.239 Synergy[5028] Error while attempting automatic version check
Something odd. Possibly the file name diagnostic is simply an unhelpful red herring. Many google hits, here's one at randomish:
-
Greg Hurrell
Ok, the autosave information I have no idea how or why that one gets created. There are a lot of places in Mac OS X where you request a resource or perform an operation and the system itself will create this kind of settings file, or cache, or whatever, and will supposedly clean up after itself. Undoubtedly it's being triggered indirectly by use of some other API. I might be able to set a breakpoint on
CFLog()and find out where it's originating from.As for the other messages, eg the
/Users/foo/Library/Application Support/Synergy/Album Covers/Artist-BBCRadio4,Album-ReithLectures2009.plist; those are specifically created by Synergy, so I will look at the place where that's happening and see if I can switch to a different API which doesn't trigger those messages.Needless to say, you shouldn't worry too much about these messages as they're not actually indicative of any real problem. But I will see if I can remove them as a cosmetic clean up anyway.
-
anonymous
Thanks - I wasn't (worrying) :)
I did wonder if they might in some way be related to the version check message (it is consistently close in time). Unless/until you release a new version I shall not know whether the version check is actually working as intended. I do recall not becoming aware that there was a version 3.2.2 available until I checked the web-site for some reason, so perhaps there is a real defect.
Regards
-
Greg Hurrell
Ok, will look into the version check stuff as well to make sure it's all working as intended.
Still don't have proper Internet access yet, but the technicians are apparently coming tomorrow so should be able to make some progress soon.
Add a comment
Comments are now closed for this issue.