Second Monitor/Desk FvwmPager displays incorrect state at startup #1077
Comments
|
Are you starting the pager in your StartFunction, or from your configuration directly? If this is at startup, how are you putting xterms on a different desk/page, using a style, when are these being launched? |
|
I've added a tar file of a cut-down configuration that still shows the issue. I'll see what else I can cull out of it. It's started via:
There's also specific configuration for You might want to hold off until I've boiled this down to the bare minimum. |
|
We need your full configuration file (or a simple way to recreate the issue with the default configuration), anyways you shouldn't be using |
|
Note if using the default-config file (just |
I'm just editing my X startup file to specify the configuration file, it's no hassle. |
|
I've now boiled the configuration down, keeping what seems relevant (i.e. remove extraneous styling and menus) to: |
I'll see if migrating the start of these things to |
|
Changing over to I'll just go test that change in my normal configuration to confirm then close this. At least I'll have documented the gotcha for others :) . |
|
Yea, I think the issue is some interaction with Note your approach of having one pager per monitor is fine too, I was just pointing out we have tried to make the pager a bit more understandable of the |
|
Maybe have some |
|
Well, what's working is using Confirmed working correctly with my full configuration, so closing this. Is |
|
To me what was happening is the Pager was run before everything got setup (some sort of race condition), so the Pager was initializing before everything was moved into place and didn't know what pages everything was on. Once the pager is running it then takes some event for fvwm to resend info to the pager, which is why after you moved pages/desks, those events fired updating the pager on the actual location of things. Being someone who uses the shared mode, test out |
Yes, I always thought it felt like some sort of race condition.
Ah, so possibly even more improved functionality for dual monitors ? Atm I'm putting up with using the two desks and moving items between them as needed. It's at least better than my old fvwm2 config with the separate X Screens where I simply could not move anything between the two. I'd also been pondering a setup with a set of 3x2 Desks, each with only a single Page, and moving between them, rather than between pages. Although I've seen some issues with changing which monitor is viewing which desk as well. I should investigate that more and open a separate issue if I can't find a reconfiguration to prevent it. Anyway, thanks for the hint. I'll make a note to look into those additional options. |
|
|
|
Hmm, seems I might be incorrect, |
This actually brings the bug back:
The order looks a little funky there because I've tried both starting the LefPanelDP[42] before the AthanInitFunctionDP[42] calls, and after. In both cases the FvwmPager display bug at startup is back. So it seems I really do need to keep the stuff I had in |
Which is in effect what I'm now doing, with everything coming from As I understand it, unless you put |
As a first change to my configuration I now have this for my primary monitor: and similarly for What I initially tried was only having the one desk, but that didn't seem to work, with windows seeming to be randomly placed between the two monitors. I'll have another look at that now this change is satisfactory. |
|
Right, so even with the What I'd really like is a single desktop, and each monitor to show a single page from it without interfering with the other. Obviously there'd have to be some restriction or swapping of view if you try to go e.g. page 0,0 to page 0,1 on one monitor when the other was already showing it. Either that would have to be blocked, with some feedback, or the other monitor get swapped over to page 0,0. My use case would be something like a browser window and needing it now on the 'other' monitor without moving it between desks. Still, the MonitorLabels seem to be a better method of switching which desk which monitor is displaying. I'm still seeing some issues with fvwm3 restarts and it being confused about which desk (at least, maybe also page) some windows should be on. I'll look more closely at that and open a new issue for it though. |
|
The whole point of |
Sure, although in my case I still have one per monitor because sometimes one of them has something fullscreen (like the YouTube video I'm watching right now). Using So, thanks again for the nudge towards using that :) . |
|
Whilst the configuration change has fixed this for startup ... it's exhibiting the same buggy behaviour on a restart. The only two things in my The old FvwmPager-related lines relating to The only place In this case I have Firefox also now running, with Desk 1 windows on Page 1,1 - but everything is showing piled up in Desk 1 / Page 0,0 until I change pages on that desk. Then everything moves back to where it should be (both the Firefox windows, and the XTerms on Page 1,0). |
|
Open up a new issue for this, would you? A short video demonstrating this behaviour, along with a minimal fvwm2rc file, would really help. |
|
Two questions before you open another issue. Did this issue come from modifying your configuration, and it didn't happen before? I was also wondering if it is maybe an edge case the last patch I made for the issue of placing windows on different desks/monitors caused, if you revert that patch does the issue go away? Creating a minimal configuration using |
|
I can only state with confidence that I've seen some general issues with Restart, with some windows shifting between desks, but that might have been related to not utilising StartFunction for the FvwmPagers, instead I had them starting in InitFunction and restarting in RestartFunction. I'll look into a minimal reproduction and video tomorrow. |
|
I've now opened #1082 with details, some videos, and example configuration (as |
Upfront Information
Please provide the following information by running the command and providing
the output.
Fvwm3 version:
fvwm3 1.1.1 (1.1.0-89-ged4bb8503)- but note this was happening with stock 1.1.0 as well. I compile locally from a git clone, and either simplymake installthat into/usr/local/, or build a Debian package (based off the Debian fvwm3 package files for that, with any necessary tweaks given changes since) and install that.Linux distribution or BSD name/version:
Debian 12/bookworm(plus some limited backports and third-party repo packages)Platform (run:
uname -sp):Linux unknownExpected Behaviour
With at least one additional monitor, with a configuration where it gets its own Desk, the FvwmPager on that additional desk should show the current windows, in the correct pages, and the correct "currently active" page highlighted.
For my configuration it should look like:
NB: This is after I've used my
Ctrl+Down Arrowkeybind to move vertically down one page to 1,1, hence it being highlighted:Actual Behaviour
On startup it looks like all the second monitor windows are in the top-left (so, 0, 0) page of the second desk, but it's just a visual artefact. As soon as I change page within that second desk everything starts displaying correctly again. Specifically my second desk windows are a pair of XTerms that should be in middle-top, and when I use a keybind to go to middle-bottom (this is 3x2 pages), it displays correctly.
As you can see:
Enabling logging
I don't see anything relevant in this:
fvwm3-output.log
Steps to Reproduce
How can the problem be reproduced? For this, the following is helpful:
I'll work up a minimum configuration to show the problem and ping with a follow-up comment when I edit it in.A cut-down configuration, which shouldn't have any particular dependencies (i.e. additional programs or availability of hosts), that shows the issue:issue-1077-min-config.d.tar.gz
Does the problem also happen with Fvwm2? - Nothing like this did, but then with fvwm2 I was running each display as it's own distinct Xorg Screen, so a completely different configuration.
Include your configuration with this issue.
Does Fvwm3 crash?
No.
Extra Information
Anything else we should know?
Feel free to take a screen capture or video and upload to this issue if you
feel it would help.
Attach
$HOME/.fvwm/fvwm3-output.logfrom the step above.The text was updated successfully, but these errors were encountered: