https://bugzilla.novell.com/show_bug.cgi?id=248829 thoenig@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |lenz@grimmer.com ------- Comment #3 from thoenig@novell.com 2007-02-26 07:30 MST ------- Lenz, we're aware of that issue but currently there is no solution to fix it. I have been looking into that and could only cook some dirty hack. Let's discuss here how to proceed. The hack is that I can use ibm-acpi to modify the volume (I was not able to do this using /dev/nvram). Thus, whenever we read a volume up/down event from /dev/nvram we could (a) send an the corresponding events via uinput and (b) reset the volume to the level it was before using ibm-acpi That hack is really dirty and I really do not like it much. Especially, it will break the support to control the volume without having some mixer running which does the ALSA stuff. As another approach we could tell users to disable the mappings (volume up/down event -> GNOME Mixer / KDE Mixer) GNOME and KDE. That solution would not be a hack but it probably will eliminate the OSD and requires an user action to be changes. By default we would have the behavior as it is today on FACTORY. What do you think? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.