1389339 - [webvr] "SharedSurfaceType::Basic not supported for WebVR" on Linux with openvr

Status: RESOLVED WONTFIX

(Core :: WebVR, defect, P2)

Description

[haagch+ff]

Attachment: Screenshot_20170811_021611.png

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0
Build ID: 20170808130316

Steps to reproduce:

Since I heard it should be working in nightly, this is supposedly a bug.

It happens on every WebVR site (samples on webvr.info, aframe.io) when trying to enter VR mode.

RX 480 with newest linux and mesa.
GPU #1
Active	Yes
Description	X.Org -- AMD Radeon (TM) RX 480 Graphics (POLARIS10 / DRM 3.18.0 / 4.13.0-rc2-gaee65f09d28b, LLVM 6.0.0)
Vendor ID	X.Org
Device ID	AMD Radeon (TM) RX 480 Graphics (POLARIS10 / DRM 3.18.0 / 4.13.0-rc2-gaee65f09d28b, LLVM 6.0.0)
Driver Version	3.0 Mesa 17.3.0-devel (git-d78b74b8dd)

Other steamvr vulkan and opengl applications work fine.


Actual results:

The SteamVR compositor doesn't receive any frames (shows the "loading" animation window), vrmonitor says firefox is unresponsive and firefox repeatedly spams this message to the console:
[GFX1]: SharedSurfaceType::Basic not supported for WebVR

As far as I remember this has always happened from the very first time I tried it shortly after the first SteamVR beta release in february.

Comment 1

[Daosheng Mu[:daoshengmu]]

We are still working on OpenVR Linux support at Bug 1310663.

Comment 2

[:kip (Kearwood Gilbert)]

I'll take this bug, as I'll also be fixing Bug 1310663 to bring up Linux support.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee didn't login in Bugzilla in the last 7 months.
:jimm, could you have a look please?
For more information, please visit auto_nag documentation.

Comment 4

[haagch+ff]

So what I wrote initially "Since I heard it should be working in nightly" was misinformation I got told somewhere, probably some social media.

When firefox started correctly reporting that on linux VR devices are not supported (probably ~4 years ago), this issue here could have been closed.

The real issue is that (other than the pre-e10 multiprocess webvr preview in 2015) proper webvr/webxr was never implemented on Linux, which would be Bug 1310663

kip, who is assigned, started working at Meta last year https://twitter.com/kearwoodgilbert/status/1457813969410789379. Mozilla should probably go through the bug tracker and assign all bugs from the people who were caught in the XR layoff to other developers.

Comment 5

[Daniel Adams[:msub2]]

(In reply to haagch+ff from comment #4)

kip, who is assigned, started working at Meta last year https://twitter.com/kearwoodgilbert/status/1457813969410789379. Mozilla should probably go through the bug tracker and assign all bugs from the people who were caught in the XR layoff to other developers.

While I'm inclined to agree, I don't think Mozilla has any other developers qualified to move all these bugs to. The vast majority of work here the past couple years was done by Kip, Imanol, and Daosheng Mu, none of whom are with Mozilla anymore. Unless Mozilla starts hiring again for XR positions or someone/multiple people from outside start making a push for it, I don't foresee much work being done in this module.