Per the discussion above, this could be anywhere (qtmir, untiy8) not
necessarily in unity8 per se.
It does seem that this is specific to "unity8 on dragonboard" though.
We know that...
- mir-kiosk examples works on dragonboard
- unity8 works on arm64 m10
** Summary changed:
- arm64: history daemon dereferences a rogue pointer
+ dragonboard: history daemon dereferences a rogue pointer
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
dragonboard: history daemon dereferences a rogue pointer
Status in Snappy:
Status in linux package in Ubuntu:
Status in unity8 package in Ubuntu:
we are running the unity8 session snap on amd64 without any problems.
to setup and reproduce the problem follow the "on Dragonboard" section of
You can also find the panic signature at line 3276 of the attached
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~kernel-packages
Post to : email@example.com
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp