Can't suspend system

atomAltera · 2015-12-26 11:30:41

Hello. Sometimes the system is not going to sleep, just black screen appears, and after mouse move appears login screen; After this commands like sudo reboot fails with error "Failed to start reboot.target: Transaction is destructive."

But if I do sudo reboot -f the system suspends, but after wakeup continues reboot; How can I fix it?

Horizon_Brave · 2015-12-26 16:11:34

Does the command systemctl reboot work?

atomAltera · 2015-12-26 16:16:00

Horizon_Brave wrote:

Does the command systemctl reboot work?

No, nothing happens.

Unfortunately I can't reproduce the error. Can you write me a list of actions to do when it happens again?

paxmark1 · 2015-12-26 16:19:02

https://www.digitalocean.com/community/ … stemd-logs

and man journalctl are sources to learn to use the systemd logs to gather more information on problems.

man systemctl looking at (towards the end) suspend hibernate hybrid-sleep.

possible try sudo systemctl suspend and systemctl hibernate and sustemctl hybrid-sleep.

post inxi -MS

Head_on_a_Stick · 2015-12-26 16:31:51

atomAltera wrote:

Sometimes the system is not going to sleep, just black screen appears, and after mouse move appears login screen; After this commands like sudo reboot fails with error "Failed to start reboot.target: Transaction is destructive."

That error message shows because systemd is still trying to suspend your machine and the reboot instruction conflicts with this.

As paxmark1 says, the next time this happens look at the journal

atomAltera · 2015-12-26 16:34:04

I wrote the script:

#!/bin/sh


bl-lock &

(sleep 2s; sudo systemctl suspend) &

and set sudo systemctl suspend to run without password. In case of some problems, I will write again.

But I still interested in why the default method does not work properly.

Last edited by atomAltera (2015-12-26 16:34:52)

unklar · 2015-12-26 17:57:40

All my systems with systemd

-mageia
-siduction
-arch
-bunsenlabs
-kaOS

have the same behavior:
console/terminal on

systemctl suspend

and the computer goes to sleep.
Waking again with the start button.

What do you want always with this stupid sudo command forward?
The ordinary user shuts down the thing!

Head_on_a_Stick · 2015-12-26 19:05:28

unklar wrote:

What do you want always with this stupid sudo command forward?
The ordinary user shuts down the thing!

^ This.

The `systemctl` command allows the normal user to suspend, shut down & reboot.

See https://wiki.archlinux.org/index.php/Sy … management

atomAltera · 2015-12-29 21:11:37

Ok, here is journalctl's output

Dec 30 01:02:02 altera-desktop NetworkManager[624]: <info> sleep requested (sleeping: no  enabled: yes)
Dec 30 01:02:02 altera-desktop NetworkManager[624]: <info> sleeping...
Dec 30 01:02:02 altera-desktop NetworkManager[624]: <info> NetworkManager state is now ASLEEP
Dec 30 01:02:02 altera-desktop systemd-sleep[12887]: Suspending system...
Dec 30 01:02:02 altera-desktop kernel: PM: Syncing filesystems ... done.
Dec 30 01:02:02 altera-desktop kernel: PM: Preparing system for mem sleep
Dec 30 01:02:03 altera-desktop acpid[710]: client 753[0:0] has disconnected
Dec 30 01:02:03 altera-desktop acpid[710]: client connected from 12886[0:0]
Dec 30 01:02:03 altera-desktop acpid[710]: 1 client rule loaded
Dec 30 01:02:03 altera-desktop lightdm[732]: ** (process:12894): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Dec 30 01:02:03 altera-desktop lightdm[12894]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Dec 30 01:02:03 altera-desktop systemd-logind[633]: New session c20 of user lightdm.
Dec 30 01:02:03 altera-desktop org.a11y.Bus[12903]: Activating service name='org.a11y.atspi.Registry'
Dec 30 01:02:03 altera-desktop org.a11y.Bus[12903]: Successfully activated service 'org.a11y.atspi.Registry'
Dec 30 01:02:03 altera-desktop org.a11y.atspi.Registry[12909]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Dec 30 01:02:11 altera-desktop lightdm[732]: ** (process:12917): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Dec 30 01:02:11 altera-desktop lightdm[732]: ** (lightdm:732): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: Interrupted system call
Dec 30 01:02:11 altera-desktop lightdm[12894]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Dec 30 01:02:11 altera-desktop org.a11y.atspi.Registry[12909]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Dec 30 01:02:11 altera-desktop org.a11y.Bus[12903]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Dec 30 01:02:11 altera-desktop acpid[710]: client 12886[0:0] has disconnected
Dec 30 01:02:11 altera-desktop acpid[710]: client connected from 753[0:0]
Dec 30 01:02:11 altera-desktop acpid[710]: 1 client rule loaded
Dec 30 01:02:14 altera-desktop systemd-logind[633]: Removed session c20.
Dec 30 01:02:45 altera-desktop sudo[12929]: altera : TTY=pts/0 ; PWD=/home/altera ; USER=root ; COMMAND=/bin/journalctl
Dec 30 01:02:45 altera-desktop sudo[12929]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 30 01:04:28 altera-desktop sudo[12929]: pam_unix(sudo:session): session closed for user root
Dec 30 01:04:31 altera-desktop sudo[12951]: altera : TTY=pts/0 ; PWD=/home/altera ; USER=root ; COMMAND=/bin/journalctl
Dec 30 01:04:31 altera-desktop sudo[12951]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 30 01:04:36 altera-desktop sudo[12951]: pam_unix(sudo:session): session closed for user root
Dec 30 01:05:18 altera-desktop sudo[12955]: altera : TTY=pts/0 ; PWD=/home/altera ; USER=root ; COMMAND=/bin/journalctl
Dec 30 01:05:18 altera-desktop sudo[12955]: pam_unix(sudo:session): session opened for user root by (uid=0)

