Here’s an infamous one:

https://hackaday.com/2024/01/20/how-a-steam-bug-once-deleted-all-of-someones-user-data/

Did you know that you can list every process running on your system along with their various categories of memory usage?

man ps

Or for a rough idea, just browse them wtih KDE System Monitor.

This is someone’s personal fork of Cantata. (The original is no longer receiving updates.)

What makes this one more useful or trustworthy than the 183 other forks? Why did the person behind this one strip/avoid the upstream reference, which GitHub normally applies to forks?

If I understand correctly, this could be exploited to escape linux namespaces, which which are the foundation of containers like Flatpak and Docker. Those were never very good security boundaries, but running untrusted code in them is now especially dangerous, until your kernel is patched.

Maybe Lubuntu or some other distro using the LXQt desktop environment?

https://lxqt-project.org/

https://lubuntu.me/

Edit: Debian offers an LXQt live image here:

https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/

Highlights

• Low neighborhood opportunity was associated with higher CDKN2A expression.
• CDKN2A is a key marker of cellular senescence and biological aging.
• Associations were strongest for social and economic opportunity.
• Results are consistent with models of socially patterned aging.

I think mpd is better suited to your purpose than any GUI media player.

Note that despite its network support, it can run and be controlled locally. Cantata uses it, for example.

The kernel log you posted appears to be from an X11 session. (Note the many instances of AppArmor allowing Xorg to do things.) You’ll probably need the Wayland logs if you want to troubleshoot Wayland.

Unfortunately, I can’t guide you, since I’m not using Nvidia or Wayland.

Slow to change sucks on the desktop pretty often.

Subjective opinion there.

I like Debian on the desktop. It does what I need, gets out of my way, and minimises surprise changes in the software I use. In other words, it respects my time.

If I were new to unix admin (as OP appears to be) I might try something like openmediavault for a home server.

I don’t run the same distro on everything, but I find Debian works well for PC, laptop, and server. Updates become available at about the same time, and I can apply them in whichever order I like. My scripts, tweaks, and personal backports are portable between devices. Anything I learn on one can be applied to the others. This arrangement keeps things simple, and Debian respects my time, both of which are important to me.

I use different distros for special-purpose devices like phones and media players.

I could see this being used as an excuse for governments to keep spending taxpayer money on Microsoft licenses, and for software/hardware companies not to support open operating systems like Linux.

California is the fourth-largest economy in the world.

I kind of wish those games didn’t confuse evolution with metamorphosis.

Ah, yes… the old “acting responsibly here won’t completely solve the problem, so we might as well act irresponsibly” argument.

Looks like that package was removed from Debian. I wouldn’t be surprised if it was due to not following Debian policy.

Here are the first 100 entries:

$ apt-cache show librust-winapi-dev |grep ^Provides: |sed "s/Provides: "// |sed "s/, /\\n/g" |sed "s/ .*//g" |sort -V  |head -100
librust-winapi+accctrl-dev
librust-winapi+aclapi-dev
librust-winapi+activation-dev
librust-winapi+adhoc-dev
librust-winapi+appmgmt-dev
librust-winapi+audioclient-dev
librust-winapi+audiosessiontypes-dev
librust-winapi+avrt-dev
librust-winapi+basetsd-dev
librust-winapi+bcrypt-dev
librust-winapi+bits1-5-dev
librust-winapi+bits2-0-dev
librust-winapi+bits2-5-dev
librust-winapi+bits3-0-dev
librust-winapi+bits4-0-dev
librust-winapi+bits5-0-dev
librust-winapi+bits10-1-dev
librust-winapi+bitscfg-dev
librust-winapi+bitsmsg-dev
librust-winapi+bits-dev
librust-winapi+bluetoothapis-dev
librust-winapi+bluetoothleapis-dev
librust-winapi+bthdef-dev
librust-winapi+bthioctl-dev
librust-winapi+bthledef-dev
librust-winapi+bthsdpdef-dev
librust-winapi+bugcodes-dev
librust-winapi+cderr-dev
librust-winapi+cfgmgr32-dev
librust-winapi+cfg-dev
librust-winapi+cguid-dev
librust-winapi+combaseapi-dev
librust-winapi+coml2api-dev
librust-winapi+commapi-dev
librust-winapi+commctrl-dev
librust-winapi+commdlg-dev
librust-winapi+commoncontrols-dev
librust-winapi+consoleapi-dev
librust-winapi+corecrt-dev
librust-winapi+corsym-dev
librust-winapi+d2d1effectauthor-dev
librust-winapi+d2d1effects-1-dev
librust-winapi+d2d1effects-2-dev
librust-winapi+d2d1effects-dev
librust-winapi+d2d1svg-dev
librust-winapi+d2d1-1-dev
librust-winapi+d2d1-2-dev
librust-winapi+d2d1-3-dev
librust-winapi+d2d1-dev
librust-winapi+d2dbasetypes-dev
librust-winapi+d3d9caps-dev
librust-winapi+d3d9types-dev
librust-winapi+d3d9-dev
librust-winapi+d3d10effect-dev
librust-winapi+d3d10misc-dev
librust-winapi+d3d10sdklayers-dev
librust-winapi+d3d10shader-dev
librust-winapi+d3d10-1shader-dev
librust-winapi+d3d10-1-dev
librust-winapi+d3d10-dev
librust-winapi+d3d11on12-dev
librust-winapi+d3d11sdklayers-dev
librust-winapi+d3d11shader-dev
librust-winapi+d3d11tokenizedprogramformat-dev
librust-winapi+d3d11-1-dev
librust-winapi+d3d11-2-dev
librust-winapi+d3d11-3-dev
librust-winapi+d3d11-4-dev
librust-winapi+d3d11-dev
librust-winapi+d3d12sdklayers-dev
librust-winapi+d3d12shader-dev
librust-winapi+d3d12-dev
librust-winapi+d3dcommon-dev
librust-winapi+d3dcompiler-dev
librust-winapi+d3dcsx-dev
librust-winapi+d3dkmdt-dev
librust-winapi+d3dkmthk-dev
librust-winapi+d3dukmdt-dev
librust-winapi+d3dx10core-dev
librust-winapi+d3dx10math-dev
librust-winapi+d3dx10mesh-dev
librust-winapi+d3d-dev
librust-winapi+datetimeapi-dev
librust-winapi+davclnt-dev
librust-winapi+dbghelp-dev
librust-winapi+dbt-dev
librust-winapi+dcommon-dev
librust-winapi+dcompanimation-dev
librust-winapi+dcomptypes-dev
librust-winapi+dcomp-dev
librust-winapi+dde-dev
librust-winapi+ddrawint-dev
librust-winapi+ddrawi-dev
librust-winapi+ddraw-dev
librust-winapi+debugapi-dev
librust-winapi+debug-dev
librust-winapi+default-dev
librust-winapi+devguid-dev
librust-winapi+devicetopology-dev
librust-winapi+devpkey-dev

I haven’t reviewed the relevant policies lately, but I suspect those should have been separate packages, not thousands of entries in a single package’s Provides: field.

“glass houses”

Do we really want clickbait headlines in the science community?

I see it at feddit.org.

In case you’re not aware, libvirt/qemu/kvm exists, as does VirtualBox. I can’t remember the last time I used VMWare.

What’s GTT?

Debian in its GUI (at least KDE, which I’m using at the moment) demanding the root password

I run KDE Plasma on Debian. Discover (KDE’s GUI for package updates) has never demanded the root password.

I wonder why yours would do that. Maybe the difference is because my root account has password access disabled? If you’re already a sudoer, you might try that.