high cpu usage when typing

[Simon Steinbeiß]

Binary package hint: kile

hi, i'm using kile 2.0.81 on jaunty.
the problematic behaviour is quite simply described: the cpu usage raises up to ~90% when typing fast and continuosly in kile. what kind of file that is (big, small, latex, bibtex) doesn't make a difference.

this could be related to Bug #361843, but on the other hand: i tried the workaround suggested there (using --graphicssystem raster as a startup option) but that didn't make any difference. also i have to say that otherwise kile is behaving like it should, it's only the typing that makes my laptop glow beneath my hands.

i just wanted to finally note that this bug has already been reported by bjarnheidur, but not as part of Bug #368092, which i for one think is not really related.

[Bjarnheidur Kristinsdottir (bjarnheidur)]

It was pointed out to me that the reason might be kile 2.1 being unstable beta version and made for kde4 and not for gnome.

A possible solution therefore could be to set up the stable version kile 2.0.3.

Surprisingly, the synaptic package manager in Ubuntu 9.04 doesn't offer any other version of kile than 2.1 (!)

I thus tried to set up kile 2.0.3. using the directions given, but I haven't managed to do that yet, since I'm getting repeated errors when running ./configure and always when I seem to get around an error, a new one appears....

[Simon Steinbeiß (ochosi)]

I know that kile 2.1 is still unstable and under heavy development, but reverting to the stable version of kile can hardly be called a "solution", to the most this would be a temporary workaround.

Anyways, if you really want to install kile stable, then maybe follow this posting: http://kubuntuforums.net/forums/index.php?topic=3103580.msg180604#msg180604
(at least with that you don't have to compile kile yourself. instead you'd have to remove the kile package first and then install the .deb package and use synaptic to lock the package version.)
Let us know whether that works for you.

[Bjarnheidur Kristinsdottir (bjarnheidur)]

That's true, it is no solution, just a workaround.

The installation went fine and I don't encounter the CPU problem with kile 2.0.3.

According to the following, there is nothing like kile for Gnome yet:
http://www.linuxquestions.org/questions/programming-9/latex-editor-for-gnome-641654/
http://mattions.wordpress.com/2008/07/30/the-constant-itchy-proper-latex-gnome-editor/
http://ubuntuforums.org/showthread.php?t=211936

But hopefully it will be made soon:
http://sourceforge.net/projects/gnome-latex/

[Bjarnheidur Kristinsdottir (bjarnheidur)]

Now I found a new workaround to get kile 2.1 to work.

System > Preferences > Appearance > Visual Effects

Choose "None".

By choosing none not only this kile bug disappeared, but also Rhythmbox started acting normally (it was disturbed by simple actions like opening a file, causing pauses in the playback).

[Simon Steinbeiß (ochosi)]

i'm not using compiz here and enabling or disabling xfce's compositing manager doesn't make a difference.

but your comment points in the direction of Bug #361843 (rendering engine).

[Andreas Wenning (andreas-wenning)]

@Simon
Does running kile with "--graphicssystem raster" have any effect?

[xena (amira-xena)]

@Andreas: I've the same problem with kile, but when I've tried running it with "--graphicssystem raster" it looked faster

[Andreas Wenning (andreas-wenning)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 361843, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.