PeasyScale 2.0 Bug [SOLVED - Find Link Here to V2.1 Update]

[MrDuckGuy]

UPDATE - ISSUE WAS SOLVED BY REVISION OF VERSION 2.1.
YOU WILL FIND THE LINK BELOW IN THE FIRST REPLY TO THIS POST.
============================================
Hello, I installed the latest PET of PeasyScale 2.0, in my 64-bit distro
of XenialPup.

It decompiles and loads up perfectly, but it will not work. I don't see
what I'm doing wrong. I tried loading the target image into a flash drive,
but that doesn't work either. It seems to be an issue with the file's location
according to the error message.

Is this a known issue or is this simply user error on my part? Screen capture
is posted here.

Thanks in advance, Kelikaku B'H.

===============================================

HP G60 Notebook PC
Release Date: 04/07/2009
AMD Turion Dual-Core RM-72 2100 MHz
Total RAM: 3699 MB
xenialpup647.0.8.5frugal/xenialpup64save-2019_01_31[/u]

[rcrsn51]

I don't see what I'm doing wrong.

You are running a 32bit program in a 64bit Puppy.

See attached.

[MrDuckGuy]

... You are running a 32bit program in a 64bit Puppy. ...
See attached. ...

... Exactly what I thought too, but I got this same error message on my desktop which is running the same distro and this was after I loaded the package from the link that you just posted (which works well).

The same error occurs, when the first radio button (labeled 'Same') is selected. It only happened when using a file of JPEG format. I hope this is of some help. I don't think there are any more errors or bugs that I could make happen.

When using my laptop, the program didn't seem to work at all (before) but I will reinstall it with your link and hopefully it will prove a fruitful endeavor.

The desktop is booting from a CD but the laptop is booting frugal.

Thanks so very much for your wonderful help,

Kelikaku B'H.
---------------------------------
OptiPlex 9010
Intel(R) Core(TM) i5-3470S CPU @ 2.90GHz 7864 MB
Release Date: 09/19/2012
xenialpup647.0.8.5

[rcrsn51]

I just did a clean install of Xenialpup64 and the 64bit PeasyScale. It worked fine for me.

Open a terminal and run: peasyscale

What error messages do you get?

Is sda1 an NTFS Windows partition?

(which works well).

I don't understand. Under what conditions is it working well?

[MrDuckGuy]

... did a clean install of Xenialpup64 and the 64bit PeasyScale ... worked fine ...

You were right, in regards to the laptop. I was trying to run the 32-bit version (apparently), since now that I have deleted it and downloaded your linked file to the laptop, it started to work just fine, without any glitches nor any gremlins to speak of. That's solved. What is strange is the minor issue with it running on the desktop, which is the same OS but a slightly different installation.

... Open a terminal and run: peasyscale

When I do this, it loads on the laptop.

... What error messages do you get?

The error is being issued from Viewnior 1.1 image viewer, saying that it's unable to locate the file. When PeasyScale ran, it failed to create anything, so there seems to be nothing for Viewnior to display (I am assuming here). This happened with the 32-bit version, on the laptop. But it also occurred with the 64-bit version on the desktop - ONLY when the [Same] save feature was selected. The other save options didn't suffer from the same error (on the desktop). The desktop was booted from a live CD and a save file. I'll still have to check what kind of partition it's on, if that's a factor.

... Is sda1 an NTFS Windows partition?

On my laptop it's ext4, with one partition dedicated to a number of frugal installations. See the screencap of the Gparted output.

(which works well).

I don't understand. Under what conditions is it working well?

With the desktop, all functions seem to be operational, except with the [Same] save option, when it's selected. That's the only time any error crops up. As already noted, the lappy's completely functional now that I have loaded up the new version (THANKS). I am posting this reply from the laptop. B'H.

===================================
HP G60 Notebook PC
Release Date: 04/07/2009
AMD Turion Dual-Core RM-72 2100 MHz
Total RAM: 3699 MB
Linux Kernel: 3.14.54 (x86_64)
Distro: tahrpup64 6.0.5

[rcrsn51]

When you ran peasyscale in the terminal, there were NO error messages?

Change the filename extension from ".jpeg" to ".jpg".

[MrDuckGuy]

...When you ran peasyscale in the terminal, there were NO error messages? ... filename extension from ".jpeg" to ".jpg".

