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#49897 - [kdeconnect] does not launch, file missing
Attached to Project:
Community Packages
Opened by bence (vervoid) - Thursday, 30 June 2016, 21:37 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 01 July 2016, 00:13 GMT
Opened by bence (vervoid) - Thursday, 30 June 2016, 21:37 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 01 July 2016, 00:13 GMT
|
DetailsDescription:
When I try to launch kdeconnect-cli, I get the following error: kdeconnect-cli: error while loading shared libraries: libicui18n.so.56: cannot open shared object file: No such file or directory Additional info: * package version(s) kdeconnect-0.9.g-2 Steps to reproduce: Launch kdeconnect-cli in terminal. |
This task depends upon
Comment by Doug Newgard (Scimmia) -
Friday, 01 July 2016, 00:13 GMT
Nothing in the kdeconnect package is linked to libicu at all. This means there's something else on your system that kdeconnect is linked to that is then linked to libicu. Make sure your entire system is up to date and rebuild any foreign/AUR packages that you have that may be linked to the old libicu. You can set LD_DEBUG=file or use lddtree from the pax-utils package if you need help finding the problem package.