GNOME 3 autologout => gdm fails to restart X server












0















My O/S is CentOS 7.6 with all updates as of today.



I have a system where many users log in and run GNOME sessions via VNC (xrdp). I do not want idle sessions hanging around forever, so I followed the instructions for enabling automatic logout.



GNOME version



Redhat version



Both sets of instructions are the same: Create /etc/dconf/db/local.d/00-autologout; set the sleep-inactive-ac-timeout and sleep-inactive-ac-type keys in the [org/gnome/settings-daemon/plugins/power] section; run dconf update.



I did this, setting the timeout to 604800 seconds (1 week). And it works!



Well, except for one thing. The X server on the local console exited one week later, and gdm did not restart it.



This has happened a few times on a few systems now, and only after I enabled the automatic logout mechanism, so I am very certain it is responsible.



The last few lines of my /var/log/gdm/:0.log file read:



AUDIT: Wed Feb 20 15:15:11 2019: 27188: client 15 disconnected
AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 6 disconnected
AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 6 connected from local host ( uid=42 gid=42 pid=28256 )
Auth name: MIT-MAGIC-COOKIE-1 ID: 804
AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 6 disconnected
[...more "client XX disconnected lines"...]
AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 14 disconnected
(II) evdev: HID 0557:2419: Close
(II) evdev: HID 0557:2419: Close
(II) evdev: Power Button: Close
(II) Server terminated successfully (0). Closing log file.


/var/log/Xorg.0.log is very similar. No errors; just a clean server shutdown.



ps shows that /usr/sbin/gdm is still running but has no child processes. The X server for :0 simply exited cleanly and never got restarted.



Logging in and out on the console by hand works fine. And everything is OK if I disable automatic logout, except then I don't have automatic logout.



I am not entirely sure what to try next. If gdm fails to restart the X server after it exits, is that a gdm bug by definition?










