[Touch-packages] [Bug 66104] Re: [Gutsy] scim: input freezes in various applications under XIM mode

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 25 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=201284.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2006-08-04T00:55:49+00:00 Leon wrote:

Description of problem:
Sometimes a KDE app will not accept inputs anymore (even input method is not
activated). The only thing I can do to have input again is change to "Simple
Composing Input Method" which is a test input method module in Qt, or restart
the application.

How reproducible:
not everytime

Steps to Reproduce:
1. Use a KDE app long enough
  
Actual results:
No inputs were outputted

Expected results:
Output english letters

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/0


On 2006-08-08T05:56:02+00:00 Jens wrote:

Yep, I think I saw this on KDE desktop while testing this morning.

Need to test with another IM to see if it is a kde/qt problem or
issue with scim.  XIM seems to work fine with other apps.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/1


On 2006-08-15T02:21:29+00:00 Leon wrote:

Reproducible in FC6 devel using the following test case by Choe Hwanjin:

1. $ export XMODIFIERS=@im=SCIM
2. $ export GTK_IM_MODULE=xim
3. $ gedit/kedit
4. press ctrl-N
5. try to type something

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/2


On 2006-08-15T02:54:45+00:00 Jens wrote:

See 
http://sourceforge.net/mailarchive/forum.php?thread_id=30112584&forum_id=43684
for more details.  It seems like that this is a xorg-x11 regression according to
discussion there.


Reply at: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/3


On 2006-08-15T09:42:37+00:00 Jens wrote:

Reproduced on fc5 and fc6.  RHEL4 and fc4 seem ok.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/4


On 2006-08-17T13:29:34+00:00 Jens wrote:

gedit loops with kinput2 and uim xim on rawhide.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/5


On 2006-08-18T15:12:13+00:00 Kevin wrote:

Adding upstream bug from the thread referred to in comment #3 above for 
tracking:
  https://bugs.freedesktop.org/show_bug.cgi?id=7869


Reply at: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/6


On 2006-08-19T05:38:37+00:00 Jens wrote:

(Problem also occurs with gcin fwiw.)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/7


On 2006-08-19T10:03:40+00:00 Jens wrote:

I'm not easily able to reproduce the problem on kde apps.

A workaround for gtk xim at least seems to be to set "/FrontEnd/X11/Dynamic = 
true"
in .scim/config (but that breaks deadkey support under XIM direct input).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/8


On 2006-08-20T04:21:13+00:00 Jens wrote:

This can also easily be reproduced with kinput2 and gedit.

1. setup kinpu2 and restart desktop
2. run gedit
3. activate kinput2 with Shift-Space and press Ctrl-n

at this point gedit goes into a hard loop.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/9


On 2006-08-20T09:38:51+00:00 Jens wrote:

Also reproduced with libX11-0.99.3 fwiw.

Here is a backtrace of where gedit loops with kinput2:

#0  XIfEvent (dpy=0x6ca790, event=0x7fff84fd6000, 
predicate=0x2ab427a0 <_CheckCMEvent>, arg=0x10b4000 " \220ݪ�*")
at IfEvent.c:58
#1  0x2ab42cea in _XimXRead (im=0x10b4000, recv_buf=0x7fff84fd61f0 "", 
buf_len=2048, ret_len=0x7fff84fd6144) at imTrX.c:446
#2  0x2ab45f86 in _XimReadData (im=0x10b4000, len=0x7fff84fd61a6, 
buf=0x7fff84fd61f0 "", buf_size=2048) at imTransR.c:154
#3  0x2ab46323 in _XimRead (im=0x10b4000, len=0x7fff84fd71fe, 
buf=0x7fff84fd61f0 "", buf_size=2048, 
predicate=0x2ab48c20 <_XimSyncCheck>, arg=0x10b8800 
"\200\217ݪ�*")
at imTransR.c:231
#4  0x2ab49d0e in _XimForwardEvent (ic=0x10b8800, ev=0x7fff84fd7290, 
sync=1) at imDefLkup.c:296
#5  0x2ab39c8b in _Xi

[Touch-packages] [Bug 66104] Re: [Gutsy] scim: input freezes in various applications under XIM mode

2014-10-06 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/66104

** Tags added: iso-testing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/66104

Title:
  [Gutsy] scim: input freezes in various applications under XIM mode

Status in “libx11” package in Ubuntu:
  Fix Released
Status in “scim” package in Ubuntu:
  Fix Released
Status in “libx11” source package in Hardy:
  Fix Released
Status in “scim” source package in Hardy:
  Fix Released
Status in “scim” package in Debian:
  Fix Released
Status in Fedora:
  Fix Released

Bug description:
  In gutsy, the default mode of scim (detemined by im-switch's settings
  "scim") uses XIM mode.  This may cause problems in some applications
  and make it impossible to input anything, even if you choose the
  English/Keyboard input method.  This happens most often in nautilus,
  but is also seen in gedit, gnome-terminal, etc.

  This bug has been around for a long time, it only became more visible
  because of the change in the default settings of scim and the Ubuntu
  package.

  There are two work arounds for this problem:

  1. If you do not use any programs linked to libstdc++5 (very few of
  the Ubuntu official packages do, one know exception is the fglrx video
  driver for ATi cards; but plenty of third-party programs do, such as
  firefox downloaded from www.mozilla.com, and Adobe's PDF reader), you
  can use the scim-immodule setting in im-switch.  To change the im-
  switch setting, just run "im-switch -s scim-immodule" command.

  2. If you do not use the deadkeys (often seen on European keyboards, and if 
you don't know what a deadkey is, you are not using it), you can change scim's 
"/FrontEnd/X11/Dynamic" setting.  The procedure to change this setting is:
  (a) Set scim not to start automatically (because it's useless to change the 
configuration file when scim is running) using the command "im-switch -s none". 
 Log out and re-login.
  (b) Edit your ~/.scim/config configuration file, change the 
/FrontEnd/X11/Dynamic option to true.
  (c) Reset scim to start automatically with command "im-switch -s scim". Log 
out and re-login.

  If you are using programs linked to libstdc++5 as well as deadkeys,
  there is no known workaround for you.  You may try the scim-bridge
  settings (you need to install scim-bridge-* packages first), but it's
  not clear whether it works or not (and I don't even know if there is a
  written scim-bridge setting for im-switch of not).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/66104/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp