Bug 447769

Summary:	The wiki page/s about Wayland should include info about Wayland logs, ways to troubleshoot and common problems
Product:	[Plasma] kwin	Reporter:	myndstream
Component:	platform-wayland-nested	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	REPORTED ---
Severity:	wishlist	CC:	nate
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=485230
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description myndstream 2022-01-01 11:30:22 UTC

SUMMARY
An overview wiki page about Wayland under KDE, like https://community.kde.org/Goals/Wayland, should include info about Wayland logs, ways to troubleshoot and common problems.

Here I asked: Why are sessions breaking when starting from standby on Debian with Wayland - why does this occur and prevent it? Which things (logs etc) should I check or test to do so? https://unix.stackexchange.com/q/684498/233262 A solution to this issue could also be linked in an answer to that question.

I think common problems include for example issues with Nvidea drivers.
If there are no dedicated Wayland logs maybe there is a way to scan logs for Wayland-related errors.
Helping people to quickly and correctly identify the problems they have with Wayland would make things much better and easier for many.

STEPS TO REPRODUCE
1. Switch to Wayland on KDE
2. Experience a problem
3. Try to do something about it (or identify what's causing the problem)

OBSERVED RESULT
No well-findable page that describes the first steps you should take to solve (or at least identify) the problem/s.

EXPECTED RESULT
An overview page about Wayland in KDE that gives you steps or things to do for troubleshooting depending on your problem and helps you identify the problem.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian 11
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
KSystemLog: "4:20.12.0-1"

ADDITIONAL INFORMATION

Comment 1 myndstream 2022-01-01 11:47:53 UTC

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

Comment 2 Nate Graham 2022-01-12 01:41:51 UTC

Not a bad idea.