[kwin] [Bug 447769] The wiki page/s about Wayland should include info about Wayland logs, ways to troubleshoot and common problems

2024-04-08 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=447769

myndstr...@protonmail.ch changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=485230

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 447769] The wiki page/s about Wayland should include info about Wayland logs, ways to troubleshoot and common problems

2022-01-11 Thread Nate Graham 
https://bugs.kde.org/show_bug.cgi?id=447769

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

--- Comment #2 from Nate Graham  ---
Not a bad idea.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 447769] The wiki page/s about Wayland should include info about Wayland logs, ways to troubleshoot and common problems

2022-01-01 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=447769

--- Comment #1 from myndstr...@protonmail.ch ---
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.