SUMMARY *** Sorry for choosing "I don't know" category. The problem I encountered is that two component of plasma-workspace crashed when I was using VMWare Workstation. They are xembedsniproxy and gmenudbusmenuproxy. I did not notice that until I ran command `coredumpctl list` in the terminal. Here are the outputs from terminal ``` Sun 2023-09-10 19:19:34 CST 14357 1000 1000 SIGABRT present /usr/bin/xembedsniproxy 460.7K Sun 2023-09-10 19:19:34 CST 14342 1000 1000 SIGABRT present /usr/bin/gmenudbusmenuproxy 469.7K ``` Here is the coredump stack trace of xembedsniproxy: https://pastebin.com/bTZbEnRx Here is the coredump stack trace of gmenudbusmenuproxy: https://pastebin.com/K2Kg7GyF *** STEPS TO REPRODUCE 1. Just open vmware workstation and running virtual machines. OBSERVED RESULT None EXPECTED RESULT No crash happens. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION
#6 0x00007fd655f3f3f2 in init_platform (argv=<optimized out>, argc=@0x7ffe2133721c: 1, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at kernel/qguiapplication.cpp:1254 Does plasma desktop run normally? Is there any log from journalctl?
(In reply to Fushan Wen from comment #1) > #6 0x00007fd655f3f3f2 in init_platform (argv=<optimized out>, > argc=@0x7ffe2133721c: 1, platformThemeName=..., platformPluginPath=..., > pluginNamesWithArguments=...) at kernel/qguiapplication.cpp:1254 > > Does plasma desktop run normally? Is there any log from journalctl? Yes, the plasma desktop run normally. Yes, here is some related log I found from journalctl https://pastebin.com/EcFjGeUW
Lots of things are failing to find a platform plugin recently. :/ I've been moving them all to plasma-integration in the hope that someone smarter than me can find the root cause and mark them as duplicates appropriately.