Thank you for your report. Unfortunately the stack trace is unusable for diagnostics. Is this problem reproducible? If so, please just try filing a new bug.
Thanks, Martin ** Attachment removed: "CoreDump.gz" http://launchpadlibrarian.net/8176531/CoreDump.gz ** Attachment removed: "Stacktrace.txt" http://launchpadlibrarian.net/8176538/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" http://launchpadlibrarian.net/8176539/ThreadStacktrace.txt ** Attachment removed: "Stacktrace.txt (retraced)" http://launchpadlibrarian.net/8210699/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt (retraced)" http://launchpadlibrarian.net/8210700/ThreadStacktrace.txt ** Changed in: restricted-manager (Ubuntu) Status: New => Invalid -- [apport] restricted-manager crashed with SIGSEGV https://bugs.launchpad.net/bugs/121976 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
