As usual DO NOT REPORT BUGS AS COMMENTS HERE.
Where can I report runtime failures?
I have evince quitting when trying to print after upgrading to glibc 2.17:
[ 155.441947] evince: segfault at 1 ip 00007fe9c8ea02c3 sp 00007fff8831b1d8 error 4 in libpango-1.0.so.0.3200.5[7fe9c8e8c000+49000]
emerge -e world with ~1200 packages and gnome-overlay and gcc-4.7.2 and ~amd64 went fine apart from ppl (ppl build bug it's not connected to glibc 2.17) and another one package (clisp).
The problem with evince no longer occurs.
(In reply to comment #1)
> Where can I report runtime failures?
Clarification for comment #0:
- Please file a *NEW* bug for each package that fails in any way with glibc-2.17 and have it *BLOCK* this one.
- The bug should be assigned to the maintainer of the package. Please do not cc toolchain - they get enough mail on these things.
- *DO NOT* use this bug for any problems with glibc-2.17 itself. Instead, file a
NEW bug describing your issue and it will be assigned by a bug wrangler.
I did work on two of the open bugs:
One now resolved - the other should be set as resolved.
Anything else we could do to get glibc-2.17
the unstable certificate ?
Or do you want to wait for glibc-2.18 ?
(I run my system with glibc-2.17 without issues)
pretty much all bugs have been sorted now