custom shortcuts reset in reboot

So I've got a weird problem with a custom image of Bazzite created using BlueBuild, in which the shortcuts I set in KDE settings are reset after a full reboot. The image doesn't have many changes, only package changes (adding and removing packages) and setting some extra options, nothing custom-made by me so I don't think BlueBuild is to blame. By the way, the only shortcuts I set are to change from ptyxis to konsole and an extra one for a flatpak app. Another thing of note is I also remove ptyxis from the image, but even then the shortcuts reset (even the extra one for the flatpak gets deleted as far as I remember). If anyone has any insight into what could be the cause for this I would appreciate it. In case it's needed, here's the image recipe's link: https://github.com/MrQvest/my-atomic/blob/main/recipes/recipe-bazzite-nvidia.yml Thanks for your time and any answers!
GitHub
my-atomic/recipes/recipe-bazzite-nvidia.yml at main · MrQvest/my-at...
Contribute to MrQvest/my-atomic development by creating an account on GitHub.
8 Replies
HikariKnight
HikariKnight2w ago
iirc there is a script, i think bazzite-user-setup that you need to modify to stop it from doing that since we utilize ptyxis and the script does that change to "update" older systems that had konsole as default to get the new default. it will be enough to just have your custom image overwrite the script with a modified version that does not replace the terminal shortcuts. the one for the flatpak i dont know about unless its a shortcut that conflicts with something we set.
Qvest
QvestOP7d ago
Sorry for late reply, but I took a look at the script and it seems it should not execute more than once? It has these lines at the end: # Prevent future executions echo "Writing state file" echo $USER_SETUP_VER > $USER_SETUP_VER_FILE echo $FEDORA_VERSION > $USER_SETUP_FEDORA_VER_FILE echo $BASE_IMAGE_NAME > $USER_SETUP_IMAGE_VER_FILE Does this amount to anything or should I try to fiddle with the script? I'm afraid of breaking things Script file: https://github.com/ublue-os/bazzite/blob/main/system_files/desktop/shared/usr/libexec/bazzite-user-setup
GitHub
bazzite/system_files/desktop/shared/usr/libexec/bazzite-user-setup ...
Bazzite is a cloud native image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld. - ublue-os/bazzite
HikariKnight
HikariKnight7d ago
sorry its bazzite-desktop-bootstrap i was thinking about that runs each time you go to the desktop but it does not seem to edit any shortcuts
Qvest
QvestOP7d ago
Does bazzite have any systemd services that might cause this then? Does dconf do anything in KDE or is it just GNOME? There is a dconf-update.service that seems to execute on boot, maybe that's it?
HikariKnight
HikariKnight7d ago
dconf is just for gnome and gnome applications and we have no service that touches this to my knowledge
Qvest
QvestOP7d ago
Weird, so you're saying the system as it is shouldn't reset any shortcuts on reboot?
HikariKnight
HikariKnight7d ago
it shouldnt touch anything to my knowledge since i have custom shortcuts and they work fine but i have not replaced shortcuts to ptyxis and stuff since i prefer it over konsole
Qvest
QvestOP7d ago
So weird... gonna test it again and see if this persists, been a while since I used ublue, thanks for your time

Did you find this page helpful?