Bug 733462
| Summary: | glibc-2.14.90-6 causes kdeinit4 to segfault | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Martin Kho <rh-bugzilla> |
| Component: | glibc | Assignee: | Andreas Schwab <schwab> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | awilliam, eparis, fedora.qc, fweimer, iarnell, jakub, jamatos, kevin, kkshethin, rdieter, schwab, timosha |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glibc-2.14.90-8 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-09-13 06:11:31 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 719957 | ||
|
Description
Martin Kho
2011-08-25 18:35:03 UTC
to be clear, is prelinking enabled on this system? (tenatively putting on F16Blocker-kde ...) Hi, @comment 1: I've tried it on two F16 installs with the same result. One is an upgraded F15, the other is an updated F16 Alpha. For the first one I'm not 100% sure prelink is enabled, but for the second I'm rather sure it isn't, I would think? What is the default? Hope this helps. Martin Kho Prelink is enabled by default. I have prelinked enabled by default and I see the same for the two machines where I have upgraded to F16. Hi, I'm getting old :-) The same issue happened to my in 2009[1] (See also [2]) A work around was to run prelink -f /usr/bin/kdeinit4. This too, works for the current issue, at least for me. Martin Kho [1] https://bugzilla.redhat.com/show_bug.cgi?id=515539 [2] https://bugzilla.redhat.com/show_bug.cgi?id=519226 If glibc is going to disavow this being a bug, perhaps we could put a %trigger in kdelibs to include that workaround on glibc upgrades... anyway, another test for regressions: $ LD_BIND_NOW=1 /bin/ls does this work ok? (In reply to comment #8) > anyway, another test for regressions: > > $ LD_BIND_NOW=1 /bin/ls > > does this work ok? For me it does. Yes, it does for me too. Martin Kho *** Bug 733800 has been marked as a duplicate of this bug. *** *** Bug 733514 has been marked as a duplicate of this bug. *** *** Bug 733219 has been marked as a duplicate of this bug. *** *** Bug 733580 has been marked as a duplicate of this bug. *** I'd say this isn't a blocker as -6 has actually been rejected through negative karma. The 'current' glibc build is now -4 again, that's what is in the repos and on composes, so this shouldn't affect any releases. glibc-2.14.90-7 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/glibc-2.14.90-7 Package glibc-2.14.90-7: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glibc-2.14.90-7' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/glibc-2.14.90-7 then log in and leave karma (feedback). Hi, Yes, version -7 is working for me Thanks, Martin Kho Package glibc-2.14.90-8: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glibc-2.14.90-8' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/glibc-2.14.90-8 then log in and leave karma (feedback). glibc-2.14.90-8 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |