Can not switch to TTY - frozen desktop is shown instead

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
3
down vote

favorite












On one machine (Dell Latitude E7440) running Ubuntu 16.04, when I try to switch to a TTY (e.g. using Ctrl+Alt+F1 or sudo chvt 1), nothing happens.



I keep seeing the last state of my graphical desktop instead of a TTY terminal login, although it is frozen and not accepting any input. Switching back to TTY7 using Ctrl+Alt+F7 brings the desktop back to life as expected.



Why can I not switch to a TTY terminal on this system? How can I diagnose and fix the issue?



$ lspci -k | grep -iEA4 '3d|vga|display'
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
DeviceName: Onboard IGD
Subsystem: Dell Haswell-ULT Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915









share|improve this question



















  • 1




    Does this laptop have a graphics card?
    – muru
    Jan 29 at 9:19










  • @muru No, only the integrated Intel Haswell graphics. Added the lspci -k output to my question.
    – Byte Commander
    Jan 29 at 9:25










  • Have you solved the problem? I've got a similar situation, instead of getting into the tty what I see is the log of startx command that has been run on the tty which X is running, most of the times I can't even return to my working tty and I have to reboot. Haswell here too.
    – Ravexina
    Apr 3 at 10:51







  • 1




    @Ravexina Nope, no news from my side. But strangely, currently it works. Maybe it was related to the docking station I used? Don't have access to it currently though, so can't verify that...
    – Byte Commander
    Apr 3 at 11:02














up vote
3
down vote

favorite












On one machine (Dell Latitude E7440) running Ubuntu 16.04, when I try to switch to a TTY (e.g. using Ctrl+Alt+F1 or sudo chvt 1), nothing happens.



I keep seeing the last state of my graphical desktop instead of a TTY terminal login, although it is frozen and not accepting any input. Switching back to TTY7 using Ctrl+Alt+F7 brings the desktop back to life as expected.



Why can I not switch to a TTY terminal on this system? How can I diagnose and fix the issue?



$ lspci -k | grep -iEA4 '3d|vga|display'
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
DeviceName: Onboard IGD
Subsystem: Dell Haswell-ULT Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915









share|improve this question



















  • 1




    Does this laptop have a graphics card?
    – muru
    Jan 29 at 9:19










  • @muru No, only the integrated Intel Haswell graphics. Added the lspci -k output to my question.
    – Byte Commander
    Jan 29 at 9:25










  • Have you solved the problem? I've got a similar situation, instead of getting into the tty what I see is the log of startx command that has been run on the tty which X is running, most of the times I can't even return to my working tty and I have to reboot. Haswell here too.
    – Ravexina
    Apr 3 at 10:51







  • 1




    @Ravexina Nope, no news from my side. But strangely, currently it works. Maybe it was related to the docking station I used? Don't have access to it currently though, so can't verify that...
    – Byte Commander
    Apr 3 at 11:02












up vote
3
down vote

favorite









up vote
3
down vote

favorite











On one machine (Dell Latitude E7440) running Ubuntu 16.04, when I try to switch to a TTY (e.g. using Ctrl+Alt+F1 or sudo chvt 1), nothing happens.



I keep seeing the last state of my graphical desktop instead of a TTY terminal login, although it is frozen and not accepting any input. Switching back to TTY7 using Ctrl+Alt+F7 brings the desktop back to life as expected.



Why can I not switch to a TTY terminal on this system? How can I diagnose and fix the issue?



$ lspci -k | grep -iEA4 '3d|vga|display'
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
DeviceName: Onboard IGD
Subsystem: Dell Haswell-ULT Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915









share|improve this question















On one machine (Dell Latitude E7440) running Ubuntu 16.04, when I try to switch to a TTY (e.g. using Ctrl+Alt+F1 or sudo chvt 1), nothing happens.



I keep seeing the last state of my graphical desktop instead of a TTY terminal login, although it is frozen and not accepting any input. Switching back to TTY7 using Ctrl+Alt+F7 brings the desktop back to life as expected.



Why can I not switch to a TTY terminal on this system? How can I diagnose and fix the issue?



$ lspci -k | grep -iEA4 '3d|vga|display'
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
DeviceName: Onboard IGD
Subsystem: Dell Haswell-ULT Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915






16.04 dell tty






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 29 at 9:26

























asked Jan 29 at 9:01









Byte Commander

60k26159270




60k26159270







  • 1




    Does this laptop have a graphics card?
    – muru
    Jan 29 at 9:19










  • @muru No, only the integrated Intel Haswell graphics. Added the lspci -k output to my question.
    – Byte Commander
    Jan 29 at 9:25










  • Have you solved the problem? I've got a similar situation, instead of getting into the tty what I see is the log of startx command that has been run on the tty which X is running, most of the times I can't even return to my working tty and I have to reboot. Haswell here too.
    – Ravexina
    Apr 3 at 10:51







  • 1




    @Ravexina Nope, no news from my side. But strangely, currently it works. Maybe it was related to the docking station I used? Don't have access to it currently though, so can't verify that...
    – Byte Commander
    Apr 3 at 11:02












  • 1




    Does this laptop have a graphics card?
    – muru
    Jan 29 at 9:19










  • @muru No, only the integrated Intel Haswell graphics. Added the lspci -k output to my question.
    – Byte Commander
    Jan 29 at 9:25










  • Have you solved the problem? I've got a similar situation, instead of getting into the tty what I see is the log of startx command that has been run on the tty which X is running, most of the times I can't even return to my working tty and I have to reboot. Haswell here too.
    – Ravexina
    Apr 3 at 10:51







  • 1




    @Ravexina Nope, no news from my side. But strangely, currently it works. Maybe it was related to the docking station I used? Don't have access to it currently though, so can't verify that...
    – Byte Commander
    Apr 3 at 11:02







1




1




Does this laptop have a graphics card?
– muru
Jan 29 at 9:19




Does this laptop have a graphics card?
– muru
Jan 29 at 9:19












@muru No, only the integrated Intel Haswell graphics. Added the lspci -k output to my question.
– Byte Commander
Jan 29 at 9:25




@muru No, only the integrated Intel Haswell graphics. Added the lspci -k output to my question.
– Byte Commander
Jan 29 at 9:25












Have you solved the problem? I've got a similar situation, instead of getting into the tty what I see is the log of startx command that has been run on the tty which X is running, most of the times I can't even return to my working tty and I have to reboot. Haswell here too.
– Ravexina
Apr 3 at 10:51





Have you solved the problem? I've got a similar situation, instead of getting into the tty what I see is the log of startx command that has been run on the tty which X is running, most of the times I can't even return to my working tty and I have to reboot. Haswell here too.
– Ravexina
Apr 3 at 10:51





1




1




@Ravexina Nope, no news from my side. But strangely, currently it works. Maybe it was related to the docking station I used? Don't have access to it currently though, so can't verify that...
– Byte Commander
Apr 3 at 11:02




@Ravexina Nope, no news from my side. But strangely, currently it works. Maybe it was related to the docking station I used? Don't have access to it currently though, so can't verify that...
– Byte Commander
Apr 3 at 11:02















active

oldest

votes











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',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1000919%2fcan-not-switch-to-tty-frozen-desktop-is-shown-instead%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1000919%2fcan-not-switch-to-tty-frozen-desktop-is-shown-instead%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491