cancel
Showing results for 
Search instead for 
Did you mean: 
gouvinb
Stadia Player
Stadia Player

[Solved] Unable to start a session at the moment. - Failed to start the RTC client.

Jump to Best Response

Hi,

After having raised "Stadia" for quite a while, it is impossible for me to throw a game (in my case "Farcry 5").

I have tried a number of methods such as :

  • Deactivate my extensions
  • Go through the browser and not the WebApp created by Chrome

But not work.

Then I tried to reinstall Chrome, which had the effect of launching the game correctly but only on the first launch of Chrome.

The error message is :

Unable to start a session at the moment.
Failed to start the RTC client.

I tried all its manipulations with :

  • Stable Chrome
  • Chrome beta
  • Chromium

My config :

OS: Arch Linux x86_64
Host: ThinkPad T470s
Kernel: 5.10.6-arch1-1
Resolution: 1920x1080
WM: sway
CPU: Intel i7-7500U
GPU: Intel HD Graphics 620
Memory: 16GB

Logs :

 

 

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[1160305:1160305:0113/194640.271322:ERROR:vaapi_wrapper.cc(541)] vaInitialize failed: unknown libva error
[1160305:1160305:0113/194640.273999:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[1160328:15:0113/194645.149526:ERROR:webrtc_video_engine.cc(3308)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
[1160328:15:0113/194645.156382:ERROR:webrtc_video_engine.cc(3308)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
[1160328:15:0113/194645.157289:ERROR:webrtc_video_engine.cc(3308)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
[1160328:15:0113/194651.319166:ERROR:webrtc_video_engine.cc(3308)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
[1160328:15:0113/194651.321206:ERROR:webrtc_video_engine.cc(3308)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
[1160305:1160305:0113/194652.404503:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 1 times!
[1160305:1160305:0113/194652.405430:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 2 times!

 

 

Is there a solution for me? I haven't found a workaround for the moment, except reinstalling Chrome before each session.

I'm french and my english is bad, sorry.

OS: Arch Linux x86_64 - Host: ThinkPad T470s - Kernel: 5.10.6-arch1-1 - Resolution: 1920x1080 - WM: sway - CPU: Intel i7-7500U - GPU: Intel HD Graphics 620 - Memory: 16GB
1 Kudo
Best Response
Blackowl
Founder
Founder

I also run into this problem. Stadia will work as long as the extensions have been disabled. Try a factory reset of Chrome, then test each extension with Staida one by one. Hope this helps. 

View Best Response in original post

2 Kudos
gouvinb
Stadia Player
Stadia Player

Thank you when looking back at my extensions I noticed that 3 Google extensions were obsolete.

After having done the manipulations written below, I can finally play my games without reinstalling Chromium each time.

Here is what I did :

  • Noted all the extensions I have on my session
  • Uninstall them all without exception
  • Synchronize your account
  • Do a "factory reset" or a complete reinstallation of your browser (I tested only on Chromium)
  • Synchronize your account

From this point on I tested all my extensions one by one doing :

  • Launched one or more Stadia games to confirm that everything works.
  • Install an extension
  • Launched one or more Stadia games to confirm that everything is working well
  • Restart your browser
  • Launched one or more Stadia games in order to confirm that everything works with the installed extension.
  • If your games launch correctly, go to the next extension and repeat the operation
  • If your games don't launch anymore, uninstall your extension, synchronize your account and do a "factory reset" or a complete reinstallation of your browser before testing the next extension.

Thank's to @Blackowl 

OS: Arch Linux x86_64 - Host: ThinkPad T470s - Kernel: 5.10.6-arch1-1 - Resolution: 1920x1080 - WM: sway - CPU: Intel i7-7500U - GPU: Intel HD Graphics 620 - Memory: 16GB

View Best Response in original post

1 Kudo
13 Replies
HatDroid
Platinum Stadia Guide
Platinum Stadia Guide

Have you tried by any chance to run another game? 
Same result?

Also, if the other game starts, try to run again FarCry 5 after that.

0 Kudos
gouvinb
Stadia Player
Stadia Player

I just bought Doom 64 for testing, and it's exactly the same.

I should mention that I was able to play "Destiny 2" during the free month offered shortly after stadia was released to the general public and I had no problems at that time.

OS: Arch Linux x86_64 - Host: ThinkPad T470s - Kernel: 5.10.6-arch1-1 - Resolution: 1920x1080 - WM: sway - CPU: Intel i7-7500U - GPU: Intel HD Graphics 620 - Memory: 16GB
1 Kudo
HatDroid
Platinum Stadia Guide
Platinum Stadia Guide

Do you have the same issue on other devices too?

0 Kudos
gouvinb
Stadia Player
Stadia Player

Farcry 5 and Doom 64 works on my pixel 5.

I will try on VM with same configuration tomorrow.

OS: Arch Linux x86_64 - Host: ThinkPad T470s - Kernel: 5.10.6-arch1-1 - Resolution: 1920x1080 - WM: sway - CPU: Intel i7-7500U - GPU: Intel HD Graphics 620 - Memory: 16GB
0 Kudos
Reb00t
Stadia Player
Stadia Player

Im having the issue this morning.

Came home last night, DL the App. Signed up for trail.

I played Hit man, Monster jam and F!.

Awesome.

I Woke up and was going to buy BL 3 Ultimate and  today I cant get on any game.

:disappointed_face:

0 Kudos
HatDroid
Platinum Stadia Guide
Platinum Stadia Guide

Searched for the issue online, and it seems like an hardware accelleration settings that can fail on Arch linux, did you changed some system configuration that manage the Hardware acceleration? https://bbs.archlinux.org/viewtopic.php?id=244031

0 Kudos
gouvinb
Stadia Player
Stadia Player

I have indeed tried several configurations in connection with VA-API and Wayland, but I always find myself in the case where Stadia launches a game correctly only after a complete new installation of Chrome or Chromium. The second time I launch the browser, I always get this message with WebRTC.

OS: Arch Linux x86_64 - Host: ThinkPad T470s - Kernel: 5.10.6-arch1-1 - Resolution: 1920x1080 - WM: sway - CPU: Intel i7-7500U - GPU: Intel HD Graphics 620 - Memory: 16GB
0 Kudos
Blackowl
Founder
Founder

I also run into this problem. Stadia will work as long as the extensions have been disabled. Try a factory reset of Chrome, then test each extension with Staida one by one. Hope this helps. 

2 Kudos
gouvinb
Stadia Player
Stadia Player

Thank you when looking back at my extensions I noticed that 3 Google extensions were obsolete.

After having done the manipulations written below, I can finally play my games without reinstalling Chromium each time.

Here is what I did :

  • Noted all the extensions I have on my session
  • Uninstall them all without exception
  • Synchronize your account
  • Do a "factory reset" or a complete reinstallation of your browser (I tested only on Chromium)
  • Synchronize your account

From this point on I tested all my extensions one by one doing :

  • Launched one or more Stadia games to confirm that everything works.
  • Install an extension
  • Launched one or more Stadia games to confirm that everything is working well
  • Restart your browser
  • Launched one or more Stadia games in order to confirm that everything works with the installed extension.
  • If your games launch correctly, go to the next extension and repeat the operation
  • If your games don't launch anymore, uninstall your extension, synchronize your account and do a "factory reset" or a complete reinstallation of your browser before testing the next extension.

Thank's to @Blackowl 

OS: Arch Linux x86_64 - Host: ThinkPad T470s - Kernel: 5.10.6-arch1-1 - Resolution: 1920x1080 - WM: sway - CPU: Intel i7-7500U - GPU: Intel HD Graphics 620 - Memory: 16GB
1 Kudo
NeuroVX
Stadia Player
Stadia Player

Okay,

I checked under "chrome://flags"  then (this is the part you may miss- click at the right side top "unavailable" you might be surprised to see a few entries about "WebRTC hardware video decoding" and below it "WebRTC hardware video encoding"..

With the killer: "Not available on your platform." on the far right of this fun little page. This is with my current Windows Chrome. This was not a problem for me a short number of days ago. And it was working great!

Sorry to be conspiratorial, but the Chromium (open source Chrome) masters seem to be shutting down Chrome's hardware acceleration features for older chipset platforms like Intel 6th gen Skylake. Proof from chrome://gpu and I quote "

 Funny I used to decode hardware VP9 4k Youtube Stream without a hitch. How dare Google decide to degrade our experience because they think our hardware is too slow (when is isn't- at least not for what Stadia is throwing at us...

Extra for experts: figure out how to re enable webrtc video encode decode; and also accelerated vp9- and let's spead the news!! post solutions here:

RobertB. age 53, old as Yoda

 

         ps---Windows EDGE browser still at this writing works for STADIA- don't know how long it will last

          pps- get names and e-mail address of Stadia operations crew-- the may not know about these newly added limitations in Chrome!!                                        

 

0 Kudos
farfellow
Stadia Player
Stadia Player

for me it was a vpn plugin that solved my problems i also reset back to default

0 Kudos
RoolSands
Stadia Player
Stadia Player

The problem seems to be the WebRTC feature of the browser and if it's disabled or blocked. It is responsible for detecting you IP address so that a connection can be established. Often ad blocker, privacy tools and other security features (e.g. VPN) of browser extensions or on the operation system level (perhaps even Antivirus tools if they support anonymity features) are responsible for that.
See picture of an ad blocker tool that supports this feature:

RoolSands_0-1628340850280.png

2 Kudos
ibsphones
Community Member

Turned out to be my router Parental Control. 

0 Kudos