Linux client lockup and disconnect with "FIXME" logs

[Brent Harsh 1]

After some struggles, I did get 1.7.4 installed on a Win64 (Server) and Ubuntu (client) this afternoon. It's nice to have this working again. I haven't yet taken the time to try to get the client side automated so things run on startup; just wanted to see if 1.7.4 was really stable first. It stayed up for 7 hours; but when I came back to the system after an hour break or so and moved the mouse, I saw the client suddenly disconnect: ``` [2015-08-11T20:18:32] INFO: screen "Supermicro" updated clipboard 0 [2015-08-11T21:21:24] INFO: switch from "ubu1" to "Supermicro" at 30,437 [2015-08-11T21:21:24] INFO: entering screen [2015-08-11T21:21:33] NOTE: client "ubu1" has disconnected [2015-08-11T21:31:53] INFO: watchdog status: ok [2015-08-11T22:56:01] NOTE: accepted client connection [2015-08-11T22:56:01] INFO: accepted secure socket [2015-08-11T22:56:02] NOTE: client "ubu1" has connected ``` Looking on the Ubuntu machine, the process was still up and the following logs were showing - not sure if the FIXME notes are important or if there's a better way to get them to someone who would be interested, but figured I'd send them along. I just killed and restarted the client process and it seems to be back again. ``` bharsh@ubu1:~$ synergy "sni-qt/32184" WARN 13:23:57.106 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE Got bus address: "unix:abstract=/tmp/dbus-3bMIAmU0bb,guid=2491a8e49360804dcf9b688655ca2fad" Connected to accessibility bus at: "unix:abstract=/tmp/dbus-3bMIAmU0bb,guid=2491a8e49360804dcf9b688655ca2fad" Registered DEC: true Registered event listener change listener: true QDBusConnection: name 'org.a11y.atspi.Registry' had owner '' but we thought it was ':1.1' "http://synergy-project.org/files/plugins/ns/1.3/Linux-x86_64-deb/libns.so" QObject: Cannot create children for a parent that is in a different thread. (Parent is QNetworkAccessManager(0x1d5bee0), parent's thread is QThread(0x1aad5d0), current thread is QThread(0x1c14f20) FIXME: handle dialog end. ("-f", "--no-tray", "--debug", "DEBUG2", "--name", "ubu1", "--enable-crypto", "192.168.3.101:24800") QSpiAccessible::accessibleEvent not handled: "2" obj: QMessageBox(0x7ffe25434490) "" FIXME: handle dialog start. FIXME: handle dialog end. ("-f", "--no-tray", "--debug", "DEBUG2", "--name", "ubu1", "--enable-crypto", "192.168.3.101:24800") ^C Next run (still going): bharsh@ubu1:~$ synergy "sni-qt/6780" WARN 22:56:15.386 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE Got bus address: "unix:abstract=/tmp/dbus-3bMIAmU0bb,guid=2491a8e49360804dcf9b688655ca2fad" Connected to accessibility bus at: "unix:abstract=/tmp/dbus-3bMIAmU0bb,guid=2491a8e49360804dcf9b688655ca2fad" Registered DEC: true ("-f", "--no-tray", "--debug", "DEBUG2", "--name", "ubu1", "--enable-crypto", "192.168.3.101:24800") Registered event listener change listener: true ```

[Ben Koenig 1]

I would guess this is caused by some sort of network glitch. Either thirdparty software competing for the connection or something with the network itself, e.g wifi or otherwise intermittent. Is there anything else that you think would be relevant? Maybe a program running on a schedule at the time of disconnection.