Fatdog64-900 Beta [04 Aug 2023]

[fatdog]

Since we now have a dedicated subforum at our disposal, please do not post support questions in this thread, create a separate one instead. Comments, feedback, etc related to this specific release are still okay. Thank you.

___________

Fatdog64-900 Beta released on 4 Aug 2023.

The Fatdog team is pleased to announce the release of Fatdog 900 Beta.

Fatdog64-900 Beta is the next pre-release of the newly launched 900 series. The focus of this beta release is stability and bug fixes. Bugs and regressions found during the alpha releases have been fixed to provide smoother experience and more reliable operations. The kernel has now been updated to the 6.1.39, and we plan to stick to the 6.1 LTS kernel for the near future.

The team feels quite comfortable with this release, and we are planning to run the Beta stage for a much shorter time than alpha. If there are no major bugs found during the beta stage, we will go to final in one to two weeks time.

Fatdog64-900 Beta changelist from 900 Alpha: 900 Alpha announcement

Updates:

• Linux 6.1.39 (with xattr support on /tmp)

• Microcode updates (pulled on 2023-07-21)

• libcap 2.69

• openssl 3.1.1

• CUPS 2.4.6

• cups-filters: patch applied to mitigate nasty bug

• cURL 8.1.2

• dbus 1.14.8

• Exiv2 0.27.7

• gstreamer 1.22.4

• libjpeg-turbo 3.0.0

• libwebp 1.3.1

• libX11 1.8.6

• libxml2 2.10.4

• Python 3.11.4

New Features:

• Basesfs/savefile on 9p filesystem (mainly on qemu).

Known Issues:

• Certain Radeon-based machines require "radeon" module to be preloaded using "loadmodules" boot parameter, otherwise there could be a delay in the booting process.

As usual Fatdog64 does not upgrade from any older version. Using a new savefile/savedir is recommended. But for a change, you might be able to carry on your savefile from 900 Alpha.

Downloads:

Get the Fatdog64-900 Beta ISO from here: ibiblio.org, or from uoc.gr, or nluug.nl.

The ISO and corresponding devx, nls and 32-bit compatibility library are located in the same location above. Kernel sources can be downloaded using the "SFS Manager" applet located in Fatdog64 Control Panel's "System" tab.

The ISO builder has not been made available as yet. It will be released along with Fatdog64-900 Final.

=====

If you need to boot on a machine with Secure Boot enabled, please make sure you read this first this: http://distro.ibiblio.org/fatdog/web/fa ... -boot.html.

If you have any questions please check this pages first: http://distro.ibiblio.org/fatdog/web/faqs/faq.html. This page is also available offline, and you can view it on Fatdog64 by visiting file:///usr/share/doc/faqs/faq.html or clicking the "question mark" icon on the desktop.

=====

If you still run earlier Fatdog series (700 or 600) and want to upgrade to 900, please read the notes/warnings noted in Fatdog64 802/801/800 thread. Note that "make-spot-more-secure" script has been removed (it has been six years and ten releases since the change was made; if you think you still need this script. you probably need to start a new savefile/savedir instead).

[fatdog]

Reserved.

[fatdog]

The Fatdog64 900 package repo is now on par with 814 repo (not including obsolete packages or large packages that cannot be (easily) built). Things have changed since 800 was released; these days third-party AppImages or self-contained binary tarballs are more prevalent than before. Use them if you cannot find the packages 900 repo (both txz and SFS packages). In fact, one of the motivations for the 900 series is to provide a stable up-to-date platform where you can run these large packages.

Note:
1. AppImages or binary tarballs are the recommended way to install these third party packages.
2. We do not support Flatpak and Snap. At least, not officially. There are ways to use them, by converting them to SFS, as documented elsewhere in this forum - but they have lesser chances to work than AppImages.

In addition, checkout sbopkg: Slackware.org Package browser for access to more packages.

[fatdog]

Reserved.

[don570]

I tested the Beta version of Fatdog64-900
Frugal install with a Save folder

I noticed following...

1) The SFS package format created by BarryK for Easy containers isn't compatible with Fatdog64
or probably other Puppies

2) When shutting down for the first time-
Instead of creating a brand new Save folder I used an existing empty folder.
I filled in the name in the field. Fatdog correctly used this folder to store and save documents.
However there was a confusing message that a folder was created by Fatdog.

[Jinx]

I did copy the save folder from FatDog64 900-alpha to 900-beta and it worked fine. The main change to 900-alpha was a firefox installation with extensions and my settings. Also, you can drop the gtk3 installation (and pulse audio?) from the get firefox script.

[proebler]

Updated without issue from 900-Alpha to 900-Beta using the existing savefolder.

I have installed fotoxx-23.50 from the repo and get the following error when trying to run it:

command: fotoxx
fotoxx-23.50
program exe: /usr/bin/fotoxx
build date/time: Jun 24 2023 13:48:32
fotoxx home: /root/.fotoxx
-------------------------------------------
start fotoxx Tue Aug 08 20:26:59

