S15Pup - Discussion

[peebee]

Abiword - inserting symbols does not work for me. No symbols are showing for none of the fonts and it's not working. Is there a fix?

That is very odd as S15Pup32 works fine.........and I can't offhand think of any differences to explain

[amethyst]

Abiword - inserting symbols does not work for me. No symbols are showing for none of the fonts and it's not working. Is there a fix?

That is very odd as S15Pup32 works fine.........and I can't offhand think of any differences to explain

It's not a distro problem per se as far as I know but a problem with Abiword (its executable specific) or it may be related to a certain version/build of Abiword, not sure. Some versions of the executable seem to have this issue with the "insert character function" either crashing the application or that function not working at all. Changing the executable in /usr/bin with another version seems to solve the problem (well mostly as the operation has a a bit of a delay but it works).

[Wiz57]

@peebee I'm getting an error when trying to start LxTerminal in
S15Pup32-2401201 w/LXDE via ydrv. First noticed LxTerminal wouldn't start, so, fired up URXVT,
issued command lxterminal, got the top error in copy and paste below. Tried "copying" the
missing lib by renaming the one pfind found, then get second error. Ideas? libvte-2.91.so.0 copied
to libvte.so.9 throws second error

lxterminal
lxterminal: error while loading shared libraries: libvte.so.9: cannot open shared object file: No such file or directory
# lxterminal

(lxterminal:6497): Gtk-ERROR **: 13:41:40.667: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported
Trace/breakpoint trap

ps...edit to add...I've booted back into my daily driver S15Pup32 240413 w/older kernel. Have copied
the relevant libvte.so.9 files from its system to a storage area on hd, will next try booting into the
latest 2401201 and try copying those files back into the system, will see how that goes.

pss...IT WORKS! So, insofar as others may encounter this issue, there are 2 files needed for LxTerminal
to run in S15Pup32 22.12 2401201...need libvte.so.9 and libvte.so.9.2800.2. If someone needs them
I could send them. Best I can tell the two files are the same, same size, dates, etc..

[peebee]

@Wiz57

Problem was caused by an old, redundant version of lxterminal in the ydrv - now removed and the ydrv re-uploaded.
https://sourceforge.net/projects/pb-gh-releases/files/

[Wiz57]

@peebee I've tried a number of times, redownloaded, etc but still cannot
get the new LXDE ydrv.sfs to load at bootup in S15Pup32 22.12 241201. Haven't tried it in other pups.
This is attempted in the normal method I use, rename the LXDE-ydrv_XXX.sfs to just ydrv_XXX.sfs.
Then upon failure to load at boot, it results in xorg failure since the savefile I've got was done with the
older LXDE ydrv. If I rename the old one, boot is completed without issue.
I may try just SFS-Load and see what happens. I once did that a few years ago with the old ArchPup32
from like 2020 or so. That may give me an idea of why it isn't being found at boot.
Wiz

[Wiz57]

OK, seems that my problem is probably due to using the older LXDE-ydrv...I booted my test S15Pup32
without the save file, after renaming both ydrvs so they didn't load at boot, then using Rox, clicked on the
newest one, selected to load, and it ran just fine. SO...for future use, I'll have to remember to unload a prior
LXDE ydrv or boot to another Pup, rename it, etc. OR, start all over by booting without the ydrv, then rename
the new one, and reboot. New frugal installs of the current S15Pup32 shouldn't have any issues by using
them in the normal method. Only problem will be with updating a Pup that has been using a prior version.

ps..edit..Oops, even in a new install, LXDE-ydrv will not load at boot. Will require more investigation.

[peebee]

It's meant to be used as a ydrv as loading in that way "patches" the underlying LxPupSc64 - sfs-loading does not overwrite some components.

[Wiz57]

It's meant to be used as a ydrv as loading in that way "patches" the underlying LxPupSc64 - sfs-loading does not overwrite some components.

Yes that how I normally load it, but in S15Pup32 22.12 this particular ydrv is not recognized at boot. As I mentioned above, the older one loads
at boot just fine, but contains an older LxTerminal which won't run without the libraries I tracked down. I'm not able to boot 64bit pups on the
old Acer. I may extract the 2 ydrvs in a tmp directory and look for some problem blocking boot time loading in the new one, then try my hand
at mksquashfs if I find an issue.

[peebee]

It's meant to be used as a ydrv as loading in that way "patches" the underlying LxPupSc64 - sfs-loading does not overwrite some components.

Yes that how I normally load it, but in S15Pup32 22.12 this particular ydrv is not recognized at boot. As I mentioned above, the older one loads
at boot just fine, but contains an older LxTerminal which won't run without the libraries I tracked down. I'm not able to boot 64bit pups on the
old Acer. I may extract the 2 ydrvs in a tmp directory and look for some problem blocking boot time loading in the new one, then try my hand
at mksquashfs if I find an issue.

I am completely flummoxed!!! No matter what I try I can't get S15Pup32 (of any vintage) to load any new *drv.sfs at boot (whether created in S15Pup or in another build like BookwormPup32)!!! I can think of no reason why this might be! Yukkk.

[Wiz57]

It's meant to be used as a ydrv as loading in that way "patches" the underlying LxPupSc64 - sfs-loading does not overwrite some components.

Yes that how I normally load it, but in S15Pup32 22.12 this particular ydrv is not recognized at boot. As I mentioned above, the older one loads
at boot just fine, but contains an older LxTerminal which won't run without the libraries I tracked down. I'm not able to boot 64bit pups on the
old Acer. I may extract the 2 ydrvs in a tmp directory and look for some problem blocking boot time loading in the new one, then try my hand
at mksquashfs if I find an issue.

I am completely flummoxed!!! No matter what I try I can't get S15Pup32 (of any vintage) to load any new *drv.sfs at boot (whether created in S15Pup or in another build like BookwormPup32)!!! I can think of no reason why this might be! Yukkk.

That's what I'm seeing as well. My older ydrv.sfs loads just fine, but the LxTerminal app included needs older libraries that aren't in newer
Pups. I tracked down the 2 needed from an older S15Pup32, copied them into the usr/lib directory and then it runs w/o problems. Not sure
if other LX apps are affected, doesn't appear so. When I get time I might extract the new ydrv and the old ones, then see if I can see anything
in like the boot directory of the sfs that isn't being read. Will report any findings.

[peebee]

@Wiz57

Grrrrrrrrrrrr........... simple naming fault - Pup32 should be pup32 - corrected on SF

[Wiz57]

@Wiz57

Grrrrrrrrrrrr........... simple naming fault - Pup32 should be pup32 - corrected on SF

Was the naming error in the LXDE sfs or the Pup ISO? Which corrected one to download? Thanks!

edit to add...ahhh, got it, and it's booting! No need to redownload, just the correct capitalization in the SFS!

[Wiz57]

@peebee Just wanted to let you and others interested in S15Pup32 that so far
this latest version from 12/01/2024 is behaving quite well, stable, and quick on this old Acer Aspire One AOA150.
Once you figured out the spelling issue, the LXDE ydrv is doing great! Thank you for another excellent Pup!
It does use a tad more memory than my "daily driver" S15Pup32 22.12 240413 with the kernel swap from an
older ScPup/ArchPup32, but that's to be expected with the added drivers and such...only about 30kb more!
Thank you again!
Wiz

[Clarity]

Since 2022, Slackware ISO moved to GRUB2 v2.06. Today they are at v2.12.

[Wiz57]

@peebee Say peebee, I just had a thought...I know, that's dangerous, ! What do you think about renewing your Slackware Current Puppies? Sort of a testbed for whenever Slackware 15.1 is released. I've been doing a bit of searching around, and noticed that in Slackware-Current packages there are quite a number of newer things, especially glibc (even in the "32bit" X86 repo!!). The main reason for my searches has been one of the later Palemoon 3rd Party builds that although it uses GTK2, it also is built with glibc 2.34, and S15Pup32 is glibc 2.33. I've also toyed with the idea of attempting a glibc update, but that can result in breakage! I have found a Palemoon 3rd Party build based on glibc2.33, but also GTK3, which seems to be a bit more sluggish than the GTK2s I've used in the past, but it does run fairly well.
Ideas?
Thanks,
Wiz

[peebee]

@peebee Say peebee, I just had a thought...I know, that's dangerous, ! What do you think about renewing your Slackware Current Puppies? Sort of a testbed for whenever Slackware 15.1 is released. I've been doing a bit of searching around, and noticed that in Slackware-Current packages there are quite a number of newer things, especially glibc (even in the "32bit" X86 repo!!). The main reason for my searches has been one of the later Palemoon 3rd Party builds that although it uses GTK2, it also is built with glibc 2.34, and S15Pup32 is glibc 2.33. I've also toyed with the idea of attempting a glibc update, but that can result in breakage! I have found a Palemoon 3rd Party build based on glibc2.33, but also GTK3, which seems to be a bit more sluggish than the GTK2s I've used in the past, but it does run fairly well.
Ideas?
Thanks,
Wiz

