I have been using Fedora Workstation for almost a year now. I did a fresh install on a Framework 16, and after configuring the system to my preferences, the “Maximize Window” keyboard shortcut disables itself after every reboot. As far as I can tell no other keybinds are behaving this way. I prefer to have the keybind set to ‘Super + F’ (with ‘Shift + Super + F’ being fullscreen) and the fullscreen keybind is working, but maximize keeps becoming disabled every reboot. It’s not even reverting to its default setting (Super + PgUp), its just disabled again, every time.
Hi and welcome to 
!
I have tested your issue and couldn’t reproduce it. After a reboot the shortcut stayed in place.
You could try resetting the whole dconf DB (with dconf reset -f /) after having it backed up (with dconf dump / >~/Documents/dconf.backup), then setting the key binding again.
Are you using any extensions? For example, Tiling Assistant may clear that binding in certain circumstances. Other tiling extensions may be similar.
To my surprise, this worked. I didn’t do anything differently than before though, other than one change, so this is just my best guess. I have used wmctrl in the past to add shortcuts for workspaces 5-10. For some reason wmctrl is not working to move windows to different workspaces anymore, so I did edit the dconf file to get this functionality back while keeping the wmctrl keybinds to move to workspaces 5-10 since they were already bound and working. When I reset dconf it obviously reset all my keybinds, so I removed wmctrl and just set the keybinds all in the dconf editor this time and everything is working the way it is supposed to now. The only other dconf configuration I haven’t repeated from before is removing the ‘close’ button from the appmenu since I just use the shortcuts to close all my windows (it looks nicer to me), but I don’t think that is the problem, but if it is I’ll post an update here again. I don’t actually think wmctrl caused this issue, I probably did something by accident, but it’s the only thing I can think of assuming I didn’t unintentionally do something stupid. Thanks for the help.
1 Like
I’ve had bad experiences with technical issues in the past from running just a few extensions and they don’t really provide enough functionality for me to justify using them a lot. I only run one extension these days, and that’s ‘AppIndicator and KStatusNotifierItem Support’ - I don’t see this extension being the cause of this issue. Even then, if this extension causes me issues in the future I can turn it off. The only thing I use it for is to kill programs running in the background which can be done with the system monitor or something like btop in the terminal.