Another report of the same crash came in today.
Perhaps we need a fix like that of bug 1579630.
** Summary changed:
- Mir crashed with std::exception::what: Couldn't clear output eDP-1
(drmModeSetCrtc = -13)
+ Mir/unity-system-compositor crashed with std::exception::what: Couldn't clear
output
I tried this yesterday with the latest daily 16.04 image and just wanted
to note that the user-facing behavior is the same. I didn't check the
logs to see if the same messages were appearing but could do more if it
would help.
--
You received this bug notification because you are a member of Ubun
** Changed in: unity-system-compositor
Importance: Undecided => High
** Changed in: unity-system-compositor (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539
** Changed in: mir (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539811
Title:
Mir crashed with std::exception::what: Couldn't clear output eDP-1
(drmMod
I tried reproducing this yesterday with the Mir demos, but no luck yet.
I suspect we'll have to modify some code to more easily reproduce the
problem. I don't think you need to do anything more right now, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
@Daniel, let me know if there's something I can test for you (or a
different log I can scrape) to check if something is turning the screen
off when I try to enter the Mir session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Changed in: unity-system-compositor
Status: New => Invalid
** Changed in: unity-system-compositor
Status: Invalid => New
** Package changed: unity8-desktop-session (Ubuntu) => unity-system-
compositor (Ubuntu)
** Changed in: unity-system-compositor
Status: New => Confirme
Error 13 is "Permission denied". That could mean unity-system-compositor
is being shut down from a VT other than the one it is running on. So we
might expect to see that error.
I'm tempted to say if this only happens on shutdown then we just need to
make it a non-fatal error. However there's only
