Bug 444641 - Crash wl_display@1: error 1: invalid arguments for org_kde_plasma_window@207.get_icon
Summary: Crash wl_display@1: error 1: invalid arguments for org_kde_plasma_window@207....
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.22.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-30 02:05 UTC by Ash
Modified: 2021-12-01 04:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
systemd logs at time of crash, see 12:46:44 and 12:46:56 (505.14 KB, text/x-log)
2021-10-30 02:05 UTC, Ash
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ash 2021-10-30 02:05:37 UTC
Created attachment 143019 [details]
systemd logs at time of crash, see 12:46:44 and 12:46:56

SUMMARY
Shell and Wayland apps crashed twice in quick succession while I was working. Logs say wl_display@1: error 1: invalid arguments for org_kde_plasma_window@207.get_icon.

STEPS TO REPRODUCE
Unsure. Was using Firefox (XWayland) and Ghidra (Java, I think Wayland-native?) across two virtual desktops when the shell crashed. I pressed Meta to open the menu and it crashed again.

OBSERVED RESULT
Plasma crashes with wl_display@1: error 1: invalid arguments for org_kde_plasma_window@207.get_icon.

EXPECTED RESULT
Plasma doesn't crash.

SOFTWARE/OS VERSIONS
Operating System: Fedora 34
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.14.13-200.fc34.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × Intel® Xeon® CPU E5-2620 v3 @ 2.40GHz
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon HD 7700 Series

ADDITIONAL INFORMATION
Logs attached - they're kinda log, crashes occur at 12:46:44 and 12:46:56. I closed all my windows and it seems stable again.
Comment 1 Nate Graham 2021-11-01 15:38:53 UTC
Please attach a backtrace of the crash. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 2 Bug Janitor Service 2021-11-16 04:39:07 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 3 Bug Janitor Service 2021-12-01 04:38:40 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!