Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 154058 - - "Unable to locate theme engine"
Summary: - "Unable to locate theme engine"
Alias: None
Product: Fedora
Classification: Fedora
Version: rawhide
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-04-06 21:44 UTC by Michal Jaegermann
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: 1.9.89-5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-04-08 14:33:32 UTC

Attachments (Terms of Use)

Description Michal Jaegermann 2005-04-06 21:44:13 UTC
Description of problem:

Starting any of "component programs", like for example 'oowriter', from comes with the following warning:

(soffice.bin:3750): Gtk-WARNING **: Unable to locate theme engine in
module_path: "clearlooks",

'locate' shows only one "clearlooks".  Namely
from gtk2-engines package.  If that is what is serched for then 32-bit
soffice.bin cannot use 64-bit libraries but a dependency on
gtk2-engines.i386 does not seem to be present.

That warning may be not so benign as I observed right after that a progress
bar on OO splash to stop and 'oowriter' stuck and not starting.  OTOH
this does not seem to be easy to reproduce and it may be unrelated.

Version-Release number of selected component (if applicable):

How reproducible:
On every program startup.

Comment 1 Caolan McNamara 2005-04-07 12:01:34 UTC
I think adding a Requires: should do the right thing

Comment 2 Michal Jaegermann 2005-04-07 15:55:41 UTC
I do not know package relationships to that level, and what this library
really provides, but "" sounds awfully specific.  Is that really
a good idea? What if "artwork" will change for any reasons?

If "Unable to locate theme engine" is really only a warning, and there
are no good ways to avoid it, I think that I prefer a warning over a spurious

Comment 3 Caolan McNamara 2005-04-07 16:18:56 UTC
It's what the 1.1.X rpm does. From rh#153129# it seems the best way to force an
i386 dependancy on a package that is not directly linked to by the app is to
require directly a .so from that package. 1.1.X picked which
will pull in the gtk-engines from i386 so hopefully the same will work for 2.0

Comment 4 Michal Jaegermann 2005-04-08 00:26:35 UTC
Why then not simply 'Requires: gtk-engines' instead of forcing that in
a roundabout way which has a potential of failing in the future?

Comment 5 Caolan McNamara 2005-04-08 06:59:58 UTC
Because Requires: gtk-engines is useless for x86_64, it would be matched against
the 64bit gtk-engines. Which is what happened in rh#153129#

Comment 6 Caolan McNamara 2005-04-08 14:33:32 UTC
Hopefully good in 1.9.89-5

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