-
-
Notifications
You must be signed in to change notification settings - Fork 86
Description
- Fvwm3 version (run:
fvwm3 --version
)
fvwm3 1.0.5 (1.0.4-116-g8342d9dc)
with support for: ReadLine, XPM, PNG, SVG, Shape, XShm, SM, Bidi text, XRandR, XRender, XCursor, XFT, NLS
- Linux distribution or BSD name/version
Debian 11
- Platform
Linux x86_64
Expected Behaviour
In four monitor setup, and DesktopConfiguration is set to "shared", there should be only one trigger for the new_desk event. However ...
Actual Behaviour
... new_desk event is triggered 7-9 times. Looks like as fast as it can until desk is changed. Reducing number of monitors to two, also reduces this triggering to 2-4.
Enabling logging
Function which is defined for new_desk event - if we put some Echo at the beginning (2 monitors):
[1645631581.505294] CMD_Echo: DESK IS: 2
[1645631581.615735] CMD_Echo: DESK IS: 2
[1645631581.633214] CMD_Echo: DESK IS: 2
[1645631581.654741] CMD_Echo: DESK IS: 2
[1645631583.051600] CMD_Echo: DESK IS: 3
[1645631583.087933] CMD_Echo: DESK IS: 3
Steps to Reproduce
-
Enable FvwmEvent module and configure new_desk to run some verbose/visible function
-
Configure virtual (or real) environment with 4 monitors.
-
Configure FVWM with
DesktopConfiguration shared
-
Enable monitors (example):
xrandr --output Virtual-1 --mode 1400x1050 --primary --output Virtual-2 --mode 1400x1050 --right-of Virtual-1 --output Virtual-3 --mode 1400x1050 --below Virtual-1 --output Virtual-4 --mode 1400x1050 --below Virtual-2
-
Restart FVWM (FvwmMFL must be enabled in config):
FvwmCommand Restart
-
Observe ~/.xsession-errors ~/fvwm.log or equivalent for echo from your function which is run by FvwmEvent on new_desk event
-
Does the problem also happen with Fvwm2?
N/A
Does Fvwm3 crash?
No.
Extra Information
This weird event behaviour may be similar to disfuctional monitor_focus in #604
Metadata
Metadata
Assignees
Labels
Type
Projects
Status