systemd: Logging from gnome session is passed on to all syslog facilities
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd |
Fix Released
|
Unknown
|
|||
systemd (Ubuntu) |
Fix Released
|
High
|
Dimitri John Ledkov | ||
Zesty |
Fix Released
|
High
|
Dimitri John Ledkov |
Bug Description
[Impact]
* untagged messages in journal do not have any syslog facility specified, this may result in spamming logs.
* The solution is to cherrypick upstream fix which sanity checks and provides default syslog facility, e.g. it sets user facility on user/desktop session syslog/journal entries.
[Test Case]
* launch gnome terminal
* check output of $ journalctl -o verbose -e
* entries from gnome-terminal (e.g. "Allocating size to GtkBox without calling gtk_widget_
[Regression Potential]
* We are changing (fixing regression) in logging, thus release images have those messages untagged, and may require different filtering rules before this update is applied.
[Other Info]
* Original bug report from debian.
Bug imported from Debian https:/
Package: systemd
Version: 231-6
Severity: normal
Since recently, log messages from programs running under the gnome
session have started appearing in all logs in /var/logs, including
/var/logs/kern.log, even though my rsyslog configuration has not
changed, and correctly only routes kern.* there.
This is very annoying since it fills the logs with messages that don't
belong there, and makes running logcheck tedious.
It seems this is a recent regression, since before I was able to route
these messages to a low-priority log using the following rsyslog
configuration:
user.
If I look at the messages directly with journalctl -o verbose, it seems
they do not set the syslog facility, which should make them end up with
user facility, but doesn't.
Changed in systemd (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Dimitri John Ledkov (xnox) |
description: | updated |
Changed in systemd: | |
status: | Unknown → Fix Released |
Hello Dimitri, or anyone else affected,
Accepted systemd into zesty-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ systemd/ 232-21ubuntu3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!