Bug#793641: glibc: too few static TLS slots

[Andreas Henriksson <andreas@fatal.se>]

Hello Andreas Cadhalpun.

Thanks for your interest in this issue.

On Sun, Jul 26, 2015 at 09:35:16PM +0200, Andreas Cadhalpun wrote:
> Control: severity 793641 important
[...]

I'd like to start out with questioning this.... gstreamer1.0-libav
is completely unuable now, breaking very popular programs like totem.
Severity should in my opinion be grave.

[...]
> The link [1] provided there is quite helpful.
[...]
> 1: https://bugzilla.redhat.com/show_bug.cgi?id=1124987

It indeed is, and I'd like to point out comment #22:

"
  For the record it is not a glibc bug. It is a defect in the loaded
  libraries, they should not require TLS. Fundamentally it's a defect
  that we allowed developers to build shared libraries with static TLS
  in the first place.
"

https://bugzilla.redhat.com/show_bug.cgi?id=1124987#c22


No matter if this is a bug in glibc or not, ffmpeg maintainers should
take any 'temporary' measures at hand to ensure usability and not expect
changes to be done on a whim to critical system components like glibc.
This breakage has persisted way too long now. If there are no other
option, maybe it's time to start planning transitioning back to libav
until there's a better tested and working way to transition
to ffmpeg? Speaking to #debian-multimedia there doesn't seem to
be much interest in dealing with the breakage caused by the ffmpeg
transition right now.

Regards,
Andreas Henriksson