antiXscreenshot2 — updated version 1.08f available

[Member Robin]

antiXscreenshot2 was updated again.

The new update fixes the issue with broken layout of antiXscreenshot2 help screen display when the default antiX system font was changed from „Ubuntu 10.5” to something with a wider tracking like e.G. „Courrier New 16”.

Please be aware you’ll need a tiny additional helper tool for this version: „laufweite”
You can download it’s installer package matching your system from my gitlab:

laufweite 0.2 (32bit)
Installer package: https://gitlab.com/Robin-antiX/laufweite/-/raw/main/deb-installer/laufweite-x32.deb?inline=false
Checksum file: https://gitlab.com/Robin-antiX/laufweite/-/raw/main/deb-installer/laufweite-x32.deb.sha512.sum?inline=false

laufweite 0.2 (64 bit)
Installer package: https://gitlab.com/Robin-antiX/laufweite/-/raw/main/deb-installer/laufweite-x64.deb?inline=false
Checksum file: https://gitlab.com/Robin-antiX/laufweite/-/raw/main/deb-installer/laufweite-x64.deb.sha512.sum?inline=false

You can install it together with antiXscreenshot 1.08f in one go, after downloading the new version:

antiXscreenshot 1.08f (32bit and 64bit both)
Installer package: https://gitlab.com/Robin-antiX/antixscreenshot2/-/raw/main/debian-installer-packages/1.08f-antiX-community/antixscreenshot2.deb?inline=false
Checksum file: https://gitlab.com/Robin-antiX/antixscreenshot2/-/raw/main/debian-installer-packages/1.08f-antiX-community/antixscreenshot2.sha512.sum?inline=false

1.) File checking (replace 32 by 64 for 64bit systems)

$ shasum -c laufweite-x32.deb.sha512.sum
OK
$ shasum -c antixscreenshot2.sha512.sum
OK

Only proceed if both checks return a clean „OK”. Otherwise try to redownload.

2.) Installation (replace 32 by 64 for 64bit systems)

$ sudo apt-get update
$ sudo apt-get install './laufweite-x32.deb' './antixscreenshot2.deb'

You will be asked whether to set up gdrive. Please read carefully the instructions (your browser will open the original instructions site) after pressing „h” key and then go on with your decision in the install console window. If you choose „y” an additional console window will open, allowing to complete the gdrive setup. All the gdrive setup can also be done later on in case you choose „n”. But if you don’t want to use the personal cloud upload functionality you can just keep it unconfigured, or even delete the gdrive executable from your system. antiXscreenshot won’t complain, but just grey out the personal cloud upload fields in its GUI.

If you want to setup gdrive later, just start antiXscreenshot from console and follow the instruction from its output:

Error: No accounts found
Use  'gdrive account add'  to add an account.

Close antiXscreenshot2 again. It was just to see the message. Then simply enter in the console window

$ gdrive account add

Follow the instructions provided from its output. On next call antiXscreenshot2 will automatically recognise the oauth2 account(s) and allow selection of uploading to personal cloud space as storage target.

Additionally to what the antiXscreenshot2 installer describes about switching between classic antiXscreenshot and antiXscreenshot2 on your system …

Setting up antiXscreenshot2 as system wide alternative. Call
  sudo update-alternatives --config screenshot
in order to restore the original version of antiXscreenshot tool.

… you can use the antiX Control Center as well:

Translations from version 1.08e will match for the 1.08f version.

Kind regards
Robin

Windows is like a submarine. Open a window and serious problems will start.

[Member verdy]

Helpful

Up

0

::

Hello Robin,

By your easy-to-understand explanations i got new version with no problem.
Off course i cheked SHA sums after download.

And i saw “–window” option saying farewell to the error massege.

Thanks.

[Member verdy]

Helpful

Up

0

::

I have a sad report.
When I ran it with LANG=ja_JP.UTF8, I got the same trouble as Wallon.
The strange thing is that the gdrive error message appears twice. This is the same as Wallon’s case.
Also,the error message related to ~/.cache/antiXscreenshot2 is the same as Wallon’s case.
I have only seen this once. It doesn’t reproduce after that.
This is terminal message.

