Arch Linux

easydizzy

Member

Registered: 2017-12-22

Posts: 11

[Solved] wrong behavior on suspend/resume

Hi guys! When I resume from the suspended system, all the processes are gone. And if I had external display connected, the screen will go blank. I wonder how can I fix the problems? Thank you!

I tired to edit systemd suspend/resume service files according to this post, but it doesn't seem to work.

My logind.conf

[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
HandleLidSwitch=suspend
HandleLidSwitchDocked=suspend
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#HoldoffTimeoutSec=30s
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RemoveIPC=yes
#InhibitorsMax=8192
#SessionsMax=8192
#UserTasksMax=33%

edit:

<!--Please post information about your system -- is this a laptop or a desktop? What make/model? What graphics card? What driver? What processor? What DE/WM are you using? Do you use a login manager? What kernel are you booting? What are your kernel boot options?-->

I am running on a Thinkpad T470p laptop. I am using grub to boot and the desktop environment is GNOME (with gdm).

$ lspci | grep -e VGA -e 3D
00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04)

$ xdpyinfo | grep version
version number:    11.0
X.Org version: 1.19.6

$ uname -a                                      
Linux ie 4.15.3-2-ARCH #1 SMP PREEMPT Thu Feb 15 00:13:49 UTC 2018 x86_64 GNU/Linux

Last edited by easydizzy (2018-02-23 23:36:49)

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 13,720

Website

Re: [Solved] wrong behavior on suspend/resume

Please post information about your system -- is this a laptop or a desktop? What make/model? What graphics card? What driver? What processor? What DE/WM are you using? Do you use a login manager? What kernel are you booting? What are your kernel boot options?

Also post the full journal from an affected session.

And read http://www.catb.org/~esr/faqs/smart-questions.html

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,863

Re: [Solved] wrong behavior on suspend/resume

all the processes are gone

Sounds more like a failed S4 than an S3 problem.
Most likely causes:
a) windows fastboot
b) bad resume device (configuration)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

easydizzy

Member

Registered: 2017-12-22

Posts: 11

Re: [Solved] wrong behavior on suspend/resume

Please post information about your system -- is this a laptop or a desktop? What make/model? What graphics card? What driver? What processor? What DE/WM are you using? Do you use a login manager? What kernel are you booting? What are your kernel boot options?

Also post the full journal from an affected session.

And read http://www.catb.org/~esr/faqs/smart-questions.html

Sorry about that, I have edited the question accordingly. I changed gnome session from wayland to xorg. It seems solved the problem of suspend. However, when I close the lid and reopen it after ~30 seconds, the screen couldn't display a thing.

edit:

journalctl --unit=systemd-logind

...skipping...
Feb 23 20:46:06 ie systemd-logind[636]: Watching system buttons on /dev/input/event5 (Logitech USB Receiver)
Feb 23 20:46:06 ie systemd-logind[636]: Watching system buttons on /dev/input/event6 (Topre Corporation HHKB Professional)
Feb 23 20:46:06 ie systemd-logind[636]: Watching system buttons on /dev/input/event3 (AT Translated Set 2 keyboard)
Feb 23 20:46:06 ie systemd-logind[636]: Watching system buttons on /dev/input/event7 (ThinkPad Extra Buttons)
Feb 23 20:46:06 ie systemd[1]: Started Login Service.
Feb 23 20:46:07 ie systemd-logind[636]: New session c1 of user gdm.
Feb 23 20:46:14 ie systemd-logind[636]: New session c2 of user peter.
Feb 23 21:07:41 ie systemd-logind[636]: Lid closed.
Feb 23 21:07:41 ie systemd-logind[636]: Suspending...
Feb 23 21:07:54 ie systemd-logind[636]: Operation 'sleep' finished.
Feb 23 21:08:14 ie systemd-logind[636]: Suspending...
Feb 23 21:08:17 ie systemd-logind[636]: Operation 'sleep' finished.
Feb 23 21:08:46 ie systemd-logind[636]: Suspending...
Feb 23 21:08:49 ie systemd-logind[636]: Operation 'sleep' finished.
Feb 23 21:09:02 ie systemd-logind[636]: Lid opened.
Feb 23 21:09:25 ie systemd-logind[636]: Power key pressed.
Feb 23 21:09:29 ie systemd-logind[636]: Operation 'sleep' finished.

And there doesn't seem to be anything wrong with gnome-session

$  journalctl -b /usr/bin/gnome-session 

-- Logs begin at Thu 2018-02-22 19:43:17 CST, end at Fri 2018-02-23 21:29:46 CST. --
-- No entries --

Last edited by easydizzy (2018-02-23 13:30:42)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,863

Re: [Solved] wrong behavior on suspend/resume

post the full journal from an affected session.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

easydizzy

Member

Registered: 2017-12-22

Posts: 11

Re: [Solved] wrong behavior on suspend/resume

Sorry but I am not sure which journal command to get affected session other than check `journalctl --unit=systemd-logind` because if I do suspend then when I resume, the screen goes black and I need to manually close the laptop by pressing the power button.

The recent  log looks like

-- Reboot --
Feb 23 20:46:06 ie systemd[1]: Starting Login Service...
Feb 23 20:46:06 ie systemd-logind[636]: New seat seat0.
Feb 23 20:46:06 ie systemd-logind[636]: Watching system buttons on /dev/input/event2 (Power Button)
Feb 23 20:46:06 ie systemd-logind[636]: Watching system buttons on /dev/input/event1 (Lid Switch)
Feb 23 20:46:06 ie systemd-logind[636]: Watching system buttons on /dev/input/event0 (Sleep Button)
Feb 23 20:46:06 ie systemd-logind[636]: Watching system buttons on /dev/input/event5 (Logitech USB Receiver)
Feb 23 20:46:06 ie systemd-logind[636]: Watching system buttons on /dev/input/event6 (Topre Corporation HHKB Professional)
Feb 23 20:46:06 ie systemd-logind[636]: Watching system buttons on /dev/input/event3 (AT Translated Set 2 keyboard)
Feb 23 20:46:06 ie systemd-logind[636]: Watching system buttons on /dev/input/event7 (ThinkPad Extra Buttons)
Feb 23 20:46:06 ie systemd[1]: Started Login Service.
Feb 23 20:46:07 ie systemd-logind[636]: New session c1 of user gdm.
Feb 23 20:46:14 ie systemd-logind[636]: New session c2 of user peter.
Feb 23 21:07:41 ie systemd-logind[636]: Lid closed.
Feb 23 21:07:41 ie systemd-logind[636]: Suspending...
Feb 23 21:07:54 ie systemd-logind[636]: Operation 'sleep' finished.
Feb 23 21:08:14 ie systemd-logind[636]: Suspending...
Feb 23 21:08:17 ie systemd-logind[636]: Operation 'sleep' finished.
Feb 23 21:08:46 ie systemd-logind[636]: Suspending...
Feb 23 21:08:49 ie systemd-logind[636]: Operation 'sleep' finished.
Feb 23 21:09:02 ie systemd-logind[636]: Lid opened.
Feb 23 21:09:25 ie systemd-logind[636]: Power key pressed.
Feb 23 21:09:29 ie systemd-logind[636]: Operation 'sleep' finished.
-- Reboot --
Feb 23 21:10:43 ie systemd[1]: Starting Login Service...
Feb 23 21:10:43 ie systemd-logind[632]: New seat seat0.
Feb 23 21:10:43 ie systemd-logind[632]: Watching system buttons on /dev/input/event2 (Power Button)
Feb 23 21:10:43 ie systemd-logind[632]: Watching system buttons on /dev/input/event1 (Lid Switch)
Feb 23 21:10:43 ie systemd-logind[632]: Watching system buttons on /dev/input/event0 (Sleep Button)
Feb 23 21:10:43 ie systemd-logind[632]: Watching system buttons on /dev/input/event5 (Logitech USB Receiver)
Feb 23 21:10:43 ie systemd-logind[632]: Watching system buttons on /dev/input/event6 (Topre Corporation HHKB Professional)
Feb 23 21:10:43 ie systemd-logind[632]: Watching system buttons on /dev/input/event3 (AT Translated Set 2 keyboard)
Feb 23 21:10:43 ie systemd-logind[632]: Watching system buttons on /dev/input/event7 (ThinkPad Extra Buttons)
Feb 23 21:10:43 ie systemd[1]: Started Login Service.
Feb 23 21:10:44 ie systemd-logind[632]: New session c1 of user gdm.
Feb 23 21:10:51 ie systemd-logind[632]: New session c2 of user peter.
Feb 23 21:40:20 ie systemd-logind[632]: Operation 'sleep' finished.
-- Reboot --
Feb 23 21:47:45 ie systemd[1]: Starting Login Service...
Feb 23 21:47:45 ie systemd-logind[635]: New seat seat0.
Feb 23 21:47:45 ie systemd-logind[635]: Watching system buttons on /dev/input/event2 (Power Button)
Feb 23 21:47:45 ie systemd-logind[635]: Watching system buttons on /dev/input/event1 (Lid Switch)
Feb 23 21:47:45 ie systemd-logind[635]: Watching system buttons on /dev/input/event0 (Sleep Button)
Feb 23 21:47:45 ie systemd-logind[635]: Watching system buttons on /dev/input/event5 (Logitech USB Receiver)
Feb 23 21:47:45 ie systemd-logind[635]: Watching system buttons on /dev/input/event6 (Topre Corporation HHKB Professional)
Feb 23 21:47:45 ie systemd-logind[635]: Watching system buttons on /dev/input/event3 (AT Translated Set 2 keyboard)
Feb 23 21:47:45 ie systemd-logind[635]: Watching system buttons on /dev/input/event7 (ThinkPad Extra Buttons)
Feb 23 21:47:45 ie systemd[1]: Started Login Service.
Feb 23 21:47:46 ie systemd-logind[635]: New session c1 of user gdm.
Feb 23 21:47:58 ie systemd-logind[635]: New session c2 of user peter.
lines 186-240/240 (END)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,435

