custom shortcuts reset in reboot
Hey, this is not really up-to-date with current BlueBuild, but seeing as no other posts have been made about this I am assuming this is still ongoing, sorry if this has been solved already.
So basically, while trying to use a custom Bazzite built with BlueBuild a couple months back, I was having this weird issue where my Konsole shortcut would be replaced by the upstream (ptyxis) one, even after removing ptyxis from the system at build time in recipe.yml.
Not only that, but other shortcuts from flatpaks I installed would also reset and disappear upon rebooting. Would this be an issue with upstream bazzite or BlueBuild? Or is it an issue with my config (I've only added and removed packages, no custom modules made by me, trying to leave as simple as possible)? As always, thanks for your time and any answers!
7 Replies
I'm not that familiar with how shortcuts are handled by KDE Plasma or those other unspecified Flatpaks lol, but I do know that BlueBuild does not touch them unless you consciously choose to do so in your image
I have some custom shortcuts set up on GNOME with
gschema-overrides or dconf I think, and they are not always applied either
I find it likely that Bazzite sets some sort of authoritative shortcuts in some file, or possibly on boot, and that is what's overwriting your custom shortcuts
I suggest asking some fellow Bazzite users on ublue's discordI will, thanks. By the way, the flatpak shortcuts I talk about are set in KDE's settings, same as others. I click the Add Shortcut button and the shortcuts added from there also gets reset
They are not applied if you already modified gsetting as an user, that can be if you simply changed pinned apps in dash, changed sorting order in folder or similar
oh, that's a bummer
just doing gsettings reset to that modification should suffice
or well, good I guess so it doesn't overwrite anything
I worked on Bazzite & Bluefin to not do this with gschema overrides & dconfs, but idk what's up with desktop file situation