No Suspend on lid close











up vote
0
down vote

favorite












I recently noted that my Thinkpad X1 Yoga (1st Generation) will not enter the suspend mode any more when I close the lid of the notebook.
I updated from Ubuntu 18.04.2 to 18.10 recently but I am not 100% sure if the error occured right after the update.
What I have checked:



(1) I checked that my /etc/default/grub was not changed since I last configured it:



GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


(2) I changed the /etc/default/grub following this hint (no effect):



GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_sleep=nonvs"


(3) I changed /etc/systemd/logind.conf to the following. I edited the Inhibit-entries to "yes" (no effect):



[Login]
HandlePowerKey=hibernate
HandleHibernateKey=hibernate
HandleSuspendKey=suspend-then-hibernate
HandleLidSwitch=suspend-then-hibernate
HandleLidSwitchDocked=suspend
PowerKeyIgnoreInhibited=yes
SuspendKeyIgnoreInhibited=yes
HibernateKeyIgnoreInhibited=yes
LidSwitchIgnoreInhibited=yes


(4) I thought about the sleep mode itself being broken. But executing sudo pm-suspend in terminal will correctly initiate the suspend mode. The screen is getting dark and the power LED is flashing after a few seconds.



(5) I checked if the lid sensor itself is broken. Since the Thinkpad uses a magetic sensor in the base and has a magnet in the lid, I tried to trigger the sensor with an external magnet. The sensor seems to work. When moving the magnet over the sensor, the screen turns black. But nothing else happens, the power LED is still on. When removing the magnet, the screen is on again.



(6) (update) I also tested sudo pm-suspend-hybrid to check if the hybrid suspend mode is broken. This was not the case. The machine entered the suspend mode as expected (screen black + Power led flashing



(update) free -h gives the following output:



           total        used        free      shared  buff/cache   available
Mem: 7,2Gi 1,7Gi 3,7Gi 674Mi 1,8Gi 4,6Gi
Swap: 9,0Gi 0B 9,0Gi


Do you have any more ideas how to get the suspend mode working again? I would like to trigger the new suspend-then-hibernate mode on lid close.










share|improve this question









New contributor




Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • And how is your RAM and with this update a lot could go wrong?
    – George Udosen
    Nov 25 at 18:05












  • I'm afraid i do not understand. I've got 8GB of RAM. An Idea: is it possible that the suspend ist working, but suspend-then-hibernate is not. Is there a terminal command which initiates the suspend-then-hibernate mode?
    – Donut
    2 days ago










  • Make sure your RAM isn't been used up And leaving nothing for hibernation. Check with free -h
    – George Udosen
    2 days ago










  • Original post edited: marked with (update)
    – Donut
    2 days ago















up vote
0
down vote

favorite












I recently noted that my Thinkpad X1 Yoga (1st Generation) will not enter the suspend mode any more when I close the lid of the notebook.
I updated from Ubuntu 18.04.2 to 18.10 recently but I am not 100% sure if the error occured right after the update.
What I have checked:



(1) I checked that my /etc/default/grub was not changed since I last configured it:



GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


(2) I changed the /etc/default/grub following this hint (no effect):



GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_sleep=nonvs"


(3) I changed /etc/systemd/logind.conf to the following. I edited the Inhibit-entries to "yes" (no effect):



[Login]
HandlePowerKey=hibernate
HandleHibernateKey=hibernate
HandleSuspendKey=suspend-then-hibernate
HandleLidSwitch=suspend-then-hibernate
HandleLidSwitchDocked=suspend
PowerKeyIgnoreInhibited=yes
SuspendKeyIgnoreInhibited=yes
HibernateKeyIgnoreInhibited=yes
LidSwitchIgnoreInhibited=yes


(4) I thought about the sleep mode itself being broken. But executing sudo pm-suspend in terminal will correctly initiate the suspend mode. The screen is getting dark and the power LED is flashing after a few seconds.



(5) I checked if the lid sensor itself is broken. Since the Thinkpad uses a magetic sensor in the base and has a magnet in the lid, I tried to trigger the sensor with an external magnet. The sensor seems to work. When moving the magnet over the sensor, the screen turns black. But nothing else happens, the power LED is still on. When removing the magnet, the screen is on again.



(6) (update) I also tested sudo pm-suspend-hybrid to check if the hybrid suspend mode is broken. This was not the case. The machine entered the suspend mode as expected (screen black + Power led flashing



(update) free -h gives the following output:



           total        used        free      shared  buff/cache   available
Mem: 7,2Gi 1,7Gi 3,7Gi 674Mi 1,8Gi 4,6Gi
Swap: 9,0Gi 0B 9,0Gi


Do you have any more ideas how to get the suspend mode working again? I would like to trigger the new suspend-then-hibernate mode on lid close.










share|improve this question









New contributor




Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • And how is your RAM and with this update a lot could go wrong?
    – George Udosen
    Nov 25 at 18:05












  • I'm afraid i do not understand. I've got 8GB of RAM. An Idea: is it possible that the suspend ist working, but suspend-then-hibernate is not. Is there a terminal command which initiates the suspend-then-hibernate mode?
    – Donut
    2 days ago










  • Make sure your RAM isn't been used up And leaving nothing for hibernation. Check with free -h
    – George Udosen
    2 days ago










  • Original post edited: marked with (update)
    – Donut
    2 days ago













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I recently noted that my Thinkpad X1 Yoga (1st Generation) will not enter the suspend mode any more when I close the lid of the notebook.
I updated from Ubuntu 18.04.2 to 18.10 recently but I am not 100% sure if the error occured right after the update.
What I have checked:



(1) I checked that my /etc/default/grub was not changed since I last configured it:



GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


(2) I changed the /etc/default/grub following this hint (no effect):



GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_sleep=nonvs"


(3) I changed /etc/systemd/logind.conf to the following. I edited the Inhibit-entries to "yes" (no effect):



[Login]
HandlePowerKey=hibernate
HandleHibernateKey=hibernate
HandleSuspendKey=suspend-then-hibernate
HandleLidSwitch=suspend-then-hibernate
HandleLidSwitchDocked=suspend
PowerKeyIgnoreInhibited=yes
SuspendKeyIgnoreInhibited=yes
HibernateKeyIgnoreInhibited=yes
LidSwitchIgnoreInhibited=yes


(4) I thought about the sleep mode itself being broken. But executing sudo pm-suspend in terminal will correctly initiate the suspend mode. The screen is getting dark and the power LED is flashing after a few seconds.



(5) I checked if the lid sensor itself is broken. Since the Thinkpad uses a magetic sensor in the base and has a magnet in the lid, I tried to trigger the sensor with an external magnet. The sensor seems to work. When moving the magnet over the sensor, the screen turns black. But nothing else happens, the power LED is still on. When removing the magnet, the screen is on again.



(6) (update) I also tested sudo pm-suspend-hybrid to check if the hybrid suspend mode is broken. This was not the case. The machine entered the suspend mode as expected (screen black + Power led flashing



(update) free -h gives the following output:



           total        used        free      shared  buff/cache   available
Mem: 7,2Gi 1,7Gi 3,7Gi 674Mi 1,8Gi 4,6Gi
Swap: 9,0Gi 0B 9,0Gi


Do you have any more ideas how to get the suspend mode working again? I would like to trigger the new suspend-then-hibernate mode on lid close.










share|improve this question









New contributor




Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











I recently noted that my Thinkpad X1 Yoga (1st Generation) will not enter the suspend mode any more when I close the lid of the notebook.
I updated from Ubuntu 18.04.2 to 18.10 recently but I am not 100% sure if the error occured right after the update.
What I have checked:



(1) I checked that my /etc/default/grub was not changed since I last configured it:



GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


(2) I changed the /etc/default/grub following this hint (no effect):



GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_sleep=nonvs"


(3) I changed /etc/systemd/logind.conf to the following. I edited the Inhibit-entries to "yes" (no effect):



[Login]
HandlePowerKey=hibernate
HandleHibernateKey=hibernate
HandleSuspendKey=suspend-then-hibernate
HandleLidSwitch=suspend-then-hibernate
HandleLidSwitchDocked=suspend
PowerKeyIgnoreInhibited=yes
SuspendKeyIgnoreInhibited=yes
HibernateKeyIgnoreInhibited=yes
LidSwitchIgnoreInhibited=yes


(4) I thought about the sleep mode itself being broken. But executing sudo pm-suspend in terminal will correctly initiate the suspend mode. The screen is getting dark and the power LED is flashing after a few seconds.



(5) I checked if the lid sensor itself is broken. Since the Thinkpad uses a magetic sensor in the base and has a magnet in the lid, I tried to trigger the sensor with an external magnet. The sensor seems to work. When moving the magnet over the sensor, the screen turns black. But nothing else happens, the power LED is still on. When removing the magnet, the screen is on again.



(6) (update) I also tested sudo pm-suspend-hybrid to check if the hybrid suspend mode is broken. This was not the case. The machine entered the suspend mode as expected (screen black + Power led flashing



(update) free -h gives the following output:



           total        used        free      shared  buff/cache   available
Mem: 7,2Gi 1,7Gi 3,7Gi 674Mi 1,8Gi 4,6Gi
Swap: 9,0Gi 0B 9,0Gi


Do you have any more ideas how to get the suspend mode working again? I would like to trigger the new suspend-then-hibernate mode on lid close.







suspend power-management laptop 18.10






share|improve this question









New contributor




Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 2 days ago





















New contributor




Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Nov 25 at 17:59









Donut

12




12




New contributor




Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • And how is your RAM and with this update a lot could go wrong?
    – George Udosen
    Nov 25 at 18:05












  • I'm afraid i do not understand. I've got 8GB of RAM. An Idea: is it possible that the suspend ist working, but suspend-then-hibernate is not. Is there a terminal command which initiates the suspend-then-hibernate mode?
    – Donut
    2 days ago










  • Make sure your RAM isn't been used up And leaving nothing for hibernation. Check with free -h
    – George Udosen
    2 days ago










  • Original post edited: marked with (update)
    – Donut
    2 days ago


















  • And how is your RAM and with this update a lot could go wrong?
    – George Udosen
    Nov 25 at 18:05












  • I'm afraid i do not understand. I've got 8GB of RAM. An Idea: is it possible that the suspend ist working, but suspend-then-hibernate is not. Is there a terminal command which initiates the suspend-then-hibernate mode?
    – Donut
    2 days ago










  • Make sure your RAM isn't been used up And leaving nothing for hibernation. Check with free -h
    – George Udosen
    2 days ago










  • Original post edited: marked with (update)
    – Donut
    2 days ago
















And how is your RAM and with this update a lot could go wrong?
– George Udosen
Nov 25 at 18:05






And how is your RAM and with this update a lot could go wrong?
– George Udosen
Nov 25 at 18:05














I'm afraid i do not understand. I've got 8GB of RAM. An Idea: is it possible that the suspend ist working, but suspend-then-hibernate is not. Is there a terminal command which initiates the suspend-then-hibernate mode?
– Donut
2 days ago




I'm afraid i do not understand. I've got 8GB of RAM. An Idea: is it possible that the suspend ist working, but suspend-then-hibernate is not. Is there a terminal command which initiates the suspend-then-hibernate mode?
– Donut
2 days ago












Make sure your RAM isn't been used up And leaving nothing for hibernation. Check with free -h
– George Udosen
2 days ago




Make sure your RAM isn't been used up And leaving nothing for hibernation. Check with free -h
– George Udosen
2 days ago












Original post edited: marked with (update)
– Donut
2 days ago




Original post edited: marked with (update)
– Donut
2 days ago










1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










After performing another Core update for Ubuntu, it is working again.



It seems like there were modifications on the suspend mode or in one of the drivers. I checked the release notes for Ubuntu 18.10 and found nothing, but it looks like there were changes anyway.






share|improve this answer








New contributor




Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.


















    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: 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
    });


    }
    });






    Donut is a new contributor. Be nice, and check out our Code of Conduct.










    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1095969%2fno-suspend-on-lid-close%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote



    accepted










    After performing another Core update for Ubuntu, it is working again.



    It seems like there were modifications on the suspend mode or in one of the drivers. I checked the release notes for Ubuntu 18.10 and found nothing, but it looks like there were changes anyway.






    share|improve this answer








    New contributor




    Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.






















      up vote
      0
      down vote



      accepted










      After performing another Core update for Ubuntu, it is working again.



      It seems like there were modifications on the suspend mode or in one of the drivers. I checked the release notes for Ubuntu 18.10 and found nothing, but it looks like there were changes anyway.






      share|improve this answer








      New contributor




      Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




















        up vote
        0
        down vote



        accepted







        up vote
        0
        down vote



        accepted






        After performing another Core update for Ubuntu, it is working again.



        It seems like there were modifications on the suspend mode or in one of the drivers. I checked the release notes for Ubuntu 18.10 and found nothing, but it looks like there were changes anyway.






        share|improve this answer








        New contributor




        Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        After performing another Core update for Ubuntu, it is working again.



        It seems like there were modifications on the suspend mode or in one of the drivers. I checked the release notes for Ubuntu 18.10 and found nothing, but it looks like there were changes anyway.







        share|improve this answer








        New contributor




        Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 11 hours ago









        Donut

        12




        12




        New contributor




        Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        Donut is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






















            Donut is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            Donut is a new contributor. Be nice, and check out our Code of Conduct.













            Donut is a new contributor. Be nice, and check out our Code of Conduct.












            Donut is a new contributor. Be nice, and check out our Code of Conduct.
















            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1095969%2fno-suspend-on-lid-close%23new-answer', 'question_page');
            }
            );

            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







            Popular posts from this blog

            數位音樂下載

            When can things happen in Etherscan, such as the picture below?

            格利澤436b