demo@antix1:~
$ LANG=ja_JP.UTF8 antixscreenshot2 -v
firstrun_PID= 14773
-v
antiXscreenshot — a screenshot tool by antiX community
Error: No accounts found
Use <code>gdrive account add</code> to add an account.
Plaese make sure to have UTF-8 locale support for your language enabled.
Error: No accounts found
Use <code>gdrive account add</code> to add an account.
Creating Workfiles: /home/demo/.cache/antiXscreenshot2/antiXscreenshot-lossless-working-copy-14773.png
Strip off troublesome special characters, Note text entered: スクリーンショット xxxxx
full screen mode
Delaying 5 seconds
scrot  -d 5 -o "/home/demo/.cache/antiXscreenshot2/antiXscreenshot-lossless-working-copy-14773.png"
scrot: Saving to file /home/demo/.cache/antiXscreenshot2/antiXscreenshot-lossless-working-copy-14773.png failed: No such file or directory
Workfile created: /home/demo/.cache/antiXscreenshot2/antiXscreenshot-lossless-working-copy-14773.png
/usr/local/bin/antixscreenshot2: line 2777: /home/demo/.cache/antiXscreenshot2/mtpaint.conf: No such file or directory
/usr/local/bin/antixscreenshot2: line 2785: /home/demo/.cache/antiXscreenshot2/mtpaint.conf: No such file or directory
Copy to clipboard first as selected
/usr/local/bin/antixscreenshot2: line 352: /home/demo/.cache/antiXscreenshot2/antiXscreenshot-lossless-working-copy-14773.png: No such file or directory
Saving shot to File: /home/demo/スクリーンショット/スクリーンショット-2023Apr25_210115.jpg
Creating Save file: /home/demo/スクリーンショット/スクリーンショット-2023Apr25_210115.jpg from workfile: /home/demo/.cache/antiXscreenshot2/antiXscreenshot-lossless-working-copy-14773.png
Cannot open file
[ OK ]
Mischief managed. Leaving...

I don’t know if it’s related to screenshot2, but after that, operations after selecting a file with zzzFM or Laefpad may not work.Reboot and it should be fine. Maybe there are other factors…

sorry.

[Member RJP]

Helpful

Up

0

::

antiXscreenshot2 works perfectly, but only one thing wonders me. The program seems to be fully translated even it should not be fully translated in Finnish language?

• This reply was modified 1 week, 6 days ago by RJP.

[Member Robin]

Helpful

Up

0

::

verdy wrote:

I have a sad report.

Many thanks for the detailed bug report, Verdy! The debug output you’ve posted allows me to check for the reason. Seems to be related with the management of antiXscreenshot2 lossless working copy files in cache. Maybe I’ve goofed some check for or creation of cache directory on some line in a specific workflow if not present already. Will be fixed as soon as possible.

Concerning the gdrive3 error message: Will see whether the double message could be suppressed.

RJP wrote:

…even it should not be fully translated in Finnish language?

Why not? looks like the Finnish translators are working assiduously on the resource, most strings apart from the help text are ready meanwhile: https://app.transifex.com/anticapitalista/antix-development/translate/#fi/antixscreenshot2/455515078?q=translated%3Ano

Windows is like a submarine. Open a window and serious problems will start.

[Member Robin]

Helpful

Up

0

::

Finally found the reason for the trouble. Actually I didn’t goof any line for the proper cache directory creation, everything is prepared properly. Instead of this, an overexcited error handler triggers the cleanup meant only to be executed when actually leaving antiXscreenshot2 after processing to execute all the cleanup already after simply reading the help page. So the initially created antiXscreenhsot2 cache subdirectory was removed again when merely leaving the help screen. The error handler ERR was added to the cleanup trap in line 192 in one of the last updates to make sure antiXscreenshot2 will clean up reliable and properly after hard killing, and I wasn’t aware this would catch errors when merely leaving internal functions as well, which obviously happens. Sorry for the inconvenience.

Hotfix:

Step 1.) Open the file /usr/local/bin/antixscreenshot2 with geany. Root permissions required, so e.g. call it from command line (roxterm-window):
sudo geany '/usr/local/bin/antixscreenshot2'

Step 2.)
Scroll down and edit line 2662

Replace the 1 by a 0 (zero)

2662 --button=$"Back":1

The line should read then:

2662 --button=$"Back":0

This will cause to return from the help subroutine with exit status 0 instead of exit status 1, the latter interpreted falsely by bash as an error, while it is the default exit status from yad for the „abort” button merely, not meant to be interpreted as an error at all. So changing the 1 to a 0 (the default yad OK button exit status) in this place will cause the antiXscreenshot2 cache folder not to be removed before work is actually done.

Step 3.)
Save the file back to disk. (Saving will only be possible if you have opened it with root permissions beforehand)
Close geany.
Start a screenshot and check out whether the issue has gone.

Many thanks @Wallon and in particular @Verdy for providing the detailed bug report.

Next version of antiXscreenshot will include this fix, and I’ll also check whether other error conditions might trigger this as well. If you notice any issues, please check whether the ~/.cache/antiXscreenshot2 folder is removed while antiXscreenshot2 is still running. In this case please let me know the precise condition under which it happens and also the precise processing step on which the folder vanishes.

Kind regards
Robin

————–
P.S.:

verdy wrote:

The strange thing is that the gdrive error message appears twice.

The gdrive3 error messages on console while using antiXscreenshot2 are don’t care. The second one is caused by a second call of this helper tool to make sure the original system wide gdrive3 oauth2 account was restored properly on leaving antiXscreenshot2. This checking causes complaints of gdrive3 as long no account was set up. As said, don’t care for these gdrive3 messages. Will see whether I can suppress them (at least the second one originating from cleanup at leaving.) The calls are needed if one or more oauth2 accounts were set up on your system.

Windows is like a submarine. Open a window and serious problems will start.

[Member verdy]

Helpful

Up

0

::

Hello Robin,

Thank you for Hotfix.
I changed 1 to 0 at line 2662. I will report you if i notice something.

I will do not care error messages of gdrive as you say.
It was originally something I didn’t notice unless I ran it in the terminal.

Many thanks.

[Member Robin]

Helpful

Up

0

::

Unfortunately during Marcelos next testing session this evening it turned out, the new helper tool needs to be compiled for each antiX version separately, not only once for 32 bit and once for 64 bit, since it depends on a library „libc6”. While this library is present in antiX 23 in Version 2.36, it is present on antiX 22 only in Version 2.31, which is not enough for running the version included in the 64 bit package, which I have compiled on antiX 23. Not sure how to deal with this. I can’t compile something on a antiXY version I’m not running.

The downloadable „laufweite” packages provide the helper tool only for the following two antiX versions:

32 bit package: antiX 21/22
64 bit package: antiX 23 only

For now, please compile the helper tool on your antiX version yourself in case you happen to run another version as listed above, until a solution is found.

You’ll find all needed instructions in the info text at:
https://gitlab.com/Robin-antiX/laufweite
Scroll down to the section »Compile instructions for antiX (only needed If you can’t use the installer packages)« and follow the instructions. The complete process will take a few minutes only.
Then replace the executable laufweite file in /usr/local/bin by the file you have compiled yourself.

Kind regards
Robin.

Windows is like a submarine. Open a window and serious problems will start.

[Member marcelocripe]

Helpful

Up

0

::

Unfortunately during Marcelos next testing session this evening it turned out, the new helper tool needs to be compiled for each antiX version separately, not only once for 32 bit and once for 64 bit, since it depends on a library „libc6”. While this library is present in antiX 23 in Version 2.36, it is present on antiX 22 only in Version 2.31, which is not enough for running the version included in the 64 bit package, which I have compiled on antiX 23. Not sure how to deal with this. I can’t compile something on a antiXY version I’m not running.

Robin, the test I did yesterday was with antiX 22 full 64-bit without any kind of update, that is, I tested it with antiX outdated with the ISO that was published on October 18, 2022.
I don’t know if it’s possible to compile a program on an operating system with a LiveUSB with the original ISO without any kind of update.

The .deb packages that I was able to build from the .rpm of the PCLinuxOS Brasil community were made from the full 64-bit antiX 21 ISO or the 64-bit antiX 22 full ISO. I think the following, if it works with the ISO without any kind of update, then it should work with the updated operating system.

Thank you for guiding me through yesterday’s tests.

– – – – –

Unfortunately during Marcelos next testing session this evening it turned out, the new helper tool needs to be compiled for each antiX version separately, not only once for 32 bit and once for 64 bit, since it depends on a library „libc6”. While this library is present in antiX 23 in Version 2.36, it is present on antiX 22 only in Version 2.31, which is not enough for running the version included in the 64 bit package, which I have compiled on antiX 23. Not sure how to deal with this. I can’t compile something on a antiXY version I’m not running.

Robin, o teste que eu fiz ontem foi com o antiX 22 full de 64 bits sem qualquer tipo de atualização, ou seja, eu testei com o antiX desatualizado com a ISO que foi publicada no dia 18 de outubro de 2022.
Eu não sei se é possível compilar um programa em um sistema operacional com um LiveUSB com a ISO original sem qualquer tipo de atualização.

Os pacotes .deb que eu consegui construir a partir dos .rpm da comunidade PCLinuxOS Brasil foram feitos a partir da ISO antiX 21 full de 64 bits ou da ISO antiX 22 full de 64 bits. Eu penso o seguinte, se funciona com a ISO sem qualquer tipo de atualização, então deverá funcionar com o sistema operacional atualizado.

Obrigado por me guiar nos testes de ontem.

[Member PPC]

Helpful

Up

0

::

@Robin: you won’t like my initial suggestion- remove the dependency on the helper app… Optionally, is possible, make it’s use optional (do X if the helper app is available, do Y if it’s not available). The previous version, without the dependency worked great for me, I’m not that worried about perfectly formatted text…
I hope I’m not misjudging the use of that helper app- localization of this app has been very time consuming, and, together with my personal life, it’s the reason I’ve not been that much on the forum, and I just skim trough most recent posts…

Optional idea – is there any way to achieve a similar goal to the helper app with calculations performed in bash? That could be baked into the script itself…

P.

[Member Robin]

Helpful

Up

0

::

PPC wrote:

is there any way to achieve a similar goal to the helper app with calculations performed in bash? That could be baked into the script itself

If I’d found a way to achieve this in plain bashscript I’d have done this 🙂 Please feel free to provide another working solution.

PPC wrote:

you won’t like my initial suggestion- remove the dependency on the helper app […] I’m not that worried about perfectly formatted text

I would be fine with this, but other people care for proper formatted text, which was the reason for I spent some hours on researching to create a workaround for this yad and gtkdialog issue we face in mostly all antiX scripts. So it’s not the very best idea to remove it again.

But hopefully I can provide an updated version, able to run on all antiX versions again (still separately for 32 and 64bit). I’m about to compile it on antiX 17.5 instead of antiX 23, which will set the min required libc6 version (and also all the other shared library versions) in a way the executable can run on all recent antiX: 17.5, 19.5, 21, 22 and 23, just as originally intended.

P.S.:

PPC wrote:

is possible, make it’s use optional

This will make the script fail.

PPC wrote:

do X if the helper app is available, do Y if it’s not available

This will render the script code mostly unmaintainable. In how many places of all the scripts this conditional branching should to be added? The amount of needed testing becomes doubled by this to make sure a script works as intended in both cases then. No, I think it’s enough already we are forced to use a helper tool like this at all.

Windows is like a submarine. Open a window and serious problems will start.

[Member Robin]

Helpful

Up

0

::

The laufweite issue is solved. The 32bit and 64bit packages have been updated at gitlab.

The download links from within first posting above in the current thread still match.

See https://www.antixforum.com/forums/topic/laufweite-a-helper-tool-for-windowsize-calculation-in-yad-gtkdialog-bashscript/#post-105645 for details about laufweite.

Please make sure to purge the former laufweite packages from your system ( sudo apt-get purge laufweite ) in case you had installed them; the replacement has got the very same version number, since source code hasn’t changed. These fixed packages are not meant for apt update over the former packages without completely purging them before.

Sorry for the inconvenience. Now the antiXscreenshot2 help screen should show up again on your non antiX 23 system also.

Kind regards
Robin.

Windows is like a submarine. Open a window and serious problems will start.

[Member marcelocripe]

Helpful

Up

0

::

Hello Robin.

I just did some tests with the new packages on antiX 22 full 64bit which doesn’t have any kind of update and everything worked as expected. I haven’t tested GDrive, but I have tested uploading the image to Imgur and it worked successfully. The Help window was able to open successfully.

About the help window text https://i.imgur.com/L3JiGYe.png, I missed the bold text that existed before the start of the first sentence. If the text before the beginning of the first sentence no longer exists, then I will only need to correct the line break and improve the text that is now missing the program name information.

Thank you very much for being able to compile the program in an old version, now it should work in all editions of antiX without having any kind of update.

– – – – –

Olá Robin.

Eu acabei de fazer alguns testes com os novos pacotes no antiX 22 full de 64 bits que não possui qualquer tipo de atualização e tudo funcionou como esperado. Eu não testei o GDrive, mas testei o envio da imagem para o Imgur e funcionou com sucesso. A janela da Ajuda conseguiu abrir com sucesso.

Sobre o texto da janela de ajuda https://i.imgur.com/L3JiGYe.png, eu senti falta do texto em negrito que existia antes do início da primeira frase. Se o texto antes do início da primeira frase não existe mais, então, eu vou precisar corrigir apenas a quebra de linha e melhorar o texto que agora ficou sem a informação do nome do programa.

Muito obrigado por conseguir compilar o programa em uma versão antiga, agora deverá funcionar em todas as edições do antiX sem possuir qualquer tipo de atualização.

[Member Robin]

Helpful

Up

0

::

marcelocripe wrote:

I missed the bold text that existed before the start of the first sentence.

Many thanks, Marcelo, for checking on another machine! Hey, that’s a catch. No, the text wasn’t removed at all from the script code. But for some strange reason yad wouldn’t display it now 🙂

I have checked the script code for this, but there seems to be literally no reason why yad does this. I guess, this is another yad issue and I’ll have to find another workaround to restore the missing text. This is not connected in any way with the helper tool laufweite, but with an additional „span” markdown instruction within the yad dialog. So, please don’t change the layout for this line in your translations. I’ll try to set the markdown instructions in another order to make the text reappear.

Windows is like a submarine. Open a window and serious problems will start.

[Member Robin]

Helpful

Up

0

::

Robin wrote:

I’ll try to set the markdown instructions in another order to make the text reappear.

This approach was successful. Next version of antiXscreenshot2 to come will restore the missing part of the first line of help text window again. As said, it was never removed from the code, but merely hidden by yad completely in display for some strange reason.

Windows is like a submarine. Open a window and serious problems will start.

[Author]

Posts