Post by .Nicolás. on Jun 10, 2021 23:21:15 GMT
Hello Everybody, I'm new with Bodhi Linux and Linux. My name is Nicolás. When I suspend Bodhi Linux 6.0.0. it does, but when I want to resume the session it suspends again after 5 seconds and I don't know why. After pressing the power button it does resume the session and I can continue using Bodhi Linux. Does anyone know how to fix up that problem?
Any recommendation?
A fellow wrote this:
"hmm i never heard of that problem
but seems what we are using for suspend is having issues with your hardware
Moksha uses pm-utils by default
@.Nicolás. but you can change what is used
look at the file /etc/enlightenment/sysactions.conf
and change the line action: action: suspend ... YOU HAVE TO EDIT THIS FILE AS ROOT
to something that maybe works better on your system
i am uncertain what
i am currenty using on my laptop:
action: suspend /bin/systemctl suspend
becuase i want that one file to work with both moksha and enlightenment
another option is using acpi
it is prob installed but if you try using acpi I would install acpid
there are probably other options ...
sorry I can't be more specific"
---------------------------------------------------------------------------------------------------------------
EDITING THE FILE AS ROOT:
ENLIGHTENMENT SYSTEM ACTIONS CONFIGURATION
#
# This is a system configuration for allowing or denying certain users or
# groups to be able to do certain actions that involve system restricted
# actions such as halt, reboot, suspend, hibernate etc.
#
# This file is read in order from top to bottom - the first rule to MATCH
# will be used for a user or a group, and nothing after that is read.
#
# You must put all the ACTION definitons BEFORE user and group rule matches.
# Any action definitons after a rule match has been found will be ignored.
# This allows actions to be re-defined for different user groups, so matches
# so the command for an action can change for matches to the rules later on.
#
# Any user or group NOT matched by an allow or a deny will be ALLOWED to
# perform the action by default (system administrators should be aware of
# this and implement whatever policies they see fit). Generally speaking
# a user of a workstation, desktop or laptop is intended to have such abilities
# to perform these actions, thus the default of allow. For multi-user systems
# the system administrator is considered capable enough to restrict what they
# see they need to.
#
# A WARNING to admins: do NOT allow access for users to this system remotely
# UNLESS you fully trust them or you have locked down permissions to halt/reboot
# suspend etc. here first. You have been warned.
#
# FORMAT:
#
# action: halt /sbin/shutdown -h now
# action: reboot /sbin/shutdown -r now
# action: suspend /etc/acpi/sleep.sh force
# action: hibernate /etc/acpi/hibernate.sh force
#
# user: username allow: halt reboot suspend hibernate
# group: groupname deny: *
# group: * deny: *
# user: * allow: suspend
# user: billy allow: halt reboot
# group: staff deny: halt suspend hibernate
#
# etc.
#
# user and group name can use glob matches (* == all for example) like the
# shell. as can action names allowed or denied.
action: halt /sbin/shutdown -h now
action: reboot /sbin/shutdown -r now
action: suspend sudo pm-suspend
action: hibernate sudo pm-hibernate
action: /bin/mount /bin/mount
action: /bin/umount /bin/umount
action: /usr/bin/eject /usr/bin/eject
# on FreeBSD use this instead of the above.
#action suspend /usr/sbin/zzz
# root is allowed to do anything - but it needs to be here explicitly anyway
user: root allow: *
# members of operator, staff and admin groups should be able to do all
group: operator allow: *
group: staff allow: *
group: admin allow: *
group: sys allow: *
group: wheel allow: *
group: adm allow: *
# common "user" groups for "console users" on desktops/laptops
group: dialout allow: *
group: disk allow: *
group: adm allow: *
group: cdrom allow: *
group: floppy allow: *
group: audio allow: *
group: dip allow: *
group: plugdev allow: *
group: netdev allow: *
group: bluetooth allow: *
group: video allow: *
group: voice allow: *
group: fax allow: *
group: tty allow: *
# put in a list of other users and groups here that are allowed or denied etc.
# e.g.
# user: myuser allow: *
# user: another allow: suspend hibernate
#
#
# uncomment this line to enable eeze mounting for users
# user: someuser allow: /bin/mount /bin/umount /usr/bin/eject
#
#
# deny everyone else by default
user: * deny: *
----------------------------------------------------------------------------------------------
In my computer I don't have the folder acpi in "etc"
What do I have to change in the file?
Thank you very much to anyone who responds
--------------------------------------------------------------------
Well, I'll leave this here in case it helps someone else (included me), but I "fixed" the problem writing in Terminology "sudo pm-suspend".
------------------------------------------------------------------------------------------------------------
Here maybe is the problem, i need to delete that sentence or put "0", I don't know, but this file is protected and I can't change the permissions or replace it with another file
/etc/systemd/logind.conf
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
#HandleLidSwitch=suspend
#HandleLidSwitchExternalPower=suspend
#HandleLidSwitchDocked=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#HoldoffTimeoutSec=30s
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RemoveIPC=yes
#InhibitorsMax=8192
#SessionsMax=8192
Any recommendation?
A fellow wrote this:
"hmm i never heard of that problem
but seems what we are using for suspend is having issues with your hardware
Moksha uses pm-utils by default
@.Nicolás. but you can change what is used
look at the file /etc/enlightenment/sysactions.conf
and change the line action: action: suspend ... YOU HAVE TO EDIT THIS FILE AS ROOT
to something that maybe works better on your system
i am uncertain what
i am currenty using on my laptop:
action: suspend /bin/systemctl suspend
becuase i want that one file to work with both moksha and enlightenment
another option is using acpi
it is prob installed but if you try using acpi I would install acpid
there are probably other options ...
sorry I can't be more specific"
---------------------------------------------------------------------------------------------------------------
EDITING THE FILE AS ROOT:
ENLIGHTENMENT SYSTEM ACTIONS CONFIGURATION
#
# This is a system configuration for allowing or denying certain users or
# groups to be able to do certain actions that involve system restricted
# actions such as halt, reboot, suspend, hibernate etc.
#
# This file is read in order from top to bottom - the first rule to MATCH
# will be used for a user or a group, and nothing after that is read.
#
# You must put all the ACTION definitons BEFORE user and group rule matches.
# Any action definitons after a rule match has been found will be ignored.
# This allows actions to be re-defined for different user groups, so matches
# so the command for an action can change for matches to the rules later on.
#
# Any user or group NOT matched by an allow or a deny will be ALLOWED to
# perform the action by default (system administrators should be aware of
# this and implement whatever policies they see fit). Generally speaking
# a user of a workstation, desktop or laptop is intended to have such abilities
# to perform these actions, thus the default of allow. For multi-user systems
# the system administrator is considered capable enough to restrict what they
# see they need to.
#
# A WARNING to admins: do NOT allow access for users to this system remotely
# UNLESS you fully trust them or you have locked down permissions to halt/reboot
# suspend etc. here first. You have been warned.
#
# FORMAT:
#
# action: halt /sbin/shutdown -h now
# action: reboot /sbin/shutdown -r now
# action: suspend /etc/acpi/sleep.sh force
# action: hibernate /etc/acpi/hibernate.sh force
#
# user: username allow: halt reboot suspend hibernate
# group: groupname deny: *
# group: * deny: *
# user: * allow: suspend
# user: billy allow: halt reboot
# group: staff deny: halt suspend hibernate
#
# etc.
#
# user and group name can use glob matches (* == all for example) like the
# shell. as can action names allowed or denied.
action: halt /sbin/shutdown -h now
action: reboot /sbin/shutdown -r now
action: suspend sudo pm-suspend
action: hibernate sudo pm-hibernate
action: /bin/mount /bin/mount
action: /bin/umount /bin/umount
action: /usr/bin/eject /usr/bin/eject
# on FreeBSD use this instead of the above.
#action suspend /usr/sbin/zzz
# root is allowed to do anything - but it needs to be here explicitly anyway
user: root allow: *
# members of operator, staff and admin groups should be able to do all
group: operator allow: *
group: staff allow: *
group: admin allow: *
group: sys allow: *
group: wheel allow: *
group: adm allow: *
# common "user" groups for "console users" on desktops/laptops
group: dialout allow: *
group: disk allow: *
group: adm allow: *
group: cdrom allow: *
group: floppy allow: *
group: audio allow: *
group: dip allow: *
group: plugdev allow: *
group: netdev allow: *
group: bluetooth allow: *
group: video allow: *
group: voice allow: *
group: fax allow: *
group: tty allow: *
# put in a list of other users and groups here that are allowed or denied etc.
# e.g.
# user: myuser allow: *
# user: another allow: suspend hibernate
#
#
# uncomment this line to enable eeze mounting for users
# user: someuser allow: /bin/mount /bin/umount /usr/bin/eject
#
#
# deny everyone else by default
user: * deny: *
----------------------------------------------------------------------------------------------
In my computer I don't have the folder acpi in "etc"
What do I have to change in the file?
Thank you very much to anyone who responds
--------------------------------------------------------------------
Well, I'll leave this here in case it helps someone else (included me), but I "fixed" the problem writing in Terminology "sudo pm-suspend".
------------------------------------------------------------------------------------------------------------
Here maybe is the problem, i need to delete that sentence or put "0", I don't know, but this file is protected and I can't change the permissions or replace it with another file
/etc/systemd/logind.conf
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
#HandleLidSwitch=suspend
#HandleLidSwitchExternalPower=suspend
#HandleLidSwitchDocked=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#HoldoffTimeoutSec=30s
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RemoveIPC=yes
#InhibitorsMax=8192
#SessionsMax=8192