| Summary: | glibc from update-testing brakes Firefox, Google-Chrome and yum update | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Denis <sorn.denis> |
| Component: | glibc | Assignee: | Andreas Schwab <schwab> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | emiel.kollof, fweimer, jakub, law, schwab, umar |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-15 10:27:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Denis
2011-11-12 18:53:54 UTC
I cannot reproduce this but I am running i686 version of firefox. Yum update fails for me but after trying for 2-3 hours it turned out it was the latest nss that was put in and pulled out but I managed to update when it was in. Going back to old nss (3.12.10-7) solved the problem. Check also you other updates as well as whether you have all the required glibc architectures. Hi, it is not only firefox, as I said google-chrome didn't work either, and some other applications couldn't start to, would segfault, unfortunately I cannot remember now which ones. Didn't mention all details due to time shortage. As I needed working environment, I did yum downgrade glibc glibc-common glibc-devel glibc-headers, and everything is fine now... with KDE at least. Gnome environment became unstable with last updates from updates-testing, but I don't have time to investigate that now. Thanks for responding. OK...are you using nvidia drivers? No, intel sandy bridge. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Everything same with 2.14.90-16. I found this in /var/log/messages after reboot with glibc-2.14.90-16.
Nov 15 07:46:56 x chronyd[1080]: *** glibc detected *** /usr/sbin/chronyd: free(): invalid pointer: 0x00007f8539e81390 ***
Nov 15 07:46:56 x kernel: [ 58.686107] type=1400 audit(1321339616.838:13): avc: denied { signal } for pid=1080 comm="chronyd" scontext=system_u:system_r:chronyd_t:s0 tcontext=system_u:system_r:chronyd_t:s0 tclass=process
Nov 15 07:46:56 x kernel: [ 58.686117] type=1400 audit(1321339616.838:14): avc: denied { signal } for pid=1080 comm="chronyd" scontext=system_u:system_r:chronyd_t:s0 tcontext=system_u:system_r:chronyd_t:s0 tclass=process
Nov 15 07:46:56 x kernel: [ 58.686121] chronyd[1080] general protection ip:7f8539b06a97 sp:7fff3e8d98d0 error:0 in libc-2.14.90.so[7f8539acf000+1ae000]
Nov 15 07:46:56 x systemd[1]: chronyd.service: main process exited, code=killed, status=11
Nov 15 07:46:56 x systemd[1]: Unit chronyd.service entered failed state.
Nov 15 07:47:14 x kernel: [ 76.767140] chrome[2411]: segfault at 17 ip 00007fa87a57fb2e sp 00007fa880494630 error 6 in libc-2.14.90.so[7fa87a458000+1ae000]
Same here. Also, abrt also bugs out (same crash with SIGABRT) because of this when it tries to resolve and send my bugreports. I reverted to glibc 2.14.90-11 to solve this problem for me. Luckily I had the rpms laying about. *** This bug has been marked as a duplicate of bug 754026 *** |