Description of problem: when qt look to emacs with gtk-qt-engine software, emacs uses 100% of CPU time.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
4.After 2 or 3 seconds, watch emacs uses about 100% of CPU time
Assuming you want GTK apps to use the Oxygen style, try installing oxygen-gtk package then change the theme to oxygen-gtk in systemsettings, this should give you the Oxygen style for all GTK apps (most likely without the 100% CPU).
Yes, it is exactly what I did. Doing this, emacs uses 100% of CPU time.
oxygen-gtk isn't the same as gtk-qt-engine, two different things; just oxygen-gtk as a theme can be selected using the gtk-qt kcm module.
So which theme is used now?
Indeed, thansk for the explanations. So, if I use only oxygen-gtk (systemsettings > GTK styles > Use another style: oxygen-gtk), emacs works fine (without eating CPU time). However, if I choose "Use my KDE style in GTK application (in systemsettings > GTK styles), then emacs becomes mad. o guess problem comes from gtk-qt-engine.
Yes, gtk-qt-engine GTK engine itself.
So it is a Mageia problem or do we need to report upstream?
Hi, seems that is a upstream problem of gtk-qt-engine:
mh wrong link http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604939
there is a workaround in the archlinux website
When reading the description of this version of gtk-qt-engine, I see:
"This theme engine is currently experimental and considered as an ugly hack
by some people. Use at your own risk."
There doesn't seem to be a lot of activity upstream:
gtk-qt.ecs.soton.ac.uk doesn't work and activity here http://code.google.com/p/gtk-qt-engine/ is low
Anyway, the issue (when it still exists of course) should be added here:
And if the bug isn't valid anymore, please tell us :)
Since you imported this package:
there is no maintainer, upstream is dead (AFAICS)
Do we need this package?
This bug was filed against cauldron, but we do not have cauldron at the moment.
Please report whether this bug is still valid for Mageia 2.
Yes this bug is still valid. Maybe it is the good time to think about removing this package if it is not absolutely necessary.
marja has missed to exclude some categories of bugs like upstream one that we can not do nothing, so I will close this one as wontfix...