Created attachment 170035 [details] screenshot *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY This is what my launcher looks like right now. I opened it in order to shut down and found it like this. Actually I tried clicking on random points within the seemingly empty region and it runs random stuff, so I guess the buttons are there but invisible. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS I'd love to open the system setting but without the launcher I don't know how to access it. Look for any recent bug report of mine. ADDITIONAL INFORMATION
Hi, can you share more information about your system? Search for "Info Center" and copy the info from "About this System" section, there's a "Copy Details" button in upper right corner.
BTW the issue went away after restarting Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.6.32-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i7-1255U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: Vivobook_ASUSLaptop X1502ZA_F1502ZA System Version: 1.0
Feels like a GPU driver glitch to me. Have you made any graphics-related customizations to this system? For example setting KWin environment variables, changing the rendering backend/threading model, setting graphics-related kernel parameters, etc? Does anything like that sound familiar?
> Have you made any graphics-related customizations to this system? For example setting KWin environment variables, changing the rendering backend/threading model, setting graphics-related kernel parameters, etc? Does anything like that sound familiar? Nothing like that, no.
Hmm, And you say you also can't reproduce the issue anymore? That being the case, I don't think there's any way we can actually debug this, sorry. :/