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#67349 - [suscan] error when starting sigdigger | wrong libvolk.so version ?
Attached to Project:
Community Packages
Opened by fallback (Fallback) - Tuesday, 21 July 2020, 18:57 GMT
Last edited by Filipe Laíns (FFY00) - Tuesday, 21 July 2020, 21:06 GMT
Opened by fallback (Fallback) - Tuesday, 21 July 2020, 18:57 GMT
Last edited by Filipe Laíns (FFY00) - Tuesday, 21 July 2020, 21:06 GMT
|
DetailsDescription:
error message when starting sigdigger: SigDigger: error while loading shared libraries: libvolk.so.2.2.1: cannot open shared object file: No such file or directory Additional info: when downgrading to libvolk 2.2.1 it works maybe related https://github.com/BatchDrake/sigutils/issues/14 Steps to reproduce: start sigdigger |
This task depends upon
Closed by Filipe Laíns (FFY00)
Tuesday, 21 July 2020, 21:06 GMT
Reason for closing: Fixed
Additional comments about closing: suscan 1.0-2
Tuesday, 21 July 2020, 21:06 GMT
Reason for closing: Fixed
Additional comments about closing: suscan 1.0-2
Comment by Antonio Rojas (arojas) -
Tuesday, 21 July 2020, 20:37 GMT
sogrep shows that sigutils also wasn't rebuilt for the libvolk soname bump
Comment by Filipe Laíns (FFY00) -
Tuesday, 21 July 2020, 21:06 GMT
Thank you for reporting! I was not notified of any soname bump. I have rebuilt suscan and sigutils, sorry for the trouble.