KDE-Forum.org

Quoted

Original von rshol

Running KDE 3.3 on SuSE 9.1 pro on a Dell Latitude. Sound seems to work fine, I can play mp3, wav, and ogg in JuK etc, video sound works ok (Real Player etc.) but I cant get any system sounds. Any suggestions?

try pointing it back to /opt/kde3/shared/sounds

Make your way over to the file ~/.kde/share/config/knotifyrc and make sure this is present
[code:1][StartProgress]
Arts Init=true
KNotify Init=true
Use Arts=true
[/code:1]
Set them to true if any are set to false.... You will probably need to restart kde.

I'm running KDE on a Dell Latitude, too, and I have also noticed something odd about the sound: System notifications work with the settings Amoeba has given, but I get a popup box saying
"Sound server fatal error: cpu overload, aborting" *after* the sound has finished playing...

This only happens with system notifications, mp3 or DVD playback works like a charm. I haven't seen this problem on any other machine yet. I don't know what's so peculiar about system notifications on Dell.

This is KDE 3.2.3 / arts 1.2.3 from Debian/testing


In my self-built CVS version of KDE arts crashes regularly instead of popping up the above message when a system sound is played...

Quoted

Original von Amoeba

Make your way over to the file ~/.kde/share/config/knotifyrc and make sure this is present
[code:1][StartProgress]
Arts Init=true
KNotify Init=true
Use Arts=true
[/code:1]
Set them to true if any are set to false.... You will probably need to restart kde.

Egads! Thank you! It works! I've been trying to solve this problem for some time via search-engine thrashing. Excuse me while I spout out phrases that might help others find this solution:

no system notifications not working sound works system notification startup sound problems

*polite cough* At any rate, it quite perplexed me. artsd worked fine... occasionally I would get "/dev/dsp can't be opened (Resource temporarily unavailable)" messages after clearing /tmp in an attmp to get things working, but that was a false lead. For some time, my problem was the default setting of the mixer for new accounts was zero. The root account, which was created by the installation distro (Knoppix, which I then dist-upgrade to Debian unstable) was working fine-- new accounts, created by the command line or with Kuser, weren't part of the audio group... so to make sound work completely, I did this:
* ensure all users were in the "audio" group
* inside the user's account, go into Kmix and turn up the appropriate volumes-- for me, there were two sliders that needed raising. At this point, normal audio, such as playing music, worked fine.
* then edit /home/(user)/.kde/share/config/knotifyrc as Amoeba so kindly explains.
And then system notifications work. Cute, aren't they ^..^ I hope this helps somebody.

I'm running kde-core 3.3.0.

Quoted

Original von cmbofh

I'm running KDE on a Dell Latitude, too, and I have also noticed something odd about the sound: System notifications work with the settings Amoeba has given, but I get a popup box saying
"Sound server fatal error: cpu overload, aborting" *after* the sound has finished playing...

I think the problem there is from ALSA. Try and select ALSA as the sound server from KControl > Sound and Multimedia > Sound System > Hardware Tab.

Quoted

Original von seb

I think the problem there is from ALSA. Try and select ALSA as the sound server from KControl > Sound and Multimedia > Sound System > Hardware Tab.

When I select "ALSA" instead of "detect automatically" I get:

Sound server informational message:
Error while initializing the sound driver:
device: default can't be opened for playback (No such file or directory)
The sound server will continue, using the null output device.

Is this an ALSA configuration error?

No, this is because aRts takes full control of the sound system.

Adjust the sound server to a 3 second timeout or something, then try again.

Quoted

Original von seb

No, this is because aRts takes full control of the sound system.

I think if that were the problem the error would be "device or resource busy", wouldn't it?

Quoted

Original von seb

Adjust the sound server to a 3 second timeout or something, then try again.

That didn't help. But choosing "OSS with threads" seems to work. At least I couldn't reproduce the problem in a quick test...

OK,
Same here, have done as suggested in knotify.rc, but can still only play .wav files as system sounds. As kde3.3 seems to use .ogg files now, I would like to be able to play these as well. Any more suggestions?
Also, this may be related. Mouseover playing of audio files in konqueror no longer works either, so any help here to please.