Handle display connection loss gracefully instead of crashing#4811
Draft
Handle display connection loss gracefully instead of crashing#4811
Conversation
…fully Co-authored-by: Alexays <13947260+Alexays@users.noreply.github.com>
Co-authored-by: Alexays <13947260+Alexays@users.noreply.github.com>
… exit Co-authored-by: Alexays <13947260+Alexays@users.noreply.github.com>
… documentation Co-authored-by: Alexays <13947260+Alexays@users.noreply.github.com>
Co-authored-by: Alexays <13947260+Alexays@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix waybar crash issue when opening dosbox
Handle display connection loss gracefully instead of crashing
Feb 4, 2026
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
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.
Waybar crashes when the display connection breaks (e.g., when opening dosbox), showing "Error reading events from display: Broken pipe" before terminating. The GTK main loop doesn't recover from this condition.
Changes
Install GLib log handlers to intercept display errors (
src/client.cpp)gdkLogHandlerthat detects "Error reading events from display" and "Broken pipe" messagesgtk_app->quit()for clean shutdown, falls back tostd::exit(1)if GTK isn't initializedgtk_appcreation to ensure availability:G_LOG_LEVEL_MASKG_LOG_LEVEL_ERROR | G_LOG_LEVEL_CRITICALto avoid library interferenceResource cleanup (
include/client.hpp,src/client.cpp)~Client()destructor viag_log_remove_handler()Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.