I think I have seen something quite similar to this bug. I made a fresh
report as Bug #1548226 which includes some valid symbolic stack traces.
Hopefully the developers will be able to use them to work on the issue.
Should this bug ticket be marked as a duplicate of Bug #1548226 as the
I don't understand this outdated debug symbol. I've been reporting this bug
for the fifth time, each time I did (apt-get update apt-get upgrade) just
before.
How to correctly report this bug?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
