ibus daemon cpu use flares up briefly when editing in Gedit

Bug #1299759 reported by Lars Noodén
144
This bug affects 32 people
Affects Status Importance Assigned to Milestone
ibus (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

When resuming an edit in Gedit, the ibus daemon flares up, abusing the CPU for a short while. This happens every time lately. All that's needed is to switch windows back to Gedit and resume editing. Then the CPU usage spikes for a moment before going back down. I would expect that the correct behavir is for the CPU usage to stay low, no matter the activity in Gedit.

top has the following, sometimes even higher use, but it's very hard to catch since it happens for only a moment:

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 2730 user 20 0 373672 23440 1740 R 172,6 0,6 45:11.21 ibus-daemon
 2756 user 20 0 285672 3660 2604 S 105,9 0,1 26:31.45 ibus-x11
 2525 root 20 0 358760 118124 21216 S 87,6 3,0 197:29.28 Xorg
11441 user 20 0 971708 73700 17856 S 81,3 1,9 13:22.85 gedit

syslog has this:

Mar 30 13:50:48 lubuntu dbus[482]: [system] Activating service name='org.freedesktop.hostname1' (using servicehelper)
Mar 30 13:50:48 lubuntu dbus[482]: [system] Successfully activated service 'org.freedesktop.hostname1'
Mar 30 13:51:36 lubuntu kernel: [212933.326558] CPU2: Core temperature above threshold, cpu clock throttled (total events = 7467)
Mar 30 13:51:36 lubuntu kernel: [212933.326559] CPU6: Core temperature above threshold, cpu clock throttled (total events = 7467)
Mar 30 13:51:36 lubuntu kernel: [212933.326562] CPU4: Package temperature above threshold, cpu clock throttled (total events = 14104)
Mar 30 13:51:36 lubuntu kernel: [212933.326564] CPU5: Package temperature above threshold, cpu clock throttled (total events = 14104)
Mar 30 13:51:36 lubuntu kernel: [212933.326566] CPU1: Package temperature above threshold, cpu clock throttled (total events = 14104)
Mar 30 13:51:36 lubuntu kernel: [212933.326567] CPU0: Package temperature above threshold, cpu clock throttled (total events = 14104)
Mar 30 13:51:36 lubuntu kernel: [212933.326569] CPU3: Package temperature above threshold, cpu clock throttled (total events = 14104)
Mar 30 13:51:36 lubuntu kernel: [212933.326571] CPU7: Package temperature above threshold, cpu clock throttled (total events = 14104)
Mar 30 13:51:36 lubuntu kernel: [212933.326572] CPU6: Package temperature above threshold, cpu clock throttled (total events = 14104)
Mar 30 13:51:36 lubuntu kernel: [212933.326585] CPU2: Package temperature above threshold, cpu clock throttled (total events = 14104)
Mar 30 13:51:36 lubuntu kernel: [212933.327540] CPU2: Core temperature/speed normal
Mar 30 13:51:36 lubuntu kernel: [212933.327541] CPU6: Core temperature/speed normal
Mar 30 13:51:36 lubuntu kernel: [212933.327543] CPU4: Package temperature/speed normal
Mar 30 13:51:36 lubuntu kernel: [212933.327544] CPU0: Package temperature/speed normal
Mar 30 13:51:36 lubuntu kernel: [212933.327546] CPU1: Package temperature/speed normal
Mar 30 13:51:36 lubuntu kernel: [212933.327547] CPU3: Package temperature/speed normal
Mar 30 13:51:36 lubuntu kernel: [212933.327550] CPU7: Package temperature/speed normal
Mar 30 13:51:36 lubuntu kernel: [212933.327551] CPU5: Package temperature/speed normal
Mar 30 13:51:36 lubuntu kernel: [212933.327552] CPU6: Package temperature/speed normal
Mar 30 13:51:36 lubuntu kernel: [212933.327561] CPU2: Package temperature/speed normal

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ibus 1.5.5-1ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: LXDE
Date: Sun Mar 30 16:14:45 2014
InstallationDate: Installed on 2014-03-07 (22 days ago)
InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha amd64+mac (20140307)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Lars Noodén (larsnooden) wrote :
Revision history for this message
August Karlstrom (fusionfile) wrote :

For me it's even worse as the CPU usage of ibus-daemon and ibus-x11 stays at around 47% and 27% respectively after I issue a find command in Gedit. Also the mouse pointer flickers as I move it. Pressing the right mouse key (which brings up a popup menu) causes the ibus CPU usage to go back to normal.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ibus (Ubuntu):
status: New → Confirmed
Revision history for this message
steve davis (launch-faygate) wrote :

I have the same problem on Lubuntu.

When using gEdit I frequently lose the mouse pointer (when I move the mouse the pointer flickers very briefly but is mostly invisible). My cpu temp rises rapidly from <50 to >70'C and I get 100%cpu utilisation due to the two processes: ibus-daemon and ibus-x11.
Giving focus to another app reduces both %cpu & temperature (as ibus process activity subsides).

Revision history for this message
August Karlstrom (fusionfile) wrote :

@steve, if you don't need IBus, a workaround is to simply disable it by setting "Keyboard input method system" to `none' in gnome-language-selector.

Revision history for this message
steve davis (launch-faygate) wrote :

@August, sorry I only just read your IBus comment. Yes, your idea seems to work.

On Lubuntu its start menu > Preferences > Language Support > Keyboard Input Method System: none

Many thanks.

Revision history for this message
Christian González (droetker) wrote :

Setting the input method to "none" does not work here. Same 19% CPU activity of ibus-daemon, fann running high. However, task-switching to another application than gedit stops the ibus usage temporarily.

Changed in ibus (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Ben James (ben-c-james) wrote :

I can confirm the same issues on a Lenovo Yoga 2 Pro running 15.04. High load from ibus-daemon ibus-engine-simple ibus-x11 and gedit. This is _severe_ on a laptop and causes the fans to kick in. In addition to the high load (and associated temperature/fan noise), gedit actually crashes.

Setting input method to "none" also does not help.

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.