Ubuntu 18.04 LTS: Attempting to change lid close action to “hibernate” broke everythinig
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have an Ubuntu 18.04 LTS laptop that dual-boots with Windows 10. I was fed up with all of my programs quitting every time I close the lid, so I attempted to change the lid close action to "hibernate," like my Windows side does. I followed the guide here: http://tipsonubuntu.com/2018/04/28/change-lid-close-action-ubuntu-18-04-lts/
Immediately after running the Systemd restart command, I was kicked to the login screen, and was unable to login again: I kept returning to the login screen after each attempt. When I powered off the laptop and attempted to boot, Ubuntu entered emergency mode. I thought perhaps reverting my changes in /etc/systemd/logind.conf would fix the issue, but it still persists. Does anyone know how I can make my computer work properly again? I can provide any additional information necessary.
power-management hibernate recovery-mode
|
show 10 more comments
I have an Ubuntu 18.04 LTS laptop that dual-boots with Windows 10. I was fed up with all of my programs quitting every time I close the lid, so I attempted to change the lid close action to "hibernate," like my Windows side does. I followed the guide here: http://tipsonubuntu.com/2018/04/28/change-lid-close-action-ubuntu-18-04-lts/
Immediately after running the Systemd restart command, I was kicked to the login screen, and was unable to login again: I kept returning to the login screen after each attempt. When I powered off the laptop and attempted to boot, Ubuntu entered emergency mode. I thought perhaps reverting my changes in /etc/systemd/logind.conf would fix the issue, but it still persists. Does anyone know how I can make my computer work properly again? I can provide any additional information necessary.
power-management hibernate recovery-mode
Did you test hibernation prior to changing the lid close action?
– Charles Green
yesterday
I did not. This may have been stupid of me, but I assumed that it would work, given that hibernation works on the Windows side of my machine. I re-commented the line in logind.conf, though, and it didn't fix it.
– Fakename Bill
yesterday
1
Hibernate is tricky, and I recent;y have stopped using it because of repeated corruption of my hard drive. Try this - load up a live USB of Ubuntu, boot it on your computer and runfsck -f /dev/sdxx
to check the integrity of your disks.
– Charles Green
yesterday
I will do that. However, I should stress that I never actually attempted to hibernate Ubuntu at all. This problem started as soon as I ran the command to reload Systemd - it logged me out and wouldn't let me log in again, then went into emergency mode after I tried restarting.
– Fakename Bill
yesterday
K - I don't think that the changes to logind.conf should have caused an issue - I tried reloading as mentioned in the article once (for another purpose) but never again. Can you append your question with the text of/etc/systemd/logind.conf
?
– Charles Green
yesterday
|
show 10 more comments
I have an Ubuntu 18.04 LTS laptop that dual-boots with Windows 10. I was fed up with all of my programs quitting every time I close the lid, so I attempted to change the lid close action to "hibernate," like my Windows side does. I followed the guide here: http://tipsonubuntu.com/2018/04/28/change-lid-close-action-ubuntu-18-04-lts/
Immediately after running the Systemd restart command, I was kicked to the login screen, and was unable to login again: I kept returning to the login screen after each attempt. When I powered off the laptop and attempted to boot, Ubuntu entered emergency mode. I thought perhaps reverting my changes in /etc/systemd/logind.conf would fix the issue, but it still persists. Does anyone know how I can make my computer work properly again? I can provide any additional information necessary.
power-management hibernate recovery-mode
I have an Ubuntu 18.04 LTS laptop that dual-boots with Windows 10. I was fed up with all of my programs quitting every time I close the lid, so I attempted to change the lid close action to "hibernate," like my Windows side does. I followed the guide here: http://tipsonubuntu.com/2018/04/28/change-lid-close-action-ubuntu-18-04-lts/
Immediately after running the Systemd restart command, I was kicked to the login screen, and was unable to login again: I kept returning to the login screen after each attempt. When I powered off the laptop and attempted to boot, Ubuntu entered emergency mode. I thought perhaps reverting my changes in /etc/systemd/logind.conf would fix the issue, but it still persists. Does anyone know how I can make my computer work properly again? I can provide any additional information necessary.
power-management hibernate recovery-mode
power-management hibernate recovery-mode
edited yesterday
Fakename Bill
asked yesterday
Fakename BillFakename Bill
114
114
Did you test hibernation prior to changing the lid close action?
– Charles Green
yesterday
I did not. This may have been stupid of me, but I assumed that it would work, given that hibernation works on the Windows side of my machine. I re-commented the line in logind.conf, though, and it didn't fix it.
– Fakename Bill
yesterday
1
Hibernate is tricky, and I recent;y have stopped using it because of repeated corruption of my hard drive. Try this - load up a live USB of Ubuntu, boot it on your computer and runfsck -f /dev/sdxx
to check the integrity of your disks.
– Charles Green
yesterday
I will do that. However, I should stress that I never actually attempted to hibernate Ubuntu at all. This problem started as soon as I ran the command to reload Systemd - it logged me out and wouldn't let me log in again, then went into emergency mode after I tried restarting.
– Fakename Bill
yesterday
K - I don't think that the changes to logind.conf should have caused an issue - I tried reloading as mentioned in the article once (for another purpose) but never again. Can you append your question with the text of/etc/systemd/logind.conf
?
– Charles Green
yesterday
|
show 10 more comments
Did you test hibernation prior to changing the lid close action?
– Charles Green
yesterday
I did not. This may have been stupid of me, but I assumed that it would work, given that hibernation works on the Windows side of my machine. I re-commented the line in logind.conf, though, and it didn't fix it.
– Fakename Bill
yesterday
1
Hibernate is tricky, and I recent;y have stopped using it because of repeated corruption of my hard drive. Try this - load up a live USB of Ubuntu, boot it on your computer and runfsck -f /dev/sdxx
to check the integrity of your disks.
– Charles Green
yesterday
I will do that. However, I should stress that I never actually attempted to hibernate Ubuntu at all. This problem started as soon as I ran the command to reload Systemd - it logged me out and wouldn't let me log in again, then went into emergency mode after I tried restarting.
– Fakename Bill
yesterday
K - I don't think that the changes to logind.conf should have caused an issue - I tried reloading as mentioned in the article once (for another purpose) but never again. Can you append your question with the text of/etc/systemd/logind.conf
?
– Charles Green
yesterday
Did you test hibernation prior to changing the lid close action?
– Charles Green
yesterday
Did you test hibernation prior to changing the lid close action?
– Charles Green
yesterday
I did not. This may have been stupid of me, but I assumed that it would work, given that hibernation works on the Windows side of my machine. I re-commented the line in logind.conf, though, and it didn't fix it.
– Fakename Bill
yesterday
I did not. This may have been stupid of me, but I assumed that it would work, given that hibernation works on the Windows side of my machine. I re-commented the line in logind.conf, though, and it didn't fix it.
– Fakename Bill
yesterday
1
1
Hibernate is tricky, and I recent;y have stopped using it because of repeated corruption of my hard drive. Try this - load up a live USB of Ubuntu, boot it on your computer and run
fsck -f /dev/sdxx
to check the integrity of your disks.– Charles Green
yesterday
Hibernate is tricky, and I recent;y have stopped using it because of repeated corruption of my hard drive. Try this - load up a live USB of Ubuntu, boot it on your computer and run
fsck -f /dev/sdxx
to check the integrity of your disks.– Charles Green
yesterday
I will do that. However, I should stress that I never actually attempted to hibernate Ubuntu at all. This problem started as soon as I ran the command to reload Systemd - it logged me out and wouldn't let me log in again, then went into emergency mode after I tried restarting.
– Fakename Bill
yesterday
I will do that. However, I should stress that I never actually attempted to hibernate Ubuntu at all. This problem started as soon as I ran the command to reload Systemd - it logged me out and wouldn't let me log in again, then went into emergency mode after I tried restarting.
– Fakename Bill
yesterday
K - I don't think that the changes to logind.conf should have caused an issue - I tried reloading as mentioned in the article once (for another purpose) but never again. Can you append your question with the text of
/etc/systemd/logind.conf
?– Charles Green
yesterday
K - I don't think that the changes to logind.conf should have caused an issue - I tried reloading as mentioned in the article once (for another purpose) but never again. Can you append your question with the text of
/etc/systemd/logind.conf
?– Charles Green
yesterday
|
show 10 more comments
0
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',
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%2f1133055%2fubuntu-18-04-lts-attempting-to-change-lid-close-action-to-hibernate-broke-eve%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2f1133055%2fubuntu-18-04-lts-attempting-to-change-lid-close-action-to-hibernate-broke-eve%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 test hibernation prior to changing the lid close action?
– Charles Green
yesterday
I did not. This may have been stupid of me, but I assumed that it would work, given that hibernation works on the Windows side of my machine. I re-commented the line in logind.conf, though, and it didn't fix it.
– Fakename Bill
yesterday
1
Hibernate is tricky, and I recent;y have stopped using it because of repeated corruption of my hard drive. Try this - load up a live USB of Ubuntu, boot it on your computer and run
fsck -f /dev/sdxx
to check the integrity of your disks.– Charles Green
yesterday
I will do that. However, I should stress that I never actually attempted to hibernate Ubuntu at all. This problem started as soon as I ran the command to reload Systemd - it logged me out and wouldn't let me log in again, then went into emergency mode after I tried restarting.
– Fakename Bill
yesterday
K - I don't think that the changes to logind.conf should have caused an issue - I tried reloading as mentioned in the article once (for another purpose) but never again. Can you append your question with the text of
/etc/systemd/logind.conf
?– Charles Green
yesterday