Limiting desktop size in Linux












0















I have a display and the right-most edge of my monitor is busted! So to make it work, I'm trying to somehow restrict my desktop to the pixels that actually work.



This would mean:




  • The pointer shouldn't enter the black region ever

  • Windows if maximized should take up only the pixels that work.


I use Ubuntu 13.10! Any terms that I can research would be great!



enter image description here










share|improve this question

























  • possible duplicate of How to use only part of screen, as if the monitor was a smaller one?, superuser.com/questions/166948/…, superuser.com/questions/369702/…

    – Ƭᴇcʜιᴇ007
    Feb 20 '14 at 17:33













  • The solution for Windows has been covered in the questions @techie007 linked to. Editing your question so it applies to Linux only should prevent it from getting closed. Speaking of Linux: Which distro and desktop environment are you using?

    – Dennis
    Feb 20 '14 at 17:52













  • Thanks @techie007, I've edited the question to be linux-only now.

    – Utkarsh Sinha
    Feb 20 '14 at 17:56











  • Using ObjectDock on windows certainly fixed the problem. Need to figure out linux now.

    – Utkarsh Sinha
    Feb 22 '14 at 5:02
















0















I have a display and the right-most edge of my monitor is busted! So to make it work, I'm trying to somehow restrict my desktop to the pixels that actually work.



This would mean:




  • The pointer shouldn't enter the black region ever

  • Windows if maximized should take up only the pixels that work.


I use Ubuntu 13.10! Any terms that I can research would be great!



enter image description here










share|improve this question

























  • possible duplicate of How to use only part of screen, as if the monitor was a smaller one?, superuser.com/questions/166948/…, superuser.com/questions/369702/…

    – Ƭᴇcʜιᴇ007
    Feb 20 '14 at 17:33













  • The solution for Windows has been covered in the questions @techie007 linked to. Editing your question so it applies to Linux only should prevent it from getting closed. Speaking of Linux: Which distro and desktop environment are you using?

    – Dennis
    Feb 20 '14 at 17:52













  • Thanks @techie007, I've edited the question to be linux-only now.

    – Utkarsh Sinha
    Feb 20 '14 at 17:56











  • Using ObjectDock on windows certainly fixed the problem. Need to figure out linux now.

    – Utkarsh Sinha
    Feb 22 '14 at 5:02














0












0








0








I have a display and the right-most edge of my monitor is busted! So to make it work, I'm trying to somehow restrict my desktop to the pixels that actually work.



This would mean:




  • The pointer shouldn't enter the black region ever

  • Windows if maximized should take up only the pixels that work.


I use Ubuntu 13.10! Any terms that I can research would be great!



enter image description here










share|improve this question
















I have a display and the right-most edge of my monitor is busted! So to make it work, I'm trying to somehow restrict my desktop to the pixels that actually work.



This would mean:




  • The pointer shouldn't enter the black region ever

  • Windows if maximized should take up only the pixels that work.


I use Ubuntu 13.10! Any terms that I can research would be great!



enter image description here







linux ubuntu display dead-pixel ubuntu-13.10






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 21 '14 at 15:25









Kevin Panko

5,929113648




5,929113648










asked Feb 20 '14 at 17:26









Utkarsh SinhaUtkarsh Sinha

68211117




68211117













  • possible duplicate of How to use only part of screen, as if the monitor was a smaller one?, superuser.com/questions/166948/…, superuser.com/questions/369702/…

    – Ƭᴇcʜιᴇ007
    Feb 20 '14 at 17:33













  • The solution for Windows has been covered in the questions @techie007 linked to. Editing your question so it applies to Linux only should prevent it from getting closed. Speaking of Linux: Which distro and desktop environment are you using?

    – Dennis
    Feb 20 '14 at 17:52













  • Thanks @techie007, I've edited the question to be linux-only now.

    – Utkarsh Sinha
    Feb 20 '14 at 17:56











  • Using ObjectDock on windows certainly fixed the problem. Need to figure out linux now.

    – Utkarsh Sinha
    Feb 22 '14 at 5:02



















  • possible duplicate of How to use only part of screen, as if the monitor was a smaller one?, superuser.com/questions/166948/…, superuser.com/questions/369702/…

    – Ƭᴇcʜιᴇ007
    Feb 20 '14 at 17:33













  • The solution for Windows has been covered in the questions @techie007 linked to. Editing your question so it applies to Linux only should prevent it from getting closed. Speaking of Linux: Which distro and desktop environment are you using?

    – Dennis
    Feb 20 '14 at 17:52













  • Thanks @techie007, I've edited the question to be linux-only now.

    – Utkarsh Sinha
    Feb 20 '14 at 17:56











  • Using ObjectDock on windows certainly fixed the problem. Need to figure out linux now.

    – Utkarsh Sinha
    Feb 22 '14 at 5:02

















possible duplicate of How to use only part of screen, as if the monitor was a smaller one?, superuser.com/questions/166948/…, superuser.com/questions/369702/…

– Ƭᴇcʜιᴇ007
Feb 20 '14 at 17:33







possible duplicate of How to use only part of screen, as if the monitor was a smaller one?, superuser.com/questions/166948/…, superuser.com/questions/369702/…

– Ƭᴇcʜιᴇ007
Feb 20 '14 at 17:33















The solution for Windows has been covered in the questions @techie007 linked to. Editing your question so it applies to Linux only should prevent it from getting closed. Speaking of Linux: Which distro and desktop environment are you using?

– Dennis
Feb 20 '14 at 17:52







The solution for Windows has been covered in the questions @techie007 linked to. Editing your question so it applies to Linux only should prevent it from getting closed. Speaking of Linux: Which distro and desktop environment are you using?

– Dennis
Feb 20 '14 at 17:52















Thanks @techie007, I've edited the question to be linux-only now.

– Utkarsh Sinha
Feb 20 '14 at 17:56





Thanks @techie007, I've edited the question to be linux-only now.

– Utkarsh Sinha
Feb 20 '14 at 17:56













Using ObjectDock on windows certainly fixed the problem. Need to figure out linux now.

– Utkarsh Sinha
Feb 22 '14 at 5:02





Using ObjectDock on windows certainly fixed the problem. Need to figure out linux now.

– Utkarsh Sinha
Feb 22 '14 at 5:02










1 Answer
1






active

oldest

votes


















1














We will be using two tools to achieve our goal. The first is cvt and the second is xrandr.



FIRST you need to know how much space you want to trim and from what side of your screen. In my case, I had dead pixels at the top of my laptop screen, taking up about 20 pixels (guestimate) so I wanted to reduce the screen size at the top of my screen and them and not have them cover the top of title bars. I will walk you through how I did this, you can adopt it to fit your situation.



So I started with running xrandr so that I could see what size my display was



$ xrandr 
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 32767 x 32767
LVDS1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
1280x800 60.0*+ 50.0
1024x768 60.0
800x600 60.3 56.2
640x480 60.0 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
TV1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)


So the screen size is 1280x800



Since my estimate is that the pixels have taken up 20 pixels across the top of the screen, so the new value will be 1280x780.



SECOND: werun cvt so that we can get the 'magic values' for this size:



 $ cvt 1280 770
# 1280x770 59.91 Hz (CVT) hsync: 47.93 kHz; pclk: 79.75 MHz
Modeline "1280x770_60.00" 79.75 1280 1344 1472 1664 770 773 783 800 -hsync +vsync


The important part is the one starting with "Modeline" - the values given in this line are the ones you will need to pass to xrandr so that it can cause the screen to display the new size. Xrandr does this using something called a "mode".



THIRD: It is time to make a new mode using the values we have gotten from cvt.



The command that allows us to do this (using the values I got above) looks like this:



$ xrandr --newmode 1280x770   79.75  1280 1344 1472 1664  770 773 783 800 -hsync +vsync


FOURTH: we add that new mode to the ones that are available in xrandr. This is done using the "--addmode" command in xrandr. In my particular case, I was adding it to the LVDS1.



So the command is going to be:



$ xrandr --addmode LVDS1 1280x770


FIFTH: We check whether the new mode has been added to xrandr. This is done using:



$ xrandr -q


I got:



    $ xrandr -q
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 32767 x 32767
LVDS1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
1280x800 60.0*+ 50.0
1024x768 60.0
800x600 60.3 56.2
640x480 60.0 59.9
1280x770 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
TV1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)


You can see it has been added and is now listed at the bottom - 1280x770 59.9



So now time to run the new mode! We do this by running:



$ xrandr --output LVDS1 --mode 1280x770


The screen should go off and come back on with the new mode applied and the screen size reduced.



The result is a black bar across the top of the screen, with the mouse and applications using this as the boundary of the screen.



So now the last step is to have that command run at login so that I don't have to deal with it. The manner of doing so depends on your desktop and is beyond the scope of this answer.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    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%2fsuperuser.com%2fquestions%2f719510%2flimiting-desktop-size-in-linux%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









    1














    We will be using two tools to achieve our goal. The first is cvt and the second is xrandr.



    FIRST you need to know how much space you want to trim and from what side of your screen. In my case, I had dead pixels at the top of my laptop screen, taking up about 20 pixels (guestimate) so I wanted to reduce the screen size at the top of my screen and them and not have them cover the top of title bars. I will walk you through how I did this, you can adopt it to fit your situation.



    So I started with running xrandr so that I could see what size my display was



    $ xrandr 
    Screen 0: minimum 320 x 200, current 1280 x 800, maximum 32767 x 32767
    LVDS1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
    1280x800 60.0*+ 50.0
    1024x768 60.0
    800x600 60.3 56.2
    640x480 60.0 59.9
    VGA1 disconnected (normal left inverted right x axis y axis)
    TV1 disconnected (normal left inverted right x axis y axis)
    VIRTUAL1 disconnected (normal left inverted right x axis y axis)


    So the screen size is 1280x800



    Since my estimate is that the pixels have taken up 20 pixels across the top of the screen, so the new value will be 1280x780.



    SECOND: werun cvt so that we can get the 'magic values' for this size:



     $ cvt 1280 770
    # 1280x770 59.91 Hz (CVT) hsync: 47.93 kHz; pclk: 79.75 MHz
    Modeline "1280x770_60.00" 79.75 1280 1344 1472 1664 770 773 783 800 -hsync +vsync


    The important part is the one starting with "Modeline" - the values given in this line are the ones you will need to pass to xrandr so that it can cause the screen to display the new size. Xrandr does this using something called a "mode".



    THIRD: It is time to make a new mode using the values we have gotten from cvt.



    The command that allows us to do this (using the values I got above) looks like this:



    $ xrandr --newmode 1280x770   79.75  1280 1344 1472 1664  770 773 783 800 -hsync +vsync


    FOURTH: we add that new mode to the ones that are available in xrandr. This is done using the "--addmode" command in xrandr. In my particular case, I was adding it to the LVDS1.



    So the command is going to be:



    $ xrandr --addmode LVDS1 1280x770


    FIFTH: We check whether the new mode has been added to xrandr. This is done using:



    $ xrandr -q


    I got:



        $ xrandr -q
    Screen 0: minimum 320 x 200, current 1280 x 800, maximum 32767 x 32767
    LVDS1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
    1280x800 60.0*+ 50.0
    1024x768 60.0
    800x600 60.3 56.2
    640x480 60.0 59.9
    1280x770 59.9
    VGA1 disconnected (normal left inverted right x axis y axis)
    TV1 disconnected (normal left inverted right x axis y axis)
    VIRTUAL1 disconnected (normal left inverted right x axis y axis)


    You can see it has been added and is now listed at the bottom - 1280x770 59.9



    So now time to run the new mode! We do this by running:



    $ xrandr --output LVDS1 --mode 1280x770


    The screen should go off and come back on with the new mode applied and the screen size reduced.



    The result is a black bar across the top of the screen, with the mouse and applications using this as the boundary of the screen.



    So now the last step is to have that command run at login so that I don't have to deal with it. The manner of doing so depends on your desktop and is beyond the scope of this answer.






    share|improve this answer




























      1














      We will be using two tools to achieve our goal. The first is cvt and the second is xrandr.



      FIRST you need to know how much space you want to trim and from what side of your screen. In my case, I had dead pixels at the top of my laptop screen, taking up about 20 pixels (guestimate) so I wanted to reduce the screen size at the top of my screen and them and not have them cover the top of title bars. I will walk you through how I did this, you can adopt it to fit your situation.



      So I started with running xrandr so that I could see what size my display was



      $ xrandr 
      Screen 0: minimum 320 x 200, current 1280 x 800, maximum 32767 x 32767
      LVDS1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
      1280x800 60.0*+ 50.0
      1024x768 60.0
      800x600 60.3 56.2
      640x480 60.0 59.9
      VGA1 disconnected (normal left inverted right x axis y axis)
      TV1 disconnected (normal left inverted right x axis y axis)
      VIRTUAL1 disconnected (normal left inverted right x axis y axis)


      So the screen size is 1280x800



      Since my estimate is that the pixels have taken up 20 pixels across the top of the screen, so the new value will be 1280x780.



      SECOND: werun cvt so that we can get the 'magic values' for this size:



       $ cvt 1280 770
      # 1280x770 59.91 Hz (CVT) hsync: 47.93 kHz; pclk: 79.75 MHz
      Modeline "1280x770_60.00" 79.75 1280 1344 1472 1664 770 773 783 800 -hsync +vsync


      The important part is the one starting with "Modeline" - the values given in this line are the ones you will need to pass to xrandr so that it can cause the screen to display the new size. Xrandr does this using something called a "mode".



      THIRD: It is time to make a new mode using the values we have gotten from cvt.



      The command that allows us to do this (using the values I got above) looks like this:



      $ xrandr --newmode 1280x770   79.75  1280 1344 1472 1664  770 773 783 800 -hsync +vsync


      FOURTH: we add that new mode to the ones that are available in xrandr. This is done using the "--addmode" command in xrandr. In my particular case, I was adding it to the LVDS1.



      So the command is going to be:



      $ xrandr --addmode LVDS1 1280x770


      FIFTH: We check whether the new mode has been added to xrandr. This is done using:



      $ xrandr -q


      I got:



          $ xrandr -q
      Screen 0: minimum 320 x 200, current 1280 x 800, maximum 32767 x 32767
      LVDS1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
      1280x800 60.0*+ 50.0
      1024x768 60.0
      800x600 60.3 56.2
      640x480 60.0 59.9
      1280x770 59.9
      VGA1 disconnected (normal left inverted right x axis y axis)
      TV1 disconnected (normal left inverted right x axis y axis)
      VIRTUAL1 disconnected (normal left inverted right x axis y axis)


      You can see it has been added and is now listed at the bottom - 1280x770 59.9



      So now time to run the new mode! We do this by running:



      $ xrandr --output LVDS1 --mode 1280x770


      The screen should go off and come back on with the new mode applied and the screen size reduced.



      The result is a black bar across the top of the screen, with the mouse and applications using this as the boundary of the screen.



      So now the last step is to have that command run at login so that I don't have to deal with it. The manner of doing so depends on your desktop and is beyond the scope of this answer.






      share|improve this answer


























        1












        1








        1







        We will be using two tools to achieve our goal. The first is cvt and the second is xrandr.



        FIRST you need to know how much space you want to trim and from what side of your screen. In my case, I had dead pixels at the top of my laptop screen, taking up about 20 pixels (guestimate) so I wanted to reduce the screen size at the top of my screen and them and not have them cover the top of title bars. I will walk you through how I did this, you can adopt it to fit your situation.



        So I started with running xrandr so that I could see what size my display was



        $ xrandr 
        Screen 0: minimum 320 x 200, current 1280 x 800, maximum 32767 x 32767
        LVDS1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
        1280x800 60.0*+ 50.0
        1024x768 60.0
        800x600 60.3 56.2
        640x480 60.0 59.9
        VGA1 disconnected (normal left inverted right x axis y axis)
        TV1 disconnected (normal left inverted right x axis y axis)
        VIRTUAL1 disconnected (normal left inverted right x axis y axis)


        So the screen size is 1280x800



        Since my estimate is that the pixels have taken up 20 pixels across the top of the screen, so the new value will be 1280x780.



        SECOND: werun cvt so that we can get the 'magic values' for this size:



         $ cvt 1280 770
        # 1280x770 59.91 Hz (CVT) hsync: 47.93 kHz; pclk: 79.75 MHz
        Modeline "1280x770_60.00" 79.75 1280 1344 1472 1664 770 773 783 800 -hsync +vsync


        The important part is the one starting with "Modeline" - the values given in this line are the ones you will need to pass to xrandr so that it can cause the screen to display the new size. Xrandr does this using something called a "mode".



        THIRD: It is time to make a new mode using the values we have gotten from cvt.



        The command that allows us to do this (using the values I got above) looks like this:



        $ xrandr --newmode 1280x770   79.75  1280 1344 1472 1664  770 773 783 800 -hsync +vsync


        FOURTH: we add that new mode to the ones that are available in xrandr. This is done using the "--addmode" command in xrandr. In my particular case, I was adding it to the LVDS1.



        So the command is going to be:



        $ xrandr --addmode LVDS1 1280x770


        FIFTH: We check whether the new mode has been added to xrandr. This is done using:



        $ xrandr -q


        I got:



            $ xrandr -q
        Screen 0: minimum 320 x 200, current 1280 x 800, maximum 32767 x 32767
        LVDS1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
        1280x800 60.0*+ 50.0
        1024x768 60.0
        800x600 60.3 56.2
        640x480 60.0 59.9
        1280x770 59.9
        VGA1 disconnected (normal left inverted right x axis y axis)
        TV1 disconnected (normal left inverted right x axis y axis)
        VIRTUAL1 disconnected (normal left inverted right x axis y axis)


        You can see it has been added and is now listed at the bottom - 1280x770 59.9



        So now time to run the new mode! We do this by running:



        $ xrandr --output LVDS1 --mode 1280x770


        The screen should go off and come back on with the new mode applied and the screen size reduced.



        The result is a black bar across the top of the screen, with the mouse and applications using this as the boundary of the screen.



        So now the last step is to have that command run at login so that I don't have to deal with it. The manner of doing so depends on your desktop and is beyond the scope of this answer.






        share|improve this answer













        We will be using two tools to achieve our goal. The first is cvt and the second is xrandr.



        FIRST you need to know how much space you want to trim and from what side of your screen. In my case, I had dead pixels at the top of my laptop screen, taking up about 20 pixels (guestimate) so I wanted to reduce the screen size at the top of my screen and them and not have them cover the top of title bars. I will walk you through how I did this, you can adopt it to fit your situation.



        So I started with running xrandr so that I could see what size my display was



        $ xrandr 
        Screen 0: minimum 320 x 200, current 1280 x 800, maximum 32767 x 32767
        LVDS1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
        1280x800 60.0*+ 50.0
        1024x768 60.0
        800x600 60.3 56.2
        640x480 60.0 59.9
        VGA1 disconnected (normal left inverted right x axis y axis)
        TV1 disconnected (normal left inverted right x axis y axis)
        VIRTUAL1 disconnected (normal left inverted right x axis y axis)


        So the screen size is 1280x800



        Since my estimate is that the pixels have taken up 20 pixels across the top of the screen, so the new value will be 1280x780.



        SECOND: werun cvt so that we can get the 'magic values' for this size:



         $ cvt 1280 770
        # 1280x770 59.91 Hz (CVT) hsync: 47.93 kHz; pclk: 79.75 MHz
        Modeline "1280x770_60.00" 79.75 1280 1344 1472 1664 770 773 783 800 -hsync +vsync


        The important part is the one starting with "Modeline" - the values given in this line are the ones you will need to pass to xrandr so that it can cause the screen to display the new size. Xrandr does this using something called a "mode".



        THIRD: It is time to make a new mode using the values we have gotten from cvt.



        The command that allows us to do this (using the values I got above) looks like this:



        $ xrandr --newmode 1280x770   79.75  1280 1344 1472 1664  770 773 783 800 -hsync +vsync


        FOURTH: we add that new mode to the ones that are available in xrandr. This is done using the "--addmode" command in xrandr. In my particular case, I was adding it to the LVDS1.



        So the command is going to be:



        $ xrandr --addmode LVDS1 1280x770


        FIFTH: We check whether the new mode has been added to xrandr. This is done using:



        $ xrandr -q


        I got:



            $ xrandr -q
        Screen 0: minimum 320 x 200, current 1280 x 800, maximum 32767 x 32767
        LVDS1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
        1280x800 60.0*+ 50.0
        1024x768 60.0
        800x600 60.3 56.2
        640x480 60.0 59.9
        1280x770 59.9
        VGA1 disconnected (normal left inverted right x axis y axis)
        TV1 disconnected (normal left inverted right x axis y axis)
        VIRTUAL1 disconnected (normal left inverted right x axis y axis)


        You can see it has been added and is now listed at the bottom - 1280x770 59.9



        So now time to run the new mode! We do this by running:



        $ xrandr --output LVDS1 --mode 1280x770


        The screen should go off and come back on with the new mode applied and the screen size reduced.



        The result is a black bar across the top of the screen, with the mouse and applications using this as the boundary of the screen.



        So now the last step is to have that command run at login so that I don't have to deal with it. The manner of doing so depends on your desktop and is beyond the scope of this answer.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Oct 6 '15 at 9:18









        curiousrabbitcuriousrabbit

        112




        112






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • 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%2fsuperuser.com%2fquestions%2f719510%2flimiting-desktop-size-in-linux%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

            Probability when a professor distributes a quiz and homework assignment to a class of n students.

            Aardman Animations

            Are they similar matrix