-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forced to run way-displays
twice in order to load configuration file
#147
Comments
This one is "harmless", merely indicating that the monitor advertised two preferred modes. The warning message is misleading and the preferred modes are not printed however are correctly handled. |
way-displays was indeed getting stuck after cancellation, with the get kicking it into action. I'd be most grateful if you could test a fix, which retries after a cancellation, a maximum of 3 times: git clone [email protected]:alex-courtis/way-displays.git
cd way-displays
git 147-retry-cancellations
make
sudo make install When you are done you can:
|
The patch works great! Thanks for being so responsive. Here's the new log in case it's of interest to you: I [10:50:55]
I [10:50:55] Found configuration file: /home/surfer/src/dotfiles/.config/way-displays/cfg.yaml~home-triple
I [10:50:55]
I [10:50:55] Active configuration:
I [10:50:55] Arrange in a ROW aligned at the TOP
I [10:50:55] Order:
I [10:50:55] DP-4
I [10:50:55] DP-3
I [10:50:55] HDMI-A-6
I [10:50:55] Scaling: ON
I [10:50:55] Auto scale: OFF (min: 1.000)
I [10:50:55] Scale:
I [10:50:55] HDMI-A-6: 0.889
I [10:50:55] DP-3: 1.000
I [10:50:55] DP-4: 0.889
I [10:50:55] Mode:
I [10:50:55] DP-3: 2560x1440@240Hz
I [10:50:55] Transform:
I [10:50:55] HDMI-A-6: 90
I [10:50:55] DP-4: 90
libinput-config: initializing
libinput-config: replacing the device config functions
libinput-config: initializing the key mapper
libinput-config: couldn't read the config file
libinput-config: configuring device 'Power Button'
libinput-config: configuring device 'Video Bus'
libinput-config: configuring device 'Power Button'
libinput-config: configuring device 'Sleep Button'
libinput-config: configuring device 'Logitech G203 LIGHTSYNC Gaming Mouse'
libinput-config: configuring device 'Logitech G203 LIGHTSYNC Gaming Mouse Keyboard'
libinput-config: configuring device 'ZSA Technology Labs ErgoDox EZ Shine'
libinput-config: configuring device 'ZSA Technology Labs ErgoDox EZ Shine'
libinput-config: configuring device 'ZSA Technology Labs ErgoDox EZ Shine System Control'
libinput-config: configuring device 'ZSA Technology Labs ErgoDox EZ Shine Consumer Control'
libinput-config: configuring device 'ZSA Technology Labs ErgoDox EZ Shine Keyboard'
W [10:50:55]
W [10:50:55] WARNING: 2560x1440@60Hz (59,951mHz) already specified for 'DP-3', ignoring 2560x1440@240Hz (239,950mHz) (preferred)
I [10:50:55]
I [10:50:55] HDMI-A-6 Arrived:
I [10:50:55] info:
I [10:50:55] name: 'HDMI-A-6'
I [10:50:55] make: 'BNQ'
I [10:50:55] model: 'BenQ BL2411'
I [10:50:55] serial: 'K6G02666019'
I [10:50:55] desc: 'BNQ BenQ BL2411 K6G02666019 (HDMI-A-6)'
I [10:50:55] width: 520mm
I [10:50:55] height: 320mm
I [10:50:55] dpi: 94.52 @ 1920x1200
I [10:50:55] mode: 1920 x 1200 @ 60 Hz 59,950 mHz (preferred)
I [10:50:55] mode: 1920 x 1080 @ 60 Hz 60,000 mHz
I [10:50:55] mode: 1680 x 1050 @ 60 Hz 59,883 mHz
I [10:50:55] mode: 1600 x 1200 @ 60 Hz 60,000 mHz
I [10:50:55] mode: 1440 x 900 @ 60 Hz 59,901 mHz
I [10:50:55] mode: 1280 x 1024 @ 75 Hz 75,025 mHz
I [10:50:55] mode: 1280 x 1024 @ 60 Hz 60,020 mHz
I [10:50:55] mode: 1280 x 800 @ 60 Hz 59,910 mHz
I [10:50:55] mode: 1280 x 720 @ 60 Hz 59,950 mHz
I [10:50:55] mode: 1152 x 864 @ 75 Hz 75,000 mHz
I [10:50:55] mode: 1024 x 768 @ 75 Hz 75,029 mHz
I [10:50:55] mode: 1024 x 768 @ 60 Hz 60,004 mHz
I [10:50:55] mode: 1024 x 576 @ 60 Hz 59,967 mHz
I [10:50:55] mode: 832 x 624 @ 75 Hz 74,551 mHz
I [10:50:55] mode: 800 x 600 @ 75 Hz 75,000 mHz
I [10:50:55] mode: 800 x 600 @ 60 Hz 60,317 mHz
I [10:50:55] mode: 720 x 400 @ 70 Hz 70,082 mHz
I [10:50:55] mode: 640 x 480 @ 75 Hz 75,000 mHz
I [10:50:55] mode: 640 x 480 @ 60 Hz 59,940 mHz
I [10:50:55] current:
I [10:50:55] scale: 1.000 (0.985)
I [10:50:55] position: 4480,0
I [10:50:55] mode: 1920x1200@60Hz (59,950mHz) (preferred)
I [10:50:55] VRR: off
I [10:50:55]
I [10:50:55] DP-4 Arrived:
I [10:50:55] info:
I [10:50:55] name: 'DP-4'
I [10:50:55] make: 'BNQ'
I [10:50:55] model: 'BenQ BL2411'
I [10:50:55] serial: 'K6G02658019'
I [10:50:55] desc: 'BNQ BenQ BL2411 K6G02658019 (DP-4)'
I [10:50:55] width: 520mm
I [10:50:55] height: 320mm
I [10:50:55] dpi: 94.52 @ 1920x1200
I [10:50:55] mode: 1920 x 1200 @ 60 Hz 59,950 mHz (preferred)
I [10:50:55] mode: 1920 x 1080 @ 60 Hz 60,000 mHz 60,000 mHz 59,940 mHz
I [10:50:55] mode: 1920 x 1080 @ 50 Hz 50,000 mHz
I [10:50:55] mode: 1680 x 1050 @ 60 Hz 59,954 mHz
I [10:50:55] mode: 1600 x 1200 @ 60 Hz 60,000 mHz
I [10:50:55] mode: 1440 x 900 @ 60 Hz 59,887 mHz
I [10:50:55] mode: 1280 x 1024 @ 75 Hz 75,025 mHz
I [10:50:55] mode: 1280 x 1024 @ 60 Hz 60,020 mHz
I [10:50:55] mode: 1280 x 800 @ 60 Hz 59,810 mHz
I [10:50:55] mode: 1280 x 720 @ 60 Hz 60,000 mHz 60,000 mHz 59,940 mHz
I [10:50:55] mode: 1280 x 720 @ 50 Hz 50,000 mHz
I [10:50:55] mode: 1152 x 864 @ 75 Hz 75,000 mHz
I [10:50:55] mode: 1024 x 768 @ 75 Hz 75,029 mHz
I [10:50:55] mode: 1024 x 768 @ 60 Hz 60,004 mHz
I [10:50:55] mode: 1024 x 576 @ 60 Hz 59,977 mHz
I [10:50:55] mode: 832 x 624 @ 75 Hz 74,551 mHz
I [10:50:55] mode: 800 x 600 @ 75 Hz 75,000 mHz
I [10:50:55] mode: 800 x 600 @ 60 Hz 60,317 mHz
I [10:50:55] mode: 720 x 576 @ 50 Hz 50,000 mHz 50,000 mHz 50,000 mHz
I [10:50:55] mode: 720 x 480 @ 60 Hz 60,000 mHz 60,000 mHz 59,940 mHz 59,940 mHz 59,940 mHz
I [10:50:55] mode: 720 x 400 @ 70 Hz 70,082 mHz
I [10:50:55] mode: 640 x 480 @ 75 Hz 75,000 mHz
I [10:50:55] mode: 640 x 480 @ 60 Hz 60,000 mHz 59,940 mHz 59,940 mHz
I [10:50:55] current:
I [10:50:55] scale: 1.000 (0.985)
I [10:50:55] position: 2560,0
I [10:50:55] mode: 1920x1200@60Hz (59,950mHz) (preferred)
I [10:50:55] VRR: off
I [10:50:55]
I [10:50:55] DP-3 Arrived:
I [10:50:55] info:
I [10:50:55] name: 'DP-3'
I [10:50:55] make: 'Iiyama North America'
I [10:50:55] model: 'PL2790QS'
I [10:50:55] serial: '1178024901361'
I [10:50:55] desc: 'Iiyama North America PL2790QS 1178024901361 (DP-3)'
I [10:50:55] width: 600mm
I [10:50:55] height: 340mm
I [10:50:55] dpi: 107.97 @ 2560x1440
I [10:50:55] mode: 2560 x 1440 @ 240 Hz 239,950 mHz (preferred)
I [10:50:55] mode: 2560 x 1440 @ 144 Hz 143,856 mHz
I [10:50:55] mode: 2560 x 1440 @ 120 Hz 120,016 mHz 119,881 mHz
I [10:50:55] mode: 2560 x 1440 @ 96 Hz 96,006 mHz
I [10:50:55] mode: 2560 x 1440 @ 72 Hz 72,015 mHz
I [10:50:55] mode: 2560 x 1440 @ 60 Hz 60,008 mHz 59,951 mHz
I [10:50:55] mode: 2560 x 1440 @ 50 Hz 50,005 mHz
I [10:50:55] mode: 2560 x 1440 @ 48 Hz 48,003 mHz
I [10:50:55] mode: 2048 x 1280 @ 60 Hz 59,993 mHz
I [10:50:55] mode: 1920 x 1200 @ 60 Hz 59,885 mHz
I [10:50:55] mode: 1920 x 1080 @ 240 Hz 239,760 mHz
I [10:50:55] mode: 1920 x 1080 @ 120 Hz 120,000 mHz 119,880 mHz
I [10:50:55] mode: 1920 x 1080 @ 60 Hz 60,000 mHz 60,000 mHz 59,940 mHz
I [10:50:55] mode: 1920 x 1080 @ 50 Hz 50,000 mHz
I [10:50:55] mode: 1680 x 1050 @ 60 Hz 59,954 mHz
I [10:50:55] mode: 1600 x 1200 @ 60 Hz 60,000 mHz
I [10:50:55] mode: 1600 x 1000 @ 60 Hz 59,957 mHz
I [10:50:55] mode: 1600 x 900 @ 60 Hz 60,000 mHz
I [10:50:55] mode: 1440 x 900 @ 60 Hz 59,887 mHz
I [10:50:55] mode: 1280 x 1024 @ 75 Hz 75,025 mHz
I [10:50:55] mode: 1280 x 800 @ 240 Hz 239,950 mHz
I [10:50:55] mode: 1280 x 720 @ 60 Hz 60,000 mHz 59,940 mHz
I [10:50:55] mode: 1280 x 720 @ 50 Hz 50,000 mHz
I [10:50:55] mode: 1024 x 768 @ 75 Hz 75,029 mHz
I [10:50:55] mode: 0 x 0 @ 0 Hz 0,000 mHz
I [10:50:55] current:
I [10:50:55] (no mode)
I [10:50:55] VRR: off
I [10:50:55] (disabled)
I [10:50:55]
I [10:50:55] DP-3 Changing:
I [10:50:55] from:
I [10:50:55] (no mode)
I [10:50:55] VRR: off
I [10:50:55] (disabled)
I [10:50:55] to:
I [10:50:55] mode: 2560x1440@240Hz (239,950mHz) (preferred)
I [10:50:55] (enabled)
W [10:50:55]
W [10:50:55] WARNING: Changes cancelled, retrying
I [10:50:55]
I [10:50:55] HDMI-A-6 Changing:
I [10:50:55] from:
I [10:50:55] scale: 1.000 (0.985)
I [10:50:55] position: 4480,0
I [10:50:55] mode: 1920x1200@60Hz (59,950mHz) (preferred)
I [10:50:55] VRR: off
I [10:50:55] to:
I [10:50:55] VRR: on
I [10:50:55]
I [10:50:55] HDMI-A-6: Cannot enable VRR, display or compositor may not support it.
I [10:50:55]
I [10:50:55] DP-4 Changing:
I [10:50:55] from:
I [10:50:55] scale: 1.000 (0.985)
I [10:50:55] position: 2560,0
I [10:50:55] mode: 1920x1200@60Hz (59,950mHz) (preferred)
I [10:50:55] VRR: off
I [10:50:55] to:
I [10:50:55] VRR: on
I [10:50:55]
I [10:50:55] DP-4: Cannot enable VRR, display or compositor may not support it.
I [10:50:55]
I [10:50:55] DP-3 Changing:
I [10:50:55] from:
I [10:50:55] scale: 1.000 (1.125)
I [10:50:55] position: 0,0
I [10:50:55] mode: 2560x1440@240Hz (239,950mHz) (preferred)
I [10:50:55] VRR: off
I [10:50:55] to:
I [10:50:55] VRR: on
W [10:50:55]
W [10:50:55] WARNING: Changes cancelled, retrying
I [10:50:55]
I [10:50:55] HDMI-A-6 Changing:
I [10:50:55] from:
I [10:50:55] scale: 1.000 (0.985)
I [10:50:55] position: 4480,0
I [10:50:55] mode: 1920x1200@60Hz (59,950mHz) (preferred)
I [10:50:55] VRR: off
I [10:50:55] to:
I [10:50:55] scale: 0.891
I [10:50:55] position: 3907,0
I [10:50:55] transform: 90
I [10:50:55]
I [10:50:55] DP-4 Changing:
I [10:50:55] from:
I [10:50:55] scale: 1.000 (0.985)
I [10:50:55] position: 2560,0
I [10:50:55] mode: 1920x1200@60Hz (59,950mHz) (preferred)
I [10:50:55] VRR: off
I [10:50:55] to:
I [10:50:55] scale: 0.891
I [10:50:55] position: 0,0
I [10:50:55] transform: 90
I [10:50:55]
I [10:50:55] DP-3 Changing:
I [10:50:55] from:
I [10:50:55] scale: 1.000 (1.125)
I [10:50:55] position: 0,0
I [10:50:55] mode: 2560x1440@240Hz (239,950mHz) (preferred)
I [10:50:55] VRR: on
I [10:50:55] to:
I [10:50:55] position: 1347,0
W [10:50:55]
W [10:50:55] WARNING: Changes cancelled, retrying edit: popped in a clean log |
Well, that looks pretty good, thanks for testing. The last cancellation: was the position change correctly applied? FYI: you can disable VRR setting for known monitor that don't support it via: https://github.com/alex-courtis/way-displays/wiki/Configuration#vrr_off |
Hmmm. I'm not sure whether the changes have had the desired effect, I installed the latest version I no longer have to run I also do have VRR_OFF specified in my config, like so:
But something seems to go wrong based on the log file:
|
I see, thanks for reporting. It looks like we have some spurious cancellation or mishandled cancellations that are adding exceeding 3. As an emergency fix I'll increase it to 25 and resolve it definitively later. |
Released 1.10.1 to AUR |
Hi Alex, I updated way-displays to I don't need to run Based on the log file, it looks like enabling VRR for the 240Hz display (DP-3) is causing the failures/retries.
When I check
An unrelated detail is that the version number doesn't seem to be synchronized with the distributed package:
Just letting you know because the version number is also reported in the log files which are useful for debugging. Please let me know if I can help you debug this further. Thank you for all your effort on this software! |
That's really useful. Different versions of river/sway/wlroots are indeed behaving differently. Plan:
|
I use the river wayland compositor, so I have added the following to my river
init
script:Unfortunately, it seems that although the
way-displays
process is running, it doesn't actually apply the configuration until after I re-run it:Of course, I can add this to my
init
script with asleep
in front of it, but it looks and feels quite hacky (the screens flicker as they reconfigure).In the log file I can see that it detects my configuration file and loads the correct values (resolutions, refresh rates, transforms, scales). However then I get the line
WARNING: Changes cancelled, retrying
after which it doesn't appear to retry. In any case, it doesn't load the correct values. Although the process is running, the displays remain un-transformed and un-scaled... until I issue a follow upway-displays -g
after which it does load the correct values.Here is my log file:
Any idea what could be going wrong?
The text was updated successfully, but these errors were encountered: