When typing Enter in mousepad with ibus-daemon running, mousepad and ibus-daemon consume 100% CPU

[Toshio Ito]

Binary package hint: mousepad

mousepad: 0.2.16-4ubuntu1
ibus: 1.3.7-1ubuntu3
ibus-anthy: 1.2.1-1
ibus-gtk: 1.3.7-1ubuntu3

I'm using Xubuntu 10.10 Live USB.
My language environment is Japanese, and I use iBus-anthy as the input method.

When I type Enter key in mousepad while ibus-daemon is running, there is no response from mousepad.
Instead, mousepad and ibus-daemon consume almost all the CPU.
If I do something to the mousepad's window, e.g, resize it, move it, switch to another window, activate its menu,
then the mousepad receives the Enter I just typed.

Notes:
- I suppose ibus-anthy is not responsible for the bug, because the problem occurs no matter what input method
is in use (I have only tested ibus-anthy and ibus-pinyin, though).
- In fact, the problem occurs even when no input method is used.
- Without any ibus-daemon process, the problem does not exist.
- "Shift + Enter" can be successfully input to mousepad.

References:
- These two Japanese blogs report that the same problem exists in Ubuntu 10.10 which had been upgraded from 10.04.
-- http://d-lights.jp/ubuntu/archives/416.html
-- http://d.hatena.ne.jp/ni_no5/20101016/1287233799
- The same problem is discussed in a Japanese thread about Arch Linux
-- http://read2ch.com/br_r/linux/1251213567/
- Perhaps this Chinese thread discusses the same problem (well, I'm not sure because I can't read Chinese)
-- http://code.google.com/p/ibus/issues/detail?id=99

Sorry, I could not find any report in English...

[Charlie Kravetz (cjkgeek)]

Thank you for reporting this issue. I can confirm this bug using Xubuntu 10.10 final version. When mousepad is started, the following is happening on my Athlon 64bit 3200

1. open Mousepad
2. open Task Monitor
3. type "this is a test" and hit ENTER
4. observe the CPU jumps to over 50% use
     observe the RSS goes from 14MiB to 608MiB before mousepad accepts the ENTER

I am attaching the ~/.xsession-errors log which shows the DBUS errors while this is in progress.

[vishal verma (vishal-is-verma)]

Thanks you for reporting this bug,
I tried to reproduce it in ubuntu Lucid 10.04.But my cpu usage was still 100%

[Toshio Ito (debug-ito)]

The problem still exists in Xubuntu Natty Beta1.

I found an upstream report in iBus project.
http://code.google.com/p/ibus/issues/detail?id=1192

There is a patch that seems to fix the problem.

[plutino (plutino)]

When changing line during editing, after the "enter" key is pressed, it takes a few seconds for line breaking to occur in the mousepad editing window.

To reproduce:
Open a new or exist file;
press "enter" key at any place within the file.

Actual result:
The line breaks after a few seconds

Expected result:
The line breaks instantly

OS: Xubuntu 10.10
Mousepad 0.2.16

[OmegaPhil (omegaphil)]

Note that this has more information on the Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631114

In the above, people have also experienced the problem through using ibus to enter non-English characters. Was originally reported to ibus here: https://code.google.com/p/ibus/issues/detail?id=1192 , but was demonstrated to be a mousepad bug.

[Lionel Le Folgoc (mrpouit)]

Hi,

Is it still reproducible with mousepad 0.3.0 in raring? Thanks.

[Toshio Ito (debug-ito)]

Sorry, I did not try Raring or Quantum.
The problem is still reproducible in Xubuntu Presice with mousepad 0.2.16-5ubuntu1, though.

[André Miranda (andreldm)]

I can't reproduce this bug with the latest version.
Please check if this bug still occur with new version.

OS: Archlinux 64-bit
Mousepad 0.3.0

[G-matt-8 (g-matt-8)]

Closing as fixed since it can't be reproduced with lastest version, which is a total re-write of version this bug is about, and which is no longer maintained or supported. Please feel free to re-open/make a new report if you experience it still in latest version.

[Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount)]

This bug should be fixed with version 0.2.16-6 (Debian). Ubuntu releases which ship a newer version of mousepad are not affected by this problem anymore.