Index » PageStream Support » Linux » Unable to locate theme engine in module_path:
Sign in to add a comment. Pages: 1
2007-09-15 17:31:23 CT #1
David Herman
From: United States
Registered: 2006-02-14
Posts: 94

Pagestream has stopped reacting to my gtk/gnome theme settings.
This has worked in the past, but now I get the errors:
=========================================
(PageStream5:2174Cool: Gnome-WARNING **: invalid gnome config
path '=/section/key'

(PageStream5:2174Cool: GLib-GObject-WARNING **: gsignal.c:1019: unable
to lookup signal "show" of unloaded type `GtkMessageDialog'

(PageStream5:2174Cool: GLib-GObject-CRITICAL **:
g_signal_add_emission_hook: assertion `signal_id > 0' failed


(PageStream5:2174Cool: Gtk-WARNING **: Unable to locate theme engine
in module_path: "clearlooks",
==========================================

when i run pagestream from a terminal

My system, opensuse10.2-64bit smp, I use kde as my desktop but have
a full gnome 2.18... install as well

Pagestream seems to work fine but the tool icons look like something
from gnome1 or motif, blech ;-P

Any Idea what is meant by "module path" and how to tell pagestream
where to look?

Thanks
--
dh


[Non-text portions of this message have been removed]


2007-09-16 03:01:21 CT #2
Tim Doty
From: United States
Registered: 2006-02-06
Posts: 2939

On Saturday 15 September 2007, David Herman wrote:
> Pagestream has stopped reacting to my gtk/gnome theme settings.
> This has worked in the past, but now I get the errors:
> =========================================
> (PageStream5:2174Cool: Gnome-WARNING **: invalid gnome config
> path '=/section/key'
>
> (PageStream5:2174Cool: GLib-GObject-WARNING **: gsignal.c:1019: unable
> to lookup signal "show" of unloaded type `GtkMessageDialog'
>
> (PageStream5:2174Cool: GLib-GObject-CRITICAL **:
> g_signal_add_emission_hook: assertion `signal_id > 0' failed
>
>
> (PageStream5:2174Cool: Gtk-WARNING **: Unable to locate theme engine
> in module_path: "clearlooks",
> ==========================================
>
> when i run pagestream from a terminal
>
> My system, opensuse10.2-64bit smp, I use kde as my desktop but have
> a full gnome 2.18... install as well
>
> Pagestream seems to work fine but the tool icons look like something
> from gnome1 or motif, blech ;-P
>
> Any Idea what is meant by "module path" and how to tell pagestream
> where to look?
>
> Thanks

Do you use any other 32-bit gnome/gtk applications? If so, do they use the
themes?

When did this start? I note that with your other problem you mention
downgrading from v2.18 to v2.16 for some gnome libraries -- mayber there's a
version mismatch going on?

Tim Doty

2007-09-16 10:28:39 CT #3
David Herman
From: United States
Registered: 2006-02-14
Posts: 94

On Sunday 16 September 2007, Tim Doty wrote:
> On Saturday 15 September 2007, David Herman wrote:
> > Pagestream has stopped reacting to my gtk/gnome theme settings.
> > This has worked in the past, but now I get the errors:
> > =========================================
> > (PageStream5:2174Cool: Gnome-WARNING **: invalid gnome config
> > path '=/section/key'
> >
> > (PageStream5:2174Cool: GLib-GObject-WARNING **: gsignal.c:1019:
> > unable to lookup signal "show" of unloaded type
> > `GtkMessageDialog'
> >
> > (PageStream5:2174Cool: GLib-GObject-CRITICAL **:
> > g_signal_add_emission_hook: assertion `signal_id > 0' failed
> >
> >
> > (PageStream5:2174Cool: Gtk-WARNING **: Unable to locate theme
> > engine in module_path: "clearlooks",
> > ==========================================
> >
> > when i run pagestream from a terminal
> >
> > My system, opensuse10.2-64bit smp, I use kde as my desktop but
> > have a full gnome 2.18... install as well
> >
> > Pagestream seems to work fine but the tool icons look like
> > something from gnome1 or motif, blech ;-P
> >
> > Any Idea what is meant by "module path" and how to tell
> > pagestream where to look?
> >
> > Thanks
>
> Do you use any other 32-bit gnome/gtk applications? If so, do
> they use the themes?
>
> When did this start? I note that with your other problem you
> mention downgrading from v2.18 to v2.16 for some gnome libraries
> -- mayber there's a version mismatch going on?

I suspect that you may be right.
My own theory is that suse changed the default directory locations
as part of the upgrade to gnome 2.18

After I did the full gnome upgrade (to 2.1Cool I was not able to get
pagestream to run so I did not notice the unappealing gui until I
downgraded the vfs packages (in order to get vmware's file selector
working again). Other packages that I suspect may be involved are
Orbit and Pango but I'm not sure yet.

I had noticed a change in vmware's appearance (after doing the full
upgrade) as well but it wasn't as distracting to me so I let it go.

Also firefox (and pagestream) popped up requesters notifying me that
my gconf preferences had not been loaded or saved properly.
Firefox continued to give me a similar message even after the vfs
downgrade but it mysteriously changed to gecko from gconf.

Details of the current message:
"Failed to launch configuration server: Failed to execute child
process "/opt/gnome/lib/GConf/2/gconfd-2" (No such file or
directory)"

I suspect that openSuse may be moving their gnome installation
to /usr/lib as I found gconf-2 at /usr/lib/GConf/2/gconfd-2.

By linking this to /opt/gnome/lib/GConf/2/gconfd-2 (I think) I was
able to get rid of this requester but nothing changes with vmware
or pagestreams gui's

I am most curious about the
"Unable to locate theme engine in module_path:"
warning when pagestream is run from the shell. If I knew how to
change the "module path" that pagestream was looking in it seems
that it would be able to find the modules it is looking for.

I have tried linking various theme engine files and directories to
the locations I thought they might be looked for but have had no
success.

Sorry for the length of this message but hopefully the abundance of
information will be useful in solving this minor but distracting
issue.

Thanks for your help

--
dh


[Non-text portions of this message have been removed]


2007-09-16 13:03:04 CT #4
Tim Doty
From: United States
Registered: 2006-02-06
Posts: 2939

On Sunday 16 September 2007, David Herman wrote:
[snip lots of info]
> I am most curious about the
> "Unable to locate theme engine in module_path:"
> warning when pagestream is run from the shell. If I knew how to
> change the "module path" that pagestream was looking in it seems
> that it would be able to find the modules it is looking for.

I did find this for a similar problem:
>Add this line to the appropriate gtkrc:
>module_path "/opt/gnome/lib/gtk-2.0/2.2.0/engines"
src:http://marc.info/?l=gtk&m=108284558122624&w=2

given that I would recommend checking gtkrc for a module_path definition.

Tim Doty

2007-09-17 10:34:07 CT #5
David Herman
From: United States
Registered: 2006-02-14
Posts: 94

On Sunday 16 September 2007, Tim Doty wrote:
> On Sunday 16 September 2007, David Herman wrote:
> [snip lots of info]

>
> I did find this for a similar problem:
> >Add this line to the appropriate gtkrc:
> >module_path "/opt/gnome/lib/gtk-2.0/2.2.0/engines"
>
> src:http://marc.info/?l=gtk&m=108284558122624&w=2
>
>
given that I would recommend checking gtkrc for a module_path
> definition.

Thanks for your help Tim. I looked at the site you linked to and did
some gtkrc research. Unfortunately none of it gave me the result I
was looking for.

It occurred to me that I hadn't tried pagestream as a different user
since I got it working again (vfs issue) so I went to my daughters
login and tried it.

Apparently the issue I am seeing is with my user settings
(somewhere), things work as they should in her login.

Thanks again for your help.

--
dh


[Non-text portions of this message have been removed]


2007-09-17 11:33:02 CT #6
David Herman
From: United States
Registered: 2006-02-14
Posts: 94

On Monday 17 September 2007, David Herman wrote:
> On Sunday 16 September 2007, Tim Doty wrote:
> > On Sunday 16 September 2007, David Herman wrote:
> > [snip lots of info]
> >
> > I did find this for a similar problem:
> > >Add this line to the appropriate gtkrc:
> > >module_path "/opt/gnome/lib/gtk-2.0/2.2.0/engines"
> >
> > src:http://marc.info/?l=gtk&m=108284558122624&w=2
>
>
> > given that I would recommend checking gtkrc for a module_path
> > definition.

I still don't know where "module_path" is being set but I found the
source of my problem.

It seems that suse has 2 (actually 3 but lets not get into that)
ways of setting the way gtk apps appear on the kde desktop.

One is with the kcm_gtk module, another is the gtk-qt-engine. Either
one of these will show up in the kde preferences panel (but only
one can be installed at a time).

Apparently Pagestream, vmware and vlc do not use the settings of the
gtk-qt-engine but work fine with the kcm_gtk module.

I can now have a beautiful gui for my gtk apps again.

Thanks for all the help
--
dh


[Non-text portions of this message have been removed]


Sign in to add a comment. Pages: 1
Index » PageStream Support » Linux » Unable to locate theme engine in module_path:

This topic is closed due to inactivity.