|
Bugzilla – Full Text Bug Listing |
| Summary: | newly setup bluetooth speaker is available in gnome-settings/audio only after reboot | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Lubos Kocman <lubos.kocman> |
| Component: | GNOME | Assignee: | Takashi Iwai <tiwai> |
| Status: | NEW --- | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | alarrosa |
| Version: | Leap 15.5 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
device is connected
new bluetooth device is not displayed after successful bluetooth connection device overview device is visible after reboot |
||
Created attachment 867269 [details]
new bluetooth device is not displayed after successful bluetooth connection
Created attachment 867270 [details]
device overview
Created attachment 867271 [details]
device is visible after reboot
I've noticed the same with my corporate bluetooth headset from microsoft. That one was connected via usb dongle. Just to clarify, simple logout from gnome-session (that should restart are userspace processes) did not work and reboot had to be involved in order to display device. Assigning to Takashi after a brief discussion with Antonio. As mentioned in private, I'd try if pavucontrol sees the device (just in case it's an issue with gnome-settings, which I doubt, but it's better to check everything) and also, I'd check if it works with pipewire instead of pulseaudio [1] to check if it might be related to pulseaudio or with the bluez layer. [1] Installing the wireplumber-audio package which will show a conflict which offers to uninstall pulseaudio. After doing that the easiest thing to do is reboot which will make sure all the relevant services are stopped/started. (In reply to Lubos Kocman from comment #4) > I've noticed the same with my corporate bluetooth headset from microsoft. > That one was connected via usb dongle. Hm, so it's not specific to BT, but also USB-audio? I checked with a clean installation of Leap 15.5 on Thinkpad T14 gen3, and it seems working. I connected to a BT headset, and it was connected immediately, working. Reboot, and it keeps working. |
Created attachment 867268 [details] device is connected Hello, Default 15.5 installation on my workstation which is connected to Alexa Echo (a wireless speaker). lkocman@localhost:~> ps aux | egrep "audio|pipe" lkocman 3762 0.4 0.0 2291412 23308 ? S<sl 11:59 0:00 /usr/bin/pulseaudio --daemonize=no --log-target=journal lkocman 4774 0.0 0.0 60496 10612 ? S<sl 11:59 0:00 /usr/bin/pipewire lkocman 7852 0.0 0.0 10388 2616 pts/0 S+ 12:01 0:00 grep -E --color=auto audio|pipe somethings is not right with gnome-settings Step 1) connect to the wireless speaker (gnome-settings) Step 2) select newly connected bluetooth device (alexa echo) as a sound output device (gnome-settings) Actual results) Device is not visible as an option in gnome-settings / audio. Logout doesn't help. Expectations) newly device is visible, selected and used as external audio speaker Workaround) reboot your computer, device is suddenly listed and works as external device