The Move-Window shortcuts aren't being applied after reboot; help please!

[RainyCityDiver]

I'm running Mint 21.3 XFCE. In Menu > Settings > Window Manager > Keyboard tab there's 4 entries that allow keyboard shortcuts to be assigned to "Move window to X monitor" (with X = left, right, upper, lower). I set a shortcut for each:

• Lower: Ctrl-Alt-Down (arrow)
• Upper: Ctrl-Alt-Up (arrow)
• Left: Ctrl-Alt-Left (arrow)
• Right: Ctrl-Alt-Right (arrow)

I rebooted my machine, but the shortcuts don't work after startup, OR they work once per window, then stop. They're still listed in Window Manager. I can re-enter them each startup, but that's a true PITA.

How can I make these settings stick?

[michael-hi]

I notice that by default those keyboard shortcuts are already in use to show bottom/upper/left/right workspaces. Presumably you have cleared those shortcuts before setting the new ones. Of course, you would expect it to give a warning if you are trying to set a combination already in use, but maybe it doesn't always...

You've probably done that, in which case I can only think that perhaps the system erroneously retains, in some obscure location, a memory of the defaults and consequently gets confused on startup. After rebooting, it may be worth checking the Window Manager settings again to see if the defaults have also sneaked back in. Double-check also in the Settings Editor (under the xfce4-keyboard-shortcuts channel).

Failing that, I can only suggest choosing a different combination for the shortcuts and see if those stick. Sorry I can't give a more definitive reply

PS. I should add that bugs in the shortcut settings are not unknown - as here for instance:
https://forum.xfce.org/viewtopic.php?id=16739
Although that probably isn't directly related to your case, it makes me wonder if there might be something relevant in your ~/.xsession-errors file. If so, you could post the relevant lines here (plus your full System Info) and someone more technically minded might be able to interpret it.

[RainyCityDiver]

you would expect it to give a warning if you are trying to set a combination already in use, but maybe it doesn't always...

It did give me a warning when I set them up. I didn't clear those shortcuts first, I simply applied them to Window-move actions and clicked-through the 'apply to this new action' button each time the warning came up.

Double-check also in the Settings Editor (under the xfce4-keyboard-shortcuts channel).

They were indeed in Settings Editor. I removed the workspace-related entries, and added the window-to-monitor entries I wanted.

it makes me wonder if there might be something relevant in your ~/.xsession-errors file.

Yep, errors were present. Partway down (I think after the libva entries, but I'm not 100% certain) is where I started adding entries to Settings Editor.

Code: Select all

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:04.805: getMoveToMonitorProps: assertion 'current_rect->x == other_rect->x + other_rect->width' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:04.806: getMoveToMonitorProps: assertion 'other_rect->x == current_rect->x + current_rect->width' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:04.806: getMoveToMonitorProps: assertion 'other_rect->x == current_rect->x + current_rect->width' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:04.806: clientMoveToMonitorByDirectionTarget: assertion 'candidate_monitors != NULL' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:04.806: getMoveToMonitorProps: assertion 'current_rect->y == other_rect->y + other_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:04.806: getMoveToMonitorProps: assertion 'current_rect->y == other_rect->y + other_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:04.806: clientMoveToMonitorByDirectionTarget: assertion 'candidate_monitors != NULL' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:04.806: getMoveToMonitorProps: assertion 'other_rect->y == current_rect->y + current_rect->height' failed
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:54.007: getMoveToMonitorProps: assertion 'current_rect->x == other_rect->x + other_rect->width' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:54.007: getMoveToMonitorProps: assertion 'other_rect->x == current_rect->x + current_rect->width' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:54.007: getMoveToMonitorProps: assertion 'other_rect->x == current_rect->x + current_rect->width' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:54.007: clientMoveToMonitorByDirectionTarget: assertion 'candidate_monitors != NULL' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:54.007: getMoveToMonitorProps: assertion 'current_rect->y == other_rect->y + other_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:54.007: getMoveToMonitorProps: assertion 'current_rect->y == other_rect->y + other_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:54.007: clientMoveToMonitorByDirectionTarget: assertion 'candidate_monitors != NULL' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:23:54.007: getMoveToMonitorProps: assertion 'other_rect->y == current_rect->y + current_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:28:20.082: getMoveToMonitorProps: assertion 'current_rect->x == other_rect->x + other_rect->width' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:28:20.083: getMoveToMonitorProps: assertion 'other_rect->x == current_rect->x + current_rect->width' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:28:20.083: getMoveToMonitorProps: assertion 'other_rect->x == current_rect->x + current_rect->width' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:28:20.083: clientMoveToMonitorByDirectionTarget: assertion 'candidate_monitors != NULL' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:28:20.083: getMoveToMonitorProps: assertion 'current_rect->y == other_rect->y + other_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:28:20.083: getMoveToMonitorProps: assertion 'current_rect->y == other_rect->y + other_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:28:20.083: clientMoveToMonitorByDirectionTarget: assertion 'candidate_monitors != NULL' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:28:20.083: getMoveToMonitorProps: assertion 'other_rect->y == current_rect->y + current_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:28:52.397: getMoveToMonitorProps: assertion 'current_rect->y == other_rect->y + other_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:28:52.397: getMoveToMonitorProps: assertion 'current_rect->y == other_rect->y + other_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:28:52.398: clientMoveToMonitorByDirectionTarget: assertion 'candidate_monitors != NULL' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:28:52.398: clientMoveToMonitorByDirection: assertion 'target != NULL' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:29:52.634: getMoveToMonitorProps: assertion 'current_rect->x == other_rect->x + other_rect->width' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:29:52.634: getMoveToMonitorProps: assertion 'current_rect->x == other_rect->x + other_rect->width' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:29:52.634: clientMoveToMonitorByDirectionTarget: assertion 'candidate_monitors != NULL' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:29:52.634: clientMoveToMonitorByDirection: assertion 'target != NULL' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:31:21.078: getMoveToMonitorProps: assertion 'current_rect->y == other_rect->y + other_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:31:21.983: getMoveToMonitorProps: assertion 'other_rect->y == current_rect->y + current_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:31:23.114: getMoveToMonitorProps: assertion 'current_rect->y == other_rect->y + other_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:31:23.492: getMoveToMonitorProps: assertion 'current_rect->y == other_rect->y + other_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:31:23.492: getMoveToMonitorProps: assertion 'current_rect->y == other_rect->y + other_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:31:23.492: clientMoveToMonitorByDirectionTarget: assertion 'candidate_monitors != NULL' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:31:23.492: clientMoveToMonitorByDirection: assertion 'target != NULL' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:31:23.492: getMoveToMonitorProps: assertion 'other_rect->y == current_rect->y + current_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:31:23.687: getMoveToMonitorProps: assertion 'current_rect->x == other_rect->x + other_rect->width' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:31:23.986: getMoveToMonitorProps: assertion 'current_rect->y == other_rect->y + other_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:31:23.986: getMoveToMonitorProps: assertion 'current_rect->y == other_rect->y + other_rect->height' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:31:23.986: clientMoveToMonitorByDirectionTarget: assertion 'candidate_monitors != NULL' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:31:23.986: clientMoveToMonitorByDirection: assertion 'target != NULL' failed

(xfwm4:2675): xfwm4-CRITICAL **: 10:31:31.905: getMoveToMonitorProps: assertion 'other_rect->y == current_rect->y + current_rect->height' failed

[RainyCityDiver]

Double-check also in the Settings Editor (under the xfce4-keyboard-shortcuts channel).

They were indeed in Settings Editor. I removed the workspace-related entries, and added the window-to-monitor entries I wanted.

At the risk of celebrating too soon; I rebooted after entering the shortcuts into Settings Editor, and spent a little time playing with open windows, and I think it's working.

Does anyone know what file the Settings Editor > xfce4-keyboard-shortcuts entries live in? I'm searching online but not finding much yet...