Still unable to validate documents after upgrading to 10.5.1 #4357
Comments
mlinaresalvaro
changed the title
Merged
|
I opened a PR with the fix and I will create a new release as a soon. If you wish, you can apply the changes handmade to verify if will work fine. |
|
Ok, as you wish. Thank you very much for your attention and quick and
efficient response You can count on me for any test you wish to do.
Manuel
Ok como usted desee.
Muchas gracias por su atención y rápida y eficiente respuesta
Puede contar conmigo para cualquier prueba que desee hacer.
El jue, 16 ene 2025 a las 8:20, Vitor Mattos ***@***.***>)
escribió:
… I opened a PR with the fix and I will create a new release as a soon.
If you wish, you can apply the changes handmade to verify if will work
fine.
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXS4DP6L2DRCC2GXFJL2K6WZLAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJVGY2TENBUGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Mr. Mattos.
I am sorry to confirm that it remains more or less the same after applying
the patch.
Look, this is the validation URL for a signed document:
https://cloud.udg.co.cu/index.php/apps/libresign/validation/607470fc-c597-4302-aaa7-11b169bb818f
and this is what you get
[image: imagen.png]
El jue, 16 ene 2025 a las 8:20, Vitor Mattos ***@***.***>)
escribió:
… I opened a PR with the fix and I will create a new release as a soon.
If you wish, you can apply the changes handmade to verify if will work
fine.
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXS4DP6L2DRCC2GXFJL2K6WZLAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJVGY2TENBUGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I actually tried to downgrade to 10.4.4, however, version conflicts
between the applications that libresign uses started and I decided not to
continue playing with a production system.
El jue, 16 ene 2025 a las 8:20, Vitor Mattos ***@***.***>)
escribió:
… I opened a PR with the fix and I will create a new release as a soon.
If you wish, you can apply the changes handmade to verify if will work
fine.
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXS4DP6L2DRCC2GXFJL2K6WZLAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJVGY2TENBUGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I will check what's happened because the error page wasn't displayed correctly. But I saw that the error that this page return is: Current user is not logged in. Check at your Administration Settings > LibreSign. You need to maintain by this way to make the validation URL public:
|
|
Looking the administration setting I found another issue that don't display correctly the saved data about the validation url. I will fix as a soon. |
|
Thank you for your help and answers, and for being so efficient. Yes, I
have it always on, see the following image:
[image: imagen.png]
El jue, 16 ene 2025 a las 9:53, Vitor Mattos ***@***.***>)
escribió:
… Looking the administration setting I found another issue that don't
display correctly the saved data about the validation url. I will fix as a
soon.
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXS3HJAWKTUVPJT43Y32K7BXDAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJVHEZTSNRZHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Check the newest release, 10.5.2 Your images aren't coming at GitHub issue. |
|
enseguida chequeo y le comento, gracias
El jue, 16 ene 2025 a las 10:41, Vitor Mattos ***@***.***>)
escribió:
… Check the newest release, 10.5.2
Your images aren't coming at GitHub issue.
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXTTP735WBCXBOW5CF32K7HK3AVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJWGA2TSNZWG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
the version 10.5.2 not yet published
El jue, 16 ene 2025 a las 10:41, Vitor Mattos ***@***.***>)
escribió:
… Check the newest release, 10.5.2
Your images aren't coming at GitHub issue.
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXTTP735WBCXBOW5CF32K7HK3AVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJWGA2TSNZWG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
This is a cache of Nextcloud. Move the folder data/appdata_/appstore to a temporary folder and run again what you made to fetch the newest version of apps. This is a cache folder. Also would be good to run If work fine, delete your backup of appstore folder. |
|
It is frustrating, as it continues the same. I am sorry to be bothering
you with this. I also cannot validate a document without being
authenticated Now the administration settings are lost, even though I
activate the options to add a footer with the validation URL and write the
QR code, they appear disabled every time I enter the LibreSign
configuration.
El jue, 16 ene 2025 a las 10:50, Vitor Mattos ***@***.***>)
escribió:
… This is a cache of Nextcloud.
Move the folder data/appdata_/appstore to a temporary folder and run again
what you made to fetch the newest version of apps.
This is a cache folder.
Also would be good to run occ files:scan-app-data after move the folder
to a temporary folder.
If work fine, delete your backup of appstore folder.
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXUBUN5ZIXJAX32SVVT2K7IM5AVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJWGA4DGMJTHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I made a lot of checks to identify if have any issue at validation page and I found a JS issue that could be what's you having but I can't confirm because at this issue I can't see your screenshots and haven't a detailed steps to reproduce the issue. I created a new release fixing the JS issue that I found. Could you verify if will work with the newest release? |
|
Of course I can check, I'll be happy to do so, but the data center is shut
down today because of some repairs they're doing on the power line. I'll
try first thing tomorrow morning.
Regards
Manuel
El dom, 19 de ene de 2025, 6:41 a. m., Vitor Mattos <
***@***.***> escribió:
… I made a lot of checks to identify if have any issue at validation page
and I found a JS issue that could be what's you having but I can't confirm
because at this issue I can't see your screenshots and haven't a detailed
steps to reproduce the issue.
I created a new release fixing the JS issue that I found.
Could you verify if will work with the newest release?
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXTV7PKNOV5BCERNKHT2LOFPJAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBQHAZDGMJSGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Hello Vitor.
I would like to tell you that both in the current version (10.5.3) and in
the previous one (10.5.4), there are several problems.
When I try to sign a document, it simply shows what I send in image 1,
however, the document is signed correctly. I also cannot validate the
document without being in the nextcloud. If I am within the platform, the
validation is carried out successfully, but if I am not authenticated in
the platform, it shows what I attach in image 2.
In the application settings, the configurations of the check boxes of the
validation URL are not saved; when one exits the configuration and
re-enters, they are always in the same position: only the first two are
deactivated. (image 3).
Is there no way to publish an update equivalent to the old version 10.4.4
that worked so well? I have tried to downgrade but it gives me a conflict
with the Java libraries and components.
El dom, 19 ene 2025 a las 6:41, Vitor Mattos ***@***.***>)
escribió:
… I made a lot of checks to identify if have any issue at validation page
and I found a JS issue that could be what's you having but I can't confirm
because at this issue I can't see your screenshots and haven't a detailed
steps to reproduce the issue.
I created a new release fixing the JS issue that I found.
Could you verify if will work with the newest release?
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXTV7PKNOV5BCERNKHT2LOFPJAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBQHAZDGMJSGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Vittor,
One last detail, which I forgot in the previous post: the configuration
check reports that Poppler utils is not installed, however, it is.
El dom, 19 ene 2025 a las 6:41, Vitor Mattos ***@***.***>)
escribió:
… I made a lot of checks to identify if have any issue at validation page
and I found a JS issue that could be what's you having but I can't confirm
because at this issue I can't see your screenshots and haven't a detailed
steps to reproduce the issue.
I created a new release fixing the JS issue that I found.
Could you verify if will work with the newest release?
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXTV7PKNOV5BCERNKHT2LOFPJAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBQHAZDGMJSGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
At GitHub side I never can see your attachments. To add images to your issues will be necessary open GitHub and write the message. |
|
Hello Vitor. I would like to tell you that both in the current version (10.5.3) and in When I try to sign a document, it simply shows what I send in image 1, In the application settings, the configurations of the check boxes of the Is there no way to publish an update or downgrade equivalent to the old version 10.4.4 another problem: the configuration check reports that Poppler utils is not installed, however, it is.
|
|
I identified another issue when saving the settings. Could you check again if you can save the settings? |
|
Dear Vittor.
I have already installed the new version today, and everything has improved
significantly. It now validates signatures without being authenticated on
the platform and when a document is signed, the process ends correctly.
The only thing left is that the LibreSign administration interface
configurator reports that Poppler Utils has not yet been installed on the
operating system, and it is installed.
Thankyou very much!
Manuel linares
El lun, 27 de ene de 2025, 10:23 a. m., Vitor Mattos <
***@***.***> escribió:
… I identified another issue when saving the settings. Could you check again
if you can save the settings?
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXWQBYWQIM7COF3QQ3D2MZFNLAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJWGA2TIOBXGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
An yes, I can save the settings, but I can't not sale settings about
identity documento, so it is no very important.
El lun, 27 de ene de 2025, 10:23 a. m., Vitor Mattos <
***@***.***> escribió:
… I identified another issue when saving the settings. Could you check again
if you can save the settings?
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXWQBYWQIM7COF3QQ3D2MZFNLAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJWGA2TIOBXGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Follow the checks that LibreSign do to identify if all is working fine with poppler: To reproduce handmade you can: php -r "print_r(shell_exec('which pdfsig'));"This will need to return the path of pdfsig binary php -r "print_r(shell_exec('pdfsig -v 2>&1'));"This will need to return your pdfsig version |
|
The "Identification documents" isn't working now because we haven't any customer using this feature and to be possible go ahead with the development of LibreSign with our very reduced team and without money to pay us, was necessary to ignore the issues about " Identification documents " |
|
Ahh, ok this issue is not very important.
El lun, 27 de ene de 2025, 10:37 a. m., Vitor Mattos <
***@***.***> escribió:
… The "Identification documents" isn't working now because we haven't any
customer using this feature and to be possible go ahead with the
development of LibreSign with our very reduced team and without money to
pay us, was necessary to ignore the issues about " Identification documents
"
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXXOL76EXCGP2HWGKRL2MZHFBAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJWGA4TINBQHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I needed the validation and the entire signature process to work, and now,
for me, is the more importants elements ok.
El lun, 27 de ene de 2025, 10:37 a. m., Vitor Mattos <
***@***.***> escribió:
… The "Identification documents" isn't working now because we haven't any
customer using this feature and to be possible go ahead with the
development of LibreSign with our very reduced team and without money to
pay us, was necessary to ignore the issues about " Identification documents
"
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXXOL76EXCGP2HWGKRL2MZHFBAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJWGA4TINBQHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
***@***.*** ~]# php -r "print_r(shell_exec('which pdfsig'));"
/usr/bin/pdfsig
***@***.*** ~]# php -r "print_r(shell_exec('pdfsig -v 2>&1'));"
pdfsig version 21.01.0
Copyright 2005-2021 The Poppler Developers - http://poppler.freedesktop.org
Copyright 1996-2011 Glyph & Cog, LLC
***@***.*** ~]#
El lun, 27 ene 2025 a las 10:35, Vitor Mattos ***@***.***>)
escribió:
… Follow the checks that LibreSign do to identify if all is working fine
with poppler:
https://github.com/LibreSign/libresign/blob/main/lib/Service/Install/ConfigureCheckService.php#L75-L106
To reproduce handmade you can:
php -r "print_r(shell_exec('which pdfsig'));"
This will need to return the path of pdfsig binary
php -r "print_r(shell_exec('pdfsig -v 2>&1'));"
This will need to return your pdfsig version
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXS2LYXHM67KT7A67MT2MZG3RAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJWGA4DOOJVHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I'm looking that you used the root user, use the same use that your PHP process is executed. |
|
Ok, I test now
El lun, 27 de ene de 2025, 12:29 p. m., Vitor Mattos <
***@***.***> escribió:
… I'm looking that you used the root user, use the same use that your PHP
process is executed.
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXXCLEGVYU7XCAQCYPL2MZUIHAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJWGQ2DSOJZGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
***@***.*** ~]# su apache
bash-5.1$ php -r "print_r(shell_exec('which pdfsig'));"
/usr/bin/pdfsig
bash-5.1$ php -r "print_r(shell_exec('pdfsig -v 2>&1'));"
pdfsig version 21.01.0
Copyright 2005-2021 The Poppler Developers - http://poppler.freedesktop.org
Copyright 1996-2011 Glyph & Cog, LLC
bash-5.1$
El lun, 27 ene 2025 a las 12:29, Vitor Mattos ***@***.***>)
escribió:
… I'm looking that you used the root user, use the same use that your PHP
process is executed.
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXXCLEGVYU7XCAQCYPL2MZUIHAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJWGQ2DSOJZGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
If you're getting the message "Poppler utils not installed" is because the command |
|
Ok Vittor, thank you very much for everything. At least I have the basics
working now: LibreSign can sign without errors and the signatures can be
validated. The rest can be perfected slowly.
El lun, 27 ene 2025 a las 12:36, Vitor Mattos ***@***.***>)
escribió:
… If you're getting the message "Poppler utils not installed" is because the
command which pdfsig says that the binary pdfsig don't exists and return
nothing.
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXXDHIRQSB2FC5E63DD2MZVABAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJWGQ3DMMZXG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Is there anything pending here? I think we can close this issue then, correct? |
|
Yes, all is ok, thank you
El mar, 28 de ene de 2025, 1:29 p. m., Vitor Mattos <
***@***.***> escribió:
… Is there anything pending here? I think we can close this issue then,
correct?
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXU4JU3AT54D2ZTD3IT2M7EATAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJZG43DGNRUGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
If is possible, will be good to receive a sponsor to help the development of LibreSign. The funding is very important to keep alive this project. |
github-project-automation
bot
moved this from 0. Needs triage
to 4. to release
in Roadmap
|
Dear. I would like to help you with the search for sponsors. The fact is
that I work and live in a country where this kind of collaboration is
practically impossible. My country (Cuba) is in a very serious crisis at
the moment.
El mar, 28 ene 2025 a las 13:41, Vitor Mattos ***@***.***>)
escribió:
… If is possible, will be good to receive a sponsor to help the development
of LibreSign.
The funding is very important to keep alive this project.
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXRG4MQGR4IN3NWFZJT2M7FMTAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJZG44TCMBVGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I know. |
|
If you need to do tests, try out new versions, or whatever you need me to
do, you can count on me, I will be happy to help you.
El mar, 28 ene 2025 a las 14:23, Vitor Mattos ***@***.***>)
escribió:
… I know.
All help will be welcome, including more tests, motivate people to develop
new features, translations,...
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXVKQAOB2LGECHLQEQ32M7KMHAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJZHA3TGMRWHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Do you know the Transifex patform to translate LibreSign? |
|
I don't know this, but I can lean tonise
El mar, 28 de ene de 2025, 2:30 p. m., Vitor Mattos <
***@***.***> escribió:
… Do you know the Transifex patform to translate LibreSign?
https://app.transifex.com/nextcloud/nextcloud/libresign/
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXXFCMVL5RF4BEVOBRD2M7LERAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJZHA4DKOJYG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Probé la nueva versión 10.6.1, que se liberó ayer. Al menos las cosas
básicas, firma y validación, funcionan bien.
El mar, 28 de ene de 2025, 2:30 p. m., Vitor Mattos <
***@***.***> escribió:
… Do you know the Transifex patform to translate LibreSign?
https://app.transifex.com/nextcloud/nextcloud/libresign/
—
Reply to this email directly, view it on GitHub
<#4357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFUGXXXFCMVL5RF4BEVOBRD2M7LERAVCNFSM6AAAAABVJM7YDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJZHA4DKOJYG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks to Mr. Victor Mattos for his quick response.
However, the problem with validating documents in the cloud with LibreSign continues after updating to LibreSign version 10.5.1.
I'll give you more details.
Previously I had Nextcloud 30.0.4 with LibreSign 10.4.4, PHP 8.3.16, Zend Engine v4.3.16 and Zend OPcache v8.3.16, on a Rocky Linux 9, and everything worked without problems.
Then I updated LibreSign to 10.5.0 and since then I can't validate documents if I click on the URL in the footer or if I scan the QR code of a previously signed document. When I do this, what I achieve is to open a LibreSign page in NextCloud.
Something interesting:
In the list of applications required by LibreSign, within the NextCloud administration interface, it is reported that the Poppler utils application is not installed, however, it is installed in the operating system.
The text was updated successfully, but these errors were encountered: