This bug hasn't been encountered for about 2 months. Looking at the
stack trace, it seems to me that qtmir is accessing 'name' member of a
session that's already been destroyed, from the
onSessionDestroyingSurface function. I don't think this is a problem in
Mir, but may still be a problem in qtmir, though it may have been masked
by code changes since around the last time this was seen.
** Changed in: mir (Ubuntu)
Status: New => Invalid
** Changed in: mir
Status: Triaged => Invalid
--
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/1494062
Title:
Crash in mir::scene::ApplicationSession::name (this=<optimized out>)
at /build/mir-
xon0uu/mir-0.14.1+15.04.20150821/src/server/scene/application_session.cpp:237
Status in Mir:
Invalid
Status in mir package in Ubuntu:
Invalid
Status in qtmir package in Ubuntu:
Invalid
Status in unity8 package in Ubuntu:
Invalid
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity8. This problem was most recently seen with version
8.11+15.04.20150831.2-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/991b418fa265212ec607fdb9a7ab715d6e60bbc2
contains more details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1494062/+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
