https://bugs.kde.org/show_bug.cgi?id=456210
--- Comment #67 from ratijas <m...@ratijas.tk> ---
> This issue brings Plasma's reliability to 0
While I understand that situation kinda sucks for people like you who encounter
this bug, that is an emotional overstatement. Please, keep it ethical.
> When can I expect to see this fix on my PC?
As soon as we have someone to reliably reproduce the issue. So far it happened
to minority of users (me personally included), and goes away as soon as we try
to investigate. There's only so much extrasensory powers we possess, so it's
rather hard to give any reasonable expectations in such situation ¯\_(ツ)_/¯
> I would actually like better instructions to send logs to debug the error. Is
> it possible to attach something do SDDM and generate better logs? It's hard
> to reproduce this bug.
First, this is not about SDDM but about kscreenlocker. Although I admit they
look almost indistinguishable at a glance. But SDDM is a login manager, for
signing into a new session with a new user; while kscreenlocker is a lock
screen for an already logged in user.
Second, starting with Plasma 5.27.1 (hopefully?[1]) you could open
KDebugSettings app, and raise logging level for "KScreenLocker (greeter)"
component. But for now you can put this line in your ~/.bash_profile or
~/.zprofile depending on your shell:
export QT_LOGGING_RULES=kscreenlocker_greet.debug=true
Lastly, you may try setting up dev environment (it's fairly easy with
kdesrc-build[2]) and building kscreenlocker from git. Add print() calls in QML
files here and there, and check logs in journal:
journalctl --user -ef --no-pager
Note that most components are in plasma-workspace repository under
lookandfeel/org.kde.breeze directory[3], because they are reused between screen
locker and SDDM themes.
I hope that helps!
[1]: https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/129
[2]: https://invent.kde.org/sdk/kdesrc-build
[3]:
https://invent.kde.org/plasma/plasma-workspace/-/tree/master/lookandfeel/org.kde.breeze/contents
--
You are receiving this mail because:
You are watching all bug changes.
