# rpm -q xfce4-notifyd xfce4-volumed claws-mail
xfce4-notifyd-0.2.2-6.fc18.x86_64
xfce4-volumed-0.1.13-4.fc18.x86_64
claws-mail-3.9.0-1.fc18.x86_64



+++ This bug was initially created as a clone of Bug #731430 +++

Description of problem:
When playing audiofiles via audacious a notification that the volume has changed pops even on every title change. This is totaly anoying

Version-Release number of selected component (if applicable):
xfce4-mixer-4.8.0-1.fc15.i686

How reproducible:
allways

Steps to Reproduce:
1. start audacious
2. activate the libnotify-aosd plugin
3. play some audio files
  
Actual results:
on every track change a volume-notification pops up

Expected results:
volume-notifications should only pop up on manual volume modifications

Additional info:

--- Additional comment from Kevin Fenzi on 2011-08-17 19:52:54 CEST ---

Odd. xfce4-mixer has no notification ability. Are you sure this is coming from xfce4-mixer? 

Perhaps it's gnome-volume-control or whatever?

--- Additional comment from Heiko Adams on 2011-08-17 20:19:50 CEST ---

I try to verfiy this behaviour with parole and no volume-notifications pop up. So it could also be that audacious is causing these pop ups.

--- Additional comment from Heiko Adams on 2011-08-17 20:58:49 CEST ---

gnome-volume-control isn't installed on my system but xfce4-volumed-0.1.12-1.fc15.i686

--- Additional comment from Kevin Fenzi on 2011-08-19 20:59:51 CEST ---

Moving over to xfce4-volumed for comment.

--- Additional comment from Christoph Wickert on 2011-08-26 11:08:47 CEST ---

There is not much we can do here. It's a combination of audacious, puseaudio and xfce4-volumed and of them behave correct - at least from there point of view.

If you look at pavucontrol you will see that audacious has no continuous stream but disappears when the track changes. Thus it is a new channel for pulseaudio and a new channel is like raising the volume form 0-x for xfce4-volumed. So if one application is to blame it is audacious - but I am not sure if it's developers will agree, so I am not sure how to move on.

--- Additional comment from Heiko Adams on 2011-08-26 11:30:21 CEST ---

Let's try and see what's their point of view :-)

--- Additional comment from Christoph Wickert on 2011-08-26 11:44:42 CEST ---

I guess they'll blame PulseAudio... are you taking care of this? Please file a bug against audacious upstream or reassign this one to the audacious component in Fedora.

To get rid of the notifications, I suggest to uninstall xfce4-volumed. Volume keys will continue to work through amixer directly.

--- Additional comment from Michael Schwendt on 2011-09-11 21:52:03 CEST ---

> 2. activate the libnotify-aosd plugin

Completely unrelated. Else, expand on how this would be relevant.


> 3. play some audio files

Missing some steps here. At least with F-15, one must first install xfce4-notifyd and xfce4-volumed, then relogin to have them both autostarted. Without xfce4-notifyd there would not be any notifications from Audacious' libnotify plugin either.


> on every track change a volume-notification pops up

Cannot reproduce.

This is with Pulse Audio and XFCE Mixer Plugin reconfigured to control "Playback: Internal Audio Analog Stereo (PulseAudio Mixer)" as the default controlled something that didn't affect the master volume.

If I change the current volume level with either Audacious or XFCE panel mixer, I do get the volume level displayed by volumed, and it vanishes automatically after several seconds.

While typing this comment, XFCE mixer stopped working. Using the mouse-wheel on it displays the right animation of the mixer icon, but without an audible effect. Trying to make it work again, audio suddently turnt silent. Audacious continues to play, but changing the volume level is not possible. 100% completely silent. I may have to log out and in again, and would still need a test-case.


> Please file a bug against audacious upstream

Appreciated, because I couldn't answer any questions they might have. It's likely they will ask whether it's reproducible with 3.0.2 (F-16) or latest git. I couldn't even answer that without a clear test-case. Does it need to be a specific volume level in Audacious? Perhaps a rounding error that triggers the notification?

