Bug 472980 - Plasmashell crashes sometimes when clearing the clipboard
Summary: Plasmashell crashes sometimes when clearing the clipboard
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Clipboard widget & pop-up (other bugs)
Version First Reported In: 5.27.7
Platform: Neon Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-03 21:41 UTC by the_archer_xz
Modified: 2023-10-02 03:46 UTC (History)
1 user (show)

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


Attachments
plasmashell-20230804-132004.kcrash (7.96 KB, text/vnd.kde.kcrash-report)
2023-08-06 09:51 UTC, the_archer_xz
Details
Screenshot_20230806_034809.png (69.85 KB, image/png)
2023-08-06 09:51 UTC, the_archer_xz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description the_archer_xz 2023-08-03 21:41:28 UTC
SUMMARY
***
Plasmashell crashes sometimes when clearing the clipboard.
***


STEPS TO REPRODUCE
1. Copy various text
2. Clear clipboard

OBSERVED RESULT

Plasmashell crashes

EXPECTED RESULT

Clipboard should clear. No crashing

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 5.19.0-50-generic (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics
Memory: 31.1 GiB of RAM
Graphics Processor: AMD Radeon RX 570 Series

ADDITIONAL INFORMATION

NA.
Comment 1 Nate Graham 2023-08-04 19:05:50 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?
Thanks!
Comment 2 the_archer_xz 2023-08-06 09:51:24 UTC
Created attachment 160775 [details]
plasmashell-20230804-132004.kcrash

All I get is this:

"The crash information could not be generated."

I also attached a kcrash file that I could save. Maybe you can get something 
out of that. Also, when I run coredumpctl after the crash, it just comes up 
empty.

On Friday, August 4, 2023 1:05:50 P.M. MDT you wrote:
> https://bugs.kde.org/show_bug.cgi?id=472980
> 
> Nate Graham <nate@kde.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> Status|REPORTED                    |NEEDSINFO
>          Resolution|---                         |BACKTRACE
>                  CC|                            |nate@kde.org
> 
> --- Comment #1 from Nate Graham <nate@kde.org> ---
> If something crashed, we need a backtrace of it so we can figure out what's
> going on. Can you please attach a backtrace of the crash using the
> coredumpctl command-line program, as detailed in
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_usef
> ul_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Thanks!
> 
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 the_archer_xz 2023-08-06 09:51:24 UTC
Created attachment 160776 [details]
Screenshot_20230806_034809.png
Comment 4 Bug Janitor Service 2023-08-21 03:45:16 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 the_archer_xz 2023-09-01 01:44:49 UTC
(In reply to Nate Graham from comment #1)
> If something crashed, we need a backtrace of it so we can figure out what's
> going on. Can you please attach a backtrace of the crash using the
> coredumpctl command-line program, as detailed in
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?
> Thanks!

Never mind. After much hell, I figured out a perfect solution; delete the ~/.config/plasma-org.kde.plasma.desktop-appletsrc file and generate a new one by logging off and logging back in. Seems like that fixed everything regarding this issue I have been having. I think this issued occurred because I was running X11 and now I am using Wayland. And I manually set my settings all over again. Haven't experienced a single crash yet.  Hopefully I didn't just jinx myself. :)
Comment 6 the_archer_xz 2023-09-01 01:47:06 UTC
(In reply to Nate Graham from comment #1)
> If something crashed, we need a backtrace of it so we can figure out what's
> going on. Can you please attach a backtrace of the crash using the
> coredumpctl command-line program, as detailed in
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?
> Thanks!

You might want to mention this to people who are switching over from X11 to Wayland. Which is: delete the ~/.config/plasma-org.kde.plasma.desktop-appletsrc file and generate a new one by logging off and logging back in.
Comment 7 the_archer_xz 2023-09-02 05:17:17 UTC
(In reply to Nate Graham from comment #1)
> If something crashed, we need a backtrace of it so we can figure out what's
> going on. Can you please attach a backtrace of the crash using the
> coredumpctl command-line program, as detailed in
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?
> Thanks!

Spoke too soon. Still crashing. Just not as often.
Comment 8 Bug Janitor Service 2023-09-17 03:45:33 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 9 Bug Janitor Service 2023-10-02 03:46:07 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!