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 731361 - Banshee doesn't remember volume setting
Banshee doesn't remember volume setting
Status: RESOLVED DUPLICATE of bug 686908
Product: banshee
Classification: Other
Component: User Interface
2.9.1
Other Linux
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-06-07 13:06 UTC by yefexe7584
Modified: 2014-07-22 09:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description yefexe7584 2014-06-07 13:06:36 UTC 
+++ This bug was initially created as a clone of Bug #686908 +++

Originally reported at:
  https://bugs.launchpad.net/bugs/1071277

If I set the music volume using the volume control in the top right of Banshee, then quit and restart the program, the volume is reset to 100%.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: banshee 2.6.0-1ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Thu Oct 25 12:25:15 2012
InstallationDate: Installed on 2012-04-24 (183 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
MarkForUpload: True
SourcePackage: banshee
UpgradeStatus: Upgraded to quantal on 2012-09-17 (37 days ago)




For me, Banshee always starts with a volume of 100% and bumps the system volume to 100% when audio playback begins. This is with Banshee 2.9.1 (git build) on Arch Linux 64 bit.
Comment 1 Andrés G. Aragoneses (IRC: knocte) 2014-07-22 09:58:36 UTC 
(In reply to comment #0)
> (...)
> DistroRelease: Ubuntu 12.10
> Package: banshee 2.6.0-1ubuntu2

Charles, this shows that you're using banshee 2.6.0, and the bug you're reporting was fixed after that. You should upgrade to 2.6.2 and test again (ubuntu 14.04 contains this release).

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