Disabling monitor does not call RandrFunc

Hawkmoon · 17 February 2023 18:19

I’m not sure when exactly RandrFunc is going to trigger.

I’m trying to trigger it when connecting/disconnecting a monitor, basically on xrandr --output HDMI-1 --off and xrandr --output HDMI-1 --auto. But no such luck.

It does get triggered when changing position with xrandr --output HDMI-1 --right-of DP-1 etc, and changing resolution.

Is this intentional or a bug?

Hawkmoon · 18 February 2023 10:26

Thinking further it’s probably a bug, or at least a feature request, so I opened an issue:

github.com/fvwmorg/fvwm3

Disabling/enabling monitor does not call RandRFunc

opened 10:24AM - 18 Feb 23 UTC

entropic77

type:bug

## Upfront Information * Fvwm3 version: fvwm3 1.0.7 (1.0.6a-8-g2327aac1) *… Linux distribution or BSD name/version: Debian 11.6 Bullseye * Platform (run: `uname -sp`): Linux unknown ## Expected Behaviour I expected RandRFunc to trigger when connecting/disconnecting a monitor. Basically on `xrandr --output HDMI-1 --off` and `xrandr --output HDMI-1 --auto`. ## Actual Behaviour The RandRFunc is not triggered. FvwmEvent's `monitor_enabled`/`monitor_enabled` functions are also not triggered. RandRFunc is called correctly on resolution and position change (for example `xrandr --output HDMI-1 --right-of DP-1`) ## Steps to Reproduce I'm using this minimal configuration file: ``` BugOpts DebugRandR true DestroyFunc RandRFunc AddToFunc RandRFunc + I Echo "randrfunc called" ``` Then executing `xrandr --output HDMI-1 --auto` followed by `xrandr --output HDMI-1 --off` gives the following output in the log, but "randrfunc called" is not logged. ``` [1676715323.394479] monitor_output_change: monitor_output_change: outputs have changed [1676715323.397734] monitor_update_ewmh: monitor debug... [1676715323.397788] monitor_dump_state: Monitor Debug [1676715323.397808] monitor_dump_state: number of outputs: 2 [1676715323.397833] monitor_dump_state: Name: DP-1 Disabled: false Is Primary: yes Is Current: yes Is Previous: yes Output: 68 Coords: {x: 0, y: 0, w: 2560, h: 1440} VirtScr: { VxMax: 0, VyMax: 0, Vx: 0, Vy: 0 EdgeScrollX: 0, EdgeScrollY: 0 CurrentDesk: 0 CurrentPage: {x: 0, y: 0} MyDisplayWidth: 2560, MyDisplayHeight: 1440 } Desktops: yes Flags:global [1676715323.397884] monitor_dump_state: Name: HDMI-1 Disabled: false Is Primary: no Is Current: no Is Previous: no Output: 71 Coords: {x: 0, y: 0, w: 1920, h: 1080} VirtScr: { VxMax: 0, VyMax: 0, Vx: 0, Vy: 0 EdgeScrollX: 0, EdgeScrollY: 0 CurrentDesk: 0 CurrentPage: {x: 0, y: 0} MyDisplayWidth: 2560, MyDisplayHeight: 1440 } Desktops: yes Flags:global [1676715323.417977] ewmh_ComputeAndSetWorkArea: monitor 'DP-1': {l: 0, r: 0, t: 0, b: 0} {x: 0, y: 0, w: 2560, h: 1440} [1676715323.419066] ewmh_ComputeAndSetWorkArea: monitor 'HDMI-1': {l: 0, r: 0, t: 0, b: 0} {x: 0, y: 0, w: 1920, h: 1080} ``` ``` [1676715329.950613] monitor_output_change: monitor_output_change: outputs have changed [1676715329.954508] monitor_update_ewmh: monitor debug... [1676715329.954562] monitor_dump_state: Monitor Debug [1676715329.954579] monitor_dump_state: number of outputs: 2 [1676715329.954593] monitor_dump_state: Name: DP-1 Disabled: false Is Primary: yes Is Current: yes Is Previous: yes Output: 68 Coords: {x: 0, y: 0, w: 2560, h: 1440} VirtScr: { VxMax: 0, VyMax: 0, Vx: 0, Vy: 0 EdgeScrollX: 0, EdgeScrollY: 0 CurrentDesk: 0 CurrentPage: {x: 0, y: 0} MyDisplayWidth: 2560, MyDisplayHeight: 1440 } Desktops: yes Flags:global [1676715329.954656] monitor_dump_state: Name: HDMI-1 Disabled: false Is Primary: no Is Current: no Is Previous: no Output: 71 Coords: {x: 0, y: 0, w: 1920, h: 1080} VirtScr: { VxMax: 0, VyMax: 0, Vx: 0, Vy: 0 EdgeScrollX: 0, EdgeScrollY: 0 CurrentDesk: 0 CurrentPage: {x: 0, y: 0} MyDisplayWidth: 2560, MyDisplayHeight: 1440 } Desktops: yes Flags:global [1676715329.956858] ewmh_ComputeAndSetWorkArea: monitor 'DP-1': {l: 0, r: 0, t: 0, b: 0} {x: 0, y: 0, w: 2560, h: 1440} [1676715329.957642] ewmh_ComputeAndSetWorkArea: monitor 'HDMI-1': {l: 0, r: 0, t: 0, b: 0} {x: 0, y: 0, w: 1920, h: 1080} ```

system · 18 February 2024 10:27

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.