Vanilla Dpup 9.x (x86 and x86_64) (old thread)

[dimkr]

Vanilla Dpup is moving here.
__

Vanilla Dpup has some cool features:

• The latest 5.10.x kernel with a large selection of drivers, very similar to the Debian Bullseye kernel

• The apt package manager, with support for 32-bit applications (like Steam) on a 64-bit installation and automatic menu update

• PulseAudio and Bluetooth audio support (the Bluetooth tray icon is disabled on x86 to save RAM)

• Tear-free and hardware-accelerated rendering using Xwayland (on x86_64 only, with automated fallback to X.Org if unsupported)

• Firefox, with privacy-oriented default settings and lower resource consumption, plus extra fonts, for a browsing experience comparable to that on large distros

• Almost exclusive use of GTK+ 3 (on x86_64 only), with 3 theme packs that cover both GTK+ 2 and GTK+ 3

• Security features like applications running as spot and auto-enabled firewall

• Speed and responsiveness features, like DNS cache, zstd compression, preinstalled VAAPI drivers and malloc() tuning to reduce waste of RAM

• Power user features like vi as the default editor, keyboard shortcuts and tab completion in the terminal

• Simple installer and updater, with UEFI support and weekly bug+security fixes

• ext4 images that can be written directly to a flash drive to produce a working, persistent installation

• And much more!

__

>>> More Information and Downloads <<<

Please report issues here.
__

The 64-bit build uses GTK+ 3 almost everywhere, but can run GTK+ 2 applications and most old, gtkdialog-based applications:

screeny.png (167.55 KiB) Viewed 7988 times

The much lighter 32-bit build uses GTK+ 2 where possible, but looks almost identical:

screeny32.png (118.55 KiB) Viewed 7987 times

If you want to build Vanilla Dpup yourself, using the latest woof-CE, you have three options:

1. Give up on this idea, and just use prebuilt ISOs of Vanilla Dpup, built once a week using the latest woof-CE, from https://github.com/vanilla-dpup/releases (recommended)

2. Build a Puppy using woof-CE in GitHub Actions - you need a browser and a GitHub account

3. Build Vanilla Dpup locally using woof-CE (warning: it might take a very long time, and might not work if you don't have enough space, a recent enough OS, etc')

To build it locally:

Code: Select all

git clone -b vanilladpup-9.1.x https://github.com/vanilla-dpup/woof-CE
cd woof-CE
./merge2out woof-distro/x86_64/debian/bullseye64
cd ../woof-out_x86_64_x86_64_debian_bullseye64
yes "" | ./0setup
./1download
echo | ./2createpackages
./3builddistro

(or, alternatively, replace "x86_64" with "x86" and "bullseye64" with "bullseye", to build a 32-bit dpup)

You can grab a prebuilt, up-to-date kernel package from https://github.com/puppylinux-woof-CE/w ... el-kit.yml, and extract the .zip to woof-out_*/kernel-out/output before 3builddistro; otherwise, you'll need to run build a kernel, which can take a very long time:

Code: Select all

cd kernel-kit/output
cp 5.10.x-x86_64-build.conf build.conf
./build.sh

[Grey]

Code: Select all

git clone https://github.com/puppylinux-woof-CE/woof-CE
cd woof-CE
./merge2out woof-distro/x86_64/debian/bullseye64
cd ../woof-out_x86_64_x86_64_debian_bullseye64
yes "" | ./0setup
./1download
echo | ./2createpackages
./3builddistro

I tried to build it in Fossapup. After 51 minutes (./3builddistro), the process failed with the message "pinstall.sh aborted before completion". Before these there were a lot of errors "ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored".

[dimkr]

I tried to build it in Fossapup. After 51 minutes (./3builddistro), the process failed with the message "pinstall.sh aborted before completion". Before these there were a lot of errors "ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored".

Try to unset LD_PRELOAD - i.e. LD_PRELOAD= ./3builddistro.

[TerryH]

I attempted to build a vanilla bullseye64. It went well up to installing the kernel. The error message received was :
wget: missing URL

So how do I correct the wget error?

I then downloaded the latest output for the kernel-kit for 5.10.x-x86_64 from github. Regardless of what I put in the huge-kernel directory, re-running 3builddistro failed. The message below, is following extracting and placing all components in the huge-kernel directory.

Code: Select all

Installing HUGE kernel to build/
Please choose the number of the kernel you wish to use
1 ../huge_kernel/huge-5.10-kernel-kit.tar.bz2
2 ../huge_kernel/huge-5.10-kernel-kit.tar.bz2.sha256.txt
1
You chose ../huge_kernel/huge-5.10-kernel-kit.tar.bz2.
Kernel is 5.10-kernel-kit version
tar: huge-5.10-kernel-kit.tar.bz2.md5.txt: Not found in archive
tar: huge-5.10-kernel-kit.tar.bz2.sha256.txt: Not found in archive
tar: Exiting with failure status due to previous errors
/mnt/sda6/woof/woof-out_x86_64_x86_64_debian_bullseye64$ 

What should be placed in the huge-kernel directory?

[Grey]

I tried to build it in Fossapup. After 51 minutes (./3builddistro), the process failed with the message "pinstall.sh aborted before completion". Before these there were a lot of errors "ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored".

Try to unset LD_PRELOAD - i.e. LD_PRELOAD= ./3builddistro.

Yes, it solved the second problem. To solve the first, I had to install patchelf. Then the script swore at the lack of a huge kernel. I slipped him a Fossapup kernel for testing. And then the iso was built.
Why was 9.0.0 built and not 9.0.1?

vanilladpup.png (26.35 KiB) Viewed 7931 times

[dimkr]

I then downloaded the latest output for the kernel-kit for 5.10.x-x86_64 from github. Regardless of what I put in the huge-kernel directory, re-running 3builddistro failed.

You need to download the zip, and extract it to kernel-kit/output.

Why was 9.0.0 built and not 9.0.1?
vanilladpup.png

Because the automated builds put the build number in the version number - see https://github.com/vanilla-dpup/release ... ay.yml#L48.

[Grey]

Because the automated builds put the build number in the version number - see https://github.com/vanilla-dpup/release ... ay.yml#L48.

Now I see

[TerryH]

I then downloaded the latest output for the kernel-kit for 5.10.x-x86_64 from github. Regardless of what I put in the huge-kernel directory, re-running 3builddistro failed.

You need to download the zip, and extract it to kernel-kit/output.

Following doing this the 3 builddistro continued, it then failed at mkisofs. I didn't need the iso, as I was doing a manual frugal install. Following doing a frugal install using the output files and initial set up, I encountered an issue I have never seen before. On shutting down to create a save folder, I encountered an error that stated I hadn't chosen a partition. I had to shutdown without saving. I re-tested this and received the same error, even when selecting different partition. Attached screenshots show the partition selection and the resulting error message.

For a third attempt I created a directory on with the expected save folder name (vanilladpupsave). When I booted with this directory in place, the Save icon was on the desktop on first boot. The first run setup still ran. On shutdown following initial set up, the save folder was saved successfully. The vanilladpup is functioning as expected.

[dimkr]

Thanks @TerryH, I'm investigating this. Looks like /dev/stdout and /dev/stderr are messed up - they're supposed to be symlinks to /proc/self/fd/1 and 2, respectively.

This breaks pupdialog, which in turn, breaks shutdownconfig.

I still don't know what causes this, but I'll find out.

[mikeslr]

Hi dimkr, Thanks for the Puppy.
I grabbed the 64-bit ISO you offered, extracted it to a folder on a USB-Key and ran shinobar's new grub2-config. Booted fine. But like TerryH I ran into a problem, albeit trying to create a SaveFile. On the 3rd go-round, I SFS-loaded nicOS-Utility Suite and used its Make-Save-File option. On reboot it loaded and I was able to save changes (wifi-config) which were used on reboot.

Only just begun to explore this Puppy, but it seems nice and responsive. One thing, under frisbee it offered my wifi-adapter, but to select it had to both select it and click-twice. Is this a default setting? modifiable? or a problem?

[dimkr]

The fix for saving is ready at https://github.com/puppylinux-woof-CE/woof-CE/pull/2515.

I'm testing it, and if it works, I'll trigger a 9.0.3 build (without waiting until next week) with the fix.

Only just begun to explore this Puppy, but it seems nice and responsive. One thing, under frisbee it offered my wifi-adapter, but to select it had to both select it and click-twice. Is this a default setting? modifiable? or a problem?

To be honest, I don't use frisbee (and avoid fixing bugs in frisbee, SNS, etc'). I'm going to remove it from Vanilla Dpup soon:

https://github.com/puppylinux-woof-CE/woof-CE/pull/2514

