[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Real player doesn't work on F9 under KDE



On Thu, 2008-06-19 at 23:57 +0100, Anne Wilson wrote:
> On Thursday 19 June 2008 21:29:41 Patrick O'Callaghan wrote:
> > I have RealPlayer-11.0.0.4028-20080225.i586 (my system is x86_64 but
> > Real only seem to have a i586 rpm available). When I run realplay from
> > the command line with an appropriate URL (e.g. a BBC video link) I get:
> >
> >         realplay.bin:31914): Gtk-WARNING **: Unable to locate theme engine
> > in module_path: "nodoka",
> >
> >         (realplay.bin:31914): Gtk-WARNING **: Unable to locate theme engine
> > in module_path: "nodoka",
> >
> >         (realplay.bin:31914): Gtk-WARNING **: Unable to locate theme engine
> > in module_path: "nodoka",
> >
> >         (realplay.bin:31914): Gtk-WARNING **: Unable to locate theme engine
> > in module_path: "nodoka", Opening ALSA PCM device default
> >         Opening ALSA PCM device default
> >         The program 'realplay.bin' received an X Window System error.
> >         	etc.
> >
> > This is under KDE and I have KDE Settings configured to use the Nodoka
> > theme for GTK apps, but even when I turn this off I get the same error,
> > except for:
> >
> >         ... Unable to locate theme engine in module_path: "qt4engine"
> >         	etc.
> >
> > Any suggestions welcome.
> >
> > poc
> 
> Bugs.kde.org :-)

Possibly. With the nodoka theme I fixed it by installing
gtk-nodoka-engine.i386, following Bassel's suggestion. However in trying
to do the same for qt (i.e. gtk-qt-engine.i386) yum pulled in an extra
42 extra packages (yes, forty-two, the Ultimate Answer to Life, The
Universe and Everything). At least it tried to, before bailing out on a
conflict with kdelibs. I'm just going to back slowly away from that ...

poc


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]