I’ve just switched from Win11 to Pop!_OS. The only issue that I have and can’t seem to resolve is the behaviour of external monitor with closed lid. I’m running 22.04 LTS Pop!_OS with nVidia GTX 3050. What I’ve tried so far to make it work:

  1. Simply closing the lid - external monitor remains on and displays DE, I can move cursor there but the computer remains unresponsive to any keyboard/mouse input.

  2. Using Single display through Display option in settings with lid open. Same result as in 1. System remains unresponsive to any input, closing and reopening lid allows me to regain control.

  3. Changes in the configuration file. I’ve changed value of following parameters to ignore:

HandleLidSwitch HandleLidSwitchExternalPower

Then, I tried doing same thing as in 1. and 2. but I got the same negative results.

Is it possible to get the monitor set that I want to work? If not, would other newb friendly distros handle this issue better? Thanks for any advice.

  • jimi_henrik@lemmy.worldEnglish
    2·
    5 days ago

    In #1 when you say the monitor displays the DE, is the Dock visible? If not, it could be that you’re trying to interact with the DE but the dock and application launcher is on the laptop display.

    I didn’t have to change any config values and it works. The only other thing I can think of is that I have Gnome Tweaks installed and the ‘Suspend when laptop lid is closed’ is disabled in the ‘General’ tab.

    Another thing to try is to see what Pop!_OS outputs in the /var/log/syslog file when this happens. What I would suggest you do is:

    1. open the terminal app
    2. type sudo /var/log/syslog -f (this will start writing all sorts of messages to the screen)
    3. do your step #1 (when it becomes unresponsive)
    4. open the lid again so the system becomes reponsive
    5. press Ctrl + c to stop outputting the contents of the systog file.

    Scroll up and see if there’s any error, warning or something to that affect in the log related to power management, displays or the desktop environment.

    And one more thing which is probably obvious: make sure your system is up do date (both the operating system and the BIOS).

    • Bohurt@mander.xyzOPEnglish
      2·
      4 days ago

      Thanks for the answer. I looked kind of like you described in the first paragraph. Fortunately, the issue resolved itself, probably after system components were updated. Initially I didn’t notice that they are updated separately from the system itself