https://bugs.kde.org/show_bug.cgi?id=474811
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |crash
Resolution|--- |WAITINGFORINFO
Status|REPORTED |NEEDSINFO
--- Comment #1 from Nate Graham <n...@kde.org> ---
Sep 21 08:01:27 latitude kernel: traps: kscreenlocker_g[14410] general
protection fault ip:7f7f9c847de8 sp:7fff4bc6d988 error:0 in
libQt5Qml.so.5.15.10[7f7f9c6a7000+281000]
Well that doesn't seem good. There's also:
Sep 21 08:01:27 latitude kscreenlocker_greet[14825]: qt.qpa.wayland: Creating a
fake screen in order for Qt not to crash
Sep 21 08:01:27 latitude kscreenlocker_greet[14825]: The Wayland connection
experienced a fatal error: Das Argument ist ungültig ("Invalid argument" in
English)
Sep 21 08:01:27 latitude kscreenlocker_greet[14837]: qt.qpa.wayland: Creating a
fake screen in order for Qt not to crash
Sep 21 08:01:27 latitude kscreenlocker_greet[14837]: The Wayland connection
broke. Did the Wayland compositor die?
If you run `coredumpctl --reverse`, do you see any crashes in kwin_wayland, or
kscreenlocker_greet in the first 10 or 15 entries?
Does it ever happen with only a single screen connected?
--
You are receiving this mail because:
You are watching all bug changes.
