scim-bridge crashed with SIGSEGV in scim::Module::unload()

[HX_unbanned]

Binary package hint: scim-bridge

Using Ubuntu 9.10, Synaptic Package Manager 0.62.5.
After resuming from Hibernate, the ScreenSaver cannot be ended by any keyboard / mouse combination and after clicking or pressing ESC key, the mouse cursor shows, ScreensSaver freezes and that's it.
After mouse shows up and screensaver stays on the monitor in frozen state, I can move cursor to edit box or button and even mouse cursos changes on entering password edit box nad reacts by Loading cursor on pressing Log-In button.
Nothing else happens. Only way to start using FUCKING linux is to reboot.
After reboot, the "scim-bridge" error shows up.

ProblemType: Crash
Architecture: i386
CheckboxSubmission: d82ad5d42a6a777de05b0242b853a17a
CheckboxSystem: ac7bec3a75145a77f3583d717595c2f5
CrashCounter: 1
Date: Tue Oct 20 07:59:41 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/scim-bridge
NonfreeKernelModules: fglrx
Package: scim-bridge-agent 0.4.16-2ubuntu3
ProcCmdline: scim-bridge
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x67c5d7 <_ZN4scim6Module6unloadEv+23>: mov (%esi),%eax
 PC (0x0067c5d7) ok
 source "(%esi)" (0x4444415f) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
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.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #338217, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.