Ryan, Yea although there are lots of metoo's on this bug there isn't a given way to reproduce this bug, and I don't see it. The backtrace is also invalid thus there isn't any way to track it down either. The original bug report was actually for 1:3.2.0~rc4-1ubuntu1 which is quite a bit older so hopefully 1:3.2.0-4ubuntu2 fixes the issue. Otherwise if a new report is opened with a proper backtrace we may be able to track down the issue.
Thanks, Chris -- soffice.bin crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/518072 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
