Hi,
a recent update has left me without the sleep and hibernate buttons on logout. I get a message instead: warning: suspend to ram disabled by administrator
I can't seem to find any config file for this.
Suspend still works when invoked from the console.
Any hints on how to get this back?
Thanks, Mike
Anno domini 2019 Fri, 31 May 10:48:03 +0200 de.bug scripsit:
Hi,
a recent update has left me without the sleep and hibernate buttons on logout. I get a message instead: warning: suspend to ram disabled by administrator
I can't seem to find any config file for this.
Suspend still works when invoked from the console.
Any hints on how to get this back?
Which distribution are you using?
Thanks, Mike
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Anno domini 2019 Fri, 31 May 10:48:03 +0200 de.bug scripsit:
Hi,
a recent update has left me without the sleep and hibernate buttons on logout. I get a message instead: warning: suspend to ram disabled by administrator
I can't seem to find any config file for this.
Suspend still works when invoked from the console.
Any hints on how to get this back?
Which distribution are you using?
ExeGnuLinux (Devuan + Trinity), R14.0.6, 3.16.0-6-amd64, x86_64
Anno domini 11:06:31 Fri, 31 May 2019 +0200 (CEST) de.bug@t-online.de scripsit:
Anno domini 2019 Fri, 31 May 10:48:03 +0200 de.bug scripsit:
Hi,
a recent update has left me without the sleep and hibernate buttons on logout. I get a message instead: warning: suspend to ram disabled by administrator
I can't seem to find any config file for this.
Suspend still works when invoked from the console.
Any hints on how to get this back?
Which distribution are you using?
ExeGnuLinux (Devuan + Trinity), R14.0.6, 3.16.0-6-amd64, x86_64
Ah, ok. That distribution is based on jessie, which has been moved to "archive" just some weeks ago. If I recall correctly, backports is gone now, but the patched consolekit/policycit was in backports. You might want to upgrade to ascii (stable) and then to beowulf.
Nik
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
You can still use Jessie and backports you just have to change a couple of things. I take no credit for this I found the fix online and am using it on my Jessie box. Change your sources to: deb http://deb.debian.org/debian jessie main deb http://deb.debian.org/debian stable-updates main deb http://archive.debian.org/debian/ jessie-backports main You can add contrib and non-free if you want Then run: echo "Acquire::Check-Valid-Until false;" | sudo tee -a /etc/apt/apt.conf.d/10-nocheckvalid Jessie sources will still work.
Now you are running Devuan which should not have been affected by the change to the best of my knowlege. According to: https://devuan.org/os/etc/apt/sources.list You need to add the following deb http://deb.devuan.org/merged jessie-backports main deb-src http://deb.devuan.org/merged jessie-backports main
In both cases you can install from backports with: apt-get install -t jessie-backports [name-of-package]
On 05/31/2019 03:48 AM, de.bug wrote:
Hi,
a recent update has left me without the sleep and hibernate buttons on logout. I get a message instead: warning: suspend to ram disabled by administrator
I can't seem to find any config file for this.
Suspend still works when invoked from the console.
Any hints on how to get this back?
Thanks, Mike
This isn't trinity specific. If you check immediately after you start your desktop all options will be there. Later (I suspect after a dpms power-off event), the options for sleep and suspend are no longer shown. (I suspect some systemd/kernel reporting to the available states after this occurs is causing the problem)
I have noticed this with KDE3 as well.
-
David C. Rankin -
de.bug -
de.bug＠t-online.de
-
Dr. Nikolaus Klepp -
Pisini, John