Probably worth mentioning, just recently seen & described here https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1302550 which was duplicated (so, don't be fooled that this was fixed, we're considering this an active bug)
Some summary from IRC its an issue because unity8 is exited for our AP testing go "while true; do restart unity8; done" you should hit the issue after a few times * see note obvious issue for debugging is that it's running under upstart, you might want to run it under gdb, so `stop unity8`, export MIR_ things (you can check which in initctl get-env --global | grep MIR), and then loop it under gdb SIGILL on startup is expected, so you might go "gdb -ex run -ex continue unity8" * note: some discussion about just starting/stopping unity8 might not reproduce it. Since you need an app to be running to invoke screenshots - but saviq thinks he saw it just looping unity8 too. ** Changed in: mir Status: New => Confirmed ** Changed in: mir Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1256360 Title: unity8 crashed with SIGSEGV in glDeleteTextures() from mir::scene::GLPixelBuffer::~GLPixelBuffer() from mir::scene::ThreadedSnapshotStrategy::~ThreadedSnapshotStrategy() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1256360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs