After cat'ing something with a lot of escape sequences in Konsole (producing an endless stream of beeps), arTs popped up a messaging saying it had to go away because of "cpu overload" and promptly threw signal 11. May or may not be a bug, because it was getting saturated with beeps, but I don't know if this is the desired effect.
sounds like an upstream problem
aRts conflicts with several sound drivers (arts devs will tell you the drivers are badly written). One bad driver is the kernel i810 audio driver. Also, other bugs in arts itself sometimes seem to result in such a crash. Try searching on bugs.kde.org, and in the kdemultimedia list archive at lists.kde.org, for "arts cpu overload aborting" and you'll find lots of bugs etc. I can't help you really :-/ because this is a whole class of problems and you should report it to the kde[multimedia] developers directly, they'd know best. A google on it would probably come up with answers, too. Good luck in your search. Tell me (here) if there's any way I can help you, in which case you should tell me your sound card and driver, too. (And I suggest you use ALSA and not the kernel oss, it doesn't seem to have these problems. It fixed them with my i81x audio.)
Right, it's not a big deal; I just felt like reporting it somewhere because otherwise I'd forget. This has only happened once, so it's not really a problem, so I don't really need help with it. ;- ) I am using the emu10k1 driver included with the kernel (yes, I know, but I was having ALSA troubles a while back) with a SoundBlaster PCI512, for reference.
OK, then I'll close this. If problems resurface, try alsa drivers, then try searching kde bugs/archives/web about it.
This just started happening to me -- more or less repeatably -- on my P3 i8x0 system. I *think* it started when I emerged the latest alsa-driver, media-sound/alsa-driver-1.0.9_rc2. I'm running a fairly recent kernel, 2.6.11-gentoo-r4, and KDE is kde-base/kde-3.4.0. I'm rebuilding the kernel to 2.6.11-gentoo-r5, and if it's still there, I think I'll back alsa-driver down to 1.0.8 and see if it goes away.
*** Bug 88496 has been marked as a duplicate of this bug. ***
