Although the logs also suggest that Unity8/USC had a hiccup/restart at
10:25 too, but without actually restarting.
The only definite error is the one in the telegram log, which is a
libmirclient exception.
** Summary changed:
- Mir crashes from time to time when using Telegram while network changes
+ Mir crashes from time to time when using Telegram while network changes
[AndroidWindow: Caught exception at Mir/EGL driver boundary (in dequeueBuffer):
Dynamic exception type: St11logic_error std::exception::what: state was not
valid]
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Tags added: android
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630230
Title:
Mir crashes from time to time when using Telegram while network
changes [AndroidWindow: Caught exception at Mir/EGL driver boundary
(in dequeueBuffer): Dynamic exception type: St11logic_error
std::exception::what: state was not valid]
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1630230/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs