Alot of KDE components produce a vast ammount of debug output that is written to .xsession-errors. This does not only cause unnecessary IO but also decreases performance, battery life, ssd life and in extreme cases causes multi-gigabye logfiles for some users. Googling for '.xsession-errors' reveals that a lot of users notice this file in a negative way while there are little actual issues solved by providing information from this file. Usually dedicated logfiles or the output from a run on the console is used to find issues. Even using kdebug to disable debug messages, some components still produce a a lot of output. There are previously reported bug, some that have no been addressed for several years. I hope it is not bad as a non-kde-dev to create this metabug that depends on the currently open bugs regarding this issue. Most of these components should only log really ciritcal stuff - any other errors/issues should be enabled on-demand by running the application with --debug or something like this. Reproducible: Always Expected Results: .xession-errors should only provide first-hint informations if randomly X-applications crash or encounter other critical issues. For regular debugging programs are usually invoked on a separate console and debugged in other ways.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
All blockers are closed; marking this as fixed.