--- Additional comment from Heiko Adams on 2011-09-11 22:27:28 CEST ---

You need to active the libnotify-aosd plugin otherwise you truely can't reproduce this behaviour. But at the moment I can't reproduce this problem myself. strange.

--- Additional comment from Michael Schwendt on 2011-09-11 23:55:32 CEST ---

The libnotify-aosd plugin cannot trigger any xfce4-volumed notification. It is just the "Audacious OSD" plugin modified to use libnotify instead of on-screen-display. A direct library call with some message text and no information about the volume level. libnotify itself would not "magically" decide to show an unrelated second notification based on a data poiner from a separate process (xfce4-volumed) … just in case you start thinking it could be in a bug in libnotify. ;)  It isn't.

[...]

So, since it is xfce4-volumed that notifies about volume changes, when exactly does it do that? Speaking in terms of its implementation. How does it get notified about volume changes? Does it poll a service? And how/where does it read out the current volume level it displays?

--- Additional comment from Christoph Wickert on 2012-01-10 03:49:30 CET ---

Hi Michael, I think I already answered some of your questions in my previous comment, but maybe my comments were not clear enough.(In reply to comment #10)

(In reply to comment #10)
> So, since it is xfce4-volumed that notifies about volume changes, when exactly
> does it do that?

Whenever a new track starts. The problem with audacious is that it doesn't really do continuous playback from PulseAudio's POV. Whenever the title changes, the volume of the playback stream goes to zero and then back to the original value. This change is then seen and reported by xfce4-volumed.

> Speaking in terms of its implementation. How does it get
> notified about volume changes? Does it poll a service? And how/where does it
> read out the current volume level it displays?

It uses gstreamer. It creates a GstBus and then used gst_bus_add_signal_watch. I'm pretty sure that if one wrote a test program we'd see this moment of silence in GStreamer.

--- Additional comment from Christoph Wickert on 2012-01-10 03:56:57 CET ---

I'd like to add that it's not just Audacious but other programs, too. Some players are fine, others not. So who is to blame? GStreamer? PulseAudio?

--- Additional comment from Michael Schwendt on 2012-01-10 09:37:20 CET ---

Audacious does not use GStreamer, however, so that comment only confuses the matter.

Audacious' PulseAudio plugin connects to Pulse Audio with default stream volume, at least since I fixed it to do that in 2009, and it has seen upstream maintenance since then again, too. It used to connect with a custom start volume level years ago (the original code is from the Pulse Audio author even, albeit for XMMS).

In comment 8 I wrote I cannot reproduce the problem. Latest Audacious (3.2-beta1) is in Rawhide, so if it's still reproducible for you, that would be the latest code of interest.

[...]

I don't know what to report upstream. I don't want to waste any resources there with a mysterious issue that is not specific to Audacious.

I also cannot support Pulse Audio, since I'm one of the users who need to run it with "flat-volumes = no" in /etc/pulse/daemon.conf. Activity related to that can be found in audacious-plugins %changelog before 2.4.0, and the cause is something that's known by Pulse Audio upstream. It is not specific to Audacious either.

--- Additional comment from Michael Schwendt on 2012-01-10 10:37:33 CET ---

Perhaps you also need to disable flat-volumes. Here are some of the links to the pulseaudio.org bug tracker tickets:
http://pkgs.fedoraproject.org/gitweb/?p=audacious-plugins.git;a=blob_plain;f=README

--- Additional comment from Fedora End Of Life on 2012-08-07 17:50:25 CEST ---

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from Raphael Groner on 2013-05-07 14:40:49 CEST ---

I can reproduce the doubled notification in two popups.
1) new mail message from claws-mail
2) volume level for sound

Request to reopen this bug!

--- Additional comment from Raphael Groner on 2013-05-07 14:41:29 CEST ---

(In reply to comment #16)
> I can reproduce the doubled notification in two popups.
> 1) new mail message from claws-mail
> 2) volume level for sound
> 
> Request to reopen this bug!

xfce4-notifyd-0.2.2-6.fc18.x86_64