Results 1 to 3 of 3
I'm having some trouble getting the sound to work on Suse 10.0; the ALSA, OSS and arts sound drivers are all installed on my system, but when I enter the ...
- 12-15-2006 #1
Weird sound problem Part 2
I'm having some trouble getting the sound to work on Suse 10.0; the ALSA, OSS and arts sound drivers are all installed on my system, but when I enter the KDE control center and chose ALSA as my sound device, I get this error message when testing the sound:
Here is what I get from the backtrace (I'm not sure what to look for here):The application Soundserver (artsd) crashed and caused the signal 11 (SIGSEGV).
The dialog box that pops up suggests visiting kde.bugs.org, which I did. Though there are plenty of reports on this bug and a lot of discussion, no one has a solution. I tried downgrading my version of arts and kdelib but I still get the same error.(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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 1082323040 (LWP 9279)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#15 0x400a3ae6 in Arts::PlayObject_base::_create ()
from /opt/kde3/lib/libkmedia2_idl.so.1
#16 0x08057776 in ?? ()
#17 0xbfbd37ec in ?? ()
#18 0xbfbd37d8 in ?? ()
#19 0x080d5b6c in ?? ()
#20 0x00000001 in ?? ()
#21 0x0000006f in ?? ()
#22 0x00000000 in ?? ()
#23 0x01bd37db in ?? ()
#24 0x00000000 in ?? ()
#25 0xbfbd37db in ?? ()
#26 0x00000028 in ?? ()
#27 0x080d5b60 in ?? ()
#28 0x080d5aa8 in ?? ()
#29 0x080db638 in ?? ()
#30 0x080db7cc in ?? ()
#31 0x080cd494 in ?? ()
#32 0x080d824c in ?? ()
#33 0x080d7cbc in ?? ()
#34 0x080d5dd4 in ?? ()
#35 0x080cd494 in ?? ()
#36 0x080cd494 in ?? ()
#37 0x080d5b6c in ?? ()
#38 0x080db46c in ?? ()
#39 0x00000028 in ?? ()
#40 0x00000028 in ?? ()
#41 0x4082a8a0 in mp_ () from /lib/tls/libc.so.6
#42 0x080da0d0 in ?? ()
#43 0xbfbd3828 in ?? ()
#44 0x406d3cd0 in ?? () from /usr/lib/libstdc++.so.6
#45 0xbfbd3884 in ?? ()
#46 0x00000028 in ?? ()
#47 0xbfbd3848 in ?? ()
#48 0x4068ce77 in std::string::assign () from /usr/lib/libstdc++.so.6
#49 0x08053772 in ?? ()
#50 0xbfbd384c in ?? ()
#51 0x080a28b0 in ?? ()
#52 0xbfbd3884 in ?? ()
#53 0x403b48a9 in Arts::Buffer::readString () from /opt/kde3/lib/libmcop.so.1
#54 0x40059681 in Arts::ByteSoundReceiver::_Creator ()
from /opt/kde3/lib/libsoundserver_idl.so.1
#55 0x403cf876 in Arts::Object_skel::_dispatch ()
from /opt/kde3/lib/libmcop.so.1
#56 0x403cff0e in Arts:
ispatcher::handle () from /opt/kde3/lib/libmcop.so.1
#57 0x403d0cf9 in Arts::Connection::receive () from /opt/kde3/lib/libmcop.so.1
#58 0x403d0ecb in Arts::Connection::receive () from /opt/kde3/lib/libmcop.so.1
#59 0x403b642b in Arts::StdIOManager:
rocessOneEvent ()
from /opt/kde3/lib/libmcop.so.1
#60 0x403aeab1 in Arts::StdIOManager::run () from /opt/kde3/lib/libmcop.so.1
#61 0x403ae937 in Arts:
ispatcher::run () from /opt/kde3/lib/libmcop.so.1
#62 0x08059c94 in ?? ()
#63 0xbfbd5d28 in ?? ()
#64 0x00000005 in ?? ()
#65 0xbfbd5e3e in ?? ()
#66 0x00000000 in ?? ()
#67 0xbfbd5dac in ?? ()
#68 0x40007fd7 in _dl_lookup_symbol_x () from /lib/ld-linux.so.2
#69 0x40722ea0 in __libc_start_main () from /lib/tls/libc.so.6
#70 0x080520d1 in ?? ()
The odd thing is, when I enter the KDE control to chose my sound device, I don't select arts, I chose ALSA. Why is arts crashing when I'm not even using it? Unless arts has appropriated the system somehow and won't let any other drivers load...Thinking this, I uninstalled arts from the system completely -- the problem with doing that is I get NO choice of sound device (the drop down menu in KDE control center becomes blank).
I also can't delete my sound card in Yast --> hardware --> sound; when I try, the screen just blinks but the sound card is still there...Anyone know what the hell is going on?
- 12-15-2006 #2
Ok, one part of the problem is solved; I upgraded kdelib3-arts to the latest version and the artsd crash I mentioned above has stopped.
Now the only thing left is to get the sound working; any ideas are welcome.
- 01-13-2007 #3Just Joined!
- Join Date
- Jan 2007
- Location
- South Limburg, The Netherlands
- Posts
- 6
sound, amarok etc
My problems looks simular to your's. I also had two engines dissapeared in Amarok and have simular problems with the sound cards, My possitive thing is:
It worked fine with the same setup, but the next day it was all gone, maybe I did something stupid. Did you allready have a solution?


Reply With Quote