You shouldn't need QtDeclarative in a kded, and it's being used at the moment tsdgeos@xps:~$ ldd /usr/lib/kde4/kded_touchpad.so | grep Decl libQtDeclarative.so.4 => /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 (0x00007f29578db000)
KCM and KDED live in the same .so library. And in KCM I use Plasma::Theme (to show wallpaper), so kded+kcm links with Plasma libs, which, in turn, need QtDeclarative. If you could suggest how to link to less libs, I'll be happy to fix this bug. Also, I plan to rewrite "testing area" using plasma widgets.
And why do they live in the same library what's the need for it?
(In reply to comment #2) > And why do they live in the same library what's the need for it? Because they share a lot of code. I had two choices: - library for kded, library for kcm, library for shared code - both kded and kcm in single library I've choosen second, because it is simplier. Actually, I don't see a problem in linking to QtDeclarative - it is used by plasma anyway.
kded daemons are supposed to be small stuff that starts quickly at startup, and you need to load 111 libraries into your daemon, i'd say you can probably do with around 50 (ktouchpadenabler uses 46, kscreen 48) I see that as a bug, if you don't, close it as invalid.
I'll think about it. IMHO, what really slows down startup is single event loop for all kded modules. And sometimes it causes sudden deadlocks...
Hello! This bug report concerns the Synaptics version of the Touchpad page, which is no longer supported in Plasma 6. Can you please see if the issue still happens when using Libinput? If so, please change the status back to "REPORTED." If not, go ahead and change it to "RESOLVED FIXED", or let the bot do it automatically after a month. Thanks!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!