Amarok 2 Beta

[Peter Zhou]

I am not a Gentoo user, but afaik, the generator doesn't generate qt
bindings correctly in your case.
I wonder if someone has the same experience?


On Mon, Aug 25, 2008 at 1:19 AM, Christoph Spielmann <spielc at gmail.com> wrote:
> Hi everybody!
>
> As a long time user of Amarok i've been watching the development
> progress of Amarok 2 with alot of interest. As the (first?) beta was
> released last week i decided to give it a go this weekend. I was
> positively surprised by the current state of the program. Almost
> everything worked out of the box without the necessity of interference
> from my side. For example last.fm-submission of my tracks worked as soon
> as i entered correct username and password), scanning of my music
> collection was quite fast and as far as i could see all my music files
> are there... Only thing i couldn't get to work was QtScript (neither the
> console nor the test script worked). When i start e.g. the
> Script-console i get this:
>
> amarok: BEGIN: bool ScriptManager::slotRunScript(QString, bool)
> amarok: BEGIN: void ScriptManager::startScriptEngine(QString)
> amarok: BEGIN:
> ScriptableServiceScript::ScriptableServiceScript(QScriptEngine*)
> amarok: END__:
> ScriptableServiceScript::ScriptableServiceScript(QScriptEngine*)
> - Took 3.8e-05s
> Object::connect: No such signal
> Playlist::Model::activeRowExplicitlyChanged(int,
> int)
> amarok: END__: void ScriptManager::startScriptEngine(QString) - Took
> 0.00039s
> amarok: BEGIN: void AmarokScript::ScriptImporter::loadQtBinding(const
> QString&)
> amarok:      importing qt bindings  "qt.core"
> amarok: END__: void AmarokScript::ScriptImporter::loadQtBinding(const
> QString&)
> - Took 0.031s
> amarok:   [ScriptManager] [ERROR!] Script Error: "18:52:36 Error: Unable
> to impo
> rt qt.core: no such extension on Line: -1"
> amarok: BEGIN: void ScriptManager::slotStopScript(QString)
> amarok: BEGIN: void ScriptManager::scriptFinished(QString)
> amarok: BEGIN: virtual ScriptableServiceScript::~ScriptableServiceScript()
> amarok: END__: virtual
> ScriptableServiceScript::~ScriptableServiceScript() - Too
> k 1.6e-05s
> amarok: END__: void ScriptManager::scriptFinished(QString) - Took 0.00023s
> amarok: END__: void ScriptManager::slotStopScript(QString) - Took 0.00028s
>
> amarok seems to be linked to the correct version of libQtScript:
>
> ldd /usr/kde/4.1/bin/amarok | grep Qt
>        libQtCore.so.4 => /usr/lib64/qt4/libQtCore.so.4 (0x00007f881c00b000)
>        libQtNetwork.so.4 => /usr/lib64/qt4/libQtNetwork.so.4
> (0x00007f881baee000)
>        libQtDBus.so.4 => /usr/lib64/qt4/libQtDBus.so.4 (0x00007f881b885000)
>        libQtXml.so.4 => /usr/lib64/qt4/libQtXml.so.4 (0x00007f881b63e000)
>        libQtScript.so.4 => /usr/lib64/qt4/libQtScript.so.4
> (0x00007f8817f3c000)
>        libQtWebKit.so.4 => /usr/lib64/qt4/libQtWebKit.so.4
> (0x00007f8815e9c000)
>        libQtOpenGL.so.4 => /usr/lib64/qt4/libQtOpenGL.so.4
> (0x00007f88132e7000)
>        libQtGui.so.4 => /usr/lib64/qt4/libQtGui.so.4 (0x00007f8812404000)
>        libQtSvg.so.4 => /usr/lib64/qt4/libQtSvg.so.4 (0x00007f88121b1000)
>        libQt3Support.so.4 => /usr/lib64/qt4/libQt3Support.so.4
> (0x00007f880e306000)
>        libQtSql.so.4 => /usr/lib/qt4/libQtSql.so.4 (0x00007f880d4c9000)
>
> equery belongs /usr/lib64/qt4/libQtScript.so.4
> [ Searching for file(s) /usr/lib64/qt4/libQtScript.so.4 in *... ]
> x11-libs/qt-script-4.4.1 (/usr/lib64/qt4/libQtScript.so.4 ->
> libQtScript.so.4.4.1)
>
> Does anybody have an idea what could be wrong here?
>
> For your information i'm using Gentoo/~amd64 here.
>
> As some things were acting up a bit, i'll post the steps i took to get a
> working version of amarok2 here:
>
> First i'm still using portage so if you are using paludis or any other
> package manager and something does not work, don't blame me. Second i
> assume that you know how to use layman. So here you go:
>
> 1. get kdesvn-portage overlay using layman.
> 2. emerge -pv amarok and add the masked packages to your
> /etc/portage/package.unmask
> 3. repeat step two till you are actually able to install amarok
> 4. emerge amarok (might take a while depending on the dependencies that
> need to be merged first)
> 5. install phonon-xine (i was NOT able to get sound working with
> phonon-gstreamer so i would suggest to use phonon-xine as this fixed
> almost all my problems concerning sound)
> 6. if sound is still not working (this means when you try to play a
> track you get the osd and the progress bar is showing activity but you
> don't hear anything) emerge kde-base/systemsettings, start it, go to
> sound setting and set everything to the correct alsa-device. Apply the
> changes and restart amarok now you should actually hear something (if
> not i don't have a clue what could be the problem because these steps
> made it possible for me to use amarok2)
>
> So to sum up: The current state of Amarok2 is that it is usable (at
> least as usable as you a beta-version of a software-product could be). I
> haven't experienced crashes, i get sound , osd is working, the playlist
> works, the collection works, plasma-applets work (as far as i tested it).
>
> Keep up the good work,
>
> Christoph
> _______________________________________________
> Amarok mailing list
> Amarok at kde.org
> https://mail.kde.org/mailman/listinfo/amarok
>



-- 
Peter