Jelle van der Waa

It's explained in `systemd.timer` https://man.archlinux.org/man/systemd.timer.5#OPTIONS

I've also managed to get in another confusing state by first configuring kdump with nfs and then enabling the `crashernel` command line option. Then rebooting and trying to enabling the...

After discussing with @martinpitt * [ ] Cut down the shown lines in the error message * [ ] Change the error message to not say "unable to save settings"...

That's good idea, I'll have to check how easy it is to change the current code to use the PF's validation but it's certainly something we want to improve.

We also should land this to `starterkit` too after it worked out and then land it in `machines` and `podman`.

Auto fixing rules to appy in future pull requests: - [ ] alpha-value-notation - [ ] at-rule-empty-line-before - [ ] at-rule-name-case - [ ] at-rule-name-space-after - [ ] at-rule-no-vendor-prefix -...

Reported upstream https://bugs.archlinux.org/task/75495

Python issue fixed on Arch, but now the packages are split too. So I wonder if this breaks one of our tests.

We can't import `scss-variables.scss` as it depends on `$pf-color-white` ``` Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js): ModuleBuildError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js): SassError: Undefined variable. ╷ 26 │ $pf-global--BackgroundColor--100: $pf-color-white !default;...

`pkg/users/authorized-keys-panel.jsx` should be ported to PF4 JSX components instead of using PF html, that would also help out a bit.