Re: [Solved] wrong behavior on suspend/resume

https://wiki.archlinux.org/index.php/Sy … ing_output the first example.

easydizzy

Member

Registered: 2017-12-22

Posts: 11

Re: [Solved] wrong behavior on suspend/resume

https://wiki.archlinux.org/index.php/Sy … ing_output the first example.

Thank you. So the log from the crash case when I resumed from suspension

Feb 23 18:32:17 ie systemd-logind[24686]: New session c2 of user peter.
Feb 23 18:32:17 ie systemd-logind[24686]: New session c1 of user gdm.
Feb 23 18:32:18 ie gnome-shell[9379]: Object St.BoxLayout (0x55ad435fce00), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C c
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: == Stack trace for context 0x55ad41a7d000 ==
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #0 0x7fffa1b98650 I   resource:///org/gnome/gjs/modules/overrides/GObject.js:452 (0x7fac380d2560 @ 25)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #1 0x55ad41c9f8d0 i   /usr/share/gnome-shell/extensions/workspaces-to-dock@passingthru67.gmail.com/convenience.js:124 (0x7fabec10a340 @ 91)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #2 0x7fffa1b99290 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fac380c2bc0 @ 71)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #3 0x55ad41c9f848 i   /usr/share/gnome-shell/extensions/workspaces-to-dock@passingthru67.gmail.com/dockedWorkspaces.js:1548 (0x7fabec124d58 @ 60)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #4 0x7fffa1b99ed0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fac380c2bc0 @ 71)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #5 0x7fffa1b99f10 I   self-hosted:915 (0x7fac380ee5e8 @ 367)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #6 0x7fffa1b99f90 I   resource:///org/gnome/gjs/modules/signals.js:126 (0x7fac380e2b38 @ 386)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #7 0x55ad41c9f7c0 i   /home/peter/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/docking.js:1656 (0x7fabf24332b8 @ 52)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #8 0x7fffa1b9abd0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fac380c2bc0 @ 71)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #9 0x7fffa1b9ac10 I   self-hosted:915 (0x7fac380ee5e8 @ 367)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: == Stack trace for context 0x55ad41a7d000 ==
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #0 0x7fffa1b98650 I   resource:///org/gnome/gjs/modules/overrides/GObject.js:452 (0x7fac380d2560 @ 25)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #1 0x55ad41c9f8d0 i   /usr/share/gnome-shell/extensions/workspaces-to-dock@passingthru67.gmail.com/convenience.js:124 (0x7fabec10a340 @ 91)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #2 0x7fffa1b99290 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fac380c2bc0 @ 71)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #3 0x55ad41c9f848 i   /usr/share/gnome-shell/extensions/workspaces-to-dock@passingthru67.gmail.com/dockedWorkspaces.js:1548 (0x7fabec124d58 @ 60)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #4 0x7fffa1b99ed0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fac380c2bc0 @ 71)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #5 0x7fffa1b99f10 I   self-hosted:915 (0x7fac380ee5e8 @ 367)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #6 0x7fffa1b99f90 I   resource:///org/gnome/gjs/modules/signals.js:126 (0x7fac380e2b38 @ 386)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #7 0x55ad41c9f7c0 i   /home/peter/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/docking.js:1656 (0x7fabf24332b8 @ 52)
Feb 23 18:32:18 ie gnome-shell[9379]: gsignal.c:2641: instance '0x55ad435fce00' has no handler with id '13180'
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #8 0x7fffa1b9abd0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fac380c2bc0 @ 71)
Feb 23 18:32:18 ie org.gnome.Shell.desktop[9379]: #9 0x7fffa1b9ac10 I   self-hosted:915 (0x7fac380ee5e8 @ 367)
Feb 23 18:32:18 ie gnome-shell[9379]: Object St.BoxLayout (0x55ad435fce00), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C c
Feb 23 18:32:18 ie gnome-shell[9379]: gsignal.c:2641: instance '0x55ad435fce00' has no handler with id '13181'
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event2: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event9: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event1: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event0: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event4: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event5: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event6: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event19: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event11: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event12: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event13: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event14: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event15: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event16: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event17: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event3: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event18: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event20: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken
Feb 23 18:32:18 ie gnome-shell[9379]: Could not open device /dev/input/event7: GDBus.Error:org.freedesktop.login1.DeviceIsTaken: Device already taken

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,435

Re: [Solved] wrong behavior on suspend/resume

You should post the entire output when asked for the entire output. However it seems relatively clear that you are using some old extension that breaks horribly when the system goies to sleep. Disable the workspace-to-dock extension. In fact disable all extensions. If it doesn't break anymore add them one by one, maybe there are others that are failing. Then don't use them or check if they have been updated.