scim-bridge crashed with SIGSEGV in scim::IMEngineInstanceBase::get_frontend_data()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
scim-bridge (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: scim-bridge
Sorry, if this bug is a duplicate, but I couldn't recognize a really similarity to older bugs.
1)
Description: Ubuntu 9.10
Release: 9.10
2)
dpkg -l | grep scim
ii libscim8c2a 1.4.9-1ubuntu2 library for SCIM platform
ii scim 1.4.9-1ubuntu2 smart common input method platform
ii scim-bridge-agent 0.4.16-2ubuntu3 IME server of scim-bridge communicate with S
ii scim-bridge-
ii scim-gtk2-immodule 1.4.9-1ubuntu2 GTK+2 input method module with SCIM as backe
ii scim-modules-socket 1.4.9-1ubuntu2 socket modules for SCIM platform
3)
nothing
4)
As I wasn't using scim-bridge "actively", I just describe what I did:
I simply tab-jumped through Rhythmbox Music Player when the crash alert popped up. This can be reproduced by pressing tab in Rhythmbox about 10 times, but does not occur everytime.
ProblemType: Crash
Architecture: amd64
Date: Sun Nov 1 14:50:04 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
NonfreeKernelMo
Package: scim-bridge-agent 0.4.16-2ubuntu3
ProcCmdline: scim-bridge
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7f1321d4c9e6 <_ZN4scim20IMEn
PC (0x7f1321d4c9e6) ok
source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: scim-bridge
StacktraceTop:
scim::
?? ()
?? ()
?? ()
?? ()
Title: scim-bridge crashed with SIGSEGV in scim::IMEngineI
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
visibility: | private → public |
"Launching a SCIM process with x11...
Loading socket Config module ...
Creating backend ...
Loading x11 FrontEnd module ...
Failed to load x11 FrontEnd module.
SCIM has exited abnormally."
Since this is the output I get when I try to restart SCIM after a (possibly unprovoked? = I was using the google- chrome- unstable Browser in an unrelated matter at the time) sudden crash of scim-bridge, the bug I encountered may be related to this one.