bad extension state makes windows immovable (jumping back to previously saved position)

[peter-lyons-kehl]

Thank you for Smart Auto Move. I used to love it.

However, on a multi-screen in GNOME 42.2 (current Manjaro Linux), it started to move a window (of GNOME "Terminal" application) to one screen. If I press Alt+Space > "Move to Monitor Left", it's ignored. If I grab the (terminal's) menu bar and move it to another screen, right after I release the mouse button it moves back.

I have many "Saved Windows" and nothing in "Overrides":

[zanovis]

Are you using Static Workspaces? Settings > Multitasking > Workspaces > Static Workspaces

Reference: #22

[khimaros]

there may have been some backward compatibility issues with the config format between releases.

i'm sad to hear this bit you and i'll be more mindful of this with future releases.

@peter-kehl would you mind providing a dump of your current configuration? note, there may be some private information in window titles, so you may want to review before posting here. you can also email to me privately me@khimaros.com

you can grab a dconf dump with:

$ dconf dump /org/gnome/shell/extensions/smart-auto-move/

after you've done that, you can try to reset your configuration and see if it fixes your problem. after this you will need to manually reposition all of the windows and update your overrides (hopefully) one last time:

$ dconf reset -f /org/gnome/shell/extensions/smart-auto-move/

if you are able to reproduce after that, please let me know.

[peter-lyons-kehl]

Thank you. I don't use dynamic workspaces:

[peter-lyons-kehl]

Now I'm on GNOME 43. If all is fine for a few days, I'll close this. Thank you Khimaros.

[khimaros]

@peter-kehl i am curious to hear if the upgrade helped you. however, i do think this is a real bug which shows up in some circumstances and needs to be fixed.

in the meantime, there is a potential workaround, which is to run the following:

dconf reset /org/gnome/shell/extensions/smart-auto-move/saved-windows

it may be necessary to disable the extension, run the command, and then reenable but i have not yet confirmed this.