search

flathub / org.signal.Signal

https://flathub.org/apps/details/org.signal.Signal
59 stars 34 forks source link

Linux: bluetooth headset profile autoswitch loop #655

Open Altonss opened 1 month ago

Altonss commented 1 month ago

When accepting a call on Signal, while having a bluetooth headset connected on A2DP profile, a profile autoswitch bug appears. The profile keeps looping between A2DP and HSP/HFP, making it unusable. I don't know if it is caused by the flatpak wrapper or not :thinking:, but didn't found anything related on the upstream repo.

OS: Fedora 40, Gnome desktop Version: 7.8.0

fvalasiad commented 1 month ago

+1, discord isn't working either but in an alternative way.

OBS works as intended. Hard to pinpoint where the issue lies.

fvalasiad commented 1 month ago

Confirmed that it only happens with pipewire 1.0.x

upstream version pipewire 1.1.x works properly.

So it's not a flatpak issue, it happens in native signal-desktop too, but as it seems it ain't a signal issue in general.

Altonss commented 1 month ago

Confirmed that it only happens with pipewire 1.0.x

upstream version pipewire 1.1.x works properly.

So you mean the Signal flatpak with pipewire1.1.x on the system works properly?

Altonss commented 1 month ago

So it's not a flatpak issue, it happens in native signal-desktop too, but as it seems it ain't a signal issue in general.

If the same bug happens also with the official build, maybe let's open a bug on their issuetracker also.

fvalasiad commented 1 month ago

Confirmed that it only happens with pipewire 1.0.x

upstream version pipewire 1.1.x works properly.

So you mean the Signal flatpak with pipewire1.1.x on the system works properly?

At least with the current release, 1.1.82, yes.

But you do not have to stray off from your distribution's packages, this worked for me: https://wiki.archlinux.org/title/PipeWire#Automatic_profile_selection

fvalasiad commented 1 month ago

So it's not a flatpak issue, it happens in native signal-desktop too, but as it seems it ain't a signal issue in general.

If the same bug happens also with the official build, maybe let's open a bug on their issuetracker also.

I am actually thinking that maybe we shouldn't open an issue at all since it ain't a signal issue, unless it is...

I mean I find it weird that it only happens with signal, OBS works fine, discord works fine. Weird.

Maybe we should instead open an issue in pipewire, or both.

I was planning to when I found out the issue, but pipewire's issue tracker is so big right now and plenty of the issues reported were similar. Still I find it weird for the older version to have bugs that the new one doesnt imho