This will ensure that the journal retains its state even after a system
reboot or service restart, improving the ability to troubleshoot and
maintain system integrity.
Resolves#331
This provides a fancy readout of your hardware that's useful for
debugging, and also allows the DaVinci Resolve distrobox container to
work.
This will add 8.1 MB to the base image size.
We can simplify this a lot for KDE developers setting up a new
development environment.
If this is merged, we can replace all of the documentation at https://community.kde.org/KDE_Linux#Setup with a single script invocation.
Resolves#213
since user services aren't default-off on arch this service is auto
started when installed, which leads to orca reading the screen by
default.
disable this so it becomes opt-in
we don't need git builds and they are troublesome. so instead we use the
main arch packages, with a slight twist: the packages pipeline rebuilds
systemd with sysupdated enabled.
It was just removed recently, and was not needed anyway because KDE's
nightly apps use the released runtime, not the nightly runtime.
Ideally that would be changed, but until it is, we don't need it.
Resolves#374
Related to #217
Part of https://invent.kde.org/kde-linux/kde-linux/-/issues/282
Increasing nofile limits is required for certain games to work, e.g.
Stronghold 2, and increasing memlock limits is required for certain
real-time workloads, e.g. the use of DAWs.
excitingly systemd will just not look at .conf files anymore when there
is a single .transfer file. so a couple days ago I actually broke the
update system by introducing a caibx transfer file. yay.
rename everything to .transfer so updates start working again
they are needed so sub ids actually get created
from the manpage:
> Note, that newusers, useradd, and usermod will only create entries
> in /etc/subuid if subid delegation is managed via subid files.
It's on Flathub now! So developers and designers who need it can grab it
from there.
We have to delete its files rather than stopping installing it, since
it's in the conjoined plasma-sdk package, and other apps in there aren't
on Flathub yet.
this is a bit dangerous but necessary for more efficient delta updates.
we must be very careful to avoid a bug in systemd caused by putting
foo.erofs.caibx into the sha256sums. so instead we have foo.caibx that
gets installed with the correct name by sysupdate
we still have the foo.erofs.caibx on the server for backwards compat,
but continue to not put it into the sha256sums
These days local music library managers are niche apps; most people
seem to listen to music using Spotify, YouTube, etc.
We already don't pre-install an email client on the basis that it's a
fairly niche app, so my sense is that we should consider a local music
library manager to be in the same boat.
Haruna is pre-installed and can handle audio files, so users won't
be left without a way to play any local audio files they do have.
Users who do still maintain local music collections can manually
download Elisa or any similar app of their choice. Elisa is even
featured on Discover's home page, so getting it if desired shouldn't
be a grueling task.
This is the data source for foomatic-db-engine, which is already
pre-installed. Adding it allows the Foomatic engine to generate PPD
files for a bunch more printers.
Resolves#328
This patch makes improvements to latency for pro audio use cases:
- Reduce the default and maximum audio latency for apps using PipeWire
or else ALSA, JACK, or PulseAudio directly. Cost: some CPU time when
performing heavy audio loads.
- Give users in the `audio` group the ability to make the CPU work
harder and access the real-time clock. Cost: easier for misinformed
users to allow misbehaving programs to waste energy.
Overall I think these costs are worth the benefits of better suitability
for real-time audio workloads.
My research sources included:
- https://blog.rtrace.io/posts/the-linux-audio-stack-demystified/
- https://forum.endeavouros.com/t/pipewire-guide-audio-crackling-popping-and-latency/69602
otherwise we are not cleaning up raw images
unfortunately this also means we'll screw over the sha256sums in the
root a bit. not easily dealt with. needs some refactoring of how the v2
stuff works
