VoidPup32 and VoidPup64 Discussion

[peebee]

But I take from this that the lack of ffplay may not be intentional. Even though the pup calls itself "Void" I don't regard it as a "cut-down" distro. Also I don't know how common such setup is. I always assumed that a distro, when it includes ffmpeg, it would also include /ffprob/ffplay.

It is intentional in the sense that SDL2 is 727K and ffplay is 334K....... so quite big......

You could try installing ffplay:
vpm i ffplay

which should also install dependencies including SDL2

You may also have to force install ffmpeg to update the shipped version to 4.4.3:
vpm fi ffmpeg

https://voidlinux.org/packages/?arch=x86_64&q=ffplay

[peebee]

+12 is available.

[Vverve]

peebee and all , round of applause for voidpup(+kernels+browser+++),using only 64 no 32 bit test.
now +12 ,been in and out of voidpup64 before +10 only testing some sfs,using it almost daily since.

- devx sfs break chromium run-as-spot lx sfs ,start ok if unloaded. Took i while to figure it out...

-Does wake up from suspend work normaly for some of you?
or is i again my capricious intel everything tablets the problem?
on those computers who both got wacom pen/touch fresh first boot etc/acpi/action/suspend freeze the desktop ,niet ,
pen&touch works but no access to menu ,files, power button ok ,cold boot required .
If booting from save folder ,it suspend but restartx on wake up.

-Firmware iwlwifi-8000C-36.ucode is missing ,no problem.

-may worth updating xf86-input-wacom from 0.40.0_1 to 1.1.0_1

-cellwriter is very deeply integrated in there !!! internationalisation a pain and removing the thing too,if possible,i dont understand the choice here ,esthetic?
Installed that trusty some say ugly xvkbd & my pill for tablets ,
easytroke... unmaintained but works very very well no vpm pkg , deb pkg works.
+xcompmgr ,light ,no gui ,just to add transparency to xvkbd .

Are devs robots created by devs?
do they stop between power outages ?

[Clarity]

Could you explain

...Are devs robots created by devs?...

Curious

[Vverve]

Clarity ...the robots ?
they work until they break...or someone pull the plug.
i should have added one smiley emoj!
Its nothing of a real question...lack of seriousness ?
I do believe developers are real breathing humans.

[Vverve]

I'm used to peculiar hardwares related glitches , it could be just another one.
Just ask for details if it worth digging those.
Posting from Voidpup64 here ,its fast , get all the jobs done+
void linux community + plenty of online instructions about a lot of options/pkg.
Hoping you all enjoy working on it as much as i do using it.
A bowing user.

note: i do like to run latest peebee lx kernels,6.0.12 now , but all my glitches been tried with ,if +12 isos/kernel +12 devx supplied original ones.

[bert07]

Abiword not working in +12.

# abiword
MESA-LOADER: failed to open iris: /usr/lib64/dri/iris_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: iris
MESA-LOADER: failed to open zink: /usr/lib64/dri/zink_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: zink
MESA-LOADER: failed to open kms_swrast: /usr/lib64/dri/kms_swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib64/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
failed to load swrast driver
MESA-LOADER: failed to open iris: /usr/lib64/dri/iris_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: iris
MESA-LOADER: failed to open zink: /usr/lib64/dri/zink_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: zink
MESA-LOADER: failed to open kms_swrast: /usr/lib64/dri/kms_swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib64/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
failed to load swrast driver

(abiword:13973): GLib-CRITICAL **: 01:30:16.114: g_strsplit: assertion 'string != NULL' failed
MESA-LOADER: failed to open iris: /usr/lib64/dri/iris_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: iris
MESA-LOADER: failed to open zink: /usr/lib64/dri/zink_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: zink
MESA-LOADER: failed to open kms_swrast: /usr/lib64/dri/kms_swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib64/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
failed to load swrast driver

(abiword:13973): GLib-CRITICAL **: 01:30:16.132: g_strsplit: assertion 'string != NULL' failed

(abiword:13973): Clutter-CRITICAL **: 01:30:16.132: Unable to initialize Clutter: Unable to initialise the Clutter backend: no available drivers found.

** (abiword:13973): WARNING **: 01:30:16.132: clutter failed -3, get a life.
Aborted
#

[peebee]

Void is updating to glibc-2.36 - VPup+13 will be out shortly to match (hopefully)..........
https://voidlinux.org/packages/?arch=x86_64&q=glibc

This is one of the BIG Void updates that will cause problems - expect other VPM installs to fail until VPup catches up!

DO NOT DO SYSTEM UPDATES FOR THE MOMENT - you will kill the system!!

[MochiMoppel]

@peebee Currently testing VoidPup32-22.02+12

ffmpeg essentially reports a violation of its usual GNU GPL license terms (see end of output):

Code: Select all

# ffmpeg  -L 
ffmpeg version 4.0 Copyright (c) 2000-2018 the FFmpeg developers
  built with gcc 7.3.0 (GCC)
  configuration: --prefix=/usr --libdir=/usr/lib --enable-libmp3lame --enable-libx264 --enable-libx265 --enable-pthreads --enable-small --enable-postproc --enable-libvorbis --enable-gpl --enable-shared --enable-nonfree --enable-libopencore-amrnb --enable-libopencore-amrwb --disable-debug --enable-bzlib --enable-zlib --enable-libspeex --enable-version3 --enable-runtime-cpudetect --enable-libxcb --enable-libtheora --enable-libxvid --enable-swscale --enable-libvpx
  libavutil      56. 14.100 / 56. 14.100
  libavcodec     58. 18.100 / 58. 18.100
  libavformat    58. 12.100 / 58. 12.100
  libavdevice    58.  3.100 / 58.  3.100
  libavfilter     7. 16.100 /  7. 16.100
  libswscale      5.  1.100 /  5.  1.100
  libswresample   3.  1.100 /  3.  1.100
  libpostproc    55.  1.100 / 55.  1.100
This version of ffmpeg has nonfree parts compiled in.
Therefore it is not legally redistributable.

Cause for concern?

[rockedge]

saw this last post and was curious so a test in KLV-Airedale:

Screenshot_2022-12-18_07-51-31.png (108.32 KiB) Viewed 7973 times

[peebee]

Abiword not working in +12.

Hi @bert07

Abiword works for me ................

menu -> setup -> voidpup app install -> abiword
+
vpm fi libdb

Screenshot.png (93.52 KiB) Viewed 8149 times

[OscarTalks]

As a test I compiled abiword-3.0.5 from source in VoidPup, configured for GTK2 and with 7 plugins. Looks clean as a whistle in terminal. The rsvg plugin might have been nice to add, but it seems to look for the glib headers in the wrong location. Maybe possible to fix that but for now I built with that plugin not enabled. Building GTK3 version also works but there are some warnings in terminal. I could upload builds but maybe it is not needed if the provided builds work. For my personal packages I remove all those translation ".strings" files which add to the size quite a lot and which are no use to me. Also, abiword is seen by some as rather unstable so it is never a good idea to use it for anything where a crash or a loss of data would cause distress. I think this may be one example of where installing via the package manager is problematic and compiling from source is much better.

[peebee]

@peebee Currently testing VoidPup32-22.02+12

ffmpeg essentially reports a violation of its usual GNU GPL license terms (see end of output):

Cause for concern?

Hi @MochiMoppel - hmmmmmmmmmm

That is the case for many Pups (BionicPup32, JammyPup32, S15Pups etc.) where ffmpeg is built using the petbuild on GitHub:
https://github.com/puppylinux-woof-CE/p ... 0.petbuild

which contains:
--enable-nonfree

What advantages does compiling with --enable-nonfree offer?

This option alone gives no advantages. It is required for some external libraries that are considered to be non-free. You can view which libraries require this in the source code of the configure file: refer to EXTERNAL_LIBRARY_NONFREE_LIST (and HWACCEL_LIBRARY_NONFREE_LIST). As of this answer these include: decklink, libndi_newtek, libfdk_aac, openssl, libtls (and cuda_nvcc, cuda_sdk, libnpp).

[dimkr]

This old ffmpeg is 4 years old, why not just replace it with Void's one?

[OscarTalks]

I think using Void's one would drag in extra dependencies which would be considered surplus to requirements for a Puppy. The best approach, in my opinion, is to create a custom Puppy build of ffmpeg, but latest version of 4.4.x branch so that all the library version numbers will match up with all the other Void packages which link to ffmpeg libs. The other thing to do is run ./configure --help and review all the configure options that are being used. Some of those will have changed (as well as included packages within the Puppy) since those in the older ffmpeg package were chosen.

[peebee]

+13 with glibc-2.36 (and gcc-12.2.0 in devx) is available

[Marv]

OK, took a deep breath and dove in. Frugal install to SSD on the Fujitsu S761:

Code: Select all

# inxi -b
System:    Host: puppypc29015 Kernel: 6.1.0-lxpup64 x86_64 (64 bit)
           Desktop: LXDE (Openbox 3.6.1) Distro: VoidPup64 22.02
Machine:   Device: laptop System: FUJITSU product: LIFEBOOK S761 serial: R1Y00453
           Mobo: FUJITSU model: FJNB225
           UEFI [Legacy]: FUJITSU // Phoenix v: Version 1.17 date: 03/14/2012
Battery    CMB1: charge: 56.0 Wh 100.0% condition: 56.0/56.0 Wh (100%)
CPU:       Dual core Intel Core i5-2520M (-HT-MCP-) speed/max: 811/3200 MHz
Graphics:  Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
           Display Server: X.org 1.21.1.5 drivers: intel (unloaded: modesetting,fbdev,vesa)
           tty size: 80x24 Advanced Data: N/A for root
Network:   Card: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express)
           driver: ath9k
Drives:    HDD Total Size: 250.1GB (34.3% used)
Info:      Processes: 230 Uptime: 14 min Memory: 372.4/5779.7MB
           Client: Shell (bash) inxi: 2.3.8 

First a pristine install, no adrv, no fdrv. Clean boot, clean dmesg, excellent idle characteristics, SNS wifi connection normal, lidsuspend working. Libinput still insisting I have no physical touchpad buttons -no surprise there-

Next @peebee ydrv added in, still stock kernel. Transition to LXDE and PcManFM as expected, clean dmesg, normal wifi connection with SNS, CPU and memory use edge up a bit but still very good and basically unchanged from +12. Libevent touchpad handling still sub-par.

Then the breath-holding part. Kernel 6.1.0 swapped in, along with my savefile from +12 with the synaptics touchpad drivers,symlinks to portables, tray, PWF for connection, etc. Aah, all good. As above, clean boot and dmesg, good idle characteristics, nice touchpad control, lidsuspend, etc. Posting from that now in a portable Slimjet.

One note on suspend. I use it a lot, probably 10x per day with the laptops, so it has to just work. I noted that after a LOT of suspend/use with the 6.1.0 or 6.0.8 kernels suspend would just stop working. What was happening -on this hardware anyway- was that the tpm_tis process was not shutting down correctly. What showed up in dmesg was:

Code: Select all

[ 5631.852187] tpm_tis 00:06: PM: failed to suspend: error 28

Searching, this has been around for a decade or so with lots of kernel patching to do an end run on it. I'd never seen it before. I did try the usual fixes, tpm disabled in BIOS firmware, blacklisting etc. and they didn't do the trick. What worked for me was to rmmod tpm_tis prior to suspend and modprobe it post suspend in /etc/acpi/actions/suspend.sh. Not the first patch there I don't have enough time on S15Pup64 or LxPupSc64 to see if it shows up there with the newest kernels. One of those darn intermittants, but at least once it failed it stayed failed and showed something useful in dmesg.

VoidPup64 continues as the daily, playing with a minimized savefile-less fossapup64_9.6. Solid, polished and very good at this point but after LXDE, the JWM panel still drives me nuts.

Thanks and Cheers,

[OscarTalks]

Testing dunst-1.9.0 desktop notification daemon
With new recursive icon lookup feature
Compiled in VoidPup +13 with newer glibc so may not work in earlier VoidPup builds
Some more information in the "Desktop" section here http://forum.puppylinux.com/viewtopic.php?p=76264
Running cleanly in my brief tests

[rockedge]

While waiting for the field tech to fix the fiber optic by switching on connection that they accidentally turned off working on a neighbor's new fiber optic line, I am going to test this Dunst package if it will work as is in KLV-Airedale. More or less to see what is compatible between VoidPup's and KLV's

[peebee]

+14 is the same as +13 except for ffmpeg update (openssl no longer enabled)

92c38850c913818bf1032b8f8e8cf027 VoidPup32-22.02+14.iso
701e6a041c6501cf83cab47214212980 VoidPup64-22.02+14.iso

[Marv]

Quick bump from +13 to +14on my 64b frugal install, scrubbed savefile and 6.1.1 kernel. The usual Fujitsu S761 hardware. Uneventful.

Thanks,

[OscarTalks]

Viewnior-1.8 is installed and working from left click as default image viewer and right-click menu on image files in ROX, but it is missing a main menu entry.
A quick edit of /usr/share/applications/viewnior.desktop will fix this. Change the Categories line from Categories=X-Uncategorized to Categories=X-Graphic-viewer
along with any other edits you may wish to do. Save and then run fixmenus and jwm -reload or use Menu > Setup > Menu manager > "OK"

[mikeslr]

Just some info related to OscarTalks post. As I discovered when working on the lazpaint pet, just 'Graphics' is not recognized by Puppys as a valid category, i.e. one which will show up on the Menu. Consequently, when using a package designed for some other LInux its /usr/share/applications...desktop' Categories= argument has to be changed.

[peebee]

@OscarTalks will change for next build - thanks.

@mikeslr needs a PR to e.g. lines 43-:
https://github.com/puppylinux-woof-CE/w ... aphic.menu

<Category>Graphics</Category>

[OscarTalks]

The upgrade of ffmpeg from 3.x.x to 4.x.x in VoidPup64 version +14 is welcome, but it does mean that some of my previous application builds needed re-compiling. I have now done that. These are mostly intended for my own experimentation and use, but others are welcome to inspect and test them. In vlc I added live555 for rtsp support. With audacious and guvcview I have compiled with rpath set. This enables location of all the private runtime libraries in a directory where they can never conflict with other programs. It also avoids having to use a wrapper script and keeps the main binary as an ELF executable.
http://smokey01.com/OscarTalks/vlc-3.0.18_1.x86_64.xbps VLC as .xbps
http://smokey01.com/OscarTalks/vlc-3.0. ... 4-void.sfs VLC as .sfs
http://smokey01.com/OscarTalks/audaciou ... 86_64.xbps audacious as .xbps
http://smokey01.com/OscarTalks/guvcview ... 86_64.xbps guvcview as .xbps

[Clarity]

The upgrade of ffmpeg from 3.x.x to 4.x.x in VoidPup64 version +14 is welcome... In vlc I added live555 for rtsp support ...

+1
Great for LAN camera data streams.

Thanks

[Clarity]

Is forum's PKG2 "a thing" for this PUP (or WoofCE)?

[Clarity]

@peebee I hope this is where you want us to share findings of your VoidPUP64. If not, please move this post, appropriately.

I have tested 3 of your PUPs, in the last hour by booting each's ISO to their desktops.

• LxPUPSc64 and S15PUP64 boot and operate without issue. It so simple to be able to boot these and go directly onto the network with the OOTB ability to share the common public folder this PC has. Great to see you are continuing @01micko tradition for this SMB ability in the "Slacky" ISO you continue to provide. Thanks for continuing.
  .
  There is one minor issue that exist with ALL of your recent ISOs. The 'findsmb' utility that @01micko has built-in to the Slacko family, is missing in your distros. ... probably an oversight. Could you add this to your samba builds, please?
  .

• VoidPUP64. For Samba services both Server as well as Client features including findsmb, the PUP has major problems for packages. If possible to avoid user hunting, could either

  1. SAMBA be built-in OR

  2. clients be built-in OR

  3. when the SSM is initially clicked it open a message window giving the user the option to install it.

  Either of these 3 would reduce user headaches.

NO response to this post is begged. If you think this would help user use, it will show up in future releases of your timely ISOs.

Your work is GREATLY appreciated

[peebee]

[*]VoidPUP64. For Samba services both Server as well as Client features including findsmb, the PUP has major problems for packages. If possible to avoid user hunting, could either

1. SAMBA be built-in OR

2. clients be built-in OR

3. when the SSM is initially clicked it open a message window giving the user the option to install it.

Either of these 3 would reduce user headaches.
[/list]

3 has been implemented for a long time and works OK:

Screenshot.png (229.16 KiB) Viewed 6547 times

.

Screenshot(1).png (229.04 KiB) Viewed 6547 times

.

Screenshot(2).png (241.22 KiB) Viewed 6547 times

[Clarity]

Tested your latest S15, just last night via QEMU. SSM, SAMBA, and client services are working OOTB exactly as the old Slacko.

Thanks @peebee, muchly, for the continued user friendliness in your work.