| Summary: | [kdesrc-build] KDE applications always call kded5 from "/usr/bin", rather than kdesrc-build install prefix | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kded | Reporter: | Kyle Devir <kyle.devir> |
| Component: | general | Assignee: | David Faure <faure> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | kdelibs-bugs, kyle.devir, nate, nicolas.fella |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
kdesrc-build prefix build kded5 dying with correct paths
/usr/bin/kded5 and friends started with Dolphin file / folder right-click kded5 after copying files |
||
|
Description
Kyle Devir
2021-05-08 13:37:32 UTC
Whoops ~ forgot to mention that right-clicking folders also triggers it. In order for kded and other DBus-activated things to work correctly you need to configure DBus to take the custom location into account. See https://community.kde.org/Get_Involved/development#Plasma_Desktop for how to do that, in particular the "In order to make DBus and KAuth actions work properly..." part (In reply to Nicolas Fella from comment #2) > In order for kded and other DBus-activated things to work correctly you need > to configure DBus to take the custom location into account. > > See https://community.kde.org/Get_Involved/development#Plasma_Desktop for > how to do that, in particular the "In order to make DBus and KAuth actions > work properly..." part Cheers. Didn't know about that. :) Okay, creating the "/etc/dbus-1/session-local.conf" file with the necessary paths, and restarting the session, hasn't solved anything for me...
Starting Ksysguard immediately on startup, kded5 does get started from the kdesrc-build prefix, but it crashes in short order, which starts drkonqi also from the kdesrc-build prefix, while /usr/lib/kauth/kded-smart-helper oddly gets called...
Right-clicking files / folders from within Dolphin still ends up calling everything from /usr/{bin,lib}/ :|
Created attachment 138269 [details]
kdesrc-build prefix build kded5 dying with correct paths
Created attachment 138270 [details]
/usr/bin/kded5 and friends started with Dolphin file / folder right-click
Does this help? sudo cp -r ~/kde/usr/share/dbus-1/ /usr/share/ sudo cp -r ~/kde/usr/share/polkit-1/actions/* /usr/share/polkit-1/actions/ Created attachment 138309 [details]
kded5 after copying files
kded5 is now called from the kdesrc-build prefix after coping said files.
Still crashes though, it seems. But, that'll be for a different bug report.
> sudo cp -r ~/kde/usr/share/dbus-1/ /usr/share/
> sudo cp -r ~/kde/usr/share/polkit-1/actions/* /usr/share/polkit-1/actions/
Would be nice to have this documented for future, or at least, made clearer, if it already is documented somewhere.
That's what I personally do, but I've resisted adding it to the wiki since it overwrites system files. This is fine... until it isn't. :) Sadly nobody has figured out the correct way to get dbus from the prefix set up properly. See Bug 425272. *** This bug has been marked as a duplicate of bug 425272 *** (In reply to Nate Graham from comment #10) > That's what I personally do, but I've resisted adding it to the wiki since > it overwrites system files. This is fine... until it isn't. :) On Arch, at least, "paccheck --md5sum --quiet" lets you check whether what system files differ from their package checksums. So, in that sense, it's completely fine. The real trick is remembering to reinstall those system packages when you want to use your system's KDE install, heh. Exactly. I live in a git master Plasma session 99% of the time, but doing this would be completely unacceptable for someone who does it 1% of the time. :) Ultimately I think we need to just get Bug 425272 fixed. |