SCIM entry hangs oowriter on main display, not "switch user" display

Bug #150457 reported by Dave M.
4
Affects Status Importance Assigned to Milestone
scim (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On a 6.06LTS system with all updates, a Japanese user recently developed trouble entering Japanese text with SCIM into oowriter. The symptom is that oowriter hangs after SCIM input converts a Kanji and the user types "enter" to accept the conversion. The characters are never un-hilighted and oowriter is unresponsive (does not repaint after exposes, but also does not use any CPU time). SCIM input into other programs still works OK.

An unusual twist: if the user logs in over another session using "Switch User," then SCIM and oowriter work OK. (IOW, if DISPLAY=:20.0, SCIM works.)

Ubuntu 6.06 LTS
Linux version 2.6.15-29-686 (buildd@terranova) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 SMP PREEMPT Mon Sep 24 17:24:47 UTC 2007
$ apt-cache showpkg scim
Package: scim
Versions:
1.4.4-1ubuntu12(/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_dapper_main_binary-i386_Packages)(/var/lib/dpkg/status)
$ apt-cache showpkg openoffice.org
Package: openoffice.org
Versions:
2.0.2-2ubuntu12.5(/var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_dapper-security_main_binary-i386_Packages)(/var/lib/dpkg/status)
2.0.2-2ubuntu12(/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_dapper_main_binary-i386_Packages)

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest ubuntu release?

Also, if this is still a problem, does the information at https://help.ubuntu.com/community/SCIM#Additional%20configuration%20if%20you're%20not%20using%20a%20CJK%20session help ?

Thanks in advance.

Changed in scim:
status: New → Incomplete
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in scim:
status: Incomplete → Invalid
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.