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 '18 at 18:01
physicsGuyphysicsGuy
1706
|
show 1 more 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 '18 at 18:01
physicsGuyphysicsGuy
1706
2
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 '18 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 '18 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 '18 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 '18 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
Dec 27 '18 at 12:16
|
show 1 more 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 '18 at 18:01
physicsGuyphysicsGuy
1706
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 '18 at 18:01
physicsGuyphysicsGuy
1706
asked Dec 18 '18 at 18:01
physicsGuyphysicsGuy
1706
edited Dec 27 '18 at 12:18
physicsGuy
asked Dec 18 '18 at 18:01
physicsGuyphysicsGuy
1706
asked Dec 18 '18 at 18:01
physicsGuyphysicsGuy
1706
asked Dec 18 '18 at 18:01
physicsGuyphysicsGuy
1706
1706
2
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 '18 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 '18 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 '18 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 '18 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
Dec 27 '18 at 12:16
|
show 1 more comment
2
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 '18 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 '18 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 '18 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 '18 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
Dec 27 '18 at 12:16
2
2
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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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
Dec 27 '18 at 12:16
@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
Dec 27 '18 at 12:16
|
show 1 more comment
4 Answers
4
active
oldest
votes
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 '18 at 9:07
nirnir
361
Thanks a lot, that fixed the problem.
– physicsGuy
Jan 3 at 19:11
add a comment |
I also have same problem in ubuntu-mate 18.10 and google chrome 71
the problem is probably because there is no required library/package for the ibus to work in google chrome
installing these package fix the problem in my computer
sudo apt install ibus ibus-gtk ibus-gtk3 ibus-qt4
answered Jan 2 at 15:08
buncisbuncis
15116
Thanks, but for me this didn't solve the problem.
– physicsGuy
Jan 3 at 19:12
This solved the problem for me, thanks! I knew it had to do with ibus as killing ibus-daemon works around the issue, but I'm not sure why this was needed. Installing ibus-qt4 probably isn't needed, though, considering Chromium doesn't use Qt4.
– Léo Lam
9 hours ago
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 '18 at 8:24
OlofLOlofL
315
The kernel doesn't have anything to do with keyboard shortcuts in this case. That's pretty much an userspace problem, and here it is in fact caused by ibus. That your problem got solved after you updated your kernel is very likely to be a coincidence.
– Léo Lam
9 hours ago
add a comment |
I am on Chrome 71.0.3578.80 & Ubuntu 18.04. Same problem.
It's due to IBus input system - whenever it's selected in the Language Support, chrome shortcuts stop working in textbox (address bar, form, etc), but not elsewhere.
None of other input systems have the same problem: fcitx, gcin, etc.
PS: I verified on my Ubuntu that it has nothing to do with language, locale or keyboard layout.
answered Jan 2 at 11:54
AqDAqD
1011
New contributor
AqD 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
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
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 '18 at 9:07
nirnir
361
Thanks a lot, that fixed the problem.
– physicsGuy
Jan 3 at 19:11
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 '18 at 9:07
nirnir
361
Thanks a lot, that fixed the problem.
– physicsGuy
Jan 3 at 19:11
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 '18 at 9:07
nirnir
361
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 '18 at 9:07
nirnir
361
answered Dec 24 '18 at 9:07
nirnir
361
answered Dec 24 '18 at 9:07
nirnir
361
answered Dec 24 '18 at 9:07
nirnir
361
361
Thanks a lot, that fixed the problem.
– physicsGuy
Jan 3 at 19:11
add a comment |
Thanks a lot, that fixed the problem.
– physicsGuy
Jan 3 at 19:11
Thanks a lot, that fixed the problem.
– physicsGuy
Jan 3 at 19:11
Thanks a lot, that fixed the problem.
– physicsGuy
Jan 3 at 19:11
add a comment |
I also have same problem in ubuntu-mate 18.10 and google chrome 71
the problem is probably because there is no required library/package for the ibus to work in google chrome
installing these package fix the problem in my computer
sudo apt install ibus ibus-gtk ibus-gtk3 ibus-qt4
answered Jan 2 at 15:08
buncisbuncis
15116
Thanks, but for me this didn't solve the problem.
– physicsGuy
Jan 3 at 19:12
This solved the problem for me, thanks! I knew it had to do with ibus as killing ibus-daemon works around the issue, but I'm not sure why this was needed. Installing ibus-qt4 probably isn't needed, though, considering Chromium doesn't use Qt4.
– Léo Lam
9 hours ago
add a comment |
I also have same problem in ubuntu-mate 18.10 and google chrome 71
the problem is probably because there is no required library/package for the ibus to work in google chrome
installing these package fix the problem in my computer
sudo apt install ibus ibus-gtk ibus-gtk3 ibus-qt4
answered Jan 2 at 15:08
buncisbuncis
15116
Thanks, but for me this didn't solve the problem.
– physicsGuy
Jan 3 at 19:12
This solved the problem for me, thanks! I knew it had to do with ibus as killing ibus-daemon works around the issue, but I'm not sure why this was needed. Installing ibus-qt4 probably isn't needed, though, considering Chromium doesn't use Qt4.
– Léo Lam
9 hours ago
add a comment |
I also have same problem in ubuntu-mate 18.10 and google chrome 71
the problem is probably because there is no required library/package for the ibus to work in google chrome
installing these package fix the problem in my computer
sudo apt install ibus ibus-gtk ibus-gtk3 ibus-qt4
answered Jan 2 at 15:08
buncisbuncis
15116
I also have same problem in ubuntu-mate 18.10 and google chrome 71
the problem is probably because there is no required library/package for the ibus to work in google chrome
installing these package fix the problem in my computer
sudo apt install ibus ibus-gtk ibus-gtk3 ibus-qt4
answered Jan 2 at 15:08
buncisbuncis
15116
answered Jan 2 at 15:08
buncisbuncis
15116
answered Jan 2 at 15:08
buncisbuncis
15116
answered Jan 2 at 15:08
buncisbuncis
15116
15116
Thanks, but for me this didn't solve the problem.
– physicsGuy
Jan 3 at 19:12
This solved the problem for me, thanks! I knew it had to do with ibus as killing ibus-daemon works around the issue, but I'm not sure why this was needed. Installing ibus-qt4 probably isn't needed, though, considering Chromium doesn't use Qt4.
– Léo Lam
9 hours ago
add a comment |
Thanks, but for me this didn't solve the problem.
– physicsGuy
Jan 3 at 19:12
This solved the problem for me, thanks! I knew it had to do with ibus as killing ibus-daemon works around the issue, but I'm not sure why this was needed. Installing ibus-qt4 probably isn't needed, though, considering Chromium doesn't use Qt4.
– Léo Lam
9 hours ago
Thanks, but for me this didn't solve the problem.
– physicsGuy
Jan 3 at 19:12
Thanks, but for me this didn't solve the problem.
– physicsGuy
Jan 3 at 19:12
This solved the problem for me, thanks! I knew it had to do with ibus as killing ibus-daemon works around the issue, but I'm not sure why this was needed. Installing ibus-qt4 probably isn't needed, though, considering Chromium doesn't use Qt4.
– Léo Lam
9 hours ago
This solved the problem for me, thanks! I knew it had to do with ibus as killing ibus-daemon works around the issue, but I'm not sure why this was needed. Installing ibus-qt4 probably isn't needed, though, considering Chromium doesn't use Qt4.
– Léo Lam
9 hours ago
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 '18 at 8:24
OlofLOlofL
315
The kernel doesn't have anything to do with keyboard shortcuts in this case. That's pretty much an userspace problem, and here it is in fact caused by ibus. That your problem got solved after you updated your kernel is very likely to be a coincidence.
– Léo Lam
9 hours ago
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 '18 at 8:24
OlofLOlofL
315
The kernel doesn't have anything to do with keyboard shortcuts in this case. That's pretty much an userspace problem, and here it is in fact caused by ibus. That your problem got solved after you updated your kernel is very likely to be a coincidence.
– Léo Lam
9 hours ago
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 '18 at 8:24
OlofLOlofL
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 '18 at 8:24
OlofLOlofL
315
answered Dec 21 '18 at 8:24
OlofLOlofL
315
answered Dec 21 '18 at 8:24
OlofLOlofL
315
answered Dec 21 '18 at 8:24
OlofLOlofL
315
315
The kernel doesn't have anything to do with keyboard shortcuts in this case. That's pretty much an userspace problem, and here it is in fact caused by ibus. That your problem got solved after you updated your kernel is very likely to be a coincidence.
– Léo Lam
9 hours ago
add a comment |
The kernel doesn't have anything to do with keyboard shortcuts in this case. That's pretty much an userspace problem, and here it is in fact caused by ibus. That your problem got solved after you updated your kernel is very likely to be a coincidence.
– Léo Lam
9 hours ago
The kernel doesn't have anything to do with keyboard shortcuts in this case. That's pretty much an userspace problem, and here it is in fact caused by ibus. That your problem got solved after you updated your kernel is very likely to be a coincidence.
– Léo Lam
9 hours ago
The kernel doesn't have anything to do with keyboard shortcuts in this case. That's pretty much an userspace problem, and here it is in fact caused by ibus. That your problem got solved after you updated your kernel is very likely to be a coincidence.
– Léo Lam
9 hours ago
add a comment |
I am on Chrome 71.0.3578.80 & Ubuntu 18.04. Same problem.
It's due to IBus input system - whenever it's selected in the Language Support, chrome shortcuts stop working in textbox (address bar, form, etc), but not elsewhere.
None of other input systems have the same problem: fcitx, gcin, etc.
PS: I verified on my Ubuntu that it has nothing to do with language, locale or keyboard layout.
answered Jan 2 at 11:54
AqDAqD
1011
New contributor
AqD 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 |
I am on Chrome 71.0.3578.80 & Ubuntu 18.04. Same problem.
It's due to IBus input system - whenever it's selected in the Language Support, chrome shortcuts stop working in textbox (address bar, form, etc), but not elsewhere.
None of other input systems have the same problem: fcitx, gcin, etc.
PS: I verified on my Ubuntu that it has nothing to do with language, locale or keyboard layout.
answered Jan 2 at 11:54
AqDAqD
1011
New contributor
AqD 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 |
I am on Chrome 71.0.3578.80 & Ubuntu 18.04. Same problem.
It's due to IBus input system - whenever it's selected in the Language Support, chrome shortcuts stop working in textbox (address bar, form, etc), but not elsewhere.
None of other input systems have the same problem: fcitx, gcin, etc.
PS: I verified on my Ubuntu that it has nothing to do with language, locale or keyboard layout.
answered Jan 2 at 11:54
AqDAqD
1011
New contributor
AqD is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I am on Chrome 71.0.3578.80 & Ubuntu 18.04. Same problem.
It's due to IBus input system - whenever it's selected in the Language Support, chrome shortcuts stop working in textbox (address bar, form, etc), but not elsewhere.
None of other input systems have the same problem: fcitx, gcin, etc.
PS: I verified on my Ubuntu that it has nothing to do with language, locale or keyboard layout.
answered Jan 2 at 11:54
AqDAqD
1011
New contributor
AqD is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Jan 2 at 11:54
AqDAqD
1011
New contributor
AqD is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Jan 2 at 11:54
AqDAqD
1011
answered Jan 2 at 11:54
AqDAqD
1011
1011
New contributor
AqD is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
AqD is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
AqD 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
2
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 '18 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 '18 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 '18 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 '18 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
Dec 27 '18 at 12:16