Thank you for waking up this thread, again. Am I understanding you correctly, that you are not having this issue in bullseye?
Thank you, --FC > On Jan 3, 2025, at 13:52, Geoff Shang <ge...@quitelikely.com> wrote: > > Hi, > > Was a bug ever filed on this issue? > > If not, I can open one, but I don't really understand the technical stuff as > much as I would like to. > > But I would like to see it fixed. This happens to me on a regular basis and > is very annoying, especially during high priority issue investigations at > work which are time sensitive. > > I have actually not upgraded one of my machines from Bullseye due to this > issue. > > At the very least, I would not like to see this bug make it into Trixie. > > Geoff. > > > On Fri, 15 Mar 2024, Frank Carmickle wrote: > >> Waking up this thread. >> >> Samuel and others. Please let us know what we can do to help get this one >> sorted. >> >> Thanks so much. >> --FC >> >> >>> On Jan 23, 2024, at 08:20, Geoff Shang <ge...@quitelikely.com> wrote: >>> >>> On Sat, 6 Jan 2024, Samuel Thibault wrote: >>> >>>> Geoff Shang, le jeu. 04 janv. 2024 15:04:22 +0200, a ecrit: >>>>> I updated the core file at http://quitelikely.com/gcore >>>> >>>> Thanks, that's indeed still the same situation: an alsa-lib mutex is >>>> said to be held by a thread which is not executing alsa-lib code. >>> >>> What's the next step then? >>> >>> Cheers, >>> Geoff. >>> >> >> >
