You must be logged in to use the forums. Don't have an account? Sign up for free.
Remember me
Snoobster
#0 September 26th, 11:08

"Starting windows...."

After quite a few infinite loading screens, i managed to connect to my cloud rig. However, now that i'm in, i'm stuck in the "Starting windows..." loading screen, whenever i try to start windows. I have no idea what to do. I've tried to restart the client and to put it fullscreen, changes nothing. I'm using Arch Linux, and i use chrome version 61. I noticed a similar thread: https://www.snoost.com/fr/community/guides/linux-user/ , which is also by a Linux user, so maybe this a Linux-specific problem (but maybe not). I hope i manage to try the service before the end of my trial period

Showing 1-9 of 9 comments
Staff
#1 September 26th, 11:13
Is the screen black, or does it keep showing the "Starting Windows" message? If the screen is just black, sometimes it can be because it's still loading and you may just need to wait a little bit and perhaps click the mouse after a few seconds to keep it active.

We are working to make the startup of Windows on Linux more seamless and smooth, but will do our best to guide you towards a temporary solution until it's more stable.

Snoobster
#2 September 26th, 11:16
No it keeps showing the "Starting Windows" message.

Snoobster
#3 September 26th, 11:19
I also noticed that when it is already in fullscreen it keeps loading, but if i click on the windows icon while the client is not in fullscresen, it goes in fullscreen for a few seconds, then it leaves fullscreen, stops loading, and goes back to the menu with the windows icon.

Staff
#4 September 26th, 11:19
Hmm okay. Thanks for the details. I hope we'll get to the bottom of this. :)

Here's what you could try:

  • exit out (alt+ctrl+q)
  • "Force-quit Windows" (and maybe also "Re-scan system" right after) to the left of the Snoost Window
  • Open Windows again
Snoobster
#5 September 26th, 11:25
I tried to re-scan and force quit windows, in any order possible, changes nothing. However, the command "alt+ctrl+q" does not work (nor "alt+shift+q"), is it normal? I usually leave the client by simply closing the window it's in.

Snoobster
#6 September 26th, 11:26
Oh wait it works in the loading screen, it juste doesn't work in the menu (with the windows icon). Duh! But the problem is still there.

Edit: i meant the shortcut for quitting works in the loading screen, but it still doesn't load.

Last edited: September 26th, 11:30

Staff
#7 September 26th, 11:49
Alright, it sounds like it could be an issue with the Linux distribution, which we will then have to address as soon as we can. Snoost has been tested on a variety of Linux versions, so I'm a bit surprised to see it fail here.

Nevertheless, this has already landed on the developer desk and we are digging into the code at this very moment. Please let us know if you discover any other findings which may help the troubleshooting/debugging - Thanks for letting us know about the problem, and for the information related to the issue so far! :)

Snoobster
#8 September 26th, 11:58
Thank you for the answer. I will try to see if i can try with another distribution in the meantime, maybe a bootable key. Note that i am sure this is not desktop-specific: i tried all this with several desktops (i3, openbox, gnome). But it might be because of the distrib.

Snoobster
#9 September 26th, 12:01
I didn't think about providing it before, but here is the console output of me launching chrome, connecting to snoost, and attempting to connect to windows in my cloud rig (the server was already started). Here goes:

[5379:5415:0926/115102.819507:ERROR:service_manager.cc(156)] Connection InterfaceProviderSpec prevented service: content_browser from binding interface: content::mojom::Child exposed by: nacl_loader [3,1701234752:09:51:02.827996] Native Client module will be loaded at base address 0x00005bfd00000000

  • timeout on name lookup is not supported
  • Hostname was NOT found in DNS cache
  • Trying 54.229.59.9...
  • Connected to ec2-54-229-59-9.eu-west-1.compute.amazonaws.com (54.229.59.9) port 47984 (#0)
  • libcurl is now using a weak random seed!
  • SSL connection using TLSv1.2 / AES256-GCM-SHA384
  • Server certificate:
  • subject: CN=NVIDIA GameStream Server
  • start date: 2017-04-15 11:57:28 GMT
  • expire date: 2037-04-15 11:57:28 GMT
  • issuer: CN=NVIDIA GameStream Server
  • SSL certificate verify result: self signed certificate (18), continuing anyway. > GET /serverinfo?uniqueid=b2c66ca5289c1ba7&uuid=987cba9c-4fa2-4636-afdc-c87dc8e491b9 HTTP/1.1 Host: ec2-54-229-59-9.eu-west-1.compute.amazonaws.com:47984 Accept: /
< HTTP/1.1 200 OK < Content-Type: text/plain < Content-Length: 924 <

  • Closing connection 0
  • timeout on name lookup is not supported
  • Hostname was NOT found in DNS cache
  • Trying 54.229.59.9...
  • Connected to ec2-54-229-59-9.eu-west-1.compute.amazonaws.com (54.229.59.9) port 47984 (#1)
  • SSL connection using TLSv1.2 / AES256-GCM-SHA384
  • Server certificate:
  • subject: CN=NVIDIA GameStream Server
  • start date: 2017-04-15 11:57:28 GMT
  • expire date: 2037-04-15 11:57:28 GMT
  • issuer: CN=NVIDIA GameStream Server
  • SSL certificate verify result: self signed certificate (18), continuing anyway. > GET /applist?uniqueid=b2c66ca5289c1ba7&uuid=cd348b46-d83c-44fe-a8b3-7c11e935c041 HTTP/1.1 Host: ec2-54-229-59-9.eu-west-1.compute.amazonaws.com:47984 Accept: /
< HTTP/1.1 200 OK < Content-Type: text/plain < Content-Length: 431 <

  • Closing connection 1
  • timeout on name lookup is not supported
  • Hostname was NOT found in DNS cache
  • Trying 54.229.59.9...
  • Connected to ec2-54-229-59-9.eu-west-1.compute.amazonaws.com (54.229.59.9) port 47984 (#2)
  • SSL connection using TLSv1.2 / AES256-GCM-SHA384
  • Server certificate:
  • subject: CN=NVIDIA GameStream Server
  • start date: 2017-04-15 11:57:28 GMT
  • expire date: 2037-04-15 11:57:28 GMT
  • issuer: CN=NVIDIA GameStream Server
  • SSL certificate verify result: self signed certificate (18), continuing anyway. > GET /serverinfo?uniqueid=b2c66ca5289c1ba7&uuid=eb617919-c9aa-4c2f-9172-ad07be424e2c HTTP/1.1 Host: ec2-54-229-59-9.eu-west-1.compute.amazonaws.com:47984 Accept: /
< HTTP/1.1 200 OK < Content-Type: text/plain < Content-Length: 924 <

  • Closing connection 2
  • timeout on name lookup is not supported
  • Hostname was NOT found in DNS cache
  • Trying 54.229.59.9...
  • Connected to ec2-54-229-59-9.eu-west-1.compute.amazonaws.com (54.229.59.9) port 47984 (#3)
  • SSL connection using TLSv1.2 / AES256-GCM-SHA384
  • Server certificate:
  • subject: CN=NVIDIA GameStream Server
  • start date: 2017-04-15 11:57:28 GMT
  • expire date: 2037-04-15 11:57:28 GMT
  • issuer: CN=NVIDIA GameStream Server
  • SSL certificate verify result: self signed certificate (18), continuing anyway. > GET /applist?uniqueid=b2c66ca5289c1ba7&uuid=b6cb1717-a882-4b1d-aad4-f0365a27d4b6 HTTP/1.1 Host: ec2-54-229-59-9.eu-west-1.compute.amazonaws.com:47984 Accept: /
< HTTP/1.1 200 OK < Content-Type: text/plain < Content-Length: 431 <

  • Closing connection 3
  • timeout on name lookup is not supported
  • Hostname was NOT found in DNS cache
  • Trying 54.229.59.9...
  • Connected to ec2-54-229-59-9.eu-west-1.compute.amazonaws.com (54.229.59.9) port 47984 (#4)
  • SSL connection using TLSv1.2 / AES256-GCM-SHA384
  • Server certificate:
  • subject: CN=NVIDIA GameStream Server
  • start date: 2017-04-15 11:57:28 GMT
  • expire date: 2037-04-15 11:57:28 GMT
  • issuer: CN=NVIDIA GameStream Server
  • SSL certificate verify result: self signed certificate (18), continuing anyway. > GET /resume?uniqueid=b2c66ca5289c1ba7&uuid=6dd66ae7-c801-42a0-9a68-555f3af9137a&rikey=b26b7279d0ad119d00d22154c04e029b&rikeyid=-614150453 HTTP/1.1 Host: ec2-54-229-59-9.eu-west-1.compute.amazonaws.com:47984 Accept: /
< HTTP/1.1 200 OK < Content-Type: text/plain < Content-Length: 574 <

  • Closing connection 4 [0926/095117.224770:WARNING:ipc_message_attachment_set.cc(49)] MessageAttachmentSet destroyed with unconsumed attachments: 0/1
  • timeout on name lookup is not supported
  • Hostname was NOT found in DNS cache
  • Trying 54.229.59.9...
  • Connected to ec2-54-229-59-9.eu-west-1.compute.amazonaws.com (54.229.59.9) port 47984 (#5)
  • SSL connection using TLSv1.2 / AES256-GCM-SHA384
  • Server certificate:
  • subject: CN=NVIDIA GameStream Server
  • start date: 2017-04-15 11:57:28 GMT
  • expire date: 2037-04-15 11:57:28 GMT
  • issuer: CN=NVIDIA GameStream Server
  • SSL certificate verify result: self signed certificate (18), continuing anyway. > GET /serverinfo?uniqueid=b2c66ca5289c1ba7&uuid=ae02e650-f0fd-4614-a26f-15ceb97f531b HTTP/1.1 Host: ec2-54-229-59-9.eu-west-1.compute.amazonaws.com:47984 Accept: /
< HTTP/1.1 200 OK < Content-Type: text/plain < Content-Length: 924 <

  • Closing connection 5
  • timeout on name lookup is not supported
  • Hostname was NOT found in DNS cache
  • Trying 54.229.59.9...
  • Connected to ec2-54-229-59-9.eu-west-1.compute.amazonaws.com (54.229.59.9) port 47984 (#6)
  • SSL connection using TLSv1.2 / AES256-GCM-SHA384
  • Server certificate:
  • subject: CN=NVIDIA GameStream Server
  • start date: 2017-04-15 11:57:28 GMT
  • expire date: 2037-04-15 11:57:28 GMT
  • issuer: CN=NVIDIA GameStream Server
  • SSL certificate verify result: self signed certificate (18), continuing anyway. > GET /applist?uniqueid=b2c66ca5289c1ba7&uuid=075081cf-a20e-45f0-b100-8cf9bc97e750 HTTP/1.1 Host: ec2-54-229-59-9.eu-west-1.compute.amazonaws.com:47984 Accept: /
< HTTP/1.1 200 OK < Content-Type: text/plain < Content-Length: 431 <

  • Closing connection 6
  • timeout on name lookup is not supported
  • Hostname was NOT found in DNS cache
  • Trying 54.229.59.9...
  • Connected to ec2-54-229-59-9.eu-west-1.compute.amazonaws.com (54.229.59.9) port 47984 (#7)
  • SSL connection using TLSv1.2 / AES256-GCM-SHA384
  • Server certificate:
  • subject: CN=NVIDIA GameStream Server
  • start date: 2017-04-15 11:57:28 GMT
  • expire date: 2037-04-15 11:57:28 GMT
  • issuer: CN=NVIDIA GameStream Server
  • SSL certificate verify result: self signed certificate (18), continuing anyway. > GET /applist?uniqueid=b2c66ca5289c1ba7&uuid=ac1bf127-c1f6-4ead-9d66-20608dabf332 HTTP/1.1 Host: ec2-54-229-59-9.eu-west-1.compute.amazonaws.com:47984 Accept: /
< HTTP/1.1 200 OK < Content-Type: text/plain < Content-Length: 431 <

  • Closing connection 7
Showing 1-9 of 9 comments