Failed to merge PDF with footer

[humaun21]

Describe the bug

Failed to merge PDF with footer when installing libraries manually..

To reproduce

1. Manually place JSignPdf.jar in /opt/libresign.
2. Set correct ownership and permissions (www-data:www-data, 755)
3. Installed java,pdftk from debian repositories
4. Set the path manually
5. php occ config:app:set libresign jsignpdf_path --value "/opt/libresign/jsignpdf-2.3.0/JSignPdf.jar"
6. php occ config:app:set libresign java_path --value "/usr/bin/java"
7. php occ config:app:set libresign pdftk_path --value "/usr/bin/pdftk"

Expected behavior

LibreSign should merge the PDF with the footer successfully, even if the libraries were installed manually instead of "occ libresign:install --all"

Screenshots

Environment information

1. Nextcloud version: Nextcloud Hub 10(31.0.5)
2. LibreSign version: 11.6.0
3. PHP version: 8.2.28
4. OS: debian 12 (bookworm)
5. Java: openjdk 17.0.17
6. JSignPdf version: 2.3.0
7. pdftk: pdftk port to java 3.3.2 a Handy Tool for Manipulating PDF Documents

root@nextcloud:/var/www/nextcloud# php occ config:app:get libresign java_path
/usr/bin/java
root@nextcloud:/var/www/nextcloud# php occ config:app:get libresign pdftk_path
/usr/bin/pdftk
root@nextcloud:/var/www/nextcloud# php occ config:app:get libresign jsignpdf_path
/opt/libresign/jsignpdf-2.3.0/JSignPdf.jar
root@nextcloud:/var/www/nextcloud#

Additional context

For java, pdftk, and jsignpdf, the “Invalid hash of binary files” error is expected because I manually set the paths instead of using occ libresign:install --all, so the verification fails. However, this should not be a problem since the paths are correctly set. I didn’t want to install these libraries through LibreSign because they are already installed on my system from repositories except jsignpdf and I want to use them.

Does it have to be installed through occ libresign:install --all? If not, what could be the possible issues?

[vitormattos]

I didn’t want to install these libraries through LibreSign because they are already installed on my system from repositories except jsignpdf and I want to use them.

LibreSign does not perform a system-wide installation of these tools. It only downloads and uses standalone binaries bundled for the application.

Your approach can work, but we strongly recommend using the LibreSign way to get the binaries because the application is tested specifically against those exact versions. Using different versions or distributions may lead to unexpected behavior.

---

Does it have to be installed through occ libresign:install --all?

No. You can also install everything via the web interface, which already downloads all required dependencies automatically.
The occ libresign:install --all command is mainly intended for advanced or CLI-oriented setups. For example, in development environments, I often complete the setup entirely via CLI, but not necessarily using the --all option.

---

If not, what could be the possible issues?

Based on the code path where this error is triggered, the issue is related to pdftk. It is likely caused by differences between the pdftk binary/version you are using and the one expected by LibreSign.

LibreSign uses a wrapper around pdftk, and currently this wrapper does not provide detailed feedback about failures at this exactly point, which makes troubleshooting harder. To fully diagnose this, it would be necessary to debug the issue directly in your environment.

Using custom binaries may work, but this setup is not officially tested, so failures are possible.

As a troubleshooting step, we strongly recommend downloading and using the LibreSign-provided binaries. This will not affect your system packages in any way, it is not a real installation. The only impact is additional disk usage (approximately 200 MB).