https://bugs.kde.org/show_bug.cgi?id=391805
Nate Graham changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=391805
--- Comment #5 from Arek Guzinski ---
Bug no longer occurs in 5.12.5 :)
As for formalaties: should I set the status to closed, or should that be done
by the assignee/maintainer/whoever after some investigation into what might
have fixed it? Are there a
https://bugs.kde.org/show_bug.cgi?id=391805
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=391805
Arek Guzinski changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=391805
--- Comment #3 from Arek Guzinski ---
> Can you include output of ~/.local/share/sddm/xorg-session.log after logging
> in.
I would, if there was something to include.
$ ls -l ~/.local/share/sddm/xorg-session.log
-rw--- 1 arek arek 0 Mär 13 14:29
/
https://bugs.kde.org/show_bug.cgi?id=391805
David Edmundson changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=391805
--- Comment #1 from David Edmundson ---
>What would, under normal circumstances, tell ksplashqml to quit?
Plasma signalling it's ready (along with some other modules)
Can you include output of ~/.local/share/sddm/xorg-session.log after logging
in.
--
https://bugs.kde.org/show_bug.cgi?id=391805
Kai Uwe Broulik changed:
What|Removed |Added
CC||k...@privat.broulik.de,
|
