This bug was fixed in the package systemd - 232-21ubuntu3
---------------
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by default for those. Users can still turn it back on with
DNSSEC=allow-downgrade (or even "yes"). (LP: #1682499)
[ Michael Biebl ]
* journal: fix up syslog facility when forwarding native messages.
Native journal messages (_TRANSPORT=journal) typically don't have a
syslog facility attached to it. As a result when forwarding the
messages to syslog they ended up with facility 0 (LOG_KERN).
Apply syslog_fixup_facility() so we use LOG_USER instead. (Closes: #837893)
(LP: #1682484)
[ Dimitri John Ledkov ]
* networkd: cherry-pick support for setting bridge port's priority.
This is a useful feature/bugfix to improve feature parity of networkd with
ifupdown. This matches netplan's expectations to be able to set bridge
port's
priorities via networked. This featue is to be used by
netplan/MAAS/OpenStack.
(LP: #1668347)
* TEST-12: cherry-pick upstream fix for compat with new netcat-openbsd.
(LP: #1672542)
* udev.postinst: preserve virtio interfaces names on upgrades, on s390x.
New udev generates stable interface names on s390x kvm instances, however,
upon
upgrades existing ethX names should be preserved to prevent breaking
networking
and software configurations. (Closes: #860246) (LP: #1682437)
-- Dimitri John Ledkov <x...@ubuntu.com> Thu, 13 Apr 2017 18:10:33
+0100
** Changed in: systemd (Ubuntu Zesty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1682484
Title:
systemd: Logging from gnome session is passed on to all syslog
facilities
Status in systemd:
Unknown
Status in systemd package in Ubuntu:
Fix Committed
Status in systemd source package in Zesty:
Fix Released
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_get_preferred_width/height()....") should have a syslog
facility listed as one of the variables.
[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://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=837893
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.=info;user.=notice;\
user.=warn -/var/log/user-low.log
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1682484/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
