Hi Sebastien. Thank you for looking into this.
I already wrote down my version of Ubuntu and the gnome-settings-daemon
package. What other version numbers do you need? I can confirm that this
bug still exists on an up-to-date system as of today.
I suggest that the volume change events are not cached/enqueued like
they seem to be at the moment. This causes the annoying side-effect
mentioned in my original post ("This causes the volume to rise/fall more
than you wanted (because you first stopped holding down the key when the
OSD showed the volume you wanted - yet several events have been enqueued
in the meantime)").
I'm not entirely sure how the events are cached/enqueued at the moment
(again, seems to depend on the keyboard used?), but while the system is
working on displaying the volume graph on screen, additional events
triggered by the held down key should be discarded. By doing this, the
actual system volume and the OSD will be "synced" as the user would
expect them to.
This might be related to the fact that the OSD uses about 50% CPU (of an
AMD Sempron Mobile 3100+) to draw the volume OSD while holding down a
volume key. I guess that is another bug to report though?
I hope that is what you wanted to know. If not, let me know :).
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete => New
--
Holding down volume hotkeys causes CPU lag and enqueued volume events
https://bugs.launchpad.net/bugs/216788
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
