I think Mir's at fault here.
It's unreasonable to expect a client or shell to know it's being
screencast and avoid setting swap interval. Mir should handle (or
ignore) this transparently.
** Also affects: mir
Importance: Undecided
Status: New
** Summary changed:
- Exception when runni
(gdb) catch throw
Catchpoint 1 (throw)
(gdb) r -m /run/mir_socket -n1 -f /tmp/mir_screencast_768x1280.rgba
Starting program: /usr/bin/mirscreencast -m /run/mir_socket -n1 -f
/tmp/mir_screencast_768x1280.rgba
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-li
Seems it's not a fatal issue though, as the png was extracted correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425307
Title:
Exception when running phablet-screenshot (mako/vivid 110)
To m
