Jump to content

Problem with Sierra and iCloud


Morpheus NS
 Share

17 posts in this topic

Recommended Posts

I have successfully installed Sierra public beta on my machine from description. It runs fine but there is one problem. I cannot start certain applications (Messages, QuickTime Player, iBooks).

 

I've (kind of) isolated the problem to iCloud. If I do not enter my iCloud username and password in System preferences, these apps work fine. But if I choose to do it, I run into problems. I tried creating a new user, the same thing happens - as long as I don't login to iCloud everything works fine.

 

So, I'm guessing there is a problem with some configuration files downloaded from iCloud, but how can I find out which ones? Is there an application which can check all plists and determine which one is corrupted?

 

Also:

post-626651-0-51397900-1468531141_thumb.png

 

Any ideas?

Link to comment
Share on other sites

Nothing? The crashed thread is always the same, attached below. vImage, ColorSync, QuartzCore... problems with graphics compatibility?

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.vImage              	0x000000010bfc98b3 vConvert_PlanarFtoPlanar16F_hardware_rm_tonearest + 547
1   com.apple.vImage              	0x000000010bfacd25 vImageConvert_PlanarFtoPlanar16F + 661
2   com.apple.ColorSync           	0x000000010f58fba2 NxMLUTCreateData(int, void*, bool, unsigned long, unsigned long, unsigned long) + 951
3   com.apple.ColorSync           	0x000000010f587847 compact_and_flatten_sequence(CMMTransform*, CMMConvNode*, CMMConvNode*, CMMMemMgr&, CMMColorSpaceType, CMMColorSpaceType, unsigned long, __CFString const*, __CFString const*, unsigned long) + 1353
4   com.apple.ColorSync           	0x000000010f587dfa DoFlattenCompactConversion + 770
5   com.apple.ColorSync           	0x000000010f588943 AppleCMMCreateTransformProperty + 377
6   com.apple.ColorSync           	0x000000010f570918 ColorSyncTransformIterate + 392
7   com.apple.CoreGraphics        	0x000000010b1647d8 CGColorConversionInfoIterateFunctionsWithCallbacks + 741
8   com.apple.QuartzCore          	0x000000010bd839fe CA::ColorProgram::Program::compact_program(CGColorConversionInfo const*, int, bool, bool&) + 594
9   com.apple.QuartzCore          	0x000000010bd85b84 CA::ColorProgram::Cache::lookup_(CGColorSpace*, unsigned int, CGColorRenderingIntent) + 420
10  com.apple.QuartzCore          	0x000000010bd8615f CA::ColorProgram::Cache::convert_color(CGColorSpace*, float*, CGColorRenderingIntent) + 69
11  com.apple.QuartzCore          	0x000000010bd5d98a CA::CG::ContextDelegate::device_color(double const*, CGColorSpace*) + 238
12  com.apple.QuartzCore          	0x000000010bc6e272 CA::CG::DeviceColor::DeviceColor(CGColor*, CGRenderingState*, CGGState*, CA::CG::ContextDelegate&, CA::OGL::BaseColor) + 284
13  com.apple.QuartzCore          	0x000000010bd60414 CA::CG::DrawOp::DrawOp(CA::CG::ContextDelegate&, CGRenderingState*, CGGState*, CGColor*, unsigned int) + 240
14  com.apple.QuartzCore          	0x000000010bd5dd61 CA::CG::ContextDelegate::fill_rects(CA::CG::Queue*, CGRenderingState*, CGGState*, CGColor*, CGRect const*, unsigned long, bool) + 213
15  com.apple.QuartzCore          	0x000000010bd5f11f CA::CG::ContextDelegate::draw_rects_(CGContextDelegate*, CGRenderingState*, CGGState*, CGPathDrawingMode, CGRect const*, unsigned long) + 121
16  com.apple.CoreGraphics        	0x000000010b115254 CGContextFillRects + 96
17  com.apple.CoreGraphics        	0x000000010b115347 CGContextFillRect + 135
18  com.apple.AppKit              	0x00000001092811ef NSRectFill + 272
19  com.apple.AppKit              	0x00000001092e354e -[NSScrollView drawRect:] + 489
20  com.apple.AppKit              	0x000000010929634d -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inGraphicsContext:CGContext:topView:shouldChangeFontReferenceColor:] + 1318
21  com.apple.AppKit              	0x00000001092967fd -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inGraphicsContext:CGContext:topView:shouldChangeFontReferenceColor:] + 2518
22  com.apple.AppKit              	0x00000001092967fd -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inGraphicsContext:CGContext:topView:shouldChangeFontReferenceColor:] + 2518
23  com.apple.AppKit              	0x0000000109295cf0 __46-[NSView(NSLayerKitGlue) drawLayer:inContext:]_block_invoke + 267
24  com.apple.AppKit              	0x000000010929580d -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 2509
25  com.apple.AppKit              	0x0000000109294e3a -[NSView(NSLayerKitGlue) drawLayer:inContext:] + 80
26  com.apple.QuartzCore          	0x000000010bc7d0f8 CABackingStoreUpdate_ + 4314
27  com.apple.QuartzCore          	0x000000010bd98dd4 ___ZN2CA5Layer8display_Ev_block_invoke + 75
28  com.apple.QuartzCore          	0x000000010bd98a4e CA::Layer::display_() + 1748
29  com.apple.AppKit              	0x0000000109293d2e _NSBackingLayerDisplay + 577
30  com.apple.AppKit              	0x0000000109286ac9 -[_NSViewBackingLayer display] + 885
31  com.apple.QuartzCore          	0x000000010bd8cbae CA::Layer::display_if_needed(CA::Transaction*) + 572
32  com.apple.QuartzCore          	0x000000010bd8ccd9 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 35
33  com.apple.QuartzCore          	0x000000010bd82530 CA::Context::commit_transaction(CA::Transaction*) + 280
34  com.apple.QuartzCore          	0x000000010bc7a1e5 CA::Transaction::commit() + 475
35  com.apple.QuartzCore          	0x000000010bc7ab42 CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*) + 108
36  com.apple.CoreFoundation      	0x000000010a7d1247 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
37  com.apple.CoreFoundation      	0x000000010a7d11b7 __CFRunLoopDoObservers + 391
38  com.apple.CoreFoundation      	0x000000010a7b1ba6 CFRunLoopRunSpecific + 454
39  com.apple.HIToolbox           	0x0000000111c49a3c RunCurrentEventLoopInMode + 240
40  com.apple.HIToolbox           	0x0000000111c49871 ReceiveNextEventCommon + 432
41  com.apple.HIToolbox           	0x0000000111c496a6 _BlockUntilNextEventMatchingListInModeWithFilter + 71
42  com.apple.AppKit              	0x0000000109137dcd _DPSNextEvent + 1093
43  com.apple.AppKit              	0x0000000109844bbc -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1658
44  com.apple.AppKit              	0x000000010912c73c -[NSApplication run] + 926
45  com.apple.AppKit              	0x00000001090f7cda NSApplicationMain + 1237
46  com.apple.iChat               	0x0000000104a22813 main + 1679
47  libdyld.dylib                 	0x000000010c8d4255 start + 1

