- install message handler that writes debug messages in the kscreen.* categories and track outputs
- add KSCREEN_PLASMASHELL debug category
- debugging for output changes, pretty basic, maybe we want to add some
Details
Details
- Reviewers
mart
tested if these things now end up in kscreen.log, they do
Diff Detail
Diff Detail
- Repository
- R120 Plasma Workspace
- Branch
- sebas/kscreenlog
- Lint
No Linters Available - Unit
No Unit Test Coverage
| shell/shellcorona.cpp | ||
|---|---|---|
| 87 | static | |
| 95 | Just saying: I don't like this writing to a dedicated file per session. We are starting to introduce a second xsession-errors. Also I don't like that we have a duplication for the log message handling here between kscreen and plasma-workspace. If we want to start having additional applications write to the kscreen log, libkscreen should expose an API for it. I also have to ask why debug messages like "plasmashell starting" should go into a "kscreen.log". How is that in any way related to kscreen? This is semantically not correct. I understand that you want everything multi screen related in one log file, but then please get the semantics correct. | |
| 125 | this is not screen related | |
Comment Actions
We may already have fixed the most pressing problem needing this, so postponing/abandoning it for now.
Comment Actions
Sorry, my fault. I was completely unaware that Plasma does not even use kscreen. Now that I have seen how it works, I am no longer disappointed to not find Plasma steps in the kscreen logs.