https://bugs.kde.org/show_bug.cgi?id=444742
burne...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burne...@gmail.com
--- Comment #7 from burne...@gmail.com ---
Created attachment 144636
--> https://bugs.kde.org/attachment.cgi?id=144636&action=edit
journal output at the time of the crash
Not completely sure if this is the same crash, but seeing you mention monitors
makes me suspect it is. In my case this has been happening since I got a new
monitor that is a different resolution than my other monitor (and different
orientation; I run my secondary monitor in portrait mode), so I think in my
case it's caused by two different-resolution monitors waking up. One of my
monitors takes 5-10 seconds longer to wake up than the other, which may also
have a contributing effect.
In my case the issue is far older than this report (I've been having it since
November 2020, when I got a new monitor), but for a while it went away when I
switched from an NVidia GPU to an AMD one -- only to return after I upgraded to
Plasma 5.23.
I'm attaching journal output from one crash from a few days ago.
PS: at least on Fedora the easiest way to restart Plasmashell is with
"systemctl --user restart plasma-plasmashell". If your system doesn't have a
systemd service for Plasmashell for some reason, you can use something like
this, though beware that any error output from Plasmashell will be discarded if
you do this: "nohup plasmashell --replace &> /dev/null & disown"
--
You are receiving this mail because:
You are watching all bug changes.