Link to comment
Share on other sites

I would try to create another User in OSX and log on.

Then try the iCloud connection with that user and your AppleID.

Maybe there is some issue with your original OSX user account or profile...

Link to comment
Share on other sites

I tried that earlier, but situation is the same. I can open iMessage with new user, but as soon as I enter my iCloud username and password it panics and from that moment on everything is the same as on my main account. iMessage fails as soon as I open it, iCloud system preferences panel logs me out as soon as I open it, and iBooks have trouble opening PDF's. 

 

The obvious solution is to create new iCloud account but that would be a pain in the ***, I'd have to backup everything. enter all my passwords again and change iCloud account on my iPhone too.

Link to comment
Share on other sites

Sure, here's the current one:

 

config.plist.zip

 

It worked very well with Yosemite and El Capitan, I never had any problems with iCloud services. Even now everything works fine apart from the iMessage issue, everything is synced.

 

I plan to move to iMac 13,1 SMBios, it seems to be a better fit for my current configuration because it uses an Ivy Bridge processor with similar clock speed.

Link to comment
Share on other sites

iMessage works fine with all the same settings in El Capitan. The only thing different between two installations is that Sierra is installed on an SSD, and El Capitan on 7200rpm HDD.

 

Now I am really lost. When I enter the top message from the error report in google search there is one (literally ONE) result -> mine from this thread. 

Link to comment
Share on other sites

  • 1 month later...

iMessage works fine with all the same settings in El Capitan. The only thing different between two installations is that Sierra is installed on an SSD, and El Capitan on 7200rpm HDD.

 

Now I am really lost. When I enter the top message from the error report in google search there is one (literally ONE) result -> mine from this thread. 

 

Hello. Please try this kernel patch in your config plist in KernelAndKextPatches section

 		<key>KernelToPatch</key>
		<array>
			<dict>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				uaABAAAPMg==
				</data>
				<key>MatchOS</key>
				<string>10.12</string>
				<key>Replace</key>
				<data>
				uaABAAAxwA==
				</data>
			</dict>
		</array>

post-1069282-0-20617200-1473376349_thumb.png

 

It should help with your problem.

Please report.

 

Best regards.

  • Like 2
Link to comment
Share on other sites

  • 2 weeks later...

Hello. Please try this kernel patch in your config plist in KernelAndKextPatches section

 

 

It took a while, sorry.  I managed to try it today using USB stick with the same version of Clover as on my main SSD... did not help. I get exactly the same error as before. 

Link to comment
Share on other sites

It took a while, sorry. I managed to try it today using USB stick with the same version of Clover as on my main SSD... did not help. I get exactly the same error as before.

You sure injecting this patch in KernelToPatch section, 'cos everybody insert it in KextToPatch))) This is KERNEL patch.

Also use latest clover!!!

Link to comment
Share on other sites

It works with Clover r3763! I needed NullCPUPowerManagement.kext for some reason (kernel panic with AppleIntelCPUPowerManagement.kext otherwise), but iMessage works fine. Thank you so much!

 

I think i can help you with this also :)

1. Delete NullCPUPowerManagement.kext

2. Add one more KERNEL patch in KernelToPatch section

			<dict>
				<key>Comment</key>
				<string>xcpm on Sierra Haswell Celeron/Pentium</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				g8PEg/si
				</data>
				<key>MatchOS</key>
				<string>10.12</string>
				<key>Replace</key>
				<data>
				g8PGg/si
				</data>
			</dict>

post-1069282-0-67684600-1474560337_thumb.png

 

3. Add -xcpm in BootArgs

4. Now your CPU will use XCPM mode instead of AppleIntelCPUPowerManagement and speedstep will work

5. Profit :)

Link to comment
Share on other sites

Hello. Please try this kernel patch in your config plist in KernelAndKextPatches section

 		<key>KernelToPatch</key>
		<array>
			<dict>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				uaABAAAPMg==
				</data>
				<key>MatchOS</key>
				<string>10.12</string>
				<key>Replace</key>
				<data>
				uaABAAAxwA==
				</data>
			</dict>
		</array>

attachicon.gifСнимок экрана 2016-09-09 в 02.14.28.png

 

It should help with your problem.

Please report.

 

Best regards.

wow .. thanks @vandroiy2012 ..  :thumbsup_anim:

Link to comment
Share on other sites

That one didn't work, I guess because G1610 is an Ivy Bridge processor. None of the power management tweaks worked for me in the past. That's not a problem, I plan on moving to newer architecture in a couple of months anyway.

 

Try adding FakeCPUID 0x0306A0 in config.plist

It should work because we mask our Haswell Celeron with IvyBridge ID :) And this patch enables XCPM mode for Ivy Bridge forcing system to think that Ivy Bridge is actually Haswell Core i5 . 

post-1069282-0-93807100-1474564226_thumb.png

Link to comment
Share on other sites

  • 1 month later...

It works with Clover r3763! I needed NullCPUPowerManagement.kext for some reason (kernel panic with AppleIntelCPUPowerManagement.kext otherwise), but iMessage works fine. Thank you so much!

 

I have same issue with iMessage, and find this thread so useful, thank you @vandroiy2012 for the iMassage patch. Yes for some reason AICPM clover patch is not working (KP) . So, I tried manually patching the kernel with hex editor, and let clover did the job with AICPM patch. And it works!! (hope this fixed in future clover update).

Link to comment
Share on other sites

 Share

×
×
  • Create New...