scim crashes Xchat

Bug #34851 reported by viyyer
This bug report is a duplicate of:  Bug #64011: Scim and m17n. Edit Remove
16
Affects Status Importance Assigned to Milestone
scim-m17n (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

on having Scim running on background crashed xchat. I have tested on different boxes . I am attaching xchat logs here.
It main sticks around looking for scim/m17n/*mim files. this log is pretty much what I get across different systems

Revision history for this message
viyyer (viyyer) wrote : strace output in reference to the bug report.

attached the strace log.

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

Please also attach the output of "/usr/share/bug/scim/script 3>&1" (or use "/usr/share/bug/scim/script 3> file" and attach the redirected file.

Thanks for reporting.

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

Hmm, something seems to be wrong with scim-m17n. On my computer it just refuse to start at all. I can specify the m17n module, but no input methods show up. I'll have to investigate more on scim-m17n. On the other hand, other SCIM modules are working fine.

Revision history for this message
viyyer (viyyer) wrote : Re: [Bug 34851] scim crashes Xchat

I don't seem to have a "/usr/share/bug/scim/ " directory.

Ming Hua wrote:

>Public bug report changed:
>https://launchpad.net/malone/bugs/34851
>
>Comment:
>Please also attach the output of "/usr/share/bug/scim/script 3>&1" (or
>use "/usr/share/bug/scim/script 3> file" and attach the redirected file.
>
>Thanks for reporting.
>
>

Revision history for this message
Doug Rintoul (doug-rintoul) wrote :

The problem with the scim-m17n module not working with dapper is cause by a version mismatch in the libm17n-0 library and the m17n-db. libm17n-0 is at version 1.2.0 in dapper but m17n-db is at 1.3.1. I Created a 1.3.3 version of libm17n-0 and installed it and scim-m17n started working again.

Revision history for this message
Doug Rintoul (doug-rintoul) wrote :

I also want to state that with libm17n-0 up to 1.3.3, xchat does not crash for me. I can enable scim in xchat and type using different IMs.

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

On Thu, Mar 16, 2006 at 08:57:04PM -0000, viyyer wrote:
>
> Comment:
> I don't seem to have a "/usr/share/bug/scim/ " directory.

Right. So scim-m17n doesn't depends on scim, which is definitely a bug
but irrelevant to this crash/can't start issue.

Thanks for spotting this. I'll fix it later.

Ming
2006.03.16

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

On Thu, Mar 16, 2006 at 10:26:12PM -0000, Doug Rintoul wrote:
>
> Comment:
> The problem with the scim-m17n module not working with dapper is cause
> by a version mismatch in the libm17n-0 library and the m17n-db.
> libm17n-0 is at version 1.2.0 in dapper but m17n-db is at 1.3.1. I
> Created a 1.3.3 version of libm17n-0 and installed it and scim-m17n
> started working again.

Hmm, I was concerned about this when I heard about the m17n-db upgrade.
But some one told me that libm17n 1.2 works with m17n-db 1.3. I'll have
to look closer.

Doug, thanks a lot for investigating this issue.

Revision history for this message
Doug Rintoul (doug-rintoul) wrote :

I haven't confirmed this, but I think the difference might be do to the handling of wildcards in /usr/share/m17n/mdb.dir. m17n-db 1.2 listed each mim file separately. 1.3.1 uses (input-method * "*.mim"). It is possible that libm17n 1.2 does not handle wildcards.

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

Downgrading m17n-db to 1.2.0-1 fixes my scim-m17n. And it seems to work fine in XChat, I can even input Chinese in XChat with m17n-py module (in XIM mode). So Doug's version mismatch theory seems more and more likely.

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

Using libm17n-0 1.3.1-1 (rebuilt from Debian unstable) along with m17n-db 1.3.1-1build1 works with scim-m17n as well.

A version mismatch is almost certain. The question is how to solve it. I'll ask the Debian maintainer of m17n stuff.

Revision history for this message
viyyer (viyyer) wrote :

I think this can now be confirmed as a bug.

Changed in scim-m17n:
status: Unconfirmed → Confirmed
Revision history for this message
HPNadig (hpnadig) wrote :

> Created a 1.3.3 version of libm17n-0 and installed it and scim-m17n
> started working again.

Doug, can you share with us deb file of that version?

Thanks,

Revision history for this message
Doug Rintoul (doug-rintoul) wrote :

I would be glad to share the deb files. Drop me an email, an I will send them to you.

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

Doug's analysis above about .mim list format is correct.

TAKAHASHI Naoto, a m17n developer, recently gave the following answer on scim-devel mailing list:

> I have installed the Dapper on my old laptop and found a version
> mismatch; m17n-db is 1.3.l but libm17n-0 is 1.2.0.

> Edit /usr/share/m17n/mdb.dir. Replace the line
>
> (input-method * "*.mim")
>
> with
>
> (input-method bn itrans "bn-itrans.mim")
> (input-method bn unijoy "bn-unijoy.mim")
>
> and so on. You can include as many lines as you want.

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

By the way, the title of this bug is completely wrong. Is there anybody still experiencing Xchat crash with scim-m17n? If not, the bug title and description should be changed (and maybe merged with bug #64011 as well).

Revision history for this message
HPNadig (hpnadig) wrote :

no, the GNOME or GTK based applications were crashing with SCIM, but now seem OK.

The problem is that the default installation still does not let people to just install m17n with SCIM and start using it. Some of us can patch them up, but normal users can't, even it is just 1 or 2 lines.

We should make sure that the version mismatch is corrected and no issues would prevail at least on Edgy :)

Revision history for this message
HPNadig (hpnadig) wrote :

ah, just ignore my comments here. I just read on the other bug related discussion that this has already been solved on Edgy.

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

The real reason of the crash is a package version mismatch in dapper. Fixed in edgy.

Since the title and description is too misleading, I'm marking this as a duplicate of bug #64011, which has a much more clear and short decription of the problem.

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.