https://bugs.kde.org/show_bug.cgi?id=376755
--- Comment #7 from Kathie Dart ---
Created attachment 104157
--> https://bugs.kde.org/attachment.cgi?id=104157=edit
kde info without compositing
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376755
--- Comment #6 from Kathie Dart ---
OK - I tried manually suspending - this appeared to work just fine.
So am I to understand that this isn't a kscreenlocker bug - but a bug with the
way suspends are (or are not) handled?
--
You
https://bugs.kde.org/show_bug.cgi?id=376755
--- Comment #5 from Martin Gräßlin ---
Could you also provide the support information with compositing. That has the
interesting part for me. Please also just paste here instead of paste.kde.org
as that expires.
> I just close the
https://bugs.kde.org/show_bug.cgi?id=376755
--- Comment #4 from Kathie Dart ---
I just close the lid and the laptop suspends by ACPI.
It resumes and I can see all the data as above.
Here's the support info:
https://paste.kde.org/plxnvff4o
It has also happened before
https://bugs.kde.org/show_bug.cgi?id=376755
--- Comment #3 from Martin Gräßlin ---
How do you suspend the system? Can you please provide the output of:
qdbus org.kde.KWin /KWin supportInformation
Please note that the screenlocker does ensure that the screen is locked prior
https://bugs.kde.org/show_bug.cgi?id=376755
Kathie Dart changed:
What|Removed |Added
Platform|Ubuntu Packages |unspecified
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=376755
--- Comment #1 from Martin Gräßlin ---
Which version are you using?
--
You are receiving this mail because:
You are watching all bug changes.