Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#71522 - libpackagekitqt5 is not provided at runtime for dolphin service menu installer
Attached to Project:
Arch Linux
Opened by Alexander Lohnau (alex1701c) - Friday, 16 July 2021, 12:17 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 14 August 2021, 08:16 GMT
Opened by Alexander Lohnau (alex1701c) - Friday, 16 July 2021, 12:17 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 14 August 2021, 08:16 GMT
|
DetailsDescription: The libpackagekitqt5 package is optional for dolphin, but if the project is compiled with it and it is not provided at runtime the service menu installer will crash.
The solution would be to make this dependency required or set the CMAKE_DISABLE_FIND_PACKAGE variable for this dependency. Considering that I am not aware of the packagekit functionality being much used on arch I would recommend the second option. This was reported by multiple users on reddit or the individual service menu projects, including https://store.kde.org/p/1328693 or https://github.com/alex1701c/JetBrainsDolphinPlugin/issues/2. A similar issue is https://bugs.kde.org/show_bug.cgi?id=424734, but there at least no crash is caused. Additional info: * package version(s) * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: |
This task depends upon
Closed by Antonio Rojas (arojas)
Saturday, 14 August 2021, 08:16 GMT
Reason for closing: Fixed
Additional comments about closing: Removed packagekit support
Saturday, 14 August 2021, 08:16 GMT
Reason for closing: Fixed
Additional comments about closing: Removed packagekit support
If they are provided at build time they need to be provided at runtime too.
You might argue that the packagekit use in the installer is residual enough to justify dropping its use, and that might be the case (I'd have to take a look), but there's certainly nothing wrong with the way it is currently packaged per se: that's just how optional runtime functionality (such as plugins) is managed in Arch.