Hi Wiz

LxPupSc 32&64 is ScPup but with LXDE included - and I follow Slackware Current so 15.1 should not be a problem. +9g is the most recent version.

[Wiz57]

@peebee Say peebee, I just had a thought...I know, that's dangerous, ! What do you think about renewing your Slackware Current Puppies? Sort of a testbed for whenever Slackware 15.1 is released. I've been doing a bit of searching around, and noticed that in Slackware-Current packages there are quite a number of newer things, especially glibc (even in the "32bit" X86 repo!!). The main reason for my searches has been one of the later Palemoon 3rd Party builds that although it uses GTK2, it also is built with glibc 2.34, and S15Pup32 is glibc 2.33. I've also toyed with the idea of attempting a glibc update, but that can result in breakage! I have found a Palemoon 3rd Party build based on glibc2.33, but also GTK3, which seems to be a bit more sluggish than the GTK2s I've used in the past, but it does run fairly well.
Ideas?
Thanks,
Wiz

Hi Wiz

LxPupSc 32&64 is ScPup but with LXDE included - and I follow Slackware Current so 15.1 should not be a problem. +9g is the most recent version.

Does LxPupSc still require a 64bit CPU? That was what prevented me trying it out before. The ScPup32s would run on either 32 or 64bit CPUs.
I use your LXDE by ydrv in the old ScPups as well as S15Pup32s, so LXDE is welcome!!

[Wiz57]

@peebee Well, you know how I am, and I just had to try...I downloaded all the glibc2.40 updates I found in the Slackware-Current directory at packages.slackware.com and installed the txz files using PPM into my test install of S15Pup32 250101...everything seems to be OK, haven't noticed any issues as of yet! SO, I'll continue test driving it, maybe try that Palemoon build I found needing newer glibc! Will report any issues I encounter. If it stays stable, may have stumbled across a method to keep 32bit Slackware based Pups somewhat relevant!

[Wiz57]

Still booted into my test version of S15Pup32 with updated GLIBC...tried that 32 bit Palemoon 33.5.1 GTK2 build but still doesn't run. Seems it is built against a different linker or somesuch. Error in LxTerminal as follows:

# palemoon
XPCOMGlueLoad error for file /usr/lib/palemoon/libxul.so:
/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /usr/lib/palemoon/libxul.so)
Couldn't load XPCOM.

So, uninstalled that one went back with the GTK3 build, posting from it now.

LxTerminal reports glibc 2.40 installed

# ldd --version
ldd (GNU libc) 2.40
Copyright (C) 2024 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.
#

Well, that's all for now. If you have any ideas, I'm open to suggestions. I might contact the person that built that GTK2 build and see if they MIGHT consider using a different glib! For now, I'll continue testing this updated glibc S15Pup32 and look for anomolies!

Wiz

[peebee]

Does LxPupSc still require a 64bit CPU?

The LxPupSc32 iso does ship with a 64-bit kernel but that can be replaced with a 32-bit kernel - for example from S15Pup32.....

[Fenyo]

Hello,
If you want you can try my latest 33.5.1 build, it is specifically for old distros, it is already running with the minimum glibc 2.17 and GTK2 of course.
Other retro builds can be found here.

[Wiz57]

Hello,
If you want you can try my build, it is specifically for old distros, it is already running with the minimum glibc 2.17 and GTK2 of course.
Other retro builds can be found here.

Thanks for the offer, but the old Acer is running newer Palemoon pretty well. I'll keep it in mind if the time comes that Steven Pusser's MX 21 builds are no longer updated. By the way, on the Acer, I run NewMoon, latest available, from Roytam1 when booted into Windows XP...any correspondence with him?
I may give your NewMoon build a run if I boot the Acer into the old Slacko 6.3.2!

[Fenyo]

Hello,
If you want you can try my build, it is specifically for old distros, it is already running with the minimum glibc 2.17 and GTK2 of course.
Other retro builds can be found here.

Thanks for the offer, but the old Acer is running newer Palemoon pretty well. I'll keep it in mind if the time comes that Steven Pusser's MX 21 builds are no longer updated. By the way, on the Acer, I run NewMoon, latest available, from Roytam1 when booted into Windows XP...any correspondence with him?
I may give your NewMoon build a run if I boot the Acer into the old Slacko 6.3.2!

Also linked above is the latest 33.5.1 build.

[Wiz57]

Hello,
If you want you can try my build, it is specifically for old distros, it is already running with the minimum glibc 2.17 and GTK2 of course.
Other retro builds can be found here.

Thanks for the offer, but the old Acer is running newer Palemoon pretty well. I'll keep it in mind if the time comes that Steven Pusser's MX 21 builds are no longer updated. By the way, on the Acer, I run NewMoon, latest available, from Roytam1 when booted into Windows XP...any correspondence with him?
I may give your NewMoon build a run if I boot the Acer into the old Slacko 6.3.2!

Also linked above is the latest 33.5.1 build.

Fenyo, I installed your centos7 build of Newmoon 33.5.1 successfully in an older ScPup 32 bit I keep around...
so with that on my mind, I then extracted the contents into a directory under /tmp, then extracted the 33.5.1 build for Mx21 by Steve Pusser into another directory under /tmp. OK, then I did a comparison of the various directory structures of the two...then did a copy and replace of the same directories in the Mx build with the same from your Newmoon build! When finished, opened a terminal in the now changed Mx directory and ran dir2sfs and created a newmoon.sfs. Next I copied this sfs to a storage location. Deleted the directories I had extracted the files to under /tmp, rebooted. The next step was to uninstall via PPM the Mx21 build of Palemoon 33.5.1, when that finished, I opened my file manager to the storage location, click on the newmoon.sfs and choose to install...it worked! Once it loaded, rebuilt the start menu, and fired it up! I'm here now posting from your NewMoon build of Palemoon 33.5.1 32 bit GTK2! As I figured it would, loading the sfs found all my add-ons and customizations. This may be something we can work together on in the future as well to kind of keep an updated Palemoon/NewMoon browser available for 32 bit Puppys!
After I give this a few tests, I might upload the sfs to the Forum, if anyone is interested.
ps...Palemoon released version 33.6 recently...so when you get a new build ready let me know!
Wiz
ps...I did have to modify the "desktop" menu entry to display a sort of generic web browser icon so as not to infringe on Moonchild Productions. The one that was put in via dir2sfs just gives an "executable" icon since I don't think I put any MCP branded icons in it. I can work on finding a better icon sometime.

[Wiz57]

After multiple tests, loading, unloadiing the sfs, in a couple of my 32 bit S15Pup32s, as well as an older ScPup 32 bit, I think it's time to share my newmoon.sfs for others running 32 bit Puppys to trial. This was made from Fenyo's CentoOS 7 builds, needs at least glibc2.19 and gtk2.

LINKS SUPERSEDED BY UPDATED SFS, SEE BELOW!

Note: this is 32 bit, an unofficial build of Palemoon 33.5.1, though it is named "newmoon" the executable program and supporting files are palemoon. If you have problems, PLEASE do not post on the PaleMoon Forum! You will be dismissed as an idiot and told to take the issues up with the developer of the 3rd party build!
You have been warned! See "Help. About" in the Menu Bar.

edited to remove older links, new sfs available below, Wiz57

[Fenyo]

Sure, feel free to use it, that's why it's being made.

[Wiz57]

I have updated my SFS based on Fenyo's CentOS 7 GTK2 build of NewMoon (Palemoon) 32 bit version 33.6.0, also runs on older GLIBC 2.19, IIRC. The shared links are to the newmoon-33.6.0-gtk2.sfs and the corresponding MD5 hash if desired. Test it out, runs well in Slackware based S15Pup32 for me.
Thanks go to Fenyo for building this for us!
https://1drv.ms/f/c/753f8bf9abaabf8f/En ... Q?e=ANBRnj

[thinkpadfreak]

Hello.
It seems that, on S15Pup32 (release 250301), palemoon and firefox can't play videos in h264/mp4 format.
Those browsers depend on ffmpeg to play h264/mp4 videos, and I suspect that something is wrong with it.

The problem does not occur on the release 250101.

[Clarity]

Hello @thinkpadfreak

Hello. ... The problem does not occur on the release 250101.

Does this occur when you run the 64bit 250101 version?

[thinkpadfreak]

Does this occur when you run the 64bit 250101 version?

I have remained at S15Pup64-250101, and it does not have the problem.
Today I tried S15Pup64-250301, and found that the same problem occurs.