[Bug 338217] Re: scim-bridge crashed with SIGSEGV in scim::Module::unload() - fixed by "rm -Rf ~/.scim/"

[Mario Vukelic]

Excuse the maybe ignorant question, but why is it assumed to be "just
the way it is" if a package chokes on its own config data after an
update? Certainly it should be expected to handle such a conflict in
some graceful way?

-- 
scim-bridge crashed with SIGSEGV in scim::Module::unload() - fixed by "rm -Rf ~/.scim/"
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.

Status in “scim-bridge” package in Ubuntu: Confirmed

Bug description:
Bug occured just after system start.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/scim-bridge
NonfreeKernelModules: nvidia
Package: scim-bridge-agent 0.4.14-2ubuntu5
ProcCmdline: scim-bridge
ProcEnviron:
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: scim-bridge
StacktraceTop:
 scim::Module::unload () from /usr/lib/libscim-1.0.so.8
 scim::Module::~Module () from /usr/lib/libscim-1.0.so.8
 ?? ()
 ?? ()
 ?? ()
Title: scim-bridge crashed with SIGSEGV in scim::Module::unload()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare