https://bugs.kde.org/show_bug.cgi?id=400058
David Edmundson changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
--- Comment #8 from David Edmundson
https://bugs.kde.org/show_bug.cgi?id=400058
--- Comment #7 from JordanL ---
I too can confirm the issue is fixed since the second batch of Qt updates.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400058
Chris Cheney changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
--- Comment #4 from Chris Cheney ---
How
https://bugs.kde.org/show_bug.cgi?id=400058
Chris Cheney changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
--- Comment #4 from Chris Cheney ---
How
https://bugs.kde.org/show_bug.cgi?id=400058
--- Comment #6 from Chris Cheney ---
I just noticed a big Qt update got pushed to neon today which fixed the
problem.
Apparently KDE/Qt updates are very fragile, and is not reflected by soname
updates. :-\
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=400058
David Edmundson changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
CC|
https://bugs.kde.org/show_bug.cgi?id=400058
--- Comment #2 from JordanL ---
My issue also started today, after the update of Qt to 5.11.2. It happens
whether the Plasma or the Plasma Wayland session is selected. I was going to
file a bug for SDDM, but couldn't find it (is it not a KDE project?).
https://bugs.kde.org/show_bug.cgi?id=400058
JordanL changed:
What|Removed |Added
CC||jordanlepp...@gmail.com
--- Comment #1 from JordanL
https://bugs.kde.org/show_bug.cgi?id=400058
Chuck Ard changed:
What|Removed |Added
CC||chuck.a...@gmail.com
--
You are receiving this
