amarok 2.2 and phonon-xine backend

Matt datahead4 at gmail.com
Wed Sep 30 19:26:33 UTC 2009


On Wed, Sep 30, 2009 at 5:37 AM, Mark Kretschmann <kretschmann at kde.org> wrote:
> On Wed, Sep 30, 2009 at 7:17 AM, Dima Panov <Fluffy at fluffy.khv.ru> wrote:
>> Amarok 2.2.0 (same here for all versions since 2.1.80)
>>
>> Compiling is fine, but when it start - got a crash
>>
>> [fluffy at Fluffy] ~> amarok --debug
>>
>> QWaitCondition::wait(): cv wait failure: Operation not permitted
>>
>> QWaitCondition::wait(): cv wait failure: Operation not permitted
>>
>> <fluffy_khv> ASSERT: "that->m_newStream" in file
>> /var/tmp/usr/ports/multimedia/phonon-xine/work/phonon-4.3.1/xine/xinethread.cpp,
>> line 79
>>
>> <unknown program name>(67925)/: Communication problem with  "amarok" , it
>> probably crashed.
>>
>> Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did
>> not receive a reply (timeout by message bus)" "
>>
>> KCrash: Application 'amarok' crashing...
>>
>> sock_file=/home/fluffy/.kde4/socket-Fluffy.Khv.RU/kdeinit4__0
>>
>> Can't get backtrace - gdb doesn't see stack data.
>
> Hi Dima,
>
> your error is very strange, and it happens in Phonon, the multimedia
> framework from KDE. I've asked our Phonon expert on IRC, this is what
> he said:
>
> "<sandsmark> the problem seems to be that mutexes don't work on his system"
>
>
> So there might be something really wrong with your system. I'm not
> very familiar with FreeBSD, so I can't really help much, sorry. Do we
> have any FreeBSD experts here?
>
As another data point indicating something happening related to
mutexes, here's the output I receive when launching Amarok with the
--debug and --nofork options:

$ amarok --debug --nofork
amarok: BEGIN: App::App()
amarok:   BEGIN: virtual int App::newInstance()
amarok:     BEGIN: static void App::handleCliArgs()
amarok:     END__: static void App::handleCliArgs() - Took 0.00032s
amarok:   END__: virtual int App::newInstance() - Took 0.00056s
amarok:   BEGIN: void App::continueInit()
amarok:     BEGIN: EngineController::EngineController()
amarok:       BEGIN: void EngineController::initializePhonon()
amarok(33713)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying
to open ksycoca from  "/var/tmp/kdecache-<username>/ksycoca4"
amarok(33713)/kdecore (KLibLoader) KPluginLoader::KPluginLoader: Could
not find plugin/library for "phononbackends/xine.desktop" library
name: "phonon_xine"
amarok(33713) Phonon::KdePlatformPlugin::createBackend: using backend:  "Xine"
Assertion 'pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE)
== 0' failed at pulsecore/mutex-posix.c:52, function pa_mutex_new().
Aborting.
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = amarok path = <unknown> pid = 33713
sock_file=/home/<username>/.kde4/socket-<hostname>/kdeinit4_localhost_10
kdeinit4: Got EXEC_NEW '/usr/local/kde4/lib/kde4/libexec/drkonqi' from wrapper.
kdeinit4: preparing to launch /usr/local/kde4/lib/kde4/libexec/drkonqi
QObject::connect: Connecting from COMPAT signal (KTabBar::moveTab(int,int))

Somewhat interestingly is that the assertion stated above is the exact
same thing that was reported at
http://miwi.bsdcrew.de/2009/07/firefox-35-in-ports/ when Firefox 3.5
was added to the FreeBSD ports tree.  If I make sure that PulseAudio
is not the preferred device for music audio output in KDE, then
launching with the --nofork option yields a fully functional Amarok
instance, but without --nofork the program crashes with the same error
that Dima posted above.

My FreeBSD version info is "8.0-RC1 FreeBSD 8.0-RC1 #0: Mon Sep 21
09:46:16 CDT 2009" and I'm running with KDE 4.3.1 ports built in a
tinderbox.

Hope this helps.  My efforts to obtain a full dump and backtrace to
help identify this problem have not yielded any success.



More information about the Amarok mailing list