touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #00378
[Bug 1320114] Re: [DRM/GBM] Crashing Mir (via fatal signal) often leaves the screen blank and difficult to recover
** Branch linked: lp:~afrantzis/mir/platform-emergency-cleanup
** Changed in: mir
Milestone: 0.5.0 => 0.4.0
** Changed in: mir
Status: Triaged => Fix Released
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mir (Ubuntu)
Status: New => Fix Released
** Changed in: mir
Importance: Medium => High
** Changed in: mir (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1320114
Title:
[DRM/GBM] Crashing Mir (via fatal signal) often leaves the screen
blank and difficult to recover
Status in Mir:
Fix Released
Status in “mir” package in Ubuntu:
Fix Released
Bug description:
Add VT/DRM screen recovery to Mir's server crash handler...
We catch most crashes in here:
src/server/run_mir.cpp
and do lightweight cleanup of the socket file.
I think we should add VT/DRM screen recovery to the list of things
that get cleaned up there. Otherwise the user just gets a black screen
that is very hard to recover from.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1320114/+subscriptions