Description of problem: There are no sounds for xfce events, though both options are activated in xfce4-settings-manager. Version-Release number of selected component (if applicable): - How reproducible: yes Steps to Reproduce: 1. login to xfce 2. enable event sounds in xfconf 3. click around Actual results: none Expected results: sounds Additional info:
From upstream bug https://bugzilla.xfce.org/show_bug.cgi?id=4367 Stephan Arts editbugs 2008-10-19 06:26:38 CEST (In reply to comment #24) > Thanks for adding a support for this. > > Anyways there is a problem how to play logout sound on logout/restart ? Yes, for that to work, xfce4-session needs support for libcanberra... Since we are at a feature-freeze for 4.6, that won't be added now. I am closing this bug since the related XSETTINGS have been added now. You need to submit separate bugreports for libcanberra support in xfce4-session and xfwm4 (targeted at 4.8)
I know this worked in the past... Do you have libcanberra and sound-theme-freedesktop (or some sound theme) installed?
$ rpm -q libcanberra libcanberra-gtk2 libcanberra-gtk3 sound-theme-freedesktop libcanberra-0.30-4.fc20.x86_64 libcanberra-gtk2-0.30-4.fc20.x86_64 libcanberra-gtk3-0.30-4.fc20.x86_64 sound-theme-freedesktop-0.8-3.fc20.noarch Maybe this is related to pulseaudio or a muted special sound channel? Just guessing...
So, some more info: xfconf-query -c xsettings -p /Net/SoundThemeName env | grep GTK_MODULES ls /usr/share/sounds/$(xfconf-query -c xsettings -p /Net/SoundThemeName)/stereo which canberra-gtk-play You may need to set SoundThemeName to 'freedesktop' and export GTK_MODULES=canberra-gtk-module:canberra-gtk-module
(In reply to Kevin Fenzi from comment #4) > xfconf-query -c xsettings -p /Net/SoundThemeName default > env | grep GTK_MODULES <nothing> > ls /usr/share/sounds/default/stereo <not found> # find /usr/share/sounds/* -name stereo /usr/share/sounds/freedesktop/stereo > which canberra-gtk-play /usr/bin/canberra-gtk-play > You may need to set SoundThemeName to 'freedesktop' and export > GTK_MODULES=canberra-gtk-module:canberra-gtk-module Where should I put the export statement? Is this still a bug?
No success so far, no sounds ... > xfconf-query -c xsettings -p /Net/SoundThemeName freedesktop > env | grep GTK_MODULES GTK_MODULES=canberra-gtk-module:canberra-gtk-module > ls /usr/share/sounds/$(xfconf-query -c xsettings -p /Net/SoundThemeName)/stereo alarm-clock-elapsed.oga dialog-warning.oga audio-channel-front-center.oga message-new-instant.oga audio-channel-front-left.oga message.oga audio-channel-front-right.oga network-connectivity-established.oga audio-channel-rear-center.oga network-connectivity-lost.oga audio-channel-rear-left.oga phone-incoming-call.oga audio-channel-rear-right.oga phone-outgoing-busy.oga audio-channel-side-left.oga phone-outgoing-calling.oga audio-channel-side-right.oga power-plug.oga audio-test-signal.oga power-unplug.oga audio-volume-change.oga screen-capture.oga bell.oga service-login.oga camera-shutter.oga service-logout.oga complete.oga suspend-error.oga device-added.oga trash-empty.oga device-removed.oga window-attention.oga dialog-error.oga window-question.oga dialog-information.oga > which canberra-gtk-play /usr/bin/canberra-gtk-play
Could it be an issue with PulseAudio? I found something that Pulse can't write to sockets in some circumstances according to missing access rights or the like?
It seems unlikely, but you could try removing alsa-plugins-pulseaudio and relogin and see?
(In reply to Kevin Fenzi from comment #8) > It seems unlikely, but you could try removing > > alsa-plugins-pulseaudio > > and relogin and see? I don't understand what's going on here… https://bugzilla.redhat.com/show_bug.cgi?id=1104951
I have removed all the pulseaudio crap. But ALSA doesn't detect the internal sound card, alsamixer does only see SPDIF HDMI that I don't use.
Thats odd, as pulse uses alsa... so if alsa doesn't see the card, I wouldn't expect it to work under pulseaudio either. ;(
Well, PulseAudio sees the card and there's generally sound available (e.g. Clase-Mail, Firefox, etc.). But Alsa only doesn't detect the internal chip, only HDMI SPDIF is offered. But that's a general issue and has nothing to do with canberra support in Xfce.
Setting to rawhide to prevent upcoming EOL warnings.
Maybe that user can reproduce and knows the solution and it's a duplication: https://bugzilla.redhat.com/show_bug.cgi?id=1067899
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
I'll try to reproduce when Xfce 4.12 has officially arrived in Fedora.
Ping. Should we close here with WONTFIX? Possible duplication in bug #1067899 is EOL'ed since over four years.
So, I have not had any time to try and duplicate what you are seeing or get it working... and not sure when i will. Perhaps nonamedotc could look? or you could post to the fedora xfce list and ask for others to test there and see if they all also can't get it working?
yeah, I can take a look. @raphael, do you have sound working at all?
I've got this working with the Fedora 34 Xfce spin, more or less. Main problem: Those few sound events which are supported by Xfce and/or libcanberra have no corresponding files in pre-installed package sound-theme-freedesktop. Package yaru-sound-theme contains at least dialog-question.oga, and external sources like ubuntu-sounds provide a few more sound files which will indeed be used. Chances are good that sound events work if command "canberra-gtk-play -i dialog-question" produces a sound and "export GTK_MODULES=canberra-gtk-module" is specified e.g. in ~/.profile. However even with proper sound files installed the user experience is rather disappointing. For example, leafpad triggers dialog-question when you try to close it with unsaved text, but Xfce standard editor mousepad does not.