ncbrowns

@iluvtoflytoo: Your issue appears to be completely unrelated to the issue reported by the original poster. That said, what you describe sounds similar to a problem I had back in 2015. The reply I got to my support ticket pasted below solved my problem. I'm not sure if this was a firewall issue or Multiplicity has security logic to disable itself on "Public" networks. In any event, I hope that this helps. <span style="font-family: Verdana, Arial, Helveti

I did an experiment when I removed the extra secondary system from the desktop configuration on the secondary, so that I only had my (two-monitor) primary system plus a single (one-monitor) secondary. That had no effect. Also, disabling one of the two monitors on my primary system had no effect.

@Neil, reply #8: Secondary system has a Intel core i7-4770 (4 physical cores) with an NVIDIA GeForce RTX 2080. Not sure if there are any other details you're interested in. @Sean, reply #9: Sleep on the secondary system of concern is set to 3 hours and is unlikely to be relevant. I actually have two secondary systems, but the other one is powered off/sleeping during this repro. (It's a secondary test system that I only use when trying to do too many thi

My problem appears to have returned this morning, immediately after the new cumulative update KB4517389 was applied to my system, which probably brought back whatever part of KB4515384. Both my primary and secondary system are now updated with the latest patches. Here's a detailed description of what's happening to me, and hopefully how to reproduce the problem: On the secondary, set the power settings to turn off the screen after 1 minute of inactivity (I usually

Update: I had previously backed out KB4515384 on my primary because of the Start Menu search bug, but it was still installed on my secondary. Since backing it out on the secondary yesterday, I have had no disconnects. The only issue I still have occurs when the secondary has been inactive long enough for the monitor to shut off. In this case, when I drag my mouse to the secondary, there are several seconds of latency where the mouse is non-responsive. Even if I

I've been seeing something similar recently, though I haven't specifically tied it to KB4515384 yet. (I was affected by the start menu search failure on my primary.) I'll try rolling it back on my secondary to see if it helps. My disconnects feel like they might be tied to the screensaver kicking in, though it typically recovers eventually.

I'm a relatively new Multiplicity user, and am configuring it to have a hotkey switch back to the primary. I often use Multiplicity on a setup where my secondaries have a kernel debugger that breaks in some time. I've configured Multiplicity to use the same hotkey I used in a different virtual KVM system (Ctrl-Shift-Alt-Insert) so I don't have to wait on a timeout to switch back to the primary. The problem that I'm seeing is that the hotkey is firing when i

I attempted to download via the the Start8 configuration screen, via the "Check for update..." link on the "About" tab. Clicking it produces a dialog saying "No updates for Start8 have been found". Bug?