Fatdog64-813 Final [07 Oct 2022]

[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-813 Final released on 7 October 2022.

The Fatdog team is pleased to release Fatdog 813 Final.

It is a special release driven by the need to update the Secure Boot shim. There are no new major features but the usual bug fixes and incremental improvements that we have collected since the 812 release.

Changes from 812: 812 announcement

Updates:

• Linux-5.19.14, low-latency, 1000Hz, dynamic preemption

• Microcode as of 2022.10.09

• openssl 1.1.1q

• curl 7.85.0

• Xdialog-gtk2 2.3.2

• gtkdialog-gtk2 0.8.5

• desktop-wallpaper 1.1.0

• Packit 1.23

• shim 1.38

• refind 0.13.3.1

• mesa: rebuild to support Intel Iris and Iris XE graphics

• multirename 1.12

• uextract 4.10

• rox-filer 2022-08-04

• feh 3.9

• dunst 1.9.0

• libwebp-pixbuf-loader 0.0.5

• squashfs-tools 4.5.1

• rxvt-unicode 9.30

• vlc 3.0.17.3

• picom 9.1

• libwacom 2.1.0

• xf64-input-wacom 1.0.0

• expat 2.4.6

• qemu-vm-manager 1.4

• civetwet 1.15

• hardinfo 2021.12.05

• avidemux 2.8.0

• magdock 1.3

• exfat-utils 1.3.0.2021.01

• xf86-video-intel fixes

• xorg-server to 1.20.14

• bluez 5.62

• libzstd 1.5.0

• sqlite 3.37

• bluez-alsa 3.1.0

• dds9 11

New Features:

• filemnt now supports mounting disk images containing partitions

• proper support for lxdm as an alternative to slim

• lxdm with virtual keyboard support (in repo)

• io-scheduler udev rule to restore harddisk performance

• this release uses an updated Fatdog cert, which will expire in 2041, to sign its kernels and bootloader tools (older Fatdog releases use a Fatdog cert that will expire in 2022)

• rox-filer now supports the "F2" key to rename

• clicking the bluetooth icon launches btmanager.sh

• btmanager.sh supports trust/untrust (needed for some bt mice)

• sandbox-lxc.sh now supports audio, and does not force desktop emulation anymore

• set-cpufreq-governor script to easily change cpu governor for multi-cpu systems

• new, more comprehensive MIME manager (fatdog-sync-mime)

• aloopd now supports remote audio (when combined with trx package from repo)

• aloopd now supports mixer re-direction

and numerous bug fixes and fine tunings.

Please do not post support questions in this thread. Instead create a separate thread for your support question. This thread is for comments, feedback, etc related to this specific release.

----------------

If you still run earlier Fatdog series (700 or 600), we also recommend upgrading to this version where possible. In this case, you may want to read the notes/warnings noted in Fatdog64 802/801/800 thread.

As usual Fatdog64 does not upgrade from any older version. Using a new savefile/savedir is recommended.

If you downloaded the Fatdog64-813 ISO before this announcement: please scratch your existing ISO, and download the 813 ISO again, and verify that the checksums match.

Downloads:

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

DEXV, NLS, 32-bit compatibility, and kernel source SFS files can be downloaded using the "SFS Manager" applet located in Fatdog64 Control Panel's "System" tab.

The ISO builder is dated 2022.10 and 813-pkglist.tar.xz.

The ISO builder is available on ibiblio.org or one of the mirrors above.

=====

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.

=====

[fatdog]

Known problems and their fixes

1. PROBLEM: Bluetooth does not seem to function.
CAUSE: Newer kernels (5.19) do not automatically power up bluetooth adapters at boot the way old kernel (5.4) did.
FIX: Open /etc/init.d/85-bluetooth with geany, and insert the following line: bluetoothctl power on __after__ hciconfig hci0 up

2. PROBLEM: Shift-left- and shift-right-arrow keys print 4 and 6 instead of moving the text cursor on some Macbook Pro models.
CAUSE: Conflicting key-maps in the system Xmodmap file; noticed on a Macbook Pro mid 2012 model.
FIX: Delete the two lines that remap keycodes 113 and 114 in /etc/X11/app-defaults/Xmodmap then save the file and restart X. Thanks to @je55eah for reporting this issue and how to fix it.

3. PROBLEM: Clicking a network share icon in /usr/share/Shares displays an error dialog suggesting bad credentials or invalid options or...
CAUSE: The new kernel 5.19 does not allow empty CIFS mount options the way the old kernel 5.4 did.
FIX: Unmount all network shares in /usr/share/Shares - right click each share and select "Unmount SHARENAME" from the menu. Click the icon named "Network" to rescan for network shares, and enter valid credentials for each rediscovered network share.

4. Kernel 5.19.xx has reached end of life. We have built the final version of 5.19.xx (version 5.19.17) and it's available in ibiblio or one of its mirrors. In ibiblio it's located here: http://distro.ibiblio.org/fatdog/kernels/800/
It has identical configuration as 5.19.14 with comes with 813 release.

5. PROBLEM: Fatdog Remaster doesn't seem to work if trying to remaster without UEFI support.
FIX: Download fatdog-remaster-fix-1.0-noarch-1.tar.xz attached here. Then rename it to fatdog-remaster-fix-1.0-noarch-1.txz. Then then open terminal, and inside terminal run "installpkg fatdog-remaster-fix-1.0-noarch-1.txz".

6. PROBLEM: "Get Google Chrome" creates corrupted packge of 536 bytes in size.
CAUSE: Busybox ar, used by undeb, used by get-google-chrome.sh doesn't recognize this specific Chrome DEB package.
WORKAROUND: If you have devx.sfs loaded, full version of ar is being used instead and it works fine.
FIX: Download undeb-fix-1.0-noarch-1.tar.xz package, rename the extension from .tar.xz to .txz and install it. It contains a fixed version of the /usr/bin/undeb script.

[fatdog]

reserved

[Clarity]

Please note the final comments also found on this 'closed' thread.

Questions for @fatdog

• FATDOG version numbering: Will there be a version 9xx?

• On Distrowatch, here, FATDOG's subsystems for v813 is not present: Is this intentional?

[Duprate]

Hi! Using the "Fatdog64-813 Final October 7, 2022" version. Working perfectly.....

[Keef]

I did use my existing save folder, but wasn't expecting any problems. Haven't had any either. All good so far.

[Clarity]

@m1k3's problem brings to mind a question that has probably been answered somewhere before:

Can a Save-file/save-folder be added/installed from desktop AFTER booting pristine?

hummm

[Null_ID]

Another fine release, thank you. No issues so far on a Thinkpad T510, 4 Gb RAM, Intel Core i5 M430.

[jamesbond]

Thank you everyone for your confirmation and feedback.

FATDOG version numbering: Will there be a version 9xx?

Yes, in time.

On Distrowatch, here, FATDOG's subsystems for v813 is not present: Is this intentional?

We haven't informed Distrowatch of the update yet. 813 is a relatively minor maintenance release.

Can a Save-file/save-folder be added/installed from desktop AFTER booting pristine?

You can but those save-file will not be treated as savefile. They will be treated as uncompressed "SFS" and is only available as a read-only layer.