I'm okay with Yakuake reporting things. But whatever the problem it could be, it can't fall in a loop sending messages to journals without any kind of temporization. For example it should pause 1 second every time before sending anything to journal. Whatever the problem it could complain about. Ideally it would report only one time per execution about one precise problem. So 10 problems = no more than 10 message in the whole process life For now I should lack something and it seems to want badly that thing (without actually needing it but anyway), so it literally spam numbers that I can't even count, it's more than the buffer can support. But sometime its 100 per second, sometimes more than 500 per second (can't count more). And it's constant across whole life of the process whatever you do or not with it. Message is `dpi is invalid got from xsettings(Qt/DPI/ and Xft/DPI), fallback to get dpi from QXcbScreen::logicalDpi()` I repeat. I don't search to correct the actual problem but to limit yakuake message throughput whatever the problem it experiences SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION