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

[Linux] Sound defaults to the wrong device #2808

Closed
jgedri opened this issue Jan 3, 2019 · 1 comment
Closed

[Linux] Sound defaults to the wrong device #2808

jgedri opened this issue Jan 3, 2019 · 1 comment

Comments

@jgedri
Copy link

jgedri commented Jan 3, 2019

PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->

Description

Videos play silently because the wrong output is selected.

Steps to Reproduce

  1. Play a video.
  2. Start pavucontrol.
  3. Select the right output device.

Actual result:

Videos play without sound.

Expected result:

Videos should play with sound.

Reproduces how often:

easily reproducible

Brave version (brave://version info)

Brave v. 0.25.2
rev. 8ea2a
OS: Linux (Debian 9)

Reproducible on current release:

  • Does it reproduce on brave-browser dev/beta builds?

Website problems only:

  • Does the issue resolve itself when disabling Brave Shields?
  • Is the issue reproducible on the latest version of Chrome?
    Chromium automatically selects the right device.

Additional Information

I'm running Debian "stretch" on a custom-built desktop PC. There are two output devices; the one I use is an Nvidia GM204 audio controller.

@srirambv
Copy link
Contributor

srirambv commented Jan 4, 2019

You are running the deprecated version of Brave. Please install the new version (0.58.16). You can follow the instructions from here

@srirambv srirambv closed this as completed Jan 4, 2019
@srirambv srirambv added this to the Dupe / Invalid / Not actionable milestone Jan 4, 2019
@rebron rebron removed this from the Dupe / Invalid / Not actionable milestone May 9, 2019
@NejcZdovc NejcZdovc added this to the Dupe / Invalid / Not actionable milestone Jun 3, 2019
@bbondy bbondy removed this from the Dupe / Invalid / Not actionable milestone May 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants