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

Bug #466331 reported by Olivier Jeulin
70
This bug affects 1 person
Affects Status Importance Assigned to Milestone
scim-bridge (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: scim-bridge

Ubuntu 9.10 (updated from 9.04 one day ago)

$ apt-cache policy scim-bridge scim-bridge-agent scim-bridge-client-gtk scim-bridge-client-qt scim-bridge-client-qt4
scim-bridge:
  Installé : (aucun)
  Candidat : (aucun)
 Table de version :
scim-bridge-agent:
  Installé : 0.4.16-2ubuntu3
  Candidat : 0.4.16-2ubuntu3
 Table de version :
 *** 0.4.16-2ubuntu3 0
        500 http://fr.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
scim-bridge-client-gtk:
  Installé : 0.4.16-2ubuntu3
  Candidat : 0.4.16-2ubuntu3
 Table de version :
 *** 0.4.16-2ubuntu3 0
        500 http://fr.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
scim-bridge-client-qt:
  Installé : (aucun)
  Candidat : 0.4.16-2ubuntu3
 Table de version :
     0.4.16-2ubuntu3 0
        500 http://fr.archive.ubuntu.com karmic/universe Packages
scim-bridge-client-qt4:
  Installé : (aucun)
  Candidat : 0.4.16-2ubuntu3
 Table de version :
     0.4.16-2ubuntu3 0
        500 http://fr.archive.ubuntu.com karmic/main Packages

I didn't do anything related to scim (for what I know). After logging as a normal user, I saw the "crashed application" icon, and it was about scim-bridge.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Oct 31 10:44:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/scim-bridge
Package: scim-bridge-agent 0.4.16-2ubuntu3
ProcCmdline: scim-bridge
ProcEnviron:
 LANGUAGE=fr_FR.UTF-8
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0xf1e5d7 <_ZN4scim6Module6unloadEv+23>: mov (%esi),%eax
 PC (0x00f1e5d7) 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 cdrom dialout lpadmin plugdev sambashare

visibility: private → public
Revision history for this message
Olivier Jeulin (olivierjln) wrote :
Download full text (3.6 KiB)

Seems to be like bugs 338217: I renamed ~/.scim/ and reinstalled scim (1.4.9-1ubuntu2) and scim doesn't crash anymore. But my previous configuration is lost (of course).
Here is the previous content of my .scim/, configured for chinese (pinyin).

If I recall correctly, some packages for the chinese support where uninstaled during the upgrade from Jaunty to Karmic.
Now I can't choose pinyin in scim because the scim-pinyin packale is not installed.

$ dpkg -l 'scim*'
ii scim 1.4.9-1ubuntu2 smart common input method platform
un scim-anthy <néant> (aucune description n'est disponible)
un scim-bridge <néant> (aucune description n'est disponible)
ii scim-bridge-agent 0.4.16-2ubuntu3 IME server of scim-bridge communicate with SCIM
ii scim-bridge-client-gtk 0.4.16-2ubuntu3 IME server of scim-bridge communicate with SCIM
un scim-bridge-client-qt <néant> (aucune description n'est disponible)
un scim-bridge-client-qt4 <néant> (aucune description n'est disponible)
un scim-canna <néant> (aucune description n'est disponible)
rc scim-chewing 0.3.3-1ubuntu1 Chewing IM engine module for SCIM
un scim-chinese <néant> (aucune description n'est disponible)
un scim-config-gconf <néant> (aucune description n'est disponible)
un scim-config-socket <néant> (aucune description n'est disponible)
un scim-frontend-socket <néant> (aucune description n'est disponible)
ii scim-gtk2-immodule 1.4.9-1ubuntu2 GTK+2 input method module with SCIM as backend
un scim-hangul <néant> (aucune description n'est disponible)
un scim-m17n <néant> (aucune description n'est disponible)
ii scim-modules-socket 1.4.9-1ubuntu2 socket modules for SCIM platform
un scim-modules-table <néant> (aucune description n'est disponible)
rc scim-pinyin 0.5.91-1ubuntu2 smart pinyin IM engine for SCIM platform
un scim-prime <néant> (aucune description n'est disponible)
un scim-server-socket <néant> (aucune description n'est disponible)
un scim-skk <néant> (aucune description n'est disponible)
un scim-tables-additional <néant> (aucune description n'est disponible)
un scim-tables-ja <néant> ...

Read more...

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug report is public and visible to everyone but I noticed that it has an attachment named 'CoreDump.gz'. It is possible that this contains sensitive information so I've set it back to private.

visibility: public → private
Revision history for this message
Olivier Jeulin (olivierjln) wrote :

Thanks for your concern.
No application with sensitive data (email reader, personnal file, IM, ...) was loaded between the opening of the session and the generation of the core dump. I also used "od -a" + "grep" to check for sensitive data (password, names), and I read the whole file. There is nothing in it that I consider sensitive (there's a user name, but that's OK).

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
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.