scim-bridge crashed with SIGSEGV in scim::IMEngineInstanceBase::get_frontend_data()

Bug #641146 reported by Xavier Fung
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
scim-bridge (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: scim-bridge

Apport simply comes up. Nothing erratic happens and SCIM behaves properly.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: scim-bridge-agent 0.4.16-2ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Fri Sep 17 17:18:16 2010
ExecutablePath: /usr/bin/scim-bridge
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: scim-bridge
ProcEnviron:
 LANG=en_HK.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xd8a447 <_ZN4scim20IMEngineInstanceBase17get_frontend_dataEv+7>: mov 0xc(%eax),%eax
 PC (0x00d8a447) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: scim-bridge
StacktraceTop:
 scim::IMEngineInstanceBase::get_frontend_data() () from /usr/lib/libscim-1.0.so.8
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: scim-bridge crashed with SIGSEGV in scim::IMEngineInstanceBase::get_frontend_data()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Xavier Fung (xavier114fch) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 scim::IMEngineInstanceBase::get_frontend_data (this=0x8f5ae00)
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in scim-bridge (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libxrender1: installed version 1:0.9.6+git20100705.d3d20437-0ubuntu0sarvatt, latest version: 1:0.9.6-1
libxext6: installed version 2:1.1.2+git20100705.23643bd1-0ubuntu0sarvatt, latest version: 2:1.1.2-1
libxfixes3: installed version 1:4.0.5+git20100705.01e803ae-0ubuntu0sarvatt, latest version: 1:4.0.5-1
libxcursor1: installed version 1:1.1.10+git20100604.0caadca5-0ubuntu0sarvatt, latest version: 1:1.1.10-2
libxcb-shm0: installed version 1.6+git20100703.75ff427d-0ubuntu0sarvatt2, latest version: 1.6-1
libxrandr2: installed version 2:1.3.0+git20100604.18517a55-0ubuntu0sarvatt, latest version: 2:1.3.0-3
libxcb-render0: installed version 1.6+git20100703.75ff427d-0ubuntu0sarvatt2, latest version: 1.6-1
libxcb1: installed version 1.6+git20100703.75ff427d-0ubuntu0sarvatt2, latest version: 1.6-1
libxinerama1: installed version 2:1.1+git20100605.d8a51c48-0ubuntu0sarvatt, latest version: 2:1.1-3
libxdamage1: installed version 1:1.1.3+git20100705.8abc1c8e-0ubuntu0sarvatt, latest version: 1:1.1.3-1
libxi6: installed version 2:1.3+git20100604.54fbe575-0ubuntu0sarvatt, latest version: 2:1.3-4
libxdmcp6: installed version 1:1.0.3+git20100604.39993ef6-0ubuntu0sarvatt, latest version: 1:1.0.3-2
libx11-data: installed version 2:1.3.4+git20100720.554da76e-0ubuntu0sarvatt3, latest version: 2:1.3.3-3ubuntu1
libpixman-1-0: installed version 0.19.3+git20100909.e29d9dfc-0ubuntu0sarvatt, latest version: 0.18.4-1
libx11-6: installed version 2:1.3.4+git20100720.554da76e-0ubuntu0sarvatt3, latest version: 2:1.3.3-3ubuntu1
libxcomposite1: installed version 1:0.4.2+git20100705.01c4691e-0ubuntu0sarvatt, latest version: 1:0.4.2-1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.