Bug 204118

Summary: scim-bridge outputting IOException on cursor movement
Product: [Fedora] Fedora Reporter: charles harris <charlesr.harris>
Component: scim-bridgeAssignee: Jens Petersen <petersen>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: eng-i18n-bugs, karsten, ryo-dairiki
Target Milestone: ---Keywords: i18n
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-28 09:03:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description charles harris 2006-08-25 18:13:12 UTC
Description of problem:

When started from a console gvim throws the error:
An IOException occured at scim_bridge_client_imcontext_set_cursor_location ()
Whenever the cursor is repositioned.

Version-Release number of selected component (if applicable):

vim-X11-7.0.066-1

How reproducible:

always

Steps to Reproduce:
1. start gvim
2. reposition cursor
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 charles harris 2006-08-25 18:23:09 UTC
The following messages are printed on file save:

Unknown message: Unknown
The socket is borken at scim_bridge_messenger_receive_message ()
Failed to receive messages at scim_bridge_client_read_and_dispatch ()
An IOException at scim_bridge_client_set_preedit_mode ()
An IOException occured at scim_bridge_client_imcontext_set_preedit_enabled ()
An IOException at scim_bridge_messenger_send_message (): Broken pipe
Failed to send a message at scim_bridge_client_set_preedit_mode ()
An IOException occured at scim_bridge_client_imcontext_set_preedit_enabled ()
The messenger is now down


Comment 2 Karsten Hopp 2006-08-25 18:49:10 UTC
gvim doesn't use scim directly, this most likely is a bug in the input method
user interface

Comment 3 Jens Petersen 2006-08-25 20:29:29 UTC
I believe this is already fixed in upstream cvs.

Comment 4 Jens Petersen 2006-08-28 09:03:27 UTC
Fixed in scim-bridge-0.4.1.

Comment 5 Ryo Dairiki 2006-08-31 06:49:15 UTC
Not, really.
This bug still exists.

Fortunately, scim-bridge-0.4.1 has auto reconneciton feature, 
which reopens the socket automatically on errors.
So this is not serious bug for users, because it repairs the connection as soon
as they type something on it.
I'll fix this on 0.4.3; Dealying 0.4.2 is not necessary I think.

Comment 6 Ryo Dairiki 2006-08-31 07:14:24 UTC
Fixed on 0.4.2. :)