https://bugs.kde.org/show_bug.cgi?id=466288

            Bug ID: 466288
           Summary: Bluetooth media sessions don't appear in Media Player
                    when using mpris-proxy
    Classification: Plasma
           Product: plasmashell
           Version: 5.27.1
          Platform: Archlinux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Media Player
          Assignee: plasma-b...@kde.org
          Reporter: jacksonbur...@icloud.com
                CC: k...@privat.broulik.de
  Target Milestone: 1.0

SUMMARY
By connecting my phone to my computer through Bluetooth, and by using PipeWire,
I'm able to play my phone's audio through my computer. By default, my phone's
Bluetooth media session doesn't show up in Media Player, but I can use BlueZ's
mpris-proxy utility to expose the session as an MPRIS player. However, the
MPRIS player generated by mpris-proxy isn't detected by Media Player. Media
keys don't work either.

STEPS TO REPRODUCE
1. Use Bluetooth to connect a phone to a machine running Plasma with PipeWire
as the audio system.
2. Play music on the phone. Make sure the sound output is set to the computer.
3. Open a terminal, and run `mpris-proxy`.

OBSERVED RESULT
The Media Player icon doesn't appear in the system tray, and manually selecting
it results in the 'No media playing' message. Media keys don't affect playback,
either.

EXPECTED RESULT
Once mpris-proxy is started, playback controls for the Bluetooth media session
should appear in Media Player, and media keys should function.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux (Wayland)
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
I'm able to successfully control playback by using playerctl v2.4.1 or GNOME
Shell 43.3.
I'm using a Pixel 6 running Android 13 with YouTube Music, but the same
behavior should occur with other phone brands and music apps.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to