Hey, folks, I’m hoping someone here can help me out.

I have a laptop that has been messed up for a while, and I just got it repaired. I was using as basically a desktop, external monitor, mouse, keyboard. I just got it repaired and would like to use it as a laptop again. My problem is that something like 2 years ago, I edited some setting so that I could close the lid of the laptop and it wouldn’t suspend, but I can’t remember how I did it, and now it won’t suspend when I close it, which is less than convenient for use as a laptop.

I googled, but it’s not in GNOME tweaks anymore, and I’m not sure how to do any of the stuff I see people posting about terminal commands. I can follow instructions for command line stuff, but I sort of need it spelled out for me from step 1.

Any help is really appreciated. Thanks in advance!

  • nmtake@lemm.ee
    2·
    3 months ago

    Can you run these commands and paste the output here?

    $ systemd-analyze cat-config systemd/logind.conf | grep -i lid
$ grep -i lid /etc/UPower/UPower.conf
    • Dharma Curious (he/him)@slrpnk.netOP
      1·
      3 months ago

      If I’m reading it right, it’s saying it should be working?

      /usr/lib/systemd/logind.confcody@fedora:$ systemd-analyze cat-config systemd/logind.conf | grsystemd-analyze cat-config systemd/logind.conf | grep -i lid #HandleLidSwitch=suspend #HandleLidSwitchExternalPower=suspend #HandleLidSwitchDocked=ignore #LidSwitchIgnoreInhibited=yes cody@fedora:~$ grep -i lid /etc/UPower/UPower.conf

      Do we ignore the lid state

      Some laptops are broken. The lid state is either inverted, or stuck

      IgnoreLid=false

      If any value is invalid, or not in descending order, the defaults

      If any value is invalid, or not in descending order, the defaults

      cody@fedora:~$

      Apparently # makes a line huge? All the huge lines are preceded by a #

      • macniel
        3·
        3 months ago

        # at the beginning of a line followed by a space is markdown for a H1 format. That’s why it gets huge. You can escape this formatting with \

      • nmtake@lemm.ee
        2·
        3 months ago

        If I’m reading it right, it’s saying it should be working?

        I think so, but I might be overlooking something.

        Apparently # makes a line huge? All the huge lines are preceded by a #

        As macniel said, a line starts with “#” is converted to a heading. To post preformatted lines such as the log or source code, you can use “fenced code block”. For example,

        ```
foo
#bar
baz
```

        becomes

        foo
#bar
baz
        • Dharma Curious (he/him)@slrpnk.netOP
          1·
          3 months ago

          Thanks for teaching me something! :)

          Any idea what to do about the lid close issues with that output? I’m stumped, but I’m stumped easily, so I’m not sure how dead-endy this is haha

          • nmtake@lemm.ee
            2·
            3 months ago

            It’s not a dead end :) Can you

            1. make sure "systemctl suspend" suspends your machine to check suspend work
            2. Run "gnome-tweaks" and there’s no suspend inhibitor in the “Startup Applications”
            3. post the output of "systemd-inhibit | less" to know who inhibit the suspend
            4. post the output of "gsettings list-recursively | grep -i 'lid\|suspend'"

            (Please remove enclosing double quotes when you try them.)

            • Dharma Curious (he/him)@slrpnk.netOP
              1·
              3 months ago

              I really appreciate your help, but I had to do a fresh install of Fedora last night. It was having major issues after I updated to 40. I hadn’t used the laptop in nearly 2 years, and I think it just messed up when I updated it. It is working perfectly now, though!

              My main issue now is that I got nextcloud through hertzner to back up everything before I reinstalled, and I accidently rented a server on there in addition to the storage share, and I’m not sure how to give it back 😭

                • Dharma Curious (he/him)@slrpnk.netOP
                  2·
                  3 months ago

                  Yeah, that’s what I get for not reading well enough and just busting my way through like a bull in a china shop. Lol. Lesson learned, though.

                  I really appreciate all your help. Honestly, it’s one of the best things about switching to Linux, since I have, any time I’ve had any issue, even minor stuff, people have jumped on the chance to help me learn and fix it. It’s been amazing. And then switching to Lemmy has just made that experience even better

  • jmf@lemm.ee
    2·
    3 months ago

    It may seem silly but I switched to KDE plasma becaus of this feature. In my humble opinion as a sysadmin, a modern desktop PC in 2024 should not need the user to query config values for power settings!

    • Dharma Curious (he/him)@slrpnk.netOP
      1·
      3 months ago

      This is the first thing I’ve found since I switched from Windows where windows just does it better, to be honest. Kde doesn’t make you jump through these hoops? I love gnome, It’s the perfect aesthetic for me, and I love how… Flowy it feels. But grrrrrr about this. Lol

      • jmf@lemm.ee
        2·
        3 months ago

        Nope! Plasma has a nice settings page dedicated to to this power related configuration, so you click exactly what you want to happen and forget about it. I configured plasma to work almost identically to gnome with the overview and gestures and it is so snappy. Still hope that the gnome devs work out a way to make these options more accessible, but even if they added those there’s no way I’d switch back now!