Prevent laptop from sleep after closing lid

[Member anteeks]

Hi,

I am a new antiX user and I’ve just installed antiX 19.3 on my old HP ProBook.
I am testing the new system and I am struggling to find any option to disable the Lid sleep.

I couldn’t find any settings in Control Centre to do this and I also tried to modify
/etc/default/acpi-support by setting:
# Uncomment this to enable ACPI sleep when the lid screen is closed.
LID_SLEEP=false
But it still does not work.

I am wondering if I can get any help from forum pros?

Thanks!

[Member Robin]

Helpful

Up

0

::

Hi,
you’re welcome.

Maybe the sleep option defaults to forced sleep on closing the lid in your BIOS accidentally? Don’t know whether your laptop provides this feature in BIOS setup. I’m not a “pro” 🙂

Windows is like a submarine. Open a window and serious problems will start.

[Anonymous]

Helpful

Up

0

::

try this
sudo sed -i 's/^action=/#action=/' /etc/acpi/events/lidbtn

A more surgical approach might be achieved (idunno) by editing /etc/acpi/events/lidbtn
(maybe instead of COMPLETELY ignoring, you want to at least blank the display upon lid closure)

[Member Xecure]

Helpful

Up

0

::

Could this be another case of elogind taking control over acpi events or am I trying to find blame when there are no reasons for it?

Using the /etc/default/acpi-support modification mentioned by anteeks has always worked for me, so not sure what could be the reason for this particular case.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member anteeks]

Helpful

Up

0

::

I tried to comment out “action line but without luck. The laptop still sleeps after lid close 🙁

~ $ cat /etc/acpi/events/lidbtn
# /etc/acpi/events/lidbtn
# Called when the user closes or opens the lid

event=button[ /]lid
#action=/etc/acpi/lid.sh

[Member anteeks]

Helpful

Up

0

::

anteeks wrote:

y

Thanks Xecure!
This is my acpi-support. Am I missing anything?

~ $ cat  /etc/default/acpi-support
#
# Configuration file for the acpi-support package
#
#
# The acpi-support package is intended as "glue" to make special functions of
# laptops work. Specifically, it translates special function keys for some
# laptop models into actions or generic function key presses.
#

#
# Suspend/hibernate method
# ------------------------
#
# When gnome or kde power management daemons are running, acpi-support will
# translate the suspend and hibernate keys of laptops into special "suspend"
# and "hibernate" keys that these daemons handle.
#
# Only in situations where there is no power management daemon
# running, acpi-support needs to perform suspend/hibernate in some other way.
# Beginning with version 0.122-1 acpi-support solely uses pm-utils then.

# Comment the next line to disable ACPI suspend to RAM
ACPI_SLEEP=true

# Comment the next line to disable suspend to disk
ACPI_HIBERNATE=true

# Use Radeontool to switch the screen off? Seems to be needed on some machines
# RADEON_LIGHT=true

# Comment this out to disable screen locking on resume
LOCK_SCREEN=true

# Uncomment this to enable ACPI sleep when the lid screen is closed.
LID_SLEEP=false

# Uncomment this to shutdown the system if ACPI sleep has not been possible
# upon lid closure. Has no effect if LID_SLEEP is not set.
#LID_SHUTDOWN=true

# On some systems pressing the wireless button only results in an event that we
# handle, but not in some hardware enforced action. On these systems we are
# free to choose whether or not we cycle through "Both on, Both off, Wireless
# only, Bluetooth only" as we used to do, or if we just do "Both on, Both off"
# as the hardware kill switch does on most systems.
#
# For compatibility reasons with older version the larger cycle is the default.
# Enable this to to have both in switched on and off simultaniously. 
#WIRELESS_BLUETOOTH_SYNC=true

# Choose the method used to switch off/on the display. Available options are
# "xset", "xrandr" and "vbetool".
DISPLAY_DPMS=xset

# xrandr needs the output device to be named
XRANDR_OUTPUT=LVDS

# vbetool can switch off/on the display even if no user is logged in. However,
# there are systems that do not reset the display when coming out of suspend,
# so that the screen remains dark. Enable this option to switch off the display
# even if no one is logged in.
#DISPLAY_DPMS_NO_USER=true

[Member anteeks]

Helpful

Up

0

::

@Robin
Thanks! But I couldn’t find the lid close action option in BIOS on this old laptop 🙁

[Member Xecure]

Helpful

Up

0

::

@anteeks
I see no problem in the acpi-support defaults file. I will try experiment later today to see if there are other ways to disable to closed-lid behavior.

There have been other posts related to this issue, but most of them were related to suspension errors or lid-switch (like this thread). I will check on my laptop when I have time.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Xecure]

Helpful

Up

0

::

I hadn’t tested this for a long time, and now I know /etc/default/acpi-support no longer manages all power events. Seems that elogind, inheriting systemd’s naughty behavior, is now in control of more things that shouldn’t be in its plate.

Anyway, the solution I found is to edit elogind configuration
sudo geany /etc/elogind/logind.conf
search for the commented line containing HandleLidSwitch=suspend, un-comment it and change it to ignore, so it looks like:
HandleLidSwitch=ignore
Save the file, reboot and see if now the laptop doesn’t suspend when closing the lid.

Let us know how it goes. If it also worked for you, I will update my personal notes and recommend this thread to others in the future.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member anteeks]

Helpful

Up

0

::

Xecure wrote:

I hadn’t tested this for a long time, and now I know /etc/default/acpi-support no longer manages all power events. Seems that elogind, inheriting systemd’s naughty behavior, is now in control of more things that shouldn’t be in its plate.

Anyway, the solution I found is to edit elogind configuration
sudo geany /etc/elogind/logind.conf
search for the commented line containing HandleLidSwitch=suspend, un-comment it and change it to ignore, so it looks like:
HandleLidSwitch=ignore
Save the file, reboot and see if now the laptop doesn’t suspend when closing the lid.

Let us know how it goes. If it also worked for you, I will update my personal notes and recommend this thread to others in the future.

That is awesome! It works! Thanks a lot!

But I found a new minor issue. After I re-open the laptop lid, the cursor disappears. The mouse is still functional. When I hold left button and draw box on the desktop, I can see the blue box. But no cursor. It is almost like cursor becomes transparent.
The only workaround I figure out so far is to press Ctrl-Alt-Backspace to kill X and re-login.

• This reply was modified 2 years, 1 month ago by anteeks.

[Member Xecure]

Helpful

Up

0

::

anteeks wrote:

But I found a new minor issue. After I re-open the laptop lid, the cursor disappears. The mouse is still functional.

I had that happen to me some time ago. I found that slightly increasing the cursor size using the Mouse Configuration program, as I mentioned in this other forum answer.

Xecure wrote:

If it is only the cursor disappearing, using the Mouse Configuration to increase the cursor size (even if just a little bit) may help avoid this from happening in the future.

(Control Centre > Hardware > Mouse Configuration), Enable on startup (switch at the bottom) and slightly increase the cursor size in pixels. Save and this should fix the disappearing cursor problem on next reboot.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member anteeks]

Helpful

Up

0

::

Xecure wrote:

(Control Centre > Hardware > Mouse Configuration), Enable on startup (switch at the bottom) and slightly increase the cursor size in pixels. Save and this should fix the disappearing cursor problem on next reboot.

It did changed the cursor size, but the cursor disappear after lid opening issue still persists.
PS: each time I open the “Control Centre > Hardware > Mouse Configuration”, I see the “Enable on startup” switch at OFF position. I assume it works, since I noticed my cursor is larger after reboot.

@Xecure, did you also have the cursor disappearing issue after you opened the lid?

[Member Xecure]

Helpful

Up

0

::

anteeks wrote:

@Xecure, did you also have the cursor disappearing issue after you opened the lid?

It happen to me on late antiX 17.4 or early antiX19 on live USB, when I had the laptop always connected to a monitor, and closing the lid to suspend and then waking it up resulted in an invisible mouse cursor. Increasing the cursor size slightly made it no longer disappear. Also, doing Control+Alt+F1 to enter tty1 and then Control+Alt+F7 to return to the graphic environment would also make the cursor reappear.

Using the solution I described above for stopping the suspension behavior when the lid closes using elogind doesn’t make my cursor disappear. I think it doesn’t even blank the screen, so it should affect anything X11 related. If someone else could check with their machine, maybe we could find some relation between a kernel version or maybe a specific driver that doesn’t behave as intended. I can tell you that, on my particular laptop, closing and opening the lid with the change I explained above to elogind doesn’t affect anything, not even the mouse cursor.

Can someone else check it out?

For now, try doing Control+Alt+F1 to enter tty1 and then Control+Alt+F7 to return to the graphic environment instead of stopping X to see if the mouse cursor returns.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member anteeks]

Helpful

Up

0

::

Xecure wrote:

try doing Control+Alt+F1 to enter tty1 and then Control+Alt+F7 to return to the graphic environment instead of stopping X

Very nice trick! It always works after the switch =)
This can be a temporary workaround! Thanks!

[Member Robin]

Helpful

Up

0

::

Another workaround:

Robin wrote:

Even if mouse pointer was not visible, one could get main menu by klicking right mouse button somewhere. When very carefully moving the mouse down blindly you would be able to toggle its focus to one of the menue entries — and right after clicking it the program (e.g. “terminal”) would open, which brings mouse pointer back to visibility immediately every single time.

@Xecure: only after installing original nvidia drivers this behaviour stopped. Refer to the quoted post for some information. I suspect this bug to be related to “noveau” driver. Different kernels didn’t have any effect on this back then.

Windows is like a submarine. Open a window and serious problems will start.

[Author]

Posts