-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
Crash on monitor hotplugging #947
Comments
Hi @galibert Yeah, OK. Presumably the following helps?
|
ThomasAdam
added a commit
that referenced
this issue
Feb 21, 2024
When two monitors go to one monitor (undocking a laptop with one external display, for example), don't set the previous monitor if it's the same as the current monitor. Fixes #947
It does indeed, thanks :-) |
ThomasAdam
added a commit
that referenced
this issue
Feb 22, 2024
When two monitors go to one monitor (undocking a laptop with one external display, for example), don't set the previous monitor if it's the same as the current monitor. Fixes #947
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Upfront Information
Please provide the following information by running the command and providing
the output.
fvwm3 --version
)fvwm3 1.1.0 (1.0.9-15-g4af6dbe6)
with support for: ReadLine, XPM, PNG, SVG, Shape, XShm, SM, Bidi text, XRandR, XRender, XCursor, XFT, NLS
Arch
uname -sp
)Linux unknown
Expected Behaviour
Not crash :-)
Actual Behaviour
My laptop has one external screen connected to a dock and another to the hdmi port. When disconnecting the dock and cable nothing much happens (for some reason the desktop is not automatically reconfigured by X, maybe to allow reconnecting?). Then I go under arandr to switch off the screens and change the primary to the laptop screen. Fvwm3 segfaults at that point.
This happens because toggle_prev_monitor_state gets prev = nullptr due to the monitor not existing anymore, hence monitor_resolve_name(prev_focused_monitor) returning nullptr.
Ideally fvwm3 should follow the RANDR events, but at least if it didn't crash it would be possible to put things back in place through a simple restart. If I do arandr, restart then unplug I have no crash.
fvwm2 randomly crashes in xcb in such a configuration, either at restart time or when a notification happens.
The text was updated successfully, but these errors were encountered: