"Sound volume down" key launches GCalc

[Stéphane Maniaci]

For some strange reason, on my HP Probook 5310m, the "Volume down" special key (triggered with Fn) launches GCalc in Ubuntu. Please let me know which package is concerned, and what information I should provide.

[Robert Roth (evfool)]

Thank you for reporting the bug. I have tried it on a HP Probook 4710s, but the volume down shortcut with Fn is working as expected. So it's not something generally HP Probook related.
About testing laptop keys you can find some info here: https://wiki.ubuntu.com/LaptopTesting/Keycodes
I have tested the keycodes for volume up and down with the xev command, but the output for these did not differ. A method using the showkey in another TTY is also described there, that gave me the keycodes 114 and 115 for volume changes. Maybe you could test this too.

[Stéphane Maniaci (stephh)]

This is the log when running xev. I just press the Fn + Volume Down combo, then quit it.

[Stéphane Maniaci (stephh)]

And here's the output of showkey.

[Stéphane Maniaci (stephh)]

Okay so I've been doing a few experiments with the System → Preferences → Keyboard shortcut menu.

* Launch a calculator : XF86Calculator
* Raise down volumne : XF86AudioLowerVolume

Now if I remove the calculator shortcut, it's not launched anymore when I press Fn + Volume down, but volume is still lowered (which means that XF86AudioLowerVolume is emitted). But if I change the "Lower volume" shortcut and press my volume down combo again, it's set to XF86Calculator. My guess would be that my Fn + Volume down combo triggers both Calculator and AudioLowerVolume signals, in that order.

[Leo Arias (elopio)]

Hotkey handling, such as volume and suspend keys, involves multiple packages. Please take a look at [1], follow the Step-by-step Troubleshooting and comment back here your findings.

Please also add the files mentioned in "Useful Information to Collect in Reports" as separate attachments.

[1] https://wiki.ubuntu.com/Hotkeys/Troubleshooting

[Leo Arias (elopio)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Leo Arias (elopio)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!