Keyboard shortcuts not working after hybrid sleep

rocket19 · 31 October 2020 12:46

Hi all,

Running Manjaro XFCE on my old ASUS laptop. Once I am booted into Manjaro it runs very nicely.

However, after either:

I would guess about 10minutes+ of inactivity, or
Putting the laptop into Hybrid Sleep mode, and then logging back in,

the computer seems to be working harder (the fan speed increases, and looking at htop shows that one core is working at around 100%) and also my keyboard application shortcuts (Ctrl + Alt + T, Ctrl + Alt + X, …etc…) and keyboard volume controls (both on USB KB and the laptop KB itself) don’t work or take awhile before they randomly start working again.

Also returning from the sleep state, usually whatever applications I had open would become unresponsive, so I close them and re-open them and they run fine.

Anything I can look into to try to remedy this?

I’m a pretty basic user but am learning much as I go with Linux. Thanks!!

inxi -Fazy returns:

System:
  Kernel: 5.8.16-2-MANJARO x86_64 bits: 64 compiler: N/A 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 
  root=UUID=3aa0ac64-1933-4b2b-b9c7-d7d5cdbb7a48 rw quiet apparmor=1 
  security=apparmor resume=UUID=f9620ed0-383b-482f-9df0-473fc0c365f5 
  udev.log_priority=3 
  Desktop: Xfce 4.14.2 tk: Gtk 3.24.20 info: xfce4-panel wm: xfwm4 
  dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:
  Type: Laptop System: ASUSTeK product: N56VZ v: 1.0 serial: <filter> 
  Mobo: ASUSTeK model: N56VZ v: 1.0 serial: <filter> UEFI: American Megatrends 
  v: N56VZ.215 date: 11/02/2012 
Battery:
  ID-1: BAT0 charge: 22.0 Wh condition: 22.5/57.7 Wh (39%) volts: 11.1/11.1 
  model: ASUSTeK N56--52 type: Li-ion serial: N/A status: Unknown cycles: 577 
