https://bugs.kde.org/show_bug.cgi?id=447769
--- Comment #1 from [email protected] --- It could be similar to: https://wiki.archlinux.org/title/Wayland#Troubleshooting but more comprehensive and KDE-specific I was mistaken about the logs, it's included here: https://community.kde.org/KWin/Wayland#Reading_wayland_session_logs (but not in the other pages). However, these logs don't have timestamps so it's at least difficult to find out the log entries during earlier problems. Additionally, the log is very long - how can one find the cause of a problem even if there were timestamps (are there some kind of specific entries for a crash like ERROR keywords)? Furthermore, the logs should be included in KSystemLog. One example log entry is: > [impl-module.c:77 find_module()] could not open > /usr/lib/x86_64-linux-gnu/pipewire-0.3: File or directory not found -- You are receiving this mail because: You are watching all bug changes.
