After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 591283 - totem reduces system volume at start and end of playback
totem reduces system volume at start and end of playback
Status: RESOLVED DUPLICATE of bug 590884
Product: totem
Classification: Core
Component: general
2.27.x
Other All
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-08-10 03:00 UTC by rockorequin
Modified: 2009-09-04 10:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description rockorequin 2009-08-10 03:00:18 UTC
Please describe the problem:
totem reduces system volume at start and end of playback, sometimes to zero. If you click on the master volume icon, it restores system volume.

Steps to reproduce:
1. Run alsamixer and set the volume.
2. From nautilus, open an audio or video file so that totem starts playing it and observe that the master volume (and sometimes PCM) is reduced. It also behaves this way if you drag and drop a file into totem.
3. Scroll playback to near the end of the file, and when it stops playing, observer that the master volume (and sometimes PCM) is reduced.
4. Click on the totem volume icon and observe that the master volume in alsamixer is restored.

Actual results:
As noted above

Expected results:
totem shouldn't adjust the system volume unless I tell it to.

Does this happen every time?
Yes, although the volume is sometimes reduced to zero and sometimes to some value above zero.

Other information:
This is in Ubuntu 9.10 with:

* totem 2.27.2-0ubuntu2
* pulseaudio 1:0.9.16~test4-0ubuntu4
* kernel 2.6.31-5-generic
Comment 1 Bastien Nocera 2009-09-04 10:58:01 UTC
Totem doesn't change the system volume, PulseAudio does through the flat-volumes feature.

*** This bug has been marked as a duplicate of bug 590884 ***