https://issues.apache.org/ooo/show_bug.cgi?id=99520
--- Comment #64 from Amenel VOGLOZIN <[email protected]> --- (In reply to Marcus from comment #62) > Thanks a lot for testing the patch. > Marcus, I have **NOT** tested the patch at hand in AOO, tested as in "imported the patch and applied it in an AOO codebase, built the whole thing and tried it". What I tested is THIS BUG in **vanilla** AOO 4.1.1, that is to say I wanted to answer the question "is bug 99520 still present in AOO 4.1.1?". The answer for me is diverse: * Dell XPS L702X laptop + Windows 8.1 + onboard keyboard: fully functional, meaning NOT PRESENT; * XPS L702X laptop + Windows 8.1 + Logitech G105 USB keyboard (this one has a 7th media key, i.e. a STOP key. Media keys are also accessible via an Fn metakey): fully functional. * Fujitsu Siemens Amilo Xi2528 + Windows Vista SP2 32-bit + onboard "LightTouch" media bar: half-functional (volume-related keys don't work, whether with A00 v4.0.1 or with 4.1.1; other keys work); * Fujitsu Siemens Amilo Xi2528 + Windows Vista SP2 32-bit + G105: half-functional. * desktop machine custom-built by myself, Win 8.1, G105: **NON**-functional. Bare system (no branded utility software à la Dell Quickset): Win 8.1 + Eclipse IDE + Steam. Conclusion: the keyboard doesn't matter but the software stack seems to matter. In my case, this issue has vanished from my main system (XPS 17 L702X) but I can't fully comprehend these results. Please, CC subscribers, check your installation to see whether your multimedia keys are still not functioning in AOO 4.1.1. -- You are receiving this mail because: You are on the CC list for the issue. You are the assignee for the issue. You are watching all issue changes.
