workaround for glibc bug

Leo Savernik l.savernik at aon.at
Sun Sep 30 20:22:07 BST 2007


Am Freitag, 28. September 2007 schrieb Matthias Kretz:
> On Friday 28 September 2007, Leo Savernik wrote:
> > Can you work around it by using the null backend? (Assuming switching to
> > another functional backend wouldn't change the situation.)
>
> Sure, you can also delete all apps on your system that use threads. Then
> you're safe. ;-)
>
> There's no null backend. There's a fake backend - use it if you want to. It
> doesn't use threads. Are uninstall all phonon backends and send the
> backtraces of crashes to me. Seriously, that would be a nice task if
> someone could test that apps work fine if no Phonon backend is available.

I've yet to hit this bug but I'm asking just in case. I don't see me 
installing a new glibc any time soon. I'll try the *fake* backend if 
necessary (even though I *will* upgrade eventually as I want to have stable 
sound ;-) ).

mfg
	Leo







More information about the kde-core-devel mailing list