OK, that was from the laptop. Also, I'm sorry - if this makes any difference, I rebooted my laptop into the Tahr64 install. Last night I was having issues while running Xenial and I rebooted. So, what I just verified was that it's working in Tahrpup64, and I still have to check on Xenial64. But it holds that I was using the 32-bit version, as you already pointed out to me. (This is why I put a huge note on my desktops ... to remind me which OS is running, whether it's 32 or 64 or Tahrpup, Xenial or otherwise).

I'll have to get back to you, after I retry this with the laptop running Xenial, and I will get to the desktop and try both your suggestions presently. Hope this helps, and thanks for your assistance. B'H.
===================================
HP G60 Notebook PC
Release Date: 04/07/2009
AMD Turion Dual-Core RM-72 2100 MHz
Total RAM: 3699 MB
Linux Kernel: 3.14.54 (x86_64)
Distro: tahrpup64 6.0.5

[rcrsn51]

OK. There was definitely a problem with files using the ".jpeg" extension if you selected "Same".

I have posted a new version above.

[MrDuckGuy]

... you ran peasyscale in the terminal, there were NO error messages? ...

I rebooted the laptop into Xenial64, and ran it from Terminal. It's behaving normally. Screenshot below.

Change the filename extension from ".jpeg" to ".jpg".

I got a few errors here. It doesn't like the "jpeg" extension, when [Same] is operational. It accepts the extension when [JPEG] is selected. I've checked this a few times on the laptop. Screenshot below.

When the extension is altered to "jpg" there is a new error box that pops up, which alerts another "File not found!" message. The issue is when either [Same] or [JPEG] are selected, but here's an assumption, that the computer wants to find the file with that extension, and I'd have to alter the file itself as well as the dialog box for that to happen. Screenshot below. (I just tried it, and the computer likes it when the extension is simply [JPG], both when [Same] and when [JPEG] options are active). No screenshot, but it worked both times. That's probably what you meant in the first place, anyway, wasn't it?

I still have to repeat this on the desktop, all this was on the laptop. Please, bear with me, if possible. B'H.
===============================================

HP G60 Notebook PC
Release Date: 04/07/2009
AMD Turion Dual-Core RM-72 2100 MHz
Total RAM: 3699 MB
xenialpup647.0.8.5frugal/xenialpup64save-2019_01_31

[MrDuckGuy]

... problem with files using the ".jpeg" extension if you selected "Same". ... a new version above.

OK. There was definitely an improvement, both the desktop and laptop had identical issues with the v2.0 which were totally eliminated by the update v2.1.

Thanks so very much for the alacrity and assistance, and thank you for making me part of the troubleshooting process. I hopefully can provide you with the address to send my royalty checks. We make quite a good team, and I'm certain in no time we can hopefully conquer the cold fusion problem tomorrow morning.

I can't wait to start fueling my Delorean with banana peels, personally. How about you? B'H.

[MrDuckGuy]

UPDATE - ISSUE WAS SOLVED BY REVISION OF VERSION 2.1.
YOU WILL FIND THE LINK ABOVE IN THE FIRST REPLY TO THIS POST.
============================================
PeasyScale 2.0 Bug [SOLVED - Find Link Here to V2.1 Update]

Link to update is in the first reply to this post. Above.
Thanks to rcrsn51 for doing the update.
We're going to solve the room-temperature-superconductor problem next. B'H.
===============================================

HP G60 Notebook PC
Release Date: 04/07/2009
AMD Turion Dual-Core RM-72 2100 MHz
Total RAM: 3699 MB
xenialpup647.0.8.5frugal/xenialpup64save-2019_01_31[/u]

[MrDuckGuy]

... a clean install of Xenialpup64 and the 64bit PeasyScale.
It worked fine ... is it working well?

So, I have a slightly different issue
about right-click context menus. I noticed that when right-clicking, there's a
context menu option for Peasyscale sometimes, but not ALL the time.

When I click on either a "JPG" or a "JPEG" file, the context menu option to load the
Peasyscale program is listed. Not in other cases though.

If I click on a folder, or a "BMP," "TIFF," "GIF" or "PNG" file, the context menu option
for Peasyscale isn't to be found? Screen shots below.

Thanks in advance, Kelikaku B'H.

[rcrsn51]

The original PeasyScale only worked with JPEGs and had a post-install script like this:

Code: Select all

ln -sf /usr/share/applications/peasyscale.desktop /root/.config/rox.sourceforge.net/SendTo/.image_jpeg/PeasyScale

But once PeasyScale started handling other types, I removed it from the PET.

You can try modifying the above command for other types.

[MrDuckGuy]

... original PeasyScale only worked with JPEGs and had a post-install script like this:

Code: Select all

ln -sf /usr/share/applications/peasyscale.desktop /root/.config/rox.sourceforge.net/SendTo/.image_jpeg/PeasyScale

... PeasyScale ... removed it ... try modifying the above command for other types ...

I just downloaded and am running "stretch" puppy and it's pretty new. The graphics menu still, even now, includes PeasyScale 2.0.

So how would I even decompile the instructions/scripts? Then I can edit them. I bet this is bombastically simple. I truly don't know though.

I'm sure I can do it though. B'H.

[rcrsn51]

Open a terminal, paste in the above line and run it. It's all ONE line.

Then change "jpeg" to "png" and repeat.

[MrDuckGuy]

Open a terminal ... change "jpeg" to "png" and repeat. ...

Great, so straightforward. I can actually do that faster than you can say "bobs yar uncle." What about for a directory though? I know this is going to be awfully easy, am I wrong?

Thanks in advance, Kelikaku B'H.

[rcrsn51]

Change ".image_jpeg" to ".inode_directory".