[Touch-packages] [Bug 1347789] Re: Crash in USC during mir::compositor::BufferQueue::BufferQueue::operator()

Also on a separate boot, an almost identical stacktrace from unity8 this time: Core was generated by `unity8'. Program terminated with signal SIGABRT, Aborted. #0 __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 #1 0xb620a05e in __GI_raise (sig=sig@entry=6)

[Touch-packages] [Bug 1347789] Re: Crash in USC during mir::compositor::BufferQueue::BufferQueue::operator()

** Also affects: mir Importance: Undecided Status: New ** Changed in: mir Status: New = Fix Released ** Changed in: mir (Ubuntu) Status: New = Confirmed ** Changed in: mir Importance: Undecided = Medium -- You received this bug notification because you are a member

[Touch-packages] [Bug 1347789] Re: Crash in USC during mir::compositor::BufferQueue::BufferQueue::operator()

Looks like we need to backport r1775 from mir/devel to 0.5 series... ** Changed in: mir Milestone: None = 0.6.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1347789

[Touch-packages] [Bug 1347789] Re: Crash in USC during mir::compositor::BufferQueue::BufferQueue::operator()

*** This bug is a duplicate of bug 1335481 *** https://bugs.launchpad.net/bugs/1335481 ** This bug has been marked a duplicate of bug 1335481 Mir servers crash with SIGABRT - assertion failed at buffer_queue.cpp:136 - !pending_client_notifications.empty() -- You received this bug