Bug 361621 - kdeinit5 and other plasma 5 tools fill syslog with too many messages
Summary: kdeinit5 and other plasma 5 tools fill syslog with too many messages
Status: RESOLVED NOT A BUG
Alias: None
Product: frameworks-kinit
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.18.0
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-11 09:19 UTC by Michal Petrucha
Modified: 2023-07-03 21:37 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Petrucha 2016-04-11 09:19:22 UTC
kdeinit5, kscreen_backend_launcher, kwin_x11, xembedsniproxy, and a bunch of other programs keep writing massive amounts of verbose messages into the syslog, making it pretty much impossible to find any meaningful messages in there.

On kde4, these messages were all logged on stderr, which means they ended up in the user's .xsession-errors instead of the global system log. IMO, the user's homedir is where they belong, since all those messages are only ever relevant to the user running the plasma/kde session, and moreover, most systems I have worked with do not grant access to system logs to regular users.

Reproducible: Always
Comment 1 David Faure 2016-04-17 21:24:01 UTC
The redirecting from stderr to syslog is done by systemd, I don't think it's anything we are doing.
qDebug just outputs to stderr.

But you can use kdebugsettings to turn it all off.
Comment 2 Serhiy Zahoriya 2019-07-05 11:19:08 UTC
While kdebugsettings can disable _some_ logging (maybe even most of it by size which will alleviate this particular issue) there are still messages that cannot be toggled after compilation, I've created new report for that #409521
Comment 3 auxsvr 2022-08-07 15:02:00 UTC
I can confirm that plasmashell 5.25.3 fills the systemlog with output from the programs it launches, although QT_LOGGING_RULES='*=false', all log output is disabled in kdebugdialog and almost all debug output is disabled in kdebugsettings.
Comment 4 Christoph Cullmann 2023-07-03 21:37:03 UTC
I think that is nor really avoidable, you need to report the issue to the apps that output stuff. e.g. for Kate I tried to minimize that.