client and server both fedora f38. x2gokdriveclient-0.0.0.1-1.fc38.x86_64
I find that when connection gets interrupted 3 bad things can happen:
client uses 100% cpu
Trying to reconnect, screen starts to open and immediately closes. Then on next attempt a new session starts, old session is lost.
With client connected, closing laptop lid should initiate sleep. Instead client runs 100% cpu and machine doesn't sleep.
On 7/22/23 12:34, Neal Becker wrote:
client and server both fedora f38. x2gokdriveclient-0.0.0.1-1.fc38.x86_64
I find that when connection gets interrupted 3 bad things can happen:
client uses 100% cpu
Trying to reconnect, screen starts to open and immediately closes. Then on next attempt a new session starts, old session is lost.
With client connected, closing laptop lid should initiate sleep. Instead client runs 100% cpu and machine doesn't sleep.
We seem to be seeing #2 - not entirely sure if it's connected to a previous interruption.
How do we debug this so we can fix it?
-- Orion Poplawski IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 https://www.nwra.com/
-
Neal Becker -
Orion Poplawski