EDIT: the fix works, triggered the 9.0.3 build job

EDIT 2: 9.0.4 will fix tray icon right-click - https://github.com/puppylinux-woof-CE/woof-CE/pull/2516

[TerryH]

To test the Save Folder creation I manually edited the rc.sysinit and update the puppy_vanillapup_9.0.0.sfs. I then booted with pfix=ram. On shutdown the save folder was created successfully.

On an additional boot with pfix=ram, I attempted to change the hostname in the initial set up. The first message that shows this step was successful was displayed, but the subsequent steps did not run. Following this, the cursor worked but any executable link from an icon or menu entry did not execute when clicked. I had to hard shutdown to exit.

[Clarity]

Hi @dimkr

This thread is under the forum topic "Built from woof-CE Recipes" where this OP statement says

The dpup (Puppy based on Debian packages) the unmodified woof-CE

But the boot-loader and stanza do NOT match the same used in almost all modern PUPs & DOGs; namely no grub.cfg or its accompanying loopback.cfg which allow frugal boots directly from PUP's ISO file.

Is this 'new' use by you for booting signaling a WoofCE strategy change for all PUPs & DOGs in our future?

Or is this a need to not use the WoofCE strategy for just this PUP?

Curious, if something you have found to be wrong with current PUPs & DOGs boot setups in WoofCE builds which for the past several years have worked flawlessly.

[dimkr]

Or is this a need to not use the WoofCE strategy for just this PUP?

No, but it's my strategy to ignore repeated requests for one feature if I find them long and annoying, especially if they're coming from one user.

https://github.com/search?q=org%3Apuppy ... ype=issues
https://github.com/search?q=org%3Apuppy ... ype=issues

Please stop this, @Clarity.

[Clarity]

Ah, its viewed as personal. That was not my intent on asking these questions.

Sorry if its found as offensive. Not the reasons for asking.

[dimkr]

Ah, its viewed as personal. That was not my intent on asking these questions.

It's not personal, but professional. Asking for this feature once, in one place, is enough - everything else is a distraction or an annoyance.

[Clarity]

My request, on this thread, is NOT asking for a feature. It is asking if there is a change afoot...I think.

If there is a change coming, its nice to be able to plan ahead for things of this sort.

Is it asking something different?

Edit: In this response to another user asking about a directional change. Its merely to plan for our behavior objectives looking forward. Nothing personal, its professional, honest.

NO response to this post requested or expected. Let's let it drop.

[dimkr]

9.0.4 (due this Saturday) will feature:

ConnMan+connman-ui as a replacement for SNS, Frisbee, and friends (only on x86_64): https://github.com/puppylinux-woof-CE/woof-CE/pull/2514
Consistent right-click behavior in tray icons (an issue that affects only x86_64): https://github.com/puppylinux-woof-CE/woof-CE/pull/2516
The ability to switch from Xwayland to X.Org and vice versa (only on x86_64): https://github.com/puppylinux-woof-CE/woof-CE/pull/2512
A fix for D-Bus startup failure, which also prevents ConnMan and Blueman from starting: https://github.com/puppylinux-woof-CE/woof-CE/pull/2519

In addition, there are two GTK+ 3 theme fixes which make connman-ui more visually consistent, that will probably make it into 9.0.4 (depending on the GitHub Actions cache retention interval):

https://github.com/puppylinux-woof-CE/g ... 531fe209bb
https://github.com/puppylinux-woof-CE/g ... 4876bf62cb

Before:
After:

[Feek]

Hello,
after more than 1 hour in VanillaDpup9.0.3 I did not encounter a problem on my laptop.
I like this pup and I will continue to discover.

Right now I have 2 questions:

1. Is it recommended to update (overwrite) the puppy "install" files each time a new prebuilt .iso is released?

2. If the savefolder was created in an older version of Vanilla dpup, will it work with newer builds?

Thanks.

[dimkr]

1. Is it recommended to update (overwrite) the puppy "install" files each time a new prebuilt .iso is released?

That's up to you. I'll do my best to share a list of changes, so you can decide for yourself.

My current focus is bug fixes and polish (for example, fixes for theme inconsistency), but I guess not every issue is critical for all users, and some will choose to live with it.

2. If the savefolder was created in an older version of Vanilla dpup, will it work with newer builds?

Specifically in the case of 9.0.4 - compatibility with 9.0.3 will be broken because of the switch from SNS to ConnMan, and changes in xorgwizard.

[dimkr]

Extra changes that will make it into 9.0.4:

1. powerapplet_tray now runs as spot and doesn't pollute /tmp - https://github.com/puppylinux-woof-CE/woof-CE/pull/2531
2. Consistent toolbar style across GTK+ 2 and GTK+ 3 - https://github.com/puppylinux-woof-CE/woof-CE/pull/2533
3. External monitor placement is now consistent between X.Org and Xwayland - https://github.com/puppylinux-woof-CE/woof-CE/pull/2530
4. Xwayland now tries a lower resolution or refresh rate instead of disabling an external monitor that prefers a mode that won't work due to hardware limitations (like the maximum resolution the GPU can handle) - https://github.com/puppylinux-woof-CE/woof-CE/pull/2527
5. The issue that prevents D-Bus, Blueman and ConnMan from starting should be fixed now - https://github.com/puppylinux-woof-CE/woof-CE/pull/2519
6. Extra GTK+ 3 theme fixes, for menu items and the printing dialog -
https://github.com/puppylinux-woof-CE/g ... 389ac17e18
https://github.com/puppylinux-woof-CE/g ... 2edfc1d88e
https://github.com/puppylinux-woof-CE/g ... 5ff3cbab5e
https://github.com/puppylinux-woof-CE/g ... c2884202e4
https://github.com/puppylinux-woof-CE/g ... 74cacc4e04
https://github.com/puppylinux-woof-CE/g ... be7c89ac09

Before (left) and after (right):

These two screenshots come from 32-bit and 64-bit dpup (Geany is built against GTK+ 2 and GTK+ 3, respectively), after changes (2) and (6). Can you tell which is which?

[Clarity]

YOur request; "Which is which?"
Maybe the icons colors blue vs grey ...

[dimkr]

The good news: 9.0.4 is out!

The bad news: the build used cached tarballs of the GTK+ themes, so all GTK+ 3 theme bug fixes are left out. I made woof-CE ignore the cache and always download the latest theme tarballs (https://github.com/puppylinux-woof-CE/w ... 2545/files) and triggered another build, 9.0.5.

Another fix that made it into 9.0.4 is https://github.com/puppylinux-woof-CE/woof-CE/pull/2543: previously, .desktop entries with Terminal=true didn't work in Puppy. For example, if you install htop from PPM, the menu entry doesn't do anything, because it runs htop directly and not inside a terminal window. This PR makes the menu generator wrap the command-line of such .desktop entries with rxvt -e.

EDIT: 9.0.5 is out.

[dimkr]

9.0.6 will consist of fixes, too. See https://github.com/puppylinux-woof-CE/w ... 2?closed=1 for the list of changes.

The only change that is not a bug fix is https://github.com/puppylinux-woof-CE/woof-CE/pull/2557: the default font rendering settings are now similar to Xfce's default. On my ARM laptop, websites render faster after this change.

[Feek]

Since vanilladpup doesn't have a built-in spreadsheet, word processor and draw I decided to try Libreoffice appimage as a better solution instead of installing these apps one by one.
And it works for me after installation of "fuse_2.9.9-5" from the PPM.

I also succesfully tested the Firefox appimage from fredx181.

BTW nice loop of animations when screensaver is active.

[dimkr]

Since vanilladpup doesn't have a built-in spreadsheet, word processor and draw I decided to try Libreoffice appimage as a better solution instead of installing these apps one by one.

LibreOffice from PPM and https://www.libreoffice.org/download/download/ work, too

[Clarity]

@dimkr Does this mean that downloading the Libre RPM from the site and clicking it will install and resolve dependencies or will the ldd be required?

[dimkr]

@Clarity it should "just work".

[dimkr]

9.0.6 is out! https://github.com/vanilla-dpup/releases/releases

[Duprate]

Hi! Using Vanilla Dpup 9.0.6 now! I liked your dimkr work. I found it similar to slacko64-8.2.1. Initially I even used a slacko savefile, just to test it (it worked!)... I found it very interesting for those who want to use only browsers, or install only the programs they like. I even remembered the first Linux I used: Browserlinux501 (95Mb) by Puppy Martin. Yeah: The first puppy I used was "out of the box".
It worked well with Firefox, Google-Chrome and Vivaldi. Also testing with Overlayfs. The filesystem is small, just the way I've wanted it for a long time, but I don't know how to make it myself.
Good luck on your project!