ibus-engine-pinyin crashed with signal 7 in PyZy::PhoneticContext::update()

[sepwei]

看不到图标

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: ibus-pinyin 1.5.0-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Tue Mar 11 11:00:18 2014
ExecutablePath: /usr/lib/ibus/ibus-engine-pinyin
InstallationDate: Installed on 2014-03-11 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140309)
ProcCmdline: /usr/lib/ibus/ibus-engine-pinyin --ibus
ProcEnviron:
 LANGUAGE=zh_CN:zh
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
Signal: 7
SourcePackage: ibus-pinyin
StacktraceTop:
 ?? ()
 ?? ()
 PyZy::PhoneticContext::update() () from /usr/lib/x86_64-linux-gnu/libpyzy-1.0.so.0
 PyZy::PhoneticContext::reset() () from /usr/lib/x86_64-linux-gnu/libpyzy-1.0.so.0
 ?? ()
Title: ibus-engine-pinyin crashed with signal 7 in PyZy::PhoneticContext::update()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 PY::BopomofoEditor::updateLookupTableLabel (this=this@entry=0x1d74a00) at PYBopomofoEditor.cc:214
 PY::BopomofoEditor::updateLookupTable (this=0x1d74a00) at PYBopomofoEditor.cc:243
 PyZy::PhoneticContext::update() () from /tmp/apport_sandbox_jeyOpk/usr/lib/x86_64-linux-gnu/libpyzy-1.0.so.0
 PyZy::PhoneticContext::reset() () from /tmp/apport_sandbox_jeyOpk/usr/lib/x86_64-linux-gnu/libpyzy-1.0.so.0
 PY::BopomofoEngine::reset (this=0x1d39a80) at PYBopomofoEngine.cc:173

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.