Hang when click on Configure in Big Sur

[RyanC17]

I'm using macOS Big Sur as the host and Parallels hangs when trying to enter the Configure page. I also tried the App Store version which has the same problem. Is there any workaround for this issue?

 

[Maria@Parallels]

I'm using macOS Big Sur as the host and Parallels hangs when trying to enter the Configure page. I also tried the App Store version which has the same problem. Is there any workaround for this issue?

Hello, did you get any specific error message?

 

[RyanC17]

Hello, did you get any specific error message?

Nope. The only thing I got is a spinning rainbow.

 

[Maria@Parallels]

Nope. The only thing I got is a spinning rainbow.

Did you check this KB article for more info about the known issues with Parallels Desktop and Big Sur?

 

[RyanC17]

Did you check this KB article for more info about the known issues with Parallels Desktop and Big Sur?

Yes, I did. But this issue is not listed there. I believe I saw somebody else has reported the same issue in another thread but no one got the solution.

 

[Maria@Parallels]

Yes, I did. But this issue is not listed there. I believe I saw somebody else has reported the same issue in another thread but no one got the solution.

Could you please share a bit more details about the issue?
When does it happened? After starting VM or after login?
Could yo collect the tech report once the issue reproduced please? and post the report's ID here?

 

[RyanC17]

Could you please share a bit more details about the issue?
When does it happened? After starting VM or after login?
Could yo collect the tech report once the issue reproduced please? and post the report's ID here?

As long as you click on that Configure button, no matter the VM is started or stoped or is in installing process, the whole program hangs. This is the ID:
345670552. Thanks

 

[RyanC17]

Could you please share a bit more details about the issue?
When does it happened? After starting VM or after login?
Could yo collect the tech report once the issue reproduced please? and post the report's ID here?

So I checked Console and this is the error I believe is causing the issue: Failed to get QCocoaScreen for NSObject(0x0)

 

[Maria@Parallels]

So I checked Console and this is the error I believe is causing the issue: Failed to get QCocoaScreen for NSObject(0x0)

Found this article about the error
Did you check some.
BTW thank a lot for the tech report, we will check it and let you know the results.

 

[RyanC17]

Found this article about the error
Did you check some.
BTW thank a lot for the tech report, we will check it and let you know the results.

I don't have flutter on my laptop.

 

[AnietieA]

Hello there, I'm also having this same issue. I recently upgraded to Big Sur and found out that some keyboard inputs on my Windows 10 guest OS wasn't working (e.g. when entering text). I looked up the keyboard issue and found some Parallels KB help articles that said configuring the guest OS keyboard settings would resolve the keyboard input problem. Doing this - by clicking on the Parallels "configure" button (on the settings menu) doesn't bring up any configuration menu, instead, it hangs the application.

 

[Maria@Parallels]

Hello there, I'm also having this same issue. I recently upgraded to Big Sur and found out that some keyboard inputs on my Windows 10 guest OS wasn't working (e.g. when entering text). I looked up the keyboard issue and found some Parallels KB help articles that said configuring the guest OS keyboard settings would resolve the keyboard input problem. Doing this - by clicking on the Parallels "configure" button (on the settings menu) doesn't bring up any configuration menu, instead, it hangs the application.

Hi, please check this KB article for more information about the Parallels Desktop and macOS 11 Big Sur known issues and try a workaround for your keyboard issue.

 

[jvh]

I have the same freezing issue ...

Date/Time: 2020-08-06 21:40:55.659 +0200
End time: 2020-08-06 21:41:37.813 +0200
OS Version: macOS 11.0 (Build 20A5343i)
Architecture: x86_64h
Report Version: 31
Share With Devs: Yes

Data Source: Stackshots
Shared Cache: 36720154-4F7E-347D-B1B7-8B73655104A2 slid base address 0x7fff206b0000, slide 0x6b0000

Command: prl_client_app
Path: /Applications/Parallels Desktop.app/Contents/MacOS/prl_client_app
Identifier: com.parallels.desktop.appstore
Version: 1.5.0 (20116)
Build Version: 1.5.20116.0
Project Name: Parallels
Source Version: 20116.0
App Item ID: 1085114709
App External ID: 833768849
Parent: launchd [1]
PID: 5753
Time Since Fork: 293s

Event: hang
Duration: 42.15s
Duration Sampled: 5.00s (process was unresponsive for 37 seconds before sampling)
Steps: 50 (100ms sampling interval)
Report threshold: 2.5s

Hardware model: Macmini8,1
Active cpus: 12
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Time Awake Since Boot: 6248s


--------------------------------------------------
Timeline format: stacks are sorted chronologically
Use -i and -heavy to re-report with count sorting
--------------------------------------------------


Heaviest stack for the main thread of the target process:
50 start + 1 (libdyld.dylib + 88145) [0x7fff685e7851]
50 ??? (prl_client_app + 643129) [0x10674d039]
50 QCoreApplication::exec() + 130 (QtCore + 2004226) [0x10cf05502]
50 QEventLoop::exec(QFlags<QEventLoop:rocessEventsFlag>) + 431 (QtCore + 1983903) [0x10cf0059f]
50 ??? (libqcocoa.dylib + 212715) [0x111668eeb]
50 -[NSApplication run] + 586 (AppKit + 193530) [0x7fff240f73fa]
50 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352 (AppKit + 249609) [0x7fff24104f09]
50 _DPSNextEvent + 877 (AppKit + 255707) [0x7fff241066db]
50 _BlockUntilNextEventMatchingListInModeWithFilter + 64 (HIToolbox + 204015) [0x7fff25bc7cef]
50 ReceiveNextEventCommon + 709 (HIToolbox + 204748) [0x7fff25bc7fcc]
50 RunCurrentEventLoopInMode + 292 (HIToolbox + 205264) [0x7fff25bc81d0]
50 CFRunLoopRunSpecific + 563 (CoreFoundation + 520500) [0x7fff27276134]
50 __CFRunLoopRun + 890 (CoreFoundation + 523159) [0x7fff27276b97]
50 __CFRunLoopDoSources0 + 248 (CoreFoundation + 528712) [0x7fff27278148]
50 __CFRunLoopDoSource0 + 180 (CoreFoundation + 529357) [0x7fff272783cd]
50 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 (CoreFoundation + 529509) [0x7fff27278465]
50 ??? (libqcocoa.dylib + 216967) [0x111669f87]
50 ??? (libqcocoa.dylib + 215049) [0x111669809]
50 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 878 (QtCore + 2007342) [0x10cf0612e]
50 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 240 (QtCore + 2002672) [0x10cf04ef0]
50 QApplication::notify(QObject*, QEvent*) + 594 (QtWidgets + 73858) [0x10b391082]
50 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 269 (QtWidgets + 68733) [0x10b38fc7d]
50 QObject::event(QEvent*) + 753 (QtCore + 2172929) [0x10cf2e801]
50 ??? (libPrlSdkCommunication.1.dylib + 34703) [0x108eeb78f]
50 ??? (libPrlSdkCommunication.1.dylib + 32066) [0x108eead42]
50 ??? (libPrlSdkCommunication.1.dylib + 32617) [0x108eeaf69]
50 CSdkCommunicator::handleJob(t_SdkHandleWrap<0>) + 230 (libPrlSdkCommunication.1.dylib + 29846) [0x108eea496]

 

[Shaunt3]

I have the same issue. Parallels Version 1.5.0 (20116) on Big Sur Beta 20A5343i.
Hangs on "configure" on any of the VMs, regardless of OS.