Unable to build workspace with kde-builder (unable to install libksysguard)

Development
1

Building plasma/libksysguard (workspace/libksysguard) (5/64)
Fetching remote changes to libksysguard
Merging libksysguard changes from branch master
No changes to libksysguard source code, but proceeding to build anyway.
Compiling… succeeded (after 2 seconds)
Installing libksysguard failed (after 2 seconds)
Unable to install libksysguard!

LOGS:

CMake Error at processcore/cmake_install.cmake:175 (file):
file INSTALL cannot copy file
“/home/ifrahim/kde/build/libksysguard/processcore/org.kde.ksysguard.processlisthelper.policy”
to
“/usr/share/polkit-1/actions/org.kde.ksysguard.processlisthelper.policy”:
Permission denied.
Call Stack (most recent call first):
cmake_install.cmake:52 (include)

FAILED: CMakeFiles/install.util
cd /home/ifrahim/kde/build/libksysguard && /usr/bin/cmake -P cmake_install.cmake
ninja: build stopped: subcommand failed.
exit code was: 256

2

Which distro are you running? Are you using a system without sudo?

CC: @Ashark

4

I’m on Arch, and no I am not running a system without sudo. I also don’t have app armor or SELinux enabled, if that helps.

5

That’s a known kauth issue I think…

Deleting the build directory for libksysguard (~/kde/build/libksysguard) and rebuilding it should work.

6

I’m facing the same issue currently, and deleting the directory didn’t help.

I’m wondering if anyone else has faced this issue and debugged it?

7

Unfortunately, as I can’t edit, here are some more details!

The build only works with sudo ninja install, otherwise giving the same error mentioned in the original post.

However, kde-builder doesn’t detect that it’s been built after I’ve manually built it, which causes it still to catch at libksysguard.

8

Also on Arch, ran into the same issue. I’ve been able to get past it by setting -DINSTALL_BROKEN_KAUTH_POLICY_FILES=Yes in my kde-builder configuration’s cmake-options. This changes the destination of the install commands into the install directory of the application, so they don’t explode due to lack of sudo.

I imagine it won’t cause big issues, since the already installed policy files from the system packages aren’t that much different from the ones that were just generated. Your mileage may vary of course.