I confirm this bug. Really annoying.
The solution should be as close to the hardware as possible, so no aplication have ability to lock it.
For example , when I push volume up button in my laptop
- information of pressing the key is processen in very deep level, and volume changes
- no aplication, is informed about pressing any key at all.
- informing apropriate system component about volume change, needed for example to notify-osd window about volume change.
Example is very simple and maybe not very correct, but the point is:
- processing such keys in deep level of system.
This would solve bug #344978 as well, and help avoid other similar bugs .
Basicly volume control buttons should work like ( or almost like ) completely analog hardware potentiometer connected directly to laptop speakers. In such configuration there is no problems and no place for bugs any at all.
I confirm this bug. Really annoying.
The solution should be as close to the hardware as possible, so no aplication have ability to lock it.
For example , when I push volume up button in my laptop
- information of pressing the key is processen in very deep level, and volume changes
- no aplication, is informed about pressing any key at all.
- informing apropriate system component about volume change, needed for example to notify-osd window about volume change.
Example is very simple and maybe not very correct, but the point is:
- processing such keys in deep level of system.
This would solve bug #344978 as well, and help avoid other similar bugs .
Basicly volume control buttons should work like ( or almost like ) completely analog hardware potentiometer connected directly to laptop speakers. In such configuration there is no problems and no place for bugs any at all.