Recaptured windows can have a negative offset away from the page they should be on

[dumblob]

Upfront Information

• Fvwm3 version (run: fvwm3 --version)

fvwm3 1.0.5 (1.0.4-128-gc7b41a03)
with support for: ReadLine, XPM, PNG, SVG, Shape, XShm, SM, Bidi text, XRandR, XRender, XCursor, XFT, NLS

• Linux distribution or BSD name/version

Arch Linux

• Platform (run: uname -sp)

Linux 5.15.53-1-lts #1 SMP Fri, 08 Jul 2022 12:38:20 +0000 x86_64 GNU/Linux

Expected Behaviour

W0 and W1 will stay on their respective pages after killing and re-running fvwm3.

Actual Behaviour

See steps to reproduce.

Enabling logging

N/A

Steps to Reproduce

1. run plain X with a terminal emulator (W0)
2. run fvwm3 with the bundled config from W0
3. switch to second page and open new terminal emulator window there (W1)
4. in W1 run killall -9 fvwm3 (note killall fvwm3 is not enough to reproduce)
5. now you will see W1, you can interact with it with mouse, but any interaction with W1 using keyboard will not work, so you have to switch from X to console
6. from console run fvwm3 with the bundled config and DISPLAY=:N set accordingly
7. switch from console to X
8. observe W0 missing on any page (it was on first page)
9. observe W1 being on first page (it was on second page)
10. observe W0 having negative page number 😮

• Does the problem also happen with Fvwm2?

IDK

Does Fvwm3 crash?

No.

Extra Information

N/A

[dumblob]

Oh, thanks for the quick completion! May I ask where can I find the fix in the repo? Or which branch?

[ThomasAdam]

FYI this is a duplicate of #694 .

Hi @dumblob. No, it's not a duplicate of #694 -- they're different problems.

As for this problem, this also happens on fvwm2 as well. It'll be to do with how windows are being recaptured, but I'm inclined to put this very low on the priority list.