CPU:
  Topology: Quad Core model: Intel Core i7-3630QM bits: 64 type: MT MCP 
  arch: Ivy Bridge family: 6 model-id: 3A (58) stepping: 9 microcode: 21 
  L2 cache: 6144 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 38334 
  Speed: 2794 MHz min/max: 1200/3400 MHz Core speeds (MHz): 1: 2940 2: 2479 
  3: 3196 4: 3197 5: 2738 6: 2952 7: 3173 8: 3210 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: conditional, RSB filling 
  Type: srbds status: Vulnerable: No microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel 3rd Gen Core processor Graphics vendor: ASUSTeK N56VZ 
  driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0166 
  Device-2: NVIDIA GK107M [GeForce GT 650M] driver: N/A 
  alternate: nouveau, nvidia_drm, nvidia bus ID: 01:00.0 chip ID: 10de:0fd1 
  Device-3: Sunplus Innovation Asus Webcam type: USB driver: uvcvideo 
  bus ID: 1-1.3:4 chip ID: 1bcf:2883 
  Display: x11 server: X.Org 1.20.9 driver: intel display ID: :0.0 screens: 1 
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
  s-diag: 582mm (22.9") 
  Monitor-1: LVDS1 res: 1920x1080 hz: 60 dpi: 143 size: 340x190mm (13.4x7.5") 
  diag: 389mm (15.3") 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2) 
  v: 4.2 Mesa 20.1.8 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio 
  vendor: ASUSTeK N56VZ driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  chip ID: 8086:1e20 
  Device-2: NVIDIA GK107 HDMI Audio driver: snd_hda_intel v: kernel 
  bus ID: 01:00.1 chip ID: 10de:0e1b 
  Sound Server: ALSA v: k5.8.16-2-MANJARO 
Network:
  Device-1: Intel Centrino Wireless-N 2230 driver: iwlwifi v: kernel 
  port: f040 bus ID: 03:00.0 chip ID: 8086:0887 
  IF: wlp3s0 state: up mac: <filter> 
  Device-2: Qualcomm Atheros AR8161 Gigabit Ethernet vendor: ASUSTeK N56VZ 
  driver: alx v: kernel port: d000 bus ID: 04:00.0 chip ID: 1969:1091 
  IF: enp4s0 state: down mac: <filter> 
Drives:
  Local Storage: total: 698.64 GiB used: 57.95 GiB (8.3%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/sda vendor: Seagate model: ST750LM022 HN-M750MBB size: 698.64 GiB 
  block size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s 
  rotation: 5400 rpm serial: <filter> rev: 0001 scheme: GPT 
Partition:
  ID-1: / raw size: 689.54 GiB size: 677.72 GiB (98.29%) 
  used: 57.95 GiB (8.6%) fs: ext4 dev: /dev/sda2 
Swap:
  Kernel: swappiness: 10 (default 60) cache pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 8.80 GiB used: 488 KiB (0.0%) 
  priority: -2 dev: /dev/sda3 
Sensors:
  System Temperatures: cpu: 68.0 C mobo: N/A 
  Fan Speeds (RPM): cpu: 2800 
Info:
  Processes: 228 Uptime: 3h 50m Memory: 7.66 GiB used: 1.55 GiB (20.2%) 
  Init: systemd v: 246 Compilers: gcc: 10.2.0 Packages: pacman: 1177 lib: 348 
  flatpak: 0 Shell: Bash v: 5.0.18 running in: xfce4-terminal inxi: 3.1.05

Fabby · 1 November 2020 14:14

When it happens, please do the following:

journalctl --system --boot=0 | grep "suspend entry"
journalctl --system --boot=0 | grep "suspend exit"

then have a look at the begin and end time and post the output of:

journalctl --system --boot=0 --since "YYYY-MM-DD HH:MM:SS" --until "YYYY-MM-DD HH:MM:SS"

where obviously --since is the datetime of suspend entry and --until is the datetime of suspension exit.

rocket19 · 2 November 2020 11:38

Thanks for your reply @Fabby.

So I put my laptop into hybrid sleep, and then turned it back on. It did the same as usual (unresponsive programs, keyboard shortcuts not working, …etc…)

I did those first two journalctl commands, and then I entered the third one, and it returned this:
Failed to parse timestamp: YYYY-MM-DD HH:MM:SS

Fabby · 2 November 2020 11:40

Please read this again:

rocket19 · 2 November 2020 11:48

Ah right okay, so those I input myself?

When I do these commands

nothing returns in terminal, it just goes to the next line where I can enter the next command.
I’m guessing an output of these commands would be used in that third command?

Apologies for my questions, again, basic user haha.

Cheers.

Fabby · 2 November 2020 12:12

Sorry for being unclear, but every word is important:

So just to be clear:

journalctl --system --boot=0 | grep "suspend entry"

does not show anything after you come out of hybrid sleep???

If that’s indeed the case:

How do you invoke hybrid sleep?

rocket19 · 2 November 2020 12:24

No problems!

Yes that’s correct.

For hybrid sleep I:

Click the Whisker menu
Click the green Log Out button
Click the purple Hybrid Sleep button
The screen goes black for about 20secs, then turns off, I assume into hybrid sleep mode?

Thanks

Fabby · 2 November 2020 12:32

I’m on KDE so XFCE might be different…

Please:

Reboot
Hybrid sleep

Execute:

journalctl --system --boot=0 | grep "sleep"

Report back

rocket19 · 2 November 2020 12:43

Rebooted, hybrid sleep, then logged back in.

returns:

Nov 02 21:38:35 pc-series ModemManager[910]: <info>  [sleep-monitor] system is about to suspend
Nov 02 21:38:35 pc-series NetworkManager[855]: <info>  [1604320715.8642] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Nov 02 21:38:35 pc-series NetworkManager[855]: <info>  [1604320715.8643] device (enp4s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 02 21:38:35 pc-series NetworkManager[855]: <info>  [1604320715.8684] device (wlp3s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Nov 02 21:38:36 pc-series NetworkManager[855]: <info>  [1604320716.0692] device (wlp3s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Nov 02 21:38:36 pc-series NetworkManager[855]: <info>  [1604320716.5382] device (wlp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 02 21:38:37 pc-series systemd-sleep[1912]: Suspending system...
Nov 02 21:39:08 pc-series kernel: ACPI: Preparing to enter system sleep state S3
Nov 02 21:39:08 pc-series kernel: ACPI: Waking up from system sleep state S3
Nov 02 21:39:08 pc-series systemd-sleep[1912]: System resumed.
Nov 02 21:39:09 pc-series systemd[1]: systemd-hybrid-sleep.service: Succeeded.
Nov 02 21:39:09 pc-series audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-hybrid-sleep comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 02 21:39:09 pc-series audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-hybrid-sleep comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 02 21:39:09 pc-series systemd-logind[860]: Operation 'sleep' finished.
Nov 02 21:39:09 pc-series ModemManager[910]: <info>  [sleep-monitor] system is resuming
Nov 02 21:39:09 pc-series NetworkManager[855]: <info>  [1604320749.2469] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Nov 02 21:39:09 pc-series kernel: audit: type=1130 audit(1604320749.243:112): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-hybrid-sleep comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 02 21:39:09 pc-series kernel: audit: type=1131 audit(1604320749.243:113): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-hybrid-sleep comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Fabby · 2 November 2020 12:52

Please post the output of:

journalctl --system --boot=0 --since="2020-11-02 21:35:37" --until "2020-11-02 21:39:08"

P.S. You’ve already helped me make my requests more clear… Next time when someone has this kind of problem, I’ll ask:

When it happens, please do the following:
journalctl --system --boot=0 | grep "suspend entry"
journalctl --system --boot=0 | grep "suspend exit"
If that gives no output, try:
journalctl --system --boot=0 | grep "Suspending system"
journalctl --system --boot=0 | grep "System resumed"
then have a look at the begin and end time and post the output of:
journalctl --system --boot=0 --since "YYYY-MM-DD HH:MM:SS" --until "YYYY-MM-DD HH:MM:SS"
where obviously --since is the datetime of the suspension start and --until is the datetime of suspension end.

rocket19 · 3 November 2020 12:37

returns:

-- Logs begin at Sat 2020-10-24 17:29:59 KST, end at Tue 2020-11-03 21:35:46 KS>
-- No entries --

Edit: I just put into hybrid sleep, and then executed

And journalctl --system --boot=0 --since="2020-11-02 21:41:37" --until "2020-11-03 21:47:31" returned:

-- Logs begin at Sat 2020-10-24 17:29:59 KST, end at Tue 2020-11-03 21:48:16 KST. --
Nov 03 20:55:27 pc-series kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13
Nov 03 20:55:27 pc-series kernel: Linux version 5.8.16-2-MANJARO (builduser@development) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35)>
Nov 03 20:55:27 pc-series kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 root=UUID=3aa0ac64-1933-4b2b-b9c7-d7d5cdbb7a48 rw q>
Nov 03 20:55:27 pc-series kernel: KERNEL supported cpus:
Nov 03 20:55:27 pc-series kernel:   Intel GenuineIntel
Nov 03 20:55:27 pc-series kernel:   AMD AuthenticAMD
Nov 03 20:55:27 pc-series kernel:   Hygon HygonGenuine
Nov 03 20:55:27 pc-series kernel:   Centaur CentaurHauls
Nov 03 20:55:27 pc-series kernel:   zhaoxin   Shanghai  
Nov 03 20:55:27 pc-series kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Nov 03 20:55:27 pc-series kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Nov 03 20:55:27 pc-series kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Nov 03 20:55:27 pc-series kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Nov 03 20:55:27 pc-series kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Nov 03 20:55:27 pc-series kernel: BIOS-provided physical RAM map:
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x0000000020200000-0x0000000040003fff] usable
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x0000000040004000-0x0000000040004fff] reserved
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x0000000040005000-0x00000000c972afff] usable
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c972b000-0x00000000c9d2bfff] ACPI NVS
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c9d2c000-0x00000000c9d2efff] type 20
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c9d2f000-0x00000000c9d44fff] usable
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c9d45000-0x00000000c9d4afff] type 20
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c9d4b000-0x00000000c9d4cfff] usable
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c9d4d000-0x00000000c9d56fff] type 20
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c9d57000-0x00000000c9ee9fff] usable
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c9eea000-0x00000000c9eedfff] type 20
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c9eee000-0x00000000c9f36fff] usable
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c9f37000-0x00000000c9f3dfff] type 20
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c9f3e000-0x00000000c9f4afff] reserved
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c9f4b000-0x00000000c9f5bfff] type 20
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c9f5c000-0x00000000c9f5efff] usable
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c9f5f000-0x00000000c9f60fff] type 20
Nov 03 20:55:27 pc-series kernel: BIOS-e820: [mem 0x00000000c9f61000-0x00000000c9f77fff] usable

