-
Notifications
You must be signed in to change notification settings - Fork 26
WebSocket connection issues #112
Comments
confirm |
This is a wild guess as I'm not able to inspect or test right now, but this change da32cbb#diff-06bb0d2b5cbd0f1dfbcaabf963cfa895R1363 doesn't feel right to me. I think Instead of deleting the entire |
@Eloston Thanks for the hint. I tried keeping I went trough the patch and tried to make some parts less invasive but didn't have any success. I noticed that a browser restart results in Discord loading successfully. It fails on subsequent page reloads though. |
With the safe browsing patch unapplied, does it fail on subsequent reloads too? Another thing that touches WebRTC is the VA-API patch. I don't know of any other patch that would remotely come close. |
@Eloston If only the safe browsing patch is not applied but the rest is applied then the subsequent reloads do work. I tried disabling VA-API at chrome://flags, it has no influence. |
@xsmile So do these tests fail for you?: https://www.websocket.org/echo.html |
Earlier I was confused with WebRTC, so we should make certain which one is actually broken. I thought Discord uses WebRTC for voice, but they could be using both technologies for a variety of things. WebRTC testing sites: |
WebSocket support is detected in all cases. with safebrowsing patchon browser restart on page reload without safebrowsing patchall tests pass I can't comment on WebRTC since I didn't (actively) use it yet and denied most permissions for audio/video access. WebRTC tests at https://test.webrtc.org/ fail with and without the patch, I guess that's fine. |
This is what I get in the console when trying to join a discord voice chat:
|
Closing, as this should be fixed in the next release. |
Source: hollunder at https://aur.archlinux.org/packages/inox-bin
I can confirm the issue when trying to use Discord at https://discordapp.com.
Discord connects fine if Inox is built with all patches except 0001-fix-building-without-safebrowsing.patch. but I don't know any details yet.
The text was updated successfully, but these errors were encountered: