Puppy Linux Discussion Forum

jrb wrote: Mon Mar 18, 2024 3:55 am

Hi @peebee, just thought I'd let you know how much I'm enjoying the VoidPups. Nicely done.

Thanks @jrb

xml2 is needed to manipulate the Void repo databases.....

The Firefox sfs from Menu -> Internet -> Get Web Browser
plays sound OK - it includes apulse.

After vpm up

Deadbeef installs and plays OK, but the .desktop is not JWM compliant - you have to remove the F% from the Exec line

# vpm i deadbeef
[vpm]  Installing packages: deadbeef (xbps-install -S deadbeef) ... 
[*] Updating repository `https://repo-default.voidlinux.org/current/x86_64-repodata' ...
39 packages will be downloaded:

39 packages will be installed:
  faad2-2.11.1_1 libaom-3.8.1_1 libde265-1.0.12_1 libheif-1.17.5_1 
  libjxl-0.10.2_1 libspectre-0.2.12_1 imlib2-1.12.2_2 celt-0.11.3_3 
  lame-3.100_2 libva-2.20.0_1 libvdpau-1.5_1 ocl-icd-2.3.2_2 
  libavutil-4.4.4_6 libdav1d-1.3.0_1 libspeex-1.2.1_1 
  libsvt-av1-1.7.0_1 libswresample-4.4.4_6 xvidcore-1.3.7_1 
  libavcodec-4.4.4_6 libmodplug-0.8.9.0_1 mbedtls-2.16.12_1 
  librist-0.2.7_1 librtmp-2.4.20161210_10 libsrt-1.5.3_1 
  libavformat-4.4.4_6 libasyncns-0.8_9 libgomp-13.2.0_2 
  libfftw-3.3.10_2 libjack-1.9.22_1 libsoxr-0.1.3_2 libtdb-1.4.9_2 
  sbc-2.0_1 speexdsp-1.2.1_1 webrtc-audio-processing-1.3_1 
  libpulseaudio-16.1_2 libwavpack-5.6.0_1 libzip-1.10.1_1 
  opusfile-0.12_3 deadbeef-1.8.8_3 

Size to download:               24MB
Size required on disk:          65MB

Hi! Thank you for working on voidpup, it is one of my favorite pups to use right now.

I downloaded a current VoidPup32 a couple days ago and I am trying it out on an old 32-bit netbook right now. It runs very well!

But I did have one problem: there were no CA certificates installed, so things like vpm, curl, and other programs could not do HTTPS. Basically the /etc/ssl/certs/ folder was completely empty.

I manually ran this command in a terminal:

update-ca-certificates

And that fixed it.

cheers!

artemis wrote: Thu Apr 11, 2024 8:57 pm

But I did have one problem: there were no CA certificates installed,

Hi @artemis

I don't see this problem......../etc/ssl/certs is populated - see screenie
Was this a pristine boot?
I suspect you have /opt/vpup/vpm_holds which affects /root/Startup/00_start_vpup

vpm up works ok for me:

# vpm up
[vpm]  Running system update (xbps-install -Suv) 
[*] Updating repository `https://repo-default.voidlinux.org/current/i686-repodata' ...

Updated my 240223 install of Voidpup64 (rolled back to that for non-malware xz) to the 240413 version. My usual 2nd gen i5 based laptop, conventional frugal install to SSD with savefile.

Clean dmesg, excellent idle resource use, normal daily operation with all portables continuing to run correctly. /etc/ssl/certs also filled correctly here. The 6.6.25 kernel update noted with no issues seen there. No multimedia checks as yet. Lidsuspend and resume normal.

Posting from that install using the current Brave, portable, run-as-spot.

Thanks,

Update on 04/22/2024: Update from the 20240413 version to the 20240420 version (with 6.6.27 kernel) on bare metal went fine here. The usual Fujitsu S761 hardware, install and tests as above.

Update on 05/04/2024: Updated my 240420 install to the 240504 version. 6.6.29 kernel noted. No hitches or issues seen so far, testing and hardware as above. As part of getting localsend working -no problems in Voidpup64- I pulled MPV from my install (I don't use it, put it in to test it and VPM) using VPM and used an interim ydrv to shrink the savefile. Nice clean uninstall by VPM and the result runs very well from the ydrv sans savefile! Haven't made the downsized savefile as yet.

Update on 05/23/2024: My install is now at VoidPup64-22.02-240518. No issues to note in daily use, configuration and tests as above. I did add osmo version 0.4.4 to the install using a LxPupSc64 repo pet (a very quick look in the Void repos didn't show it but I wasn't thorough as I had the pet) and linked it to my shared profile on my data partition since I use the calendar daily. Kernel 6.6.31 noted. Posting using the current Brave portable (run-as-spot) in the install now.

Update on 06/03/2024: Install detailed above updated to the 240602 version with the 6.6.32 kernel. Configuration and tests as above. No issues seen on boot or with a days daily use on the i5 based Fujitsu S761 laptops. Posting from that install now using the portable Brave browser. A note: gnumeric not present so I use the LibreOffice spreadsheet run as a portable in this install. Just works.

Update on 07/04/2024: Install above updated to the 240703 version with the 6.6.36 kernel. Config and tests as above. Smooth update, tests as above with no issues seen. Continues to be a solid daily driver.

Update on 07/21/2024: Bumped above install to the 240717 version. Smooth update, tests and lack of issues as above. Using as my 'daily' currently.

Bump to the 08/03/2024 version in the install above. No hitches, no glitches seen in daily use. 6.6.43 kernel noted.

Thanks @peebee

@peebee

Just trying out VoidPup64-22.02-240717.iso

Wanted to bring to your attention some cosmetic issues.

Missing icon for PupMTP

The 'top' section of the Menu is huge .......... is this intentional?

Also, when I loaded the DevX.SFS, Cmake does not function correctly.

Thanks @Jasper

cppdap added to devx for next build

will investigate other issues

@peebee

Strange behaviour of pNote application.

It does startup and is huge ...... the height in the script needs to adjusted (?)

It disappears immediately, so text cannot be input

Hello @Jasper

I did not see the large menu icons that you reported - I suspect something in the way you've setup your desktop - possibly also explaining pNote ....... please try again with a pristine install with no changes. Thanks.

pNote height is correct - see /usr/sbin/pnote line 53:

#find height of screen
TMP=`xwininfo -root | grep -m 1 '\geometry' | cut -f4 -d ' ' | cut -f2 -d 'x' | cut -f1 -d '+'`
HEIGHT=$((TMP-27)) #minus main-tray
[ ! "$HEIGHT" ] && HEIGHT=571 #in case

#run app
export pNote='
<window title="pNote" width-request="250" height-request="'$HEIGHT'" decorated="false">
<edit left-margin="5" wrap-mode="2"><variable>PAD</variable><input file>'$HOME'/.pnote</input></edit>
<action signal="leave-notify-event">echo "$PAD" | xclip -i -selection clipboard</action>
<action signal="leave-notify-event">check_exit</action>
</window>'
gtkdialog -p pNote -G +0+0 --styles=/tmp/pnote_gtk3.css

@peebee

Tried this again as suggested on a pristine installation.

Encounter the same issue

Screen resolution 1920x1080

@peebee

The file/script is identical to the one in JammyPup64 but still exhibits the same behaviour.

Works fine in JammyPup64 and is the correct size.

VoidPup ISO file boot results published here.

@peebee

Thank you, the latest DevX built for VoidPup64-22.02-240803 has CMake functioning perfectly

Updated my 240803 VoidPup64 install to the 240824 version. This is done on the usual second gen i5 Fujitsu S761, an LXDE'd non-savefile ydrive frugal install to SSD. Clean dmesg, all portables continue to run normally, very low idle resource use,

ffmpeg will not start so pmusic fails. It is fine in my install of the 240803 version. ffmpeg is looking for libx265.so.199, libx265.so.209 is on board. A symlink there gets ffmpeg a bit closer but there seems to be a problem with the libxvidcore lib. Install/versions of that look ok. A complete reinstall of ffmpeg using the vpm pkg manager does bring ffmpeg and pmusic to life but it reinstalls a LOT. That's as far as I've gotten with that.

Jim

Marv wrote: Sat Aug 24, 2024 8:29 pm

Updated my 240803 VoidPup64 install to the 240824 version. This is done on the usual second gen i5 Fujitsu S761, an LXDE'd non-savefile ydrive frugal install to SSD. Clean dmesg, all portables continue to run normally, very low idle resource use,

ffmpeg will not start so pmusic fails. It is fine in my install of the 240803 version. ffmpeg is looking for libx265.so.199, libx265.so.209 is on board. A symlink there gets ffmpeg a bit closer but there seems to be a problem with the libxvidcore lib. Install/versions of that look ok. A complete reinstall of ffmpeg using the vpm pkg manager does bring ffmpeg and pmusic to life but it reinstalls a LOT. That's as far as I've gotten with that.

Jim

Thanks for report - ffmpeg needs rebuilding to match libx265.......... I will delete 240824 for now.

Will this v240824 ISO file name change to v240825? OR ... ???

VoidPup64 v240810 terminal comands check for my admin tools:

# findsmb
bash: findsmb: command not found
# btop
bash: btop: command not found
# tldr
bash: tldr: command not found
# smbclient -U% -L localhost
bash: smbclient: command not found
# uname -a
Linux VoidPupTest 6.6.43 #1 SMP PREEMPT_DYNAMIC Thu Aug  1 10:29:10 UTC 2024 x86_64 GNU/Linux
# 

Booted bare-metal via Ventoy

These, have usefulness. Am I to assume @peebee, or other developers on this project, you would like users to re-install these tools each new release? We know things can go wrong when left to us, users; for example mistyping, misunderstanding, miss-directed usage, etc.

Clarity wrote: Sun Aug 25, 2024 8:47 am

VoidPup64 v240810 terminal comands check for my admin tools:

Code: Select all

# findsmb
bash: findsmb: command not found
# btop
bash: btop: command not found
# tldr
bash: tldr: command not found
# smbclient -U% -L localhost
bash: smbclient: command not found
# uname -a
Linux VoidPupTest 6.6.43 #1 SMP PREEMPT_DYNAMIC Thu Aug  1 10:29:10 UTC 2024 x86_64 GNU/Linux
# 

Booted bare-metal via Ventoy

These, have usefulness. Am I to assume @peebee, or other developers on this project, you would like users to re-install these tools each new release? We know things can go wrong when left to us, users; for example mistyping, misunderstanding, miss-directed usage, etc.

Please understand: I am NOT complaining about this PUP or any others. But, its a little bit of a concern when some WoofCE PUPs have a feature set one-way while others have different-ways. It kinda makes these from this family should have some sort of consistent features WHILE if they are different, maybe a startup utility can be expanded to steer the pristine use to a page of consistent features to be OOTB added.

This way, if some developer chooses to create an inconsistent ISO for distribution sharing on the forum, he/she would indicate in their opening post that their offering is inconsistent.

YES, this means 'consistent' will need to be defined as the WoofCE base. And those built outside of the base (features beyond the base or removed from the base) would be inconsistent requiring an opening post to indicate differences or features missing.

I think consistent (base) could be simple in structure; much like what @01micko provided, what @666PhilB provided or similar to the set BarryK is providing; or even the KLs as the developers there seem to try to provide consistent feature packaging in all of their distro offerings. When these distros are booted to prisine desktop, including the forum's DOGs, the feature set in their menus and their desktop apps, ALL SMELL THE SAME so to speak! Thus any user practically instantly knows what/where to do next. Thus ... 'consistency' per se although foundationally they all differ.

This all boils down to the earlier threads elsewhere on the forum which garnered a lot of member attention for "what makes a Puppy?" In review of those discussions, I summarize: 'A common set of OOTB features!'

This is just a view...nothing more.

Booted SG2D and launched VoidPup64 allowing it to take the default menu item where it timed out to start the booting.

This allow the v240810 version to find and automatically use the prior save-session in the Sessions folder on the Persistence drive. Thus it is using the SAVESPEC file for directions.

Upon desktop, I opened a terminal to use VPM. Here are a result: "Should I be concerned?"

# uname -a
Linux VoidPupTest 6.6.43 #1 SMP PREEMPT_DYNAMIC Thu Aug  1 10:29:10 UTC 2024 x86_64 GNU/Linux
# vpm sync
[vpm]  Synchronizing remote repository data: (xbps-install -S): 
[*] Updating repository `https://repo-default.voidlinux.org/current/x86_64-repodata' ...
[vpm]  [xbps-install -S] return code: 0 
# vpm update
[vpm]  Running system update (xbps-install -Suv) 
[*] Updating repository `https://repo-default.voidlinux.org/current/x86_64-repodata' ...
Found xbps-0.59.2_3 in repository https://repo-default.voidlinux.org/current
The 'xbps' package must be updated, please run `xbps-install -u xbps`
[vpm]  Updating xbps (xbps-install -u xbps) 

Name    Action    Version           New version            Download size
libxbps update    0.59.2_2          0.59.2_3               137KB 
xbps    update    0.59.2_2          0.59.2_3               109KB 

Size to download:              247KB
Size required on disk:         790KB
Space available on disk:      7470MB

Do you want to continue? [Y/n] 

[*] Downloading packages
libxbps-0.59.2_3.x86_64.xbps.sig2: 512B [avg rate: 15MB/s]
libxbps-0.59.2_3.x86_64.xbps: 137KB [avg rate: 1783MB/s]
libxbps-0.59.2_3: verifying RSA signature...
xbps-0.59.2_3.x86_64.xbps.sig2: 512B [avg rate: 21MB/s]
xbps-0.59.2_3.x86_64.xbps: 109KB [avg rate: -- stalled --]
xbps-0.59.2_3: verifying RSA signature...

[*] Collecting package files
libxbps-0.59.2_3: collecting files...
libxbps-0.59.2_2: collecting files...
xbps-0.59.2_3: collecting files...
xbps-0.59.2_2: collecting files...

[*] Unpacking packages
libxbps-0.59.2_2: updating to 0.59.2_3 ...
libxbps-0.59.2_3: unpacking ...
xbps-0.59.2_2: updating to 0.59.2_3 ...
xbps-0.59.2_3: unpacking ...

[*] Configuring unpacked packages
libxbps-0.59.2_3: configuring ...
libxbps-0.59.2_3: updated successfully.
xbps-0.59.2_3: configuring ...
chown: unknown user/group root:xbuilder
ln: failed to create symbolic link 'usr/sbin/xbps-alternatives': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-checkvers': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-create': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-dgraph': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-digest': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-fbulk': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-fetch': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-install': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-pkgdb': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-query': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-reconfigure': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-remove': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-rindex': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-uchroot': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-uhelper': File exists
ln: failed to create symbolic link 'usr/sbin/xbps-uunshare': File exists
xbps-0.59.2_3: updated successfully.

2 downloaded, 0 installed, 2 updated, 2 configured, 0 removed.
[vpm]  [xbps-install -u xbps] return code: 0 
# 

I find that I can install PETs on this VP64. Is there a utility somewhere to un-install PET packages?

Using VPM is not listing PET installs.

Marv wrote: Sat Aug 24, 2024 8:29 pm

ffmpeg will not start so pmusic fails. It is fine in my install of the 240803 version. ffmpeg is looking for libx265.so.199, libx265.so.209 is on board.
Jim

VoidPup rebuilt and re-uploaded at version 240825
https://sourceforge.net/projects/pb-gh-releases/files/

My install updated to version 240825. ffmpeg now starts correctly and pmusic plays CDs OK. pmusic icons kind of quirky in my LXDE install, I'll try it in a pristine. At any rate it works.

Thanks,

Checked, it's fine in a pristine boot. Displays and works perfectly.

@peebee ,

Interesting new development for me in VoidPup64 version 240825. For the first time, VoidPup64, like BW64 since version 10.0.3 will not resume after a lidsuspend with the correct touchpad button mappings. (Fujitsu S761 2nd gen all Intel laptops, I have 6) I have a well tested workaround in BW64 and it also now works in the most recent Void, but it entails a long pause on resume as psmouse removal and reinstating using modprobe takes 8 seconds to settle on these laptops.

VoidPup64 version 240803 and all prior versions were just fine in this regard. 240825 fails so it has to be something in the build changing during that 18 day period.

Like BW64, it is kernel and WM independent. and I can isolate it to something in the main SFS. So far I haven't been able to pin it down further. I looked on GitHub for commits to Void in that timeframe and don't see anything that seems relevant. I hope the pox doesn't spread to NoblePup64. It's been just enough of an irk to limit my use of BW64, and now probably VoidPup64 if I can't sort it.

Clarity wrote: Sun Aug 25, 2024 12:21 pm

I find that I can install PETs on this VP64. Is there a utility somewhere to un-install PET packages?

Using VPM is not listing PET installs.

Don't know the answer, but I suspect not. Sometime after Puppys began using alternatives to PPM, and since neither package manager knew what the other was doing, my procedure has been to use the official package manager to install anything it offers and use PaDS or nicOS-Utility>Save2SFS to construct SFSes of pets and other non-official packages. nicOS-Utility>SFS is used immediately after first run to include applications I know I want which will never be found in the Puppy's repository, e.g. masterpdfeditor-4 (which employs the discontinued Qt4 framework).

The hard way to uninstall pets is to look for its 'reference' in /var/packages. That file lists all the components installed and their locations. But the problem is they are installed, and may have overwritten a file you previously installed that is needed for some other application. Deleting it may break something. Hence my aversion to installing anything other than 'official' packages.

Testing the 240907 build in my Fujitsu S761 laptop as an update to my 240803 and 240825 installs. Everything seems ok, clean dmesg, normal operation of all portables, sound, wifi connection, CDs and DVDs, etc. BUT as in the 240825 version, lidsuspend fails -see 2 posts up-. Again, OK in 240803, fails in 240825 and 240907. Something changed in the 18 days between 240803 and 240825 that causes it to fail. For now, I'm back to the 240803 version.

Update on 10 Sept, 2024: OK, I'm back in the saddle with the 240907 version on the S761. I never did fish out what changed in that time period to break resume for me but unlike in BW64 10.0.4-7 where it is necessary to remove and re-modprobe psmouse and then reload touchpad settings, in VoidPup64 so far just reloading the touchpad settings on resume works. No time penalty there and easy to carry in my ydrive.

@peebee

I am using the VoidPup64-22.02-240907.iso

I am guessing that there has been some work done with GTKdialog as the dialog boxes appear a lot crisper to my eyes

@Clarity

You can 'uninstall' Pet packages here:

https://forum.puppylinux.com/viewtopic.php?t=12309

Hello @peebee
If the near future (next couple years) of VoidPUPs will be serviced, should/could @Jasper's finding be a part of either a GUI in utilities or a feature of some package lister?

If PPM is destined toward a decline in WoofCE and increasingly we will be asked to use other package managers instead for these newer distros, then I imagine adding a built-in system feature would be "going against the grain" and counter-productive.

Just couple thoughts

Hi, is there any explanation somewhere what are all of those "drv" or other sfs packages (nlsx, docx devx ydrv adrv fdrv zdrf etc.)?

See here.
https://forum.puppylinux.com/viewtopic.php?t=5818