Atom: Keyboard shortcut to Reload Window not (always) working

[idleberg]

Prerequisites

• [x] Can you reproduce the problem in safe mode?
• [x] Are you running the latest version of Atom?
• [x] Did you check the debugging guide?
• [x] Did you check the FAQs on Discuss?
• [x] Are you reporting to the correct repository?
• [x] Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.

Description

I have noticed that the keyboard-shortcut for View > Developer > Reload Window is not working across all the systems on which I'm using Atom.

Mac OS X 10.8.x - working
Mac OS X 10.11 - not working
Windows 10 - working
Fedora - working

I suspected conflicting keyboard shortcuts, but neither safe mode resolved this nor did the keybinding resolver find any conflicts. No errors in the console either.

Which keyboard layout are you using? Apple QWERTZ Keyboard (German layout)

Steps to Reproduce

1. Launch Atom
2. Press CtrlAltCmdL

Expected behavior: The Window to reload

Actual behavior: The Window did not reload

Versions

You can get this information from executing atom --version and apm --version at the command line.

atom --version
1.5.4

apm --version
apm  1.6.0
npm  2.13.3
node 0.10.40
python 2.7.10
git 2.5.4

[idleberg]

I noticed some additional details in the Key Binding Resolver.

1. When pressing the CtrlAltCmdL shortcut, it only displays CtrlAltCmd, whereas shorter versions (any combination of involved keys, e.g. CtrlAltL) and longer versions (e.g. CtrlAltShiftCmdL) are displayed correctly.
2. Other combinations that include CtrlAltCmd are also displayed correctly.
3. Different key bindings for windows:reload work fine.

This behavious remains unchanged in Atom 1.6.0 (I previously used 1.5.4)

[idleberg]

The reason was 1Password's conflicting global shortcut to lock the app.

[lock[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!