Fabby · 3 November 2020 13:45

That’s because you rebooted in the meantime. You should have taken boot=-1 instead of boot=0 in that particular case.

That doesn’t give any useful information…

So back to where we started:

reboot
Go to hybrid sleep

Execute:

journalctl --system --boot=0 | grep "suspend entry"
journalctl --system --boot=0 | grep "suspend exit"

If that gives no output, try:

journalctl --system --boot=0 | grep "Suspending system"
journalctl --system --boot=0 | grep "System resumed"

then have a look at the begin and end time and post the output of:
```
journalctl --system --boot=0 --since "YYYY-MM-DD HH:MM:SS" --until "YYYY-MM-DD HH:MM:SS"
```
where obviously --since is the datetime of the suspension start and --until is the datetime of suspension end.

rocket19 · 4 November 2020 09:53

Rebooted, hybrid sleep, logged back in, and then

returns:

-- Logs begin at Sat 2020-10-24 17:29:59 KST, end at Wed 2020-11-04 18:52:25 KST. --
Nov 04 18:47:11 pc-series systemd[1]: Reached target Sleep.
Nov 04 18:47:11 pc-series systemd[1]: Starting Hybrid Suspend+Hibernate...
Nov 04 18:47:11 pc-series kernel: PM: Image not found (code -22)
Nov 04 18:47:11 pc-series wpa_supplicant[920]: nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
Nov 04 18:47:11 pc-series systemd-sleep[1859]: Suspending system...
Nov 04 18:47:11 pc-series kernel: PM: hibernation: hibernation entry
Nov 04 18:47:11 pc-series kernel: bbswitch: enabling discrete graphics

Fabby · 4 November 2020 10:20

Can I have a blkid, please?

rocket19 · 4 November 2020 10:45

/dev/sda1: UUID="3984-1FEC" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="3f452e9a-b86b-f44d-a68b-a2b15f3a16a2"
/dev/sda2: UUID="3aa0ac64-1933-4b2b-b9c7-d7d5cdbb7a48" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="6a08ffa8-4a29-2f4f-8a48-a7421311e20d"
/dev/sda3: UUID="f9620ed0-383b-482f-9df0-473fc0c365f5" TYPE="swap" PARTUUID="48554d82-629b-4640-99d3-0ad866a3c54d"

Fabby · 4 November 2020 13:07

Weird: that checks out:

Could you re-verify your output because

rocket19:

-- Logs begin at Sat 2020-10-24 17:29:59 KST, end at Wed 2020-11-04 18:52:25 KST. --
Nov 04 18:47:11 pc-series systemd[1]: Reached target Sleep.
Nov 04 18:47:11 pc-series systemd[1]: Starting Hybrid Suspend+Hibernate...
Nov 04 18:47:11 pc-series kernel: PM: Image not found (code -22)
Nov 04 18:47:11 pc-series wpa_supplicant[920]: nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
Nov 04 18:47:11 pc-series systemd-sleep[1859]: Suspending system...
Nov 04 18:47:11 pc-series kernel: PM: hibernation: hibernation entry
Nov 04 18:47:11 pc-series kernel: bbswitch: enabling discrete graphics

should be much bigger than that, so I’m missing information…

rocket19 · 5 November 2020 11:33

