Impossible to hibernate

[Weg]

Hello,

I already had this problem randomly when I was under Fedora KDE edition and it was one of the motivations to reformat my PC.

But now it seems to happen systematically : when I want to hibernate, my pc simply shutdown. When I reboot, I arrive on a virgin desktop without all my opened windows.

Thanks.

[mithrial]

Welcome to Manjaro!

1. Please read this:
   How to provide good information
   and post some more information so we can see what’s really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin lies…
2. An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information for us to be able to help you. (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
   Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.

Most of the time, if hibernation doesn’t work, it is either not enough swap space or something wrong with the nvidia driver.

[Weg]

Sorry,
So here are the config information :

System:
  Kernel: 5.13.11-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
  parameters: BOOT_IMAGE=/@/boot/vmlinuz-5.13-x86_64 
  root=UUID=0423bfc7-2401-4c0d-aff1-d445732fd0ba rw rootflags=subvol=@ quiet 
  cryptdevice=UUID=0601a8bf-665e-43b5-a183-1a9cc8d83bc4:luks-0601a8bf-665e-43b5-a183-1a9cc8d83bc4 
  root=/dev/mapper/luks-0601a8bf-665e-43b5-a183-1a9cc8d83bc4 
  resume=/dev/mapper/luks-fcec610d-0b7b-4609-9fe0-be9508822a57 
  udev.log_priority=3 
  Desktop: GNOME 40.3 tk: GTK 3.24.30 wm: gnome-shell dm: GDM 40.1 
  Distro: Manjaro Linux base: Arch Linux 
Machine:
  Type: Laptop System: Notebook product: <filter> v: N/A serial: <filter> 
  Chassis: No Enclosure type: 10 serial: <filter> 
  Mobo: Notebook model: <filter> serial: <filter> UEFI: American Megatrends 
  v: 5.12 date: 11/01/2017 
Battery:
  ID-1: BAT0 charge: 36.8 Wh (100.0%) condition: 36.8/45.3 Wh (81.3%) 
  volts: 17.2 min: 15.1 model: Notebook BAT type: Li-ion serial: <filter> 
  status: Full 
Memory:
  RAM: total: 3.72 GiB used: 2.44 GiB (65.6%) 
  RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
CPU:
  Info: Quad Core model: Intel Core i5-8250U bits: 64 type: MT MCP 
  arch: Kaby Lake note: check family: 6 model-id: 8E (142) stepping: A (10) 
  microcode: EA cache: L2: 6 MiB bogomips: 28808 
  Speed: 700 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 700 2: 1525 
  3: 1042 4: 1011 5: 800 6: 792 7: 700 8: 700 
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat arch_perfmon art 
  avx avx2 bmi1 bmi2 bts clflush clflushopt cmov constant_tsc cpuid 
  cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est 
  f16c flexpriority flush_l1d fma fpu fsgsbase fxsr ht hwp hwp_act_window 
  hwp_epp hwp_notify ibpb ibrs ida intel_pt invpcid invpcid_single lahf_lm lm 
  mca mce md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae pat 
  pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts 
  rdrand rdseed rdtscp rep_good sdbg sep smap smep ss ssbd sse sse2 sse4_1 
  sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust 
  tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt 
  xsaves xtopology xtpr 
  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 mitigation: Microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: CLEVO/KAPOK driver: i915 v: kernel 
  bus-ID: 00:02.0 chip-ID: 8086:5917 class-ID: 0300 
  Device-2: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo 
  bus-ID: 1-6:3 chip-ID: 04f2:b59e class-ID: 0e02 serial: <filter> 
  Display: wayland server: X.org 1.20.13 compositor: gnome-shell driver: 
  loaded: i915 note: n/a (using device driver) - try sudo/root display-ID: 0 
  resolution: <missing: xdpyinfo> 
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 21.1.6 
  direct render: Yes 
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: CLEVO/KAPOK 
  driver: snd_hda_intel v: kernel alternate: snd_soc_skl bus-ID: 00:1f.3 
  chip-ID: 8086:9d71 class-ID: 0403 
  Sound Server-1: ALSA v: k5.13.11-1-MANJARO running: yes 
  Sound Server-2: JACK v: 1.9.19 running: no 
  Sound Server-3: PulseAudio v: 15.0 running: yes 
  Sound Server-4: PipeWire v: 0.3.33 running: yes 
Network:
  Device-1: Intel Wireless-AC 9260 driver: iwlwifi v: kernel port: f040 
  bus-ID: 01:00.0 chip-ID: 8086:2526 class-ID: 0280 
  IF: wlp1s0 state: up mac: <filter> 
  IP v4: <filter> type: dynamic noprefixroute scope: global 
  broadcast: <filter> 
  IP v6: <filter> type: dynamic noprefixroute scope: global 
  IP v6: <filter> type: noprefixroute scope: link 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: CLEVO/KAPOK driver: r8169 v: kernel port: e000 bus-ID: 02:00.1 
  chip-ID: 10ec:8168 class-ID: 0200 
  IF: enp2s0f1 state: down mac: <filter> 
  WAN IP: <filter> 
Bluetooth:
  Device-1: Intel Wireless-AC 9260 Bluetooth Adapter type: USB driver: btusb 
  v: 0.8 bus-ID: 1-5:2 chip-ID: 8087:0025 class-ID: e001 
  Report: rfkill ID: hci0 rfk-id: 3 state: up address: see --recommends 
Logical:
  Message: No logical block device data found. 
  Device-1: luks-bca40e75-a646-43ce-94bf-baa9e8465544 maj-min: 254:2 
  type: LUKS dm: dm-2 size: 931.51 GiB 
  Components: 
  p-1: sda1 maj-min: 8:1 size: 931.51 GiB 
  Device-2: luks-0601a8bf-665e-43b5-a183-1a9cc8d83bc4 maj-min: 254:0 
  type: LUKS dm: dm-0 size: 102.71 GiB 
  Components: 
  p-1: sdb2 maj-min: 8:18 size: 102.71 GiB 
  Device-3: luks-fcec610d-0b7b-4609-9fe0-be9508822a57 maj-min: 254:1 
  type: LUKS dm: dm-1 size: 8.79 GiB 
  Components: 
  p-1: sdb3 maj-min: 8:19 size: 8.79 GiB 
RAID:
  Message: No RAID data found. 
Drives:
  Local Storage: total: 1.02 TiB used: 424.33 GiB (40.7%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10SPZX-00Z10T0 
  size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  type: HDD rpm: 5400 serial: <filter> rev: 1A01 scheme: GPT 
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital 
  model: WDS120G2G0B-00EPW0 size: 111.8 GiB block-size: physical: 512 B 
  logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0000 
  scheme: GPT 
  Message: No optical or floppy data found. 
Partition:
  ID-1: / raw-size: 102.71 GiB size: 102.71 GiB (100.00%) 
  used: 14.22 GiB (13.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0 
  mapped: luks-0601a8bf-665e-43b5-a183-1a9cc8d83bc4 label: root 
  uuid: 0423bfc7-2401-4c0d-aff1-d445732fd0ba 
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) 
  used: 712 KiB (0.2%) fs: vfat dev: /dev/sdb1 maj-min: 8:17 label: BOOT 
  uuid: 94E5-C199 
  ID-3: /home raw-size: 931.51 GiB size: 931.51 GiB (100.00%) 
  used: 409.89 GiB (44.0%) fs: btrfs dev: /dev/dm-2 maj-min: 254:2 
  mapped: luks-bca40e75-a646-43ce-94bf-baa9e8465544 label: home 
  uuid: b21ad208-5212-46c6-a90b-ebf8a9be1460 
  ID-4: /run/timeshift/backup raw-size: 102.71 GiB size: 102.71 GiB (100.00%) 
  used: 14.22 GiB (13.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0 
  mapped: luks-0601a8bf-665e-43b5-a183-1a9cc8d83bc4 label: root 
  uuid: 0423bfc7-2401-4c0d-aff1-d445732fd0ba 
  ID-5: /var/cache raw-size: 102.71 GiB size: 102.71 GiB (100.00%) 
  used: 14.22 GiB (13.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0 
  mapped: luks-0601a8bf-665e-43b5-a183-1a9cc8d83bc4 label: root 
  uuid: 0423bfc7-2401-4c0d-aff1-d445732fd0ba 
  ID-6: /var/log raw-size: 102.71 GiB size: 102.71 GiB (100.00%) 
  used: 14.22 GiB (13.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0 
  mapped: luks-0601a8bf-665e-43b5-a183-1a9cc8d83bc4 label: root 
  uuid: 0423bfc7-2401-4c0d-aff1-d445732fd0ba 
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 8.79 GiB used: 225.8 MiB (2.5%) 
  priority: -2 dev: /dev/dm-1 maj-min: 254:1 
  mapped: luks-fcec610d-0b7b-4609-9fe0-be9508822a57 label: swap 
  uuid: 044553cb-9ce4-41c0-9d95-b5f54a38361d 
Unmounted:
  Message: No unmounted partitions found. 
USB:
  Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 12 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Device-1: 1-5:2 info: Intel Wireless-AC 9260 Bluetooth Adapter 
  type: Bluetooth driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s 
  power: 100mA chip-ID: 8087:0025 class-ID: e001 
  Device-2: 1-6:3 info: Chicony Chicony USB2.0 Camera type: Video 
  driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 500mA 
  chip-ID: 04f2:b59e class-ID: 0e02 serial: <filter> 
  Hub-2: 2-0:1 info: Full speed (or root) Hub ports: 6 rev: 3.0 speed: 5 Gb/s 
  chip-ID: 1d6b:0003 class-ID: 0900 
Sensors:
  System Temperatures: cpu: 46.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 335 Uptime: 2h 53m wakeups: 426 Init: systemd v: 248 
  tool: systemctl Compilers: gcc: 11.1.0 Packages: 1332 pacman: 1325 lib: 345 
  flatpak: 7 Shell: Zsh v: 5.8 running-in: gnome-terminal inxi: 3.3.06 

About more probing, I guess what you might be a shutdown/boot log ? Where can I find this ?

The sudo dmesg | less return is quite long. Do you want it all ?

As you see, the swap size is more than twice the RAM, so the problem is not there.
So, it would be the GPU driver ?

[mithrial]

You might be right about swap, this shouldn’t be a problem.

The dmesg output might only be relevant for the time during hibernating or waking-up. If the system crashes, I don’t see an option to recover this output. The journal journalctl -xeb should give some insight.

Maybe it has something to to with the swap partition being encrypted. I don’t know the order but have you tried it with the actual UUID instead of the luks-id?

[Weg]

the journalctl seems to give some warnings and errors :

août 26 17:55:08 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:55:08 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:55:13 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:55:13 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:55:16 weg systemd[694]: Started Application launched by gnome-shell.
░░ Subject: L'unité (unit) UNIT a terminé son démarrage
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ L'unité (unit) UNIT a terminé son démarrage, avec le résultat done.
août 26 17:55:17 weg dbus-daemon[765]: [session uid=1000 pid=765] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.103' (uid=1000 pid=1962 >
août 26 17:55:17 weg systemd[694]: Created slice Slice /app/org.gnome.Terminal.
░░ Subject: L'unité (unit) UNIT a terminé son démarrage
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ L'unité (unit) UNIT a terminé son démarrage, avec le résultat done.
août 26 17:55:17 weg systemd[694]: Starting GNOME Terminal Server...
░░ Subject: L'unité (unit) UNIT a commencé à démarrer
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ L'unité (unit) UNIT a commencé à démarrer.
août 26 17:55:17 weg dbus-daemon[765]: [session uid=1000 pid=765] Successfully activated service 'org.gnome.Terminal'
août 26 17:55:17 weg systemd[694]: Started GNOME Terminal Server.
░░ Subject: L'unité (unit) UNIT a terminé son démarrage
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ L'unité (unit) UNIT a terminé son démarrage, avec le résultat done.
août 26 17:55:17 weg systemd[694]: Started VTE child process 1990 launched by gnome-terminal-server process 1968.
░░ Subject: L'unité (unit) UNIT a terminé son démarrage
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ L'unité (unit) UNIT a terminé son démarrage, avec le résultat done.
 ESCOC

ct: Connection refused

ct: Connection refused

ct: Connection refused

ct: Connection refused

ct: Connection refused

ct: Connection refused

ct: Connection refused

ct: Connection refused







 name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.103' (uid=1000 pid=1962 comm="gnome-terminal --window ")












'org.gnome.Terminal'






er process 1968.





 ESCOD
août 26 17:54:37 weg rtkit-daemon[1012]: Supervising 5 threads of 3 processes of 1 users.
août 26 17:54:38 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:53:50 weg dbus-daemon[765]: [session uid=1000 pid=765] Activating service name='org.gnome.ChromeGnomeShell' requested by ':1.90' (uid=1000 pid=1799 comm="/usr/bin/python /usr/bin/chrome-gnome>
août 26 17:53:50 weg rtkit-daemon[1012]: Supervising 4 threads of 2 processes of 1 users.
août 26 17:53:50 weg dbus-daemon[765]: [session uid=1000 pid=765] Activating service name='org.gnome.ChromeGnomeShell' requested by ':1.90' (uid=1000 pid=1799 comm="/usr/bin/python /usr/bin/chrome-gnome>
août 26 17:53:51 weg dbus-daemon[765]: [session uid=1000 pid=765] Successfully activated service 'org.gnome.ChromeGnomeShell'
août 26 17:53:52 weg rtkit-daemon[1012]: Supervising 4 threads of 2 processes of 1 users.
août 26 17:53:52 weg rtkit-daemon[1012]: Supervising 4 threads of 2 processes of 1 users.
août 26 17:53:52 weg rtkit-daemon[1012]: Supervising 4 threads of 2 processes of 1 users.
août 26 17:53:52 weg rtkit-daemon[1012]: Supervising 4 threads of 2 processes of 1 users.
août 26 17:53:53 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:53:53 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:53:58 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:53:58 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:54:03 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:54:03 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:54:07 weg gnome-shell[897]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xc00008 specified for 0xc0006d.
août 26 17:54:08 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:54:08 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:54:13 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:54:13 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:54:18 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:54:18 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:54:21 weg gnome-shell[897]: Could not create transient scope for PID 1890: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 1890 does not exist.
août 26 17:54:23 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:54:23 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:54:28 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:54:28 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:54:33 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:54:33 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:54:36 weg rtkit-daemon[1012]: Supervising 4 threads of 2 processes of 1 users.
août 26 17:54:36 weg rtkit-daemon[1012]: Supervising 4 threads of 2 processes of 1 users.
août 26 17:54:37 weg rtkit-daemon[1012]: Supervising 4 threads of 2 processes of 1 users.
août 26 17:54:37 weg rtkit-daemon[1012]: Supervising 4 threads of 2 processes of 1 users.
août 26 17:54:37 weg rtkit-daemon[1012]: Supervising 4 threads of 2 processes of 1 users.
août 26 17:54:37 weg rtkit-daemon[1012]: Supervising 4 threads of 2 processes of 1 users.
août 26 17:54:37 weg rtkit-daemon[1012]: Successfully made thread 1954 of process 1652 owned by '1000' RT at priority 10.
août 26 17:54:37 weg rtkit-daemon[1012]: Supervising 5 threads of 3 processes of 1 users.
août 26 17:54:38 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:54:38 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:54:43 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:54:43 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:54:48 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:54:48 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:54:53 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:54:53 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:54:58 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:54:58 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:55:03 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:55:03 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:55:08 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:55:08 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:55:13 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:55:13 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
août 26 17:55:16 weg systemd[694]: Started Application launched by gnome-shell.
░░ Subject: L'unité (unit) UNIT a terminé son démarrage
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ L'unité (unit) UNIT a terminé son démarrage, avec le résultat done.
août 26 17:55:17 weg dbus-daemon[765]: [session uid=1000 pid=765] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.103' (uid=1000 pid=1962 >
août 26 17:55:17 weg systemd[694]: Created slice Slice /app/org.gnome.Terminal.
░░ Subject: L'unité (unit) UNIT a terminé son démarrage
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ L'unité (unit) UNIT a terminé son démarrage, avec le résultat done.
août 26 17:55:17 weg systemd[694]: Starting GNOME Terminal Server...
░░ Subject: L'unité (unit) UNIT a commencé à démarrer
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ L'unité (unit) UNIT a commencé à démarrer.
août 26 17:55:17 weg dbus-daemon[765]: [session uid=1000 pid=765] Successfully activated service 'org.gnome.Terminal'
août 26 17:55:17 weg systemd[694]: Started GNOME Terminal Server.
░░ Subject: L'unité (unit) UNIT a terminé son démarrage
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ L'unité (unit) UNIT a terminé son démarrage, avec le résultat done.
août 26 17:55:17 weg systemd[694]: Started VTE child process 1990 launched by gnome-terminal-server process 1968.
░░ Subject: L'unité (unit) UNIT a terminé son démarrage
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ L'unité (unit) UNIT a terminé son démarrage, avec le résultat done.
août 26 17:55:18 weg touchegg.desktop[1251]: Error connecting to Touchégg daemon: Could not connect: Connection refused
août 26 17:55:18 weg touchegg.desktop[1251]: Reconnecting in 5 seconds...
lines 2002-2050/2050 (END)

[Fabby]

You’re on a Stable Development kernel; is there any reason to be on that?

If not, please read this:

[HowTo] become a Manjaro power user when you're a wizard at Windows but a N00b at Manjaro / Linux

Difficulty: ☆☆☆☆☆ Remember when you installed your very first Windows, added bells and whistles and then couldn’t see the wood for the trees any more and had to re-install? Well, you’re in the same situation now: You’re a N00b again! Embrace it! I know right now you’re thinking:

Why is this so much more difficult than Windows?

[image]

Whereas in 6 months time, you’ll be like:

Why can't I make Windows jump through fiery hoops like I do with Linux???

<a class="lightbox&qu…

especially the kernel section and then install an LTS kernel and try that first.

[Weg]

The special reason is this is the kernel installed by default…
I can’t install the lts kernel :

The following packages will be installed:
linux510
linux510-rt

Starting
resolving dependencies...
looking for conflicting packages...
warning: linux510-rt-5.10.52_rt47-3 is up to date -- reinstalling
Packages (2) linux510-5.10.59-1  linux510-rt-5.10.52_rt47-3
Total Installed Size:  157.94 MiB
Net Upgrade Size:       78.24 MiB
:: Proceed with installation? [Y/n]
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Running pre-transaction hooks...
(1/1) Creating Timeshift snapshot before upgrade...
E: Commands listed below are not available on this system:
* rsync
 * /sbin/blkid
* df
* mount
* umount
* fuser
* crontab
* cp
* rm
* touch
* ln
* sync
* which
Please install required packages and try running TimeShift again
** (process:4364): CRITICAL **: 19:23:22.519: app_lock_remove: assertion 'self != NULL' failed
Unable to run timeshift-autosnap! Please close Timeshift and try again. Script will now exit...
Errors occurred, no packages were upgraded.
error: command failed to execute correctly
error: failed to commit transaction (failed to run transaction hooks)


Terminé ...

It seems it try to install the kernel already installed. weird.

[Fabby]

1. What’s the command you used to install the kernel?

2. What’s the output of

   sudo blkid
   

3. Which kind of system do you have because this is weird:

   @Weg

   Notebook product: <filter>
Mobo: Notebook model: <filter>

[Weg]

@Fabby

What’s the command you used to install the kernel?

I used graphic installer in Manjaro parameters manager

@Fabby

What’s the output of

sudo blkid

/dev/mapper/luks-fcec610d-0b7b-4609-9fe0-be9508822a57: LABEL="swap" UUID="044553cb-9ce4-41c0-9d95-b5f54a38361d" TYPE="swap"
/dev/sdb2: UUID="0601a8bf-665e-43b5-a183-1a9cc8d83bc4" TYPE="crypto_LUKS" PARTUUID="53451a1c-24a4-fd4a-9f28-66a950204a3e"
/dev/sdb3: UUID="fcec610d-0b7b-4609-9fe0-be9508822a57" TYPE="crypto_LUKS" PARTUUID="62278d6a-10a8-4a4b-85ea-623c891478cc"
/dev/sdb1: LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="94E5-C199" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="bce26440-64c1-dc47-b064-992809bb1270"
/dev/mapper/luks-bca40e75-a646-43ce-94bf-baa9e8465544: LABEL="home" UUID="b21ad208-5212-46c6-a90b-ebf8a9be1460" UUID_SUB="fbccfa01-c8ed-433b-8b56-1ccc0df9eeb3" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/mapper/luks-0601a8bf-665e-43b5-a183-1a9cc8d83bc4: LABEL="root" UUID="0423bfc7-2401-4c0d-aff1-d445732fd0ba" UUID_SUB="132e1453-22cc-4941-bbeb-75b9ecb34426" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/sda1: UUID="bca40e75-a646-43ce-94bf-baa9e8465544" TYPE="crypto_LUKS" PARTUUID="5bd77ec8-a8bc-3d4b-883d-a0868aea3085"

@Fabby

Which kind of system do you have because this is weird:

a Clevo laptop if this is what you mean by “system”.

[Fabby]

1. Read this:

[HowTo] make a crash-proof backup in Manjaro for your entire system

Difficulty: ★★☆☆☆ If you follow the tutorial completely, you will be able to create a backup of your entire system not only limited to Manjaro, but also including Windows, RHEL, Ubuntu, … and whatever else you might have installed on your system! Even if you replace your HDD by an SSD, your HDD crashes, your entire system gets stolen, … you can always restore a Cold System backup to an identical system (You cannot restore E.G. a Dell XPS onto a Dell PowerEdge and then expect that to…

2. After you’ve done the above, you no longer need TimeShift, so remove that because it seems to be causing problems on your system!

3. Execute:

   sudo mhwd-kernel --install linux54
   sudo mhwd-kernel --install linux510
   

4. to ensure grub is showing, execute:

   sudo nano --backup /etc/default/grub
   

5. Change (or add?) the following 3 lines:

   GRUB_TIMEOUT=3
   #GRUB_HIDDEN_TIMEOUT=0
   #GRUB_TIMEOUT_STYLE=hidden
   

   (3 or higher is fine, add the # before the lines above if those lines are present)

6. Ctrl+X Y Enter to save if there is anything to save

7. If you did save, execute:

   sudo update-grub
   

8. Reboot

9. Go to grub’s Advanced options

10. Choose these kernels one by one and try them out one by one and see if that helps.

[Weg]

Ok, I was able to install new kernels and to boot on them (I didn’t uninstall timeshift, I will take the time to look at clonezilla later when I’ll have more time). I tried to boot with the two lts kernel recommended and it didn’t change anything.

I can give one supplementary information which could help. When booting, after entering the password to decrypt disks, I have the following messages :

Failed to open key files.
ERROR: resume: hibernation device ’dev/mapper/luks-fcec610d[…]

It happen at each start-up, no matter I clicked on hibernate, shutdown or reboot when leaving.
So, maybe it is rather a problem of encryption/decryption ?

[Fabby]

Sorry: missed that you have encrypted your swap file, and then I can’t help you…

[Weg]

Ok, still thank you very much.
The topic stay open if somebody have a better idea.

I googled from my side. One possibility seems really probable to me. It seems by default the swap key is generated randomly at each reboot in some distrib’. May it be the case on manjaro ? In this case how can I check it ? And if this is the cause how can I make the swap use the same key files than the rest of the system ?

Edit : I think I found something interesting :

  GNU nano 5.8                                                  /etc/crypttab                                                           
# /etc/crypttab: mappings for encrypted partitions.
#
# Each mapped device will be created in /dev/mapper, so your /etc/fstab
# should use the /dev/mapper/<name> paths for encrypted devices.
#
# See crypttab(5) for the supported syntax.
#
# NOTE: Do not list your root (/) partition here, it must be set up
#       beforehand by the initramfs (/etc/mkinitcpio.conf). The same applies
#       to encrypted swap, which should be set up with mkinitcpio-openswap
#       for resume support.
#
# <name>               <device>                         <password> <options>
luks-bca40e75-a646-43ce-94bf-baa9e8465544 UUID=bca40e75-a646-43ce-94bf-baa9e8465544     /crypto_keyfile.bin luks
luks-0601a8bf-665e-43b5-a183-1a9cc8d83bc4 UUID=0601a8bf-665e-43b5-a183-1a9cc8d83bc4     /crypto_keyfile.bin luks
luks-fcec610d-0b7b-4609-9fe0-be9508822a57 UUID=fcec610d-0b7b-4609-9fe0-be9508822a57     /crypto_keyfile.bin luks

“Do not list your root (/) partition here, it must be set up
beforehand by the initramfs (/etc/mkinitcpio.conf). The same applies
to encrypted swap, which should be set up with mkinitcpio-openswap
for resume support.”

The third line correspond to the swap, so, it is listed here. And I don’t know how to use mkinitcpio-openswap.

I am waiting for an answer before touching these files… Should I comment the last line for example ?

[Weg]

Some update, I tried:

• comment the third line in crypttab: doesn’t work. The same message appear a longer time, plus another one that I don’t have the time to read. Afterwhat it boot normally.
• close reopen the swap partition with gparted : work fine, so I guess that mean the swap is encrypted with the good password and not a random one.
• uncomment GRUB_ENABLE_CRYPTODISK=y in /etc/default/grub: doesn’t change anything.

[Spunkie]

Failed to open key files.
ERROR: resume: hibernation device ’dev/mapper/luks[…]

I’ve also have this error message, since first boot, off a fresh Manjaro KDE 21.1.0 install using calamares automatic partitioning + luks + btrfs + swap.

It happens on every boot, the system still boots though, and I also had to disable hibernation because it didn’t work.

[Weg]

Nobody ? I am still looking for a solution.

[Spunkie]

@Weg I found a github issue that has a suggested fix and at first glance looks like it resolved this issue on my system, needs more testing though.

Btrfs Encrypted with small or big swap - partitioning automatically - error message

[Weg]

Many thanks, it worked for me too.

[Weg]

So the topic is solved. But if somebody have the patience for it, I would be happy to understand what I have done exactly.

What does this line mean for example : keyfile_device_mount_options="--options=subvol=@"

Thank you very much.