Red Hat Bugzilla – Bug 1003703
Crash on mouse click due to missing symbol
Last modified: 2015-11-01 20:37:27 EST
Description of problem:
Whenever I left or right-click any action on Daisy, plasma-desktop crashes:
/usr/bin/plasma-desktop: symbol lookup error: /usr/lib64/kde4/plasma_applet_daisy.so: undefined symbol: _ZN11TaskManager9BasicMenuC1EP7QWidgetPNS_8TaskItemEPNS_12GroupManagerE5QListIP7QActionESA_
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.add Daisy to desktop
2.left or right click any action
Using KDE 4.11
Unfortunately, I can't confirm, neither on F18 nor on F19 (fresh vm).
Can you reproduce this in a fresh user profile? Could you please try and reinstall daisy? Do you use kde-testing by any chance?
Indeed I use kde-testing (and some self-compiled parts of KDE). I expected kde-workspace to be API/ABI compatible, maybe I'm wrong :)
I'll try to reproduce it later this week.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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.
This was most probably my mistake due to using self-compiled KDE with possible ABI changes.