Bug 1872 - emacs uses 100% of CPU time when gtk-qt-engine is installed
Summary: emacs uses 100% of CPU time when gtk-qt-engine is installed
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: D Morgan
QA Contact:
Whiteboard: Errata
Depends on:
Reported: 2011-06-20 17:58 CEST by Olivier Delaune
Modified: 2012-05-27 01:48 CEST (History)
2 users (show)

See Also:
Source RPM: gtk-qt-engine-1.1-5.r5.3.mga1
Status comment:


Description Olivier Delaune 2011-06-20 17:58:50 CEST
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):

How reproducible:

Steps to Reproduce:
1.urpmi emacs
2.urpmi gtk-qt-engine
3.type emacs
4.After 2 or 3 seconds, watch emacs uses about 100% of CPU time
Comment 1 Ahmad Samir 2011-06-20 21:47:23 CEST
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).
Comment 2 Olivier Delaune 2011-06-20 22:21:53 CEST
Yes, it is exactly what I did. Doing this, emacs uses 100% of CPU time.
Comment 3 Ahmad Samir 2011-06-20 22:43:09 CEST
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?
Comment 4 Olivier Delaune 2011-06-20 23:47:16 CEST
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.
Comment 5 Ahmad Samir 2011-06-21 14:32:48 CEST
Yes, gtk-qt-engine GTK engine itself.
Comment 6 Olivier Delaune 2011-09-04 15:40:05 CEST
So it is a Mageia problem or do we need to report upstream?
Comment 7 Manuel Hiebel 2011-09-06 01:04:53 CEST
Hi, seems that is a upstream problem of gtk-qt-engine:
Comment 8 Manuel Hiebel 2011-09-06 01:10:36 CEST
mh wrong link http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604939
there is a workaround in the archlinux website

Keywords: (none) => UPSTREAM

Comment 9 Marja Van Waes 2011-11-24 11:42:09 CET
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 :)

CC: (none) => marja11
Source RPM: gtk-qt-engine => gtk-qt-engine-1.1-5.r5.3.mga1

Comment 10 Marja Van Waes 2012-01-20 14:00:55 CET
@ John

Since you imported this package:

there is no maintainer, upstream is dead (AFAICS)

Do we need this package?

CC: (none) => balcaen.john

Manuel Hiebel 2012-01-31 13:03:15 CET

Keywords: (none) => NO_PATCH
Whiteboard: (none) => Errata

Remco Rijnders 2012-03-01 13:11:10 CET

Assignee: bugsquad => dmorganec

Comment 11 Marja Van Waes 2012-05-26 13:05:23 CEST

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.

Thanks :)


Keywords: (none) => NEEDINFO

Comment 12 Olivier Delaune 2012-05-27 00:56:34 CEST
Yes this bug is still valid. Maybe it is the good time to think about removing this package if it is not absolutely necessary.
Comment 13 Manuel Hiebel 2012-05-27 01:48:39 CEST
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...

Keywords: NEEDINFO => (none)
Resolution: (none) => WONTFIX

Note You need to log in before you can comment on or make changes to this bug.