Bug 208664 - scim-bridge outputting IOException when gvim run from terminal
Summary: scim-bridge outputting IOException when gvim run from terminal
Status: CLOSED DUPLICATE of bug 204657
Alias: None
Product: Fedora
Classification: Fedora
Component: scim-bridge
Version: rawhide
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-29 22:45 UTC by charles harris
Modified: 2012-09-29 12:08 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-09-30 04:05:35 UTC


Attachments (Terms of Use)

Description charles harris 2006-09-29 22:45:43 UTC
Description of problem:
When run from a terminal scim-bridge emits:
An IOException occurred at scim_bridge_client_imcontext_set_cursor_location ()
on start up and cursor motion.

When the gvim window is moved the followin errors are emitted:
Another agent is running...
Failed to allocate the agent. Exitting...
Failed to invoking the agent: Connection refused
Cannot launch the agent

I don't know if this is from the same component.


Version-Release number of selected component (if applicable):
scim-bridge-0.4.5-2.fc6
scim-bridge-gtk-0.4.5-2.fc6
vim-X11-7.0.109-3

How reproducible:
always


Steps to Reproduce:
1. open terminal
2. run gvim
3. move gvim window for further errors
  
Actual results:


Expected results:


Additional info:

Comment 1 Jens Petersen 2006-09-30 04:05:35 UTC
This was fixed a while back in scim-bridge-0.4.2
and I can't reproduce this anymore.  Perhaps you still had
an old scim-bridge-0.4.2 running?

Closing.  Can you reopen if you are sure you can still reproduce this?

*** This bug has been marked as a duplicate of 204657 ***

Comment 2 charles harris 2006-09-30 04:38:57 UTC
This bug resurfaced after I did a yum update today. I rebooted to make sure
there wasn't some sort of incompatability with the new stuff and it was still
there. The errors on moving the window were new to me, so I think it was
something new. I don't see it on my current machine with the same software
versions, but it definitely was there on my office machine. I'll reboot again
tomorrow and see if it persists.

Comment 3 Guru 2012-09-29 12:08:50 UTC
Just run below its works fine

scim-restart

-Guru


Note You need to log in before you can comment on or make changes to this bug.