If removing the ~/.scim/ directory resolves this issue, I guess we cannot fix this bug. It seems to me that it is a configuration conflict between older versions and the current one. The user needs to do this step manually anyways as packages are not supposed to delete data in the users' home directory.
However, if this bug is a duplicate of bug #199592, which I cannot confirm as I cannot read stack traces (I'm not a programmer), it suggests that there is something else going on. Therefor I'm uncertain what to do with this. I cannot reproduce any of the reported scim related crashes at all. -- scim-bridge crashed with SIGSEGV in scim::Module::unload() https://bugs.launchpad.net/bugs/338217 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs