Puppy Linux Discussion Forum

Yes, another one!

Blog announcement:

https://bkhome.org/news/202202/easyos-v ... eased.html

If anyone wants to try Pitivi video editor, please do. I only gave it a very basic workout, and it seemed ok.

Good morning, @BarryK .

Ah, back to the roots of EasyOS by a look at the screen.

I updated my system from EasyOS 3.2 to EasyOS 3.3 using the 'update' icon.
Update went well, devx v. 3.2 was taken care of as well.

I have just updated from 3.2.1 to 3.3, and the wallpaper did not update. It is an easy fix, see appended blog post:

https://bkhome.org/news/202202/easyos-v ... eased.html

Another thing that did not update is "petget" on the desktop. That should now be "pkgget". Again, you can manually fix it.

I will endeavour to automate these fixes for future updates.

Hello @BarryK .

filemnt is broken for the old encrypted puppy save files! Error : "losetup-FULL: invalid option -- 'p'"
In fact losetup is missing -p and -e options!
Cryptsetup in the build would be nice so LUKS encryption would work.
Is there a reason why Ciper blowfish is not in raspberry pups (it is in all others including this easy) ?

My sound card is not remembered and have to be selected every boot.

Other than that everything I tested seems to be working , posted this from seamonkey on easy 3.3 .

I think the mouse cursor acceleration setting tool is not working?
The code for this appears to be in /usr/bin/pupx
Various ways of getting to it from Menu items:-
Desktop > pupX set properties of X
Setup > Mouse/keyboard Wizard
Setup > Wizard Wizard (PupControl) > Hardware > Input Devices
Settings don't seem to store correctly, GUI is stuck on accel=2.0 and threshold=4
Looking at /root/.xset.sh the setting for acceleration has a missing numerator
eg should be 12/10 (for accel-1.2) but the "12" is missing
Could this be because one of the linux utilities has changed behaviour, or has a bug crept in somehow?

Similar issue in modern WoofCE Puppies. I reported this to dimkr in his Vanilla Dpup thread but no reply yet.
The code there has been moved from pupx to /usr/sbin/input-wizard but it has the same problem

since your going to include a video editor, what about including DVDStyler (https://sourceforge.net/projects/dvdstyler/) for professional (fancy) dvds to manage your works.

OscarTalks wrote: ↑Wed Feb 02, 2022 10:21 pm

I think the mouse cursor acceleration setting tool is not working?

Good morning @OscarTalks ,

xset is coded with 2.0/4. You need to recompile xset-1.2.4 to make it work properly. I have mine set up to '10/10 2' to slow down my mouse. I had to do the same for the Pi4-built. I have compiled xset2 (not stripped). You can give this one a try (fake gz).

Debug info from /tmp/xerrs.log: dc: can't open '2': No such file or directory
dc tool was identified as the problem back in late 2021.

Hello FeodorF,
Thanks for the reply and for the attached executable xset. I ran strip --strip-unneeded on it. I don't think there is any problem with doing that.
Do you have the GUI for mouse acceleration fully working?
Does it write correctly to /root/.xset.sh and does it show the changes if you open it again?
It seems OK if I set it by manually editing /root/.xset.sh
In terminal "xset q" reflects the changes (after restart of X)
I didn't really have enough time to fully study it today and I don't understand all the code in the pupx GUI script
The dc error shows up in terminal. I see that dc is a busybox symlink
I tried compiling the package which contains "real" dc executable, but it also shows errors.
Maybe I am looking at things wrongly. Will look some more when I get some time.

scsijon wrote: ↑Thu Feb 03, 2022 6:49 am

since your going to include a video editor, what about including DVDStyler (https://sourceforge.net/projects/dvdstyler/) for professional (fancy) dvds to manage your works.

Yes, looks interesting.
Though, my only interest for now is to create videos to upload to YouTube.

FeodorF wrote: ↑Thu Feb 03, 2022 7:45 am

OscarTalks wrote: ↑Wed Feb 02, 2022 10:21 pm

I think the mouse cursor acceleration setting tool is not working?

Good morning @OscarTalks ,

xset is coded with 2.0/4. You need to recompile xset-1.2.4 to make it work properly. I have mine set up to '10/10 2' to slow down my mouse. I had to do the same for the Pi4-built. I have compiled xset2 (not stripped). You can give this one a try (fake gz).

How is that "10/10 2" set when you compile it?
I just looked at the recipe in OE, xset version 1.2.4:

DESCRIPTION = "xset is a utility that is used to set various user \
preference options of the display."

LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://COPYING;md5=bea81cc9827cdf1af0e12c2b8228cf8d"
DEPENDS += "libxext libxmu libxau"
PE = "1"

SRC_URI += "file://disable-xkb.patch"

SRC_URI[md5sum] = "70ea7bc7bacf1a124b1692605883f620"
SRC_URI[sha256sum] = "e4fd95280df52a88e9b0abc1fee11dcf0f34fc24041b9f45a247e52df941c957"

CFLAGS += "-D_GNU_SOURCE"
EXTRA_OECONF = "--disable-xkb --without-fontcache"

...I wonder if the "--disable-xkb" is important?

FeodorF wrote: ↑Thu Feb 03, 2022 7:45 am

Debug info from /tmp/xerrs.log: dc: can't open '2': No such file or directory
dc tool was identified as the problem back in late 2021.

That one has slipped through the cracks. The commandline syntax for busybox dc changed a few years ago.

If you look at /usr/sbin/xinitrc_test script, there is a test whether busybox has the "old" or the "new" dc.
We can put this same test into /usr/sbin/pupx

I can't do it right now, have other duties.

I was trying to figure out the syntax for busybox dc tool (new version) and I am struggling a bit with setting the number of decimal places that it prints out
There is one step where it divides by 10 to give the current acceleration number in the GUI
There is another step where it multiplies the selected number by 10 to give the correct setting for the .xset.sh config file
If stray decimal places get printed out, it messes things up
eg it must be 30/10 for acceleration=3 and NOT 30.0/10
I used a workaround by multiplying by 100 and then dividing by 10 (actually 5+5)
That way the final numerator number does not have any decimal places, only the integer.
The division step is giving me for example (from 14/10) a result of 1.4 and NOT 1.40 which is good
Anyway, I seem to have the acceleration settings working from the /usr/bin/pupx GUI (with the recompiled xset executable installed)

Edit line 15 to read:-
MOUSEACCEL=`LANG=C dc -e "${MOUSEACCEL10} ${MOUSEACCELDIV} 1 k / p"` #130209

Edit line 56 to read:-
MOUSEACCX10=`LANG=C dc -e "${1} 100 * 5 5 + / p"` #130209

That seems to eliminate the dc errors and the settings from the drop-down list appear to store correctly.

@OscarTalks
Thanks for figuring that out.

I was puzzled, why is it so difficult now to get an integer result?
I have spent the last couple of hours puzzling over this, then I stumbled upon this:

https://unix.stackexchange.com/question ... to-integer

The essence is, if you divide by 1 you get an integer! That link is using 'bc':

# bc <<<"(2.3 * 10)/1"
23
# echo "(2.3 * 10)/1" | bc
23

...first example requires bash.

Since bc and dc are very similar under the hood, I tried this:

# LANG=C dcFULL -e "2.3 10 * 1 / p"
23
# LANG=C busybox dc -e "2.3 10 * 1 / p"
23

...the full dc and the busybox dc give same result.