crash of scim

Bug #70078 reported by aaren
4
Affects Status Importance Assigned to Milestone
scim (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

scim crashed. Report attached.

Revision history for this message
Kees Cook (kees) wrote :

(I trimmed the description and have attached the report so it is more easily parsable)

description: updated
Revision history for this message
Kees Cook (kees) wrote :

Hi! Thanks for the report.

Can you give some details about what you were doing when this crashed? What scim modules you have installed? Can you get the crash to repeat?

From the backtrace, it looks like scim::FrontEndModule::load failed.

Changed in scim:
status: Unconfirmed → Needs Info
Revision history for this message
ville palo (vi64pa) wrote :

backtraces are similiar with Bug #68771 (scim-launcher crashes on startup)
Could this be the same case?

Revision history for this message
Ming Hua (minghua) wrote :

Just a heads-up. This crasher seems to be quite common -- we have already at least five bugs reported: bug #68771, bug #70078, bug #71086, bug #72059, bug #76673.

I use scim myself on feisty and don't see any crash. Also since the scim package in Ubuntu is too different from the Debian one, I don't have a good guess where the problem may be (nobody seems to experience crashs in Debian), so I need help here. If someone can compare these backtraces or get a backtrace with debug symbols, it would help. Also it would be nice to figure out the exact environment of the system (there is a reportbug script /usr/share/bug/scim/script that may be useful), for example, which scim modules are installed, what locale setting and X keyboard mapping is used, GNOME or KDE, and which IM module (the setting of GTK_IM_MODULE and QT_IM_MODULE) is used, and so on.

I don't have time to investigate this, but if the problem is more clear or this bug can be reliably reproduced, I would be happy to look at it more closely.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for scim (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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