Black Screen on Primary When Secondary Returning from Sleep (KVM mode)

from Stardock Forums

In KVM mode, whenever my secondary machine wakes from sleep, I only get a black screen on my primary machine when I reconnect to the secondary.

Mouse and keyboard inputs work fine, I can type on the primary and see it show up on the secondary, but the display on the primary just stays black.

The only thing that fixes this is restarting the secondary machine.

I've tried unloading and restarting only Multiplicity on both machines to fix it, but that doesn't change anything.

The only thing that seems to work is rebooting the secondary.

Any ideas?

multiplicity
3,654 views 3 replies
Reply #1 from Stardock Forums Top

I have an update if it's helpful.

It looks like unloading Multiplicity on the secondary machine didn't actually kill the core multiplicity process. So I killed that manually and now the image shows up on the primary.

But the performance is super degraded compared to the usual. The interface lag is huge compared to before, switching from fullscreen to windowed mode also lags even though that should be just running locally I thought, and minimizing the resulting window blacks my entire screen out for a few seconds before it minimizes.

Reply #2 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. Have you tried looking into this two thread?

Black Screen on Secondary:

Taken from Multiplicity Support FAQ: https://forums.stardock.com/486104/multiplicity-support-faq

Thank you,

Basj,
Stardock Community Assistant.

Galactic Civilizations IV
Reply #3 from Stardock Forums Top

Hi, yeah, I've read through those posts and they don't seem to apply here. At least, the suggestions either don't help, or don't apply (it's between two laptops, so not headless, etc).

 

Rebooting the primary fixes the performance lag though. Consistently.

 

But then sometimes the primary gets into some state again where performance goes really bad. Restarting Multiplicity doesn't fix it, only restarting the PC.

 

Is there something else I could manually restart on the Primary to fix the performance besides multiplicity itself?