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
These offer better default settings and compatibility for apps that want
to use ALSA or JACK directly, similar to how we already pre-install
pipewire-pulse for apps using PulseAudio directly.
And also add `unzip` to the list so it doesn't accidentally get
uninstalled in the future if we shift around our packages to remove the
thing that's incidentally pulling it in.
Resolves#314
GTK 3 apps are still around, and these packages improve support for them
by letting them put icons in the System Tray and export their menus over
D-Bus for the Global Menu widget.
Resolves#288
A surprising number of people use this to put together fairly
sophisticated local automation systems. It's also made by KDE, so it
helps to showcase how kool we are. Let's pre-install it.
Some of the profiles — most notably "throughput-performance" which gets
activated as the "Performance mode" exposed in Plasma — will mess with
the vm.swappiness value. But we already set it to a value of our
choosing, and that value should be fine for all modes given our zram
setup. So let's stop tuned from doing this.
There are some papercuts that makes the UX non-ideal for an initial
public release right now; revert until we can have those fixed.
Related to #275
Reverts dffa871ec7
Reverts 3ac85bc4e1
Right now it gets pulled in automatically as a dependency of something
we also pre-install, but we should mark it down here so it never goes
away by accident as a result of other package changes, because then
kde-builder would stop working.
it's unclear why we would need a full blown dns server and its
installation predates even the git repo so it's not documented why it
was added to begin with.
The internet is absolutely chock-full of complaints about this, all
being pointed to the same workaround: disable power management for the
snd_hda_intel module. It appears to be quite widespread over a long
period of time.
Let's do it automatically so users of affected hardware don't get driven
mad.
Related to #258
