I'm not sure what's going on, but a report like this is useless, without
a retrace the stack trace is unusable. I've filed bug #1363081 for
retracing now, but is there a way to get from the oops back to the
problem page on errors.c.c?
** Changed in: unity8 (Ubuntu)
Status: New => Incomplete
--
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/1362684
Title:
Crash in unity8 during autopilot tests
Status in “unity8” package in Ubuntu:
Incomplete
Bug description:
Summary:
unity8 crashes during autopilot tests
https://errors.ubuntu.com/oops/72b75aa2-2ec4-11e4-85a5-fa163e22e467
Steps:
1. Reboot the device
2. Wait for the device mount to settle (nautilus pops up, at that point
adb connection breaks)
3. Phablet-test-run -n -p unity8-autopilot unity8
Expected results:
Unity8 does not crash
Actual results:
Unity8 Crashes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1362684/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
