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#40775 - [open-vm-tools] vmtoolsd does not start with icu 53.1
Attached to Project:
Community Packages
Opened by evilhamsterman (evilhamsterman) - Monday, 09 June 2014, 21:02 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 10 June 2014, 15:25 GMT
Opened by evilhamsterman (evilhamsterman) - Monday, 09 June 2014, 21:02 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 10 June 2014, 15:25 GMT
|
DetailsDescription:
It appears the package was last built against icu version 52.1 but icu has since been updated to 53.1. When attempting to start the vmtoolsd service it fails with the error /usr/bin/vmtoolsd: error while loading shared libraries: libicui18n.so.52: cannot open shared object file: No such file or directory When I rebuilt the package against the latest icu 53.1 it works normally Additional info: * open-vm-tools 5:2013.09.16 * icu 53.1 Steps to reproduce: Install open-vm-tools in a VMware guest Start vmtoolsd with systemctl start vmtoolsd View the status of the service to see it has failed |
This task depends upon
Closed by Doug Newgard (Scimmia)
Tuesday, 10 June 2014, 15:25 GMT
Reason for closing: Not a bug
Additional comments about closing: User had outdated packages.
Tuesday, 10 June 2014, 15:25 GMT
Reason for closing: Not a bug
Additional comments about closing: User had outdated packages.
Comment by Doug Newgard (Scimmia) -
Monday, 09 June 2014, 22:30 GMT
I just checked open-vm-tools 5:2013.09.16-8 for both x86_64 and i686, both are linked to libicu*.so.53. You gave a version, but not a package version number, what version are you on, exactly?