Ubuntu shortcuts not working when Chrome text fields are highlighted
Since recently, whenever a text-field (e.g. the address bar or the askubuntu search field) is highlighted inside Google Chrome, I cannot use Ubuntu shortcuts (e.g. Ctrl+W to close a window). When hitting Ctrl+W nothing happens. As soon as I press tab to leave the text-field, the shortcuts work as expected (e.g. Ctrl+W closes the window).
I have no idea why this happens. Any ideas how to debug or solve this?
I am using Ubuntu 18.04.1 LTS and Google Chrome 71.0.3578.98.
Edit: It seems that this issue is somehow connect to Keyboard Layouts. Mostly, I use the layout "English (US, intl., with dead Keys)". In this case, the above problem occurs and shortcuts no longer work when text fields are highlighted. When switching to "English (US)", Ctrl + w closes the window as intended, even when a text field is highlighted. (Credit to mr. Pavlikov)
shortcut-keys google-chrome chromium
asked Dec 18 at 18:01
physicsGuy
1435
add a comment |
Since recently, whenever a text-field (e.g. the address bar or the askubuntu search field) is highlighted inside Google Chrome, I cannot use Ubuntu shortcuts (e.g. Ctrl+W to close a window). When hitting Ctrl+W nothing happens. As soon as I press tab to leave the text-field, the shortcuts work as expected (e.g. Ctrl+W closes the window).
I have no idea why this happens. Any ideas how to debug or solve this?
I am using Ubuntu 18.04.1 LTS and Google Chrome 71.0.3578.98.
Edit: It seems that this issue is somehow connect to Keyboard Layouts. Mostly, I use the layout "English (US, intl., with dead Keys)". In this case, the above problem occurs and shortcuts no longer work when text fields are highlighted. When switching to "English (US)", Ctrl + w closes the window as intended, even when a text field is highlighted. (Credit to mr. Pavlikov)
shortcut-keys google-chrome chromium
asked Dec 18 at 18:01
physicsGuy
1435
1
I am seeing the same. Also on Chromium. NOT on Firefox or other applications. Also maybe worth noting that this is with Unity.
– nkoren
Dec 19 at 17:23
2
Also worth noting that this happens with any selected input element, and also if the URL bar is selected. Basically any time any keyboard input is expected to be received, OS shortcut key combinations are blocked.
– nkoren
Dec 20 at 12:14
Looks like a problem with ibus :/ Killing ibus-daemon works around the issue... not sure if it's a bug in ibus or in chromium.
– Léo Lam
Dec 25 at 12:48
1
I have same issue on Ubuntu 18.10 / Google Chrome Version 71.0.3578.98 (Official Build) (64-bit). It only happens when I have alternate keyboard layout (RUS in my case), and is fine with EN layout.
– mr. Pavlikov
Dec 26 at 14:30
@mr.Pavlikov I can confirm, a change of the keyboard layout removes this issue. Details: I use the layout "English (US, intl., with dead Keys)". When switching to "English (US)", Ctrl + w closes the window as intended, even when a text field is highlighted.
– physicsGuy
2 days ago
add a comment |
Since recently, whenever a text-field (e.g. the address bar or the askubuntu search field) is highlighted inside Google Chrome, I cannot use Ubuntu shortcuts (e.g. Ctrl+W to close a window). When hitting Ctrl+W nothing happens. As soon as I press tab to leave the text-field, the shortcuts work as expected (e.g. Ctrl+W closes the window).
I have no idea why this happens. Any ideas how to debug or solve this?
I am using Ubuntu 18.04.1 LTS and Google Chrome 71.0.3578.98.
Edit: It seems that this issue is somehow connect to Keyboard Layouts. Mostly, I use the layout "English (US, intl., with dead Keys)". In this case, the above problem occurs and shortcuts no longer work when text fields are highlighted. When switching to "English (US)", Ctrl + w closes the window as intended, even when a text field is highlighted. (Credit to mr. Pavlikov)
shortcut-keys google-chrome chromium
asked Dec 18 at 18:01
physicsGuy
1435
Since recently, whenever a text-field (e.g. the address bar or the askubuntu search field) is highlighted inside Google Chrome, I cannot use Ubuntu shortcuts (e.g. Ctrl+W to close a window). When hitting Ctrl+W nothing happens. As soon as I press tab to leave the text-field, the shortcuts work as expected (e.g. Ctrl+W closes the window).
I have no idea why this happens. Any ideas how to debug or solve this?
I am using Ubuntu 18.04.1 LTS and Google Chrome 71.0.3578.98.
Edit: It seems that this issue is somehow connect to Keyboard Layouts. Mostly, I use the layout "English (US, intl., with dead Keys)". In this case, the above problem occurs and shortcuts no longer work when text fields are highlighted. When switching to "English (US)", Ctrl + w closes the window as intended, even when a text field is highlighted. (Credit to mr. Pavlikov)
shortcut-keys google-chrome chromium
shortcut-keys google-chrome chromium
asked Dec 18 at 18:01
physicsGuy
1435
asked Dec 18 at 18:01
physicsGuy
1435
edited 2 days ago
asked Dec 18 at 18:01
physicsGuy
1435
asked Dec 18 at 18:01
physicsGuy
1435
asked Dec 18 at 18:01
physicsGuy
1435
1435
1
I am seeing the same. Also on Chromium. NOT on Firefox or other applications. Also maybe worth noting that this is with Unity.
– nkoren
Dec 19 at 17:23
2
Also worth noting that this happens with any selected input element, and also if the URL bar is selected. Basically any time any keyboard input is expected to be received, OS shortcut key combinations are blocked.
– nkoren
Dec 20 at 12:14
Looks like a problem with ibus :/ Killing ibus-daemon works around the issue... not sure if it's a bug in ibus or in chromium.
– Léo Lam
Dec 25 at 12:48
1
I have same issue on Ubuntu 18.10 / Google Chrome Version 71.0.3578.98 (Official Build) (64-bit). It only happens when I have alternate keyboard layout (RUS in my case), and is fine with EN layout.
– mr. Pavlikov
Dec 26 at 14:30
@mr.Pavlikov I can confirm, a change of the keyboard layout removes this issue. Details: I use the layout "English (US, intl., with dead Keys)". When switching to "English (US)", Ctrl + w closes the window as intended, even when a text field is highlighted.
– physicsGuy
2 days ago
add a comment |
1
I am seeing the same. Also on Chromium. NOT on Firefox or other applications. Also maybe worth noting that this is with Unity.
– nkoren
Dec 19 at 17:23
2
Also worth noting that this happens with any selected input element, and also if the URL bar is selected. Basically any time any keyboard input is expected to be received, OS shortcut key combinations are blocked.
– nkoren
Dec 20 at 12:14
Looks like a problem with ibus :/ Killing ibus-daemon works around the issue... not sure if it's a bug in ibus or in chromium.
– Léo Lam
Dec 25 at 12:48
1
I have same issue on Ubuntu 18.10 / Google Chrome Version 71.0.3578.98 (Official Build) (64-bit). It only happens when I have alternate keyboard layout (RUS in my case), and is fine with EN layout.
– mr. Pavlikov
Dec 26 at 14:30
@mr.Pavlikov I can confirm, a change of the keyboard layout removes this issue. Details: I use the layout "English (US, intl., with dead Keys)". When switching to "English (US)", Ctrl + w closes the window as intended, even when a text field is highlighted.
– physicsGuy
2 days ago
1
1
I am seeing the same. Also on Chromium. NOT on Firefox or other applications. Also maybe worth noting that this is with Unity.
– nkoren
Dec 19 at 17:23
I am seeing the same. Also on Chromium. NOT on Firefox or other applications. Also maybe worth noting that this is with Unity.
– nkoren
Dec 19 at 17:23
2
2
Also worth noting that this happens with any selected input element, and also if the URL bar is selected. Basically any time any keyboard input is expected to be received, OS shortcut key combinations are blocked.
– nkoren
Dec 20 at 12:14
Also worth noting that this happens with any selected input element, and also if the URL bar is selected. Basically any time any keyboard input is expected to be received, OS shortcut key combinations are blocked.
– nkoren
Dec 20 at 12:14
Looks like a problem with ibus :/ Killing ibus-daemon works around the issue... not sure if it's a bug in ibus or in chromium.
– Léo Lam
Dec 25 at 12:48
Looks like a problem with ibus :/ Killing ibus-daemon works around the issue... not sure if it's a bug in ibus or in chromium.
– Léo Lam
Dec 25 at 12:48
1
1
I have same issue on Ubuntu 18.10 / Google Chrome Version 71.0.3578.98 (Official Build) (64-bit). It only happens when I have alternate keyboard layout (RUS in my case), and is fine with EN layout.
– mr. Pavlikov
Dec 26 at 14:30
I have same issue on Ubuntu 18.10 / Google Chrome Version 71.0.3578.98 (Official Build) (64-bit). It only happens when I have alternate keyboard layout (RUS in my case), and is fine with EN layout.
– mr. Pavlikov
Dec 26 at 14:30
@mr.Pavlikov I can confirm, a change of the keyboard layout removes this issue. Details: I use the layout "English (US, intl., with dead Keys)". When switching to "English (US)", Ctrl + w closes the window as intended, even when a text field is highlighted.
– physicsGuy
2 days ago
@mr.Pavlikov I can confirm, a change of the keyboard layout removes this issue. Details: I use the layout "English (US, intl., with dead Keys)". When switching to "English (US)", Ctrl + w closes the window as intended, even when a text field is highlighted.
– physicsGuy
2 days ago
add a comment |
2 Answers
2
active
oldest
votes
I am on Chrome Version 71.0.3578.98 (Official Build) (64-bit) and Ubuntu 18.10, I was having the same issues, including Alt+D was no longer working (focus address bar), and Ctrl+T (new tab).
I had some other non-related issues with my Thunderbolt laptop dock, and therefore I updated my Linux kernel to 4.20.0-042000rc7-lowlatency. This also solved my issues with not being able to hit all keycombinations in Chrome. Before the upgrade I was on 4.18.0-13 and 4.18.0-12.
answered Dec 21 at 8:24
OlofL
315
add a comment |
Had the same problem.
What worked for me was that I changed the order of language input on my system. Make sure your default language (the one you use the most) is the first on the 'Region & Languages' input sources tab. That would make your shortcuts work when using the first language, but not the second.
Hope this helps.
answered Dec 24 at 9:07
nir
1
New contributor
nir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1102895%2fubuntu-shortcuts-not-working-when-chrome-text-fields-are-highlighted%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I am on Chrome Version 71.0.3578.98 (Official Build) (64-bit) and Ubuntu 18.10, I was having the same issues, including Alt+D was no longer working (focus address bar), and Ctrl+T (new tab).
I had some other non-related issues with my Thunderbolt laptop dock, and therefore I updated my Linux kernel to 4.20.0-042000rc7-lowlatency. This also solved my issues with not being able to hit all keycombinations in Chrome. Before the upgrade I was on 4.18.0-13 and 4.18.0-12.
answered Dec 21 at 8:24
OlofL
315
add a comment |
I am on Chrome Version 71.0.3578.98 (Official Build) (64-bit) and Ubuntu 18.10, I was having the same issues, including Alt+D was no longer working (focus address bar), and Ctrl+T (new tab).
I had some other non-related issues with my Thunderbolt laptop dock, and therefore I updated my Linux kernel to 4.20.0-042000rc7-lowlatency. This also solved my issues with not being able to hit all keycombinations in Chrome. Before the upgrade I was on 4.18.0-13 and 4.18.0-12.
answered Dec 21 at 8:24
OlofL
315
add a comment |
I am on Chrome Version 71.0.3578.98 (Official Build) (64-bit) and Ubuntu 18.10, I was having the same issues, including Alt+D was no longer working (focus address bar), and Ctrl+T (new tab).
I had some other non-related issues with my Thunderbolt laptop dock, and therefore I updated my Linux kernel to 4.20.0-042000rc7-lowlatency. This also solved my issues with not being able to hit all keycombinations in Chrome. Before the upgrade I was on 4.18.0-13 and 4.18.0-12.
answered Dec 21 at 8:24
OlofL
315
I am on Chrome Version 71.0.3578.98 (Official Build) (64-bit) and Ubuntu 18.10, I was having the same issues, including Alt+D was no longer working (focus address bar), and Ctrl+T (new tab).
I had some other non-related issues with my Thunderbolt laptop dock, and therefore I updated my Linux kernel to 4.20.0-042000rc7-lowlatency. This also solved my issues with not being able to hit all keycombinations in Chrome. Before the upgrade I was on 4.18.0-13 and 4.18.0-12.
answered Dec 21 at 8:24
OlofL
315
answered Dec 21 at 8:24
OlofL
315
answered Dec 21 at 8:24
OlofL
315
answered Dec 21 at 8:24
OlofL
315
315
add a comment |
add a comment |
Had the same problem.
What worked for me was that I changed the order of language input on my system. Make sure your default language (the one you use the most) is the first on the 'Region & Languages' input sources tab. That would make your shortcuts work when using the first language, but not the second.
Hope this helps.
answered Dec 24 at 9:07
nir
1
New contributor
nir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Had the same problem.
What worked for me was that I changed the order of language input on my system. Make sure your default language (the one you use the most) is the first on the 'Region & Languages' input sources tab. That would make your shortcuts work when using the first language, but not the second.
Hope this helps.
answered Dec 24 at 9:07
nir
1
New contributor
nir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Had the same problem.
What worked for me was that I changed the order of language input on my system. Make sure your default language (the one you use the most) is the first on the 'Region & Languages' input sources tab. That would make your shortcuts work when using the first language, but not the second.
Hope this helps.
answered Dec 24 at 9:07
nir
1
New contributor
nir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Had the same problem.
What worked for me was that I changed the order of language input on my system. Make sure your default language (the one you use the most) is the first on the 'Region & Languages' input sources tab. That would make your shortcuts work when using the first language, but not the second.
Hope this helps.
answered Dec 24 at 9:07
nir
1
New contributor
nir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Dec 24 at 9:07
nir
1
New contributor
nir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Dec 24 at 9:07
nir
1
answered Dec 24 at 9:07
nir
1
1
New contributor
nir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
nir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
nir is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1102895%2fubuntu-shortcuts-not-working-when-chrome-text-fields-are-highlighted%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I am seeing the same. Also on Chromium. NOT on Firefox or other applications. Also maybe worth noting that this is with Unity.
– nkoren
Dec 19 at 17:23
2
Also worth noting that this happens with any selected input element, and also if the URL bar is selected. Basically any time any keyboard input is expected to be received, OS shortcut key combinations are blocked.
– nkoren
Dec 20 at 12:14
Looks like a problem with ibus :/ Killing ibus-daemon works around the issue... not sure if it's a bug in ibus or in chromium.
– Léo Lam
Dec 25 at 12:48
1
I have same issue on Ubuntu 18.10 / Google Chrome Version 71.0.3578.98 (Official Build) (64-bit). It only happens when I have alternate keyboard layout (RUS in my case), and is fine with EN layout.
– mr. Pavlikov
Dec 26 at 14:30
@mr.Pavlikov I can confirm, a change of the keyboard layout removes this issue. Details: I use the layout "English (US, intl., with dead Keys)". When switching to "English (US)", Ctrl + w closes the window as intended, even when a text field is highlighted.
– physicsGuy
2 days ago