SUMMARY discover crashes and cannot be started in the Chinese system language environment. STEPS TO REPRODUCE 1. Install the latest kde neon os, and select the Chinese system language. 2. Open discover using any method. 3. Can't open it, just keeps saying discover closed unexpectedly. EXPECTED RESULT discover can run normally. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.0 x86_64 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Use the terminal to run plasma-discover, and you will get the following log: gunanovo@SIncerely:/$ plasma-discover libs QList("/usr/lib/x86_64-linux-gnu/qt6/plugins", "/usr/bin") org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false adding empty sources model QStandardItemModel(0x5919bb2ca730) ASSERT: "isSorted(cats)" in file ./libdiscover/Category/Category.cpp, line 240 KCrash: Application 'plasma-discover' crashing... crashRecursionCounter = 2 KCrash: Application Name = plasma-discover path = /usr/bin pid = 12992 KCrash: Arguments: /usr/bin/plasma-discover KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi org.kde.drkonqi: Mapping found despite product information being provided by the application. Consider removing the mapping entry "plasma-discover" kf5idletime_wayland: This plugin does not support polling idle time ** OSTree:ERROR:./libglnx/glnx-local-alloc.h:74:glnx_close_fd: assertion failed: (errno != EBADF) Bail out! OSTree:ERROR:./libglnx/glnx-local-alloc.h:74:glnx_close_fd: assertion failed: (errno != EBADF) Unable to start Dr. Konqi I'm not 100% sure that this problem is related to the Chinese system language. Since I upgraded to plasma6.0, discover has never run properly. I reinstalled kde neon and the situation remained the same, but when I tried to change the system language, discover ran normally again. If you try to change the system language to English, everything returns to normal and discover will be able to run normally. I use Google Translate, please forgive me and thank you for your help.
*** This bug has been marked as a duplicate of bug 481303 ***