Currently the script sets the release file to be owned by root so it
can't be accidentally removed, but even though it is owned by root it
can still be deleted by a user because the permissions on the parent
directory are what allow the file to be deleted.
This change instead marks the file as immutable, so that it truly can't
be removed accidentally (one would have to first explicitly remove the
immutable flag).
It's not in the base image and not in an enabled Arch repo. Have it
nowhere temporarily so that we can release an image, then later fix
this mess properly.
Homebrew by default will add itself to the system $PATH if you follow
the official installation instructions from their website and will
override important system binaries which can lead to failures like
experienced in https://invent.kde.org/kde-linux/kde-linux/-/issues/427.
This will make it safe to extend KDE Linux with homebrew again as this
will only add homebrew to the $PATH in interactive shells i.e. when a
user launched a graphical terminal.
Related to: https://invent.kde.org/kde-linux/kde-linux/-/issues/442
Additionally system binaries will be preferred over homebrew
provided ones if they are installed. This avoids a cat & mouse game
where homebrew will override things like systemctl, dbus and bash.
This was further discussed in https://github.com/ublue-os/brew/pull/1.
This has been used in every Universal Blue Bootc Image like Bazzite
for quite some time already.
this is now in the main repos, so we don't need to get them from AUR
anymore. Explicitly ask for the non-AUR Package here, in preparation for
removing it from our AUR package list.
A number of installed applications like visudo, vipw and vigr need vi to work as expected.
This commit installs the Arch's vi to vim compatibility package so that everything will work as expected after a fresh installation.
Fixes#497
Allows a developer to build an image with their local changes, then test it on their own system by soft rebooting into the generated *-root.erofs. This is ephemeral, and doesn't last a reboot.
plasmalogin doesn't do this anymore, as of fa3916a4aa, and it's noted that it should be done in environment.d instead. This fixes expected behaviour where binaries in /usr/local/bin should take precedence over /usr/bin.
These two need to be enabled by default because they don't get
auto-started. Instead, they have run conditions that cause them to only
do something if they detect they're a guest OS.
Enable them by default to make that work.
Fixes#426
libratbag is dependency for Piper UI application that can be used
for modifying configurable mice. It also comes with ratbagctl that
allows doing this from terminal.
Considering we sometimes encounter bugs with mice that have
different polling rates, we should have a tool to allow
us discover those bugs easier with such mice.
Sorts with ls -v to ensure correct version ordering, and prevents bootstrap.sh from failing when ls (previously find) outputs multiple archive paths into tar that are separated by \n.
Closes invent.kde.org/kde-linux/kde-linux/-/issues/299
When using a full disk, calamares is using partition layout within partition.conf and sets GPT type for root partition
When using manual partitioning tool, calamares is creating root partition with GPT type "Linux filesystem", then at reboot, the root partition is not found by systemd.
I added a patch in calamares@subvol to force gpt type on root partition.
I hope it can be usefull
Some WiFi dongles have included flash storage which includes driver installers for Windows. This isn't relevant to us, and prevents use of the dongles when they're in flash storage mode. Pre-install usb_modeswitch to automatically switch them into WLAN mode so they can be used.
Installed size is 252.9 KB.
With the 25.08 Flatpak runtime, this will always automatically install itself in an appropriate way. There's no need to do it here. Once Firefox switches over to the 25.08 runtime, which is tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=2010742, then it will already have codecs-extra automatically installed and available to it.
at some point in the past apparently we had a bogus sysusers file that
pointed the home to /usr/var/... which of course makes no sense and
breaks things.
the only way to rectify this is to throw away the user and start over.
to achieve that we have a new fix service that runs unless a marker file
is present and possibly deletes the broken user. recreation is delegated
to sysusers as per usual
Fixes#476
Otherwise, upgrade-installs will still try to use SDDM, which only
remained in the image by accident, and will be removed with
f20d66e1b26a4d5d9cdc9efd0aedaab725003a49 in the packages pipeline.
Resolves#475
Makes plasma-login automatically re-log the live user back in when logged out. This doesn't lead to login "death loops" anymore - which was the case on SDDM - and is the expected behaviour for a live environment.
