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 running phablet-screenshot (mako/vivid 110)
+ Exception when running phablet-screenshot (mako/vivid 110)
[std::exception::what: Attempt to set swap interval on screencast is invalid]
** Tags added: screencast
** Changed in: mir
Importance: Undecided => Medium
** Changed in: mir (Ubuntu)
Importance: Undecided => Medium
** Changed in: mir
Status: New => Triaged
** Changed in: mir (Ubuntu)
Status: New => Triaged
--
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)
[std::exception::what: Attempt to set swap interval on screencast is
invalid]
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1425307/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
