Description of problem: Starting k3b in a terminal I get following error: k3b: symbol lookup error: /lib64/libkdeui.so.5: undefined symbol: _ZNK26KRecursiveFilterProxyMkdel10metaObjectEv Version-Release number of selected component (if applicable): k3b-2.0.2-20.20130927git.fc20.x86_64 k3b-common-2.0.2-20.20130927git.fc20.noarch k3b-extras-freeworld-2.0.2-14.fc20.x86_64 k3b-libs-2.0.2-20.20130927git.fc20.x86_64 kdelibs-4.11.4-1.fc20.x86_64 kdelibs-common-4.11.4-1.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1.Just try to start k3b Actual results: k3b: symbol lookup error: /lib64/libkdeui.so.5: undefined symbol: _ZNK26KRecursiveFilterProxyMkdel10metaObjectEv Expected results: k3b started Additional info: none
Are you sure you're running our packaged K3b? What does: which k3b return? I don't think our (nor upstream's) kdelibs ever exported _ZNK26KRecursiveFilterProxyModel10metaObjectEv (let alone _ZNK26KRecursiveFilterProxyMkdel10metaObjectEv, what's a "Mkdel"? ;-) ), which corresponds to "KRecursiveFilterProxyModel::metaObject() const", the metaObject() method is inherited from QObject.
Oh, please also post the output of: ldd `which k3b` to check what kdelibs are being loaded.
Created attachment 843205 [details] Additionnal information requested by Kevin Kofler
OK, and what does: rpm -V k3b k3b-libs kdelibs say?
Created attachment 843208 [details] Additionnal information requested by Kevin Kofler
So... ...I disabled prelink in /etc/sysconfig/prelink (PRELINKING=no) and I manually run /etc/cron.daily/prelink Then I rebooted and try to restart k3b. I got the same error. So to return to original situation, I re-enabled prelink in /etc/sysconfig/prelink (PRELINKING=yes) and I manually re-run /etc/cron.daily/prelink Then I rebooted and try to restart k3b. Now k3b starts even if I get few messages (see attachement below)
Created attachment 843232 [details] New messages after to have re-enabled prelinking
So it looks like prelink screwed things up for you somehow.
prelink implies LD_BIND_NOW=1 for the non-dlopened libraries, can't you reproduce the same when not prelinked with LD_BIND_NOW=1 ? That would still be a k3b bug.
$ export LD_BIND_NOW=1 $ k3b (still) starts up ok for me, using, $ rpm -q prelink glibc k3b prelink-0.5.0-1.fc20.x86_64 glibc-2.18-11.fc20.x86_64 k3b-2.0.2-20.20130927git.fc20.x86_64
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.