During rpm-ostree operations, it's normal. Outside of that:
- Make sure you followed the nvidia steps in the readme if you're using nvidia.
- Make sure you're using an
asus
image if you're using asus.
No, use bubblejail
if there's no flatpak available for an app.
Override LD_PRELOAD
for that app. For flatpaks, this is as simple as removing the environment variable via Flatseal.
mitigations=auto,nosmt
is set on secureblue. This means that if your CPU is vulnerable to attacks that utilize Simultaneous Multithreading, SMT will be disabled.
- Check if it's already installed using
rpm -qa | grep x
- Check if there's a flatpak available at https://flathub.org
- Consider using distrobox or brew to install it
- Layer it using
rpm-ostree install
, as a last option
First check if the README already has an equivalent or better feature. If it doesn't, open a new github issue.
To use steam you can either:
- Install the flatpak
- Layer the rpm with:
rpm-ostree install steam
Bluetooth has a long and consistent history of security issues. However, if you still need it, run:
ujust toggle-bluetooth-modules
This is an issue with rpm-ostree image-based systems generally, and not specific to secureblue. Ideally upgrades would come in the form of a zstd-compressed container diff, but it's not there yet. Check out this upstream issue for more information.
The functionality that provides this, called GHNS, is disabled by default due to the risk posed by the installation of potentially damaging or malicious scripts. This has caused real damage.
If you still want to enable this functionality, run:
ujust toggle-ghns
Xwayland is disabled by default on GNOME, KDE Plasma, and Sway. If you need it, run:
ujust toggle-xwayland
This is because support for installing & using them has been intentionally disabled by default in secureblue. Only GNOME system extensions are trusted, if they are installed.
To enable support for installing GNOME user extensions, you can run ujust command:
ujust toggle-gnome-extensions
If your system time is off by an excessive amount due to rare conditions like a CMOS reset, your network will not connect. A one-time manual reset will fix this. This should never be required except under very rare circumstances.
For more technical detail, see #268
The DNSSEC setting we set in /etc/systemd/resolved.conf.d/securedns.conf
causes known issues with network connectivity when secureblue is used in a VM. To fix it, comment out DNSSEC=allow-downgrade
in that file and manually set a dns provider in network settings.
On the secureblue github page, click "Watch", and then "Custom", and select Releases like so:
AppImages depend on fuse2, which is unmaintained and depends on a suid root binary. For this reason, fuse2 support is removed by default. It's strongly recommended that you find alternative mechanisms to install your applications (flatpak, distrobox, etc). If you can't find an alternative and still need fuse2, you can add it back by layering something that depends on it.
For example:
rpm-ostree install zfs-fuse
Similar to the AppImage FAQ, the KDE Vault default backend cryfs
depends on fuse2. For this reason it's recommended that you migrate to an alternative that doesn't depend on fuse2, for example fscrypt
. If you don't want to do so, you can add fuse2 back by layering something that depends on it, as described in the AppImage FAQ.
ujust distrobox-assemble
There is an upstream bug. You may need to run:
mkdir -p ~/.config/environment.d && echo "GSK_RENDERER=gl" >> ~/.config/environment.d/gsk.conf
On some Nvidia machines, hardened-chromium
defaults to the X11 backend. Since secureblue disables Xwayland by default, this means that you will need to run ujust toggle-xwayland
and reboot, for hardened-chromium
to work.
Why don't some websites that require JIT/WebAssembly work in hardened-chromium even with the V8 Optimizer toggle enabled?
This is an upstream bug that prevents V8 optimization settings from being applied to iframes embedded within a parent website. As a result, WebAssembly may not function on services that use a separate URL for their content delivery network or other included domains, such as VSCode Web (https://github.dev). To make VSCode Web work properly, you need to manually allow V8 optimizations for the CDN by adding https://[*.]vscode-cdn.net
to your list of trusted websites.