https://bugs.kde.org/show_bug.cgi?id=487699
--- Comment #21 from Mark Deneen ---
(In reply to TraceyC from comment #19)
> I'm not able to reproduce this right now on git-master
>
> Screen lock timeout - 1 min
> Konversation running
> 1. Laptop closed with external monit
https://bugs.kde.org/show_bug.cgi?id=487699
--- Comment #18 from Mark Deneen ---
(In reply to jy6x2b32pie9 from comment #17)
> I think I isolated cause of the crash? If konversation is running,
> plasmashell crashes. If konversation is not running, plasmashell survives
> lock and unlock
https://bugs.kde.org/show_bug.cgi?id=499324
--- Comment #6 from Mark Deneen ---
This is definitely still a problem, although I've worked around it by disabling
the laptop monitor.
You may be able to recreate it by adding an external monitor to a laptop and
making it the primary display.
https://bugs.kde.org/show_bug.cgi?id=499324
--- Comment #4 from Mark Deneen ---
I disabled the laptop monitor last week, and unlocked the screen today. I also
set "Preferred Ozone platform" to "Wayland" in Chrome.
There was no delay and no crash when unlocking my desktop th
https://bugs.kde.org/show_bug.cgi?id=499324
--- Comment #3 from Mark Deneen ---
I also wanted to note that I have both the laptop screen and an external
monitor active.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=499324
--- Comment #2 from Mark Deneen ---
Hey Nate,
The system is not configured to sleep unless it's on battery power, which it is
not.
The device itself has two GPUs and I have the nvidia drivers installed.
01:00.0 VGA compatible controller: N
https://bugs.kde.org/show_bug.cgi?id=499324
Bug ID: 499324
Summary: plasmashell crashes after extended period of lock time
Classification: Plasma
Product: plasmashell
Version: 6.2.5
Platform: Arch Linux
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=494451
--- Comment #9 from Mark Deneen ---
I tried unlocking from the other screen but the behavior was the same. I will
attach another trace to this bug report. This trace shows the syscalls of
kwin_wayland from the time I unlock until the time the desktop
https://bugs.kde.org/show_bug.cgi?id=494451
Mark Deneen changed:
What|Removed |Added
Attachment #175916|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=494451
Mark Deneen changed:
What|Removed |Added
Version|6.1.5 |6.2.3
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=494451
Mark Deneen changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=494451
Mark Deneen changed:
What|Removed |Added
Attachment #174630|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=494451
--- Comment #5 from Mark Deneen ---
We may be able to close this. The problem seems to have vanished after I
removed some .desktop files from ~/Desktop.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=494451
--- Comment #4 from Mark Deneen ---
I will do a test this weekend, and close all programs except for the core of
Plasma (no browsers open, etc) and see what happens when I unlock the session
on Monday.
My gut feeling is that it has to do with the
https://bugs.kde.org/show_bug.cgi?id=494451
--- Comment #2 from Mark Deneen ---
The length of time the session remains locked seems to impact how long the
desktop remains frozen when it is unlocked. Leaving it locked over night or
for the weekend is pretty bad.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=494451
--- Comment #1 from Mark Deneen ---
I also wanted to mention that this typically happens after the screen has been
locked for the night. One or two notifications may not be enough to trigger
the behavior.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=494451
Bug ID: 494451
Summary: Desktop session freezes for several minutes after
unlocking if notifications are received while the
desktop session was locked
Classification: Plasma
Pr
17 matches
Mail list logo
