It sounds weird to me that the service can crash that hard and systematically.
Are you using a11y specifically, and does turning that off change the
situation. I know that may not be practical, but it could clarify whether the
issue comes under special circumstance or not.
Otherwise, is there a test procedure that we could follow to try and
make it crash here as well? With a particular set of actions?
Last, i'd be interested to know which machines it's crashing on, and
which are not prone to exposing the issue. That may also be HW related,
but at this point it's just an hypothesis.
Thanks in advance for your feedback.
** Changed in: unity (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: unity
Status: Confirmed => Incomplete
** Changed in: unity (Ubuntu)
Assignee: Canonical Desktop Experience Team (canonical-dx-team) => Neil J.
Patel (njpatel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810145
Title:
unity-panel-service crashed with SIGABRT in __kernel_vsyscall()
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/810145/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
