Athanasius
commented
3 months ago OK, reproduced it with as minimal a configuration as possible (whilst ensuring I could still interact with things as needed):
Athanasius_github_miggy_org-fvwm3_configs-1043-minimal.tar.gz
This still exhibits the issue. Opening a bunch of XTerm using the menu works fine on the left hand monitor, they get autotiled until there's no room, then it's manual placement. But on the right monitor they all go to the same position, all the way left and just under the FvwmPager for Desk1 on that monitor.
Upfront Information
Please provide the following information by running the command and providing the output.
Fvwm3 version (run:
fvwm3 --version): 1.1.0 (compiled from source myself using the git tag)Linux distribution or BSD name/version: Debian bookworm (which is on fvwm3 v1.0.6, hence compiling from source)
Platform (run:
uname -sp): Linux unknownExpected Behaviour
I'm converting over from an old fvwm2 configuration, and ended up starting from scratch so as to not be polluted by old/deprecated things. I'm trying to get window placement working how I want it to. I'm using
~/.fvwm/configas the initial configuration file. That then reads~/.fvwm/conf.d/commonfirst, which is where this configuration lies. It also then reads in~/.fvwm/conf.d/monitor-leftand~/.fvwm/conf.d/monitor-right. These last two files should only contain configuration specific to each monitor, i.e. mostly startup items.I now have
Style "*" TileManualPlacementincommon, which I expect to cause that placement scheme to be used for all windows that don't otherwise have a geometry/placement specified.Actual Behaviour
It appears to be working fine on the left monitor (where desk 0 is used), but appears to have no effect on the right one (where desk 1 is used). Instead all new windows are placed as if there were no windows currently displaying in that Desk+Page. They even ignore any window just created via the same method, i.e. menu item that performs
Exec exec xterm.Enabling logging
There is no new logging as I place windows. Nothing earlier looks relevant. I did check this immediately after fvwm3 first started and the behaviour was the same, i.e. this wasn't caused by a
Restart. This is the log file, which does include some restarts since as I was trying other options and addressing a need to usePositionPlacementforssh-askpass-fullscreen.fvwm3-output.log
Steps to Reproduce
How can the problem be reproduced? For this, the following is helpful:
Reduce the problem to the smallest
fvwmconfiguration example (where possible). Start with a blank config file (fvwm3 -f/dev/null) and go from there.I'll get back to you on this point, but see the attached configuration. It's possible I'm misunderstanding something about the fvwm3 paradigm for multiple monitors, with the ability to move/drag windows between them, i.e. using two desks when perhaps a single one would work.
Does the problem also happen with Fvwm2? No, I was using
Style "*" SmartPlacementthere, and it did work.Include your configuration with this issue.
Athanasius_github_miggy_org-fvwm3_configs.tar.gz
The
.XDGMenufile is just menus, as produced by theModule FvwmPerl -l fvwm-menu-desktop-config.fplwindow.Does Fvwm3 crash?
No.
Extra Information
As I said, this is a wholly new configuration, and I might be misunderstanding, and thus misconfiguring, something to do with multiple monitors but single X11 screen. I'm using this:
to get the monitors in the correct configuration/layout. So,
DP-4is the left monitor, andDP-2the right.$HOME/.fvwm/fvwm3-output.logfrom the step above. - Attached in that section.