Red Hat Bugzilla – Bug 733462
glibc-2.14.90-6 causes kdeinit4 to segfault
Last modified: 2016-11-24 11:01:22 EST
Description of problem: After the update to the above glibc the kde-desktop wont show up. In /var/log/message the following message appears: "Aug 25 11:22:19 ps-1866 kernel: [ 129.668398] kdeinit4[1021]: segfault at b0 ip 00007f9e60ddf2f1 sp 00007fff95741730 error 4 in libc-2.14.90.so[7f9e60cb8000+1a5000]" Downgrading glibc (1.14.90-4) solves this issue. Version-Release number of selected component (if applicable): * glibc-2.14.90-6.x86_64 * kdelibs-4.7.0-1.fc16.x86_64 How reproducible: Always Steps to Reproduce: 1. Log in into kde (plasma-desktop) 2. A message appears telling kdeinit4 can't be started 3. Actual results: No desktop Expected results: Desktop shows up Additional info:
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.