-
Notifications
You must be signed in to change notification settings - Fork 1.4k
fix: prevent Chromium crash when moving windows between monitors #2394
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
Merged
+19
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Oct 12, 2025
4855e99 to
9d623d8
Compare
Adds --disable-features=WaylandWpColorManagerV1 to Chromium and Brave flag configs to prevent crashes when moving windows between monitors or workspaces on Hyprland. This is a workaround for a Chromium/Wayland color management conflict. Upstream Chromium fix exists but won't reach stable for ~a month. This provides a temporary bridge until the fix lands in stable releases. Fixes basecamp#2384 Refs basecamp#2184 Refs: hyprwm/Hyprland#11957 Refs: hyprwm/Hyprland#11961 Refs: https://issues.chromium.org/issues/40263183 Refs: https://chromium-review.googlesource.com/c/chromium/src/+/7003036
9d623d8 to
35fdc8c
Compare
|
Need a migration to add this line to existing configs (use grep to check it's not already there, then sed to add it, see other migrations for the pattern). |
|
@dhh Added migration script to update existing user configs. The script:
Ready for review! |
Adds migration script to append --disable-features=WaylandWpColorManagerV1 to existing users' chromium-flags.conf and brave-flags.conf files. The script: - Checks if config files exist before attempting to modify them - Uses grep to verify the flag isn't already present - Only adds the flag and explanatory comment if needed - Handles both Chromium and Brave configurations This ensures existing Omarchy users get the Hyprland crash workaround without needing to manually update their configs. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
052af9b to
d9b2326
Compare
|
Updated migration script to use |
Merged
ahartness
pushed a commit
to ahartness/omarchy-hrtns
that referenced
this pull request
Oct 19, 2025
…ecamp#2394) * fix: prevent Chromium crash when moving windows between monitors Adds --disable-features=WaylandWpColorManagerV1 to Chromium and Brave flag configs to prevent crashes when moving windows between monitors or workspaces on Hyprland. This is a workaround for a Chromium/Wayland color management conflict. Upstream Chromium fix exists but won't reach stable for ~a month. This provides a temporary bridge until the fix lands in stable releases. Fixes basecamp#2384 Refs basecamp#2184 Refs: hyprwm/Hyprland#11957 Refs: hyprwm/Hyprland#11961 Refs: https://issues.chromium.org/issues/40263183 Refs: https://chromium-review.googlesource.com/c/chromium/src/+/7003036 * Add migration to update existing Chromium/Brave configs with crash fix Adds migration script to append --disable-features=WaylandWpColorManagerV1 to existing users' chromium-flags.conf and brave-flags.conf files. The script: - Checks if config files exist before attempting to modify them - Uses grep to verify the flag isn't already present - Only adds the flag and explanatory comment if needed - Handles both Chromium and Brave configurations This ensures existing Omarchy users get the Hyprland crash workaround without needing to manually update their configs. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]> * Fix warnings and make conditional explicit --------- Co-authored-by: Derek Castillo <[email protected]> Co-authored-by: Claude <[email protected]> Co-authored-by: David Heinemeier Hansson <[email protected]>
dhcrzf
pushed a commit
to dhcrzf/omarchy
that referenced
this pull request
Oct 21, 2025
…ecamp#2394) * fix: prevent Chromium crash when moving windows between monitors Adds --disable-features=WaylandWpColorManagerV1 to Chromium and Brave flag configs to prevent crashes when moving windows between monitors or workspaces on Hyprland. This is a workaround for a Chromium/Wayland color management conflict. Upstream Chromium fix exists but won't reach stable for ~a month. This provides a temporary bridge until the fix lands in stable releases. Fixes basecamp#2384 Refs basecamp#2184 Refs: hyprwm/Hyprland#11957 Refs: hyprwm/Hyprland#11961 Refs: https://issues.chromium.org/issues/40263183 Refs: https://chromium-review.googlesource.com/c/chromium/src/+/7003036 * Add migration to update existing Chromium/Brave configs with crash fix Adds migration script to append --disable-features=WaylandWpColorManagerV1 to existing users' chromium-flags.conf and brave-flags.conf files. The script: - Checks if config files exist before attempting to modify them - Uses grep to verify the flag isn't already present - Only adds the flag and explanatory comment if needed - Handles both Chromium and Brave configurations This ensures existing Omarchy users get the Hyprland crash workaround without needing to manually update their configs. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]> * Fix warnings and make conditional explicit --------- Co-authored-by: Derek Castillo <[email protected]> Co-authored-by: Claude <[email protected]> Co-authored-by: David Heinemeier Hansson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix Chromium Crash When Moving Windows Between Monitors
Problem
Chromium-based browsers (Chrome, Brave, etc.) crash instantly when dragging windows between monitors or moving them to different workspaces using Hyprland keybinds (super+shift+number). This started after recent Chromium updates enabled Wayland color management, which conflicts with Hyprland's implementation.
Note: A fix has landed upstream in Chromium but won't reach stable releases for approximately a month. This PR provides a temporary workaround in the meantime.
Solution
Add
--disable-features=WaylandWpColorManagerV1to default flag configs:config/chromium-flags.confconfig/brave-flags.confThese are deployed to
~/.config/during Omarchy setup and apply automatically to all Chromium-based browsers.Impact
Users can edit
~/.config/chromium-flags.confto customize or remove the flag once the upstream fix lands in their Chromium version.Testing
References