Apache OpenOffice (AOO) Bugzilla – Issue 99520
malfunction of multimedia keyboard
Last modified: 2017-02-24 23:09:08 UTC
I noticed (since OOo 3.0.1 in all versions) that the player/sound-buttons (inc./dec. volume, stop, play, mute) on multimedia keyboards do not function under OOo. In all other programs there is no problem (and i think in OOo 2.4 there was also no problem because i did not notice this problem ever). Also there is no problem with other multimedia buttons in OOo (e.g. mail, calculator, my computer, sleep...) only with the player/sound buttons, who do not affect what they should. I tried 2 different keyboard and also more players (mainly winamp, but laso quick time player, windows media player). Increasing and decreasing of sound and also muting the sound works for all players in all programs except OOo.
This is true for every multimedia keyboard?
I tried on 2 different (one KME, one Chicony). I do not know if for every, but i think this is a new problem, because i use OOo for more than year and hear music everytime and until 3.0.1 i did not notice this problem. The configuration of my pc has not changed.
I just installed OOO 310m11 (Built: 9399) and the problem persist. I have got an e-mail (probably a tester who don´t know how to use issue tracker) reporting he has got the same problem on his laptop after installed 3.1.0 version. It would be great if somebody could take a look at this issue, because this problem did not occur in the 3.0.1 version and for everybody who is listening music (e.g. through WinAMP) by using OOo it must be a little bit uncomfortable to switch to another application to change the volume for example.
i can confirm on Win XP using OOo 3.1.0 and a Logitech Media Keyboard (Y-SAE71: http://www.logitech.com/index.cfm/keyboards/keyboard/devices/186&cl=de,de) same has been reported for a Medion "Wireless Multimedia Keyboard", model "RKM014". seems to be a windows-only problem
I can confirm as a problem in Windows Vista, using OpenOffice 3.1.0, build 9399. Seems that OpenOffice is Hijacking all keyboard input except special keys like the windows key, but it may be a special case pass through. The Multimedia keys don't seem to be on this list.
I confirm the issue in Window XP, Ooo 3.0.1. It disables the Volume up/down buttons on my laptop. (But not the play/stop/ff buttons!) Consequently, I cannot set the Volume of music while doing OpenOffice work!
I can confirm same problem on Windows 7 RC1, OOo 3.1.0, and a Gateway M-153X laptop with a multimedia panel. Multimedia keys do not function only when OOo is the active application.
Issue Continues in Bug fix, Openoffice.org 3.1.1 (OOO310m19 build 9420) on Vista SP2. Is it possible to change the OS of this issue to be all Windows versions (and other OS if it affects) or is it only possible to put one OS in there?
also occurs for me on windows 7, logitech illuminated keyboard with generic (i.e. non setpoint) drivers. would be great to get a fix for this.
I can confirm with 3.1.1 (build 9420), Windows XP SP3 and a Microsoft Comfort Curve Keyboard 2000 (USB). The behavior is exactly as described: all extra keys work (WWW, calculator, mail...) BUT the multimedia ones (Play/Pause, Vol+, Vol-, Mute...).
I've had the same problem for a while with OOo 3.1.0, and now with 3.1.1. I am running Windows Vista SP2 on a HP DV6700 Laptop. The computer still makes the clicking sound through the speakers when I use the keys, but the player and sound buttons don't work.
I'm using MS natural keyboard 4000 v.1, with the same issue, just as described by other posters. My OS is XP. However, I don't have this problem on my wife's macbook. This is more than an annoyance for me as far as listening to music etc. I'm doing transcription, so the autotext feature in OO is a major boone. However, having to switch windows every few seconds is just too much, so I've gone back to using Word. Just to point out that this issue effects more than recreational functions. Hopefully it will be resolved soon so I can go back to using OO.
I have installed OOo-dev 3.2 m4 (Build:9450) and the issue continues. I've noticed that the play, stop, next and prev keys work with songbird but not with Windows Media Player. The volume key don't work with any one.
TM->WG: please have a look, thanks !
Same situation, different devices. OOo is 3.1.1 using XP and a logitech G15 keyboard. Volume and track controls are MIA for media player.
I am using OOO320m12 Build 9483 under Win 7 x64 with a Gear Head multi-media keyboard. OOo seems to block all media keys (Vol up/down, forward, backward, stop and, most importantly, mute!). I believe OOo is inadvertently "consuming" keyboard events it does not handle, instead of passing them on and letting the operating system distribute them.
Appears to be fixed (for me at least) in OpenOffice 3.2.0 release (320m12 build 9483)
Still not working for me in OpenOffice 3.2.0 (320m12 build 9483), just like when I commented in Sep 2009 with 3.1.1 (9420) :(
Still not working for me in OpenOffice 3.2.0 (320m12 build 9483) and Windows 7 x64. Any news about this issue? It's very uncomfortable.
I have a similar problem with my Thinkpad T61, XP SP3: Nearly all Fn-key-combinations DO work (such as sleep, num-lock, wlan-on/off, touch-pad on/off, brightness, etc.), however the volume-keys don't. The on-screen display actually comes on and displays the current volume, but pressing volume-up or volume-down has no effect. What also doesn't work if OOo is active are the Fn+arrowkeys combinations which on my laptop access the media player and tells it to play/pause(Fn+down-arrow), stop (Fn+up), or play the previous/next track (Fn+left/right). It seems to be a problem with the audiofunctions of the Fn-keys but it's a little strange because the volume keys access the windows sound whereas the Fn+arrowkey access the media player directly.
I have this problem, too. The button to open Windows Media Player works, but the seven play/volume keys do nothing. My specifics: OOo 3.2 on XP (SP3), with a Logitech Y-UV90 keyboard.
Problem is very annoying when using something like wireless presenter with Impress to change volume. I used OOo 3.0.0 for a long time now, but I switched to Windows 7. OOo 3.0.0 does not work with Windows 7, so now I can't use OOo any more. Hotkeys (Fn+Left/Right) do not work either. Please raise priority if possible.
I'm experiencing the problem on a ThinkPad W510 under Windows 7 64 bit. The volume up & down and speaker on / off buttons work fine UNLESS an OOo application is in the foreground. When an OOo app is in the foreground, the volume up & down buttons cause the volume bar to display, but the setting does not change no matter how many times you press one of the buttons. The speaker on / off button doesn't even cause the volume bar to display, which it should. Pressing the speaker on / off button normally causes the volume bar to display, and the speaker will switch to having a slash through it or to remove the slash, depending on whether you're turning the speaker on or off. Neither happens if an OOo app is in the foreground.
Quick update: In my post above, the OOo version information got lost due to the "Reset" button being right next to the "Submit" button. I first experienced the problem using OOo 3.2.0, and then upgraded to the latest (3.2.1) and still have the problem.
My player buttons (play/pause, stop, skip) work with OOo active. Only the Volume and Mute Keys don't work. Win7 64, OOo 3.2.0
My Media Keys work, only volume and mute keys don't. Win7 64, OOo 3.2.0 This bug was filed several times: Issue 99520 Issue 98795 Issue 100769 Issue 101739 Issue 103155
*** Issue 98795 has been marked as a duplicate of this issue. ***
*** Issue 100769 has been marked as a duplicate of this issue. ***
correct version (all issues report that problem was introduced in 3.0.1)
comment from issue 101739 (maybe a patch?) The keys are handled for mieda play toolbar. But this should not prevent system from handling it. salframe.cxx case WM_APPCOMMAND: if( ImplHandleAppCommand( hWnd, lParam ) ) { rDef = false; <= this should be true nRet = 1; } break;
*** Issue 101739 has been marked as a duplicate of this issue. ***
*** Issue 103155 has been marked as a duplicate of this issue. ***
*** Issue 116176 has been marked as a duplicate of this issue. ***
I should add that this problem affects the volume in general - I have a manual volume dial on my Toshiba Satellite Pro L300D and experience the same problem.
Really, really, really annoying...
My calculator\email\etc. buttons all work in OOO, but the volume up\down\mute do not unless I switch focus to another app. Holy crap is that annoying! OpenOffice.Org 3.3.0 OOO330m20 (Build:9567) Windows Vista Business,64 Bit, SP2 Microsoft Digital Media Keyboard 1.0A
This problem persist more than 2 years (since the 3.0.1 ver)! It is really so hard to fix it (we have now 3.3 ver.)? I am a little bit disappointed, have thought developers take care about user problems and this problem was pointed so many times... I really ask myself if it is not only a waste of time to report bugs if they are not solved for a such long time...
Well it's been a year and a half and... I'm on Linux now and it works fine. So no problems on OSX and Linux. Strange because developers usually give priority to Windows. It may be that a Windows upgrade changed something and OO didn't adapt to the change. Maybe try Libre Office, if there's a windows version.
(In reply to comment #38) > Well it's been a year and a half and... I'm on Linux now and it works fine. So > no problems on OSX and Linux. Strange because developers usually give priority > to Windows. It may be that a Windows upgrade changed something and OO didn't > adapt to the change. Maybe try Libre Office, if there's a windows version. I don't think it was a windows update, because it started after I upgraded Open Office. You're right that it works fine in Linux, but at work I don't have that luxury - we have windows machines. If I had more experience programming, I'd fix it myself, but I'm still a beginner.
Just tried it on Libre Office for Win. Doesn't work. That's with SP2 on under VBox though, if that matters. Works fine in MS Office though. Try filing this bug on the Libre Office website. Maybe they'll be more responsive.
(In reply to comment #40) > Try filing this bug on the Libre Office website. Maybe they'll be more responsive. It seems to be already there: https://bugs.freedesktop.org/show_bug.cgi?id=32664
Can the version of this bug be an issue, it is currently at 3.0.1, and this might lead to a skimming over this bug in favour of bugs for current version, even though this affects all versions of OpenOffice 3. Is it possible to change the version information for this bug report? Also the Windows Version if that's an issue, because it is all versions of Windows affected.
Win 7 32bit, OO 3.2 -> same problem. To developers: please, at least write down something about progress, if there's any. From this thread, OO seems like a dead project :-/
I confirm the problem. I have to make sure that OOo is not in the foreground before my multimedia keyboard shortcuts can function again. This is very irritating as a college student, because I am always listening to my music while working on homework and can't make song play/pause, skip track or control volume with my keyboard.
OpenOffice 3.4.0 B:9590 Acer laptop, Win7, Fn controlled by Dritek lmanager.exe 4.0.12.718 Fn commands using PageNav keys not functional [multimedia] Play/Pause[Home] PgUp[Stop] PgDn[Back] End[Forward] Arrow pad Fn commands functional: [Volume, Brightness] F key based Fn commands functional.
Year 2013 now. It will soon be 4 years! Version 3.4 has this annoying bug as well - neither volume control nor fn-based media keys work (other fn-based special keys work fine. Calculator opening for example) as long as any OO window has focus. Win7, 64 bit, logitech illuminated USB-keyboard with MS-Keyboard driver 6.1.7600.16385. Some feedback on that would be appreciated :\
Version 4.0 is out today and this is still not part of the batch of bugfixes. Sigh… This is actually the only gripe I have with OpenOffice.
Apache OO.o 4.0.0 and I have this issue. I cannot use my media keys on my custom (CyberPowerPC) laptop without switching focus. This is wasting my productivity, and is hardly a small bug. Why does OO.o even need the hotkeys? What can I even do with them? The only thought is macros, which generally use keyboard shortcuts and only function when in focus on the table/document. Please fix this. OO.o is the only application that I have that steals the keys like this, unless I am playing music and watching a video at the same time... which never happens on purpose.
Added my vote. I've experienced this over 6 machines and 4 OSs (all Windows). It doesn't impact me regularly (hence my waiting a few years before looking into it) but, when it does, it definitely impacts the way I use my computer.
Same issue here. Windows Server 2008 R2 (7-equivalent) and MS Sidewinder X6. Volume dial/knob not working when AOO is in foreground/activated. As soon as I activate either windows desktop, taskbar or another program it works again. It is very annoying while working or studying. The issue has been around for 4 years and is probably easy to fix. PLEASE ATTEND TO THIS ISSUE.
(In reply to axnberg from comment #50) > The issue has been around for 4 years and is probably easy to fix. If you're not a programmer, you you can't know how easy or hard it would be to fix. These kind of comments are incredibly unhelpful and frustrating to everyone subscribed, so keep that (and the fact that AOO is developed by volunteers) in mind ;-)
(In reply to fito from comment #51) > (In reply to axnberg from comment #50) > > The issue has been around for 4 years and is probably easy to fix. > > If you're not a programmer, you you can't know how easy or hard it would be > to fix. These kind of comments are incredibly unhelpful and frustrating to > everyone subscribed, so keep that (and the fact that AOO is developed by > volunteers) in mind ;-) I'm a programmer, and I think an issue with grabbing a key should not be to hard to fix. At least not to hard when comparing how irritating the issue is. Almost all people I know listen to some kind of music while they work. Also, almost all of them get interrupted now and then by someone by some question of comment. Having to switch windows to turn down (or off) the music instead of pushing one button is really annoying. And the issue has been here for 5 years. Sadly, such things are exactly why people think of OO as very user-un-friendly, and why it looks lousy when compared to MS office.
I really like Open Office as a rule, but since I added my Logitech k400r, I am really beginning to not like it. Why can't I use the page up/down buttons when in a document. When in the middle of a 40 page document it is so frustrating to have to manually move back to the top of the page and than try to remember where you were going back down manually. I have given up on trying to use any of the other features of my keyboard since they won't work. Since this has been a problem for about 4 years from reading the comments, why can't it be fixed? I am really close to not using or recommending your program any longer.
*** Issue 124646 has been marked as a duplicate of this issue. ***
*** Issue 117416 has been marked as a duplicate of this issue. ***
LibreOffice has solved this bug (https://bugs.documentfoundation.org/show_bug.cgi?id=32664#c63). The fix will be in the upcoming LibreOffice 4.4.1, which will be released in 25 days. Coincidentally, around this time the bug will become 6 years old!
(In reply to agnostos88 from comment #56) > LibreOffice has solved this bug > (https://bugs.documentfoundation.org/show_bug.cgi?id=32664#c63). The fix > will be in the upcoming LibreOffice 4.4.1, which will be released in 25 > days. Coincidentally, around this time the bug will become 6 years old! And what is the point of commenting this here? Did you try something more productive? Did you contact the author of the fix and ask him if he wants to release his patch under the ALv2 license?
(In reply to Ariel Constenla-Haile from comment #57) > (In reply to agnostos88 from comment #56) > > LibreOffice has solved this bug > > (https://bugs.documentfoundation.org/show_bug.cgi?id=32664#c63). The fix > > will be in the upcoming LibreOffice 4.4.1, which will be released in 25 > > days. Coincidentally, around this time the bug will become 6 years old! > > And what is the point of commenting this here? There are 22 users on the CC list that signed up to learn when the bug would be fixed. It may be urgent for them, and since OpenOffice has not solved it (yet) they may want to know that this functionality exists in another program. > Did you contact the author of the fix and ask him if he wants > to release his patch under the ALv2 license? I'm not affiliated with the OpenOffice project to ask this, but I commented here because maybe someone from the Apache Foundation would like to do so. Perhaps you can try yourself this productive task? P.S. An aggressive tone rarely helps an open source project. Unless of course it wasn't aggressive but defensive...
(In reply to agnostos88 from comment #58) > > And what is the point of commenting this here? > > There are 22 users on the CC list that signed up to learn when the bug would > be fixed. It may be urgent for them, and since OpenOffice has not solved it > (yet) they may want to know that this functionality exists in another > program. See Bug 105140 comment 6
OK. I will not comment about anything else related to LibreOffice.
Thank you for reporting progress on this. The farthest I went is reading the latest comments and it appears that 8 minutes went by between the moment someone decided to tackle it and the moment the patch was submitted. Seriously? Although I think the author is someone familiar with the code base, I only get the feeling that the fix can't be that complicated, all the more since IIRC, this bug is a side effect of another bugfix. Thinking about fixing this bug, I have just tested it again in AOO 4.1.1 and I can no longer reproduce the bug on a Dell XPS 17 laptop with media keys accessible on the function keys using the Fn metakey. This is the same computer on which I had the problem and for which I posted a comment here. The only differences are Windows 8.1 and AOO 4.1.1 opposed to Windows 7 SP1 and the latest AOO back then. NOT REPRODUCED in either of Writer, Calc, Impress and Draw. Cursor position: document, menu, modal windows, sidebar controls, add-on dialogs. Keys tested: * prev track * play/pause * next track * vol. down * vol. up * mute I'll test it with a Logitech gaming keyboard and report later. Can someone else retest this bug?
Thanks a lot for testing the patch. I've looked at it and see that several places are affected (5 files changed, 38 insertions, 21 deletions). Unfortunately, this is too much - more than a single line or something similar. For this kind of patches we always need the permission of the author that it is OK for her/him to commit it also via ALv2.
@ agnostos88 Much appreciated that you did post it here as well. I am using OOo and Libre office in parallel, since they seems to be drifting apart a bit, one has a bug fix the other does not. (Even so I am leaning nowadays more towards Libre Office. Still have an original Star Office installation on board :-)
(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.
(In reply to Amenel VOGLOZIN from comment #61) > Thank you for reporting progress on this. The farthest I went is reading the > latest comments and it appears that 8 minutes went by between the moment > someone decided to tackle it and the moment the patch was submitted. > Seriously? > Although I think the author is someone familiar with the code base, I only > get the feeling that the fix can't be that complicated, all the more since > IIRC, this bug is a side effect of another bugfix. > > Thinking about fixing this bug, I have just tested it again in AOO 4.1.1 and > I can no longer reproduce the bug on a Dell XPS 17 laptop with media keys > accessible on the function keys using the Fn metakey. This is the same > computer on which I had the problem and for which I posted a comment here. > The only differences are Windows 8.1 and AOO 4.1.1 opposed to Windows 7 SP1 > and the latest AOO back then. > > NOT REPRODUCED in either of Writer, Calc, Impress and Draw. Cursor position: > document, menu, modal windows, sidebar controls, add-on dialogs. Keys tested: > * prev track > * play/pause > * next track > * vol. down > * vol. up > * mute > > I'll test it with a Logitech gaming keyboard and report later. Can someone > else retest this bug? It is not uncommon for a developer to already have a "fix" in hand, then accept an issue, and just commit a patch -- thus the 8 minutes. :)
A year later and i'm having the same problem in a windows 10 environment. Sure just clicking on the start-menu then "next" works but still, annoying.
Experiencing this issue on OOo 4.1.3 and Windows 10.