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#61549 - [pulseeffects] Can't install/load plugins
Attached to Project:
Community Packages
Opened by Anton Hvornum (Torxed) - Sunday, 27 January 2019, 16:31 GMT
Last edited by Filipe Laíns (FFY00) - Tuesday, 09 April 2019, 23:56 GMT
Opened by Anton Hvornum (Torxed) - Sunday, 27 January 2019, 16:31 GMT
Last edited by Filipe Laíns (FFY00) - Tuesday, 09 April 2019, 23:56 GMT
|
DetailsDescription:
~$ pulseeffects (pulseeffects:2731): pulseeffects-WARNING **: 16:39:05.141: limiter plugin was not found! ~$ flatpak run com.github.wwmm.pulseeffects Note that the directories '/var/lib/flatpak/exports/share' '/home/anton/.local/share/flatpak/exports/share' are not in the search path set by the XDG_DATA_DIRS environment variable, soapplications installed by Flatpak may not appear on your desktop until thesession is restarted. error: app/com.github.wwmm.pulseeffects/x86_64/master not installed Additional info: I expected the installer-package to install all the necessary paths to be able to install basic/official plugins. This doesn't appear to be the case. Our wiki says very little in this regard and the official github https://github.com/wwmm/pulseeffects/wiki/Installation-from-Source doesn't mention much about it either. * package version(s) - 4.4.7-1 pulseeffects Steps to reproduce: pacman -S pulseeffects |
This task depends upon
Closed by Filipe Laíns (FFY00)
Tuesday, 09 April 2019, 23:56 GMT
Reason for closing: Not a bug
Additional comments about closing: The pulseeffects arch package has *nothing* to do with the pulseeffects flatpak package. It makes no sense for the arch package to create an empty plugin directory, you shouldn't be using the /usr prefix to manually install plugins, /usr/local would be the correct one. If you think there's a problem in our flatpak package, please open a bug for that package.
Tuesday, 09 April 2019, 23:56 GMT
Reason for closing: Not a bug
Additional comments about closing: The pulseeffects arch package has *nothing* to do with the pulseeffects flatpak package. It makes no sense for the arch package to create an empty plugin directory, you shouldn't be using the /usr prefix to manually install plugins, /usr/local would be the correct one. If you think there's a problem in our flatpak package, please open a bug for that package.