*** This bug is a duplicate of bug 1506358 ***
https://bugs.launchpad.net/bugs/1506358
BTW, you won't get a crash report either. Because although it starts out
as a serious-sounding C++ exception, libmirclient converts that into a
SIGHUP for consumption by C clients. And SIGHUP's default action is to
terminate without dumping core.
Normally SIGHUP is the right answer, because most such exceptions are
just "the server disconnected us or died". So we do want the client to
die (or catch the signal), and to not bother us with a core dump.
However bug 1506358 is a special unusual case where Mir has accidentally
mapped a serious exception indicating a programming error into a non-
serious SIGHUP. We need to learn to tell the difference between "normal"
(server died and disconnected) and abnormal (server's still running but
libmirclient is broken) exceptions...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - followed by "restart"
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
