Issue with Mac Desktop after upgrade to parallels 12 [Workaround Found]

Hi everyone,

With Parallels 11, I was able to set an option in the configuration so that parallels would use one of the Mac desktops. This would allow me to switch between Mac OS/Desktop full screen and Windows 10/Desktop full screen using CTRL 1-3.

Now that I can't assign one of the three Mac desktops to Parallels, this feature is gone.

Would anyone know how to do the same with Parallels 12?

Failing this, could it be brought back? Surely I'm not the only user who needs this to switch easily between Mac/Win?

Thanks!

 

Hi EmmanuelO1,
Try to follow the steps given in this article.

 

Thanks Ajith, but my issue isn't related to a second monitor or to full screen. I only have one monitor, and I have no problem to switch parallels between windowed and full screen using ctrl-command-F.
What I used to do with Parallels 11 was to assign one of the three Mac OS desktops (say desktop 1) to Mac OS, and another Mac OS desktop (say desktop 2) to PArallels full screen. That way, I was able to switch (on the same monitor) between Mac OS and Windows 10 using CTRL-1 (Mac OS) and CTRL-2 (Windows 10). This was using the Mac OS shortcuts to switch between its 3 desktops. Parallels 11 also assigned a Parallels desktop initially, but there was an option in the settings (forgot which one) that allowed me to force it to use a Mac OS desktop (1-3) instead of a specific Parallels desktop (no number).
With Parallels 12, there is no way to do this because the option is gone. I can only use Parallels in its own specific desktop, so I can't switch between MacOS and Windows in full screen using the CRTL-1 or CTRL-2 key combinations.

 

In fact looking at your screenshot in step 3 this is precisely the option that disappeared in Parallels 12, that screenshot is from Parallels 11. If you look at the full screen options in Parallels 12, you'll see that they are different and the option to use OS X full screen is gone. So I wouldn't be able to follow the steps given in this article

 

Hi Ajith, Have you been able to reproduce, and is there any chance this could be fixed? Thanks

 

Any chance to get a reply?

 

So no one is dealing with this?

 

If Ajith isn't available, could someone else at Parallels look into this issue and confirm whether it is being investigated or whether this is supposed to be an "upgrade"? I've upgraded all my versions of Parallels yearly for years, but if it's staying like this I'm just going to revert to Parallels 11 and forget about upgrading.

 

Please check this article for more information.
Ctrl + 1,2,3 is a Mission control Mac setting to switch between Mac Desktops.
Please make sure "Switch to Desktop" is enabled from System Preference -> Keyboard -> Shortcuts -> Mission Control -> Switch to Desktop 1,2,3,etc.,

 

Hi Raj,

Thank you for this, but as explained in the thread, I have no issues using CTRL 1-3 to switch between Mac desktops. The problem is that in Parallels 12, contrary to Parallels 11, it's impossible to assign a Mac Desktop to Parallels. Parrallels has its own desktop (called parallels desktop) which isn't controlled by CTRL 1-3. It was the same in Parallels 11 initially, but there was an option in Parallels settings that allowed to get Parallels assigned to a Mac desktop. This option in Parallels settings (assign full screen to OS X) is gone.

Please read my description in detail, and try to reproduce. The solution that Ajith provided is impossible because the settings are different in Parallels 11 and Parallels 12. The how to he linked to was from an old version of parallels, not 12.

By the way, I have assigned the Parallels app to the Mac desktop 2 only, but that doesn't pay any role when parallels is displayed full screen, unlike with version 11. The full screen Windows VM is assigned to a separate desktop (Parallels desktop) in V12 and cannot be controlled by CTRL 1-3.

 

Please could you confirm that this is being investigated? Two members of the Parallels team have replied with suggestions that don't apply due to the changes between Parallels 11 and Parallels 12. It would be nice if someone could take the time to read the description of the issue, understand it and try to replicate so that it gets fixed. Thanks!

 

Anyone from the team? Thank you.

 

Please check your private message. We'll continue from there.

 

When I go full screen (with the OS X little Green window control), I get logged out of Mac OS X. HUGE BUG! Anyone else?
(rMBP 2014, Sierra, PD12, Ubuntu Desktop VM.)

 

Please try updating Parallels Desktop to the latest build and see how it works.

 

I'm running version: 12.1.0 (41489) - problem is in this version. PD12 thinks it's up to date.

 

When I go full screen in PD12 I get this WindowServer crash - every time - a major BUG IMO:

Process: WindowServer [177]
Path: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer
Identifier: WindowServer
Version: 600.00 (13)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: WindowServer [177]
User ID: 88

Date/Time: 2016-11-12 00:56:00.205 +0000
OS Version: Mac OS X 10.12.1 (16B2555)
Report Version: 12
Anonymous UUID: FF3AA81F-206F-5362-182B-B30DECEA897E

Sleep/Wake UUID: 30B2024C-C99D-4C70-84AA-D829252D9C40

Time Awake Since Boot: 26000 seconds
Time Since Wake: 4700 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
Assertion failed: (region1 != NULL), function CGRegionContainsRegion, file /Library/Caches/com.apple.xbs/Sources/Quartz2D/Quartz2D-1070.8/CoreGraphics/Regions/CGRegion.c, line 483.


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff961a8dda __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff96294787 pthread_kill + 90
2 libsystem_c.dylib 0x00007fff9610e420 abort + 129
3 libsystem_c.dylib 0x00007fff960d5893 __assert_rtn + 320
4 com.apple.CoreGraphics 0x00007fff816bc9d0 CGRegionContainsRegion + 87
5 com.apple.SkyLight 0x00007fff924645af WSOrderSurface + 1403
6 com.apple.SkyLight 0x00007fff92587665 __PKGSystemStatusBarCloneItemsForSpace_block_invoke + 544
7 com.apple.SkyLight 0x00007fff925859d1 __WalkAllStatusItems_block_invoke + 24
8 com.apple.CoreFoundation 0x00007fff80f72214 CFArrayApplyFunction + 68
9 com.apple.SkyLight 0x00007fff92585998 WalkAllStatusItems + 151
10 com.apple.SkyLight 0x00007fff925a5078 PKGWillSwitchSpaces + 520
11 com.apple.SkyLight 0x00007fff924fb88a _XWillSwitchSpaces + 104
12 com.apple.SkyLight 0x00007fff923df8a7 __connectionHandler_block_invoke + 87
13 com.apple.SkyLight 0x00007fff9255cb0f CGXHandleMessage + 112
14 com.apple.SkyLight 0x00007fff923dec45 connectionHandler + 216
15 com.apple.SkyLight 0x00007fff92554053 post_port_data + 251
16 com.apple.SkyLight 0x00007fff92553d38 run_one_server_pass + 933
17 com.apple.SkyLight 0x00007fff925538ce CGXRunOneServicesPass + 356
18 com.apple.SkyLight 0x00007fff92554f40 SLXServer + 3738
19 WindowServer 0x0000000103d76dde 0x103d76000 + 3550
20 libdyld.dylib 0x00007fff9607a255 start + 1

Thread 1:: com.apple.coreanimation.render-server
0 libsystem_kernel.dylib 0x00007fff961a141a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff961a0867 mach_msg + 55
2 com.apple.QuartzCore 0x00007fff86b7d7f5 CA::Render::Server::server_thread(void*) + 254
3 com.apple.QuartzCore 0x00007fff86c2bce3 thread_fun + 25
4 libsystem_pthread.dylib 0x00007fff96291aab _pthread_body + 180
5 libsystem_pthread.dylib 0x00007fff962919f7 _pthread_start + 286
6 libsystem_pthread.dylib 0x00007fff96291221 thread_start + 13

Thread 2:
0 libsystem_kernel.dylib 0x00007fff961a94e6 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff96291622 _pthread_wqthread + 1023
2 libsystem_pthread.dylib 0x00007fff96291211 start_wqthread + 13

Thread 3:
0 libsystem_kernel.dylib 0x00007fff961a94e6 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff96291622 _pthread_wqthread + 1023
2 libsystem_pthread.dylib 0x00007fff96291211 start_wqthread + 13

Thread 4:
0 libsystem_kernel.dylib 0x00007fff961a94e6 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff96291622 _pthread_wqthread + 1023
2 libsystem_pthread.dylib 0x00007fff96291211 start_wqthread + 13

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff5be70a78 rdx: 0x0000000000000000
rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff5be70aa0 rsp: 0x00007fff5be70a78
r8: 0x0000000000000000 r9: 0x00000000000001e3 r10: 0x0000000008000000 r11: 0x0000000000000206
r12: 0x000000013acf7028 r13: 0x000000013acf7000 r14: 0x00007fff9ed9a3c0 r15: 0x00007fff81851b16
rip: 0x00007fff961a8dda rfl: 0x0000000000000206 cr2: 0x00007fff9ed7c128
Logical CPU: 0
Error Code: 0x02000148
Trap Number: 133

... There is more of this crash report - let me know if you want it. Thanks for your help Parallels!

 

Hi Raj,

Thanks very much for looking into this, I've emailed you a link to a video showing the issue so you can reproduce.

JeremyK3, please could you create a separate thread as your issue has nothing to do with mine? Thanks!

 

@emmanuel: Sorry for the hijacking attempt and I will create another thread. Although I strongly suspect if they fix your issue, mine will go away too.

 

No problem .
My issue was escalated yesterday after support received a video showing the issue and a problem report ID, I'll keep the thread updated when I hear back from support.