https://bugs.kde.org/show_bug.cgi?id=495765
--- Comment #14 from Peter ---
OK great news, it does sound very similar. Currently running kernel 6.13.5 so
will continue to monitor and check when 6.14 is release the problem goes away.
I might also monitor RAM usage and see when its running high, I c
https://bugs.kde.org/show_bug.cgi?id=495765
Méven changed:
What|Removed |Added
CC||me...@kde.org
--- Comment #13 from Méven ---
Could it
https://bugs.kde.org/show_bug.cgi?id=495765
alderae...@gmail.com changed:
What|Removed |Added
CC||alderae...@gmail.com
--- Comment #12 from
https://bugs.kde.org/show_bug.cgi?id=495765
--- Comment #11 from Peter ---
Created attachment 175771
--> https://bugs.kde.org/attachment.cgi?id=175771&action=edit
Last unsuccesful resume Nov 11th
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=495765
--- Comment #10 from Peter ---
That does appear each time even when successful resume from sleep. This is a
rare, but annoying issue, so since posting this its only happened once. This
time docked to Lenovo displaylink with two external screens but also
https://bugs.kde.org/show_bug.cgi?id=495765
--- Comment #9 from Nate Graham ---
> kscreenlocker_greet[4984]: Failed to write to the pipe: Bad file descriptor
That seems related, and bad.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=495765
--- Comment #8 from Peter ---
Ah ok I didnt now that, they look the mirror image of each other. But yes
looking at a journal logs and locking the computer and unlocking its showing
kscreenlocker, same if I sleep and wake up.
Nov 09 11:16:46 arhclinuxT
https://bugs.kde.org/show_bug.cgi?id=495765
Nate Graham changed:
What|Removed |Added
Severity|crash |major
Summary|Resume from sleep freeze
