I have to press Ctrl+Alt+F1 on new Ubuntu 18.10 install to unlock after sleep
I recently installed 18.10 on an old 4th gen Core i5 desktop and I'm seeing a peculiar issue with the sleep/wake behaviour. The computer sleeps normally, but everytime I wake it, the screen isn't the login window, rather it is, what I can only assume is a screenshot of when I put the computer to sleep. I cant' interact with it, it's just a frozen screen.
I found this question from a long time back, and tried the trick in there, press Ctrl + Alt + F1, and it works everytime.
I've decided to try out Ubuntu/Linux after a long macOS hiatus and so I'm not sure if the response to that question, reconfiguring the desktop manager is the correct answer. I have searched syslog for any intuitive errors, but didn't find anything. Hoping someone here has run into a similar issue and can help out.
suspend 18.10 wakeup
asked Nov 21 '18 at 2:28
chin7an
11
add a comment |
I recently installed 18.10 on an old 4th gen Core i5 desktop and I'm seeing a peculiar issue with the sleep/wake behaviour. The computer sleeps normally, but everytime I wake it, the screen isn't the login window, rather it is, what I can only assume is a screenshot of when I put the computer to sleep. I cant' interact with it, it's just a frozen screen.
I found this question from a long time back, and tried the trick in there, press Ctrl + Alt + F1, and it works everytime.
I've decided to try out Ubuntu/Linux after a long macOS hiatus and so I'm not sure if the response to that question, reconfiguring the desktop manager is the correct answer. I have searched syslog for any intuitive errors, but didn't find anything. Hoping someone here has run into a similar issue and can help out.
suspend 18.10 wakeup
asked Nov 21 '18 at 2:28
chin7an
11
I'd like to add one more observation, after this special wake operation, the favourites bar shortcuts won't work - Super + numbers. I have to restart the PC in order to get them to work again. Hopefully it's helpful.
– chin7an
Nov 21 '18 at 2:29
add a comment |
I recently installed 18.10 on an old 4th gen Core i5 desktop and I'm seeing a peculiar issue with the sleep/wake behaviour. The computer sleeps normally, but everytime I wake it, the screen isn't the login window, rather it is, what I can only assume is a screenshot of when I put the computer to sleep. I cant' interact with it, it's just a frozen screen.
I found this question from a long time back, and tried the trick in there, press Ctrl + Alt + F1, and it works everytime.
I've decided to try out Ubuntu/Linux after a long macOS hiatus and so I'm not sure if the response to that question, reconfiguring the desktop manager is the correct answer. I have searched syslog for any intuitive errors, but didn't find anything. Hoping someone here has run into a similar issue and can help out.
suspend 18.10 wakeup
asked Nov 21 '18 at 2:28
chin7an
11
I recently installed 18.10 on an old 4th gen Core i5 desktop and I'm seeing a peculiar issue with the sleep/wake behaviour. The computer sleeps normally, but everytime I wake it, the screen isn't the login window, rather it is, what I can only assume is a screenshot of when I put the computer to sleep. I cant' interact with it, it's just a frozen screen.
I found this question from a long time back, and tried the trick in there, press Ctrl + Alt + F1, and it works everytime.
I've decided to try out Ubuntu/Linux after a long macOS hiatus and so I'm not sure if the response to that question, reconfiguring the desktop manager is the correct answer. I have searched syslog for any intuitive errors, but didn't find anything. Hoping someone here has run into a similar issue and can help out.
suspend 18.10 wakeup
suspend 18.10 wakeup
asked Nov 21 '18 at 2:28
chin7an
11
asked Nov 21 '18 at 2:28
chin7an
11
asked Nov 21 '18 at 2:28
chin7an
11
asked Nov 21 '18 at 2:28
chin7an
11
asked Nov 21 '18 at 2:28
chin7an
11
11
I'd like to add one more observation, after this special wake operation, the favourites bar shortcuts won't work - Super + numbers. I have to restart the PC in order to get them to work again. Hopefully it's helpful.
– chin7an
Nov 21 '18 at 2:29
add a comment |
I'd like to add one more observation, after this special wake operation, the favourites bar shortcuts won't work - Super + numbers. I have to restart the PC in order to get them to work again. Hopefully it's helpful.
– chin7an
Nov 21 '18 at 2:29
I'd like to add one more observation, after this special wake operation, the favourites bar shortcuts won't work - Super + numbers. I have to restart the PC in order to get them to work again. Hopefully it's helpful.
– chin7an
Nov 21 '18 at 2:29
I'd like to add one more observation, after this special wake operation, the favourites bar shortcuts won't work - Super + numbers. I have to restart the PC in order to get them to work again. Hopefully it's helpful.
– chin7an
Nov 21 '18 at 2:29
add a comment |
2 Answers
2
active
oldest
votes
I figured out what I was doing wrong. I used Alt to suspend the computer, which apparently causes the strange behaviour. The correct way is to long-click the shut-off button, which changes it to the suspend button.
I have a follow-up question to ask for help understanding the behaviour with the Alt key here - What does pressing Alt do when suspending the computer?
answered Dec 2 '18 at 0:27
chin7an
11
add a comment |
I doubt pressing Alt to suspend is the issue, I tried both and I can see very the same output. After resuming I am on wrong screen and I need to still switch to Screen 1 with Ctrl+Alt+F1 keys.
Pressing Alt and keeping pressed Power button should do the same.
edited Dec 31 '18 at 9:45
Thomas
3,55381427
answered Dec 31 '18 at 9:00
MarekN
1
New contributor
MarekN is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I solved the issue on my local desktop by uninstalling all gnome-shell extensions in my~/.local/share/gnome-shell/extensions/, which are not installed from deb packages and also removedgnome-shell-extension-appindicatorpackage
– MarekN
Jan 3 at 10:51
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%2f1094679%2fi-have-to-press-ctrlaltf1-on-new-ubuntu-18-10-install-to-unlock-after-sleep%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 figured out what I was doing wrong. I used Alt to suspend the computer, which apparently causes the strange behaviour. The correct way is to long-click the shut-off button, which changes it to the suspend button.
I have a follow-up question to ask for help understanding the behaviour with the Alt key here - What does pressing Alt do when suspending the computer?
answered Dec 2 '18 at 0:27
chin7an
11
add a comment |
I figured out what I was doing wrong. I used Alt to suspend the computer, which apparently causes the strange behaviour. The correct way is to long-click the shut-off button, which changes it to the suspend button.
I have a follow-up question to ask for help understanding the behaviour with the Alt key here - What does pressing Alt do when suspending the computer?
answered Dec 2 '18 at 0:27
chin7an
11
add a comment |
I figured out what I was doing wrong. I used Alt to suspend the computer, which apparently causes the strange behaviour. The correct way is to long-click the shut-off button, which changes it to the suspend button.
I have a follow-up question to ask for help understanding the behaviour with the Alt key here - What does pressing Alt do when suspending the computer?
answered Dec 2 '18 at 0:27
chin7an
11
I figured out what I was doing wrong. I used Alt to suspend the computer, which apparently causes the strange behaviour. The correct way is to long-click the shut-off button, which changes it to the suspend button.
I have a follow-up question to ask for help understanding the behaviour with the Alt key here - What does pressing Alt do when suspending the computer?
answered Dec 2 '18 at 0:27
chin7an
11
answered Dec 2 '18 at 0:27
chin7an
11
answered Dec 2 '18 at 0:27
chin7an
11
answered Dec 2 '18 at 0:27
chin7an
11
11
add a comment |
add a comment |
I doubt pressing Alt to suspend is the issue, I tried both and I can see very the same output. After resuming I am on wrong screen and I need to still switch to Screen 1 with Ctrl+Alt+F1 keys.
Pressing Alt and keeping pressed Power button should do the same.
edited Dec 31 '18 at 9:45
Thomas
3,55381427
answered Dec 31 '18 at 9:00
MarekN
1
New contributor
MarekN is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I solved the issue on my local desktop by uninstalling all gnome-shell extensions in my~/.local/share/gnome-shell/extensions/, which are not installed from deb packages and also removedgnome-shell-extension-appindicatorpackage
– MarekN
Jan 3 at 10:51
add a comment |
I doubt pressing Alt to suspend is the issue, I tried both and I can see very the same output. After resuming I am on wrong screen and I need to still switch to Screen 1 with Ctrl+Alt+F1 keys.
Pressing Alt and keeping pressed Power button should do the same.
edited Dec 31 '18 at 9:45
Thomas
3,55381427
answered Dec 31 '18 at 9:00
MarekN
1
New contributor
MarekN is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I solved the issue on my local desktop by uninstalling all gnome-shell extensions in my~/.local/share/gnome-shell/extensions/, which are not installed from deb packages and also removedgnome-shell-extension-appindicatorpackage
– MarekN
Jan 3 at 10:51
add a comment |
I doubt pressing Alt to suspend is the issue, I tried both and I can see very the same output. After resuming I am on wrong screen and I need to still switch to Screen 1 with Ctrl+Alt+F1 keys.
Pressing Alt and keeping pressed Power button should do the same.
edited Dec 31 '18 at 9:45
Thomas
3,55381427
answered Dec 31 '18 at 9:00
MarekN
1
New contributor
MarekN is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I doubt pressing Alt to suspend is the issue, I tried both and I can see very the same output. After resuming I am on wrong screen and I need to still switch to Screen 1 with Ctrl+Alt+F1 keys.
Pressing Alt and keeping pressed Power button should do the same.
edited Dec 31 '18 at 9:45
Thomas
3,55381427
answered Dec 31 '18 at 9:00
MarekN
1
New contributor
MarekN is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Dec 31 '18 at 9:45
Thomas
3,55381427
edited Dec 31 '18 at 9:45
Thomas
3,55381427
edited Dec 31 '18 at 9:45
Thomas
3,55381427
3,55381427
answered Dec 31 '18 at 9:00
MarekN
1
New contributor
MarekN is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Dec 31 '18 at 9:00
MarekN
1
answered Dec 31 '18 at 9:00
MarekN
1
1
New contributor
MarekN is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
MarekN is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
MarekN is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I solved the issue on my local desktop by uninstalling all gnome-shell extensions in my~/.local/share/gnome-shell/extensions/, which are not installed from deb packages and also removedgnome-shell-extension-appindicatorpackage
– MarekN
Jan 3 at 10:51
add a comment |
I solved the issue on my local desktop by uninstalling all gnome-shell extensions in my~/.local/share/gnome-shell/extensions/, which are not installed from deb packages and also removedgnome-shell-extension-appindicatorpackage
– MarekN
Jan 3 at 10:51
I solved the issue on my local desktop by uninstalling all gnome-shell extensions in my
~/.local/share/gnome-shell/extensions/, which are not installed from deb packages and also removed gnome-shell-extension-appindicator package– MarekN
Jan 3 at 10:51
I solved the issue on my local desktop by uninstalling all gnome-shell extensions in my
~/.local/share/gnome-shell/extensions/, which are not installed from deb packages and also removed gnome-shell-extension-appindicator package– MarekN
Jan 3 at 10:51
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%2f1094679%2fi-have-to-press-ctrlaltf1-on-new-ubuntu-18-10-install-to-unlock-after-sleep%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
I'd like to add one more observation, after this special wake operation, the favourites bar shortcuts won't work - Super + numbers. I have to restart the PC in order to get them to work again. Hopefully it's helpful.
– chin7an
Nov 21 '18 at 2:29