Steam screws up suspend

Hello, I'm using Manjaro XFCE and, after starting the Steam launcher, my computer seems to fail to suspend but light-locker does lock the screen. Trying to suspend again results in this error notification from xfce4-power-manager:

GDBus.Error:org.freedesktop.login1.OperationInProgress: There's already a shutdown or sleep operation in progress

I also get a similar error with systemctl suspend, systemctl reboot, (etc). I can't find a way to fix this other than running sudo reboot, so what can be done? From what I can tell, this might have something to do with inhibiting suspend or something, but I have no real idea.

Here is the hardware info of my laptop if that helps:

$ inxi -Fxxxz --no-hostname   
System:
  Kernel: 5.6.19-2-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0 
  Desktop: Xfce 4.14.2 tk: Gtk 3.24.20 info: xfce4-panel, plank wm: xfwm4 
  dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:
  Type: Laptop System: Dell product: XPS 15 9570 v: N/A serial: <filter> 
  Chassis: type: 10 serial: <filter> 
  Mobo: Dell model: 0YYW9X v: A04 serial: <filter> UEFI: Dell v: 1.16.2 
  date: 04/21/2020 
Battery:
  ID-1: BAT0 charge: 71.2 Wh condition: 87.2/97.0 Wh (90%) volts: 12.3/11.4 
  model: SMP DELL GPM0365 type: Li-ion serial: <filter> status: Discharging 
CPU:
  Topology: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP 
  arch: Kaby Lake rev: A L2 cache: 9216 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 52815 
  Speed: 900 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 900 2: 900 
  3: 900 4: 900 5: 900 6: 900 7: 900 8: 900 9: 900 10: 900 11: 900 12: 900 
Graphics:
  Device-1: Intel UHD Graphics 630 vendor: Dell driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:3e9b 
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: nvidia 
  v: 440.100 bus ID: 01:00.0 chip ID: 10de:1c8c 
  Display: x11 server: X.Org 1.20.8 driver: modesetting,nvidia 
  alternate: fbdev,intel,nouveau,nv,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 20.1.3 
  direct render: Yes 
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Dell driver: snd_hda_intel 
  v: kernel bus ID: 00:1f.3 chip ID: 8086:a348 
  Sound Server: ALSA v: k5.6.19-2-MANJARO 
Network:
  Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter 
  vendor: Bigfoot Networks driver: ath10k_pci v: kernel port: 3000 
  bus ID: 3b:00.0 chip ID: 168c:003e 
  IF: wlp59s0 state: up mac: <filter> 
  Device-2: Qualcomm Atheros type: USB driver: btusb bus ID: 1-4:2 
  chip ID: 0cf3:e301 
Drives:
  Local Storage: total: 238.47 GiB used: 26.72 GiB (11.2%) 
  ID-1: /dev/nvme0n1 vendor: Toshiba model: KXG50ZNV256G NVMe 256GB 
  size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: AADA4104 
  scheme: GPT 
Partition:
  ID-1: / size: 34.18 GiB used: 12.03 GiB (35.2%) fs: btrfs 
  dev: /dev/nvme0n1p2 
  ID-2: /home size: 184.58 GiB used: 14.69 GiB (8.0%) fs: ext4 
  dev: /dev/dm-0 
  ID-3: swap-1 size: 15.63 GiB used: 0 KiB (0.0%) fs: swap 
  dev: /dev/nvme0n1p4 
Sensors:
  System Temperatures: cpu: 49.0 C mobo: N/A 
  Fan Speeds (RPM): cpu: 0 fan-2: 0 
Info:
  Processes: 322 Uptime: 3m Memory: 15.31 GiB used: 1.29 GiB (8.4%) 
  Init: systemd v: 245 Compilers: gcc: 10.1.0 Shell: zsh v: 5.8 
  running in: xfce4-terminal inxi: 3.0.37 

PS: I would have my PC info here, but I am currently out of power as well as with poor internet access.

Unrelated to your issue, but that kernel is EOL.

I might be wrong, but steam like wine are not well integrated with the power management sleep/suspend/hibernate features and will keep some of their services alive, hence the sleep/suspend will fail.
Make sure the suspend works with no applications opened, then try it with some native linux applications running. If that works then avoid to sleep/suspend the system while steam is running.

2 Likes

Thanks for the note about my kernel! For some reason I always thought linux56 was LTS...

Anyways, I switched to Cinnamon and the issue isn't present, so I think it might be an XFCE problem specifically. This post seems to confirm that...

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by