In previous gnome (2.26) I binded my "Help" button to open terminal. In new gnome (2.28) the button that previously was called "Help" became "0xf5", so I needed to reconfigure my bindings. May be names of other buttons also changed, one must check. Also, now buttons "raiseVolume" "lowerVolume" work only on the second time, if they are pressed after one another (i.e. if I, for instance, press raiseVolume repeatedly, and then start pressing lowerVolume, the first time the volume will actually increase, as if I pressed raiseVolume, and only on the second hit it will start actually decrease) Reproducible: Always Steps to Reproduce: 1.gnome 2.28 2.press XF86AudioRaiseVolume 3.press XF86AudioLowerVolume Actual Results: sometimes buttons do not what they supposed to
(In reply to comment #0) > In previous gnome (2.26) I binded my "Help" button to open terminal. In new > gnome (2.28) the button that previously was called "Help" became "0xf5", so I > needed to reconfigure my bindings. May be names of other buttons also changed, > one must check. > I think this was due an upstream change and we cannot handle it better downstream, you simply need to reconfigure keys when needed > Also, now buttons "raiseVolume" "lowerVolume" work only on the second time, if > they are pressed after one another (i.e. if I, for instance, press raiseVolume > repeatedly, and then start pressing lowerVolume, the first time the volume will > actually increase, as if I pressed raiseVolume, and only on the second hit it > will start actually decrease) > Yeah, thanks for pointing this, it't also valid with 2.30 Do you have pulseaudio USE flag enabled or disabled?
Created attachment 238119 [details] emerge --info No, I don't.
I just did some testing, and know what? The volume certainly DO changes in the right direction even in the first press, the meter just doesn't show it correctly (only in pop-up window, volume control manafer seems all right). I think the meter in pop up window just shows the previous level - the level that was before the pressing.
+*gnome-settings-daemon-2.30.2-r1 (13 Jul 2010) + + 13 Jul 2010; Pacho Ramos <pacho@gentoo.org> + +gnome-settings-daemon-2.30.2-r1.ebuild: + Revision bump including latest gstreamer volume control support patch by + Brian Cameron, it fixes volume update issue reported in bug #327609 by + Morse.
(In reply to comment #4) > +*gnome-settings-daemon-2.30.2-r1 (13 Jul 2010) > + > + 13 Jul 2010; Pacho Ramos <pacho@gentoo.org> > + +gnome-settings-daemon-2.30.2-r1.ebuild: > + Revision bump including latest gstreamer volume control support patch by > + Brian Cameron, it fixes volume update issue reported in bug #327609 by > + Morse. > This change actually breaks as-needed support.
(In reply to comment #5) > (In reply to comment #4) > > +*gnome-settings-daemon-2.30.2-r1 (13 Jul 2010) > > + > > + 13 Jul 2010; Pacho Ramos <pacho@gentoo.org> > > + +gnome-settings-daemon-2.30.2-r1.ebuild: > > + Revision bump including latest gstreamer volume control support patch by > > + Brian Cameron, it fixes volume update issue reported in bug #327609 by > > + Morse. > > > This change actually breaks as-needed support. > That explains why I didn't suffered any problem, can you please open a new bug report with build.log anyway (I don't use yet as-needed on any of my systems) Thanks
2.32.1 includes again old patch since newer one causes bug #339732 (that looks like a worse problem over this one). I have tried to modify "TIMEOUT" value on old patch from "4" to "2" (like new patch does) but doesn't fix this problem, then, the fix for this probably requires more modifications
+*gnome-settings-daemon-2.32.1-r1 (17 Mar 2011) + + 17 Mar 2011; Pacho Ramos <pacho@gentoo.org> + +gnome-settings-daemon-2.32.1-r1.ebuild, + +files/gnome-settings-daemon-2.32.1-libnotify-init.patch: + Fix runtime problems with libnotify-0.7 (bug #358535 by Justin Lecher and + patch by Ionut), use debian patch for restoring gst volume control as it + fixes volume popup problems (bug #327609 by Morse). +
