Compositor dies often

Yamo · 18 July 2022 19:18

My compositor crashed a month ago and ever since then it’s been crashing for like 3 times up till now.
I need to know what is the reason for that and how to fix it.

System:
  Kernel: 5.18.5-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.18-x86_64
    root=UUID=b395b351-d6f7-40f1-88ff-43ee89d7e608 rw quiet acpi_osi=Linux
    apparmor=1 security=apparmor udev.log_priority=3
  Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.4 info: latte-dock
    wm: kwin_x11 vt: 1 dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 82B5 v: Lenovo Legion 5 15ARH05
    serial: <superuser required> Chassis: type: 10 v: Lenovo Legion 5 15ARH05
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN
    serial: <superuser required> UEFI: LENOVO v: EUCN37WW date: 04/14/2022
Battery:
  ID-1: BAT0 charge: 6.2 Wh (12.0%) condition: 51.8/60.0 Wh (86.3%)
    volts: 15.5 min: 15.4 model: SMP L19M4PC0 type: Li-poly serial: <filter>
    status: charging cycles: 535
CPU:
  Info: model: AMD Ryzen 5 4600H with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 2 gen: 3 built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
    model-id: 0x60 (96) stepping: 1 microcode: 0x8600106
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 8 MiB
    desc: 2x4 MiB
  Speed (MHz): avg: 2008 high: 3992 min/max: 1400/3000 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1774 2: 1774
    3: 1556 4: 1504 5: 3979 6: 3992 7: 1395 8: 1535 9: 1748 10: 1757 11: 1637
    12: 1446 bogomips: 71880
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] vendor: Lenovo
    driver: N/A alternate: nouveau non-free: 515.xx+
    status: current (as of 2022-06) arch: Turing process: TSMC 12nm
    built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 8 link-max: lanes: 16
    bus-ID: 01:00.0 chip-ID: 10de:1f95 class-ID: 0300
  Device-2: AMD Renoir vendor: Lenovo driver: amdgpu v: kernel arch: GCN 5.1
    process: TSMC n7 (7nm) built: 2018-21 pcie: gen: 4 speed: 16 GT/s lanes: 16
    ports: active: eDP-1 empty: none bus-ID: 05:00.0 chip-ID: 1002:1636
    class-ID: 0300
  Device-3: Acer Integrated Camera type: USB driver: uvcvideo bus-ID: 1-3:2
    chip-ID: 5986:212b class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.3 compositor: kwin_x11 driver: X:
    loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa gpu: amdgpu
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 mapped: eDP model: AU Optronics 0xd1ed built: 2019
    res: 1920x1080 hz: 120 dpi: 142 gamma: 1.2 size: 344x193mm (13.54x7.6")
    diag: 394mm (15.5") ratio: 16:9 modes: max: 1920x1080 min: 640x480
  OpenGL: renderer: AMD RENOIR (LLVM 13.0.1 DRM 3.46 5.18.5-1-MANJARO)
    v: 4.6 Mesa 22.1.1 direct render: Yes
Audio:
  Device-1: NVIDIA driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
    lanes: 8 link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10fa
    class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo driver: N/A
    alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x,
    snd_acp_pci, snd_sof_amd_renoir
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2
    class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.6
    chip-ID: 1022:15e3 class-ID: 0403
  Sound Server-1: ALSA v: k5.18.5-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 16.0 running: yes
  Sound Server-4: PipeWire v: 0.3.52 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: 2000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp4s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-3:3
    chip-ID: 8087:0029 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 3 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 1.14 TiB used: 830.06 GiB (70.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZVLB256HBHQ-000L2 size: 238.47 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 3L1QEXH7 temp: 57.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10SPSX-08A6W
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: 1A01 scheme: GPT
Partition:
  ID-1: / raw-size: 51.29 GiB size: 50.31 GiB (98.08%) used: 44.18 GiB (87.8%)
    fs: ext4 dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 46.8 MiB (48.7%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 76.83 GiB size: 75.07 GiB (97.71%)
    used: 37.79 GiB (50.3%) fs: ext4 dev: /dev/nvme0n1p7 maj-min: 259:7
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 11.72 GiB used: 66.5 MiB (0.6%)
    priority: -2 dev: /dev/nvme0n1p6 maj-min: 259:6
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 53.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 328 Uptime: 13m wakeups: 1 Memory: 15 GiB used: 6.02 GiB (40.1%)
  Init: systemd v: 251 default: graphical tool: systemctl Compilers:
  gcc: 12.1.0 clang: 13.0.1 Packages: 1592 pacman: 1574 lib: 436 flatpak: 5
  snap: 13 Shell: Bash v: 5.1.16 running-in: konsole inxi: 3.3.19

> 0000:03:00.0 (0200:10ec:8168) Network controller Realtek Semiconductor Co., Ltd.:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
         network-r8168            2016.04.20                true            PCI


> 0000:01:00.0 (0300:10de:1f95) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
video-hybrid-amd-nvidia-prime            2021.12.18               false            PCI
video-hybrid-amd-nvidia-470xx-prime            2021.12.18               false            PCI
          video-nvidia            2021.12.18               false            PCI
    video-nvidia-470xx            2021.12.18               false            PCI
           video-linux            2018.05.04                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI


> 0000:05:00.0 (0300:1002:1636) Display controller ATI Technologies Inc:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
video-hybrid-amd-nvidia-prime            2021.12.18               false            PCI
video-hybrid-amd-nvidia-470xx-prime            2021.12.18               false            PCI
           video-linux            2018.05.04                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI


> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
video-hybrid-amd-nvidia-prime            2021.12.18               false            PCI
           video-linux            2018.05.04                true            PCI


Warning: No installed USB configs!

Yamo · 18 July 2022 19:19

Here is the journalctl

Jul 18 08:56:23 Yamo-Legion5 kwin_x11[84286]: Warning: Setting a new default format with a different version or profile after the global shared context is created may cause issues with context sharing.
Jul 18 08:56:23 Yamo-Legion5 kwin_x11[84286]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 180, resource id: 12582931, major code: 20 (GetProperty), minor code: 0
Jul 18 08:56:23 Yamo-Legion5 kwin_x11[84286]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 181, resource id: 12582931, major code: 20 (GetProperty), minor code: 0
Jul 18 08:56:23 Yamo-Legion5 kwin_x11[84286]: kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF86EmojiPicker"
Jul 18 08:56:23 Yamo-Legion5 kwin_x11[84286]: kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF86Dictate"
Jul 18 08:56:23 Yamo-Legion5 kwin_x11[84286]: Module 'org.kde.kwin.decoration' does not contain a module identifier directive - it cannot be protected from external registrations.
Jul 18 08:56:24 Yamo-Legion5 kwin_x11[84286]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3466, resource id: 113246212, major code: 18 (ChangeProperty), minor code: 0
Jul 18 08:56:24 Yamo-Legion5 kwin_x11[84286]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3470, resource id: 113246213, major code: 18 (ChangeProperty), minor code: 0
Jul 18 08:56:24 Yamo-Legion5 kwin_x11[84286]: kwin_platform_x11_standalone: Compositing disabled: video driver seems unstable. If you think it's a false positive, please remove  "OpenGLIsUnsafe"  from [Compositing] in kwinrc and restart kwin.
Jul 18 08:56:24 Yamo-Legion5 kwin_x11[84286]: kwin_core: Compositing is not possible
Jul 18 08:56:24 Yamo-Legion5 kded5[1292]: kf.coreaddons: "Could not load plugin from /usr/lib/qt/plugins/plasma/geolocationprovider/plasma-geolocation-gps.so: Cannot load library /usr/lib/qt/plugins/plasma/geolocationprovider/plasma-geolocation-gps.so: (libgps.so.29: cannot open shared object file: No such file or directory)"
Jul 18 08:56:56 Yamo-Legion5 udisksd[1198]: Error cleaning up mount point /run/media/yamo/HiSuite: Error unmounting: Command-line `umount -l '/run/media/yamo/HiSuite'' exited with non-zero exit status 32: umount: /run/media/yamo/HiSuite: not mounted.
Jul 18 08:57:40 Yamo-Legion5 kernel: __report_access: 17 callbacks suppressed
Jul 18 08:57:45 Yamo-Legion5 kernel: __report_access: 300 callbacks suppressed
Jul 18 08:57:53 Yamo-Legion5 kernel: __report_access: 386 callbacks suppressed
Jul 18 08:57:58 Yamo-Legion5 kernel: __report_access: 212 callbacks suppressed
Jul 18 08:58:03 Yamo-Legion5 kernel: __report_access: 314 callbacks suppressed
Jul 18 08:58:08 Yamo-Legion5 kernel: __report_access: 239 callbacks suppressed
Jul 18 08:58:13 Yamo-Legion5 kernel: __report_access: 71 callbacks suppressed
Jul 18 08:58:19 Yamo-Legion5 kernel: __report_access: 131 callbacks suppressed
Jul 18 08:58:24 Yamo-Legion5 kernel: __report_access: 311 callbacks suppressed
Jul 18 08:58:30 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 08:58:35 Yamo-Legion5 kernel: __report_access: 155 callbacks suppressed
Jul 18 08:58:52 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 09:00:07 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 09:01:22 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 09:02:40 Yamo-Legion5 kernel: __report_access: 152 callbacks suppressed
Jul 18 09:02:45 Yamo-Legion5 kernel: __report_access: 269 callbacks suppressed
Jul 18 09:02:50 Yamo-Legion5 kernel: __report_access: 371 callbacks suppressed
Jul 18 09:02:55 Yamo-Legion5 kernel: __report_access: 95 callbacks suppressed
Jul 18 09:03:00 Yamo-Legion5 kernel: __report_access: 224 callbacks suppressed
Jul 18 09:03:05 Yamo-Legion5 kernel: __report_access: 260 callbacks suppressed
Jul 18 09:03:12 Yamo-Legion5 kernel: __report_access: 209 callbacks suppressed
Jul 18 09:03:20 Yamo-Legion5 kernel: __report_access: 182 callbacks suppressed
Jul 18 09:03:22 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 09:03:25 Yamo-Legion5 kernel: __report_access: 290 callbacks suppressed
Jul 18 09:03:31 Yamo-Legion5 kernel: __report_access: 122 callbacks suppressed
Jul 18 09:03:36 Yamo-Legion5 kernel: __report_access: 194 callbacks suppressed
Jul 18 09:07:47 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 09:07:52 Yamo-Legion5 kernel: __report_access: 251 callbacks suppressed
Jul 18 09:07:57 Yamo-Legion5 kernel: __report_access: 368 callbacks suppressed
Jul 18 09:08:02 Yamo-Legion5 kernel: __report_access: 113 callbacks suppressed
Jul 18 09:08:07 Yamo-Legion5 kernel: __report_access: 212 callbacks suppressed
Jul 18 09:08:12 Yamo-Legion5 kernel: __report_access: 256 callbacks suppressed
Jul 18 09:08:19 Yamo-Legion5 kernel: __report_access: 231 callbacks suppressed
Jul 18 09:08:27 Yamo-Legion5 kernel: __report_access: 182 callbacks suppressed
Jul 18 09:08:32 Yamo-Legion5 kernel: __report_access: 284 callbacks suppressed
Jul 18 09:08:38 Yamo-Legion5 kernel: __report_access: 128 callbacks suppressed
Jul 18 09:08:43 Yamo-Legion5 kernel: __report_access: 204 callbacks suppressed
Jul 18 09:12:48 Yamo-Legion5 kernel: __report_access: 79 callbacks suppressed
Jul 18 09:12:53 Yamo-Legion5 kernel: __report_access: 262 callbacks suppressed
Jul 18 09:12:58 Yamo-Legion5 kernel: __report_access: 366 callbacks suppressed
Jul 18 09:13:03 Yamo-Legion5 kernel: __report_access: 101 callbacks suppressed
Jul 18 09:13:08 Yamo-Legion5 kernel: __report_access: 217 callbacks suppressed
Jul 18 09:13:13 Yamo-Legion5 kernel: __report_access: 264 callbacks suppressed
Jul 18 09:13:20 Yamo-Legion5 kernel: __report_access: 215 callbacks suppressed
Jul 18 09:13:28 Yamo-Legion5 kernel: __report_access: 182 callbacks suppressed
Jul 18 09:13:33 Yamo-Legion5 kernel: __report_access: 290 callbacks suppressed
Jul 18 09:13:39 Yamo-Legion5 kernel: __report_access: 125 callbacks suppressed
Jul 18 09:13:44 Yamo-Legion5 kernel: __report_access: 194 callbacks suppressed
Jul 18 09:17:55 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 09:18:00 Yamo-Legion5 kernel: __report_access: 287 callbacks suppressed
Jul 18 09:18:05 Yamo-Legion5 kernel: __report_access: 389 callbacks suppressed
Jul 18 09:18:10 Yamo-Legion5 kernel: __report_access: 86 callbacks suppressed
Jul 18 09:18:15 Yamo-Legion5 kernel: __report_access: 247 callbacks suppressed
Jul 18 09:18:20 Yamo-Legion5 kernel: __report_access: 234 callbacks suppressed
Jul 18 09:18:27 Yamo-Legion5 kernel: __report_access: 185 callbacks suppressed
Jul 18 09:18:34 Yamo-Legion5 kernel: __report_access: 182 callbacks suppressed
Jul 18 09:18:39 Yamo-Legion5 kernel: __report_access: 284 callbacks suppressed
Jul 18 09:18:46 Yamo-Legion5 kernel: __report_access: 131 callbacks suppressed
Jul 18 09:18:52 Yamo-Legion5 kernel: __report_access: 194 callbacks suppressed
Jul 18 09:22:53 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 09:22:58 Yamo-Legion5 kernel: __report_access: 262 callbacks suppressed
Jul 18 09:23:03 Yamo-Legion5 kernel: __report_access: 351 callbacks suppressed
Jul 18 09:23:08 Yamo-Legion5 kernel: __report_access: 107 callbacks suppressed
Jul 18 09:23:13 Yamo-Legion5 kernel: __report_access: 203 callbacks suppressed
Jul 18 09:23:18 Yamo-Legion5 kernel: __report_access: 269 callbacks suppressed
Jul 18 09:23:26 Yamo-Legion5 kernel: __report_access: 233 callbacks suppressed
Jul 18 09:23:34 Yamo-Legion5 kernel: __report_access: 182 callbacks suppressed
Jul 18 09:23:39 Yamo-Legion5 kernel: __report_access: 275 callbacks suppressed
Jul 18 09:23:46 Yamo-Legion5 kernel: __report_access: 140 callbacks suppressed
Jul 18 09:23:51 Yamo-Legion5 kernel: __report_access: 194 callbacks suppressed
Jul 18 09:27:57 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 09:28:02 Yamo-Legion5 kernel: __report_access: 259 callbacks suppressed
Jul 18 09:28:07 Yamo-Legion5 kernel: __report_access: 337 callbacks suppressed
Jul 18 09:28:12 Yamo-Legion5 kernel: __report_access: 118 callbacks suppressed
Jul 18 09:28:17 Yamo-Legion5 kernel: __report_access: 194 callbacks suppressed
Jul 18 09:28:22 Yamo-Legion5 kernel: __report_access: 281 callbacks suppressed
Jul 18 09:28:30 Yamo-Legion5 kernel: __report_access: 236 callbacks suppressed
Jul 18 09:28:35 Yamo-Legion5 kernel: __report_access: 179 callbacks suppressed
Jul 18 09:28:40 Yamo-Legion5 kernel: __report_access: 86 callbacks suppressed
Jul 18 09:28:45 Yamo-Legion5 kernel: __report_access: 287 callbacks suppressed
Jul 18 09:28:50 Yamo-Legion5 kernel: __report_access: 35 callbacks suppressed
Jul 18 09:28:56 Yamo-Legion5 kernel: __report_access: 194 callbacks suppressed
Jul 18 09:32:57 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 09:33:02 Yamo-Legion5 kernel: __report_access: 245 callbacks suppressed
Jul 18 09:33:07 Yamo-Legion5 kernel: __report_access: 335 callbacks suppressed
Jul 18 09:33:12 Yamo-Legion5 kernel: __report_access: 127 callbacks suppressed
Jul 18 09:33:17 Yamo-Legion5 kernel: __report_access: 182 callbacks suppressed
Jul 18 09:33:22 Yamo-Legion5 kernel: __report_access: 294 callbacks suppressed
Jul 18 09:33:27 Yamo-Legion5 kernel: __report_access: 230 callbacks suppressed
Jul 18 09:33:33 Yamo-Legion5 kernel: __report_access: 68 callbacks suppressed
Jul 18 09:33:39 Yamo-Legion5 kernel: __report_access: 119 callbacks suppressed
Jul 18 09:33:44 Yamo-Legion5 kernel: __report_access: 266 callbacks suppressed
Jul 18 09:33:51 Yamo-Legion5 kernel: __report_access: 149 callbacks suppressed
Jul 18 09:33:56 Yamo-Legion5 kernel: __report_access: 194 callbacks suppressed
Jul 18 09:37:59 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 09:38:04 Yamo-Legion5 kernel: __report_access: 233 callbacks suppressed
Jul 18 09:38:09 Yamo-Legion5 kernel: __report_access: 329 callbacks suppressed
Jul 18 09:38:14 Yamo-Legion5 kernel: __report_access: 132 callbacks suppressed
Jul 18 09:38:19 Yamo-Legion5 kernel: __report_access: 193 callbacks suppressed
Jul 18 09:38:24 Yamo-Legion5 kernel: __report_access: 287 callbacks suppressed
Jul 18 09:38:29 Yamo-Legion5 kernel: __report_access: 188 callbacks suppressed
Jul 18 09:38:36 Yamo-Legion5 kernel: __report_access: 122 callbacks suppressed
Jul 18 09:38:42 Yamo-Legion5 kernel: __report_access: 119 callbacks suppressed
Jul 18 09:38:47 Yamo-Legion5 kernel: __report_access: 272 callbacks suppressed
Jul 18 09:38:54 Yamo-Legion5 kernel: __report_access: 143 callbacks suppressed
Jul 18 09:39:00 Yamo-Legion5 kernel: __report_access: 194 callbacks suppressed
Jul 18 09:43:01 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 09:43:06 Yamo-Legion5 kernel: __report_access: 252 callbacks suppressed
Jul 18 09:43:11 Yamo-Legion5 kernel: __report_access: 326 callbacks suppressed
Jul 18 09:43:16 Yamo-Legion5 kernel: __report_access: 122 callbacks suppressed
Jul 18 09:43:21 Yamo-Legion5 kernel: __report_access: 190 callbacks suppressed
Jul 18 09:43:26 Yamo-Legion5 kernel: __report_access: 287 callbacks suppressed
Jul 18 09:43:31 Yamo-Legion5 kernel: __report_access: 191 callbacks suppressed
Jul 18 09:43:38 Yamo-Legion5 kernel: __report_access: 116 callbacks suppressed
Jul 18 09:43:43 Yamo-Legion5 kernel: __report_access: 119 callbacks suppressed
Jul 18 09:43:48 Yamo-Legion5 kernel: __report_access: 256 callbacks suppressed
Jul 18 09:43:56 Yamo-Legion5 kernel: __report_access: 159 callbacks suppressed
Jul 18 09:44:02 Yamo-Legion5 kernel: __report_access: 194 callbacks suppressed
Jul 18 09:48:02 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 09:48:07 Yamo-Legion5 kernel: __report_access: 252 callbacks suppressed
Jul 18 09:48:12 Yamo-Legion5 kernel: __report_access: 314 callbacks suppressed
Jul 18 09:48:17 Yamo-Legion5 kernel: __report_access: 131 callbacks suppressed
Jul 18 09:48:23 Yamo-Legion5 kernel: __report_access: 191 callbacks suppressed
Jul 18 09:48:28 Yamo-Legion5 kernel: __report_access: 287 callbacks suppressed
Jul 18 09:48:33 Yamo-Legion5 kernel: __report_access: 191 callbacks suppressed
Jul 18 09:48:40 Yamo-Legion5 kernel: __report_access: 113 callbacks suppressed
Jul 18 09:48:45 Yamo-Legion5 kernel: __report_access: 119 callbacks suppressed
Jul 18 09:48:51 Yamo-Legion5 kernel: __report_access: 263 callbacks suppressed
Jul 18 09:48:58 Yamo-Legion5 kernel: __report_access: 152 callbacks suppressed
Jul 18 09:49:03 Yamo-Legion5 kernel: __report_access: 197 callbacks suppressed
Jul 18 09:53:03 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 09:53:09 Yamo-Legion5 kernel: __report_access: 251 callbacks suppressed
Jul 18 09:53:10 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 09:53:14 Yamo-Legion5 kernel: __report_access: 314 callbacks suppressed
Jul 18 09:53:19 Yamo-Legion5 kernel: __report_access: 125 callbacks suppressed
Jul 18 09:53:24 Yamo-Legion5 kernel: __report_access: 199 callbacks suppressed
Jul 18 09:53:29 Yamo-Legion5 kernel: __report_access: 287 callbacks suppressed
Jul 18 09:53:34 Yamo-Legion5 kernel: __report_access: 179 callbacks suppressed
Jul 18 09:53:39 Yamo-Legion5 kernel: __report_access: 122 callbacks suppressed
Jul 18 09:53:44 Yamo-Legion5 kernel: __report_access: 127 callbacks suppressed
Jul 18 09:53:49 Yamo-Legion5 kernel: __report_access: 66 callbacks suppressed
Jul 18 09:53:54 Yamo-Legion5 kernel: __report_access: 266 callbacks suppressed
Jul 18 09:54:01 Yamo-Legion5 kernel: __report_access: 74 callbacks suppressed
Jul 18 09:54:06 Yamo-Legion5 kernel: __report_access: 197 callbacks suppressed
Jul 18 09:57:36 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 09:58:06 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 09:58:11 Yamo-Legion5 kernel: __report_access: 238 callbacks suppressed
Jul 18 09:58:16 Yamo-Legion5 kernel: __report_access: 291 callbacks suppressed
Jul 18 09:58:21 Yamo-Legion5 kernel: __report_access: 146 callbacks suppressed
Jul 18 09:58:27 Yamo-Legion5 kernel: __report_access: 212 callbacks suppressed
Jul 18 09:58:32 Yamo-Legion5 kernel: __report_access: 287 callbacks suppressed
Jul 18 09:58:37 Yamo-Legion5 kernel: __report_access: 185 callbacks suppressed
Jul 18 09:58:45 Yamo-Legion5 kernel: __report_access: 119 callbacks suppressed
Jul 18 09:58:50 Yamo-Legion5 kernel: __report_access: 119 callbacks suppressed
Jul 18 09:58:51 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 09:58:55 Yamo-Legion5 kernel: __report_access: 257 callbacks suppressed
Jul 18 09:59:03 Yamo-Legion5 kernel: __report_access: 158 callbacks suppressed
Jul 18 09:59:09 Yamo-Legion5 kernel: __report_access: 197 callbacks suppressed
Jul 18 10:00:06 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 10:02:06 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 10:03:09 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 10:03:14 Yamo-Legion5 kernel: __report_access: 221 callbacks suppressed
Jul 18 10:03:19 Yamo-Legion5 kernel: __report_access: 275 callbacks suppressed
Jul 18 10:03:25 Yamo-Legion5 kernel: __report_access: 179 callbacks suppressed
Jul 18 10:03:31 Yamo-Legion5 kernel: __report_access: 212 callbacks suppressed
Jul 18 10:03:36 Yamo-Legion5 kernel: __report_access: 284 callbacks suppressed
Jul 18 10:03:42 Yamo-Legion5 kernel: __report_access: 176 callbacks suppressed
Jul 18 10:03:47 Yamo-Legion5 kernel: __report_access: 113 callbacks suppressed
Jul 18 10:03:52 Yamo-Legion5 kernel: __report_access: 125 callbacks suppressed
Jul 18 10:03:57 Yamo-Legion5 kernel: __report_access: 56 callbacks suppressed
Jul 18 10:04:02 Yamo-Legion5 kernel: __report_access: 287 callbacks suppressed
Jul 18 10:04:08 Yamo-Legion5 kernel: __report_access: 83 callbacks suppressed
Jul 18 10:04:14 Yamo-Legion5 kernel: __report_access: 197 callbacks suppressed
Jul 18 10:07:32 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 10:08:10 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 10:08:15 Yamo-Legion5 kernel: __report_access: 233 callbacks suppressed
Jul 18 10:08:20 Yamo-Legion5 kernel: __report_access: 275 callbacks suppressed
Jul 18 10:08:26 Yamo-Legion5 kernel: __report_access: 167 callbacks suppressed
Jul 18 10:08:32 Yamo-Legion5 kernel: __report_access: 212 callbacks suppressed
Jul 18 10:08:37 Yamo-Legion5 kernel: __report_access: 284 callbacks suppressed
Jul 18 10:08:42 Yamo-Legion5 kernel: __report_access: 175 callbacks suppressed
Jul 18 10:08:47 Yamo-Legion5 kernel: __report_access: 105 callbacks suppressed
Jul 18 10:08:52 Yamo-Legion5 kernel: __report_access: 125 callbacks suppressed
Jul 18 10:08:58 Yamo-Legion5 kernel: __report_access: 59 callbacks suppressed
Jul 18 10:09:03 Yamo-Legion5 kernel: __report_access: 287 callbacks suppressed
Jul 18 10:09:09 Yamo-Legion5 kernel: __report_access: 83 callbacks suppressed
Jul 18 10:09:15 Yamo-Legion5 kernel: __report_access: 197 callbacks suppressed
Jul 18 10:10:06 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 10:11:21 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 10:12:36 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 10:13:13 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 10:13:18 Yamo-Legion5 kernel: __report_access: 220 callbacks suppressed
Jul 18 10:13:23 Yamo-Legion5 kernel: __report_access: 257 callbacks suppressed
Jul 18 10:13:29 Yamo-Legion5 kernel: __report_access: 198 callbacks suppressed
Jul 18 10:13:36 Yamo-Legion5 kernel: __report_access: 213 callbacks suppressed
Jul 18 10:13:41 Yamo-Legion5 kernel: __report_access: 281 callbacks suppressed
Jul 18 10:13:46 Yamo-Legion5 kernel: __report_access: 170 callbacks suppressed
Jul 18 10:13:51 Yamo-Legion5 kernel: __report_access: 100 callbacks suppressed
Jul 18 10:13:56 Yamo-Legion5 kernel: __report_access: 135 callbacks suppressed
Jul 18 10:14:01 Yamo-Legion5 kernel: __report_access: 35 callbacks suppressed
Jul 18 10:14:06 Yamo-Legion5 kernel: __report_access: 293 callbacks suppressed
Jul 18 10:14:13 Yamo-Legion5 kernel: __report_access: 104 callbacks suppressed
Jul 18 10:14:18 Yamo-Legion5 kernel: __report_access: 197 callbacks suppressed
Jul 18 10:14:36 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 10:18:15 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 10:18:20 Yamo-Legion5 kernel: __report_access: 236 callbacks suppressed
Jul 18 10:18:25 Yamo-Legion5 kernel: __report_access: 283 callbacks suppressed
Jul 18 10:18:31 Yamo-Legion5 kernel: __report_access: 156 callbacks suppressed
Jul 18 10:18:36 Yamo-Legion5 kernel: __report_access: 194 callbacks suppressed
Jul 18 10:18:41 Yamo-Legion5 kernel: __report_access: 257 callbacks suppressed
Jul 18 10:18:47 Yamo-Legion5 kernel: __report_access: 128 callbacks suppressed
Jul 18 10:18:53 Yamo-Legion5 kernel: __report_access: 167 callbacks suppressed
Jul 18 10:18:58 Yamo-Legion5 kernel: __report_access: 135 callbacks suppressed
Jul 18 10:19:04 Yamo-Legion5 kernel: __report_access: 49 callbacks suppressed
Jul 18 10:19:09 Yamo-Legion5 kernel: __report_access: 283 callbacks suppressed
Jul 18 10:19:16 Yamo-Legion5 kernel: __report_access: 120 callbacks suppressed
Jul 18 10:19:21 Yamo-Legion5 kernel: __report_access: 197 callbacks suppressed
Jul 18 10:23:21 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 10:23:26 Yamo-Legion5 kernel: __report_access: 224 callbacks suppressed
Jul 18 10:23:31 Yamo-Legion5 kernel: __report_access: 260 callbacks suppressed
Jul 18 10:23:37 Yamo-Legion5 kernel: __report_access: 191 callbacks suppressed
Jul 18 10:23:42 Yamo-Legion5 kernel: __report_access: 200 callbacks suppressed
Jul 18 10:23:47 Yamo-Legion5 kernel: __report_access: 233 callbacks suppressed
Jul 18 10:23:53 Yamo-Legion5 kernel: __report_access: 146 callbacks suppressed
Jul 18 10:24:00 Yamo-Legion5 kernel: __report_access: 167 callbacks suppressed
Jul 18 10:24:05 Yamo-Legion5 kernel: __report_access: 140 callbacks suppressed
Jul 18 10:24:10 Yamo-Legion5 kernel: __report_access: 47 callbacks suppressed
Jul 18 10:24:15 Yamo-Legion5 kernel: __report_access: 287 callbacks suppressed
Jul 18 10:24:22 Yamo-Legion5 kernel: __report_access: 110 callbacks suppressed
Jul 18 10:24:28 Yamo-Legion5 kernel: __report_access: 197 callbacks suppressed
Jul 18 10:25:33 Yamo-Legion5 tlp[2008969]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Jul 18 10:25:33 Yamo-Legion5 tlp[2008973]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Jul 18 10:25:33 Yamo-Legion5 tlp[2008973]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Jul 18 10:25:33 Yamo-Legion5 tlp[2008969]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Jul 18 10:25:33 Yamo-Legion5 tlp[2008969]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Jul 18 10:25:33 Yamo-Legion5 tlp[2008973]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Jul 18 10:25:33 Yamo-Legion5 tlp[2008969]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Jul 18 10:25:33 Yamo-Legion5 tlp[2008973]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Jul 18 10:25:33 Yamo-Legion5 tlp[2009064]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Jul 18 10:25:33 Yamo-Legion5 tlp[2009064]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Jul 18 10:25:33 Yamo-Legion5 tlp[2009064]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Jul 18 10:25:33 Yamo-Legion5 tlp[2009064]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Jul 18 10:25:33 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 10:25:33 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 10:25:33 Yamo-Legion5 org_kde_powerdevil[1355]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 18 10:25:33 Yamo-Legion5 plasmashell[1356]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x55d047c08580) QQmlContext(0x55d046638690) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Jul 18 10:25:33 Yamo-Legion5 plasmashell[1356]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x55d047c08580) QQmlContext(0x55d046638690) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Jul 18 10:25:33 Yamo-Legion5 plasmashell[1356]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:219:21: QML SelectableLabel: Binding loop detected for property "implicitWidth"
Jul 18 10:25:33 Yamo-Legion5 plasmashell[1356]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:219:21: QML SelectableLabel: Binding loop detected for property "implicitWidth"
Jul 18 10:25:33 Yamo-Legion5 plasmashell[1356]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:219:21: QML SelectableLabel: Binding loop detected for property "implicitHeight"
Jul 18 10:25:33 Yamo-Legion5 plasmashell[1356]: file:///usr/lib/qt/qml/org/kde/plasma/components.3/ScrollView.qml:37:27: QML ScrollBar: Binding loop detected for property "visible"
Jul 18 10:25:33 Yamo-Legion5 plasmashell[1356]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/SelectableLabel.qml:38:5: QML TextArea: Binding loop detected for property "implicitHeight"
Jul 18 10:26:03 Yamo-Legion5 plasmashell[1356]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x7f3f5409b2c0) QQmlContext(0x55d046638690) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Jul 18 10:26:03 Yamo-Legion5 plasmashell[1356]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x7f3f5409b2c0) QQmlContext(0x55d046638690) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Jul 18 10:26:03 Yamo-Legion5 plasmashell[1356]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:219:21: QML SelectableLabel: Binding loop detected for property "implicitWidth"
Jul 18 10:26:03 Yamo-Legion5 plasmashell[1356]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:219:21: QML SelectableLabel: Binding loop detected for property "implicitWidth"
Jul 18 10:26:03 Yamo-Legion5 plasmashell[1356]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:219:21: QML SelectableLabel: Binding loop detected for property "implicitHeight"
Jul 18 10:26:03 Yamo-Legion5 plasmashell[1356]: file:///usr/lib/qt/qml/org/kde/plasma/components.3/ScrollView.qml:37:27: QML ScrollBar: Binding loop detected for property "visible"
Jul 18 10:26:03 Yamo-Legion5 plasmashell[1356]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/SelectableLabel.qml:38:5: QML TextArea: Binding loop detected for property "implicitHeight"
Jul 18 10:28:20 Yamo-Legion5 kernel: __report_access: 89 callbacks suppressed
Jul 18 10:28:25 Yamo-Legion5 kernel: __report_access: 224 callbacks suppressed
Jul 18 10:28:30 Yamo-Legion5 kernel: __report_access: 269 callbacks suppressed
Jul 18 10:28:36 Yamo-Legion5 kernel: __report_access: 188 callbacks suppressed
Jul 18 10:28:43 Yamo-Legion5 kernel: __report_access: 212 callbacks suppressed
Jul 18 10:28:48 Yamo-Legion5 kernel: __report_access: 260 callbacks suppressed
Jul 18 10:28:53 Yamo-Legion5 kernel: __report_access: 131 callbacks suppressed
Jul 18 10:28:54 Yamo-Legion5 sddm[759]: Authentication error: "Process crashed"
Jul 18 10:28:54 Yamo-Legion5 sddm[759]: Auth: sddm-helper crashed (exit code 15)
Jul 18 10:28:54 Yamo-Legion5 sddm[759]: Authentication error: "Process crashed"
Jul 18 10:28:54 Yamo-Legion5 sddm[759]: Auth: sddm-helper exited with 15
Jul 18 10:28:54 Yamo-Legion5 kglobalaccel5[1347]: The X11 connection broke (error 1). Did the X11 server die?
Jul 18 10:28:54 Yamo-Legion5 kglobalaccel5[1347]: The X11 connection broke: I/O error (code 1)
Jul 18 10:28:54 Yamo-Legion5 kactivitymanagerd[1389]: The X11 connection broke (error 1). Did the X11 server die?
Jul 18 10:28:54 Yamo-Legion5 msm_kde_notifier[1382]: The X11 connection broke (error 1). Did the X11 server die?
Jul 18 10:28:54 Yamo-Legion5 pamac-tray-plasma[1420]: The X11 connection broke (error 1). Did the X11 server die?
Jul 18 10:28:54 Yamo-Legion5 yakuake[1459]: The X11 connection broke (error 1). Did the X11 server die?
Jul 18 10:28:54 Yamo-Legion5 yakuake[1459]: Had queued notifications on destruction. Was the eventloop running?
Jul 18 10:28:54 Yamo-Legion5 kscreen_backend_launcher[1543]: The X11 connection broke (error 1). Did the X11 server die?
Jul 18 10:28:54 Yamo-Legion5 baloorunner[66192]: The X11 connection broke (error 1). Did the X11 server die?
Jul 18 10:28:54 Yamo-Legion5 kalendarac[1538]: The X11 connection broke (error 1). Did the X11 server die?
Jul 18 10:28:54 Yamo-Legion5 pulseaudio[1379]: X11 I/O error handler called
Jul 18 10:28:54 Yamo-Legion5 pulseaudio[1379]: X11 I/O error exit handler called, preparing to tear down X11 modules
Jul 18 10:28:54 Yamo-Legion5 xdg-desktop-portal-kde[1936]: The X11 connection broke (error 1). Did the X11 server die?
Jul 18 10:28:54 Yamo-Legion5 konsole[1597]: The X11 connection broke (error 1). Did the X11 server die?
Jul 18 10:28:54 Yamo-Legion5 konsole[68318]: The X11 connection broke (error 1). Did the X11 server die?
Jul 18 10:28:54 Yamo-Legion5 konsole[68318]: Had queued notifications on destruction. Was the eventloop running?
Jul 18 10:28:54 Yamo-Legion5 kwin_x11[84286]: The X11 connection broke: I/O error (code 1)
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:54 Yamo-Legion5 kded5[1292]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jul 18 10:28:55 Yamo-Legion5 at-spi2-registr[2088049]: Could not open X display
Jul 18 10:28:55 Yamo-Legion5 at-spi2-registr[2088049]: AT-SPI: Cannot open default display
Jul 18 10:28:55 Yamo-Legion5 at-spi2-registr[2088145]: Could not open X display
Jul 18 10:28:55 Yamo-Legion5 at-spi2-registr[2088145]: AT-SPI: Cannot open default display
Jul 18 10:28:55 Yamo-Legion5 at-spi2-registr[2088147]: Could not open X display
Jul 18 10:28:55 Yamo-Legion5 at-spi2-registr[2088147]: AT-SPI: Cannot open default display
Jul 18 10:28:55 Yamo-Legion5 at-spi2-registr[2088149]: Could not open X display
Jul 18 10:28:55 Yamo-Legion5 at-spi2-registr[2088149]: AT-SPI: Cannot open default display
Jul 18 10:28:55 Yamo-Legion5 at-spi2-registr[2088151]: Could not open X display
Jul 18 10:28:55 Yamo-Legion5 at-spi2-registr[2088151]: AT-SPI: Cannot open default display
Jul 18 10:28:55 Yamo-Legion5 at-spi2-registr[2088153]: Could not open X display
Jul 18 10:28:55 Yamo-Legion5 at-spi2-registr[2088153]: AT-SPI: Cannot open default display
Jul 18 10:28:55 Yamo-Legion5 okular[1615]: The X11 connection broke (error 1). Did the X11 server die?
Jul 18 10:28:55 Yamo-Legion5 at-spi2-registr[2088155]: Could not open X display
Jul 18 10:28:55 Yamo-Legion5 at-spi2-registr[2088155]: AT-SPI: Cannot open default display
Jul 18 10:28:55 Yamo-Legion5 dolphin[1581]: The X11 connection broke (error 1). Did the X11 server die?
Jul 18 10:28:55 Yamo-Legion5 systemd-coredump[2088161]: Failed to connect to coredump service: Connection refused
Jul 18 10:28:57 Yamo-Legion5 kded5[2088160]: qt.qpa.xcb: could not connect to display :0
Jul 18 10:28:57 Yamo-Legion5 kded5[2088160]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
                                             
                                             Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Jul 18 10:28:57 Yamo-Legion5 systemd-coredump[2088191]: Failed to connect to coredump service: Connection refused
Jul 18 10:28:57 Yamo-Legion5 sddm[759]: Signal received: SIGTERM
Jul 18 10:28:57 Yamo-Legion5 org.freedesktop.secrets[1955]: discover_other_daemon: 1
Jul 18 10:28:58 Yamo-Legion5 sddm[759]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Jul 18 10:30:27 Yamo-Legion5 systemd[1235]: app-visual\x2dstudio\x2dcode-4fadaa543cdd4f749c68f4d33e63a7f3.scope: Stopping timed out. Killing.
Jul 18 10:30:27 Yamo-Legion5 systemd[1235]: app-visual\x2dstudio\x2dcode-4fadaa543cdd4f749c68f4d33e63a7f3.scope: Failed with result 'timeout'.
Jul 18 10:30:27 Yamo-Legion5 kernel: kauditd_printk_skb: 24 callbacks suppressed
Jul 18 10:30:28 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 18 10:30:28 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 18 10:30:28 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 18 10:30:28 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 18 10:30:28 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 18 10:30:28 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 18 10:30:28 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)

brahma · 18 July 2022 20:40

you have there som massive spam from kernel…
provide output from:
mhwd -l && mhwd -li

Yamo · 18 July 2022 22:54

I already provided that up in the post

brahma · 19 July 2022 07:48

well the nvidia driver is not being detected:

driver: N/A

try with different kernels, install the 5.15 and the 5.10 and try with them

deroberts1 · 19 July 2022 16:15

You could try a very functional and simple compositor called xcompmgr.

It is what I have to use with my Nouveau driver.

It is in the package manager. Just install it and put it in your autostart. It never gives me a hint of trouble.

I have come to appreciate the fade in and out effects.

Yamo · 24 July 2022 09:19

You got my attention to a very important part that the driver is not defined or seen, I’ve removed and installed the appropriate drivers and I hope it won’t happen again.
Thanks for the help <3

Yamo · 30 July 2022 15:29

Today my compositor died again, here is the logs.

Jul 30 14:50:57 Yamo-Legion5 kernel: TSC synchronization [CPU#0 -> CPU#6]:
Jul 30 14:50:57 Yamo-Legion5 kernel: Measured 4470 cycles TSC warp between CPUs, turning off TSC clock.
Jul 30 14:50:57 Yamo-Legion5 kernel:   #7  #8  #9 #10 #11
Jul 30 14:50:57 Yamo-Legion5 kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Jul 30 14:50:57 Yamo-Legion5 kernel: pci 0000:00:00.2: PCI INT A: not connected
Jul 30 14:50:57 Yamo-Legion5 kernel: Unstable clock detected, switching default tracing clock to "global"
                                     If you want to keep using the local clock, then add:
                                       "trace_clock=local"
                                     on the kernel command line
Jul 30 14:50:57 Yamo-Legion5 kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Jul 30 14:50:57 Yamo-Legion5 kernel: nvme nvme0: missing or invalid SUBNQN field.
Jul 30 14:50:57 Yamo-Legion5 systemd-modules-load[301]: Failed to find module 'acpi_call'
Jul 30 14:50:57 Yamo-Legion5 systemd-udevd[326]: /etc/udev/rules.d/40-libsane.rules:26: GOTO="libsane_rules_end" has no matching label, ignoring
Jul 30 14:50:57 Yamo-Legion5 systemd-udevd[326]: /etc/udev/rules.d/S99-2000S1.rules:26: GOTO="libsane_rules_end" has no matching label, ignoring
Jul 30 14:50:57 Yamo-Legion5 kernel: acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Jul 30 14:50:57 Yamo-Legion5 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Jul 30 14:50:57 Yamo-Legion5 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Jul 30 14:50:57 Yamo-Legion5 kernel: iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-72.ucode failed with error -2
Jul 30 14:50:57 Yamo-Legion5 kernel: iwlwifi 0000:04:00.0: api flags index 2 larger than supported by driver
Jul 30 14:50:58 Yamo-Legion5 kernel: thermal thermal_zone0: failed to read out thermal zone (-61)
Jul 30 14:50:58 Yamo-Legion5 kernel: nvidia: loading out-of-tree module taints kernel.
Jul 30 14:50:58 Yamo-Legion5 kernel: nvidia: module license 'NVIDIA' taints kernel.
Jul 30 14:50:58 Yamo-Legion5 kernel: Disabling lock debugging due to kernel taint
Jul 30 14:50:58 Yamo-Legion5 kernel: EXT4-fs (nvme0n1p7): warning: mounting fs with errors, running e2fsck is recommended
Jul 30 14:50:58 Yamo-Legion5 kernel:
Jul 30 14:50:58 Yamo-Legion5 kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  515.57  Wed Jun 22 22:44:07 UTC 2022
Jul 30 14:50:59 Yamo-Legion5 kernel: nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint.
Jul 30 14:50:59 Yamo-Legion5 kernel: VBoxNetAdp: Successfully started.
Jul 30 14:50:59 Yamo-Legion5 kernel: VBoxNetFlt: Successfully started.
Jul 30 14:50:59 Yamo-Legion5 sddm[710]: Failed to read display number from pipe
Jul 30 14:50:59 Yamo-Legion5 sddm[710]: Attempt 1 starting the Display server on vt 1 failed
Jul 30 14:51:00 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 14:51:00 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 14:51:00 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 14:51:00 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 14:51:00 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 14:51:00 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 14:51:00 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 14:51:00 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 14:51:00 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 14:51:00 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 14:51:00 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 14:51:00 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 14:51:00 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 14:51:00 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 14:51:00 Yamo-Legion5 kernel: kauditd_printk_skb: 102 callbacks suppressed
Jul 30 14:51:02 Yamo-Legion5 sddm[710]: Failed to read display number from pipe
Jul 30 14:51:02 Yamo-Legion5 sddm[710]: Attempt 2 starting the Display server on vt 1 failed
Jul 30 14:51:03 Yamo-Legion5 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
Jul 30 14:51:03 Yamo-Legion5 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 30 14:51:03 Yamo-Legion5 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 30 14:51:04 Yamo-Legion5 kernel: ATPX version 1, functions 0x00000001
Jul 30 14:51:04 Yamo-Legion5 kernel: ATPX Hybrid Graphics
Jul 30 14:51:04 Yamo-Legion5 kernel: amdgpu 0000:05:00.0: amdgpu: PSP runtime database doesn't exist
Jul 30 14:51:04 Yamo-Legion5 sddm[710]: Failed to read display number from pipe
Jul 30 14:51:04 Yamo-Legion5 sddm[710]: Attempt 3 starting the Display server on vt 1 failed
Jul 30 14:51:04 Yamo-Legion5 sddm[710]: Could not start Display server on vt 1
Jul 30 14:51:04 Yamo-Legion5 kernel: amdgpu: SRAT table not found
Jul 30 14:51:06 Yamo-Legion5 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 30 14:51:06 Yamo-Legion5 systemd[1]: pkgfile-update.service: Failed with result 'exit-code'.
Jul 30 14:51:06 Yamo-Legion5 systemd[1]: Failed to start pkgfile database update.
Jul 30 14:52:02 Yamo-Legion5 kernel: kauditd_printk_skb: 2 callbacks suppressed
Jul 30 15:01:53 Yamo-Legion5 NetworkManager[627]: <warn>  [1659186113.1556] device (wlp4s0): no secrets: No agents were available for this request.
Jul 30 15:01:53 Yamo-Legion5 NetworkManager[627]: <warn>  [1659186113.1633] device (wlp4s0): Activation: failed for connection 'Orange-2459'
Jul 30 15:01:53 Yamo-Legion5 systemd-xdg-autostart-generator[7075]: /home/yamo/.config/autostart/org.kde.latte-dock.desktop:103: Unknown key name 'InitialPreference' in section 'Desktop Entry', ignoring.
Jul 30 15:01:53 Yamo-Legion5 systemd-xdg-autostart-generator[7075]: Configuration file /home/yamo/.config/autostart/org.kde.yakuake.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Jul 30 15:01:53 Yamo-Legion5 systemd-xdg-autostart-generator[7075]: Configuration file /home/yamo/.config/autostart/xdman.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Jul 30 15:01:55 Yamo-Legion5 sddm[710]: Signal received: SIGTERM
Jul 30 15:01:55 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 15:01:55 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 15:01:55 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 15:01:55 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 15:01:55 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 15:01:55 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 15:01:55 Yamo-Legion5 kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Jul 30 15:02:04 Yamo-Legion5 kernel: kauditd_printk_skb: 33 callbacks suppressed
Jul 30 15:02:04 Yamo-Legion5 kernel: watchdog: watchdog0: watchdog did not stop!

I want to understand why it died again.

brahma · 30 July 2022 15:38

check these logs:

EXT4-fs (nvme0n1p7): warning: mounting fs with errors, running e2fsck is recommended
kernel: ACPI: \: failed to evaluate _DSM (0x1001)
watchdog: watchdog0: watchdog did not stop!

also provide output from:
mhwd -l && mhwd -li

Yamo · 30 July 2022 16:22

yamo@Yamo-Legion5 ~]$ mhwd -l && mhwd -li
> 0000:03:00.0 (0200:10ec:8168) Network controller Realtek Semiconductor Co., Ltd.:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
         network-r8168            2016.04.20                true            PCI


> 0000:01:00.0 (0300:10de:1f95) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
video-hybrid-amd-nvidia-prime            2021.12.18               false            PCI
video-hybrid-amd-nvidia-470xx-prime            2021.12.18               false            PCI
          video-nvidia            2021.12.18               false            PCI
    video-nvidia-470xx            2021.12.18               false            PCI
           video-linux            2018.05.04                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI


> 0000:05:00.0 (0300:1002:1636) Display controller ATI Technologies Inc:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
video-hybrid-amd-nvidia-prime            2021.12.18               false            PCI
video-hybrid-amd-nvidia-470xx-prime            2021.12.18               false            PCI
           video-linux            2018.05.04                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI


> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
video-hybrid-amd-nvidia-prime            2021.12.18               false            PCI
           video-linux            2018.05.04                true            PCI


Warning: No installed USB configs!

brahma · 30 July 2022 16:28

disable watchdog:
open this:
kate /etc/default/grub and put into GRUB_CMDLINE_LINUX_DEFAULT the following kernel parameter:
nowatchdog
dont remove anything from there, just add it inside the quotes to already existing parameters, and just to be sure copy the line here
Then update grub:
sudo update-grub
Create a file:
sudo nano /etc/modprobe.d/blacklist.conf
Put there these lines:
blacklist iTCO_wdt
blacklist iTCO_vendor_support
Then CTRL+X, to save the file
Recreate initframs:
sudo mkinitcpio -P
Reboot

and do what this log suggest:

EXT4-fs (nvme0n1p7): warning: mounting fs with errors, running e2fsck is recommended

Yamo · 2 August 2022 05:08

I’ve done all the steps except the last step, for those steps can you explain what exactly I have done?
And also for the last step, I don’t know how to do it. (The e2fsck one)
I’m googling those right now but perhaps you could provide an answer.

brahma · 2 August 2022 06:53

the first steps disable watchdog
and the second one: e2fsck - it checks your hard drive for errors, since according to the log you may have some …
so provide output from:
lsblk

Yamo · 3 August 2022 03:15

AME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0  55.6M  1 loop /var/lib/snapd/snap/core18/2538
loop1         7:1    0 113.9M  1 loop /var/lib/snapd/snap/core/13308
loop2         7:2    0     4K  1 loop /var/lib/snapd/snap/bare/5
loop3         7:3    0  55.5M  1 loop /var/lib/snapd/snap/core18/2409
loop4         7:4    0   114M  1 loop /var/lib/snapd/snap/core/13425
loop5         7:5    0    62M  1 loop /var/lib/snapd/snap/core20/1581
loop6         7:6    0    62M  1 loop /var/lib/snapd/snap/core20/1587
loop7         7:7    0   105M  1 loop /var/lib/snapd/snap/android-file-transfer-linux/199
loop8         7:8    0 164.8M  1 loop /var/lib/snapd/snap/gnome-3-28-1804/161
loop9         7:9    0  81.3M  1 loop /var/lib/snapd/snap/gtk-common-themes/1534
loop10        7:10   0  91.7M  1 loop /var/lib/snapd/snap/gtk-common-themes/1535
loop11        7:11   0   2.6M  1 loop /var/lib/snapd/snap/playlist-dl/11
loop12        7:12   0   2.4M  1 loop /var/lib/snapd/snap/playlist-dl/9
loop13        7:13   0 362.3M  1 loop /var/lib/snapd/snap/qt513/24
loop14        7:14   0   1.1M  1 loop /var/lib/snapd/snap/rofi-snap/3
loop15        7:15   0    47M  1 loop /var/lib/snapd/snap/snapd/16292
loop16        7:16   0 383.9M  1 loop /var/lib/snapd/snap/qt515-core20/22
loop17        7:17   0 383.9M  1 loop /var/lib/snapd/snap/qt515-core20/23
loop18        7:18   0    47M  1 loop /var/lib/snapd/snap/snapd/16010
sda           8:0    0 931.5G  0 disk 
├─sda1        8:1    0    16M  0 part 
├─sda2        8:2    0 638.5G  0 part /run/media/yamo/Main
└─sda3        8:3    0   293G  0 part /run/media/yamo/EDU
nvme0n1     259:0    0 238.5G  0 disk 
├─nvme0n1p1 259:1    0   100M  0 part /boot/efi
├─nvme0n1p2 259:2    0    16M  0 part 
├─nvme0n1p3 259:3    0    98G  0 part /run/media/yamo/9640794240792A5F
├─nvme0n1p4 259:4    0   508M  0 part 
├─nvme0n1p5 259:5    0  51.3G  0 part /
├─nvme0n1p6 259:6    0  11.7G  0 part [SWAP]
└─nvme0n1p7 259:7    0  76.8G  0 part /home

brahma · 3 August 2022 07:07

so first unmount your home partiton (nvme0n1p7) - right click on your home partition in dolphin and click unmount
and then run the check:
sudo e2fsck -p /nvme0n1/nvme0n1p7

Yamo · 17 August 2022 10:13

Sorry for the very late reply, had some issues with work and the internet but thankfully they are now solved, I can’t seem to unmount the home directory it’s dimmed for me.
Also, I couldn’t run the check since I couldn’t unmount

brahma · 17 August 2022 13:16

well your home partition is a separate one, so you should be able to unmount it…
try unmounting it with:
sudo umount /nvme0n1/nvme0n1p7
then run:
sudo e2fsck -p /nvme0n1/nvme0n1p7
if it doesnt work, you need to boot into manjaro usb and run the check from there

Yamo · 18 August 2022 22:48

That’s the result of the first command

umount: /nvme0n1/nvme0n1p7: no mount point specified.

brahma · 19 August 2022 06:39

try this:
sudo umount /dev/nvme0n1p7
and check:
sudo e2fsck -p /dev/nvme0n1p7

Erim · 19 August 2022 07:14

Out of curiosity, is it necessary to log out of the desktop environment and perform that in a tty?
Won’t unmounting home during a session lead to problems?