QuickPup64 25.01 RC1

[mistfire]

This is the all 64-bit version of QuickPup built from ScPup64, Slackware Current packages, Debian Sid packages, Opensuse Tumbleweed, and Fedora Rawhide packages.

Features:

• XFCE Desktop Environment
• Wayland session option (experimental)
• Modular design
• Basilisk web browser (in sfs module)
• PipeWire for soundcard management
• Bluetooth connectivity
• Better support on electron apps and third-party commercial linux apps.
• Improved puppy under the hood
• NetworkManager as default network management for ease of use
  -- With VPN support (PPTP, L2TP, IPSEC, OpenVPN, SSTP, SSH)
• Fax support
• With GTK+3, GTK+4, and libadwaita library to support newer apps
• Improved Puppy Remastered Setup
• Builtin flatpak support (with flatpak-installer helper for easier setup)
• Sandboxed underdog linux capable
• AppImage support (Just double click the AppImage file to run)
• Vulkan included
• Improved package management.
  -- With package updater (experimental)
  -- Wider package support. Aside from PET, Debian (DEB), Red Hat (RPM), Slackware (TXZ, TGZ), and Arch Linux packages (PKG.TXZ).
  It also accepts the following packages (natively installed, no more package conversion needed. This allows to utilize almost all available linux packages):
  ->Slitaz (.tazpkg)
  ->Tiny Core (.tcz,.tce,.tcel,.tcem)
  ->Pardus (.pisi)
  ->Alpine Linux (.apk)
  ->Slax (.sb)
  ->OpenWRT (.ipk)
  ->0linux (.spack)
  ->Void linux (.xbps)
  ->Damn Small Linux (.dsl)
  ->Puppyrus (.pfs)
  ->Nutyx (.cards.tar.xz)
  ->Solus (.eopkg)
  ->Stampede (.slp)
  ->Porteus (.xzm,.lzm)
  ->Gentoo precompiled package (.xpak)
  ->Paldo Linux
  ->Venom Linux (.spkg.txz)

Download: https://1drv.ms/u/c/349c4d7a5f9d78cd/EV ... w?e=sFgjQi
MD5 Checksum: 688b84727d51cffae61984bf77c1e12e

32-bit library module (for running wine): https://drive.google.com/file/d/1PK6ZPu ... EB0p17LjB9

Language Pack: https://drive.google.com/file/d/1O6nsZF ... sp=sharing

BOOTING FROM ISO FILE (via Grub or Ventoy)?
enter find_iso=<path of iso file from a partition> boot parameter first before booting when QuickPup64 boot menu was shown

DISCLAIMER: The developer has no any responsibility for data loss from using this derivative distro. USE IT UNDER YOUR OWN RISK

[ronriel]

@mistfire ,
I gave this a try and it worked and is usable. I installed it frugally on an SSD. However, i noticed the ff unusual behavior.

1. Shutting down takes too long. Takes a minute maybe. Savefile used is a 2GB 4fs. I restarted it, then shutdown immediately, same issue encountered.
2. Changing window style is not as smooth as expected. Dialog Window doesn't change. I'll try other styles, maybe this is just a theme issue.
3. Tray icons overlaps with each other.

That was just a quick ride. I'll report other issues I will encounter. Overall, hes a good puppy.

[mistfire]

@mistfire ,
I gave this a try and it worked and is usable. I installed it frugally on an SSD. However, i noticed the ff unusual behavior.

1. Shutting down takes too long. Takes a minute maybe. Savefile used is a 2GB 4fs. I restarted it, then shutdown immediately, same issue encountered.
2. Changing window style is not as smooth as expected. Dialog Window doesn't change. I'll try other styles, maybe this is just a theme issue.
3. Tray icons overlaps with each other.

That was just a quick ride. I'll report other issues I will encounter. Overall, hes a good puppy.

Creating a savefile in first shutdown really tooks a long time for big filesize unless you use savefolder.

Regarding dialog theming, gtkdialog, yad, Xdialog, and gxmessage uses GTK2 while XFCE uses GTK3. So you need to use GTK2 theme switcher included on QuickPup64.

Thanks for compliment

[Clarity]

Hello @mistfire

The boot stanza of this beta matches the WoofCE PUPs.

But, there are issues where it will not boot directly from the ISO file via other boot-helpers like SG2D. SG2D finds the ISO file and present its for selection, but the boot fails no matter if I boot via PC's UEFI or BIOS approach. (screenshots follow)

QuickPUP64-booterr.gif (445.33 KiB) Viewed 81803 times

Failing, above, ...
I created a CDRW from the ISO and attempting to boot to RAM with the CD, it fails with

Code: Select all

Error 15:(http://grub4dos.chenall.net)
File not found

Press any key to ...

Thus will not boot.

[mistfire]

Hello @mistfire

The boot stanza of this beta matches the WoofCE PUPs.

But, there are issues where it will not boot directly from the ISO file via other boot-helpers like SG2D. SG2D finds the ISO file and present its for selection, but the boot fails no matter if I boot via PC's UEFI or BIOS approach. (screenshots follow)

QuickPUP64-booterr.gif

Failing, above, ...
I created a CDRW from the ISO and attempting to boot to RAM with the CD, it fails with

Code: Select all

Error 15:(http://grub4dos.chenall.net)
File not found

Press any key to ...

Thus will not boot.

Oh my! I forgot to replace initrd.gz with initrd.xz on boot configurations. To temporarily fix this issue edit the boot entry and replace initrd.gz with initrd.xz then boot the iso. I will reupload the iso file within few days

[Clarity]

A test:

1. Modified each line-entry in the loopback.cfg & grub.cfg to initrd.xz vs. initrd.gz.

2. ISOmaster used to update the ISO replacing the old files with the changes

3. Attempt at booting with new-changed files on an Intel BIOS

4. SG2D presents the ISOs

5. QuickPUP64 selected and at QuickPUP64 Menu, pfix=RAM entry attempted

6. QuickPUP64 starts its boot, then this

QuickPUP64 boot err.jpg (26.67 KiB) Viewed 81759 times

[mistfire]

A test:

1. Modified each line-entry in the loopback.cfg & grub.cfg to initrd.xz vs. initrd.gz.

2. ISOmaster used to update the ISO replacing the old files with the changes

3. Attempt at booting with new-changed files on an Intel BIOS

4. SG2D presents the ISOs

5. QuickPUP64 selected and at QuickPUP64 Menu, pfix=RAM entry attempted

6. QuickPUP64 starts its boot, then this

QuickPUP64 boot err.jpg

1. Select SAVE TEMP FILES
2. Choose partition where to save the files. A tarball will be created
3. Boot other puppy and upload the tarball here

[Clarity]

Attached

[TerryH]

Created a new manual frugal install on internal SSD with UEFI boot. Apart from issues you have identified in first post, all running well. I have installed libreoffice7.1.3.2.sfs and running portable vivaldi browser. Nice work mistfire. Thank you.

[mistfire]

(post moved)

[mistfire]

Attached

Upon reading the logs. That's weird that sr0 detected but returned 0? Where did you boot that?

Code: Select all

/dev/sda1|ntfs|59077632
/dev/sda2|ext4|20971520
/dev/sda3|ntfs|67848192
/dev/sda4|none|1
/dev/sda5|ext2|8389632
/dev/sdb1|exfat|7863279
/dev/sdb2|vfat|32768
/dev/sr0|none|0

[mistfire]

QuickPup 21.06 BETA 2 released

Changes:
* Added late-loading microcode on boot
* Some fixes

NOTE: To apply microcode, install amd/intel microcode package. To apply microcode immediately without reboot, type this command on terminal then press ENTER

Code: Select all

update-microcode

Download: https://drive.google.com/file/d/1t_KJpA ... sp=sharing
MD5 Checksum: 471c746905ce57b6752c7aab513f0b3a

[Clarity]

Code: Select all

/dev/sdb1|exfat|7863279
/dev/sdb2|vfat|32768

Boot-Manager on sdb2 while ISO file in /BOOTISOS on sdb1

This is a very unique problem not seen on any prior ISO file booting over past 2 years. The same problem occurs when attempting to boot via 2 different ISO file booters.

I am sure that there is an answer, but ???.

I can make an image file of the USB if that will help you replicate the problem on your end.

BTW: This ISO file boots and runs "fine" in a KVM (QEMU).

[TerryH]

Hi mistfire,

I know you had some issues with pupMTP, when using SCPup64. pupMTP (and also pupCamera) currently doesn't function correctly in Quickpup64. When my Samsung phone is connected it returns a message that no devices found.

I don't know which actual ScPup64 -21.04 you based Quichpup64 on, but I get the same results with ScPup64 21.04+2. On SPup64-21.04+3 pupMTP functions correctly, accessing my Samsung S10e phone.

The attached screenshot is using Quickpup64 beta2. It doesn't return an error code, just shows it can't access the phone.

[Clarity]

This does NOT address the MTP problem. Rather, this is a post of how I get around this problem.

There are several ways to transfer information between a PUP and a smart-phone; namely Bluetooth, wired, or Wifi. For Wifi, I have used the following for past 4-5 years: (if I leave out something below, please correct anything missing)

Requirement:

1. Wifi active on your home's LAN,

2. PC & Phone on the same IP LAN (subnet),

3. A filemanager on the phone which is LAN aware

PUPPY
Nothing need be installed on any modern PUP or FATDOG as they already have SAMBA.

1. On your PUP

   • Start SAMBA (Menu>network>Samba Simple Management)

   • Note the SAMBA PC's IP address

2. On the phone

   1. Open your file manager

   2. Navigate to the Network section

   3. Either browse (if available) or setup a SAMBA location via the "noted" IP address

Transfer information to/from your phone as you need.

P.S. I DO RECOGNIZE that not every household has Wifi ability via their router.

[mistfire]

Hi mistfire,

I know you had some issues with pupMTP, when using SCPup64. pupMTP (and also pupCamera) currently doesn't function correctly in Quickpup64. When my Samsung phone is connected it returns a message that no devices found.

I don't know which actual ScPup64 -21.04 you based Quichpup64 on, but I get the same results with ScPup64 21.04+2. On SPup64-21.04+3 pupMTP functions correctly, accessing my Samsung S10e phone.

The attached screenshot is using Quickpup64 beta2. It doesn't return an error code, just shows it can't access the phone.

Did you enable MTP on your phone settings?

[TerryH]

Yes, the comparisons with Scpup64 I mentioned were done yesterday while testing pupmtp in quickpup64.

Also, when I plug the phones USB cable to the PC the probing devices message is displayed, but pupmtp fails to find the phone.

[mistfire]

Yes, the comparisons with Scpup64 I mentioned were done yesterday while testing pupmtp in quickpup64.

Also, when I plug the phones USB cable to the PC the probing devices message is displayed, but pupmtp fails to find the phone.

Try to install libmtp and simple-mtpfs from other distro's especially from Arch, Fedora Rawhide, Slackware Current, and Mageia Cauldron

[TerryH]

Yes, the comparisons with Scpup64 I mentioned were done yesterday while testing pupmtp in quickpup64.

Also, when I plug the phones USB cable to the PC the probing devices message is displayed, but pupmtp fails to find the phone.

Try to install libmtp and simple-mtpfs from other distro's especially from Arch, Fedora Rawhide, Slackware Current, and Mageia Cauldron

Thanks for the update, I have several installations with functioning mtp applications, or I can use other means to access my phone, I don't need to install from other distros at this stage.

[esos]

have some errors:

Gparted is not useable

Gparted130error.png (19.75 KiB) Viewed 71779 times

Draw Drawing of libreoffice7.1.3.2 error

Draw Drawing error.png (21.12 KiB) Viewed 71779 times

Search error

search-error.png (53.6 KiB) Viewed 71779 times

[mistfire]

have some errors:

Gparted is not useable
Gparted130error.png
Draw Drawing of libreoffice7.1.3.2 error
Draw Drawing error.png
Search error
search-error.png

That all errors that you encountered was in Pristine state (without loading save file)?

Regarding searching /proc is a special mountpoint for kernel process. Always avoid including that path on searching

[esos]

I think Gparted v1.3 is not ready for release. The results of booting from iso or frugal (internal or external) with/without save file come out with the same error.

[mistfire]

QuickPup64 21.08 BETA 1 released

Changes:
* Microcode loading suppport (late loading)
* Improved package updater
* Improved package manager
* Bugfix on puppy remaster script
* Fixed builtin files list which causes system failure upon updating packages
* Updated builtin packages
* Uget was moved to BDRV due to gstreamer dependency

Download: https://drive.google.com/file/d/1jSTJlp ... sp=sharing
MD5 Checksum: 1d5a2af1a53827800cdb89a2201633de

[esos]

Just compared (frugal) quickpup64_21.08-beta-1 vs.
quickpup64_21.06-beta-2

Both still have problem:
Draw Drawing of libreoffice does not work.
Thunar keeps crashing (quit without error message)

Pulse Audio quickpup64_21.06 works fine on all browsers
Vivaldi 4.0.2312.27, Brave 1.28.70 and Firefox 91.0

Pulse Audio quickpup64_21.08 works fine only on Firefox.

[mistfire]

Just compared (frugal) quickpup64_21.08-beta-1 vs.
quickpup64_21.06-beta-2

Both still have problem:
Draw Drawing of libreoffice does not work.
Thunar keeps crashing (quit without error message)

Pulse Audio quickpup64_21.06 works fine on all browsers
Vivaldi 4.0.2312.27, Brave 1.28.70 and Firefox 91.0

Pulse Audio quickpup64_21.08 works fine only on Firefox.

Can I have the libreoffice apps that you used? (in package or sfs)
What did you do before the thunar crashed?

[peebee]

I have also seen and mentioned the 64bit Thunar crash problem when using my ydrv Xfce add on
It happens randomly when opening a folder
No error messages are produced to give any clues

[esos]

I tested some versions of LibreOffice64 (.pet & .sfs).
Download from:
viewtopic.php?f=96&t=404

About Thunar: peebee mentioned above.

Sofar ok replace with pcmanfm-1.3.1

[esos]

Not sure what kind of "Bugfix on puppy remaster script".
I tested to remaster ISO.
After remastered vivaldi and brave browsers are not working anymore.
Only firefox working but all my personal setting are gone.
Many custom settings go back to original default e.g Screen resolution, network connection, speaker volume etc.

[mistfire]

Draw Drawing of libreoffice does not work.

I finally found the solution. All you need was to install avahi runtime library
https://download-ib01.fedoraproject.org ... x86_64.rpm

[esos]

Thanks, finally draw & impress work