(fotoxx:5678): Clutter-Gtk-ERROR **: 20:26:59.483: *** Unsupported backend.
Trace/breakpoint trap

Any idea on how to fix it?
Thank you
proebler

[step]

(fotoxx:5678): Clutter-Gtk-ERROR **: 20:26:59.483: *** Unsupported backend.
Trace/breakpoint trap

Any idea on how to fix it?

Try running env CLUTTER_BACKEND=x11 fotoxx. If that works you can make this change permanent for subsequent logins by creating file /etc/profile.d/clutter-backend.sh with the following contents:

Code: Select all

# specify the backend for clutter: x11, egl, or wayland
export CLUTTER_BACKEND=x11

[proebler]

(fotoxx:5678): Clutter-Gtk-ERROR **: 20:26:59.483: *** Unsupported backend.
Trace/breakpoint trap

Any idea on how to fix it?

Try running env CLUTTER_BACKEND=x11 fotoxx. If that works you can make this change permanent for subsequent logins by creating file /etc/profile.d/clutter-backend.sh with the following contents:

Code: Select all

# specify the backend for clutter: x11, egl, or wayland
export CLUTTER_BACKEND=x11

That worked, thank you.
I also had to install additional packages: exiftool, perl-5, dcraw, binutils
I will try to make it permanent. So far I have only run it from terminal.

[Duprate]

Hello! Testing FatDog64-900 Beta, in standard mode (AUFS), with the supplied kernel (6.1.39), and with a new savefile, after starting and the desktop screen appears, a completely white screen appears, with no access to anything. By clicking on the lower left corner of the screen, it is possible to open the programs menu and click "Restart X", on the keyboard I click "Enter", and I have a few seconds to click on "Wallpapers" and "Apply", to close the white screen .
After several attempts, I see that underneath the white screen is the message:
"Failed to execute child process "/usr/share/backgrounds/default.jpg/AppRun" (Not a directory).
I suspect it is related to the Desktop-Wallpaper program.
I spent the day trying to solve the problem but, I couldn't.........

FatDog64-900 Alpha version works perfectly, no bugs.

[step]

@proebler,

That worked, thank you.

I'm glad it did!

I also had to install additional packages: exiftool, perl-5, dcraw, binutils

perl is for exiftool. Exiftool is a good program to keep around anyway. It's a supercharged tag editor for all kinds of media files.

I will try to make it permanent. So far I have only run it from terminal.

I don't know if this is what you had in mind, but I posted here about how to create a rox right-click menu entry for fotoxx (GTK3).

[step]

@Duprate, please try again booting without a safefile. Also before rebooting please rename all the savefiles and savefolders, if any, that exist in all your partitions to a temporary name that starts with "NOT-".

[proebler]

all good now with fotoxx (GTK3)
see post
thank you

[don570]

I couldn't get an older appimage package of shotcut video editor to run in Fatdog64 900 Beta
shotcut-linux-x86_64-221221.AppImage
It could run in FD64 812
I'll try a more recent package and report back.
______________________________________

fSpy AppImage will run if option

Code: Select all

--no-sandbox

is added
https://github.com/stuffmatic/fSpy/releases/tag/v1.0.3
________________________________

[don570]

shotcut video editor

The latest shotcut appimage will work with fatdog64-900 beta
Older versions won't.
https://shotcut.org/download/

https://www.fosshub.com/Shotcut.html?dw ... 9.AppImage
_______________________________________________-

The stable version of fSpy app doesn't require the

Code: Select all

--no-sandbox 

option

Download:
https://github.com/stuffmatic/fSpy/rele ... 4.AppImage
_______________________________________________________________

[Duprate]

@Duprate, please try again booting without a safefile. Also before rebooting please rename all the savefiles and savefolders, if any, that exist in all your partitions to a temporary name that starts with "NOT-".

Thanks Step! I made the savefolder again. In the previous one, I had placed an old file in /root/Startup to run compton. This is what caused the white screen. After completing the savefolder, I converted it to save.sfs and added "savefile=none" to grub.cfg. Now it's working perfectly!

[jamesbond]

I had placed an old file in /root/Startup to run compton.

Compton seems to have problem with newer kernel and OpenGL, but it's not a surprise since it has not been updated for a very long time. You can run it but you need to use the unaccelerated xrender back-end and not the accelerated opengl one.

As an alternative, we put two composite managers: xcompmgr (=compton's grandparent), and picom (=compton's descendants). xcompmgr always works since it is very simple, picom has a lot more options, but only certain combination works.

@don570, thanks for the info.

[Grey]

Beta.jpg

Interesting screenshot. HardInfo shows the G3260 processor, but at the same time Xeon in the section about the video card.

Asus H81M-C/BR
Perhaps a Brazilian homemade modification for two processors

[Duprate]

Beta.jpg

Interesting screenshot. HardInfo shows the G3260 processor, but at the same time Xeon in the section about the video card.

Asus H81M-C/BR
Perhaps a Brazilian homemade modification for two processors

True! It turned out to be a very good machine, at a low cost! In my opinion, I think that to run linux the integrated video is the best option.