Ubuntu 18.04 screen lock loses highest resolution each time












1















I'm on Ubuntu 18.04 desktop, with Intel HD Integrated Graphics and a single 2560x1440 screen connected with a DP (DisplayPort) cable. I've not had this problem using the same desktop with smaller monitors.



On this large monitor, each time I resume from locking the screen (entering my password for the system's only user account), the highest available resolution is progressively eliminated from the list of choices in both GNOME Settings and the options displayed by xrandr. Initially, after the system boot:



$ xrandr
Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 699mm x 393mm
2560x1440 59.95*+
2880x1620 60.00
2048x1152 60.00
1920x1200 59.88


... then after the first screen lock & resume, a higher than natural resolution is eliminated (through having no visible effect yet):



Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 ...
2560x1440 59.95*+
2048x1152 60.00
1920x1200 59.88


... then the second screen lock & resume reduces the current resolution to 2048x1152:



Screen 0: minimum 320 x 200, current 2048 x 1152, maximum 8192 x 8192 ...
DP-1 connected primary 2048x1152+0+0 (normal left inverted right x axis y axis) 699mm x 393mm
2048x1152 60.00*
1920x1200 59.88


... and the third reduces the screen to 1920x1200, going further down the list each time: progressively eliminating the highest pair of available screen resolution & video frequency with each screen lock.



The monitor is an Acer EB321HQU - turning it off & on again has no effect on the resolutions available unless the system is also rebooted. There are related bug reports but only confirmed for nVidia graphics cards, not applicable in my case. I've also tried these so far, with no effect on the problem:




  • switching from default gdm3 to lightdm

  • upgrading video driver xserver-xorg-video-intel/bionic from native 2:2.99.917+git20171229-1 to newer version at Open Graphics Drivers PPA 2:2.99.917+git1903011933.6afed3~oibaf~b amd64


  • EDIT: disconnecting & reconnecting the DP cable reduces the maximum resolution even further, to 1024x768.










share|improve this question





























    1















    I'm on Ubuntu 18.04 desktop, with Intel HD Integrated Graphics and a single 2560x1440 screen connected with a DP (DisplayPort) cable. I've not had this problem using the same desktop with smaller monitors.



    On this large monitor, each time I resume from locking the screen (entering my password for the system's only user account), the highest available resolution is progressively eliminated from the list of choices in both GNOME Settings and the options displayed by xrandr. Initially, after the system boot:



    $ xrandr
    Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
    VGA-1 disconnected (normal left inverted right x axis y axis)
    HDMI-1 disconnected (normal left inverted right x axis y axis)
    DP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 699mm x 393mm
    2560x1440 59.95*+
    2880x1620 60.00
    2048x1152 60.00
    1920x1200 59.88


    ... then after the first screen lock & resume, a higher than natural resolution is eliminated (through having no visible effect yet):



    Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 ...
    2560x1440 59.95*+
    2048x1152 60.00
    1920x1200 59.88


    ... then the second screen lock & resume reduces the current resolution to 2048x1152:



    Screen 0: minimum 320 x 200, current 2048 x 1152, maximum 8192 x 8192 ...
    DP-1 connected primary 2048x1152+0+0 (normal left inverted right x axis y axis) 699mm x 393mm
    2048x1152 60.00*
    1920x1200 59.88


    ... and the third reduces the screen to 1920x1200, going further down the list each time: progressively eliminating the highest pair of available screen resolution & video frequency with each screen lock.



    The monitor is an Acer EB321HQU - turning it off & on again has no effect on the resolutions available unless the system is also rebooted. There are related bug reports but only confirmed for nVidia graphics cards, not applicable in my case. I've also tried these so far, with no effect on the problem:




    • switching from default gdm3 to lightdm

    • upgrading video driver xserver-xorg-video-intel/bionic from native 2:2.99.917+git20171229-1 to newer version at Open Graphics Drivers PPA 2:2.99.917+git1903011933.6afed3~oibaf~b amd64


    • EDIT: disconnecting & reconnecting the DP cable reduces the maximum resolution even further, to 1024x768.










    share|improve this question



























      1












      1








      1








      I'm on Ubuntu 18.04 desktop, with Intel HD Integrated Graphics and a single 2560x1440 screen connected with a DP (DisplayPort) cable. I've not had this problem using the same desktop with smaller monitors.



      On this large monitor, each time I resume from locking the screen (entering my password for the system's only user account), the highest available resolution is progressively eliminated from the list of choices in both GNOME Settings and the options displayed by xrandr. Initially, after the system boot:



      $ xrandr
      Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
      VGA-1 disconnected (normal left inverted right x axis y axis)
      HDMI-1 disconnected (normal left inverted right x axis y axis)
      DP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 699mm x 393mm
      2560x1440 59.95*+
      2880x1620 60.00
      2048x1152 60.00
      1920x1200 59.88


      ... then after the first screen lock & resume, a higher than natural resolution is eliminated (through having no visible effect yet):



      Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 ...
      2560x1440 59.95*+
      2048x1152 60.00
      1920x1200 59.88


      ... then the second screen lock & resume reduces the current resolution to 2048x1152:



      Screen 0: minimum 320 x 200, current 2048 x 1152, maximum 8192 x 8192 ...
      DP-1 connected primary 2048x1152+0+0 (normal left inverted right x axis y axis) 699mm x 393mm
      2048x1152 60.00*
      1920x1200 59.88


      ... and the third reduces the screen to 1920x1200, going further down the list each time: progressively eliminating the highest pair of available screen resolution & video frequency with each screen lock.



      The monitor is an Acer EB321HQU - turning it off & on again has no effect on the resolutions available unless the system is also rebooted. There are related bug reports but only confirmed for nVidia graphics cards, not applicable in my case. I've also tried these so far, with no effect on the problem:




      • switching from default gdm3 to lightdm

      • upgrading video driver xserver-xorg-video-intel/bionic from native 2:2.99.917+git20171229-1 to newer version at Open Graphics Drivers PPA 2:2.99.917+git1903011933.6afed3~oibaf~b amd64


      • EDIT: disconnecting & reconnecting the DP cable reduces the maximum resolution even further, to 1024x768.










      share|improve this question
















      I'm on Ubuntu 18.04 desktop, with Intel HD Integrated Graphics and a single 2560x1440 screen connected with a DP (DisplayPort) cable. I've not had this problem using the same desktop with smaller monitors.



      On this large monitor, each time I resume from locking the screen (entering my password for the system's only user account), the highest available resolution is progressively eliminated from the list of choices in both GNOME Settings and the options displayed by xrandr. Initially, after the system boot:



      $ xrandr
      Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
      VGA-1 disconnected (normal left inverted right x axis y axis)
      HDMI-1 disconnected (normal left inverted right x axis y axis)
      DP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 699mm x 393mm
      2560x1440 59.95*+
      2880x1620 60.00
      2048x1152 60.00
      1920x1200 59.88


      ... then after the first screen lock & resume, a higher than natural resolution is eliminated (through having no visible effect yet):



      Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 ...
      2560x1440 59.95*+
      2048x1152 60.00
      1920x1200 59.88


      ... then the second screen lock & resume reduces the current resolution to 2048x1152:



      Screen 0: minimum 320 x 200, current 2048 x 1152, maximum 8192 x 8192 ...
      DP-1 connected primary 2048x1152+0+0 (normal left inverted right x axis y axis) 699mm x 393mm
      2048x1152 60.00*
      1920x1200 59.88


      ... and the third reduces the screen to 1920x1200, going further down the list each time: progressively eliminating the highest pair of available screen resolution & video frequency with each screen lock.



      The monitor is an Acer EB321HQU - turning it off & on again has no effect on the resolutions available unless the system is also rebooted. There are related bug reports but only confirmed for nVidia graphics cards, not applicable in my case. I've also tried these so far, with no effect on the problem:




      • switching from default gdm3 to lightdm

      • upgrading video driver xserver-xorg-video-intel/bionic from native 2:2.99.917+git20171229-1 to newer version at Open Graphics Drivers PPA 2:2.99.917+git1903011933.6afed3~oibaf~b amd64


      • EDIT: disconnecting & reconnecting the DP cable reduces the maximum resolution even further, to 1024x768.







      18.04 xorg screen display-resolution lock-screen






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 17 at 17:08







      rphair

















      asked Mar 17 at 14:45









      rphairrphair

      387




      387






















          0






          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',
          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%2f1126405%2fubuntu-18-04-screen-lock-loses-highest-resolution-each-time%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 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%2f1126405%2fubuntu-18-04-screen-lock-loses-highest-resolution-each-time%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

          數位音樂下載

          When can things happen in Etherscan, such as the picture below?

          格利澤436b