scratch that on https://bugs.launchpad.net/unity-system-compositor/+bug/1359951 seems the driver thread spawing is unrelated to the crash we're seeing. (which makes sense, it's been in there since the beginning)
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1387959 Title: [TOPBLOCKER] unity8 crash in image krillin rtm 139 Status in “unity8” package in Ubuntu: Confirmed Bug description: Earlier today, a few QA folks tested image krillin rtm 138 plus silo 13, and found that it fixed the unity8 crash from bug 1382595. Silo 13 plus silo 10 landed in image 139. Now, in image 139, unity8 is crashy again. Olli mentioned getting two crashes within a few minutes, and I got a unity8 crash while trying to accept an incoming call. I'm not sure if it's the same crash as before, or if it's a new one. Attached is the crash dump I got just after hitting 'accept' for an incoming call. I tried to pre-process it in apport-cli, but it failed with "Sorry, the program "unity8" closed unexpectedly // Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp