On Sunday 26 October 2008 10:01:38 am Sune Vuorela wrote: > On Friday 24 October 2008 16:01:47 Felix Homann wrote: > > Hi, > > > > thank you Sune for your reply. I'm very sorry I didn't answer > > earlier. > > > > I've tried again building the musicplayer example from the Qt4 > > examples. It builds but it doesn't work. I'm getting error messages > > of this kind: > > > > Phonon::createPath: Cannot connect Phonon::MediaObject(no > > objectName) to Phonon::AudioOutput(no objectName). > > WARNING: bool Phonon::FactoryPrivate::createBackend() phonon > > backend plugin could not be loaded > > > > Unfortunately, the example isn't build in qt4-demos either. > > > > What's wrong? > > which phonon backends do you have installed ? > > /Sune
About the phonon backend error, see the discussion here: http://bugs.archlinux.org/task/11070 Sune, I don't know if you'd consider this a problem with the Qt or phonon packages, but it seems that by default Qt applications look for the phonon plugins under /usr/lib/qt4/plugins/. However, Debian installs them under /usr/lib/kde4/plugins/. startkde takes care of that by setting the QT_PLUGIN_PATH environment var. Something in there also causes ~/.config/Trolltech.conf to update the "4.4\libraryPath" entry. Unfortunately, there's two problems with this: 1. If a person hasn't run a KDE4 session at least once, Qt doesn't know where to find phonon's plugins. 2. For some reason the "4.4\libraryPath" entry is getting flooded with repetitions. A new pair appears each time a KDE4 session starts. John Stamp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]