https://bugs.kde.org/show_bug.cgi?id=447887
--- Comment #11 from aart...@gmail.com ---
Created attachment 162931
--> https://bugs.kde.org/attachment.cgi?id=162931=edit
screenshot
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447887
--- Comment #10 from aart...@gmail.com ---
Created attachment 162930
--> https://bugs.kde.org/attachment.cgi?id=162930=edit
jorunalctl
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447887
--- Comment #9 from aart...@gmail.com ---
same issue in my case. I'm adding a screenshot and journalctl
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447887
aart...@gmail.com changed:
What|Removed |Added
CC||aart...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=447887
mason2...@gmail.com changed:
What|Removed |Added
CC||mason2...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=447887
--- Comment #8 from jollesollepo...@gmail.com ---
(In reply to Nate Graham from comment #7)
> Ok, so let's use this only to track the graphical glitches.
Alright, although the laggy ness also happens even if there isn't any crash,
when it does I have
https://bugs.kde.org/show_bug.cgi?id=447887
Nate Graham changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Summary|Compositing crashes