share|improve this question



























    0















    My O/S is CentOS 7.6 with all updates as of today.



    I have a system where many users log in and run GNOME sessions via VNC (xrdp). I do not want idle sessions hanging around forever, so I followed the instructions for enabling automatic logout.



    GNOME version



    Redhat version



    Both sets of instructions are the same: Create /etc/dconf/db/local.d/00-autologout; set the sleep-inactive-ac-timeout and sleep-inactive-ac-type keys in the [org/gnome/settings-daemon/plugins/power] section; run dconf update.



    I did this, setting the timeout to 604800 seconds (1 week). And it works!



    Well, except for one thing. The X server on the local console exited one week later, and gdm did not restart it.



    This has happened a few times on a few systems now, and only after I enabled the automatic logout mechanism, so I am very certain it is responsible.



    The last few lines of my /var/log/gdm/:0.log file read:



    AUDIT: Wed Feb 20 15:15:11 2019: 27188: client 15 disconnected
    AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 6 disconnected
    AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 6 connected from local host ( uid=42 gid=42 pid=28256 )
    Auth name: MIT-MAGIC-COOKIE-1 ID: 804
    AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 6 disconnected
    [...more "client XX disconnected lines"...]
    AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 14 disconnected
    (II) evdev: HID 0557:2419: Close
    (II) evdev: HID 0557:2419: Close
    (II) evdev: Power Button: Close
    (II) Server terminated successfully (0). Closing log file.


    /var/log/Xorg.0.log is very similar. No errors; just a clean server shutdown.



    ps shows that /usr/sbin/gdm is still running but has no child processes. The X server for :0 simply exited cleanly and never got restarted.



    Logging in and out on the console by hand works fine. And everything is OK if I disable automatic logout, except then I don't have automatic logout.



    I am not entirely sure what to try next. If gdm fails to restart the X server after it exits, is that a gdm bug by definition?










    share|improve this question

























      0












      0








      0








      My O/S is CentOS 7.6 with all updates as of today.



      I have a system where many users log in and run GNOME sessions via VNC (xrdp). I do not want idle sessions hanging around forever, so I followed the instructions for enabling automatic logout.



      GNOME version



      Redhat version



      Both sets of instructions are the same: Create /etc/dconf/db/local.d/00-autologout; set the sleep-inactive-ac-timeout and sleep-inactive-ac-type keys in the [org/gnome/settings-daemon/plugins/power] section; run dconf update.



      I did this, setting the timeout to 604800 seconds (1 week). And it works!



      Well, except for one thing. The X server on the local console exited one week later, and gdm did not restart it.



      This has happened a few times on a few systems now, and only after I enabled the automatic logout mechanism, so I am very certain it is responsible.



      The last few lines of my /var/log/gdm/:0.log file read:



      AUDIT: Wed Feb 20 15:15:11 2019: 27188: client 15 disconnected
      AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 6 disconnected
      AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 6 connected from local host ( uid=42 gid=42 pid=28256 )
      Auth name: MIT-MAGIC-COOKIE-1 ID: 804
      AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 6 disconnected
      [...more "client XX disconnected lines"...]
      AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 14 disconnected
      (II) evdev: HID 0557:2419: Close
      (II) evdev: HID 0557:2419: Close
      (II) evdev: Power Button: Close
      (II) Server terminated successfully (0). Closing log file.


      /var/log/Xorg.0.log is very similar. No errors; just a clean server shutdown.



      ps shows that /usr/sbin/gdm is still running but has no child processes. The X server for :0 simply exited cleanly and never got restarted.



      Logging in and out on the console by hand works fine. And everything is OK if I disable automatic logout, except then I don't have automatic logout.



      I am not entirely sure what to try next. If gdm fails to restart the X server after it exits, is that a gdm bug by definition?










      share|improve this question














      My O/S is CentOS 7.6 with all updates as of today.



      I have a system where many users log in and run GNOME sessions via VNC (xrdp). I do not want idle sessions hanging around forever, so I followed the instructions for enabling automatic logout.



      GNOME version



      Redhat version



      Both sets of instructions are the same: Create /etc/dconf/db/local.d/00-autologout; set the sleep-inactive-ac-timeout and sleep-inactive-ac-type keys in the [org/gnome/settings-daemon/plugins/power] section; run dconf update.



      I did this, setting the timeout to 604800 seconds (1 week). And it works!



      Well, except for one thing. The X server on the local console exited one week later, and gdm did not restart it.



      This has happened a few times on a few systems now, and only after I enabled the automatic logout mechanism, so I am very certain it is responsible.



      The last few lines of my /var/log/gdm/:0.log file read:



      AUDIT: Wed Feb 20 15:15:11 2019: 27188: client 15 disconnected
      AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 6 disconnected
      AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 6 connected from local host ( uid=42 gid=42 pid=28256 )
      Auth name: MIT-MAGIC-COOKIE-1 ID: 804
      AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 6 disconnected
      [...more "client XX disconnected lines"...]
      AUDIT: Mon Feb 25 20:56:28 2019: 27188: client 14 disconnected
      (II) evdev: HID 0557:2419: Close
      (II) evdev: HID 0557:2419: Close
      (II) evdev: Power Button: Close
      (II) Server terminated successfully (0). Closing log file.


      /var/log/Xorg.0.log is very similar. No errors; just a clean server shutdown.



      ps shows that /usr/sbin/gdm is still running but has no child processes. The X server for :0 simply exited cleanly and never got restarted.



      Logging in and out on the console by hand works fine. And everything is OK if I disable automatic logout, except then I don't have automatic logout.



      I am not entirely sure what to try next. If gdm fails to restart the X server after it exits, is that a gdm bug by definition?







      centos gnome gnome3 gdm






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 4 hours ago









      NemoNemo

      96456




      96456






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          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: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          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%2funix.stackexchange.com%2fquestions%2f507592%2fgnome-3-autologout-gdm-fails-to-restart-x-server%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
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • 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%2funix.stackexchange.com%2fquestions%2f507592%2fgnome-3-autologout-gdm-fails-to-restart-x-server%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

          Accessing regular linux commands in Huawei's Dopra Linux

          Can't connect RFCOMM socket: Host is down

          Kernel panic - not syncing: Fatal Exception in Interrupt