GDM Xorg launching behavior on 16.04 vs 18.04

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
2
down vote

favorite












I'm testing out Ubuntu 18.04 in preparation for it's launch to make sure certain software and configuration will still work on it when I upgrade, and i've noticed a discrepency in how GDM spawns GNOME/Xorg on 18.04 vs GDM or LightDM on 16.04.



On 16.04, whatever display is launched launches as a child process of the DM, so if I run systemctl stop lightdm (or gdm), Unity/Xorg dies with it. If I do the same on 18.04, GNOME sticks around, but GDM stops. Is there a setting to make GDM on 18.04 launch GNOME as a child process instead of (presumably) disowning it?



Thanks in advance!










share|improve this question

























    up vote
    2
    down vote

    favorite












    I'm testing out Ubuntu 18.04 in preparation for it's launch to make sure certain software and configuration will still work on it when I upgrade, and i've noticed a discrepency in how GDM spawns GNOME/Xorg on 18.04 vs GDM or LightDM on 16.04.



    On 16.04, whatever display is launched launches as a child process of the DM, so if I run systemctl stop lightdm (or gdm), Unity/Xorg dies with it. If I do the same on 18.04, GNOME sticks around, but GDM stops. Is there a setting to make GDM on 18.04 launch GNOME as a child process instead of (presumably) disowning it?



    Thanks in advance!










    share|improve this question























      up vote
      2
      down vote

      favorite









      up vote
      2
      down vote

      favorite











      I'm testing out Ubuntu 18.04 in preparation for it's launch to make sure certain software and configuration will still work on it when I upgrade, and i've noticed a discrepency in how GDM spawns GNOME/Xorg on 18.04 vs GDM or LightDM on 16.04.



      On 16.04, whatever display is launched launches as a child process of the DM, so if I run systemctl stop lightdm (or gdm), Unity/Xorg dies with it. If I do the same on 18.04, GNOME sticks around, but GDM stops. Is there a setting to make GDM on 18.04 launch GNOME as a child process instead of (presumably) disowning it?



      Thanks in advance!










      share|improve this question













      I'm testing out Ubuntu 18.04 in preparation for it's launch to make sure certain software and configuration will still work on it when I upgrade, and i've noticed a discrepency in how GDM spawns GNOME/Xorg on 18.04 vs GDM or LightDM on 16.04.



      On 16.04, whatever display is launched launches as a child process of the DM, so if I run systemctl stop lightdm (or gdm), Unity/Xorg dies with it. If I do the same on 18.04, GNOME sticks around, but GDM stops. Is there a setting to make GDM on 18.04 launch GNOME as a child process instead of (presumably) disowning it?



      Thanks in advance!







      gnome xorg lightdm gdm 18.04






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 20 at 13:41









      zwater

      113




      113

























          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',
          convertImagesToLinks: true,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          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%2f1017632%2fgdm-xorg-launching-behavior-on-16-04-vs-18-04%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1017632%2fgdm-xorg-launching-behavior-on-16-04-vs-18-04%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          pylint3 and pip3 broken

          Missing snmpget and snmpwalk

          How to enroll fingerprints to Ubuntu 17.10 with VFS491