-- Logs begin at Sat 2020-10-24 17:29:59 KST, end at Thu 2020-11-05 20:32:53 KS>
Nov 05 20:29:30 pc-series kernel: iwlwifi 0000:03:00.0: Radio type=0x2-0x0-0x0
Nov 05 20:29:30 pc-series avahi-daemon[850]: Joining mDNS multicast group on in>
Nov 05 20:29:30 pc-series avahi-daemon[850]: New relevant interface wlp3s0.IPv4>
Nov 05 20:29:30 pc-series avahi-daemon[850]: Registering new address record for>
Nov 05 20:29:30 pc-series avahi-daemon[850]: Withdrawing address record for 192>
Nov 05 20:29:30 pc-series avahi-daemon[850]: Leaving mDNS multicast group on in>
Nov 05 20:29:30 pc-series avahi-daemon[850]: Interface wlp3s0.IPv4 no longer re>
Nov 05 20:29:30 pc-series NetworkManager[855]: <info>  [1604575770.1314] device>
Nov 05 20:29:30 pc-series NetworkManager[855]: <info>  [1604575770.1314] device>
Nov 05 20:29:30 pc-series NetworkManager[855]: <info>  [1604575770.1502] device>
Nov 05 20:29:30 pc-series kernel: iwlwifi 0000:03:00.0: Radio type=0x2-0x0-0x0
Nov 05 20:29:30 pc-series kernel: iwlwifi 0000:03:00.0: Radio type=0x2-0x0-0x0
Nov 05 20:29:30 pc-series systemd[1]: Reached target Sleep.
Nov 05 20:29:30 pc-series systemd[1]: Starting Hybrid Suspend+Hibernate...
Nov 05 20:29:30 pc-series kernel: PM: Image not found (code -22)
Nov 05 20:29:30 pc-series systemd-sleep[1899]: Suspending system...
Nov 05 20:29:30 pc-series kernel: PM: hibernation: hibernation entry
Nov 05 20:29:30 pc-series kernel: bbswitch: enabling discrete graphics
lines 1-19/19 (END)...skipping...
-- Logs begin at Sat 2020-10-24 17:29:59 KST, end at Thu 2020-11-05 20:32:53 KST. --
Nov 05 20:29:30 pc-series kernel: iwlwifi 0000:03:00.0: Radio type=0x2-0x0-0x0
Nov 05 20:29:30 pc-series avahi-daemon[850]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.35.67.
Nov 05 20:29:30 pc-series avahi-daemon[850]: New relevant interface wlp3s0.IPv4 for mDNS.
Nov 05 20:29:30 pc-series avahi-daemon[850]: Registering new address record for 192.168.35.67 on wlp3s0.IPv4.
Nov 05 20:29:30 pc-series avahi-daemon[850]: Withdrawing address record for 192.168.35.67 on wlp3s0.
Nov 05 20:29:30 pc-series avahi-daemon[850]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.35.67.
Nov 05 20:29:30 pc-series avahi-daemon[850]: Interface wlp3s0.IPv4 no longer relevant for mDNS.
Nov 05 20:29:30 pc-series NetworkManager[855]: <info>  [1604575770.1314] device (wlp3s0): supplicant interface state: disconnected -> interface_disabled
Nov 05 20:29:30 pc-series NetworkManager[855]: <info>  [1604575770.1314] device (wlp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 05 20:29:30 pc-series NetworkManager[855]: <info>  [1604575770.1502] device (wlp3s0): set-hw-addr: reset MAC address to 84:A6:C8:DC:19:41 (unmanage)
Nov 05 20:29:30 pc-series kernel: iwlwifi 0000:03:00.0: Radio type=0x2-0x0-0x0
Nov 05 20:29:30 pc-series kernel: iwlwifi 0000:03:00.0: Radio type=0x2-0x0-0x0
Nov 05 20:29:30 pc-series systemd[1]: Reached target Sleep.
Nov 05 20:29:30 pc-series systemd[1]: Starting Hybrid Suspend+Hibernate...
Nov 05 20:29:30 pc-series kernel: PM: Image not found (code -22)
Nov 05 20:29:30 pc-series systemd-sleep[1899]: Suspending system...
Nov 05 20:29:30 pc-series kernel: PM: hibernation: hibernation entry
Nov 05 20:29:30 pc-series kernel: bbswitch: enabling discrete graphics

Fabby · 5 November 2020 20:06

Weird… You do have swap turned on, right? If you don’t know: swapon --verbose should give something line this:

NAME      TYPE      SIZE USED PRIO
/dev/sda7 partition  20G 968K   -2

And in your output I’m still not seeing these text entries in your log files:

Suspending system
System resumed

so if it’s not the swap file being off, the only thing I can think off is the swap partition being too small: The minimum should be RAM+SQRT(RAM), so 8+2.8 = 11GB.

So if you have 11G available somewhere, deactivate the swap partition and create a swap file (just to test).

rocket19 · 5 November 2020 20:58

NAME      TYPE      SIZE USED PRIO
/dev/sda3 partition 8.8G   0B   -2

rocket19 · 7 November 2020 04:36

Sorry for my ignorance @Fabby, any advice on where I could find to go through this process?
I’m just looking through the Swap page on the Manjaro wiki.