-
Notifications
You must be signed in to change notification settings - Fork 194
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
GlazeWM crashes upon connecting multiple monitors via dock with 5 external monitors. "At least 1 workspace is required per monitor" #587
Comments
I have also seen this issue on a 3 monitor setup where the dock is connected to 2 monitors.
|
Crashes and inconsistencies on display setting changes, system standby, and monitor disconnections should now be fixed in v3 🎉 Latest release |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When connecting my laptop to the docking station, which is connected to 5 displays, GlazeWM crashes with a popup error message "At least 1 workspace is required per monitor". Starting GlazeWM again works but of course, I lose all window positions and workspace placements.
This error even happens if there are indeed 5 workspaces that are active. Running GlazeWM as administrator doesn't help either.
Displays layout and setup
These are all external screens. During the switch when connecting the dock, display "6", which is the internal laptop screen, is disabled.
3 : BenQ EL2870U (3840x2160@60Hz) (Set as primary monitor)
2 : BenQ EL2870U (3840x2160@60Hz)
1 : ASUS VG289Q1A (3840x2160@60Hz)
4 : ASUS VG289Q1A (3840x2160@60Hz) (Connected via DisplayLink adapter)
5 : LG IPS QHD (1440x2560@60Hz) (Connected via DisplayLink adapter)
6 : Internal Display (3000x2000@60Hz) (Disabled)
Hardware and Software
HP Spectre x360 13.5 (13th Gen Intel(R) Core(TM) i7-1355U, Intel Iris Xe Graphics, 32 GB RAM)
HP Thunderbolt Dock 120W G4
Windows 11 Pro 23H2 22635.3495 (Insider Build)
GlazeWM v2.1.1 (from Releases page, x64)
Log error message from errors.log
Configuration file config.yaml
The text was updated successfully, but these errors were encountered: