18.04: How to get Wayland back after upgrade to 18.04?












6















Since 17.10 I got familiar with Wayland and I really need the per-monitor-scaling!



How can I start a wayland session after dist-upgrade to Bionic? There is no option in GDM available out-of-the-box.



I do not see what is described as




The Wayland session will still be available, pre-installed




Bionic Beaver 18.04 LTS to use Xorg by default










share|improve this question




















  • 2





    Don't you see a cogwheel (⚙️) next to the sign in button in GDM login screen?

    – pomsky
    May 7 '18 at 7:32











  • yes, but there is no option for wayland available.

    – user200016
    May 22 '18 at 18:31






  • 1





    The problem might be that you upgraded. In a fresh installation of Ubuntu 18.04 LTS, there is 'action' behind the cog wheel. (I have a fresh installation, and I can switch between Xorg and Wayland; I am running Wayland most of the time). -- Unfortunately the upgrade scripts are not quite mature yet. We can expect things to work smoothly when the first point release, Ubuntu 18.04.1 LTS, is uploaded, late July or early August.

    – sudodus
    Jun 5 '18 at 10:16













  • @sudodus I have a fresh install, no cog though. Maybe it's because it's a "minimal desktop" install

    – Szabolcs
    Sep 24 '18 at 11:49













  • @Szabolcs, what do you mean by minimal desktop install? Which version of Ubuntu? Which desktop environment? How did you create it? You can also describe your computer (brand name and model). I suggest that you create an own question, where you describe your case. You can link to it from a new comment here.

    – sudodus
    Sep 24 '18 at 11:57


















6















Since 17.10 I got familiar with Wayland and I really need the per-monitor-scaling!



How can I start a wayland session after dist-upgrade to Bionic? There is no option in GDM available out-of-the-box.



I do not see what is described as




The Wayland session will still be available, pre-installed




Bionic Beaver 18.04 LTS to use Xorg by default










share|improve this question




















  • 2





    Don't you see a cogwheel (⚙️) next to the sign in button in GDM login screen?

    – pomsky
    May 7 '18 at 7:32











  • yes, but there is no option for wayland available.

    – user200016
    May 22 '18 at 18:31






  • 1





    The problem might be that you upgraded. In a fresh installation of Ubuntu 18.04 LTS, there is 'action' behind the cog wheel. (I have a fresh installation, and I can switch between Xorg and Wayland; I am running Wayland most of the time). -- Unfortunately the upgrade scripts are not quite mature yet. We can expect things to work smoothly when the first point release, Ubuntu 18.04.1 LTS, is uploaded, late July or early August.

    – sudodus
    Jun 5 '18 at 10:16













  • @sudodus I have a fresh install, no cog though. Maybe it's because it's a "minimal desktop" install

    – Szabolcs
    Sep 24 '18 at 11:49













  • @Szabolcs, what do you mean by minimal desktop install? Which version of Ubuntu? Which desktop environment? How did you create it? You can also describe your computer (brand name and model). I suggest that you create an own question, where you describe your case. You can link to it from a new comment here.

    – sudodus
    Sep 24 '18 at 11:57
















6












6








6


2






Since 17.10 I got familiar with Wayland and I really need the per-monitor-scaling!



How can I start a wayland session after dist-upgrade to Bionic? There is no option in GDM available out-of-the-box.



I do not see what is described as




The Wayland session will still be available, pre-installed




Bionic Beaver 18.04 LTS to use Xorg by default










share|improve this question
















Since 17.10 I got familiar with Wayland and I really need the per-monitor-scaling!



How can I start a wayland session after dist-upgrade to Bionic? There is no option in GDM available out-of-the-box.



I do not see what is described as




The Wayland session will still be available, pre-installed




Bionic Beaver 18.04 LTS to use Xorg by default







18.04 gdm wayland






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 7 '18 at 7:16









Zanna

50.7k13135241




50.7k13135241










asked May 7 '18 at 6:49









user200016user200016

31113




31113








  • 2





    Don't you see a cogwheel (⚙️) next to the sign in button in GDM login screen?

    – pomsky
    May 7 '18 at 7:32











  • yes, but there is no option for wayland available.

    – user200016
    May 22 '18 at 18:31






  • 1





    The problem might be that you upgraded. In a fresh installation of Ubuntu 18.04 LTS, there is 'action' behind the cog wheel. (I have a fresh installation, and I can switch between Xorg and Wayland; I am running Wayland most of the time). -- Unfortunately the upgrade scripts are not quite mature yet. We can expect things to work smoothly when the first point release, Ubuntu 18.04.1 LTS, is uploaded, late July or early August.

    – sudodus
    Jun 5 '18 at 10:16













  • @sudodus I have a fresh install, no cog though. Maybe it's because it's a "minimal desktop" install

    – Szabolcs
    Sep 24 '18 at 11:49













  • @Szabolcs, what do you mean by minimal desktop install? Which version of Ubuntu? Which desktop environment? How did you create it? You can also describe your computer (brand name and model). I suggest that you create an own question, where you describe your case. You can link to it from a new comment here.

    – sudodus
    Sep 24 '18 at 11:57
















  • 2





    Don't you see a cogwheel (⚙️) next to the sign in button in GDM login screen?

    – pomsky
    May 7 '18 at 7:32











  • yes, but there is no option for wayland available.

    – user200016
    May 22 '18 at 18:31






  • 1





    The problem might be that you upgraded. In a fresh installation of Ubuntu 18.04 LTS, there is 'action' behind the cog wheel. (I have a fresh installation, and I can switch between Xorg and Wayland; I am running Wayland most of the time). -- Unfortunately the upgrade scripts are not quite mature yet. We can expect things to work smoothly when the first point release, Ubuntu 18.04.1 LTS, is uploaded, late July or early August.

    – sudodus
    Jun 5 '18 at 10:16













  • @sudodus I have a fresh install, no cog though. Maybe it's because it's a "minimal desktop" install

    – Szabolcs
    Sep 24 '18 at 11:49













  • @Szabolcs, what do you mean by minimal desktop install? Which version of Ubuntu? Which desktop environment? How did you create it? You can also describe your computer (brand name and model). I suggest that you create an own question, where you describe your case. You can link to it from a new comment here.

    – sudodus
    Sep 24 '18 at 11:57










2




2





Don't you see a cogwheel (⚙️) next to the sign in button in GDM login screen?

– pomsky
May 7 '18 at 7:32





Don't you see a cogwheel (⚙️) next to the sign in button in GDM login screen?

– pomsky
May 7 '18 at 7:32













yes, but there is no option for wayland available.

– user200016
May 22 '18 at 18:31





yes, but there is no option for wayland available.

– user200016
May 22 '18 at 18:31




1




1





The problem might be that you upgraded. In a fresh installation of Ubuntu 18.04 LTS, there is 'action' behind the cog wheel. (I have a fresh installation, and I can switch between Xorg and Wayland; I am running Wayland most of the time). -- Unfortunately the upgrade scripts are not quite mature yet. We can expect things to work smoothly when the first point release, Ubuntu 18.04.1 LTS, is uploaded, late July or early August.

– sudodus
Jun 5 '18 at 10:16







The problem might be that you upgraded. In a fresh installation of Ubuntu 18.04 LTS, there is 'action' behind the cog wheel. (I have a fresh installation, and I can switch between Xorg and Wayland; I am running Wayland most of the time). -- Unfortunately the upgrade scripts are not quite mature yet. We can expect things to work smoothly when the first point release, Ubuntu 18.04.1 LTS, is uploaded, late July or early August.

– sudodus
Jun 5 '18 at 10:16















@sudodus I have a fresh install, no cog though. Maybe it's because it's a "minimal desktop" install

– Szabolcs
Sep 24 '18 at 11:49







@sudodus I have a fresh install, no cog though. Maybe it's because it's a "minimal desktop" install

– Szabolcs
Sep 24 '18 at 11:49















@Szabolcs, what do you mean by minimal desktop install? Which version of Ubuntu? Which desktop environment? How did you create it? You can also describe your computer (brand name and model). I suggest that you create an own question, where you describe your case. You can link to it from a new comment here.

– sudodus
Sep 24 '18 at 11:57







@Szabolcs, what do you mean by minimal desktop install? Which version of Ubuntu? Which desktop environment? How did you create it? You can also describe your computer (brand name and model). I suggest that you create an own question, where you describe your case. You can link to it from a new comment here.

– sudodus
Sep 24 '18 at 11:57












2 Answers
2






active

oldest

votes


















6














On the login screen, you should be able to select "Ubuntu on Wayland" by clicking on the settings icon, next to the login button.



If that option is not available under the cog icon on the password screen, make sure that WaylandEnable=false is commented out (or not present) in /etc/gdm3/custom.conf



Mine looks like this:



# GDM configuration storage
#
# See /usr/share/gdm/gdm.schemas for a list of available options.

[daemon]
# Uncoment the line below to force the login screen to use Xorg
# WaylandEnable=false

# Enabling automatic login
# AutomaticLoginEnable = true
# AutomaticLogin = user1

# Enabling timed login
# TimedLoginEnable = true
# TimedLogin = user1
# TimedLoginDelay = 10

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
# More verbose logs
# Additionally lets the X server dump core if it crashes
Enable=true


If you cannot log in to change this, start Ubuntu into recovery mode, go into root shell, and mount root partition as read/write: How do I boot into recovery mode?



From there edit the GDM config with nano /etc/gdm3/custom.conf and comment out the WaylandEnable line: #WaylandEnable=false






share|improve this answer


























  • «not sure why» is a bit scary. anyway, a new installation is not an option for me.

    – user200016
    May 29 '18 at 11:34






  • 1





    thank you for the addition. i am in the sudo group, so i am able to edit the file, but the named line looks good already.

    – user200016
    Jun 6 '18 at 11:07






  • 2





    I'm not seeing that option, I just see "Ubuntu", and "Gnome Classic", neither of which use Wayland. WaylandEnable = false is commented out.

    – Hassan
    Aug 27 '18 at 5:33



















3














I got this to work, but it was by specifically setting this option:



WaylandEnable=true


In any case, as mentioned elsewhere, this does not work on all applications.



Google Chrome continues to have monster fonts.






share|improve this answer

























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


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1033004%2f18-04-how-to-get-wayland-back-after-upgrade-to-18-04%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    6














    On the login screen, you should be able to select "Ubuntu on Wayland" by clicking on the settings icon, next to the login button.



    If that option is not available under the cog icon on the password screen, make sure that WaylandEnable=false is commented out (or not present) in /etc/gdm3/custom.conf



    Mine looks like this:



    # GDM configuration storage
    #
    # See /usr/share/gdm/gdm.schemas for a list of available options.

    [daemon]
    # Uncoment the line below to force the login screen to use Xorg
    # WaylandEnable=false

    # Enabling automatic login
    # AutomaticLoginEnable = true
    # AutomaticLogin = user1

    # Enabling timed login
    # TimedLoginEnable = true
    # TimedLogin = user1
    # TimedLoginDelay = 10

    [security]

    [xdmcp]

    [chooser]

    [debug]
    # Uncomment the line below to turn on debugging
    # More verbose logs
    # Additionally lets the X server dump core if it crashes
    Enable=true


    If you cannot log in to change this, start Ubuntu into recovery mode, go into root shell, and mount root partition as read/write: How do I boot into recovery mode?



    From there edit the GDM config with nano /etc/gdm3/custom.conf and comment out the WaylandEnable line: #WaylandEnable=false






    share|improve this answer


























    • «not sure why» is a bit scary. anyway, a new installation is not an option for me.

      – user200016
      May 29 '18 at 11:34






    • 1





      thank you for the addition. i am in the sudo group, so i am able to edit the file, but the named line looks good already.

      – user200016
      Jun 6 '18 at 11:07






    • 2





      I'm not seeing that option, I just see "Ubuntu", and "Gnome Classic", neither of which use Wayland. WaylandEnable = false is commented out.

      – Hassan
      Aug 27 '18 at 5:33
















    6














    On the login screen, you should be able to select "Ubuntu on Wayland" by clicking on the settings icon, next to the login button.



    If that option is not available under the cog icon on the password screen, make sure that WaylandEnable=false is commented out (or not present) in /etc/gdm3/custom.conf



    Mine looks like this:



    # GDM configuration storage
    #
    # See /usr/share/gdm/gdm.schemas for a list of available options.

    [daemon]
    # Uncoment the line below to force the login screen to use Xorg
    # WaylandEnable=false

    # Enabling automatic login
    # AutomaticLoginEnable = true
    # AutomaticLogin = user1

    # Enabling timed login
    # TimedLoginEnable = true
    # TimedLogin = user1
    # TimedLoginDelay = 10

    [security]

    [xdmcp]

    [chooser]

    [debug]
    # Uncomment the line below to turn on debugging
    # More verbose logs
    # Additionally lets the X server dump core if it crashes
    Enable=true


    If you cannot log in to change this, start Ubuntu into recovery mode, go into root shell, and mount root partition as read/write: How do I boot into recovery mode?



    From there edit the GDM config with nano /etc/gdm3/custom.conf and comment out the WaylandEnable line: #WaylandEnable=false






    share|improve this answer


























    • «not sure why» is a bit scary. anyway, a new installation is not an option for me.

      – user200016
      May 29 '18 at 11:34






    • 1





      thank you for the addition. i am in the sudo group, so i am able to edit the file, but the named line looks good already.

      – user200016
      Jun 6 '18 at 11:07






    • 2





      I'm not seeing that option, I just see "Ubuntu", and "Gnome Classic", neither of which use Wayland. WaylandEnable = false is commented out.

      – Hassan
      Aug 27 '18 at 5:33














    6












    6








    6







    On the login screen, you should be able to select "Ubuntu on Wayland" by clicking on the settings icon, next to the login button.



    If that option is not available under the cog icon on the password screen, make sure that WaylandEnable=false is commented out (or not present) in /etc/gdm3/custom.conf



    Mine looks like this:



    # GDM configuration storage
    #
    # See /usr/share/gdm/gdm.schemas for a list of available options.

    [daemon]
    # Uncoment the line below to force the login screen to use Xorg
    # WaylandEnable=false

    # Enabling automatic login
    # AutomaticLoginEnable = true
    # AutomaticLogin = user1

    # Enabling timed login
    # TimedLoginEnable = true
    # TimedLogin = user1
    # TimedLoginDelay = 10

    [security]

    [xdmcp]

    [chooser]

    [debug]
    # Uncomment the line below to turn on debugging
    # More verbose logs
    # Additionally lets the X server dump core if it crashes
    Enable=true


    If you cannot log in to change this, start Ubuntu into recovery mode, go into root shell, and mount root partition as read/write: How do I boot into recovery mode?



    From there edit the GDM config with nano /etc/gdm3/custom.conf and comment out the WaylandEnable line: #WaylandEnable=false






    share|improve this answer















    On the login screen, you should be able to select "Ubuntu on Wayland" by clicking on the settings icon, next to the login button.



    If that option is not available under the cog icon on the password screen, make sure that WaylandEnable=false is commented out (or not present) in /etc/gdm3/custom.conf



    Mine looks like this:



    # GDM configuration storage
    #
    # See /usr/share/gdm/gdm.schemas for a list of available options.

    [daemon]
    # Uncoment the line below to force the login screen to use Xorg
    # WaylandEnable=false

    # Enabling automatic login
    # AutomaticLoginEnable = true
    # AutomaticLogin = user1

    # Enabling timed login
    # TimedLoginEnable = true
    # TimedLogin = user1
    # TimedLoginDelay = 10

    [security]

    [xdmcp]

    [chooser]

    [debug]
    # Uncomment the line below to turn on debugging
    # More verbose logs
    # Additionally lets the X server dump core if it crashes
    Enable=true


    If you cannot log in to change this, start Ubuntu into recovery mode, go into root shell, and mount root partition as read/write: How do I boot into recovery mode?



    From there edit the GDM config with nano /etc/gdm3/custom.conf and comment out the WaylandEnable line: #WaylandEnable=false







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Jun 5 '18 at 10:01

























    answered May 7 '18 at 13:27









    dhuyvetterdhuyvetter

    1919




    1919













    • «not sure why» is a bit scary. anyway, a new installation is not an option for me.

      – user200016
      May 29 '18 at 11:34






    • 1





      thank you for the addition. i am in the sudo group, so i am able to edit the file, but the named line looks good already.

      – user200016
      Jun 6 '18 at 11:07






    • 2





      I'm not seeing that option, I just see "Ubuntu", and "Gnome Classic", neither of which use Wayland. WaylandEnable = false is commented out.

      – Hassan
      Aug 27 '18 at 5:33



















    • «not sure why» is a bit scary. anyway, a new installation is not an option for me.

      – user200016
      May 29 '18 at 11:34






    • 1





      thank you for the addition. i am in the sudo group, so i am able to edit the file, but the named line looks good already.

      – user200016
      Jun 6 '18 at 11:07






    • 2





      I'm not seeing that option, I just see "Ubuntu", and "Gnome Classic", neither of which use Wayland. WaylandEnable = false is commented out.

      – Hassan
      Aug 27 '18 at 5:33

















    «not sure why» is a bit scary. anyway, a new installation is not an option for me.

    – user200016
    May 29 '18 at 11:34





    «not sure why» is a bit scary. anyway, a new installation is not an option for me.

    – user200016
    May 29 '18 at 11:34




    1




    1





    thank you for the addition. i am in the sudo group, so i am able to edit the file, but the named line looks good already.

    – user200016
    Jun 6 '18 at 11:07





    thank you for the addition. i am in the sudo group, so i am able to edit the file, but the named line looks good already.

    – user200016
    Jun 6 '18 at 11:07




    2




    2





    I'm not seeing that option, I just see "Ubuntu", and "Gnome Classic", neither of which use Wayland. WaylandEnable = false is commented out.

    – Hassan
    Aug 27 '18 at 5:33





    I'm not seeing that option, I just see "Ubuntu", and "Gnome Classic", neither of which use Wayland. WaylandEnable = false is commented out.

    – Hassan
    Aug 27 '18 at 5:33













    3














    I got this to work, but it was by specifically setting this option:



    WaylandEnable=true


    In any case, as mentioned elsewhere, this does not work on all applications.



    Google Chrome continues to have monster fonts.






    share|improve this answer






























      3














      I got this to work, but it was by specifically setting this option:



      WaylandEnable=true


      In any case, as mentioned elsewhere, this does not work on all applications.



      Google Chrome continues to have monster fonts.






      share|improve this answer




























        3












        3








        3







        I got this to work, but it was by specifically setting this option:



        WaylandEnable=true


        In any case, as mentioned elsewhere, this does not work on all applications.



        Google Chrome continues to have monster fonts.






        share|improve this answer















        I got this to work, but it was by specifically setting this option:



        WaylandEnable=true


        In any case, as mentioned elsewhere, this does not work on all applications.



        Google Chrome continues to have monster fonts.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Sep 6 '18 at 20:13









        Zanna

        50.7k13135241




        50.7k13135241










        answered Sep 5 '18 at 21:28









        Scott FrancoScott Franco

        311




        311






























            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1033004%2f18-04-how-to-get-wayland-back-after-upgrade-to-18-04%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

            How to change which sound is reproduced for terminal bell?

            Can I use Tabulator js library in my java Spring + Thymeleaf project?

            Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents