Bug 486449 - Plasmashell exits with Wayland protocol error ("error 3: xdg_surface must not have a buffer at creation") after resume from sleep
Summary: Plasmashell exits with Wayland protocol error ("error 3: xdg_surface must not...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 6.0.4
Platform: Other Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: wayland
: 454524 484878 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-05-02 11:28 UTC by Graeme Murray
Modified: 2024-05-16 18:58 UTC (History)
7 users (show)

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


Attachments
log file (2.77 KB, text/plain)
2024-05-02 11:28 UTC, Graeme Murray
Details
output from wayland-debug=1 (1.34 MB, text/plain)
2024-05-03 21:59 UTC, Graeme Murray
Details
debug info (11.48 KB, text/plain)
2024-05-15 07:44 UTC, Graeme Murray
Details
backtrace of latest crash (53.44 KB, text/vnd.kde.kcrash-report)
2024-05-16 04:22 UTC, Graeme Murray
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Graeme Murray 2024-05-02 11:28:37 UTC
Created attachment 169097 [details]
log file

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
Plasmashell crashes after resume from sleep

STEPS TO REPRODUCE
1.  Click on sleep icon in application launcher
2.  Resume from sleep.
3.  Click on application launcher

OBSERVED RESULT
Screen goes blank, then restarts.

EXPECTED RESULT
System to resume as normal without crash

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  Fedora 40/KDE 6.0.4
(available in About System)
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7

ADDITIONAL INFORMATION
Kernel 6.8.8-300
Comment 1 Nate Graham 2024-05-03 20:01:39 UTC
Looks like it's a Wayland protocol error, not actually a crash:

May 02 13:13:33 kwin_wayland_wrapper[2002]: error in client communication (pid 2301)
May 02 13:13:33 plasmashell[2301]: xdg_wm_base@3: error 3: xdg_surface must not have a buffer at creation
May 02 13:13:33 plasmashell[2301]: The Wayland connection experienced a fatal error: Protocol error

Now we need to figure out which exact thing is causing it.

Can you please run `WAYLAND_DEBUG=1 plasmashell --replace` in a terminal window, then reproduce the crash, and then attach the entire contents of the output (it will be long) as a file here? Thanks!
Comment 2 Graeme Murray 2024-05-03 21:59:21 UTC
Created attachment 169165 [details]
output from wayland-debug=1

it seems like it happens every other plasmashell restart. If I can try anything else, let me know.
Comment 3 Nate Graham 2024-05-03 23:07:17 UTC
Thanks, that's helpful.

[3221647.862] wl_display@1.delete_id(159)
[3221647.942] wl_display@1.error(xdg_wm_base@3, 3, "xdg_surface must not have a buffer at creation")
xdg_wm_base@3: error 3: xdg_surface must not have a buffer at creation

So it's trying to delete a screen.
Comment 4 Nate Graham 2024-05-03 23:21:44 UTC
Do you by any chance have multiple screens when sleeping or waking up?
Comment 5 Graeme Murray 2024-05-04 06:39:20 UTC
No, just one screen.
Comment 6 Nate Graham 2024-05-14 23:19:46 UTC
*** Bug 484878 has been marked as a duplicate of this bug. ***
Comment 7 Nate Graham 2024-05-14 23:20:22 UTC
*** Bug 454524 has been marked as a duplicate of this bug. ***
Comment 8 Graeme Murray 2024-05-15 07:44:34 UTC
Created attachment 169495 [details]
debug info

Fedora has just released an update, kf6- , upto 6.2.0-1 and qt6-qtbase upto 6.7.0-5 and behaviour has changed, no black screen now but get drkonqi crash report. Have added an attachment of the output and sent a automated crash report.
Comment 9 Graeme Murray 2024-05-16 04:22:03 UTC
Created attachment 169522 [details]
backtrace of latest crash

wake from sleep
Comment 10 Nate Graham 2024-05-16 18:58:26 UTC
Ok, that's Bug 482768. Sounds like this one is fixed now.