[kde-linux] artsd chrashing

[Jan Simonson]

Hello,

On my fc4, i386 kde 3.4.3 system compiled from source I have a problem 
with artsd. Sound is working and I can use xmms with alsa output to 
play mp3. Realplayer sound also works ok.

However, when trying to start artsd from control center I get the 
crash handler with:
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208383824 (LWP 3150)]
[KCrash handler]
#3  0x007c7e3b in __gnu_cxx::__pool<true>::_M_reclaim_block ()
   from /usr/lib/libstdc++.so.6
#4  0x0805e7ae in 
Arts::SimpleSoundServer_impl::SimpleSoundServer_impl$base ()
#5  0x0805757c in Arts::SoundServer_impl::SoundServer_impl$base ()
#6  0x08056012 in Arts::SoundServerV2_impl::SoundServerV2_impl ()
#7  0x08059f57 in SoundServerV2_impl_Factory::createInstance ()
#8  0x00e7322b in Arts::ObjectManager::create ()
   from /opt/kde/lib/libmcop.so.1
#9  0x0013b7da in Arts::SoundServerV2_base::_create ()
   from /opt/kde/lib/libsoundserver_idl.so.1
#10 0x001404bd in Arts::SoundServerV2::_Creator ()
   from /opt/kde/lib/libsoundserver_idl.so.1
#11 0x00e7058a in Arts::ObjectManager::addGlobalReference ()
   from /opt/kde/lib/libmcop.so.1
#12 0x08062249 in publishReferences ()
#13 0x08064658 in main ()

And when trying the command line I get:
[jan at oden ~]$ artsd
unix_connect: can't connect to server 
(unix:/tmp/mcop-jan/oden_simonson_se-0db8-436f5590)
Segmenteringsfel
[jan at oden ~]$

but the file created in /tmp/mcop-jan is named 
oden_simonson_se-0e68-436f5971, that is: not the same number. It's 
like this (not the same number) every time I try to start artsd. Is 
this significant?

I have tried to search both in google and bugs but to no avail. I 
upgraded gstreamer as mentioned in: 
http://www.linuxquestions.org/questions/showthread.php?postid=1663036
but that didn't help either.

I also tried with 3.5B2 using a separate test-user but the result is 
the same. This problem started when upgrading from 3.4.1.

Any ideas?

Jan
-- 
Jan Simonson