fix: use tmpfiles.d to set default config in home dirs#1926
Merged
HastD merged 2 commits intosecureblue:livefrom Feb 13, 2026
Merged
fix: use tmpfiles.d to set default config in home dirs#1926HastD merged 2 commits intosecureblue:livefrom
HastD merged 2 commits intosecureblue:livefrom
Conversation
Use user-tmpfiles.d instead of ad-hoc systemd services to disable user-session QEMU core dumps and the KDE Plasma splash screen. For qemu.conf, the default file contents are only written if the file `~/.config/libvirt/qemu.conf` doesn't already exist. Thanks to @nihil-admirari for the suggestion: secureblue#1054 (comment) For ksplashrc, the file is always overwritten and is set to read-only, because certain theme settings in KDE Plasma will automatically try to overwrite that file. This also fixes a bug where the splash screen would be reenabled until next boot if the user logs out and logs back in. Users wishing to enable the splash screen can symlink the file `~/.config/user-tmpfiles.d/ksplashrc.conf` to `/dev/null` to override this configuration.
HastD
added a commit
to HastD/secureblue.dev
that referenced
this pull request
Feb 10, 2026
Update commands to reflect changes made in secureblue/secureblue#1926.
RoyalOughtness
approved these changes
Feb 13, 2026
EsseLowNitro
approved these changes
Feb 13, 2026
RoyalOughtness
pushed a commit
to secureblue/secureblue.dev
that referenced
this pull request
Feb 13, 2026
Update commands to reflect changes made in secureblue/secureblue#1926.
PhysicsIsAwesome
pushed a commit
to PhysicsIsAwesome/secureblue
that referenced
this pull request
Mar 1, 2026
Use user-tmpfiles.d instead of ad-hoc systemd services to disable user-session QEMU core dumps and the KDE Plasma splash screen. For qemu.conf, the default file contents are only written if the file `~/.config/libvirt/qemu.conf` doesn't already exist. Thanks to @nihil-admirari for the suggestion: secureblue#1054 (comment) For ksplashrc, the file is always overwritten and is set to read-only, because certain theme settings in KDE Plasma will automatically try to overwrite that file. This also fixes a bug where the splash screen would be reenabled until next boot if the user logs out and logs back in. Users wishing to enable the splash screen can symlink the file `~/.config/user-tmpfiles.d/ksplashrc.conf` to `/dev/null` to override this configuration.
PhysicsIsAwesome
pushed a commit
to PhysicsIsAwesome/secureblue
that referenced
this pull request
Mar 1, 2026
Use user-tmpfiles.d instead of ad-hoc systemd services to disable user-session QEMU core dumps and the KDE Plasma splash screen. For qemu.conf, the default file contents are only written if the file `~/.config/libvirt/qemu.conf` doesn't already exist. Thanks to @nihil-admirari for the suggestion: secureblue#1054 (comment) For ksplashrc, the file is always overwritten and is set to read-only, because certain theme settings in KDE Plasma will automatically try to overwrite that file. This also fixes a bug where the splash screen would be reenabled until next boot if the user logs out and logs back in. Users wishing to enable the splash screen can symlink the file `~/.config/user-tmpfiles.d/ksplashrc.conf` to `/dev/null` to override this configuration.
RKNF404
pushed a commit
to RKNF404/secureblue
that referenced
this pull request
Mar 1, 2026
Use user-tmpfiles.d instead of ad-hoc systemd services to disable user-session QEMU core dumps and the KDE Plasma splash screen. For qemu.conf, the default file contents are only written if the file `~/.config/libvirt/qemu.conf` doesn't already exist. Thanks to @nihil-admirari for the suggestion: secureblue#1054 (comment) For ksplashrc, the file is always overwritten and is set to read-only, because certain theme settings in KDE Plasma will automatically try to overwrite that file. This also fixes a bug where the splash screen would be reenabled until next boot if the user logs out and logs back in. Users wishing to enable the splash screen can symlink the file `~/.config/user-tmpfiles.d/ksplashrc.conf` to `/dev/null` to override this configuration.
PhysicsIsAwesome
pushed a commit
to PhysicsIsAwesome/secureblue
that referenced
this pull request
Mar 1, 2026
Use user-tmpfiles.d instead of ad-hoc systemd services to disable user-session QEMU core dumps and the KDE Plasma splash screen. For qemu.conf, the default file contents are only written if the file `~/.config/libvirt/qemu.conf` doesn't already exist. Thanks to @nihil-admirari for the suggestion: secureblue#1054 (comment) For ksplashrc, the file is always overwritten and is set to read-only, because certain theme settings in KDE Plasma will automatically try to overwrite that file. This also fixes a bug where the splash screen would be reenabled until next boot if the user logs out and logs back in. Users wishing to enable the splash screen can symlink the file `~/.config/user-tmpfiles.d/ksplashrc.conf` to `/dev/null` to override this configuration.
PhysicsIsAwesome
pushed a commit
to PhysicsIsAwesome/secureblue
that referenced
this pull request
Mar 4, 2026
Use user-tmpfiles.d instead of ad-hoc systemd services to disable user-session QEMU core dumps and the KDE Plasma splash screen. For qemu.conf, the default file contents are only written if the file `~/.config/libvirt/qemu.conf` doesn't already exist. Thanks to @nihil-admirari for the suggestion: secureblue#1054 (comment) For ksplashrc, the file is always overwritten and is set to read-only, because certain theme settings in KDE Plasma will automatically try to overwrite that file. This also fixes a bug where the splash screen would be reenabled until next boot if the user logs out and logs back in. Users wishing to enable the splash screen can symlink the file `~/.config/user-tmpfiles.d/ksplashrc.conf` to `/dev/null` to override this configuration.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use user-tmpfiles.d instead of ad-hoc systemd services to disable user-session QEMU core dumps and the KDE Plasma splash screen.
For qemu.conf, the default file contents are only written if the file
~/.config/libvirt/qemu.confdoesn't already exist.Thanks to @nihil-admirari for the suggestion: #1054 (comment)
For ksplashrc, the file is always overwritten and is set to read-only, because certain theme settings in KDE Plasma will automatically try to overwrite that file. This also fixes a bug where the splash screen would be reenabled until next boot if the user logs out and logs back in.
Users wishing to enable the splash screen can symlink the file
~/.config/user-tmpfiles.d/ksplashrc.confto/dev/nullto override this configuration.