Login after suspend taking an increasingly long time - 18.10











up vote
0
down vote

favorite












I have a Thinkpad X1 Carbon (4th gen) that I recently updated to 18.10. Ever since the update, I've had issues with resume after suspend. The biggest is that it takes a long time for the login screen to appear, and the time seems to increase after each suspend-resume cycle.



I took a look at /var/log/syslog and I'm seeing a bunch of entries like:



Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:68
Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:65
Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 226:0
Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:66
Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:72
Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:69
Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:67









share|improve this question


























    up vote
    0
    down vote

    favorite












    I have a Thinkpad X1 Carbon (4th gen) that I recently updated to 18.10. Ever since the update, I've had issues with resume after suspend. The biggest is that it takes a long time for the login screen to appear, and the time seems to increase after each suspend-resume cycle.



    I took a look at /var/log/syslog and I'm seeing a bunch of entries like:



    Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:68
    Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:65
    Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 226:0
    Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:66
    Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:72
    Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:69
    Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:67









    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have a Thinkpad X1 Carbon (4th gen) that I recently updated to 18.10. Ever since the update, I've had issues with resume after suspend. The biggest is that it takes a long time for the login screen to appear, and the time seems to increase after each suspend-resume cycle.



      I took a look at /var/log/syslog and I'm seeing a bunch of entries like:



      Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:68
      Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:65
      Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 226:0
      Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:66
      Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:72
      Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:69
      Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:67









      share|improve this question













      I have a Thinkpad X1 Carbon (4th gen) that I recently updated to 18.10. Ever since the update, I've had issues with resume after suspend. The biggest is that it takes a long time for the login screen to appear, and the time seems to increase after each suspend-resume cycle.



      I took a look at /var/log/syslog and I'm seeing a bunch of entries like:



      Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:68
      Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:65
      Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 226:0
      Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:66
      Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:72
      Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:69
      Nov 25 14:38:18 jeremy-thinkpad /usr/lib/gdm3/gdm-x-session[2867]: (II) systemd-logind: got pause for 13:67






      suspend thinkpad 18.10






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 3 at 13:53









      Jeremy

      183414




      183414






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          Try with sudo ln -s /usr/lib/systemd/system/gdm.service /etc/systemd/system/display-manager.service --force, this could fix it.






          share|improve this answer





















          • The file /usr/lib/systemd/system/gdm.service doesn't exist (in fact, the whole system directory doesn't exist
            – Jeremy
            Dec 3 at 16:57











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


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1098157%2flogin-after-suspend-taking-an-increasingly-long-time-18-10%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













          Try with sudo ln -s /usr/lib/systemd/system/gdm.service /etc/systemd/system/display-manager.service --force, this could fix it.






          share|improve this answer





















          • The file /usr/lib/systemd/system/gdm.service doesn't exist (in fact, the whole system directory doesn't exist
            – Jeremy
            Dec 3 at 16:57















          up vote
          0
          down vote













          Try with sudo ln -s /usr/lib/systemd/system/gdm.service /etc/systemd/system/display-manager.service --force, this could fix it.






          share|improve this answer





















          • The file /usr/lib/systemd/system/gdm.service doesn't exist (in fact, the whole system directory doesn't exist
            – Jeremy
            Dec 3 at 16:57













          up vote
          0
          down vote










          up vote
          0
          down vote









          Try with sudo ln -s /usr/lib/systemd/system/gdm.service /etc/systemd/system/display-manager.service --force, this could fix it.






          share|improve this answer












          Try with sudo ln -s /usr/lib/systemd/system/gdm.service /etc/systemd/system/display-manager.service --force, this could fix it.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Dec 3 at 14:18









          Federico

          1




          1












          • The file /usr/lib/systemd/system/gdm.service doesn't exist (in fact, the whole system directory doesn't exist
            – Jeremy
            Dec 3 at 16:57


















          • The file /usr/lib/systemd/system/gdm.service doesn't exist (in fact, the whole system directory doesn't exist
            – Jeremy
            Dec 3 at 16:57
















          The file /usr/lib/systemd/system/gdm.service doesn't exist (in fact, the whole system directory doesn't exist
          – Jeremy
          Dec 3 at 16:57




          The file /usr/lib/systemd/system/gdm.service doesn't exist (in fact, the whole system directory doesn't exist
          – Jeremy
          Dec 3 at 16:57


















          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.





          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%2f1098157%2flogin-after-suspend-taking-an-increasingly-long-time-18-10%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

          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

          Mangá

           ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