Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Audio renderer error, please restart your computer #158

Closed
marknefedov opened this issue Oct 5, 2021 · 12 comments
Closed

Audio renderer error, please restart your computer #158

marknefedov opened this issue Oct 5, 2021 · 12 comments

Comments

@marknefedov
Copy link

Chrome in flatpak fails to open any video and shows error. chrome from repository works fine.
image

Fedora 34, nvidia drivers.

--Oct 05 09:51:57 fedora org.chromium.Chromium.desktop[2865]: [2:19:1005/095157.560929:ERROR:chrome_browser_main_extra_parts_metrics.cc(228)] crbug.com/1216328: Checking Bluetooth availability started. Please report if there is no report that this ends.
Oct 05 09:51:57 fedora org.chromium.Chromium.desktop[2865]: [2:19:1005/095157.560954:ERROR:chrome_browser_main_extra_parts_metrics.cc(231)] crbug.com/1216328: Checking Bluetooth availability ended.
Oct 05 09:51:57 fedora org.chromium.Chromium.desktop[2865]: [2:19:1005/095157.560962:ERROR:chrome_browser_main_extra_parts_metrics.cc(234)] crbug.com/1216328: Checking default browser status started. Please report if there is no report that this ends.
Oct 05 09:51:57 fedora org.chromium.Chromium.desktop[2865]: [2:19:1005/095157.567208:ERROR:chrome_browser_main_extra_parts_metrics.cc(238)] crbug.com/1216328: Checking default browser status ended.
Oct 05 09:52:16 fedora org.chromium.Chromium.desktop[3529]: The futex facility returned an unexpected error code.
Oct 05 09:52:16 fedora org.chromium.Chromium.desktop[3543]: Failed to load cookie file from cookie: Permission denied
Oct 05 09:52:16 fedora org.chromium.Chromium.desktop[3543]: The futex facility returned an unexpected error code.
Oct 05 09:52:17 fedora org.chromium.Chromium.desktop[3648]: Failed to load cookie file from cookie: Permission denied
Oct 05 09:52:17 fedora org.chromium.Chromium.desktop[3648]: The futex facility returned an unexpected error code.
@apawelec
Copy link

apawelec commented Oct 5, 2021

Same here for Chromium, after downgrade (sudo flatpak update --commit=8102b2026553aa2f881e9a44804c2af69e97f38a513323ff5b4cf2ab9774312d org.chromium.Chromium) it works again.

@wjt
Copy link
Member

wjt commented Oct 5, 2021

All web video is broken for me, too. Attempting to play any video from https://tekeye.uk/html/html5-video-test-page gives the following in the terminal:

Failed to load cookie file from cookie: Permission denied
The futex facility returned an unexpected error code.
[1005/132914.594716:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)
Failed to load cookie file from cookie: Permission denied
The futex facility returned an unexpected error code.
[1005/132914.625699:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)

@refi64 let's roll back to the last good revision, which does indeed seem to be c08424b.

@wjt
Copy link
Member

wjt commented Oct 5, 2021

(The 'easy' thing to do would be to git revert 1956efc 5673d07 8b571b2 b884d98 and push the result.)

@wjt wjt mentioned this issue Oct 5, 2021
@wjt
Copy link
Member

wjt commented Oct 5, 2021

xvitaly on Matrix points to a number of issues with newer glibc:

There is reference in these bugs to trapping failed syscalls... perhaps this doesn't work in the Flatpak sandbox.

@wjt
Copy link
Member

wjt commented Oct 5, 2021

wjt@camille:~$ uname -a                                                                                                             
Linux camille 5.11.0-35-generic #37+dev47.2921aabbem1 SMP Tue Sep 14 20:18:40 UTC 2021 x86_64 GNU/Linux

may be relevant

@xarses
Copy link

xarses commented Oct 5, 2021

I've also run into this problem, as has https://www.reddit.com/r/pop_os/comments/q1vvgq/strange_audio_problem_in_chromium/

The problem appears to only the stable release

    Commit: c43efa0a59161b34ffbfc0a31b93ee885e7ba5c75287d63eb427607bc85f454e
    Parent: 8102b2026553aa2f881e9a44804c2af69e97f38a513323ff5b4cf2ab9774312d
   Subject: Remove now-unneeded WASM trap handler patch (1956efc9)                    
      Date: 2021-10-04 19:35:50 +0000                  

looking at the git log, this patch appears to already been reverted out. Can we remove it from stable on flathub or push a version that isn't broken so people don't get stuck on this?

reverting to

   Commit: 8102b2026553aa2f881e9a44804c2af69e97f38a513323ff5b4cf2ab9774312d                        
   Subject: Update chromium-94.0.4606.61.tar.xz to 94.0.4606.71 (c08424b5)                          
      Date: 2021-10-04 11:08:53 +0000                             

resolved this for me

@wjt
Copy link
Member

wjt commented Oct 5, 2021

It's been reverted in #160.

@xarses
Copy link

xarses commented Oct 5, 2021

Ya, I saw the reverts in the git log but I don't see a new version on flatpak remote-info --log flathub org.chromium.Chromium. Is this a wait for it thing? or is there a step needed to push the image?

@wjt
Copy link
Member

wjt commented Oct 5, 2021

@refi64
Copy link
Collaborator

refi64 commented Oct 6, 2021

The revert should be published now, @xarses @wjt any chance you could also test #161?

refi64 added a commit that referenced this issue Oct 6, 2021
Original commit: b884d98
Reverted by: 02bfc89

Changes to original:

Added an additional patch to resolve #158,
"linux-sandbox-Avoid-failing-with-FUTEX_CLOCK_REALTIME.patch".

Original commit message:

Migrate to runtime 21.08, clean up manifest
refi64 added a commit that referenced this issue Oct 7, 2021
Original commit: b884d98
Reverted by: 02bfc89

Changes to original:

Added two additional patches to resolve #158:

- Linux-sandbox-Fix-conflict-between-syscall-broker-and-fsta.patch
- Linux-sandbox-Fix-condition-variables-on-recent-glibc-vers.patch

Original commit message:

Migrate to runtime 21.08, clean up manifest
@marknefedov
Copy link
Author

Closing this, works fine on my part.

@cidit
Copy link

cidit commented Nov 7, 2022

hello, im still getting this issue. any tips on how i can provide a useful diagnosis?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants