Bug 484878 - Plasma crashes after wakeup from suspend when clicking on the Kickoff launcher
Summary: Plasma crashes after wakeup from suspend when clicking on the Kickoff launcher
Status: RESOLVED DUPLICATE of bug 486449
Alias: None
Product: plasmashell
Classification: Plasma
Component: Application Launcher (Kickoff) widget (show other bugs)
Version: 6.0.3
Platform: Other Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-01 16:10 UTC by zvova7890
Modified: 2024-05-14 23:19 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description zvova7890 2024-04-01 16:10:20 UTC
SUMMARY
Apr 01 19:01:25 minipc kwin_wayland_wrapper[797]: error in client communication (pid 2555)
Apr 01 19:01:25 minipc plasmashell[2555]: xdg_wm_base@3: error 3: xdg_surface must not have a buffer at creation
Apr 01 19:01:25 minipc plasmashell[2555]: The Wayland connection experienced a fatal error: Protocol error


STEPS TO REPRODUCE
1. Suspend/resume
2. Click on the Kickoff icon

OBSERVED RESULT
Plasma crash

EXPECTED RESULT
Kickoff menu appears

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.8.2-zen2-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 9 7940HS w/ Radeon 780M Graphics
Memory: 28.2 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Micro Computer (HK) Tech Limited
Product Name: Venus series

ADDITIONAL INFORMATION
It is only feasible on one computer. Others do not have this bug, probably related to some AMD issue. However, the crash occurs only on clicking Kickoff, so perhaps it can be addressed.
Comment 1 Marco Martin 2024-04-02 14:31:13 UTC
Can you reproduce with debug symbols? see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 2 zvova7890 2024-04-02 16:34:04 UTC
I assume this won't help because the compositor simply raises the error, which the client receives, prints, and then exit(). But if you sure that I'm wrong I'll do breakpoint on the exit function and take the backtrace from all threads before exit.
Comment 3 zvova7890 2024-04-03 00:48:29 UTC
Important note: When you navigate to Kickoff -> sleep, and then after wakeup Kickoff is still showing - there's no crash. However, if Kickoff has disappeared, a protocol error occurs, leading to _exit(-1) in QWaylandDisplay::checkWaylandError(). 

I suspect there may be an issue with the QPA plugin. Also, I assume, if go to sleep through 'systemd sleep' - there will be no crash.
Comment 4 Bug Janitor Service 2024-04-18 03:47:37 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2024-05-03 03:46:02 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 6 zvova7890 2024-05-03 21:17:21 UTC
I still experience this
Comment 7 Nate Graham 2024-05-14 23:19:46 UTC

*** This bug has been marked as a duplicate of bug 486449 ***