Journal Error log

Support
1

I am running Manjaro KDE unstable. I find that the following error appear in journal

   ~  journalctl -p 3 -b                                                                                                                                         ✔ 
Aug 23 14:36:18 ajayc-X430UA kernel: x86/cpu: SGX disabled by BIOS.
Aug 23 14:36:18 ajayc-X430UA kernel: blacklist: Problem blacklisting hash (-13)
Aug 23 14:36:18 ajayc-X430UA kernel: blacklist: Problem blacklisting hash (-13)
Aug 23 14:36:18 ajayc-X430UA kernel: blacklist: Problem blacklisting hash (-13)
Aug 23 14:36:18 ajayc-X430UA kernel: blacklist: Problem blacklisting hash (-13)
Aug 23 14:36:20 ajayc-X430UA systemd-udevd[325]: could not read from '/sys/module/pcc_cpufreq/initstate': No such device
Aug 23 14:36:20 ajayc-X430UA kernel: i2c_hid_acpi i2c-ELAN1300:00: device returned incorrect report (2 vs 14 expected)
Aug 23 14:36:22 ajayc-X430UA systemd[618]: Failed to start Update XDG user dir configuration.
Aug 23 14:38:34 ajayc-X430UA kded5[766]: org.kde.plasma.dataengine.geolocation: error:  "Unknown host location.services.mozilla.com: Host not found"
Aug 23 14:38:34 ajayc-X430UA kded5[766]: org.kde.plasma.dataengine.geolocation: error:  "Unknown host location.services.mozilla.com: Host not found"
Aug 23 15:11:14 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 23 15:17:14 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 23 15:17:15 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 23 15:17:19 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 23 15:17:20 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 23 15:18:05 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 23 15:18:06 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 23 15:18:37 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 23 15:18:38 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 23 15:19:08 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 23 15:19:09 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 23 15:21:59 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 23 15:22:01 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 23 15:24:02 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 23 15:24:03 ajayc-X430UA soffice.bin[2623]: QWaylandShmBuffer: mmap failed (Invalid argument)

My query is with regard to errors relating to “problem blacklisting …” and " soffice.bin - QwaylandShmBuffer". As regards error " system-udevd …", it appear occasionaly.
The error relating to geolocation is due to Nightlight app which if disabled resolves the error.

I know the bugs are bound to be there in unstable version. So my query is whether I can do something to resolve these errors or just accept them as a bye-product of unstable version

Operating System: Manjaro Linux
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernel Version: 5.19.3-2-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: VivoBook S14 X430UA
System Version: 1.0
2

That is the known issue because of upgrade of Linux Kernel 5.19 when using some devices and BIOS setting

See: Strange kernel errors during boot after 5.19 / Kernel & Hardware / Arch Linux Forums

LibreOffice may has the problem with Wayland using buffer

3

Thanks @Zesko
In the embedded post, it is mentioned that removing system keys seem to resolve the kernel error. I do not want to go that route as I am afraid it might lead to some issue when booting/reinstalling win11 (I am on dual boot).

I am fine to live with the error.