workaround for glibc bug

[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.

-- 
________________________________________________________
Matthias Kretz (Germany)                            <><
http://Vir.homelinux.org/
MatthiasKretz at gmx.net, kretz at kde.org,
Matthias.Kretz at urz.uni-heidelberg.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070928/fa850b5a/attachment.sig>