Login

u/GuessWhat_InTheButt

▲ 2 r/kde

I want Discover to handle automatic updates of my system (apt & flatpak). How do I enable this via terminal?

My system is Debian based. Flatpak and the Flatpak Discover Backend are installed.

Question 1:
Is setting "System Settings -> Software Update -> Update software: Automatically" enough to keep the system updated even without installing cron-apt or unattended-upgrades or similar packages? (packagekit seems to be installed by default)

Question 2:
I'm aware $ systemsettings kcm_updates opens this exact screen. However, does systemsettings have a way to set certain settings via commandline? If not, how else to set this from the terminal?
$ kwriteconfig6 --file PlasmaDiscoverUpdates --group Global --key UseUnattendedUpdates true seems to work. Is that enough?

Question 3:
I've noticed setting the option above to "Automatically" adds the line "UseUnattendedUpdates=true" to ~/.config/PlasmaDiscoverUpdates. Is writing this line enough to enable automatic updates for that user or are other steps involved?

Question 4:
Are there better ways to enable full system updates (meaning apt, flatpack, fwupd and snapd updates if desired) than setting this setting in System Settings?

reddit.com
u/GuessWhat_InTheButt — 3 days ago
▲ 2 r/MXLinux

Issue with ZFS? "OpenZFS on RT kernels is currently experimental"

I've just tried to install ZFS on a fresh MX Linux KDE amd64 installation (Kernel 6.12.88+deb13-amd64).

# DEBIAN_FRONTEND=readline apt install -y zfs-dkms zfsutils-linux

[...]
OpenZFS on RT kernels is currently experimental

You are attempting to build OpenZFS against a real-time (PREEMPT_RT) kernel.

OpenZFS has not yet officially supported PREEMPT_RT kernels. Since Linux 6.12, PREEMPT_RT has been merged into the mainline kernel, making such configurations more accessible; however, this does not imply that OpenZFS has been validated against them. The build may fail, and even if it succeeds, compatibility issues
and instability, including possible data corruption, may occur.

Proceed with caution and ensure you have adequate backups before using OpenZFS on a real-time kernel in any environment where data integrity matters.

I don't think I've ever seen this message on any other machine I installed ZFS on. I also compared the boot config (grep -i preempt /boot/config-6.12.88+deb13-amd64) with an old Kubuntu installation I have it seems to be identical, despite me never getting this warning on that machine (as far as I remember).

CONFIG_PREEMPT_BUILD=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
# CONFIG_PREEMPT_RT is not set
CONFIG_PREEMPT_COUNT=y
CONFIG_PREEMPTION=y
CONFIG_PREEMPT_DYNAMIC=y
CONFIG_PREEMPT_RCU=y
CONFIG_HAVE_PREEMPT_DYNAMIC=y
CONFIG_HAVE_PREEMPT_DYNAMIC_CALL=y
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_DRM_I915_PREEMPT_TIMEOUT=640
CONFIG_DRM_I915_PREEMPT_TIMEOUT_COMPUTE=7500
CONFIG_DRM_XE_PREEMPT_TIMEOUT=640000
CONFIG_DRM_XE_PREEMPT_TIMEOUT_MAX=10000000
CONFIG_DRM_XE_PREEMPT_TIMEOUT_MIN=1
# CONFIG_DEBUG_PREEMPT is not set
# CONFIG_PREEMPT_TRACER is not set
# CONFIG_PREEMPTIRQ_DELAY_TEST is not set

What exactly is causing this warning on MX Linux? The only talk I was able to find about an incompatibility like that is this 15 year old issue on GitHub: https://github.com/openzfs/zfs/issues/83
Is this warning a bug on MX Linux or should I reconsider using ZFS on MX Linux?

Edit: Just checked, on a fresh Debian installation with the same kernel (6.12.88+deb13-amd64) and the same kernel config I don't get this warning. So this issue seems isolated to MX Linux. Any ideas?

Edit2: Okay, I found an important differntiator:
On Debian the ZFS version is: zfs-2.3.2-2
On MX Linux the ZFS version is: zfs-2.4.2-1~mx25+1

So this is either -mx25 fork related or an ZFS 2.4.x issue.

u/GuessWhat_InTheButt — 4 days ago