support

Forum Navigation
Please or Register to create posts and topics.

[SOLVED] Help – Nothing works any more since 2.1.31

PreviousPage 2 of 2

Hi Nicole,

For your #2 and #3 This is what I did right before my last post. Notice though that #3 is nothing more than waking them up. Thus, no explicit disconnect beforehand.  The -1 for both parameters was already applied earlier.

Currently, something like 10 hours later (see time of my previous post) it is the first time all is still normal. It may not tell all as I feel it is also related to other environmental stuff. Example : a tablet may go Off for real, like when the battery is empty. This did not happen in these past 10 hours.
What also may influence is that a tablet may receive a(n unavoidable) Notification. I can hear those at the distance of where they reside, and may see a flicker on my normal monitors. Thus, this is when they wake up briefly. Please note : I am not saying that it happens right there that they disconnect from Spacedesk, but it is a “happening” that Spacedesk is aware of and it may go wrong at times.

Otherwise it may happen (that all goes wrong) exactly at the point that I may click on the desktop of my main screen, e.g. on an icon residing there. Thus say I am sitting there doing nothing (but am on the telephone) and then after 20 minutes (etc.) I click – and boom. This really is no coincidence. And a possible important data point could be : in all occasions that it happens, the normal monitors all go blank for 3-5 seconds. Thus, as if they are off. Another exhibit in other occasions would be that only the wallpaper(s) disappear for these 3-5 seconds. This is all a harder reset, with the main exhibit that an RDC session with a (virtual) monitor spread over two physical monitors, shrink back to the one main monitor.
This latter is not equal to soft powering off  the normally connected monitors(by means of their physical buttons) because in that case all remains in-tact. But it would be equal to disconnecting the power cord, or unplugging them from the video card. Thus this is how I say : a harder reset (implied by Spacedesk).

On your questions :

All connected viewers (5,6,7) are wirelessly connected only. One of them (5) is not set to its native resolution.

I don’t know what “extended mode” is.

The Windows machine never goes to sleep. Also not for their physically connected monitors. The Windows machine normally runs for months in a row (is never off).

The new thing since any of the earlier events could be that I now turned Off and On the Spacedesk driver, since all was a mess again anyway. This was also the first time I did this, when both parameters were at -1 already. So if all stays fine this time, that “workflow” will surely be related. In the end this is (very close to) what you advised in your last post …

Uploaded files:
  • You need to login to have access to uploads.

Hi @peterst2,

For further analysis of the issue, please send us the logs of your Windows machine. Follow the steps below:

  1. Open spacedesk Driver console.
  2. Click on Diagnostics.
  3. Download the DebugView.
  4. Check the Diagnostic Collection box.
  5. Reproduce the issue you encountered.
  6. Uncheck the Diagnostic Collection box.
  7. Click “Save All Information” button (this might take a while to finish).
  8. Compress/Zip the folder which contains the logs, then attach to your next reply to this post. If it exceeds the maximum allowed file size, upload it to Dropbox/Google Drive/etc. and send us the link.

Not a single glitch seen the past 24 hours …

So :
Connection Loss Delay must be at infinite / -1 now (this was not so).
Connection Close Delay must also be at infinite / -1 (this was already so).

At re-initiating this, the Driver must (obviously) be set to Off (at the Driver Console). Then switch back On.

Thank you for your help, @spacedesk_nicole.

Regards,
Peter

spacedesk Nicole has reacted to this post.
spacedesk Nicole
PreviousPage 2 of 2