To whom it might concern ...
Dear listmembers, after having struggeled for quite a while with unstable bluetooth connections / missing possibility to set the audio mode to a2dp I finally upgraded to 15.2. I had tested the "live" version of it beforehand and there it seemed to work. But after completion of the upgrade - no a2dp profile again. Searching on the net suggests many different solutions, I tested them, it failed. Finally it came to my mind what is different between the "live" system booted from a stick and my "regular" installation: - I have two KDE - session in parallel, one on tty7, the other one on tty8, - the "live" system has only one KDE - session. after not logging in to the second session - whops, a2dp is there, flawlessly, just like someone would expect. Now I am asking myself what is going wrong here, apparently two instances of the same KDE - bluetooth - configurations are "fighting" each other causing performance issues (and stability problems ...). As I would think that having two sessions in parallel on one server is nothing "out of scope" I wonder whether or not I should rise a bug report pointing to this - any opinions? Thank you for thinking that over - and, by the way, Merry Christmas to everyone out there. Best Dieter -- ----------------------------------------------------------- Dr.-Ing. Dieter Jurzitza 76131 Karlsruhe
In data mercoledì 23 dicembre 2020 20:24:04 CET, Dr.-Ing. Dieter Jurzitza ha scritto: Seasonal greetings. I would suggest you raise the bug report. I am suffering for long time now of not working BT support and my usual asset is to run 3 different user sessions on one laptop. During the years I raised several bugs against this, I did put myself on several c/c list of other bugs reported. All closed after some year without progress. A lot of things were blamed as responsible, but your finding is very in my view interesting and I saw it mentioned in none of the bug reports, on non working A2DP BT profiles, pulseaudio not working etc. In particular, there must be an issue because I have a machine with TW and running it in the very same asset I do have a working A2DP. So it is AFAIK only leap, being hit by this annoying problem. Further, a working BT stack with the possibility of correctly switching profiles, is, as of 2021 (nearly), a minimum requirement IMO, for the user perception of a modern and qualitatively well situated OS. So, you have me as member in your "fan club" if you raise it. Kind regards.
participants (2)
-
Dr.-Ing. Dieter Jurzitza
-
Stakanov