AvatarKava

"White screen of death" on initial setup on Win10

12 posts in this topic

Moved from Synergy 1.8 to another product, then purchased 2.0 once the stable release came out.

When starting up Synergy on my slave computer, I get a completely white window every time.  Assuming it might be a conflict with some old registry or config settings from 1.8, I followed the instructions for registry/ProgramData cleanup and reinstalled, but am still seeing the same behavior.

I'm assuming this may be a temporary downtime issue with the background server doing license/account checks, but I'm not positive.  Any ideas?

Screenshot and logs below.

Capture.PNG.8637f12f2aabb545b565ebeb1645388a.PNG

[ Service ] [2017-11-19T16:37:06] debug: service log path: C:\ProgramData\Symless\Synergy\synergy-service.log
[ Service ] [2017-11-19T16:37:06] debug: install dir: C:\Program Files\Synergy
[ Service ] [2017-11-19T16:37:06] info: starting service...
[ Service ] [2017-11-19T16:37:06] debug: creating rpc endpoints
[ Service ] [2017-11-19T16:37:06] debug: rpc endpoints created
[ Service ] [2017-11-19T16:37:09] debug: saying hello to config ui
[ Service ] [2017-11-19T16:37:09] debug: retrying websocket connection now
[ Service ] [2017-11-19T16:37:09] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-11-19T16:37:10] error: websocket handshake error 3: WebSocket Upgrade handshake failed
[ Service ] [2017-11-19T16:37:10] error: websocket handshake response 400: Bad Request
[ Service ] [2017-11-19T16:37:10] debug: clearing last profile snapshot
[ Service ] [2017-11-19T16:37:10] debug: retrying websocket connection in 14s
[ Service ] [2017-11-19T16:37:24] debug: retrying websocket connection now
[ Service ] [2017-11-19T16:37:24] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-11-19T16:37:24] error: websocket handshake error 3: WebSocket Upgrade handshake failed
[ Service ] [2017-11-19T16:37:24] error: websocket handshake response 400: Bad Request
[ Service ] [2017-11-19T16:37:24] debug: clearing last profile snapshot
[ Service ] [2017-11-19T16:37:24] debug: retrying websocket connection in 25s

Share this post


Link to post
Share on other sites

Hi,

same problem here, platform:

Arch linux - 4.13.12-1-ARCH #1 SMP PREEMPT Wed Nov 8 11:54:06 CET 2017 x86_64 GNU/Linux

synergy2 2.0.2.stable~b1046+665fa610-1

Untitled.jpg.7b8ff4ede7fe6d57ca99fb0692cfebff.jpg

 

journalctl

...
Nov 27 22:50:17 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:50:17] error: websocket handshake response 400: Bad Request
Nov 27 22:50:17 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:50:17] debug: clearing last profile snapshot
Nov 27 22:50:17 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:50:17] debug: retrying websocket connection in 25s
Nov 27 22:50:42 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:50:42] debug: retrying websocket connection now
Nov 27 22:50:42 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:50:42] debug: connecting websocket: pubsub1.cloud.symless.com:443
Nov 27 22:50:42 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:50:42] error: websocket handshake error 3: WebSocket Upgrade handshake failed
Nov 27 22:50:42 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:50:42] error: websocket handshake response 400: Bad Request
Nov 27 22:50:42 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:50:42] debug: clearing last profile snapshot
Nov 27 22:50:42 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:50:42] debug: retrying websocket connection in 27s
Nov 27 22:51:09 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:51:09] debug: retrying websocket connection now
Nov 27 22:51:09 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:51:09] debug: connecting websocket: pubsub1.cloud.symless.com:443
Nov 27 22:51:09 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:51:09] error: websocket handshake error 3: WebSocket Upgrade handshake failed
...

 

synergy-config  starting

"[ Config  ] " "[2017-11-27T23:00:05] debug: install dir: /usr/bin" 
"[ Config  ] " "[2017-11-27T23:00:05] info: log filename: /var/log/synergy/synergy-combined.log" 
QObject::startTimer: Timers cannot have negative intervals
"[ Config  ] " "[2017-11-27T23:00:05] debug: connecting to background service" 
"[ Config  ] " "[2017-11-27T23:00:05] debug: connected to background service" 
"[ Config  ] " "[2017-11-27T23:00:05] debug: sending uid to service: 1000" 
"[ Config  ] " "[2017-11-27T23:00:05] debug: saying hello to background service" 
qrc:/ActivationPage.qml:65:21: QML Image: Binding loop detected for property "sourceSize.height"
qrc:/ActivationPage.qml:65:21: QML Image: Error decoding: qrc:/res/image/symless-signin-button.svg: Unsupported image format
"" "[ Service ] [2017-11-27T23:00:05] debug: setting core uid from rpc: 1000" 
"" "[ Service ] [2017-11-27T23:00:05] debug: saying hello to config ui" 
"[ Config  ] " "[2017-11-27T23:00:05] debug: service cloud connection error" 
"" "[ Service ] [2017-11-27T23:00:05] debug: retrying websocket connection now" 
"" "[ Service ] [2017-11-27T23:00:05] debug: connecting websocket: pubsub1.cloud.symless.com:443" 
"" "[ Service ] [2017-11-27T23:00:05] error: websocket handshake error 3: WebSocket Upgrade handshake failed" 
"" "[ Service ] [2017-11-27T23:00:05] error: websocket handshake response 400: Bad Request" 
"" "[ Service ] [2017-11-27T23:00:05] debug: clearing last profile snapshot" 
"[ Config  ] " "[2017-11-27T23:00:05] debug: service cloud connection error" 
"" "[ Service ] [2017-11-27T23:00:05] debug: retrying websocket connection in 12s" 
"[ Config  ] " "[2017-11-27T23:00:05] debug: current version is update to date" 
"[ Config  ] " "[2017-11-27T23:00:05] debug: current version is update to date" 

 

 

Share this post


Link to post
Share on other sites

This is most likely to be an outage with the cloud service.

The symless team are working hard to improve the resiliency of this, so please be patient.

 

In the meantime, I believe it's all working now - can you try again?

Share this post


Link to post
Share on other sites

tested again, still not connecting

"" "[ Service ] [2017-11-28T19:22:13] debug: retrying websocket connection now" 
"" "[ Service ] [2017-11-28T19:22:13] debug: connecting websocket: pubsub1.cloud.symless.com:443" 
"" "[ Service ] [2017-11-28T19:22:14] error: websocket handshake error 3: WebSocket Upgrade handshake failed" 
"" "[ Service ] [2017-11-28T19:22:14] error: websocket handshake response 400: Bad Request" 
"" "[ Service ] [2017-11-28T19:22:14] debug: clearing last profile snapshot" 
"[ Config  ] " "[2017-11-28T19:22:14] debug: service cloud connection error" 
"" "[ Service ] [2017-11-28T19:22:14] debug: retrying websocket connection in 23s" 

 

Share this post


Link to post
Share on other sites

I'm getting the same error in the logs, but with a retry message to connect to the auto-config service. My first PC is working fine, but the second is getting this issue, so doesn't seem to be the cloud service being down.

Share this post


Link to post
Share on other sites

Same here.. I get the retry message, but the logs consistently show 

[ Service ] [2017-12-01T14:39:18] debug: retrying websocket connection now
[ Service ] [2017-12-01T14:39:18] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-12-01T14:39:19] error: websocket handshake error 3: WebSocket Upgrade handshake failed
[ Service ] [2017-12-01T14:39:19] error: websocket handshake response 400: Bad Request
[ Service ] [2017-12-01T14:39:19] debug: clearing last profile snapshot
[ Service ] [2017-12-01T14:39:19] debug: retrying websocket connection in 24s

I have re-installed multiple times, but still no dice. There must be some Windows setting that's causing this, because it works fine between my MacBook and my media PC.

Edited by Barron

Share this post


Link to post
Share on other sites

If your window is entirely white, try this:

1. Hit Win+R, type "sysdm.cpl" and press enter : it should open the system properties dialog
2. At the bottom right of this window, click on the "Environmental Variables"
3. Click on the first/top "New" button (under the "User variables for <your_user_name_here>" category)
4. Enter this parameters (without quotes):
  - Name:  "QMLSCENE_DEVICE"
  - Value: "softwarecontext"
5. Ok, save, apply, whatever...
6. Reboot and retry

If your problem is fixed, it means that you have issues with your graphics driver.
I'd recommend you to delete the QMLSCENE_DEVICE variable you just added and fix your graphics driver issue.

Share this post


Link to post
Share on other sites
9 hours ago, Nicnl said:

If your window is entirely white, try this:

1. Hit Win+R, type "sysdm.cpl" and press enter : it should open the system properties dialog
2. At the bottom right of this window, click on the "Environmental Variables"
3. Click on the first/top "New" button (under the "User variables for <your_user_name_here>" category)
4. Enter this parameters (without quotes):
  - Name:  "QMLSCENE_DEVICE"
  - Value: "softwarecontext"
5. Ok, save, apply, whatever...
6. Reboot and retry

If your problem is fixed, it means that you have issues with your graphics driver.
I'd recommend you to delete the QMLSCENE_DEVICE variable you just added and fix your graphics driver issue.

I'll give this a shot, I'm a little sketchy about upgrading my current Intel 530 driver, as I use a quad monitor setup and everything is working smoothly, including video playback. Lenovo t460p. Other versions of the driver always have issues with the stuttering video playback, etc, while I have 4 monitors hooked up. Thank you for the time. :)

Edited by dasunsrule32

Share this post


Link to post
Share on other sites

Ok, so the app is working now, but I'm getting the following error:

[ Service ] [2017-12-08T10:08:03] debug: retrying websocket connection now
[ Service ] [2017-12-08T10:08:03] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-12-08T10:08:04] error: websocket handshake error 3: WebSocket Upgrade handshake failed
[ Service ] [2017-12-08T10:08:04] error: websocket handshake response 400: Bad Request
[ Service ] [2017-12-08T10:08:04] debug: clearing last profile snapshot
[ Config  ] [2017-12-08T10:08:04] debug: service cloud connection error
[ Service ] [2017-12-08T10:08:04] debug: retrying websocket connection in 17s

It works on my Desktop, but not my laptop.

Edited by dasunsrule32

Share this post


Link to post
Share on other sites

Nice to hear that the problem is fixed.

Basically it forces all Qt apps (the "programming tool" that was used to create Synergy, to put it simply) to do all graphics rendering using your CPU and not your GPU.

The issue is that this setting is now applied to all Qt apps.
Sadly, I don't really know if there's a lot of graphic intensive apps that uses Qt.

I think you can set this environmental variable just for this app by right clicking synergy-config.exe, sending it to the desktop and editing the shortcut with right click > properties.

 

Concerning your other issue (pubsub1.cloud.symless.com) there's nothing to do.
Symless seems to have a lot of issues with their servers and it impacts everyone.

Share this post


Link to post
Share on other sites
11 minutes ago, Nicnl said:

Nice to hear that the problem is fixed.

Basically it forces all Qt apps (the "programming tool" that was used to create Synergy, to put it simply) to do all graphics rendering using your CPU and not your GPU.

The issue is that this setting is now applied to all Qt apps.
Sadly, I don't really know if there's a lot of graphic intensive apps that uses Qt.

I think you can set this environmental variable just for this app by right clicking synergy-config.exe, sending it to the desktop and editing the shortcut with right click > properties.

 

Concerning your other issue (pubsub1.cloud.symless.com) there's nothing to do.
Symless seems to have a lot of issues with their servers and it impacts everyone.

Yay, lovely. Does an older version of the client work, 2.0.1 for example?

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now