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

Ubuntu snap does not use GNOME media controls #22617

Closed
jayschwa opened this issue Apr 29, 2022 · 1 comment
Closed

Ubuntu snap does not use GNOME media controls #22617

jayschwa opened this issue Apr 29, 2022 · 1 comment

Comments

@jayschwa
Copy link

Description

In Ubuntu 22.04, the snap version of Brave does not use the GNOME media controls.

Steps to Reproduce

  1. Open the snap versions of Brave, Chromium, and Firefox.
  2. Play a YouTube video in each browser.
  3. Click the Ubuntu system clock to open system notifications.

Actual result:

Only Chromium and Firefox have created GNOME media controls.

image

Expected result:

Brave should also create a GNOME media control when playing web media.

Reproduces how often:

Every time.

Brave version (brave://version info)

Brave 1.38.109 Chromium: 101.0.4951.41 (Official Build) (64-bit)
Revision 93c720db8323b3ec10d056025ab95c23a31997c9-refs/branch-heads/4951@{#904}
OS Linux

Version/Channel Information:

I am using snap's latest/stable channel. I have not tested with other channels.

Additional Information:

There is a thread from 2020 on the snap forums discussing this issue for Firefox, with eventual resolution.

Snap shows that all browsers have the same mpris connection:

$ for b in brave chromium firefox; do snap connections $b | grep mpris; done
mpris                     -                               brave:mpris                     -
mpris                     -                                       chromium:mpris                   -
mpris                     -                               firefox:mpris                    -
@wknapik
Copy link
Contributor

wknapik commented Jun 27, 2023

Thanks @jayschwa! I believe this is fixed, please reopen if not

@wknapik wknapik closed this as completed Jun 27, 2023
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

2 participants