I used standard exit dialog to put sustem into sleep mode. Can you see any problems?

Here is output of systemctl suspend after that:

Failed to execute operation: There's already a shutdown or sleep operation in progress
Failed to start suspend.target: Access denied

And /lib/systemd/systemd-sleep suspend process is hanging in processes;

Head_on_a_Stick · 2015-12-30 01:05:08

@atomAltera:

You have posted this in Help & Support (Other), which operating system and distribution (if any) are you using?

atomAltera · 2015-12-30 06:02:29

Head_on_a_Stick wrote:

@atomAltera:
You have posted this in Help & Support (Other), which operating system and distribution (if any) are you using?

Last BunsenLabs (3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u1 (2015-12-14) x86_64 GNU/Linux)

I had the same problems with Crunchbang, but match rarer. Then I upgraded my hardware. Now I have:

Motherboard: Asus Z97 PRO
CPU: i5-4590
SSD: Kingston SSDNow
Video: Nvidia 8600GT (Has not been upgraded, official Nvidia driver is installed).

Last edited by atomAltera (2015-12-30 06:15:06)

Head_on_a_Stick · 2015-12-30 11:11:54

I'm moving this to Basic Help & Support

All I can think to suggest here is to try a newer kernel version from the jessie-backports repository.

If you want to try this, follow the instructions here to enable jessie-backports:
https://wiki.debian.org/Backports

Then install the new kernel & headers with:

sudo apt-get install -t jessie-backports linux-image-amd64 linux-headers-amd64

When the system is rebooted, you will have options to boot into either the original (3.16) or the new (4.3) kernels so that you can still run the old kernel if there are any problems.

The only caveat here is your video driver.

When you say "official", do you mean that you installed the NVIDIA drivers from the Debian repositories?
https://wiki.debian.org/NvidiaGraphicsDrivers

If you used a script to install the drivers, take a moment to read this:
https://wiki.debian.org/DontBreakDebian … ll_scripts

Note that the drivers from Debian are supplied with a kernel post-install script that will automatically rebuild the kernel modules after kernel upgrades (or changes, in this case).

For non-Debian drivers, you will have to re-run the installation process to re-build the required modules for the new kernel.

unklar · 2015-12-30 18:06:32

I do not know how you have created journalctl ...

It looks like that sudo is on this system also logged.

Try it:
-two consoles
-the one as root with the command

journalctl -af

(leave open) or

journalctl -af | tee journal.log

-the second as a user with the command

systemctl suspend

execute

atomAltera · 2015-12-30 18:31:12

Head_on_a_Stick wrote:

I'm moving this to Basic Help & Support
All I can think to suggest here is to try a newer kernel version from the jessie-backports repository.
If you want to try this, follow the instructions here to enable jessie-backports:
https://wiki.debian.org/Backports
Then install the new kernel & headers with:
sudo apt-get install -t jessie-backports linux-image-amd64 linux-headers-amd64
When the system is rebooted, you will have options to boot into either the original (3.16) or the new (4.3) kernels so that you can still run the old kernel if there are any problems.
The only caveat here is your video driver.
When you say "official", do you mean that you installed the NVIDIA drivers from the Debian repositories?
https://wiki.debian.org/NvidiaGraphicsDrivers
If you used a script to install the drivers, take a moment to read this:
https://wiki.debian.org/DontBreakDebian … ll_scripts
Note that the drivers from Debian are supplied with a kernel post-install script that will automatically rebuild the kernel modules after kernel upgrades (or changes, in this case).
For non-Debian drivers, you will have to re-run the installation process to re-build the required modules for the new kernel.

I have nVidia driver from nVidia official website (NVIDIA-Linux-x86_64-340.96.run)

I have installed 4.2 kernel, as you told me, from backport, and reinstalled the same driver;

Linux altera-desktop 4.2.0-0.bpo.1-amd64 #1 SMP Debian 4.2.6-3~bpo8+2 (2015-12-14) x86_64 GNU/Linux

unklar wrote:

I do not know how you have created journalctl ...
It looks like that sudo is on this system also logged.
Try it:
-two consoles
-the one as root with the command
journalctl -af
(leave open) or
journalctl -af | tee journal.log
-the second as a user with the command
systemctl suspend
execute
http://jupiter.workupload.com/image/KQDGmPqo

When I run journalctl as normal user, the error No journal files were found. is thrown to me;

I will post output journalctl -af as soon as the same situation repeats

damo · 2015-12-30 19:41:59

NB If you have the non-Debian nVidia driver you need to rebuild the kernel module again after a kernel upgrade.

#1 2015-12-26 11:30:41

Can't suspend system

#2 2015-12-26 16:11:34

Re: Can't suspend system

#3 2015-12-26 16:16:00

Re: Can't suspend system

#4 2015-12-26 16:19:02

Re: Can't suspend system

#5 2015-12-26 16:31:51

Re: Can't suspend system

#6 2015-12-26 16:34:04

Re: Can't suspend system

#7 2015-12-26 17:57:40

Re: Can't suspend system

#8 2015-12-26 19:05:28

Re: Can't suspend system

#9 2015-12-29 21:11:37

Re: Can't suspend system

#10 2015-12-30 01:05:08

Re: Can't suspend system

#11 2015-12-30 06:02:29

Re: Can't suspend system

#12 2015-12-30 11:11:54

Re: Can't suspend system

#13 2015-12-30 18:06:32

Re: Can't suspend system

#14 2015-12-30 18:31:12

Re: Can't suspend system

#15 2015-12-30 19:41:59

Re: Can't suspend system

Board footer