If I have my volume low because I don't want to wake anyone up, if I open banshee and start playing a song for the first time, it will increase my volume to the maximum and start playing. After I lower the volume, it will stay low, but if I close and re-open banshee it increases my volume again.
This seems to be related to the upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=686908 There is a patch in the ticket
*** Bug 901740 has been marked as a duplicate of this bug. ***
Still present in F20.
The commit "libbanshee: Only call volume set callback on Mac (bgo#686908)" was backported to 2.6 branch, but no 2.6.2 version yet. A cherry-pick maybe?
Created attachment 831068 [details] Patch Backported patch from upstream - not to get 100% volume on startup of Banshee.
Created attachment 831069 [details] Updated specfile to reflect the previous patch. Updated specfile to take into account the previously uploaded patch.
The previously uploaded files (patch and specfile) are for banshee-2.6.1-2 src rpm package. Builds and works fine for fc20 x86_64.
Description: The same here. Volume is set to maximum level.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is 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 change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
I can't verify if this is still a problem in F20 because now Banshee doesn't start at all: Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d) after class_init (Banshee:30279): GLib-GObject-WARNING **: attempting to add an interface (AtkSelection) to class (__gtksharp_74_Hyena_Data_Gui_Accessibility_ListViewAccessible+601+5b+5bBanshee_Collection_AlbumInfo+2c+20Banshee_Core+2c+20Version+3d2_6_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d) after class_init [Info 12:07:01.658] Updating web proxy from GConf [Info 12:07:01.739] All services are started 0.605315 [Warn 12:07:01.884] Forcefully breaking out of RCS loop b/c change in total_width less than 1.0 *** Error in `banshee': malloc(): memory corruption: 0x00007fe750077d90 *** *** Error in `banshee': malloc(): memory corruption: 0x00007fe750077d90 ***
(In reply to John Anderson from comment #10) > I can't verify if this is still a problem in F20 because now Banshee doesn't > start at all: Well, even with the latest updates (as of 10 minutes ago), I still have the problem in F20 i686. Cannot check on X86_64 right now (got patched version of Banshee and no time right now), but would be surprised if it behaved differently since 2013-11-28 (see posts above) - since Banshee version in Fedora didn't change much (if at all) since F18... > Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d) after class_init > > (Banshee:30279): GLib-GObject-WARNING **: attempting to add an interface > (AtkSelection) to class > (__gtksharp_74_Hyena_Data_Gui_Accessibility_ListViewAccessible+601+5b+5bBansh > ee_Collection_AlbumInfo+2c+20Banshee_Core+2c+20Version+3d2_6_0_0+2c+20Culture > +3dneutral+2c+20PublicKeyToken+3dnull+5d+5d) after class_init > [Info 12:07:01.658] Updating web proxy from GConf > [Info 12:07:01.739] All services are started 0.605315 > [Warn 12:07:01.884] Forcefully breaking out of RCS loop b/c change in > total_width less than 1.0 > *** Error in `banshee': malloc(): memory corruption: 0x00007fe750077d90 *** > *** Error in `banshee': malloc(): memory corruption: 0x00007fe750077d90 *** Yep, I see a similar output when running Banshee from terminal, but no memory corruption - and Banshee runs. Banshee has a development release (2.9), which should integrate Gtk3... I have already asked on the Banshee mailing list if they could release maintenance release in the stable 2.6 branch.
The problem remains also on the newest Fedora 20 x86_64 release version with updates till now.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Closed in upstream.