Bug 452069

Summary:	No plasmashell available on unlocking on Wayland
Product:	[Plasma] plasmashell	Reporter:	John E <john.ettedgui>
Component:	generic-crash	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED BACKTRACE
Severity:	crash	CC:	nate
Priority:	NOR
Version First Reported In:	5.24.4
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description John E 2022-03-30 07:42:41 UTC

SUMMARY
Hello,

I just switched to using Wayland yesterday with 2 monitors so I have no idea if this behavior is expected, or new, etc. Apologies!

When I leave my computer unattended, it runs an intensive GPU miner and autolocks the session. When I come back later, plasmashell has likely crashed but the rest of the desktop seems fine and restarting plasmashell works. I am not sure if this is related to the intensive miner, or auto session locking or else, but this behavior did not happen on X11, though on X11 I was using 5.24.3 and only a single monitor so maybe there's that too. This bug may be related to #448475.

STEPS TO REPRODUCE
1. Run the miner
2. Leave the session unattended and turn of the 2 monitors.
3. Come back later to an autolocked session.
4. Unlock
OBSERVED RESULT
Find plasmashell missing.

EXPECTED RESULT
The desktop should be as left earlier.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Arch Linux, Linux 5.16.18
(available in About System)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92
Qt Version: 5.15.3+kde+r137-1

ADDITIONAL INFORMATION

Comment 1 John E 2022-03-30 07:44:22 UTC

Unlike #445752 a simple quick lock/unlock does not crash it.

Comment 2 Nate Graham 2022-04-01 18:37:39 UTC

If something crashed, we need a backtrace of it so we can figure out what's going on. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Can you please attach one? Thanks!

Comment 3 John E 2022-04-01 20:08:28 UTC

(In reply to Nate Graham from comment #2)
> If something crashed, we need a backtrace of it so we can figure out what's
> going on. See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports
> 
> Can you please attach one? Thanks!

Well, it hasn't crashed in a couple days now.
Not sure what fixed it though since I saw no update since then, only a rebuild of frameworks.

I guess I'll close this for now, and reopen with a backtrace if it shows up again.
Thank you!