Bug 478907 - kwin_wayland: crash when clicking on clipboard's "Delete history" button
Summary: kwin_wayland: crash when clicking on clipboard's "Delete history" button
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 5.27.10
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: usability, wayland-only
Depends on:
Blocks:
 
Reported: 2023-12-23 01:24 UTC by soulsofblack12
Modified: 2024-06-04 09:06 UTC (History)
2 users (show)

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


Attachments
Log file containing an excerpt of journalctl log showing the error (4.74 KB, text/x-log)
2023-12-23 01:24 UTC, soulsofblack12
Details

Note You need to log in before you can comment on or make changes to this bug.
Description soulsofblack12 2023-12-23 01:24:14 UTC
Created attachment 164379 [details]
Log file containing an excerpt of journalctl log showing the error

SUMMARY
***
Since a reinstall of Arch Linux with KDE Plasma 5.27.10, I've been observing this weird bug with kwin_wayland, in which whenever I try to delete the entire clipboard's history by clicking the button to do so, kwin_wayland crashes and restarts. This is not reproducible on X11. This happens with any amount of clipboard content.
Attaching a copy of journalctl logs: 
***


STEPS TO REPRODUCE
1. Add anything to the clipboard.
2. Go to the clipboard, and click the button to clean the entire history.

OBSERVED RESULT
kwin_wayland crashes and restarts.

EXPECTED RESULT
The window that asks for confirmation on emptying the clipboard should appear.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux with KDE Plasma 5.27.10
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION
GPU: AMD RX 6600 XT using drm driver, not using xf86-video-amdgpu.
Comment 1 David Edmundson 2023-12-23 22:20:03 UTC
For crashes we need a backtrace rather than logs.
Hopefully we'll find this on our automatic crash reporting tracker, failing that run coredumpctl dump kwin_wayland
Comment 2 soulsofblack12 2023-12-24 23:15:07 UTC
(In reply to David Edmundson from comment #1)
> For crashes we need a backtrace rather than logs.
> Hopefully we'll find this on our automatic crash reporting tracker, failing
> that run coredumpctl dump kwin_wayland

Hello David, I had to upload the coredump to Google Drive since it's really large. I discovered that the issue is caused by Kvantum themes, anyone of them, even the stock themes.
https://drive.google.com/file/d/1G18UtB4hJ0QGgWkOTUpE0OwbwYq9uyzm/view?usp=drive_link
Comment 3 Bug Janitor Service 2024-01-08 03:45:53 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 4 soulsofblack12 2024-01-29 23:39:24 UTC
Any updates?
Comment 5 David Edmundson 2024-06-04 09:06:07 UTC
I cannot reproduce this issue, and the google drive link is now inaccessible