Portal:Aeon/Troubleshooting
Troubleshooting
This section describes known issues on Aeon and their solutions.
Always prompted for Recovery Key on boot
This is most likely due to your systems Encryption measurements being invalidated. Please read our Encryption Guide for more details.
Once the reason for the measurements changing is understood, you may update your systems measurements
Updating UEFI Firmware
Updating UEFI Firmware will always break the link between your systems TPM and Encryption.
Therefore if you are always being prompted for a Recovery Key after updating your systems firmware, you will need to run
sudo sdbootutil --ask-pin update-predictions
This will prompt for your Recovery Key to restore the link between your system and its encryption
Debugging Encryption Default Mode Issues
If sdbootutil update-predictions does not work, more information can be gathered by adding -v or -vv to the command. eg
sudo sdbootutil -vv --ask-pin update-predictions
This information will be required if you file a bug report
"Provided PIN Incorrect or TPM2 locked after too many retries"
Aeon is dependant on your systems TPM2 to unlock the Encryption in Default Mode
It is rare, but possible (especially after UEFI Firmware updates) to lock the TPM by not supplying the correct Recovery Key when updating predictions. The exact behaviour and duration of this lock depends on your hardware and cannot be bypassed by Aeon.
In this case you will need to either wait or reset the TPM in your systems UEFI/BIOS configuration, and then update new predictions with
sudo sdbootutil --ask-pin update-predictions
Rollback
Aeon has a strong focus on stability, but if in rare cases something goes wrong or a new update causes problems, this is not a problem because you can easily rollback to an older snapshot using Aeon's built-in rollback feature.
If a new update causes problems, we strongly recommend that you simply rollback the system and wait a few days for the problem to be fixed.
Do not use snapper for rollbacks!
There are two simple ways to perform a rollback:
One of the easiest ways is to simply press and hold space while booting. This will open a menu where you can see all the snapshots listed. By simply navigating using the arrow keys and pressing Enter, you can easily rollback to an older snapshot.
Perform this command inside the desired snapshot if you want it to be pinned as the "newest" snapshot:
sudo transactional-update rollback
Rollback using the Terminal
To display all snapshots available for rollback, you can exceptionally use snapper:
sudo snapper list
You can now perform the rollback using transactional-update:
sudo transactional-update rollback $NUM
Use 'last' instead of the snapshot number to rollback to the last working snapshot.
Set hostname
Set your hostname with the following command, as currently it doesn't work from Gnome Settings yet:
sudo hostnamectl set-hostname <new name>
Reboot and hostname change will take effect.
Adjust transactional-update.timer
Depending on your daily use case, the Timer may not trigger the automatic update process successfully even with persistent=true because it adds a randomized delay at each boot with RandomizedDelaySec
If you want automatic daily updates to your system, you may find that you need to adjust that delay mentioned.
Edit transactional-update.timer:
sudo systemctl edit transactional-update.timer
Add the following lines to create a override.conf (located in /etc/systemd/system/transactional-update.timer.d/override.conf)
[Timer]
RandomizedDelaySec=10m
The example above is for a randomized delay of max. 10 minutes. (Default value is 2h)
Change the time to your use case.
Steam flatpak opens, but can't start games
In case you run into this issue, where Steam opens, but games are not launching - that otherwise would - make sure that the Steam flatpak is allowed to run in the background:
flatpak permission-set background background com.valvesoftware.Steam yes