Alt + F4 switches to TTY4
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
58
Since yesterday Alt+F4 is working unexpectedly on my computer. When I press those key TTY4 is opened. Also, the application which is running on the GUI receives the Alt+F4 message. This is solved by rebooting the system, but after a while it starts working this way again.
As far as I have googled there are other people finding this problem but with no solutions (1, 2).
I am running Ubuntu Gnome 16.10, Kernel version 4.8.0-39-generic and GNOME Shell version 3.20.4.
command-line gnome shortcut-keys tty
edited Oct 19 '18 at 0:35
Jeff
880919
asked Feb 23 '17 at 17:28
ig343ig343
3831615
|
show 9 more comments
58
Since yesterday Alt+F4 is working unexpectedly on my computer. When I press those key TTY4 is opened. Also, the application which is running on the GUI receives the Alt+F4 message. This is solved by rebooting the system, but after a while it starts working this way again.
As far as I have googled there are other people finding this problem but with no solutions (1, 2).
I am running Ubuntu Gnome 16.10, Kernel version 4.8.0-39-generic and GNOME Shell version 3.20.4.
command-line gnome shortcut-keys tty
edited Oct 19 '18 at 0:35
Jeff
880919
asked Feb 23 '17 at 17:28
ig343ig343
3831615
Did you try the answer from the second post you linked?
– M. Becerra
Feb 23 '17 at 17:42
You might want to check out this question : askubuntu.com/questions/123493/screen-went-black
– Dimitri Markovich
Feb 23 '17 at 17:49
@M.Becerra I don't have the package console-cyrillic installed on my system.
– ig343
Feb 24 '17 at 3:39
3
@DimitriMarkovich I did not hit Ctrl+Alt+F4, I am absolutely sure it's Alt+F4 which is doing what Ctrl+Alt+F4 should do.
– ig343
Feb 24 '17 at 3:40
1
it seems related to a kernel upgrade, and it happens on other Linux distros: unix.stackexchange.com/questions/59949/…
– elias
Jul 10 '17 at 14:25
|
show 9 more comments
58
58
58
13
Since yesterday Alt+F4 is working unexpectedly on my computer. When I press those key TTY4 is opened. Also, the application which is running on the GUI receives the Alt+F4 message. This is solved by rebooting the system, but after a while it starts working this way again.
As far as I have googled there are other people finding this problem but with no solutions (1, 2).
I am running Ubuntu Gnome 16.10, Kernel version 4.8.0-39-generic and GNOME Shell version 3.20.4.
command-line gnome shortcut-keys tty
edited Oct 19 '18 at 0:35
Jeff
880919
asked Feb 23 '17 at 17:28
ig343ig343
3831615
Since yesterday Alt+F4 is working unexpectedly on my computer. When I press those key TTY4 is opened. Also, the application which is running on the GUI receives the Alt+F4 message. This is solved by rebooting the system, but after a while it starts working this way again.
As far as I have googled there are other people finding this problem but with no solutions (1, 2).
I am running Ubuntu Gnome 16.10, Kernel version 4.8.0-39-generic and GNOME Shell version 3.20.4.
command-line gnome shortcut-keys tty
command-line gnome shortcut-keys tty
edited Oct 19 '18 at 0:35
Jeff
880919
asked Feb 23 '17 at 17:28
ig343ig343
3831615
edited Oct 19 '18 at 0:35
Jeff
880919
asked Feb 23 '17 at 17:28
ig343ig343
3831615
edited Oct 19 '18 at 0:35
Jeff
880919
edited Oct 19 '18 at 0:35
Jeff
880919
edited Oct 19 '18 at 0:35
Jeff
880919
880919
asked Feb 23 '17 at 17:28
ig343ig343
3831615
asked Feb 23 '17 at 17:28
ig343ig343
3831615
asked Feb 23 '17 at 17:28
ig343ig343
3831615
3831615
Did you try the answer from the second post you linked?
– M. Becerra
Feb 23 '17 at 17:42
You might want to check out this question : askubuntu.com/questions/123493/screen-went-black
– Dimitri Markovich
Feb 23 '17 at 17:49
@M.Becerra I don't have the package console-cyrillic installed on my system.
– ig343
Feb 24 '17 at 3:39
3
@DimitriMarkovich I did not hit Ctrl+Alt+F4, I am absolutely sure it's Alt+F4 which is doing what Ctrl+Alt+F4 should do.
– ig343
Feb 24 '17 at 3:40
1
it seems related to a kernel upgrade, and it happens on other Linux distros: unix.stackexchange.com/questions/59949/…
– elias
Jul 10 '17 at 14:25
|
show 9 more comments
Did you try the answer from the second post you linked?
– M. Becerra
Feb 23 '17 at 17:42
You might want to check out this question : askubuntu.com/questions/123493/screen-went-black
– Dimitri Markovich
Feb 23 '17 at 17:49
@M.Becerra I don't have the package console-cyrillic installed on my system.
– ig343
Feb 24 '17 at 3:39
3
@DimitriMarkovich I did not hit Ctrl+Alt+F4, I am absolutely sure it's Alt+F4 which is doing what Ctrl+Alt+F4 should do.
– ig343
Feb 24 '17 at 3:40
1
it seems related to a kernel upgrade, and it happens on other Linux distros: unix.stackexchange.com/questions/59949/…
– elias
Jul 10 '17 at 14:25
Did you try the answer from the second post you linked?
– M. Becerra
Feb 23 '17 at 17:42
Did you try the answer from the second post you linked?
– M. Becerra
Feb 23 '17 at 17:42
You might want to check out this question : askubuntu.com/questions/123493/screen-went-black
– Dimitri Markovich
Feb 23 '17 at 17:49
You might want to check out this question : askubuntu.com/questions/123493/screen-went-black
– Dimitri Markovich
Feb 23 '17 at 17:49
@M.Becerra I don't have the package console-cyrillic installed on my system.
– ig343
Feb 24 '17 at 3:39
@M.Becerra I don't have the package console-cyrillic installed on my system.
– ig343
Feb 24 '17 at 3:39
3
3
@DimitriMarkovich I did not hit Ctrl+Alt+F4, I am absolutely sure it's Alt+F4 which is doing what Ctrl+Alt+F4 should do.
– ig343
Feb 24 '17 at 3:40
@DimitriMarkovich I did not hit Ctrl+Alt+F4, I am absolutely sure it's Alt+F4 which is doing what Ctrl+Alt+F4 should do.
– ig343
Feb 24 '17 at 3:40
1
1
it seems related to a kernel upgrade, and it happens on other Linux distros: unix.stackexchange.com/questions/59949/…
– elias
Jul 10 '17 at 14:25
it seems related to a kernel upgrade, and it happens on other Linux distros: unix.stackexchange.com/questions/59949/…
– elias
Jul 10 '17 at 14:25
|
show 9 more comments
4 Answers
4
active
oldest
votes
88
I had this recently on Ubuntu GNOME and on Unity. The answer is this:-
sudo kbd_mode -s
Run that in a terminal and then the Alt+F4 keyboard combination returns to normal.
edited Oct 19 '18 at 0:35
Jeff
880919
answered Jun 25 '17 at 21:07
popeypopey
13.3k74791
5
Runningsudo kbd_modebefore the above command showed me that my keyboard was in “Unicode (UTF-8) mode”. The above command will set your keyboard mode to “raw (scancode) mode”, asman kbd_modecan verify.
– Rory O'Kane
Jul 31 '18 at 22:26
1
Just for future reference for others, this works in 18.04 as well (it uses GNOME by default).
– jhpratt
Sep 6 '18 at 1:16
1
And sudo kbd_mode -u to switch back to unicode mode
– WitchCraft
Sep 8 '18 at 5:35
2
It is really annoying to have to do this for every boot, apparently a permanent solution is to edit /etc/console-setup/remap.inc as described by askubuntu.com/a/1059609/104605 .
– Compholio
Oct 4 '18 at 14:26
add a comment |
0
1) As root, edit /etc/console-setup/remap.inc
2) Add this line at the bottom:
alt keycode 62 = VoidSymbol
3) Run sudo dpkg-reconfigure console-setup -phigh
4) Reboot
5) The problem should be fixed now. At least it worked for me.
answered 13 mins ago
Nicolas RaoulNicolas Raoul
5,2052065115
add a comment |
-2
Things to do
1. Alt + f1
- what will above do? Will it open TTY1?
2. open terminal and just press "j" without quote
what is the output? will it work same as pressing enter key? or just prints "j"?
In the link you posted @Pielco11 says sudo update-grub solves the problem.
Also try sudo apt-get update
edited Apr 13 '17 at 12:23
Community♦
1
answered Mar 25 '17 at 7:56
Err0rrErr0rr
4019
When this happens, Alt+F1 opens TTY1. I haven't tried pressing J on a terminal specifically but I know that other commands using Ctrl work fine.
– ig343
Mar 26 '17 at 16:52
can you confirm what will happen if you just press "j" in terminal? Open terminal with ctrl + Atl +T
– Err0rr
Mar 27 '17 at 5:19
I tried what you asked and it just prints "j".
– ig343
Apr 5 '17 at 15:51
add a comment |
-3
Some ideas to trace down and maybe fix the issue:
- Booting with a Live-CD in order to check if the problem is physical
- Use another keyboard
- Switch the keyboard layout or try to remap the Ctrl
- Does it only happen on the desktop environment or does it also switch to TTY4 if you are at some other TTY? If it happens also on the TTYs, it might be related to some kernel parameter.
Did you try the tip on the last comment of your second reference (update-grub)?
answered Mar 25 '17 at 7:32
Julen LarruceaJulen Larrucea
879420
It is definitely not physical. Yes, I have updated grub.
– ig343
Mar 26 '17 at 16:50
Have you tried booting from a live CD? I happen to have a similar problem right now and I am comparing settings between a good and a bad machine. If a live CD session works properly, you could try to compare the outputs of, for example:env,locale,localectlorlocale charmap.
– Julen Larrucea
Mar 27 '17 at 16:51
The thing is my computer works normally most of times. This just happens from time to time, so it is hard to compare.
– ig343
Mar 28 '17 at 5:31
It sounds like a tricky problem. Maybe you could make a script that outputs all the related information and save it into a file (including all commands above). Then run it again when the problem reappears and make adiffor something with both files.
– Julen Larrucea
Mar 28 '17 at 7:53
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
});
}
});
draft saved
draft discarded
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%2f886593%2falt-f4-switches-to-tty4%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
88
I had this recently on Ubuntu GNOME and on Unity. The answer is this:-
sudo kbd_mode -s
Run that in a terminal and then the Alt+F4 keyboard combination returns to normal.
edited Oct 19 '18 at 0:35
Jeff
880919
answered Jun 25 '17 at 21:07
popeypopey
13.3k74791
5
Runningsudo kbd_modebefore the above command showed me that my keyboard was in “Unicode (UTF-8) mode”. The above command will set your keyboard mode to “raw (scancode) mode”, asman kbd_modecan verify.
– Rory O'Kane
Jul 31 '18 at 22:26
1
Just for future reference for others, this works in 18.04 as well (it uses GNOME by default).
– jhpratt
Sep 6 '18 at 1:16
1
And sudo kbd_mode -u to switch back to unicode mode
– WitchCraft
Sep 8 '18 at 5:35
2
It is really annoying to have to do this for every boot, apparently a permanent solution is to edit /etc/console-setup/remap.inc as described by askubuntu.com/a/1059609/104605 .
– Compholio
Oct 4 '18 at 14:26
add a comment |
88
I had this recently on Ubuntu GNOME and on Unity. The answer is this:-
sudo kbd_mode -s
Run that in a terminal and then the Alt+F4 keyboard combination returns to normal.
edited Oct 19 '18 at 0:35
Jeff
880919
answered Jun 25 '17 at 21:07
popeypopey
13.3k74791
5
Runningsudo kbd_modebefore the above command showed me that my keyboard was in “Unicode (UTF-8) mode”. The above command will set your keyboard mode to “raw (scancode) mode”, asman kbd_modecan verify.
– Rory O'Kane
Jul 31 '18 at 22:26
1
Just for future reference for others, this works in 18.04 as well (it uses GNOME by default).
– jhpratt
Sep 6 '18 at 1:16
1
And sudo kbd_mode -u to switch back to unicode mode
– WitchCraft
Sep 8 '18 at 5:35
2
It is really annoying to have to do this for every boot, apparently a permanent solution is to edit /etc/console-setup/remap.inc as described by askubuntu.com/a/1059609/104605 .
– Compholio
Oct 4 '18 at 14:26
add a comment |
88
88
88
I had this recently on Ubuntu GNOME and on Unity. The answer is this:-
sudo kbd_mode -s
Run that in a terminal and then the Alt+F4 keyboard combination returns to normal.
edited Oct 19 '18 at 0:35
Jeff
880919
answered Jun 25 '17 at 21:07
popeypopey
13.3k74791
I had this recently on Ubuntu GNOME and on Unity. The answer is this:-
sudo kbd_mode -s
Run that in a terminal and then the Alt+F4 keyboard combination returns to normal.
edited Oct 19 '18 at 0:35
Jeff
880919
answered Jun 25 '17 at 21:07
popeypopey
13.3k74791
edited Oct 19 '18 at 0:35
Jeff
880919
edited Oct 19 '18 at 0:35
Jeff
880919
edited Oct 19 '18 at 0:35
Jeff
880919
880919
answered Jun 25 '17 at 21:07
popeypopey
13.3k74791
answered Jun 25 '17 at 21:07
popeypopey
13.3k74791
answered Jun 25 '17 at 21:07
popeypopey
13.3k74791
13.3k74791
5
Runningsudo kbd_modebefore the above command showed me that my keyboard was in “Unicode (UTF-8) mode”. The above command will set your keyboard mode to “raw (scancode) mode”, asman kbd_modecan verify.
– Rory O'Kane
Jul 31 '18 at 22:26
1
Just for future reference for others, this works in 18.04 as well (it uses GNOME by default).
– jhpratt
Sep 6 '18 at 1:16
1
And sudo kbd_mode -u to switch back to unicode mode
– WitchCraft
Sep 8 '18 at 5:35
2
It is really annoying to have to do this for every boot, apparently a permanent solution is to edit /etc/console-setup/remap.inc as described by askubuntu.com/a/1059609/104605 .
– Compholio
Oct 4 '18 at 14:26
add a comment |
5
Runningsudo kbd_modebefore the above command showed me that my keyboard was in “Unicode (UTF-8) mode”. The above command will set your keyboard mode to “raw (scancode) mode”, asman kbd_modecan verify.
– Rory O'Kane
Jul 31 '18 at 22:26
1
Just for future reference for others, this works in 18.04 as well (it uses GNOME by default).
– jhpratt
Sep 6 '18 at 1:16
1
And sudo kbd_mode -u to switch back to unicode mode
– WitchCraft
Sep 8 '18 at 5:35
2
It is really annoying to have to do this for every boot, apparently a permanent solution is to edit /etc/console-setup/remap.inc as described by askubuntu.com/a/1059609/104605 .
– Compholio
Oct 4 '18 at 14:26
5
5
Running
sudo kbd_mode before the above command showed me that my keyboard was in “Unicode (UTF-8) mode”. The above command will set your keyboard mode to “raw (scancode) mode”, as man kbd_mode can verify.– Rory O'Kane
Jul 31 '18 at 22:26
Running
sudo kbd_mode before the above command showed me that my keyboard was in “Unicode (UTF-8) mode”. The above command will set your keyboard mode to “raw (scancode) mode”, as man kbd_mode can verify.– Rory O'Kane
Jul 31 '18 at 22:26
1
1
Just for future reference for others, this works in 18.04 as well (it uses GNOME by default).
– jhpratt
Sep 6 '18 at 1:16
Just for future reference for others, this works in 18.04 as well (it uses GNOME by default).
– jhpratt
Sep 6 '18 at 1:16
1
1
And sudo kbd_mode -u to switch back to unicode mode
– WitchCraft
Sep 8 '18 at 5:35
And sudo kbd_mode -u to switch back to unicode mode
– WitchCraft
Sep 8 '18 at 5:35
2
2
It is really annoying to have to do this for every boot, apparently a permanent solution is to edit /etc/console-setup/remap.inc as described by askubuntu.com/a/1059609/104605 .
– Compholio
Oct 4 '18 at 14:26
It is really annoying to have to do this for every boot, apparently a permanent solution is to edit /etc/console-setup/remap.inc as described by askubuntu.com/a/1059609/104605 .
– Compholio
Oct 4 '18 at 14:26
add a comment |
0
1) As root, edit /etc/console-setup/remap.inc
2) Add this line at the bottom:
alt keycode 62 = VoidSymbol
3) Run sudo dpkg-reconfigure console-setup -phigh
4) Reboot
5) The problem should be fixed now. At least it worked for me.
answered 13 mins ago
Nicolas RaoulNicolas Raoul
5,2052065115
add a comment |
0
1) As root, edit /etc/console-setup/remap.inc
2) Add this line at the bottom:
alt keycode 62 = VoidSymbol
3) Run sudo dpkg-reconfigure console-setup -phigh
4) Reboot
5) The problem should be fixed now. At least it worked for me.
answered 13 mins ago
Nicolas RaoulNicolas Raoul
5,2052065115
add a comment |
0
0
0
1) As root, edit /etc/console-setup/remap.inc
2) Add this line at the bottom:
alt keycode 62 = VoidSymbol
3) Run sudo dpkg-reconfigure console-setup -phigh
4) Reboot
5) The problem should be fixed now. At least it worked for me.
answered 13 mins ago
Nicolas RaoulNicolas Raoul
5,2052065115
1) As root, edit /etc/console-setup/remap.inc
2) Add this line at the bottom:
alt keycode 62 = VoidSymbol
3) Run sudo dpkg-reconfigure console-setup -phigh
4) Reboot
5) The problem should be fixed now. At least it worked for me.
answered 13 mins ago
Nicolas RaoulNicolas Raoul
5,2052065115
answered 13 mins ago
Nicolas RaoulNicolas Raoul
5,2052065115
answered 13 mins ago
Nicolas RaoulNicolas Raoul
5,2052065115
answered 13 mins ago
Nicolas RaoulNicolas Raoul
5,2052065115
5,2052065115
add a comment |
add a comment |
-2
Things to do
1. Alt + f1
- what will above do? Will it open TTY1?
2. open terminal and just press "j" without quote
what is the output? will it work same as pressing enter key? or just prints "j"?
In the link you posted @Pielco11 says sudo update-grub solves the problem.
Also try sudo apt-get update
edited Apr 13 '17 at 12:23
Community♦
1
answered Mar 25 '17 at 7:56
Err0rrErr0rr
4019
When this happens, Alt+F1 opens TTY1. I haven't tried pressing J on a terminal specifically but I know that other commands using Ctrl work fine.
– ig343
Mar 26 '17 at 16:52
can you confirm what will happen if you just press "j" in terminal? Open terminal with ctrl + Atl +T
– Err0rr
Mar 27 '17 at 5:19
I tried what you asked and it just prints "j".
– ig343
Apr 5 '17 at 15:51
add a comment |
-2
Things to do
1. Alt + f1
- what will above do? Will it open TTY1?
2. open terminal and just press "j" without quote
what is the output? will it work same as pressing enter key? or just prints "j"?
In the link you posted @Pielco11 says sudo update-grub solves the problem.
Also try sudo apt-get update
edited Apr 13 '17 at 12:23
Community♦
1
answered Mar 25 '17 at 7:56
Err0rrErr0rr
4019
When this happens, Alt+F1 opens TTY1. I haven't tried pressing J on a terminal specifically but I know that other commands using Ctrl work fine.
– ig343
Mar 26 '17 at 16:52
can you confirm what will happen if you just press "j" in terminal? Open terminal with ctrl + Atl +T
– Err0rr
Mar 27 '17 at 5:19
I tried what you asked and it just prints "j".
– ig343
Apr 5 '17 at 15:51
add a comment |
-2
-2
-2
Things to do
1. Alt + f1
- what will above do? Will it open TTY1?
2. open terminal and just press "j" without quote
what is the output? will it work same as pressing enter key? or just prints "j"?
In the link you posted @Pielco11 says sudo update-grub solves the problem.
Also try sudo apt-get update
edited Apr 13 '17 at 12:23
Community♦
1
answered Mar 25 '17 at 7:56
Err0rrErr0rr
4019
Things to do
1. Alt + f1
- what will above do? Will it open TTY1?
2. open terminal and just press "j" without quote
what is the output? will it work same as pressing enter key? or just prints "j"?
In the link you posted @Pielco11 says sudo update-grub solves the problem.
Also try sudo apt-get update
edited Apr 13 '17 at 12:23
Community♦
1
answered Mar 25 '17 at 7:56
Err0rrErr0rr
4019
edited Apr 13 '17 at 12:23
Community♦
1
edited Apr 13 '17 at 12:23
Community♦
1
edited Apr 13 '17 at 12:23
Community♦
1
1
answered Mar 25 '17 at 7:56
Err0rrErr0rr
4019
answered Mar 25 '17 at 7:56
Err0rrErr0rr
4019
answered Mar 25 '17 at 7:56
Err0rrErr0rr
4019
4019
When this happens, Alt+F1 opens TTY1. I haven't tried pressing J on a terminal specifically but I know that other commands using Ctrl work fine.
– ig343
Mar 26 '17 at 16:52
can you confirm what will happen if you just press "j" in terminal? Open terminal with ctrl + Atl +T
– Err0rr
Mar 27 '17 at 5:19
I tried what you asked and it just prints "j".
– ig343
Apr 5 '17 at 15:51
add a comment |
When this happens, Alt+F1 opens TTY1. I haven't tried pressing J on a terminal specifically but I know that other commands using Ctrl work fine.
– ig343
Mar 26 '17 at 16:52
can you confirm what will happen if you just press "j" in terminal? Open terminal with ctrl + Atl +T
– Err0rr
Mar 27 '17 at 5:19
I tried what you asked and it just prints "j".
– ig343
Apr 5 '17 at 15:51
When this happens, Alt+F1 opens TTY1. I haven't tried pressing J on a terminal specifically but I know that other commands using Ctrl work fine.
– ig343
Mar 26 '17 at 16:52
When this happens, Alt+F1 opens TTY1. I haven't tried pressing J on a terminal specifically but I know that other commands using Ctrl work fine.
– ig343
Mar 26 '17 at 16:52
can you confirm what will happen if you just press "j" in terminal? Open terminal with ctrl + Atl +T
– Err0rr
Mar 27 '17 at 5:19
can you confirm what will happen if you just press "j" in terminal? Open terminal with ctrl + Atl +T
– Err0rr
Mar 27 '17 at 5:19
I tried what you asked and it just prints "j".
– ig343
Apr 5 '17 at 15:51
I tried what you asked and it just prints "j".
– ig343
Apr 5 '17 at 15:51
add a comment |
-3
Some ideas to trace down and maybe fix the issue:
- Booting with a Live-CD in order to check if the problem is physical
- Use another keyboard
- Switch the keyboard layout or try to remap the Ctrl
- Does it only happen on the desktop environment or does it also switch to TTY4 if you are at some other TTY? If it happens also on the TTYs, it might be related to some kernel parameter.
Did you try the tip on the last comment of your second reference (update-grub)?
answered Mar 25 '17 at 7:32
Julen LarruceaJulen Larrucea
879420
It is definitely not physical. Yes, I have updated grub.
– ig343
Mar 26 '17 at 16:50
Have you tried booting from a live CD? I happen to have a similar problem right now and I am comparing settings between a good and a bad machine. If a live CD session works properly, you could try to compare the outputs of, for example:env,locale,localectlorlocale charmap.
– Julen Larrucea
Mar 27 '17 at 16:51
The thing is my computer works normally most of times. This just happens from time to time, so it is hard to compare.
– ig343
Mar 28 '17 at 5:31
It sounds like a tricky problem. Maybe you could make a script that outputs all the related information and save it into a file (including all commands above). Then run it again when the problem reappears and make adiffor something with both files.
– Julen Larrucea
Mar 28 '17 at 7:53
add a comment |
-3
Some ideas to trace down and maybe fix the issue:
- Booting with a Live-CD in order to check if the problem is physical
- Use another keyboard
- Switch the keyboard layout or try to remap the Ctrl
- Does it only happen on the desktop environment or does it also switch to TTY4 if you are at some other TTY? If it happens also on the TTYs, it might be related to some kernel parameter.
Did you try the tip on the last comment of your second reference (update-grub)?
answered Mar 25 '17 at 7:32
Julen LarruceaJulen Larrucea
879420
It is definitely not physical. Yes, I have updated grub.
– ig343
Mar 26 '17 at 16:50
Have you tried booting from a live CD? I happen to have a similar problem right now and I am comparing settings between a good and a bad machine. If a live CD session works properly, you could try to compare the outputs of, for example:env,locale,localectlorlocale charmap.
– Julen Larrucea
Mar 27 '17 at 16:51
The thing is my computer works normally most of times. This just happens from time to time, so it is hard to compare.
– ig343
Mar 28 '17 at 5:31
It sounds like a tricky problem. Maybe you could make a script that outputs all the related information and save it into a file (including all commands above). Then run it again when the problem reappears and make adiffor something with both files.
– Julen Larrucea
Mar 28 '17 at 7:53
add a comment |
-3
-3
-3
Some ideas to trace down and maybe fix the issue:
- Booting with a Live-CD in order to check if the problem is physical
- Use another keyboard
- Switch the keyboard layout or try to remap the Ctrl
- Does it only happen on the desktop environment or does it also switch to TTY4 if you are at some other TTY? If it happens also on the TTYs, it might be related to some kernel parameter.
Did you try the tip on the last comment of your second reference (update-grub)?
answered Mar 25 '17 at 7:32
Julen LarruceaJulen Larrucea
879420
Some ideas to trace down and maybe fix the issue:
- Booting with a Live-CD in order to check if the problem is physical
- Use another keyboard
- Switch the keyboard layout or try to remap the Ctrl
- Does it only happen on the desktop environment or does it also switch to TTY4 if you are at some other TTY? If it happens also on the TTYs, it might be related to some kernel parameter.
Did you try the tip on the last comment of your second reference (update-grub)?
answered Mar 25 '17 at 7:32
Julen LarruceaJulen Larrucea
879420
answered Mar 25 '17 at 7:32
Julen LarruceaJulen Larrucea
879420
answered Mar 25 '17 at 7:32
Julen LarruceaJulen Larrucea
879420
answered Mar 25 '17 at 7:32
Julen LarruceaJulen Larrucea
879420
879420
It is definitely not physical. Yes, I have updated grub.
– ig343
Mar 26 '17 at 16:50
Have you tried booting from a live CD? I happen to have a similar problem right now and I am comparing settings between a good and a bad machine. If a live CD session works properly, you could try to compare the outputs of, for example:env,locale,localectlorlocale charmap.
– Julen Larrucea
Mar 27 '17 at 16:51
The thing is my computer works normally most of times. This just happens from time to time, so it is hard to compare.
– ig343
Mar 28 '17 at 5:31
It sounds like a tricky problem. Maybe you could make a script that outputs all the related information and save it into a file (including all commands above). Then run it again when the problem reappears and make adiffor something with both files.
– Julen Larrucea
Mar 28 '17 at 7:53
add a comment |
It is definitely not physical. Yes, I have updated grub.
– ig343
Mar 26 '17 at 16:50
Have you tried booting from a live CD? I happen to have a similar problem right now and I am comparing settings between a good and a bad machine. If a live CD session works properly, you could try to compare the outputs of, for example:env,locale,localectlorlocale charmap.
– Julen Larrucea
Mar 27 '17 at 16:51
The thing is my computer works normally most of times. This just happens from time to time, so it is hard to compare.
– ig343
Mar 28 '17 at 5:31
It sounds like a tricky problem. Maybe you could make a script that outputs all the related information and save it into a file (including all commands above). Then run it again when the problem reappears and make adiffor something with both files.
– Julen Larrucea
Mar 28 '17 at 7:53
It is definitely not physical. Yes, I have updated grub.
– ig343
Mar 26 '17 at 16:50
It is definitely not physical. Yes, I have updated grub.
– ig343
Mar 26 '17 at 16:50
Have you tried booting from a live CD? I happen to have a similar problem right now and I am comparing settings between a good and a bad machine. If a live CD session works properly, you could try to compare the outputs of, for example:
env, locale, localectl or locale charmap.– Julen Larrucea
Mar 27 '17 at 16:51
Have you tried booting from a live CD? I happen to have a similar problem right now and I am comparing settings between a good and a bad machine. If a live CD session works properly, you could try to compare the outputs of, for example:
env, locale, localectl or locale charmap.– Julen Larrucea
Mar 27 '17 at 16:51
The thing is my computer works normally most of times. This just happens from time to time, so it is hard to compare.
– ig343
Mar 28 '17 at 5:31
The thing is my computer works normally most of times. This just happens from time to time, so it is hard to compare.
– ig343
Mar 28 '17 at 5:31
It sounds like a tricky problem. Maybe you could make a script that outputs all the related information and save it into a file (including all commands above). Then run it again when the problem reappears and make a
diff or something with both files.– Julen Larrucea
Mar 28 '17 at 7:53
It sounds like a tricky problem. Maybe you could make a script that outputs all the related information and save it into a file (including all commands above). Then run it again when the problem reappears and make a
diff or something with both files.– Julen Larrucea
Mar 28 '17 at 7:53
add a comment |
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f886593%2falt-f4-switches-to-tty4%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
Did you try the answer from the second post you linked?
– M. Becerra
Feb 23 '17 at 17:42
You might want to check out this question : askubuntu.com/questions/123493/screen-went-black
– Dimitri Markovich
Feb 23 '17 at 17:49
@M.Becerra I don't have the package console-cyrillic installed on my system.
– ig343
Feb 24 '17 at 3:39
3
@DimitriMarkovich I did not hit Ctrl+Alt+F4, I am absolutely sure it's Alt+F4 which is doing what Ctrl+Alt+F4 should do.
– ig343
Feb 24 '17 at 3:40
1
it seems related to a kernel upgrade, and it happens on other Linux distros: unix.stackexchange.com/questions/59949/…
– elias
Jul 10 '17 at 14:25