date:20180321

Let me reach out to xnox to see if he's planning another systemd SRU
after the current one migrates into -updates. If yes, maybe we can have
him bundle up this change. If not, we can just release this one fix
then.

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: udev (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
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/1738153

Title:
  need backport the new scancode of dell-wmi for Microphone mute hotkey
  to xenial

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New
Status in udev source package in Xenial:
  New

Bug description:
  [Impact]
  dell-wmi expend the scan code of Microphone mute hotkey from 0x150 to 
0x100150, so need to add a new mapping for it.

  related commit:
  https://github.com/systemd/systemd/pull/5012

  [Test Case]
  1. install the udev package which applied patch.
  2. check if Microphone mute hotkey works.
  3. if it not works, please provide the log of evtest.

  [Regression Potential]
  low regression potential, because it just add one more mapping.

  also affect:
  LP: #1736352
  LP: #1740080
  LP: #1734609

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1738153/+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

[Touch-packages] [Bug 1721294] Re: Unattended upgrade fails with "Error in function"

2018-03-21 Thread Marius Gedminas

Yurii: can you clarify how that broke unattended upgrades?

I also don't see how a cron script might get different PATH values from one day 
to the other.
I just had another instance of this bug on a third Ubuntu 14.04 LTS server 
(this one a physical machine, not a VPS) where unattended-upgrades worked fine 
before.  And on that machine

# cat /proc/$(pidof cron)/environ | tr '\0' '\n' | grep PATH
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin

looks fine to me.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1721294

Title:
  Unattended upgrade fails with "Error in function"

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  This is the cron email I received today:

  From: root 
  To: r...@pov.lt
  Subject: unattended-upgrades result for 'iv-4.pov.lt': 'False'
  Date: Wed,  4 Oct 2017 03:40:19 +0300 (EEST)

  Unattended upgrade returned: False

  Packages that attempted to upgrade:
   ca-certificates libidn11 libnss3 libnss3-nssdb

  Package installation log:
  Error in function:

  
  Unattended-upgrades log:
  Initial blacklisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=trusty-security', 
'o=UbuntuESM,a=trusty', 'o=Ubuntu,a=trusty-security', 
'o=Ubuntu,a=trusty-updates', 'origin=LP-PPA-pov,suite=trusty']
  Packages that will be upgraded: ca-certificates libidn11 libnss3 
libnss3-nssdb
  Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2017-10-04_03:40:17.411277.log'
  Installing the upgrades failed!
  error message: 'installArchives() failed'
  dpkg returned a error! See 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2017-10-04_03:40:17.411277.log'
 for details
  Packages that are auto removed: ''
  Packages auto-removed

  The named log file, var/log/unattended-upgrades/unattended-upgrades-
  dpkg_2017-10-04_03:40:17.411277.log contains only this:

  Error in function:

  That's it.

  Now given that ca-certificates is involved, I suspect this may be
  related to non-ASCII filenames (see bug 1554365), but unlike that bug,
  here the upgrade fails instead of succeeding, and the actual error is
  not shown anywhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2.5
  Uname: Linux 2.6.32-042stab124.2 x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Wed Oct  4 18:54:54 2017
  PackageArchitecture: all
  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721294/+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

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

2018-03-21 Thread Julian Andres Klode

Um, Steve, something is wrong in your analysis: base-files is fully
configured before bash is unpacked, and when _unpacking_ bash it tries
to process the trigger (i mean, there's no "Setting up bash" in front of
it; but maybe dpkg processes triggers before printing that).

The odd thing here is that apt should be calling dpkg with --no-
triggers, unless we're doing TriggersPending, ConfigurePending, or the
last step in the run - and that's not happening AFAICT.

@Kees long stretch, but maybe you have a dpkg.log from that?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1750465

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  New
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Committed
Status in ubuntu-gnome-default-settings package in Ubuntu:
  New
Status in ubuntu-mate-artwork package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in budgie-artwork source package in Artful:
  New
Status in kubuntu-settings source package in Artful:
  New
Status in plymouth source package in Artful:
  In Progress
Status in ubuntu-gnome-default-settings source package in Artful:
  New
Status in ubuntu-mate-artwork source package in Artful:
  New

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from artful-proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  
  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (0 days ago)
  dmi.bios.date: 01/12/2017
  dmi.bios.vend

[Touch-packages] [Bug 1572244] Re: Kubuntu requires that the WiFi password be entered twice before WiFi can be used

** Changed in: casper (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

** Changed in: casper (Ubuntu Bionic)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1572244

Title:
  Kubuntu requires that the WiFi password be entered twice before WiFi
  can be used

Status in casper package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Released
Status in plasma-nm package in Ubuntu:
  Invalid
Status in casper source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Fix Released
Status in plasma-nm source package in Bionic:
  Invalid

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1572244/+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

[Touch-packages] [Bug 1572244] Re: Kubuntu requires that the WiFi password be entered twice before WiFi can be used

2018-03-21 Thread Rik Mills

** Changed in: plasma-nm (Ubuntu Bionic)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1572244

Title:
  Kubuntu requires that the WiFi password be entered twice before WiFi
  can be used

Status in casper package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Released
Status in plasma-nm package in Ubuntu:
  Invalid
Status in casper source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Fix Released
Status in plasma-nm source package in Bionic:
  Invalid

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1572244/+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

[Touch-packages] [Bug 1572244] Re: Kubuntu requires that the WiFi password be entered twice before WiFi can be used

** Changed in: casper (Ubuntu Bionic)
 Assignee: LocutusOfBorg (costamagnagianfranco) => Rik Mills (rikmills)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1572244

Title:
  Kubuntu requires that the WiFi password be entered twice before WiFi
  can be used

Status in casper package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Released
Status in plasma-nm package in Ubuntu:
  Invalid
Status in casper source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Fix Released
Status in plasma-nm source package in Bionic:
  Invalid

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1572244/+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

[Touch-packages] [Bug 1757375] [NEW] Desktop unable to Suspend when Inactive

2018-03-21 Thread TJ

Public bug reported:

On 16.04 (XFCE session and others) and possibly later the power-manager
is unable to suspend the system when the user is inactive. A PK user-
agent dialog is presented for the user to authenticate first - and as
this action occurs specifically when the user is idle and away the PC
can end up having an unplanned loss of power when the battery is
exhausted.

/var/log/auth.log shows:

polkitd(authority=local): Operator of unix-session:c2 FAILED to
authenticate to gain authorization for action
org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-f7631ecd0b46]
(owned by unix-user:tj)

The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry to
allow Suspend. Currently it only has an entry for hibernate.

Adding the following stanza solves the issue:

[Enable suspend by default in logind]
Identity=unix-user:*
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
ResultActive=yes
ResultInactive=yes

** Affects: policykit-desktop-privileges (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-desktop-
privileges in Ubuntu.
https://bugs.launchpad.net/bugs/1757375

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  New

Bug description:
  On 16.04 (XFCE session and others) and possibly later the power-
  manager is unable to suspend the system when the user is inactive. A
  PK user-agent dialog is presented for the user to authenticate first -
  and as this action occurs specifically when the user is idle and away
  the PC can end up having an unplanned loss of power when the battery
  is exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+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

[Touch-packages] [Bug 1757266] Re: /etc/polkit-1/localauthority.conf.d/ parsed in wrong order?

2018-03-21 Thread TJ

Related Suspend bug (and fix) "Desktop unable to Suspend when Inactive
Edit" bug #1757375

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1757266

Title:
  /etc/polkit-1/localauthority.conf.d/ parsed in wrong order?

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  On 16.04 and using the Xubuntu session (this isn't limited to XFCE) I
  noticed that my notebook fails to suspend via power-management when
  the idle timeout expires. When returning to it, if it still has power,
  I see a polkit-agent GUI dialog asking me to authenticate.

  In /var/log/auth.log is:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  So I started digging:

  # inactive sleep is enabled
  $ xfconf-query -c xfce4-power-manager -lv | grep inactivity
  /xfce4-power-manager/inactivity-on-ac   14
  /xfce4-power-manager/inactivity-on-battery  15
  /xfce4-power-manager/inactivity-sleep-mode-on-battery   1

  $ awk '/login1\.suspend"/ {E=1;print} /defaults/ && E == 1 {E++} E > 1 
{print} /<\/action>/ && E > 1 {exit}' 
/usr/share/polkit-1/actions/org.freedesktop.login1.policy
  
  
  auth_admin_keep
  auth_admin_keep
  yes
  
  

  # member of sudo and adm
  $ groups
  tj adm dialout cdrom sudo dip plugdev lpadmin sambashare sbuild lxd libvirtd 
two_factor_auth

  $ sudo find /etc/polkit-1/ -type f -exec sh -c 'echo === {} ===; cat {}' \; | 
egrep -v '^(#|$)'
  === /etc/polkit-1/localauthority/50-local.d/com.ubuntu.desktop.pkla ===
  [Enable hibernate by default in upower]
  Identity=unix-user:*
  Action=org.freedesktop.upower.hibernate
  ResultActive=yes
  ResultInactive=yes
  [Enable hibernate by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.hibernate;org.freedesktop.login1.handle-hibernate-key;org.freedesktop.login1;org.freedesktop.login1.hibernate-multiple-sessions;org.freedesktop.login1.hibernate-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes
  === /etc/polkit-1/nullbackend.conf.d/50-nullbackend.conf ===
  [Configuration]
  Priority=-10
  === /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf ===
  [Configuration]
  AdminIdentities=unix-group:sudo;unix-group:admin
  === /etc/polkit-1/localauthority.conf.d/50-localauthority.conf ===
  [Configuration]
  AdminIdentities=unix-user:0

  ubuntu-admin.conf policy sets AdminIdentities to include group 'sudo'
  but seems to be ignored

  "man 8 pklocalauthority" states that these files are parsed in C
  locale lexical order, and gives examples of "...given the name 60
  -desktop-policy.conf to ensure that it is evaluted after the
  50-localauthority.conf file shipped with PolicyKit."

  However:

  $ sudo inotifywait -r -m /etc/polkit-1/localauthority.conf.d
  Setting up watches.  Beware: since -r was given, this may take a while!
  Watches established.
  /etc/polkit-1/localauthority.conf.d/ OPEN,ISDIR
  /etc/polkit-1/localauthority.conf.d/ ACCESS,ISDIR
  /etc/polkit-1/localauthority.conf.d/ ACCESS,ISDIR
  /etc/polkit-1/localauthority.conf.d/ CLOSE_NOWRITE,CLOSE,ISDIR
  /etc/polkit-1/localauthority.conf.d/ OPEN 51-ubuntu-admin.conf
  /etc/polkit-1/localauthority.conf.d/ ACCESS 51-ubuntu-admin.conf
  /etc/polkit-1/localauthority.conf.d/ CLOSE_NOWRITE,CLOSE 51-ubuntu-admin.conf
  /etc/polkit-1/localauthority.conf.d/ OPEN 50-localauthority.conf
  /etc/polkit-1/localauthority.conf.d/ ACCESS 50-localauthority.conf
  /etc/polkit-1/localauthority.conf.d/ CLOSE_NOWRITE,CLOSE 
50-localauthority.conf

  This seems to show that the sort order might be high-low not low-high
  (unless they're sorted once in memory).

  In view of the fact that ubuntu-admin.conf appears to be ignored I
  suspect 50-localauthority.conf is replacing the ubuntu conf with the
  default:

  AdminIdentities=unix-group:sudo;unix-group:admin
  AdminIdentities=unix-user:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1757266/+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

[Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

2018-03-21 Thread Alex

Daniel,

There is a small inconvenience with 'synclient' command - I have to run
it not just at startup, but also every time I restart gnome-shell (after
installing an extension, for example). But anyway, it looks like
libinput 1.10.2 resolved the problem with hysteresis on my touchpad, so
I can just use it and set options like "TappingButtonMap" "lmr" and
"HorizontalScrolling" "off" with libinput driver in
/etc/X11/xorg.conf.d/.

And thank you for your work on improving Ubuntu! :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1686081

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed
Status in xorg source package in Artful:
  Invalid
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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

[Touch-packages] [Bug 1738153] Re: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial

2018-03-21 Thread Dimitri John Ledkov

Please do not assign bugs to udev source package, it has been long time
merged into systemd source package.

Yeah, I can cherry-pick this for SRUs.

** No longer affects: udev (Ubuntu)

** No longer affects: udev (Ubuntu Xenial)

** Also affects: systemd (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => Fix Released

** Changed in: systemd (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: systemd (Ubuntu Artful)
   Status: New => Confirmed

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu Artful)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

-- 
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/1738153

Title:
  need backport the new scancode of dell-wmi for Microphone mute hotkey
  to xenial

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  [Impact]
  dell-wmi expend the scan code of Microphone mute hotkey from 0x150 to 
0x100150, so need to add a new mapping for it.

  related commit:
  https://github.com/systemd/systemd/pull/5012

  [Test Case]
  1. install the udev package which applied patch.
  2. check if Microphone mute hotkey works.
  3. if it not works, please provide the log of evtest.

  [Regression Potential]
  low regression potential, because it just add one more mapping.

  also affect:
  LP: #1736352
  LP: #1740080
  LP: #1734609

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1738153/+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

Re: [Touch-packages] [Bug 1757256] Re: Apparmor profile gajim

2018-03-21 Thread george jetson

Still not working. Please help.

the audit logs when launching gajim are:



type=SYSCALL msg=audit(1521623303.636:86): arch=c03e syscall=2
success=no exit=-13 a0=659281e35d38 a1=90800 a2=6592816e73f0
a3=659281e49000 items=1 ppid=1053 pid=1119 auid=1000 uid=0 gid=0 euid=0
suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=2 comm="gajim"
exe="/usr/bin/python3.6" key=(null)
type=CWD msg=audit(1521623303.636:86): cwd="/home/user"
type=PATH msg=audit(1521623303.636:86): item=0 name="/usr/lib/python3.6"
inode=19437 dev=00:17 mode=040755 ouid=0 ogid=0 rdev=00:00
nametype=NORMAL cap_fp= cap_fi= cap_fe=0
cap_fver=0
type=PROCTITLE msg=audit(1521623303.636:86):
proctitle=2F7573722F62696E2F707974686F6E002F7573722F62696E2F67616A696D
type=AVC msg=audit(1521623303.637:87): apparmor="ALLOWED"
operation="open" info="Failed name lookup - disconnected path" error=-13
profile="/usr/bin/gajim" name="usr/lib/python3.6/lib-dynload" pid=1119
comm="gajim" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
type=SYSCALL msg=audit(1521623303.637:87): arch=c03e syscall=2
success=no exit=-13 a0=659281e424d0 a1=90800 a2=6592816e73f0
a3=659281e09000 items=1 ppid=1053 pid=1119 auid=1000 uid=0 gid=0 euid=0
suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=2 comm="gajim"
exe="/usr/bin/python3.6" key=(null)
type=CWD msg=audit(1521623303.637:87): cwd="/home/user"
type=PATH msg=audit(1521623303.637:87): item=0
name="/usr/lib/python3.6/lib-dynload" inode=17086 dev=00:17 mode=040755
ouid=0 ogid=0 rdev=00:00 nametype=NORMAL cap_fp=
cap_fi= cap_fe=0 cap_fver=0
type=PROCTITLE msg=audit(1521623303.637:87):
proctitle=2F7573722F62696E2F707974686F6E002F7573722F62696E2F67616A696D
type=ANOM_ABEND msg=audit(1521623303.637:88): auid=1000 uid=0 gid=0
ses=2 pid=1119 comm="gajim" exe="/usr/bin/python3.6" sig=6 res=1



The profile I used:

# Last Modified: Wed Mar 21 00:06:33 2018
#include 

/usr/bin/gajim flags=(complain) {
  #include 
  #include 
  #include 
  /** rwk,
  /home/user/** r,
  /home/user/.local/share/gajim/** rwk,
  /home/user/.cache/gajim/** rwk,
  /usr/lib/python3.6/** rk,
  /home/user/.local/lib/** rk,
  /proc/*/net/arp rk,
  owner "/home/*/.mozilla/firefox/Crash Reports/**" rk,
  owner /home/*/ rk,
  owner /home/*/.ICEauthority rk,
  owner /home/*/.Xauthority rk,
  owner /home/*/.cache/fontconfig/** rwk,
  owner /home/*/.cache/gajim/** rwk,
  owner /home/*/.config/** rwk,
  owner /home/*/.local/lib/python2.7/site-packages/ rk,
  owner /home/*/.local/lib/python3.6/site-packages/ rk,
  owner /home/*/.local/share/applications/ rk,
  owner /home/*/.local/share/gajim/* rwk,
  owner /home/*/.local/share/* rwk,
  owner /home/*/.mozilla/firefox/* rk,
  owner /proc/*/fd/ rk,
  owner /proc/*/mounts rk,

On 03/21/2018 02:40 AM, Seth Arnold wrote:
> Hello,
>
>  open("/home/user", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 EACCES 
> (Permission denied)
> ...
>  open("/usr/lib/python3.6", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 
> EACCES (Permission denied)
> etc
>
> Probably these all generated DENIED lines in your logs.
>
> And probably running aa-logprof would prompt you about them. Allow them
> as appropriate and probably you'll be good to go.
>
> Thanks
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1757256

Title:
  Apparmor profile gajim

Status in apparmor package in Ubuntu:
  New

Bug description:
  Followed this guide: https://gitlab.com/apparmor/apparmor/wi … with_tools and 
saved usr.bin.gajim after scanning.
  After I restart machine and run Gajim from terminal I get:

  Fatal Python error: Py_Initialize: Unable to get the locale encoding
  ModuleNotFoundError: No module named 'encodings'

  Current thread 0x6a383a1d5540 (most recent call first):
  Aborted (core dumped)

  If I delete the profile and restart machine it runs (to confirm it is
  profile causing).

  This is my current profile

  
  # vim:syntax=apparmor
  # --
  #
  #Copyright (C) 2015-2018 Mikhail Morfikov
  #
  #This program is free software; you can redistribute it and/or
  #modify it under the terms of version 2 of the GNU General Public
  #License published by the Free Software Foundation.
  #
  # --

  #include 

  /usr/bin/gajim {
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

/usr/bin/gajim mr,

/usr/bin/ r,
/usr/local/bin/ r,

# Gajim plugins
/usr/share/gajim/plugins/ r,
/usr/share/gajim/plugins/** r,

# Gajim home files
owner @{HOME}/.config/gajim/ rw,
owner @{HOME}/.config/gajim/** rw,
owner @{HOME}/.local/share/gajim/ rw,

[Touch-packages] [Bug 1757388] [NEW] bridge device is missing

Public bug reported:

Ubuntu 18.04: Since last dist-upgrade of the bridge-utils (2018-03-21)
the bridge netwok device 'br0' is missing. A 'ls /sys/class/net' prints
the devices 'enp3s0  lo  lxcbr0  virbr0  virbr0-nic' only.

** Affects: bridge-utils (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1757388

Title:
  bridge device is missing

Status in bridge-utils package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04: Since last dist-upgrade of the bridge-utils (2018-03-21)
  the bridge netwok device 'br0' is missing. A 'ls /sys/class/net'
  prints the devices 'enp3s0  lo  lxcbr0  virbr0  virbr0-nic' only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1757388/+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

[Touch-packages] [Bug 1757388] Re: bridge device is missing

And the syslog bloats:
...
Mar 21 11:06:26 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/rx_bytes": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:26 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/tx_bytes": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:26 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/rx_errors": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:26 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/tx_errors": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:26 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/collisions": Datei oder Verzeichnis nicht 
gefunden
Mar 21 11:06:27 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/rx_packets": Datei oder Verzeichnis nicht 
gefunden
Mar 21 11:06:27 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/tx_packets": Datei oder Verzeichnis nicht 
gefunden
Mar 21 11:06:27 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/rx_bytes": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:27 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/tx_bytes": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:27 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/rx_errors": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:27 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/tx_errors": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:27 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/collisions": Datei oder Verzeichnis nicht 
gefunden
...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1757388

Title:
  bridge device is missing

Status in bridge-utils package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04: Since last dist-upgrade of the bridge-utils (2018-03-21)
  the bridge netwok device 'br0' is missing. A 'ls /sys/class/net'
  prints the devices 'enp3s0  lo  lxcbr0  virbr0  virbr0-nic' only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1757388/+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

[Touch-packages] [Bug 1572244] Re: Kubuntu requires that the WiFi password be entered twice before WiFi can be used

This bug was fixed in the package casper - 1.390

---
casper (1.390) bionic; urgency=medium

  * scripts/casper-bottom/34disable_kde_services:
- stop disabling kwallet in Kubuntu live session by removing it's
  desktop and service files, and instead write a 'kwalletrc' config
  file disabling it. Allows plasma-nm to recognise it is disabled,
  and not try to use it initially. Fixes repeated wi-fi password
  prompt. (LP: #1572244)

 -- Rik Mills   Mon, 12 Mar 2018 11:45:09 +

** Changed in: casper (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1572244

Title:
  Kubuntu requires that the WiFi password be entered twice before WiFi
  can be used

Status in casper package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in plasma-nm package in Ubuntu:
  Invalid
Status in casper source package in Bionic:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Released
Status in plasma-nm source package in Bionic:
  Invalid

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1572244/+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

[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) due to outdated gcc-4.8

2018-03-21 Thread Alexander Stohr

just found this on the GCC thread:

Launchpad Janitor (janitor) wrote on 2018-03-19:#7
This bug was fixed in the package gcc-4.8 - 4.8.5-4ubuntu8

---
gcc-4.8 (4.8.5-4ubuntu8) bionic; urgency=medium

  [ Matthias Klose ]
  * Stop build gcj in current distro releases. Addresses: #892536.
  * Split off the documentation part from the retpoline patches.
  * Fix build dependency on realpath.

  [ Steve Beattie ]
  * Add retpoline support for x86 via adding -mindirect-branch=,
-mindirect-branch-register, and -mfunction-return= support
(LP: #1749261)
- 0001-i386-Move-struct-ix86_frame-to-machine_function.diff,
  0002-i386-Use-reference-of-struct-ix86_frame-to-avoid-cop.diff,
  0003-i386-Use-const-reference-of-struct-ix86_frame-to-avo.diff,
  0004-x86-Add-mindirect-branch.diff,
  0005-x86-Add-mfunction-return.diff,
  0006-x86-Add-mindirect-branch-register.diff,
  0007-x86-Add-V-register-operand-modifier.diff,
  0008-x86-Disallow-mindirect-branch-mfunction-return-with-.diff,
  0009-Use-INVALID_REGNUM-in-indirect-thunk-processing.diff:
  implement -mindirect-branch=
  with attribute support, -mindirect-branch-register, and
  -mfunction-return= with
  attribute support. Thanks to H.J. Lu.

 -- Matthias Klose  Mon, 19 Mar 2018 16:12:10 +0800

Changed in gcc-4.8 (Ubuntu):
status: Confirmed → Fix Released
Martin W. (webi123) wrote 2 hours ago:  #8
I've seen that the fix is currently only released for bionic.
What is the release date for trusty (gcc-4.8.5 Ubuntu 4.8.5-2ubuntu1~14.04.1) ?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1750937

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) due to outdated gcc-4.8

Status in gcc-4.8 package in Ubuntu:
  Fix Released

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N

[Touch-packages] [Bug 1757388] Re: bridge device is missing

And there's no way to downgrade from 1.5-15ubuntu1 to 1.5-9ubuntu2.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1757388

Title:
  bridge device is missing

Status in bridge-utils package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04: Since last dist-upgrade of the bridge-utils (2018-03-21)
  the bridge netwok device 'br0' is missing. A 'ls /sys/class/net'
  prints the devices 'enp3s0  lo  lxcbr0  virbr0  virbr0-nic' only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1757388/+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

[Touch-packages] [Bug 1757388] Re: bridge device is missing

And the syslog bloats:
...
Mar 21 11:06:26 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/rx_bytes": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:26 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/tx_bytes": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:26 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/rx_errors": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:26 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/tx_errors": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:26 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/collisions": Datei oder Verzeichnis nicht 
gefunden
Mar 21 11:06:27 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/rx_packets": Datei oder Verzeichnis nicht 
gefunden
Mar 21 11:06:27 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/tx_packets": Datei oder Verzeichnis nicht 
gefunden
Mar 21 11:06:27 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/rx_bytes": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:27 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/tx_bytes": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:27 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/rx_errors": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:27 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/tx_errors": Datei oder Verzeichnis nicht gefunden
Mar 21 11:06:27 pyrimea org.mate.panel.applet.NetspeedAppletFactory[2240]: 
glibtop(c=2702): [WARNING] Failed to open 
"/sys/class/net/br0/statistics/collisions": Datei oder Verzeichnis nicht 
gefunden
...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1757388

Title:
  bridge device is missing

Status in bridge-utils package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04: Since last dist-upgrade of the bridge-utils (2018-03-21)
  the bridge netwok device 'br0' is missing. A 'ls /sys/class/net'
  prints the devices 'enp3s0  lo  lxcbr0  virbr0  virbr0-nic' only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1757388/+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

[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

I've now checked all the ffmpeg & libav packages against those on the PC
on which sound works. They all match and I've done all the reinstalls
again but still sound doesn't play for vlc on mp3 files. I can't think
of anything to do next. I don't want to reinstall Ubuntu as that's a big
job in terms of reconfiguration etc. I'm now using banshee to play music
& videos. But it's a slight nuisance in that when I quit banshee, it
carries on playing until I stop it in System Monitor. RhythmBox has the
same problem.

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1755144

Title:
No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
New
Status in pulseaudio package in Ubuntu:
Invalid

Bug description:
Up until a few weeks ago there was no problem with playing sound from mp3
files. I have a pair of usb speakers. Audio plays Ok on them for video clips
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos),
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok
using Rhythmbox. I've also tried vlc 3.0 with no success.
Interestingly, the standard Videos app (Totem?) also doesn't play sound on
these speakers either of an mp4 file (downloaded from YouTube, though it plays
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I
first reported this as bug 1752267 as I thought that the problem was with vlc.
On that bug, it was suggested that the problem is with Pulseaudio.
Just now, I've tried to play sound through my monitor's built in speakers
connected by hdmi (though the monitor displays Ok) with no success even though
the built-in speakers play sound using pavucontrol when testing is invoked.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.8
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: john 2410 F pulseaudio
/dev/snd/controlC0: john 2410 F pulseaudio
CurrentDesktop: Unity
Date: Mon Mar 12 11:06:46 2018
InstallationDate: Installed on 2016-12-08 (458 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/04/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
dmi.board.name: NUC5CPYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H61145-404
dmi.chassis.type: 3
dmi.modalias:
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1755144/+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

[Touch-packages] [Bug 1757388] Re: bridge device is missing

And there's no way to downgrade from 1.5-15ubuntu1 to 1.5-9ubuntu2.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1757388

Title:
  bridge device is missing

Status in bridge-utils package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04: Since last dist-upgrade of the bridge-utils (2018-03-21)
  the bridge netwok device 'br0' is missing. A 'ls /sys/class/net'
  prints the devices 'enp3s0  lo  lxcbr0  virbr0  virbr0-nic' only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1757388/+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

[Touch-packages] [Bug 1757388] Re: bridge device is missing

A manual 'brctl addbr br0' brings up the bridge interface. Doing this at
boot time would be better.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1757388

Title:
  bridge device is missing

Status in bridge-utils package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04: Since last dist-upgrade of the bridge-utils (2018-03-21)
  the bridge netwok device 'br0' is missing. A 'ls /sys/class/net'
  prints the devices 'enp3s0  lo  lxcbr0  virbr0  virbr0-nic' only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1757388/+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

[Touch-packages] [Bug 1757204] Re: libindicator is not multi-arch aware

2018-03-21 Thread Olivier Tilloy

libindicator3-dev depends on libgtk-3-dev, and it appears it is not
installable in parallel for two architectures:

$ sudo apt install libgtk-3-dev:amd64 libgtk-3-dev:i386
Reading package lists... Done
Building dependency tree   
Reading state information... Done
libgtk-3-dev is already the newest version (3.22.28-1ubuntu3).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgtk-3-dev:i386 : Depends: libgdk-pixbuf2.0-dev:i386 (>= 2.30.0) but it is 
not going to be installed
 Depends: libpango1.0-dev:i386 (>= 1.40.5) but it is not 
going to be installed
 Depends: libegl1-mesa-dev:i386 but it is not going to be 
installed
 Depends: libxkbcommon-dev:i386 but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libindicator in Ubuntu.
https://bugs.launchpad.net/bugs/1757204

Title:
  libindicator is not multi-arch aware

Status in libindicator package in Ubuntu:
  New

Bug description:
  This is preventing libappindicator from becoming multi-arch aware (bug
  #1081938).

  $ dpkg --print-architecture
  amd64

  $dpkg --print-foreign-architectures
  i386

  $ sudo apt install libindicator3-7 libindicator3-7:i386
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libindicator3-7 : Conflicts: libindicator3-7:i386 but 
16.10.0+18.04.20171205.1-0ubuntu1 is to be installed
   libindicator3-7:i386 : Conflicts: libindicator3-7 but 
16.10.0+18.04.20171205.1-0ubuntu1 is to be installed
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libindicator3-7 16.10.0+18.04.20171205.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 20 17:34:22 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (625 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libindicator
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (50 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1757204/+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

[Touch-packages] [Bug 1754265] Re: packagekitd crashed with SIGSEGV in utilBuildPackageId()

2018-03-21 Thread Julian Andres Klode

Fix in https://github.com/hughsie/PackageKit/pull/246

** Changed in: packagekit (Ubuntu)
   Status: Triaged => In Progress

** Changed in: packagekit (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1754265

Title:
  packagekitd crashed with SIGSEGV in utilBuildPackageId()

Status in packagekit package in Ubuntu:
  In Progress

Bug description:
  PackageKit seems to be crashing randomly on bionic, not sure why, did
  not investigate further yet.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: packagekit 1.1.7-1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Thu Mar  8 08:35:34 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2017-12-08 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  SegvAnalysis:
   Segfault happened at: 0x7fca622a9ecc 
<_Z18utilBuildPackageIdRKN8pkgCache11VerIteratorE+124>: cmpb   $0x6,0x22(%rax)
   PC (0x7fca622a9ecc) ok
   source "$0x6" ok
   destination "0x22(%rax)" (0x0015f6da) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: packagekit
  StacktraceTop:
   utilBuildPackageId(pkgCache::VerIterator const&) () at 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   AptIntf::emitPackage(pkgCache::VerIterator const&, PkInfoEnum) () at 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   AcqPackageKitStatus::updateStatus(pkgAcquire::ItemDesc&, int) () at 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   pkgAcquire::Worker::RunMessages() () at 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   pkgAcquire::Worker::InFdReady() () at 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
  Title: packagekitd crashed with SIGSEGV in utilBuildPackageId()
  UpgradeStatus: Upgraded to bionic on 2017-12-08 (89 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1754265/+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

[Touch-packages] [Bug 1757204] Re: libindicator is not multi-arch aware

2018-03-21 Thread Olivier Tilloy

The issue with libgtk-3-dev is bug #1317116.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libindicator in Ubuntu.
https://bugs.launchpad.net/bugs/1757204

Title:
  libindicator is not multi-arch aware

Status in libindicator package in Ubuntu:
  New

Bug description:
  This is preventing libappindicator from becoming multi-arch aware (bug
  #1081938).

  $ dpkg --print-architecture
  amd64

  $dpkg --print-foreign-architectures
  i386

  $ sudo apt install libindicator3-7 libindicator3-7:i386
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libindicator3-7 : Conflicts: libindicator3-7:i386 but 
16.10.0+18.04.20171205.1-0ubuntu1 is to be installed
   libindicator3-7:i386 : Conflicts: libindicator3-7 but 
16.10.0+18.04.20171205.1-0ubuntu1 is to be installed
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libindicator3-7 16.10.0+18.04.20171205.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 20 17:34:22 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (625 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libindicator
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (50 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1757204/+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

[Touch-packages] [Bug 1317116] Re: libgtk2.0-dev is not multiarch-ready

2018-03-21 Thread Olivier Tilloy

Same problem with gtk3:

$ sudo apt install libgtk-3-dev:amd64 libgtk-3-dev:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
libgtk-3-dev is already the newest version (3.22.28-1ubuntu3).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgtk-3-dev:i386 : Depends: libgdk-pixbuf2.0-dev:i386 (>= 2.30.0) but it is 
not going to be installed
 Depends: libpango1.0-dev:i386 (>= 1.40.5) but it is not 
going to be installed
 Depends: libegl1-mesa-dev:i386 but it is not going to be 
installed
 Depends: libxkbcommon-dev:i386 but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1317116

Title:
  libgtk2.0-dev is not multiarch-ready

Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  New
Status in gtk+2.0 package in Debian:
  New

Bug description:
  This means that if I want to compile a Gtk+ program for x86 on an
  amd64 machine, I need to install libgtk2.0-0:i386 and then manually
  symlink: libgtk-x11-2.0.so libgdk-x11-2.0.so libatk-1.0.so
  libgio-2.0.so libpangoft2-1.0.so libpangocairo-1.0.so libcairo.so
  libpango-1.0.so libgobject-2.0.so libglib-2.0.so in /usr/lib/i386
  -linux-gnu

  $ sudo apt-get install libgtk2.0-dev:i386
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgtk2.0-dev:i386 : Depends: gir1.2-gtk-2.0:i386 (= 2.24.23-0ubuntu1) but 
it is not going to be installed
Depends: libgdk-pixbuf2.0-dev:i386 (>= 2.21.0) but it 
is not going to be installed
Depends: libpango1.0-dev:i386 (>= 1.20) but it is not 
going to be installed
Depends: libatk1.0-dev:i386 (>= 1.29.2) but it is not 
going to be installed
Recommends: python:i386 (>= 2.4) but it is not going to 
be installed
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgtk2.0-dev 2.24.23-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  7 16:17:56 2014
  InstallationDate: Installed on 2011-05-11 (1091 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1317116/+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

[Touch-packages] [Bug 1734410] Re: systemd: handle undelegated cgroup2 hierarchy

Next time, please provide some information about what and how was tested
when setting verification-done for an update. It is not enough to just
set the tag. The SRU team needs to be made aware of what has been tested
and how, if the test case was followed as expected. The more verbose the
better.

-- 
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/1734410

Title:
  systemd: handle undelegated cgroup2 hierarchy

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * When a container is presented with a unified cgroup hierarchy,
  which is not properly delegated, systemd should not attempt (and fail)
  to use. This improves compatibility of xenial containers running on
  unified cgroup hierarchy hosts.

  [Test Case]

   * Xenial containers should boot, with non-writable unified cgroup
  hierarchy hosts.

  [Regression Potential]

   * unified cgroup hierarchy is not in use by default on xenial hosts,
  thus this is forward compatibility improvment with e.g. bionic hosts
  running xenial containers.

  [Other Info]
   
   * Original bug report

  Hey everyone,

  Current systemd versions all fail when the unified cgroup hierarchy is
  not-writable. This is especially problematic in containers where the
  systemd administrator might decide to not delegate the unified
  hierarchy or when running with a liblxc driver that doesn't yet know
  how to handle the unified cgroup hierarchy. I've pushed patches to
  systemd upstream that let systemd ingnore the non-delegated unified
  hierarchy. The relevant commits are:

  e07aefbd675b651f8d45b5fb458f2747b04d6e04
  2d56b80a1855836abf1d7458394c345ad9d55382
  1ff654e28b7b8e7d0a0be33522a84069ac6b07c0

  These patches will be in 236 but should be backported from xenial
  upwards.

  Christian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734410/+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

[Touch-packages] [Bug 1754265] Re: packagekitd crashed with SIGSEGV in utilBuildPackageId()

2018-03-21 Thread Julian Andres Klode

Uploaded so we don't forget about it. Probably want to do a 1.1.9-2 in
Debian though and sync it again :)

** Changed in: packagekit (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1754265

Title:
  packagekitd crashed with SIGSEGV in utilBuildPackageId()

Status in packagekit package in Ubuntu:
  Fix Committed

Bug description:
  PackageKit seems to be crashing randomly on bionic, not sure why, did
  not investigate further yet.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: packagekit 1.1.7-1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Thu Mar  8 08:35:34 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2017-12-08 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  SegvAnalysis:
   Segfault happened at: 0x7fca622a9ecc 
<_Z18utilBuildPackageIdRKN8pkgCache11VerIteratorE+124>: cmpb   $0x6,0x22(%rax)
   PC (0x7fca622a9ecc) ok
   source "$0x6" ok
   destination "0x22(%rax)" (0x0015f6da) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: packagekit
  StacktraceTop:
   utilBuildPackageId(pkgCache::VerIterator const&) () at 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   AptIntf::emitPackage(pkgCache::VerIterator const&, PkInfoEnum) () at 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   AcqPackageKitStatus::updateStatus(pkgAcquire::ItemDesc&, int) () at 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   pkgAcquire::Worker::RunMessages() () at 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   pkgAcquire::Worker::InFdReady() () at 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
  Title: packagekitd crashed with SIGSEGV in utilBuildPackageId()
  UpgradeStatus: Upgraded to bionic on 2017-12-08 (89 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1754265/+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

[Touch-packages] [Bug 1750608] Re: Fixup ADT tests

This bug was fixed in the package systemd - 234-2ubuntu12.3

---
systemd (234-2ubuntu12.3) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Fix test-functions failing with Ubuntu units. LP: #1750608
  * tests: switch to using ext4 by default, instead of ext3. LP: #1750608
  * Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
  * systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
Rebase and de-fuzz. (LP: #1734410)
  * Prevent MemoryDenyWriteExecution policy bypass, by disallowing 
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
  * networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)

  [ Kleber Sacilotto de Souza ]
  * systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We 
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)

 -- Dimitri John Ledkov   Tue, 20 Feb 2018 16:11:58
+

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15908

-- 
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/1750608

Title:
  Fixup ADT tests

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   In artful, there are autopkgtest failures that can be improved/fixed
  with the following commits:

   * stop using ext3, and instead use ext4 as fsck.ext3 may be missing
  in the initramfs.

   * correctly parse prefixes, when parsing units and deciding which
  binaries to copy into the test image.

  
  These are changes to the setup codes of the test-suite, and no change in test 
assertions being made. Hopefully this will make adt results more green.

  [Test Case]

   * Check that autopkgtests are not failing with missing fsck.ext3
   * Check that autopkgtesta are not failing with failing to copy referenced 
binaries

  [Regression Potential]

   * No changes to the code shipped / binaries shipped

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750608/+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

[Touch-packages] [Bug 1750608] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1750608

Title:
  Fixup ADT tests

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   In artful, there are autopkgtest failures that can be improved/fixed
  with the following commits:

   * stop using ext3, and instead use ext4 as fsck.ext3 may be missing
  in the initramfs.

   * correctly parse prefixes, when parsing units and deciding which
  binaries to copy into the test image.

  
  These are changes to the setup codes of the test-suite, and no change in test 
assertions being made. Hopefully this will make adt results more green.

  [Test Case]

   * Check that autopkgtests are not failing with missing fsck.ext3
   * Check that autopkgtesta are not failing with failing to copy referenced 
binaries

  [Regression Potential]

   * No changes to the code shipped / binaries shipped

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750608/+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

[Touch-packages] [Bug 1737570] Re: Add support for RequiredForOnline in networkd

This bug was fixed in the package systemd - 234-2ubuntu12.3

---
systemd (234-2ubuntu12.3) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Fix test-functions failing with Ubuntu units. LP: #1750608
  * tests: switch to using ext4 by default, instead of ext3. LP: #1750608
  * Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
  * systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
Rebase and de-fuzz. (LP: #1734410)
  * Prevent MemoryDenyWriteExecution policy bypass, by disallowing 
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
  * networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)

  [ Kleber Sacilotto de Souza ]
  * systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We 
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)

 -- Dimitri John Ledkov   Tue, 20 Feb 2018 16:11:58
+

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15908

-- 
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/1737570

Title:
  Add support for RequiredForOnline in networkd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * netplan & networkd based systems typically await networking to be
  up on boot, without any ability to specify that an interface should be
  configured, but might not be online at boot. This is a backport of the
  RequiredForOnline= feature to match optional=true in netplan.

  [Test Case]

   * Configure a netowkring interface using .link/.network file and specify 
RequiredForOnline=False
   * Bring the interface down / offline it
   * execute systemd-networkd-wait-online, which should exit immediately since 
no interfaces are required to be online

  [Regression Potential]

   * This adds a support for an additional stanza in the network files.
  This stanza is not used by default. if the stanza is used, but older
  networkd is in use, networkd will ignore this unknown stanza. Thus
  this change is backward and forward compatible. The difference is that
  boot is not blocked awaiting systemd-networkd-wait-online to timeout.

  [Other Info]
   
   * Original bug report

  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737570/+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

[Touch-packages] [Bug 1734410] Re: systemd: handle undelegated cgroup2 hierarchy

This bug was fixed in the package systemd - 234-2ubuntu12.3

---
systemd (234-2ubuntu12.3) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Fix test-functions failing with Ubuntu units. LP: #1750608
  * tests: switch to using ext4 by default, instead of ext3. LP: #1750608
  * Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
  * systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
Rebase and de-fuzz. (LP: #1734410)
  * Prevent MemoryDenyWriteExecution policy bypass, by disallowing 
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
  * networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)

  [ Kleber Sacilotto de Souza ]
  * systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We 
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)

 -- Dimitri John Ledkov   Tue, 20 Feb 2018 16:11:58
+

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15908

-- 
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/1734410

Title:
  systemd: handle undelegated cgroup2 hierarchy

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * When a container is presented with a unified cgroup hierarchy,
  which is not properly delegated, systemd should not attempt (and fail)
  to use. This improves compatibility of xenial containers running on
  unified cgroup hierarchy hosts.

  [Test Case]

   * Xenial containers should boot, with non-writable unified cgroup
  hierarchy hosts.

  [Regression Potential]

   * unified cgroup hierarchy is not in use by default on xenial hosts,
  thus this is forward compatibility improvment with e.g. bionic hosts
  running xenial containers.

  [Other Info]
   
   * Original bug report

  Hey everyone,

  Current systemd versions all fail when the unified cgroup hierarchy is
  not-writable. This is especially problematic in containers where the
  systemd administrator might decide to not delegate the unified
  hierarchy or when running with a liblxc driver that doesn't yet know
  how to handle the unified cgroup hierarchy. I've pushed patches to
  systemd upstream that let systemd ingnore the non-delegated unified
  hierarchy. The relevant commits are:

  e07aefbd675b651f8d45b5fb458f2747b04d6e04
  2d56b80a1855836abf1d7458394c345ad9d55382
  1ff654e28b7b8e7d0a0be33522a84069ac6b07c0

  These patches will be in 236 but should be backported from xenial
  upwards.

  Christian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734410/+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

[Touch-packages] [Bug 1736955] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1736955

Title:
  dep8 test systemd-fsckd fails on s390

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released

Bug description:
  The systemd-fsckd test has a constraint of isolation-machine, among
  others. Until recently, that actually prevented it from running on
  s390 because we were using containers for it.

  About 3 weeks ago, apparently we started using VMs for s390 dep8
  tests, so that constraint was finally satisfied and systemd-fsckd
  started to run. And to fail consistently, as can be see in
  http://autopkgtest.ubuntu.com/packages/s/systemd/artful/s390x:

  Traceback (most recent call last):
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 267, in 
  boot_with_systemd_distro()
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 243, in boot_with_systemd_distro
  enable_plymouth()
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 224, in enable_plymouth
  plymouth_enabled = 'splash' in open('/boot/grub/grub.cfg').read()
  FileNotFoundError: [Errno 2] No such file or directory: '/boot/grub/grub.cfg'

  There is no grub for s390, so this test must be adjusted or skipped in
  that architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1736955/+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

[Touch-packages] [Bug 1736955] Re: dep8 test systemd-fsckd fails on s390

This bug was fixed in the package systemd - 234-2ubuntu12.3

---
systemd (234-2ubuntu12.3) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Fix test-functions failing with Ubuntu units. LP: #1750608
  * tests: switch to using ext4 by default, instead of ext3. LP: #1750608
  * Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
  * systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
Rebase and de-fuzz. (LP: #1734410)
  * Prevent MemoryDenyWriteExecution policy bypass, by disallowing 
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
  * networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)

  [ Kleber Sacilotto de Souza ]
  * systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We 
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)

 -- Dimitri John Ledkov   Tue, 20 Feb 2018 16:11:58
+

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15908

-- 
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/1736955

Title:
  dep8 test systemd-fsckd fails on s390

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released

Bug description:
  The systemd-fsckd test has a constraint of isolation-machine, among
  others. Until recently, that actually prevented it from running on
  s390 because we were using containers for it.

  About 3 weeks ago, apparently we started using VMs for s390 dep8
  tests, so that constraint was finally satisfied and systemd-fsckd
  started to run. And to fail consistently, as can be see in
  http://autopkgtest.ubuntu.com/packages/s/systemd/artful/s390x:

  Traceback (most recent call last):
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 267, in 
  boot_with_systemd_distro()
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 243, in boot_with_systemd_distro
  enable_plymouth()
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 224, in enable_plymouth
  plymouth_enabled = 'splash' in open('/boot/grub/grub.cfg').read()
  FileNotFoundError: [Errno 2] No such file or directory: '/boot/grub/grub.cfg'

  There is no grub for s390, so this test must be adjusted or skipped in
  that architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1736955/+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

[Touch-packages] [Bug 1734908] Re: systemd-rfkill service times out when a new rfkill device is added

This bug was fixed in the package systemd - 234-2ubuntu12.3

---
systemd (234-2ubuntu12.3) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Fix test-functions failing with Ubuntu units. LP: #1750608
  * tests: switch to using ext4 by default, instead of ext3. LP: #1750608
  * Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
  * systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
Rebase and de-fuzz. (LP: #1734410)
  * Prevent MemoryDenyWriteExecution policy bypass, by disallowing 
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
  * networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)

  [ Kleber Sacilotto de Souza ]
  * systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We 
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)

 -- Dimitri John Ledkov   Tue, 20 Feb 2018 16:11:58
+

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15908

-- 
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/1734908

Title:
  systemd-rfkill service times out when a new rfkill device is added

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

  The following issue was observed while running network-
  manager=1.8.4-1ubuntu3 autopkgtest on Artful with
  systemd=234-2ubuntu12.1:

  ---
  Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start 
operation timed out. Terminating.
  Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill 
Switch Status.
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered 
failed state.
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with 
result 'timeout'.
  ---

  This happens after the testcase inserts the fake-rfkill module (a
  module shipped with network-manager tests that registers a new fake
  device with the rfkill subsystem).

  On Artful, it causes the network-manager autopkgtest killswitches-no-
  urfkill to fail (see bug 1733321). The testcase reveals that when
  running network-manager cli to query the status of a WiFi interface
  ('nmcli radio wifi') it can report the wrong state of the device after
  'rfkill block/unblock' is run to change the device 'Soft blocked'
  state. This can affect the state of the device presented to the user.

  [Fix]

  The issue is fixed by the following systemd upstream patches:

  ---
  
https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac

  commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f
  Author: S. Fan 
  Date:   Mon Jul 31 05:10:10 2017 -0500

  rfkill: fix erroneous behavior when polling the udev monitor
  (#6489)

  Comparing udev_device_get_sysname(device) and sysname will always return
  true. We need to check the device received from udev monitor instead.

  Also, fd_wait_for_event() sometimes never exits. Better set a timeout
  here.
  ---

  ---
  
https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac

  commit c7f6ca9379279affa8f22d15fa13063491f86a49
  Author: Xiang Fan 
  Date:   Wed Aug 9 05:51:53 2017 -0500

  rfkill: fix typo (#6574)
  ---

  With the fixes, the output from systemd-rfkill is:

  ---
  Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev 
monitor.
  Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch 
Status.

[Touch-packages] [Bug 1734410] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1734410

Title:
  systemd: handle undelegated cgroup2 hierarchy

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * When a container is presented with a unified cgroup hierarchy,
  which is not properly delegated, systemd should not attempt (and fail)
  to use. This improves compatibility of xenial containers running on
  unified cgroup hierarchy hosts.

  [Test Case]

   * Xenial containers should boot, with non-writable unified cgroup
  hierarchy hosts.

  [Regression Potential]

   * unified cgroup hierarchy is not in use by default on xenial hosts,
  thus this is forward compatibility improvment with e.g. bionic hosts
  running xenial containers.

  [Other Info]
   
   * Original bug report

  Hey everyone,

  Current systemd versions all fail when the unified cgroup hierarchy is
  not-writable. This is especially problematic in containers where the
  systemd administrator might decide to not delegate the unified
  hierarchy or when running with a liblxc driver that doesn't yet know
  how to handle the unified cgroup hierarchy. I've pushed patches to
  systemd upstream that let systemd ingnore the non-delegated unified
  hierarchy. The relevant commits are:

  e07aefbd675b651f8d45b5fb458f2747b04d6e04
  2d56b80a1855836abf1d7458394c345ad9d55382
  1ff654e28b7b8e7d0a0be33522a84069ac6b07c0

  These patches will be in 236 but should be backported from xenial
  upwards.

  Christian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734410/+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

[Touch-packages] [Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

This bug was fixed in the package systemd - 234-2ubuntu12.3

---
systemd (234-2ubuntu12.3) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Fix test-functions failing with Ubuntu units. LP: #1750608
  * tests: switch to using ext4 by default, instead of ext3. LP: #1750608
  * Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
  * systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
Rebase and de-fuzz. (LP: #1734410)
  * Prevent MemoryDenyWriteExecution policy bypass, by disallowing 
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
  * networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)

  [ Kleber Sacilotto de Souza ]
  * systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We 
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)

 -- Dimitri John Ledkov   Tue, 20 Feb 2018 16:11:58
+

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15908

-- 
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/1734167

Title:
  DNS doesn't work in no-cloud as launched by ubuntu

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * resolved does not start early enough in the boot-process preventing
  DNS resolution to be operational during early boot, for example as
  required by special early stages of cloud-init, resulting in failure
  to boot / provision the instance fully.

  [Test Case]

   * Boot container or a VM with a nocloud-net data source, and a URL pointing 
to the datasource as explained below
   * Observe that boot completes and provisioning is successful
   * Check that there are no dns-resolution errors in the cloud-init log / boot 
log

  [Regression Potential]

   * starting resolved earlier may prevent it from connecting to dbus,
  and may require a restart later on when re-triggered over dbus. This
  is on artful only, as in bionic resolved has gained ability to
  reconnected to dbus post-start. Backporting that, however, is too
  large for an SRU as it requires sd-bus changes.

  [Other Info]
   
   * Original bug report.

  I use no-cloud to test the kernel in CI (I am maintainer of the bcache
  subsystem), and have been running it successfully under 16.04 cloud
  images from qemu, using a qemu command that includes:

  -smbios "type=1,serial=ds=nocloud-
  net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-
  metadata/linuxtst/"

  As documented here:

  http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html

  Under the new 17.10 cloud images, this doesn't work: the network comes
  up, but name resolution doesn't work-- /etc/resolv.conf is a symlink
  to a nonexistent file at this point of the boot and systemd-resolved
  is not running.  When I manually hack /etc/resolv.conf in the cloud
  image to point to 4.2.2.1 it works fine.

  I don't know if nameservice not working is by design, but it seems
  like it should work.  The documentation states:

  "With ds=nocloud-net, the seedfrom value must start with http://,
  https:// or ftp://";

  And https is not going to work for a raw IP address.

  Related bugs:
   * bug 1734939: #include fails silently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1734167/+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

[Touch-packages] [Bug 1734908] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1734908

Title:
  systemd-rfkill service times out when a new rfkill device is added

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

  The following issue was observed while running network-
  manager=1.8.4-1ubuntu3 autopkgtest on Artful with
  systemd=234-2ubuntu12.1:

  ---
  Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start 
operation timed out. Terminating.
  Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill 
Switch Status.
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered 
failed state.
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with 
result 'timeout'.
  ---

  This happens after the testcase inserts the fake-rfkill module (a
  module shipped with network-manager tests that registers a new fake
  device with the rfkill subsystem).

  On Artful, it causes the network-manager autopkgtest killswitches-no-
  urfkill to fail (see bug 1733321). The testcase reveals that when
  running network-manager cli to query the status of a WiFi interface
  ('nmcli radio wifi') it can report the wrong state of the device after
  'rfkill block/unblock' is run to change the device 'Soft blocked'
  state. This can affect the state of the device presented to the user.

  [Fix]

  The issue is fixed by the following systemd upstream patches:

  ---
  
https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac

  commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f
  Author: S. Fan 
  Date:   Mon Jul 31 05:10:10 2017 -0500

  rfkill: fix erroneous behavior when polling the udev monitor
  (#6489)

  Comparing udev_device_get_sysname(device) and sysname will always return
  true. We need to check the device received from udev monitor instead.

  Also, fd_wait_for_event() sometimes never exits. Better set a timeout
  here.
  ---

  ---
  
https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac

  commit c7f6ca9379279affa8f22d15fa13063491f86a49
  Author: Xiang Fan 
  Date:   Wed Aug 9 05:51:53 2017 -0500

  rfkill: fix typo (#6574)
  ---

  With the fixes, the output from systemd-rfkill is:

  ---
  Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev 
monitor.
  Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch 
Status.
  ---

  The patches are needed to fix the ADT tests observed with Artful tests on 
ppc64el architecture:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  [Regression Potential]

  Most of the network-manager and rfkill functionalities that can be
  affected by this change are tested by killswitches-no-urfkill
  testcase. It covers querying the WiFi device state using nmcli and the
  following rfkill commands: list, block and unblock. These have been
  verified to be either fixed or not having regressions.

  The only rfkill command that is not covered by the testcase is
  'event', which listens to rfkill events and display them. I have run
  tests manually and verified that it's not affected by these changes.
  These are the outputs from the unpatched and patched systemd versions
  while running the killswitches-no-urfkill testcase, which adds the

[Touch-packages] [Bug 1737570] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1737570

Title:
  Add support for RequiredForOnline in networkd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * netplan & networkd based systems typically await networking to be
  up on boot, without any ability to specify that an interface should be
  configured, but might not be online at boot. This is a backport of the
  RequiredForOnline= feature to match optional=true in netplan.

  [Test Case]

   * Configure a netowkring interface using .link/.network file and specify 
RequiredForOnline=False
   * Bring the interface down / offline it
   * execute systemd-networkd-wait-online, which should exit immediately since 
no interfaces are required to be online

  [Regression Potential]

   * This adds a support for an additional stanza in the network files.
  This stanza is not used by default. if the stanza is used, but older
  networkd is in use, networkd will ignore this unknown stanza. Thus
  this change is backward and forward compatible. The difference is that
  boot is not blocked awaiting systemd-networkd-wait-online to timeout.

  [Other Info]
   
   * Original bug report

  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737570/+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

[Touch-packages] [Bug 1734167] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1734167

Title:
  DNS doesn't work in no-cloud as launched by ubuntu

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * resolved does not start early enough in the boot-process preventing
  DNS resolution to be operational during early boot, for example as
  required by special early stages of cloud-init, resulting in failure
  to boot / provision the instance fully.

  [Test Case]

   * Boot container or a VM with a nocloud-net data source, and a URL pointing 
to the datasource as explained below
   * Observe that boot completes and provisioning is successful
   * Check that there are no dns-resolution errors in the cloud-init log / boot 
log

  [Regression Potential]

   * starting resolved earlier may prevent it from connecting to dbus,
  and may require a restart later on when re-triggered over dbus. This
  is on artful only, as in bionic resolved has gained ability to
  reconnected to dbus post-start. Backporting that, however, is too
  large for an SRU as it requires sd-bus changes.

  [Other Info]
   
   * Original bug report.

  I use no-cloud to test the kernel in CI (I am maintainer of the bcache
  subsystem), and have been running it successfully under 16.04 cloud
  images from qemu, using a qemu command that includes:

  -smbios "type=1,serial=ds=nocloud-
  net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-
  metadata/linuxtst/"

  As documented here:

  http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html

  Under the new 17.10 cloud images, this doesn't work: the network comes
  up, but name resolution doesn't work-- /etc/resolv.conf is a symlink
  to a nonexistent file at this point of the boot and systemd-resolved
  is not running.  When I manually hack /etc/resolv.conf in the cloud
  image to point to 4.2.2.1 it works fine.

  I don't know if nameservice not working is by design, but it seems
  like it should work.  The documentation states:

  "With ds=nocloud-net, the seedfrom value must start with http://,
  https:// or ftp://";

  And https is not going to work for a raw IP address.

  Related bugs:
   * bug 1734939: #include fails silently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1734167/+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

[Touch-packages] [Bug 1725348] Re: Systemd - Bypassing MemoryDenyWriteExecution policy

This bug was fixed in the package systemd - 234-2ubuntu12.3

---
systemd (234-2ubuntu12.3) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Fix test-functions failing with Ubuntu units. LP: #1750608
  * tests: switch to using ext4 by default, instead of ext3. LP: #1750608
  * Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
  * systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
Rebase and de-fuzz. (LP: #1734410)
  * Prevent MemoryDenyWriteExecution policy bypass, by disallowing 
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
  * networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)

  [ Kleber Sacilotto de Souza ]
  * systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We 
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)

 -- Dimitri John Ledkov   Tue, 20 Feb 2018 16:11:58
+

** Changed in: systemd (Ubuntu Artful)
   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/1725348

Title:
  Systemd - Bypassing MemoryDenyWriteExecution policy

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * MemoryDenyWritePolicy can be bypassed by using a slightly different
  syscall.

  [Test Case]

   * Check that MemoryDenyWritePolicy, blocks pkey_mprotect as well as
  mprotect.

  [Regression Potential]

   * Upstream fix cherrypick, security vulnerability.

  [Other Info]
   
   * Original report

  Hello,

  We would like to report to you a vulnerability about systemd which
  allows to bypass the MemoryDenyWriteExecution policy on Linux 4.9+.

  The vulnerability is described in the attached PDF file.

  Sincerely,
  Thomas IMBERT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725348/+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

[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

This bug was fixed in the package systemd - 234-2ubuntu12.3

---
systemd (234-2ubuntu12.3) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Fix test-functions failing with Ubuntu units. LP: #1750608
  * tests: switch to using ext4 by default, instead of ext3. LP: #1750608
  * Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
  * systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
Rebase and de-fuzz. (LP: #1734410)
  * Prevent MemoryDenyWriteExecution policy bypass, by disallowing 
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
  * networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)

  [ Kleber Sacilotto de Souza ]
  * systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We 
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)

 -- Dimitri John Ledkov   Tue, 20 Feb 2018 16:11:58
+

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15908

-- 
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/1721223

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that

[Touch-packages] [Bug 1725348] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1725348

Title:
  Systemd - Bypassing MemoryDenyWriteExecution policy

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * MemoryDenyWritePolicy can be bypassed by using a slightly different
  syscall.

  [Test Case]

   * Check that MemoryDenyWritePolicy, blocks pkey_mprotect as well as
  mprotect.

  [Regression Potential]

   * Upstream fix cherrypick, security vulnerability.

  [Other Info]
   
   * Original report

  Hello,

  We would like to report to you a vulnerability about systemd which
  allows to bypass the MemoryDenyWriteExecution policy on Linux 4.9+.

  The vulnerability is described in the attached PDF file.

  Sincerely,
  Thomas IMBERT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725348/+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

[Touch-packages] [Bug 1721223] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1721223

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
  fix were SRU'd, will all of these things in the wild cope with this
  sysctl change?

  [Other Info]

   * Original bug report

  Hi there,
  we found a replicable issue that involves the Ubuntu Core networking and 
causes complete loss of connectivity.
  We run a custom board with ubuntu core: the architecure is amrhf.
  We replicated this issue with an official Ubuntu Core image on a Raspberry 
Pi: other platform was been tested.
  It shows that it is a snap core problem which interests networkd: we use the 
default network stack based on networkd + netplan.

  Below steps to replicate the issue.

  1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes).
  2)Boot the board and wait for get an ip from dhcp server
  3)Before the lease expires, set a reservation for a different ip address

  Depending on lease duration before the lease expires( for 10 minute we have 2 
minutes before ), networkd configure the new address in addition to the 
previous one.
  When the lease expire both ip address ( the prevoius and the new one ) 
disappear from the interested network interface.
  Depending on lease duration before the second lease expires ( for 10 minure 
we have 2 minutes before ) networkd configure o

[Touch-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

This bug was fixed in the package systemd - 234-2ubuntu12.3

---
systemd (234-2ubuntu12.3) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Fix test-functions failing with Ubuntu units. LP: #1750608
  * tests: switch to using ext4 by default, instead of ext3. LP: #1750608
  * Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
  * systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
Rebase and de-fuzz. (LP: #1734410)
  * Prevent MemoryDenyWriteExecution policy bypass, by disallowing 
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
  * networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)

  [ Kleber Sacilotto de Souza ]
  * systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We 
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)

 -- Dimitri John Ledkov   Tue, 20 Feb 2018 16:11:58
+

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15908

-- 
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/1708409

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Artful:
  Invalid
Status in systemd source package in Artful:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+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

[Touch-packages] [Bug 1708409] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1708409

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Artful:
  Invalid
Status in systemd source package in Artful:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+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

[Touch-packages] [Bug 1618188] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1618188

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * System logs are lost across reboots because they are not stored
  persistently.

  [Test Case]

   * Fresh installations, or upgrades to this version of systemd, should create 
/var/log/journal and trigger automatic persistent logs.
   * Users may choose to remove said directory, or disable persistent logging 
in /etc/systemd/journald.conf

  [Regression Potential]

   * Persistent logging by default will cause logs to be flushed from
  /run to /var/log, meaning there will be less RAM used (/run is tmpfs
  backed), but increased disk usage (in /var/log). The journald daemon
  has limits set for logs, meaning they will be rotated and discarded
  and should not cause out of disk-space errors.

  [Other Info]
   
   * Original bug report

  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't.
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/+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

[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

This bug was fixed in the package systemd - 234-2ubuntu12.3

---
systemd (234-2ubuntu12.3) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Fix test-functions failing with Ubuntu units. LP: #1750608
  * tests: switch to using ext4 by default, instead of ext3. LP: #1750608
  * Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
  * systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
Rebase and de-fuzz. (LP: #1734410)
  * Prevent MemoryDenyWriteExecution policy bypass, by disallowing 
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
  * networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)

  [ Kleber Sacilotto de Souza ]
  * systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We 
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)

 -- Dimitri John Ledkov   Tue, 20 Feb 2018 16:11:58
+

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15908

-- 
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/1618188

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * System logs are lost across reboots because they are not stored
  persistently.

  [Test Case]

   * Fresh installations, or upgrades to this version of systemd, should create 
/var/log/journal and trigger automatic persistent logs.
   * Users may choose to remove said directory, or disable persistent logging 
in /etc/systemd/journald.conf

  [Regression Potential]

   * Persistent logging by default will cause logs to be flushed from
  /run to /var/log, meaning there will be less RAM used (/run is tmpfs
  backed), but increased disk usage (in /var/log). The journald daemon
  has limits set for logs, meaning they will be rotated and discarded
  and should not cause out of disk-space errors.

  [Other Info]
   
   * Original bug report

  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't.
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/+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

[Touch-packages] [Bug 1732803] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1732803

Title:
  systemd-journald RateLimitBurst is sometimes divided by 4

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  systemd-journald allows you to configure a per-service journal rate limit in 
/etc/systemd/journald.conf via the RateLimitBurst parameter. systemd-journald 
has
  code that effectively increases the rate limit when there is a lot of disk 
space available.
  However, all versions of systemd before v232 had a bug which would shrink the 
rate limit
  when there is between 1 and 16 MB available on disk.

  If you designed a service to log at a rate R and configured
  RateLimitBurst to a little above R, this can lead to loss of logs when
  free disk is between 1 and 16 MB, as your service will be surprisingly
  rate limited at lower than your configured rate.

  This bug was fixed upstream in https://github.com/systemd/systemd/pull/4218
  It is a straightforward one-line change that makes the code match the 
comments under it.

  [Test Case]

  Run a systemd service that prints lots of logs (eg `yes`). Fill your
  disk to have only 1MB full. Use journalctl to see how many log lines
  are between "Suppressed" lines. Note that it is 1/4 of what you'd
  expect.  (Admittedly this test case is a little hard to achieve since
  journald itself is writing to disk. I did run into this in
  production.)

  [Regression Potential]

  This does mean that journald can write slightly more to disk than it
  did before when free disk is between 1 and 16MB, but given that the
  full burst rate is available below 1MB it seems unlikely that any
  systems are depending on this change in order to not break.

  The fix has been in systemd since v232 (shipped in Zesty). I would
  like to see it in Xenial.

  
  [Other Info]
   
  I am seeing this on:
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 1 ~/systemd-229$ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 0 ~/systemd-229$ apt-cache policy 
systemd
  systemd:
Installed: 229-4ubuntu19
Candidate: 229-4ubuntu21
Version table:
   229-4ubuntu21 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu 
xenial-updates/main amd64 Packages
   *** 229-4ubuntu19 100
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial/main amd64 
Packages

  This bug seems to date back to the original implementation of rate
  limiting (https://github.com/systemd/systemd/commit/6e409ce10d).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732803/+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

[Touch-packages] [Bug 1722481] Re: systemd should sync disks, before killing all processes on shutdown

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

** Changed in: systemd (Ubuntu Xenial)
   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/1722481

Title:
  systemd should sync disks, before killing all processes on shutdown

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * systemd-shutdown binary is executed to complete system shutdown. In
  xenial, it calls sync() after killing all processes, and not before
  killing them. This means that processes are racing the SIGKILL/TERM
  timeouts to sync all IO to disk. To mitigate this race condition, and
  make the shutdown process more reliable the sync() should also happen
  before process killing spree starts.

  [Fix]
  Backport upstream commit 
https://github.com/systemd/systemd/commit/2e79d1828a8da9b3af1b052297e3617905ec94f3

  
  [Test Case]

   * Make sure systems still shuts down, including e.g. root on raid.

  [Regression Potential]

   * Shutdowns may appear to be slower due to two sync() calls instead of one
   * However total shutdown time should not be impacted much, as there really 
should not be much additional IO caused by killing all processes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1722481/+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

[Touch-packages] [Bug 1732803] Re: systemd-journald RateLimitBurst is sometimes divided by 4

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

** Changed in: systemd (Ubuntu Xenial)
   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/1732803

Title:
  systemd-journald RateLimitBurst is sometimes divided by 4

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  systemd-journald allows you to configure a per-service journal rate limit in 
/etc/systemd/journald.conf via the RateLimitBurst parameter. systemd-journald 
has
  code that effectively increases the rate limit when there is a lot of disk 
space available.
  However, all versions of systemd before v232 had a bug which would shrink the 
rate limit
  when there is between 1 and 16 MB available on disk.

  If you designed a service to log at a rate R and configured
  RateLimitBurst to a little above R, this can lead to loss of logs when
  free disk is between 1 and 16 MB, as your service will be surprisingly
  rate limited at lower than your configured rate.

  This bug was fixed upstream in https://github.com/systemd/systemd/pull/4218
  It is a straightforward one-line change that makes the code match the 
comments under it.

  [Test Case]

  Run a systemd service that prints lots of logs (eg `yes`). Fill your
  disk to have only 1MB full. Use journalctl to see how many log lines
  are between "Suppressed" lines. Note that it is 1/4 of what you'd
  expect.  (Admittedly this test case is a little hard to achieve since
  journald itself is writing to disk. I did run into this in
  production.)

  [Regression Potential]

  This does mean that journald can write slightly more to disk than it
  did before when free disk is between 1 and 16MB, but given that the
  full burst rate is available below 1MB it seems unlikely that any
  systems are depending on this change in order to not break.

  The fix has been in systemd since v232 (shipped in Zesty). I would
  like to see it in Xenial.

  
  [Other Info]
   
  I am seeing this on:
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 1 ~/systemd-229$ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 0 ~/systemd-229$ apt-cache policy 
systemd
  systemd:
Installed: 229-4ubuntu19
Candidate: 229-4ubuntu21
Version table:
   229-4ubuntu21 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu 
xenial-updates/main amd64 Packages
   *** 229-4ubuntu19 100
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial/main amd64 
Packages

  This bug seems to date back to the original implementation of rate
  limiting (https://github.com/systemd/systemd/commit/6e409ce10d).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732803/+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

[Touch-packages] [Bug 1722481] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1722481

Title:
  systemd should sync disks, before killing all processes on shutdown

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * systemd-shutdown binary is executed to complete system shutdown. In
  xenial, it calls sync() after killing all processes, and not before
  killing them. This means that processes are racing the SIGKILL/TERM
  timeouts to sync all IO to disk. To mitigate this race condition, and
  make the shutdown process more reliable the sync() should also happen
  before process killing spree starts.

  [Fix]
  Backport upstream commit 
https://github.com/systemd/systemd/commit/2e79d1828a8da9b3af1b052297e3617905ec94f3

  
  [Test Case]

   * Make sure systems still shuts down, including e.g. root on raid.

  [Regression Potential]

   * Shutdowns may appear to be slower due to two sync() calls instead of one
   * However total shutdown time should not be impacted much, as there really 
should not be much additional IO caused by killing all processes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1722481/+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

[Touch-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

** Changed in: systemd (Ubuntu Xenial)
   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/696435

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Kernel does not generate any events when ndb-client connects /dev/nbd0 
devices, therefore it is impossible to monitor/react to the state of /dev/nbd0.

  [Fix]
  Generate change uevent when size of /dev/nbd0 changes

  [Testcase]
  * Start udevadm monitor
  * modprobe nbd
  * use ndb-client to connect something to /dev/nbd0
  * observe that there are change udev events generated on /dev/nbd0 itself

  [Regression Potential]
  There is no change to existing uevents, or their ordering.
  There is now an addition change event which will cause systemd to mark ndb 
devices as ready and trigger appropriate actions

  [Original Bug Report]

  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
   while [ -z "${FSTYPE}" ]; do
    FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

    # Run failure hooks, hoping one of them can fix up the system
    # and we can restart the wait loop.  If they all fail, abort
    # and move on to the panic handler and shell.
    if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
     break
    fi
   done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/696435/+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

[Touch-packages] [Bug 696435] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/696435

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Kernel does not generate any events when ndb-client connects /dev/nbd0 
devices, therefore it is impossible to monitor/react to the state of /dev/nbd0.

  [Fix]
  Generate change uevent when size of /dev/nbd0 changes

  [Testcase]
  * Start udevadm monitor
  * modprobe nbd
  * use ndb-client to connect something to /dev/nbd0
  * observe that there are change udev events generated on /dev/nbd0 itself

  [Regression Potential]
  There is no change to existing uevents, or their ordering.
  There is now an addition change event which will cause systemd to mark ndb 
devices as ready and trigger appropriate actions

  [Original Bug Report]

  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
   while [ -z "${FSTYPE}" ]; do
    FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

    # Run failure hooks, hoping one of them can fix up the system
    # and we can restart the wait loop.  If they all fail, abort
    # and move on to the panic handler and shell.
    if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
     break
    fi
   done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/696435/+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

[Touch-packages] [Bug 1734410] Re: systemd: handle undelegated cgroup2 hierarchy

2018-03-21 Thread Christian Brauner

Sorry for the brevity before. I tested this with systemd 23{5,6}
inside xenial and artful containers which is really the only case
where it matters.

A systemd with my patch applied would happily:
1. skip over undelegated /sys/fs/cgroup/unified mountpoints
   (e07aefbd675b651f8d45b5fb458f2747b04d6e04).
2. skip over undelegated pur cgroup2 mountpoints at /sys/fs/cgroup
   (2d56b80a1855836abf1d7458394c345ad9d55382)
3. remove any empty mountpoints created for case 1. and 2.
   (1ff654e28b7b8e7d0a0be33522a84069ac6b07c0)

Thanks for backporting these patches!
Christian

-- 
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/1734410

Title:
  systemd: handle undelegated cgroup2 hierarchy

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * When a container is presented with a unified cgroup hierarchy,
  which is not properly delegated, systemd should not attempt (and fail)
  to use. This improves compatibility of xenial containers running on
  unified cgroup hierarchy hosts.

  [Test Case]

   * Xenial containers should boot, with non-writable unified cgroup
  hierarchy hosts.

  [Regression Potential]

   * unified cgroup hierarchy is not in use by default on xenial hosts,
  thus this is forward compatibility improvment with e.g. bionic hosts
  running xenial containers.

  [Other Info]
   
   * Original bug report

  Hey everyone,

  Current systemd versions all fail when the unified cgroup hierarchy is
  not-writable. This is especially problematic in containers where the
  systemd administrator might decide to not delegate the unified
  hierarchy or when running with a liblxc driver that doesn't yet know
  how to handle the unified cgroup hierarchy. I've pushed patches to
  systemd upstream that let systemd ingnore the non-delegated unified
  hierarchy. The relevant commits are:

  e07aefbd675b651f8d45b5fb458f2747b04d6e04
  2d56b80a1855836abf1d7458394c345ad9d55382
  1ff654e28b7b8e7d0a0be33522a84069ac6b07c0

  These patches will be in 236 but should be backported from xenial
  upwards.

  Christian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734410/+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

[Touch-packages] [Bug 1756364] Re: [ffe] Livepatch integration

I'm a bit worried with this landing so late, but it's something we'd
want for sure. FFe approved.

** Changed in: software-properties (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1756364

Title:
  [ffe] Livepatch integration

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  One feature we want to add to the desktop for the LTS is to allow
  users to enable livepatch from the desktop.

  The software-properties utility has been updated to add a control allowing to 
enable livepatch, the code is up for review there:
  
https://code.launchpad.net/~azzar1/software-properties/add-canonical-livepatch/+merge/341427

  That's based on the gnome-online-account ubuntu sso provider which has
  been added to bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1756364/+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

[Touch-packages] [Bug 1737570] Re: Add support for RequiredForOnline in networkd

2018-03-21 Thread Francis Ginther

** Tags added: id-5a27044d7e3f1a528751c449

-- 
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/1737570

Title:
  Add support for RequiredForOnline in networkd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * netplan & networkd based systems typically await networking to be
  up on boot, without any ability to specify that an interface should be
  configured, but might not be online at boot. This is a backport of the
  RequiredForOnline= feature to match optional=true in netplan.

  [Test Case]

   * Configure a netowkring interface using .link/.network file and specify 
RequiredForOnline=False
   * Bring the interface down / offline it
   * execute systemd-networkd-wait-online, which should exit immediately since 
no interfaces are required to be online

  [Regression Potential]

   * This adds a support for an additional stanza in the network files.
  This stanza is not used by default. if the stanza is used, but older
  networkd is in use, networkd will ignore this unknown stanza. Thus
  this change is backward and forward compatible. The difference is that
  boot is not blocked awaiting systemd-networkd-wait-online to timeout.

  [Other Info]
   
   * Original bug report

  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737570/+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

[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

** Changed in: systemd (Ubuntu Xenial)
   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/1721223

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
  fix were SRU'd, will all of these things in the wild cope with this
  sysctl change?

  [Other Info]

   * Original bug report

  Hi there,
  we found a replicable issue that involves the Ubuntu Core networking and 
causes complete loss of connectivity.
  We run a custom board with ubuntu core: the architecure is amrhf.
  We replicated this issue with an official Ubuntu Core image on a Raspberry 
Pi: other platform was been tested.
  It shows that it is a snap core problem which interests networkd: we use the 
default network stack based on networkd + netplan.

  Below steps to replicate the issue.

  1)Setup a dhcp server for lease of abo

[Touch-packages] [Bug 1718444] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1718444

Title:
  systemd-sysctl in Xenial is not obeying the order of the sysctls

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * sysctls are applied out of order

  [Test Case]

   * Monitor that sysctls are applied in-order, instead of out of order
  / random order.

  [Regression Potential]

   * Cherrypick of an upstream patch which is present in v232+ and in
  use in Ubuntu in later releases. The code changes are minimal,
  updating s/Hashmap/OrderedHashmap/ which is implemented and available
  in xenial's systemd.

  
https://github.com/systemd/systemd/commit/886cf982d3018f7451f0548dadbc05bd2d583bb6

  [Other Info]
   
   * Original bug report.

  systemd-sysctl in Xenial forces itself over procps by shipping a link
  for procps.service to systemd-sysctl.service. However, it does not
  obey the order both of the files and also of the sysctls within the
  files. Instead it uses a simple hashmap. As it turns out that's fixed
  upstream and systemd master uses an ordered hashmap because of this,
  which at least preserves order within single files. Traditionally
  files in sysctl.d have been prefixed with numbers to ensure an order
  and that's now completely non-deterministic on Xenial.

  Relevant upstream commit:
  
https://github.com/systemd/systemd/commit/886cf982d3018f7451f0548dadbc05bd2d583bb6

  Note that conf_files_list_nulstr in master sorts the configuration
  files using strcmp, so even order of configuration files should be
  obeyed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718444/+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

[Touch-packages] [Bug 1737570] Re: Add support for RequiredForOnline in networkd

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

** Changed in: systemd (Ubuntu Xenial)
   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/1737570

Title:
  Add support for RequiredForOnline in networkd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * netplan & networkd based systems typically await networking to be
  up on boot, without any ability to specify that an interface should be
  configured, but might not be online at boot. This is a backport of the
  RequiredForOnline= feature to match optional=true in netplan.

  [Test Case]

   * Configure a netowkring interface using .link/.network file and specify 
RequiredForOnline=False
   * Bring the interface down / offline it
   * execute systemd-networkd-wait-online, which should exit immediately since 
no interfaces are required to be online

  [Regression Potential]

   * This adds a support for an additional stanza in the network files.
  This stanza is not used by default. if the stanza is used, but older
  networkd is in use, networkd will ignore this unknown stanza. Thus
  this change is backward and forward compatible. The difference is that
  boot is not blocked awaiting systemd-networkd-wait-online to timeout.

  [Other Info]
   
   * Original bug report

  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737570/+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

[Touch-packages] [Bug 1734409] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1734409

Title:
  systemd-sysctl: exit gracefully on EPERM/EACCESS

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * systemd-sysctl service fails in containers, due to read-only sysfs,
  which is normal.

  [Test Case]

   * Ensure systemd-sysctl is successful in containers, e.g. lxc & lxd

  [Regression Potential]

   * The application of sysctls fails anyway, but at least in this case
  false-errors are not reported and the container doesn't enter
  "degraded" state without a good reason.

  [Other Info]
   
   * Original bug report

  Hi everyone,

  systemd-sysctl in systemd versions prior to 232 will exit with FAILED
  when not being able to apply kernel variables. In containers it should
  simply move on and exit with SUCCESS. Upstream systemd carries
  appropriate patches for this already. The relevant commits are:

  411e869f497c7c7bd0688f1e3500f9043bc56e48
  39540de8abe24886693ca29a9caeea85c88089aa

  these should be backported to xenial's systemd.

  Christian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734409/+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

[Touch-packages] [Bug 1718444] Re: systemd-sysctl in Xenial is not obeying the order of the sysctls

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

** Changed in: systemd (Ubuntu Xenial)
   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/1718444

Title:
  systemd-sysctl in Xenial is not obeying the order of the sysctls

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * sysctls are applied out of order

  [Test Case]

   * Monitor that sysctls are applied in-order, instead of out of order
  / random order.

  [Regression Potential]

   * Cherrypick of an upstream patch which is present in v232+ and in
  use in Ubuntu in later releases. The code changes are minimal,
  updating s/Hashmap/OrderedHashmap/ which is implemented and available
  in xenial's systemd.

  
https://github.com/systemd/systemd/commit/886cf982d3018f7451f0548dadbc05bd2d583bb6

  [Other Info]
   
   * Original bug report.

  systemd-sysctl in Xenial forces itself over procps by shipping a link
  for procps.service to systemd-sysctl.service. However, it does not
  obey the order both of the files and also of the sysctls within the
  files. Instead it uses a simple hashmap. As it turns out that's fixed
  upstream and systemd master uses an ordered hashmap because of this,
  which at least preserves order within single files. Traditionally
  files in sysctl.d have been prefixed with numbers to ensure an order
  and that's now completely non-deterministic on Xenial.

  Relevant upstream commit:
  
https://github.com/systemd/systemd/commit/886cf982d3018f7451f0548dadbc05bd2d583bb6

  Note that conf_files_list_nulstr in master sorts the configuration
  files using strcmp, so even order of configuration files should be
  obeyed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718444/+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

[Touch-packages] [Bug 1734409] Re: systemd-sysctl: exit gracefully on EPERM/EACCESS

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

** Changed in: systemd (Ubuntu Xenial)
   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/1734409

Title:
  systemd-sysctl: exit gracefully on EPERM/EACCESS

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * systemd-sysctl service fails in containers, due to read-only sysfs,
  which is normal.

  [Test Case]

   * Ensure systemd-sysctl is successful in containers, e.g. lxc & lxd

  [Regression Potential]

   * The application of sysctls fails anyway, but at least in this case
  false-errors are not reported and the container doesn't enter
  "degraded" state without a good reason.

  [Other Info]
   
   * Original bug report

  Hi everyone,

  systemd-sysctl in systemd versions prior to 232 will exit with FAILED
  when not being able to apply kernel variables. In containers it should
  simply move on and exit with SUCCESS. Upstream systemd carries
  appropriate patches for this already. The relevant commits are:

  411e869f497c7c7bd0688f1e3500f9043bc56e48
  39540de8abe24886693ca29a9caeea85c88089aa

  these should be backported to xenial's systemd.

  Christian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734409/+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

[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

** Changed in: systemd (Ubuntu Xenial)
   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/1717471

Title:
  networkd does not accept / set advertised mtu

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in nplan source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Hosts may require a specific MTU to be set as passed by DHCP options. We 
should honor these settings to ensure proper communication of the host with the 
rest of the network.

  [Test case]
  1) Run netplan on a system that should receive MTU settings from DHCP.
  2) Validate that the MTU configuration provided by DHCP is applied to the 
right interface.

  [Regression Potential]
  If DHCP settings specify an invalid MTU setting which is currently being 
ignored and letting the systems communicate correctly with the network, then 
these systems would regress.

  ---

   Right, so as far as I can tell the neutron-api on lcy01 is
  configured to advertise an instance interface MTU of 1400, though
  that's lower than it has to be, and the new DHCP setup with networkd
  just doesn't respect that DHCP option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+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

[Touch-packages] [Bug 1754265] Re: packagekitd crashed with SIGSEGV in utilBuildPackageId()

This bug was fixed in the package packagekit - 1.1.9-1ubuntu1

---
packagekit (1.1.9-1ubuntu1) bionic; urgency=medium

  * Add might-fetch-non-archive.diff to prevent PackageKit from crashing
when using the mirror method (LP: #1754265)

 -- Julian Andres Klode   Wed, 21 Mar 2018 12:32:34
+0100

** Changed in: packagekit (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1754265

Title:
  packagekitd crashed with SIGSEGV in utilBuildPackageId()

Status in packagekit package in Ubuntu:
  Fix Released

Bug description:
  PackageKit seems to be crashing randomly on bionic, not sure why, did
  not investigate further yet.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: packagekit 1.1.7-1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Thu Mar  8 08:35:34 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2017-12-08 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  SegvAnalysis:
   Segfault happened at: 0x7fca622a9ecc 
<_Z18utilBuildPackageIdRKN8pkgCache11VerIteratorE+124>: cmpb   $0x6,0x22(%rax)
   PC (0x7fca622a9ecc) ok
   source "$0x6" ok
   destination "0x22(%rax)" (0x0015f6da) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: packagekit
  StacktraceTop:
   utilBuildPackageId(pkgCache::VerIterator const&) () at 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   AptIntf::emitPackage(pkgCache::VerIterator const&, PkInfoEnum) () at 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   AcqPackageKitStatus::updateStatus(pkgAcquire::ItemDesc&, int) () at 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   pkgAcquire::Worker::RunMessages() () at 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   pkgAcquire::Worker::InFdReady() () at 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
  Title: packagekitd crashed with SIGSEGV in utilBuildPackageId()
  UpgradeStatus: Upgraded to bionic on 2017-12-08 (89 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1754265/+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

[Touch-packages] [Bug 1661869] Please test proposed package

Hello Dustin, or anyone else affected,

Accepted avahi into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/avahi/0.6.32-1ubuntu1.1 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-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. 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/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1661869

Title:
  maas install fails inside of a 16.04 lxd container due to avahi
  problems

Status in MAAS:
  Invalid
Status in avahi package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in avahi source package in Trusty:
  Fix Committed
Status in lxd source package in Trusty:
  Invalid
Status in avahi source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Invalid
Status in avahi source package in Artful:
  Fix Committed
Status in lxd source package in Artful:
  Invalid

Bug description:
  [Original Description]
  The bug, and workaround, are clearly described in this mailing list thread:

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2016-January/010791.html

  I'm trying to install MAAS in a LXD container, but that's failing due
  to avahi package install problems.  I'm tagging all packages here.

  [Issue]
  Avahi sets a number of rlimits on startup including the maximum number of 
processes (nproc=2) and limits on memory usage.  These limits are hit in a 
number of cases  - specifically the maximum process limit is hit if you run lxd 
containers in 'privileged' mode such that avahi has the same uid in multiple 
containers and large networks can trigger the memory limit.

  The fix is to remove these default rlimits completely from the
  configuration file.

  [Impact]

   * Avahi is unable to start inside of containers without UID namespace 
isolation because an rlimit on the maximum number of processes is set by 
default to 2.  When a container launches Avahi, the total number of processes 
on the system in all containers exceeds this limit and Avahi is killed.  It 
also fails at install time, rather than runtime due to a failure to start the 
service.
   * Some users also have issues with the maximum memory allocation causing 
Avahi to exit on networks with a large number of services as the memory limit 
was quite small (4MB).  Refer LP #1638345

  [Test Case]

   * setup lxd (apt install lxd, lxd init, get working networking)
   * lxc launch ubuntu:16.04 avahi-test --config security.privileged=true
   * lxc exec avahi-test sudo apt install avahi-daemon

  This will fail if the parent host has avahi-daemon installed, however,
  if it does not you can setup a second container (avahi-test2) and
  install avahi there.  That should then fail (as the issue requires 2
  copies of avahi-daemon in the same uid namespace to fail)

  [Regression Potential]

   * The fix removes all rlimits configured by avahi on startup, this is
  an extra step avahi takes that most programs did not take (limiting
  memory usage, running process count, etc).  It's possible an unknown
  bug then consumes significant system resources as a result of that
  limit no longer being in place, that was previously hidden by Avahi
  crashing instead.  However I believe this risk is significantly
  reduced as this change has been shipping upstream for many months and
  have not seen any reports of new problems - however it has fixed a
  number of existing crashes/problems.

   * The main case this may not fix the issue is if they have modified
  their avahi-daemon.conf file - but it will fix new installs and most
  installs as most users don't modify the file. And users may be
  prompted on upgrade to replace the file.

  [Other Info]

   * This change already exists upstream in 0.7 which is in bionic.  SRU
  required to artful, xenial, trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1661869/+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

[Touch-packages] [Bug 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems

Hello Dustin, or anyone else affected,

Accepted avahi into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/avahi/0.6.31-4ubuntu1.2 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-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. 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/PerformingSRUVerification .  Thank you in
advance!

** Changed in: avahi (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1661869

Title:
  maas install fails inside of a 16.04 lxd container due to avahi
  problems

Status in MAAS:
  Invalid
Status in avahi package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in avahi source package in Trusty:
  Fix Committed
Status in lxd source package in Trusty:
  Invalid
Status in avahi source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Invalid
Status in avahi source package in Artful:
  Fix Committed
Status in lxd source package in Artful:
  Invalid

Bug description:
  [Original Description]
  The bug, and workaround, are clearly described in this mailing list thread:

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2016-January/010791.html

  I'm trying to install MAAS in a LXD container, but that's failing due
  to avahi package install problems.  I'm tagging all packages here.

  [Issue]
  Avahi sets a number of rlimits on startup including the maximum number of 
processes (nproc=2) and limits on memory usage.  These limits are hit in a 
number of cases  - specifically the maximum process limit is hit if you run lxd 
containers in 'privileged' mode such that avahi has the same uid in multiple 
containers and large networks can trigger the memory limit.

  The fix is to remove these default rlimits completely from the
  configuration file.

  [Impact]

   * Avahi is unable to start inside of containers without UID namespace 
isolation because an rlimit on the maximum number of processes is set by 
default to 2.  When a container launches Avahi, the total number of processes 
on the system in all containers exceeds this limit and Avahi is killed.  It 
also fails at install time, rather than runtime due to a failure to start the 
service.
   * Some users also have issues with the maximum memory allocation causing 
Avahi to exit on networks with a large number of services as the memory limit 
was quite small (4MB).  Refer LP #1638345

  [Test Case]

   * setup lxd (apt install lxd, lxd init, get working networking)
   * lxc launch ubuntu:16.04 avahi-test --config security.privileged=true
   * lxc exec avahi-test sudo apt install avahi-daemon

  This will fail if the parent host has avahi-daemon installed, however,
  if it does not you can setup a second container (avahi-test2) and
  install avahi there.  That should then fail (as the issue requires 2
  copies of avahi-daemon in the same uid namespace to fail)

  [Regression Potential]

   * The fix removes all rlimits configured by avahi on startup, this is
  an extra step avahi takes that most programs did not take (limiting
  memory usage, running process count, etc).  It's possible an unknown
  bug then consumes significant system resources as a result of that
  limit no longer being in place, that was previously hidden by Avahi
  crashing instead.  However I believe this risk is significantly
  reduced as this change has been shipping upstream for many months and
  have not seen any reports of new problems - however it has fixed a
  number of existing crashes/problems.

   * The main case this may not fix the issue is if they have modified
  their avahi-daemon.conf file - but it will fix new installs and most
  installs as most users don't modify the file. And users may be
  prompted on upgrade to replace the file.

  [Other Info]

   * This change already exists upstream in 0.7 which is in bionic.  SRU
  required to artful, xenial, trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1661869/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsub

[Touch-packages] [Bug 1661869] Please test proposed package

Hello Dustin, or anyone else affected,

Accepted avahi into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/avahi/0.6.32~rc+dfsg-
1ubuntu2.1 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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/PerformingSRUVerification .  Thank you in
advance!

** Changed in: avahi (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1661869

Title:
  maas install fails inside of a 16.04 lxd container due to avahi
  problems

Status in MAAS:
  Invalid
Status in avahi package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in avahi source package in Trusty:
  Fix Committed
Status in lxd source package in Trusty:
  Invalid
Status in avahi source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Invalid
Status in avahi source package in Artful:
  Fix Committed
Status in lxd source package in Artful:
  Invalid

Bug description:
  [Original Description]
  The bug, and workaround, are clearly described in this mailing list thread:

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2016-January/010791.html

  I'm trying to install MAAS in a LXD container, but that's failing due
  to avahi package install problems.  I'm tagging all packages here.

  [Issue]
  Avahi sets a number of rlimits on startup including the maximum number of 
processes (nproc=2) and limits on memory usage.  These limits are hit in a 
number of cases  - specifically the maximum process limit is hit if you run lxd 
containers in 'privileged' mode such that avahi has the same uid in multiple 
containers and large networks can trigger the memory limit.

  The fix is to remove these default rlimits completely from the
  configuration file.

  [Impact]

   * Avahi is unable to start inside of containers without UID namespace 
isolation because an rlimit on the maximum number of processes is set by 
default to 2.  When a container launches Avahi, the total number of processes 
on the system in all containers exceeds this limit and Avahi is killed.  It 
also fails at install time, rather than runtime due to a failure to start the 
service.
   * Some users also have issues with the maximum memory allocation causing 
Avahi to exit on networks with a large number of services as the memory limit 
was quite small (4MB).  Refer LP #1638345

  [Test Case]

   * setup lxd (apt install lxd, lxd init, get working networking)
   * lxc launch ubuntu:16.04 avahi-test --config security.privileged=true
   * lxc exec avahi-test sudo apt install avahi-daemon

  This will fail if the parent host has avahi-daemon installed, however,
  if it does not you can setup a second container (avahi-test2) and
  install avahi there.  That should then fail (as the issue requires 2
  copies of avahi-daemon in the same uid namespace to fail)

  [Regression Potential]

   * The fix removes all rlimits configured by avahi on startup, this is
  an extra step avahi takes that most programs did not take (limiting
  memory usage, running process count, etc).  It's possible an unknown
  bug then consumes significant system resources as a result of that
  limit no longer being in place, that was previously hidden by Avahi
  crashing instead.  However I believe this risk is significantly
  reduced as this change has been shipping upstream for many months and
  have not seen any reports of new problems - however it has fixed a
  number of existing crashes/problems.

   * The main case this may not fix the issue is if they have modified
  their avahi-daemon.conf file - but it will fix new installs and most
  installs as most users don't modify the file. And users may be
  prompted on upgrade to replace the file.

  [Other Info]

   * This change already exists upstream in 0.7 which is in bionic.  SRU
  required to artful, xenial, trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1661869/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : ht

[Touch-packages] [Bug 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems

Unsubscribed ~ubuntu-sponsors as there is nothing left to sponsor.

** Changed in: avahi (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1661869

Title:
  maas install fails inside of a 16.04 lxd container due to avahi
  problems

Status in MAAS:
  Invalid
Status in avahi package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in avahi source package in Trusty:
  Fix Committed
Status in lxd source package in Trusty:
  Invalid
Status in avahi source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Invalid
Status in avahi source package in Artful:
  Fix Committed
Status in lxd source package in Artful:
  Invalid

Bug description:
  [Original Description]
  The bug, and workaround, are clearly described in this mailing list thread:

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2016-January/010791.html

  I'm trying to install MAAS in a LXD container, but that's failing due
  to avahi package install problems.  I'm tagging all packages here.

  [Issue]
  Avahi sets a number of rlimits on startup including the maximum number of 
processes (nproc=2) and limits on memory usage.  These limits are hit in a 
number of cases  - specifically the maximum process limit is hit if you run lxd 
containers in 'privileged' mode such that avahi has the same uid in multiple 
containers and large networks can trigger the memory limit.

  The fix is to remove these default rlimits completely from the
  configuration file.

  [Impact]

   * Avahi is unable to start inside of containers without UID namespace 
isolation because an rlimit on the maximum number of processes is set by 
default to 2.  When a container launches Avahi, the total number of processes 
on the system in all containers exceeds this limit and Avahi is killed.  It 
also fails at install time, rather than runtime due to a failure to start the 
service.
   * Some users also have issues with the maximum memory allocation causing 
Avahi to exit on networks with a large number of services as the memory limit 
was quite small (4MB).  Refer LP #1638345

  [Test Case]

   * setup lxd (apt install lxd, lxd init, get working networking)
   * lxc launch ubuntu:16.04 avahi-test --config security.privileged=true
   * lxc exec avahi-test sudo apt install avahi-daemon

  This will fail if the parent host has avahi-daemon installed, however,
  if it does not you can setup a second container (avahi-test2) and
  install avahi there.  That should then fail (as the issue requires 2
  copies of avahi-daemon in the same uid namespace to fail)

  [Regression Potential]

   * The fix removes all rlimits configured by avahi on startup, this is
  an extra step avahi takes that most programs did not take (limiting
  memory usage, running process count, etc).  It's possible an unknown
  bug then consumes significant system resources as a result of that
  limit no longer being in place, that was previously hidden by Avahi
  crashing instead.  However I believe this risk is significantly
  reduced as this change has been shipping upstream for many months and
  have not seen any reports of new problems - however it has fixed a
  number of existing crashes/problems.

   * The main case this may not fix the issue is if they have modified
  their avahi-daemon.conf file - but it will fix new installs and most
  installs as most users don't modify the file. And users may be
  prompted on upgrade to replace the file.

  [Other Info]

   * This change already exists upstream in 0.7 which is in bionic.  SRU
  required to artful, xenial, trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1661869/+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

[Touch-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

> [Regression Potential]

> no regression possibility, since this commit is already in artful and
bionic.

No. Please review https://wiki.ubuntu.com/StableReleaseUpdates#Why and
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure and update the
bug description accordingly.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1750947

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  New

Bug description:
  SRU Document:

  [Impact]

  A HDMI audio device usually has several output ports, each port
  represents a profile in pulseaudio, without this patch, the puseaudio
  always choose the first profile no matter it is active or not.

  [Test Case]

  connect each port of HDMI device, and check if the profile of that
  port is active or not.

  [Regression Potential]

  no regression possibility, since this commit is already in artful and
  bionic.

  [Other Info]

  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+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

Re: [Touch-packages] [Bug 1757256] Re: Apparmor profile gajim

2018-03-21 Thread george jetson

I'm getting the following error in my journal.


systemd-coredump[1101]: Process 1099 (gajim) of user 1000 dumped core.
 
  Stack trace of thread 2:
  #0  0x611ea4d9a860
raise (libc.so.6)
  #1  0x611ea4d9bec9
abort (libc.so.6)
  #2  0x611ea488bcee
Py_FatalError (libpython3.6m.so.1.0)
  #3  0x611ea488c168
n/a (libpython3.6m.so.1.0)
  #4  0x611ea49f624d
_Py_InitializeEx_Private (libpython3.6m.so.1.0)
  #5  0x611ea49ec34a
Py_Main (libpython3.6m.so.1.0)
  #6  0x029f72942c39
main (python3.6)
  #7  0x611ea4d86f4a
__libc_start_main (libc.so.6)
  #8  0x029f72942dba
_start (python3.6)


On 03/21/2018 01:00 PM, Mike Miller wrote:
> Still not working. Please help.
>
> the audit logs when launching gajim are:
>
> 
>
> type=SYSCALL msg=audit(1521623303.636:86): arch=c03e syscall=2
> success=no exit=-13 a0=659281e35d38 a1=90800 a2=6592816e73f0
> a3=659281e49000 items=1 ppid=1053 pid=1119 auid=1000 uid=0 gid=0 euid=0
> suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=2 comm="gajim"
> exe="/usr/bin/python3.6" key=(null)
> type=CWD msg=audit(1521623303.636:86): cwd="/home/user"
> type=PATH msg=audit(1521623303.636:86): item=0 name="/usr/lib/python3.6"
> inode=19437 dev=00:17 mode=040755 ouid=0 ogid=0 rdev=00:00
> nametype=NORMAL cap_fp= cap_fi= cap_fe=0
> cap_fver=0
> type=PROCTITLE msg=audit(1521623303.636:86):
> proctitle=2F7573722F62696E2F707974686F6E002F7573722F62696E2F67616A696D
> type=AVC msg=audit(1521623303.637:87): apparmor="ALLOWED"
> operation="open" info="Failed name lookup - disconnected path" error=-13
> profile="/usr/bin/gajim" name="usr/lib/python3.6/lib-dynload" pid=1119
> comm="gajim" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
> type=SYSCALL msg=audit(1521623303.637:87): arch=c03e syscall=2
> success=no exit=-13 a0=659281e424d0 a1=90800 a2=6592816e73f0
> a3=659281e09000 items=1 ppid=1053 pid=1119 auid=1000 uid=0 gid=0 euid=0
> suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=2 comm="gajim"
> exe="/usr/bin/python3.6" key=(null)
> type=CWD msg=audit(1521623303.637:87): cwd="/home/user"
> type=PATH msg=audit(1521623303.637:87): item=0
> name="/usr/lib/python3.6/lib-dynload" inode=17086 dev=00:17 mode=040755
> ouid=0 ogid=0 rdev=00:00 nametype=NORMAL cap_fp=
> cap_fi= cap_fe=0 cap_fver=0
> type=PROCTITLE msg=audit(1521623303.637:87):
> proctitle=2F7573722F62696E2F707974686F6E002F7573722F62696E2F67616A696D
> type=ANOM_ABEND msg=audit(1521623303.637:88): auid=1000 uid=0 gid=0
> ses=2 pid=1119 comm="gajim" exe="/usr/bin/python3.6" sig=6 res=1
>
> 
>
> The profile I used:
>
> # Last Modified: Wed Mar 21 00:06:33 2018
> #include 
>
> /usr/bin/gajim flags=(complain) {
>   #include 
>   #include 
>   #include 
>   /** rwk,
>   /home/user/** r,
>   /home/user/.local/share/gajim/** rwk,
>   /home/user/.cache/gajim/** rwk,
>   /usr/lib/python3.6/** rk,
>   /home/user/.local/lib/** rk,
>   /proc/*/net/arp rk,
>   owner "/home/*/.mozilla/firefox/Crash Reports/**" rk,
>   owner /home/*/ rk,
>   owner /home/*/.ICEauthority rk,
>   owner /home/*/.Xauthority rk,
>   owner /home/*/.cache/fontconfig/** rwk,
>   owner /home/*/.cache/gajim/** rwk,
>   owner /home/*/.config/** rwk,
>   owner /home/*/.local/lib/python2.7/site-packages/ rk,
>   owner /home/*/.local/lib/python3.6/site-packages/ rk,
>   owner /home/*/.local/share/applications/ rk,
>   owner /home/*/.local/share/gajim/* rwk,
>   owner /home/*/.local/share/* rwk,
>   owner /home/*/.mozilla/firefox/* rk,
>   owner /proc/*/fd/ rk,
>   owner /proc/*/mounts rk,
>
> On 03/21/2018 02:40 AM, Seth Arnold wrote:
>> Hello,
>>
>>  open("/home/user", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 EACCES 
>> (Permission denied)
>> ...
>>  open("/usr/lib/python3.6", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 
>> EACCES (Permission denied)
>> etc
>>
>> Probably these all generated DENIED lines in your logs.
>>
>> And probably running aa-logprof would prompt you about them. Allow them
>> as appropriate and probably you'll be good to go.
>>
>> Thanks
>>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1757256

Title:
  Apparmor profile gajim

Status in apparmor package in Ubuntu:
  New

Bug description:
  Followed this guide: https://gitlab.com/apparmor/a

[Touch-packages] [Bug 1757444] [NEW] [Ubuntu SSO] When a second opt is required, text entry should be empty.

2018-03-21 Thread Andrea Azzarone

Public bug reported:

When a second otp is required the text entry should be cleared.

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Medium
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => In Progress

** Changed in: gnome-online-accounts (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1757444

Title:
  [Ubuntu SSO] When a second opt is required, text entry should be
  empty.

Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  When a second otp is required the text entry should be cleared.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1757444/+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

[Touch-packages] [Bug 1757444] Re: [Ubuntu SSO] When a second opt is required, text entry should be empty.

2018-03-21 Thread Andrea Azzarone

Please find attached a debdiff that addresses this issue.

** Attachment added: "goa.debidff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1757444/+attachment/5085912/+files/goa.debidff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1757444

Title:
  [Ubuntu SSO] When a second opt is required, text entry should be
  empty.

Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  When a second otp is required the text entry should be cleared.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1757444/+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

[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

2018-03-21 Thread Andre Tomt

systemd upgrades are now failing in my build chroots, and I suspect it
is related to this change.

Setting up systemd (234-2ubuntu12.3) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
[/usr/lib/tmpfiles.d/tmp.conf:15] Failed to replace specifiers: 
/tmp/systemd-private-%b-*
[/usr/lib/tmpfiles.d/tmp.conf:16] Failed to replace specifiers: 
/tmp/systemd-private-%b-*/tmp
[/usr/lib/tmpfiles.d/tmp.conf:17] Failed to replace specifiers: 
/var/tmp/systemd-private-%b-*
[/usr/lib/tmpfiles.d/tmp.conf:18] Failed to replace specifiers: 
/var/tmp/systemd-private-%b-*/tmp
ACL operation on "/var/log/journal" failed: No such file or directory
ACL operation on "/var/log/journal" failed: No such file or directory
chmod() of /var/log/journal via /proc/self/fd/3 failed: No such file or 
directory
dpkg: error processing package systemd (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- 
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/1618188

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * System logs are lost across reboots because they are not stored
  persistently.

  [Test Case]

   * Fresh installations, or upgrades to this version of systemd, should create 
/var/log/journal and trigger automatic persistent logs.
   * Users may choose to remove said directory, or disable persistent logging 
in /etc/systemd/journald.conf

  [Regression Potential]

   * Persistent logging by default will cause logs to be flushed from
  /run to /var/log, meaning there will be less RAM used (/run is tmpfs
  backed), but increased disk usage (in /var/log). The journald daemon
  has limits set for logs, meaning they will be rotated and discarded
  and should not cause out of disk-space errors.

  [Other Info]
   
   * Original bug report

  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't.
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/+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

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

This bug was fixed in the package plymouth - 0.9.3-1ubuntu2

---
plymouth (0.9.3-1ubuntu2) bionic; urgency=medium

  * Make the lsb-release triggers interest-noawait, so that we don't block
configuration of an Essential: yes package during upgrades.
LP: #1750465.

 -- Steve Langasek   Tue, 20 Mar 2018
23:15:58 -0700

** Changed in: plymouth (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1750465

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  New
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  New
Status in ubuntu-mate-artwork package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in budgie-artwork source package in Artful:
  New
Status in kubuntu-settings source package in Artful:
  New
Status in plymouth source package in Artful:
  In Progress
Status in ubuntu-gnome-default-settings source package in Artful:
  New
Status in ubuntu-mate-artwork source package in Artful:
  New

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from artful-proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  
  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (0 days ago)
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.versi

[Touch-packages] [Bug 1750465] Please test proposed package

Hello Stephen, or anyone else affected,

Accepted plymouth into artful-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/plymouth/0.9.2-3ubuntu18 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-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. 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/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1750465

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  New
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  New
Status in ubuntu-mate-artwork package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in budgie-artwork source package in Artful:
  New
Status in kubuntu-settings source package in Artful:
  New
Status in plymouth source package in Artful:
  Fix Committed
Status in ubuntu-gnome-default-settings source package in Artful:
  New
Status in ubuntu-mate-artwork source package in Artful:
  New

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from artful-proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  
  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.

[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

Here is something really interesting. mplayer (from CLI) plays mp3 Ok. mplayer
has libav/ffmpeg dependencies of libavcodec-ffmpeg56, libavutil-ffmpeg &
libavformat-ffmpeg56. vlc only has the first 2 of those packages as
libav/ffmpeg dependencies. So my deduction is that this problem has nothing to
do with libav/ffmpeg.
However, attached Terminal output for running mplayer, ffmpeg & vlc doesn't
offer real clues to me: as mplayer seems to use libavformat, ffmpeg doesn't
tell me anything (thoughit might to you) & vlc says nothing to me.
Could you take a look at the output, particularly of the ffmpeg one?

** Attachment added: "mplayer-ffmpeg-vlc Terminal.txt"

https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1755144/+attachment/5085963/+files/mplayer-ffmpeg-vlc%20Terminal.txt

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1755144

Title:
No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
New
Status in pulseaudio package in Ubuntu:
Invalid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1755144/+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

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

14:04  juliank: based on https://bugs.launchpad.net/ubuntu/+source/apt/+
bug/1750465/comments/10, are you suggesting I should hold on processing slangase
k's SRU upload? 
14:04  Launchpad bug 1750465 in plymouth (Ubuntu Artful) "upgrade attemp
ting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-
3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unpr
ocessed)" [Undecided,In progress]
14:05  rbasak: I'm not sure what he did precisely, I only saw the bug m
essages.
14:06  juliank: http://launchpadlibrarian.net/361447927/plymouth_0.9.2-3
ubuntu17_0.9.2-3ubuntu18.diff.gz is his artful SRU upload. 
14:06  That should be correct anyway.
14:06  And it probably fixes the bug even if we don't know the exact 
reason yet...
14:07  OK. If you and slangasek both agree on what we should land, I'm 
happy :) 
14:07  I'll accept assuming all the other SRU bits look OK.


** Changed in: plymouth (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1750465

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  New
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  New
Status in ubuntu-mate-artwork package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in budgie-artwork source package in Artful:
  New
Status in kubuntu-settings source package in Artful:
  New
Status in plymouth source package in Artful:
  Fix Committed
Status in ubuntu-gnome-default-settings source package in Artful:
  New
Status in ubuntu-mate-artwork source package in Artful:
  New

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from artful-proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  
  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/py

[Touch-packages] [Bug 980519] Re: Random log off in Ubuntu 12.04 LTS

2018-03-21 Thread pun

My Lenovo logs me off when Android device plugged out from PC

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/980519

Title:
  Random log off in Ubuntu 12.04 LTS

Status in Unity:
  Fix Released
Status in gnome-desktop package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in Fedora:
  New

Bug description:
  I get logged off from Ubuntu sometimes. There is no error message or
  any indication that it is going to log off. The screen goes black, and
  after 2-4 seconds, i get presented with the Ubuntu Log On Screen.

  There is no clear pattern (or at least if have not noticed any). One
  time i am working with Netbeans, another time i am using firefox. This
  also means that at present i can not clearly say what package might be
  causing this behaviour.

  I am fairly sure the problem lies in 12.04 (or more precise - the
  combination of 12.04 and the hardware i am using). I do not have the
  same problem running 11.04 or 11.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/980519/+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

[Touch-packages] [Bug 559331] Re: Permanent "Printer-out-of-paper" message.

2018-03-21 Thread Paul Abraham

Any answers to this?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/559331

Title:
  Permanent "Printer-out-of-paper" message.

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cups

  This probably has to do with CUPS. Version: 1.4.1- 4ubuntu2.4 (latest
  on Karmic).

  I was printing a document when the printer was out of paper and got a
  message that "The printer is out of paper". I went to reload it and
  clicked resume on the printer and printing carried on normally.

  From this point on, the message "The printer is out of paper" is permanently 
stuck on the printer. 
  - Every time i print, i get the message "The printer is out of paper", but 
the printing occurs without errors. 
  - The configuration tool (system-config-printer 1.1.12) shows the printer 
with the red error sign. When viewing the properties of said printer, in the 
"Ink/Toner Levels" section, i have the "Status Message":  "Printer 
HP-Officejet-Pro-k550 is out of paper". If i click refresh then i get a "CUPS 
server error": "There was an error during the CUPS operation: 
'client-error-document-format-not-supported'." (Not sure this is relevant). 

  
  Removing and reinstalling the printer fixes this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/559331/+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

[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

2018-03-21 Thread James Cowgill

To get more logs you can run:
 mplayer -v 
 ffplay -loglevel verbose 
 vlc --verbose=2 

To play files with ffmpeg you want to run "ffplay" not "ffmpeg".

Also I notice:
 ffmpeg version 3.2.6-1~backport1.1~xenial
This is another different version of ffmpeg you tried to install?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1755144

Title:
  No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1755144/+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

[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

Another piece of information. Looking at the documentation for ffmpeg,
it mentioned ffplay. So I tried that in Terminal (attached) and the
sound was working. So what's so different between ffmpeg a& ffplay? BTW
I reverted back to the get_iplayer ppa for ffmpeg as that ppa (using
ffmpeg) works Ok on my other barebones PC and laptop.

** Attachment added: "ffplay Terminal.txt"

https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1755144/+attachment/5085986/+files/ffplay%20Terminal.txt

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1755144

Title:
No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
New
Status in pulseaudio package in Ubuntu:
Invalid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1755144/+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

[Touch-packages] [Bug 1757470] [NEW] apport autopkgtests broken (valgrind error) LXC regression?

Public bug reported:

--- Testing apport_valgrind ---
test_help_display (__main__.T)
help display ... ok
test_intentional_mem_leak_detection (__main__.T)
apport-valgrind log reports intentional memory leak ... ok
test_invalid_args (__main__.T)
return code is not 0 when invalid args are passed ... ok
test_sandbox_cache_options (__main__.T)
apport-valgrind creates a user specified sandbox and cache ... WARNING: 
/lib/x86_64-linux-gnu/libc.so.6 is needed, but cannot be mapped to a package
ERROR: Cannot find package which ships ExecutablePath /bin/true

Interrupted while creating sandbox
ERROR
test_unpackaged_exe (__main__.T)
apport-valgrind creates valgrind log on unpackaged executable ... 
/tmp/autopkgtest.aOT0xm/autopkgtest_tmp/apport-tests
ok
test_valgrind_min_installed (__main__.T)
valgrind is installed and recent enough ... ok
test_vlog_created (__main__.T)
apport-valgrind creates valgrind.log with expected content ... ok

==
ERROR: test_sandbox_cache_options (__main__.T)
apport-valgrind creates a user specified sandbox and cache
--
Traceback (most recent call last):
  File "./test_apport_valgrind.py", line 143, in test_sandbox_cache_options
subprocess.check_call(cmd)
  File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apport-valgrind', '--sandbox-dir', 
'/tmp/tmpbvxep0y2/test-sandbox', '--cache', '/tmp/tmpbvxep0y2/test-cache', 
'true']' returned non-zero exit status 1.

--
Ran 7 tests in 30.319s

FAILED (errors=1)
--- Testing backend_apt_dpkg ---

the regression seems to indicate a coreutils installation issue
apport-valgrind creates a user specified sandbox and cache ... Installing extra 
package coreutils to get ExecutablePath
Sandbox directory: /tmp/tmpoytew5vn/test-sandbox
Cache directory: /tmp/tmpoytew5vn/test-cache
ok

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: lxc (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1757470

Title:
  apport autopkgtests broken (valgrind error) LXC regression?

Status in apport package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  New

Bug description:
  --- Testing apport_valgrind ---
  test_help_display (__main__.T)
  help display ... ok
  test_intentional_mem_leak_detection (__main__.T)
  apport-valgrind log reports intentional memory leak ... ok
  test_invalid_args (__main__.T)
  return code is not 0 when invalid args are passed ... ok
  test_sandbox_cache_options (__main__.T)
  apport-valgrind creates a user specified sandbox and cache ... WARNING: 
/lib/x86_64-linux-gnu/libc.so.6 is needed, but cannot be mapped to a package
  ERROR: Cannot find package which ships ExecutablePath /bin/true

  Interrupted while creating sandbox
  ERROR
  test_unpackaged_exe (__main__.T)
  apport-valgrind creates valgrind log on unpackaged executable ... 
/tmp/autopkgtest.aOT0xm/autopkgtest_tmp/apport-tests
  ok
  test_valgrind_min_installed (__main__.T)
  valgrind is installed and recent enough ... ok
  test_vlog_created (__main__.T)
  apport-valgrind creates valgrind.log with expected content ... ok

  ==
  ERROR: test_sandbox_cache_options (__main__.T)
  apport-valgrind creates a user specified sandbox and cache
  --
  Traceback (most recent call last):
File "./test_apport_valgrind.py", line 143, in test_sandbox_cache_options
  subprocess.check_call(cmd)
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['apport-valgrind', '--sandbox-dir', 
'/tmp/tmpbvxep0y2/test-sandbox', '--cache', '/tmp/tmpbvxep0y2/test-cache', 
'true']' returned non-zero exit status 1.

  --
  Ran 7 tests in 30.319s

  FAILED (errors=1)
  --- Testing backend_apt_dpkg ---

  the regression seems to indicate a coreutils installation issue
  apport-valgrind creates a user specified sandbox and cache ... Installing 
extra package coreutils to get ExecutablePath
  Sandbox directory: /tmp/tmpoytew5vn/test-sandbox
  Cache directory: /tmp/tmpoytew5vn/test-cache
  ok

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1757470/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscrib

[Touch-packages] [Bug 1757470] Re: apport autopkgtests broken (valgrind error) LXC regression?

Timing and artifacts indicates an lxc regression:

liblxc-common   3.0.0~beta2-0ubuntu2 BAD
liblxc-common   3.0.0~beta1-0ubuntu3 GOOD

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1757470

Title:
  apport autopkgtests broken (valgrind error) LXC regression?

Status in apport package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  New

Bug description:
  --- Testing apport_valgrind ---
  test_help_display (__main__.T)
  help display ... ok
  test_intentional_mem_leak_detection (__main__.T)
  apport-valgrind log reports intentional memory leak ... ok
  test_invalid_args (__main__.T)
  return code is not 0 when invalid args are passed ... ok
  test_sandbox_cache_options (__main__.T)
  apport-valgrind creates a user specified sandbox and cache ... WARNING: 
/lib/x86_64-linux-gnu/libc.so.6 is needed, but cannot be mapped to a package
  ERROR: Cannot find package which ships ExecutablePath /bin/true

  Interrupted while creating sandbox
  ERROR
  test_unpackaged_exe (__main__.T)
  apport-valgrind creates valgrind log on unpackaged executable ... 
/tmp/autopkgtest.aOT0xm/autopkgtest_tmp/apport-tests
  ok
  test_valgrind_min_installed (__main__.T)
  valgrind is installed and recent enough ... ok
  test_vlog_created (__main__.T)
  apport-valgrind creates valgrind.log with expected content ... ok

  ==
  ERROR: test_sandbox_cache_options (__main__.T)
  apport-valgrind creates a user specified sandbox and cache
  --
  Traceback (most recent call last):
File "./test_apport_valgrind.py", line 143, in test_sandbox_cache_options
  subprocess.check_call(cmd)
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['apport-valgrind', '--sandbox-dir', 
'/tmp/tmpbvxep0y2/test-sandbox', '--cache', '/tmp/tmpbvxep0y2/test-cache', 
'true']' returned non-zero exit status 1.

  --
  Ran 7 tests in 30.319s

  FAILED (errors=1)
  --- Testing backend_apt_dpkg ---

  the regression seems to indicate a coreutils installation issue
  apport-valgrind creates a user specified sandbox and cache ... Installing 
extra package coreutils to get ExecutablePath
  Sandbox directory: /tmp/tmpoytew5vn/test-sandbox
  Cache directory: /tmp/tmpoytew5vn/test-cache
  ok

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1757470/+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

[Touch-packages] [Bug 1757388] Re: bridge device is missing

2018-03-21 Thread Marco

I have the same problem after a dist-upgrade on Ubuntu 18.04 server. All
my bridges are not found anymore. There was an update from .5-9ubuntu2
to 1.5-15ubuntu1, however downgrading does NOT fix the problem. Manually
setting the bridges works, but this is not a permanent solution.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1757388

Title:
  bridge device is missing

Status in bridge-utils package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04: Since last dist-upgrade of the bridge-utils (2018-03-21)
  the bridge netwok device 'br0' is missing. A 'ls /sys/class/net'
  prints the devices 'enp3s0  lo  lxcbr0  virbr0  virbr0-nic' only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1757388/+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

[Touch-packages] [Bug 1020048] Re: after certain time printing to cups stops working

2018-03-21 Thread Raúl Vidal

I have to confirm this bug. 300 seconds timeout. CUPS does not reopen 
connections again. Notifiers are shutdown.
The workaround is to enable the web interface. But this should not be 
necessary. CUPS should work without the web interface, as that is the default 
behaviour defined by upstream.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1020048

Title:
  after certain time printing to cups stops working

Status in LibreOffice:
  Invalid
Status in cups package in Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Invalid
Status in cups source package in Precise:
  Fix Released
Status in libreoffice source package in Precise:
  Invalid

Bug description:
  SRU justification:

  [Impact]

  * When the CUPS client connects to a remote cupsd over TCP, the server 
closes an idle connection after 5 minutes and the client does not reconnect.

  * LibreOffice is affected because it keeps a CUPS connection open. The 
effect is that printing to a remote cupsd is no longer possible after 
LibreOffice has been open for 5 minutes.

  [Test Case]

  * This can be reproduced on a desktop system. You don't need a separate 
CUPS server.

  * You need at least one print queue in CUPS. If you don't have a 
printer, install "cups-pdf".

  * Optional, configure CUPS with a shorter timeout for testing:

sudo cupsctl Timeout=30 # seconds
sudo restart cups

  * Configure the CUPS client to use a TCP socket:

mkdir ~/.cups
echo ServerName 127.0.0.1 > ~/.cups/client.conf

  * Open LibreOffice. Press Ctrl-P to open the Print dialog. Press Esc to 
dismiss the dialog. Wait long enough for the timout to elapse (5 
minutes by default, or as per the Timeout setting).

  * Try to print. With cups in precise, the job simply vanishes and is 
never seen by the server. With the proposed patch, printing works 
normally.

  [Regression Potential]

  * The patch changes a library linked by many programs. An incorrect 
change might result in those programs misbehaving or crashing.

  * The patch is minimal, only adding a branch to handle a case that was 
previously not handled. The behaviour in other cases should be 
unchanged.

  [Other Info]

  * A workaround is to set the cupsd Timeout to a high value such as 8 
hours. This works on a server with few users, but on a busy server 
more and more connections are opened and eventually cupsd isn't able 
to accept new clients.

  Original description:

  == Problem ==
  In our institution we are running only printers through a cups server. while 
freshly opened document prints well, after some time (few minutes) clicking 
"print file directly" and menu item "print" do not work any more. after close 
and open again, thing prints correctly. i have checked what exactly is going on 
in such cases and logs on the cups server don't show any submissions and/or 
errors so that the thing is obviously stopped at the level of libreoffice.

  == Analysis ==
  LibreOffice loses it's TCP connection to CUPS after exactly 5 minutes of 
inactivity and does not manage to reconnect. To reproduce: print something (to 
a real printer or cups-pdf), wait 6 minutes not printing anything, and print 
again. Then, nothing is printed. You can watch the TCP connection using
  netstat -tpn | grep soffice
  While it's working, it looks like this:
  tcp0  0 127.0.0.1:48810 127.0.0.1:631   
ESTABLISHED 13976/soffice.bin
  After 5 minutes, that connection is gone permanently.

  WORKAROUND: To set the timeout to 24 hours add this line to the top of 
/etc/cups/cupsd.conf :
  Timeout 62400

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1020048/+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

[Touch-packages] [Bug 1757470] Re: apport autopkgtests broken (valgrind error) LXC regression?

2018-03-21 Thread Christian Brauner

Can we get some logs for the LXC containers that created and fail?
Otherwise this is very much a black box.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1757470

Title:
  apport autopkgtests broken (valgrind error) LXC regression?

Status in apport package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  New

Bug description:
  --- Testing apport_valgrind ---
  test_help_display (__main__.T)
  help display ... ok
  test_intentional_mem_leak_detection (__main__.T)
  apport-valgrind log reports intentional memory leak ... ok
  test_invalid_args (__main__.T)
  return code is not 0 when invalid args are passed ... ok
  test_sandbox_cache_options (__main__.T)
  apport-valgrind creates a user specified sandbox and cache ... WARNING: 
/lib/x86_64-linux-gnu/libc.so.6 is needed, but cannot be mapped to a package
  ERROR: Cannot find package which ships ExecutablePath /bin/true

  Interrupted while creating sandbox
  ERROR
  test_unpackaged_exe (__main__.T)
  apport-valgrind creates valgrind log on unpackaged executable ... 
/tmp/autopkgtest.aOT0xm/autopkgtest_tmp/apport-tests
  ok
  test_valgrind_min_installed (__main__.T)
  valgrind is installed and recent enough ... ok
  test_vlog_created (__main__.T)
  apport-valgrind creates valgrind.log with expected content ... ok

  ==
  ERROR: test_sandbox_cache_options (__main__.T)
  apport-valgrind creates a user specified sandbox and cache
  --
  Traceback (most recent call last):
File "./test_apport_valgrind.py", line 143, in test_sandbox_cache_options
  subprocess.check_call(cmd)
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['apport-valgrind', '--sandbox-dir', 
'/tmp/tmpbvxep0y2/test-sandbox', '--cache', '/tmp/tmpbvxep0y2/test-cache', 
'true']' returned non-zero exit status 1.

  --
  Ran 7 tests in 30.319s

  FAILED (errors=1)
  --- Testing backend_apt_dpkg ---

  the regression seems to indicate a coreutils installation issue
  apport-valgrind creates a user specified sandbox and cache ... Installing 
extra package coreutils to get ExecutablePath
  Sandbox directory: /tmp/tmpoytew5vn/test-sandbox
  Cache directory: /tmp/tmpoytew5vn/test-cache
  ok

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1757470/+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

[Touch-packages] [Bug 1757467] [NEW] no windows arround gnumeric program with wayland

You have been subscribed to a public bug:

Sorry, english is not my native langage.

I use gnumeric on a platform with kubuntu 18.04 (beta1) ant plasma
5.12.3.

Using plasma session, all seems ok.

Using plasma WAYLAND session, gnumeric have no "windows" arround the
program. So i can't change the size and to close gnumeric, I have to use
the main menu.

** Affects: wayland (Ubuntu)
 Importance: Undecided
 Status: New

-- 
no windows arround gnumeric program with wayland
https://bugs.launchpad.net/bugs/1757467
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to wayland in Ubuntu.

-- 
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

[Touch-packages] [Bug 1757467] Re: no windows arround gnumeric program with wayland

2018-03-21 Thread tortosa

gnumeric's version is 1.12.35

** Project changed: yarock => gnumeric (Ubuntu)

** Package changed: gnumeric (Ubuntu) => wayland (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1757467

Title:
  no windows arround gnumeric program with wayland

Status in wayland package in Ubuntu:
  New

Bug description:
  Sorry, english is not my native langage.

  I use gnumeric on a platform with kubuntu 18.04 (beta1) ant plasma
  5.12.3.

  Using plasma session, all seems ok.

  Using plasma WAYLAND session, gnumeric have no "windows" arround the
  program. So i can't change the size and to close gnumeric, I have to
  use the main menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1757467/+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

[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

I ran the vlc & ffplay commands suggested above to give a log which is
attached. Is "mpgatofixed32 audio converter error: libmad error: bad
main_data_begin pointer" in the vlc significant as it's not in the ffplay log?
ffmpeg version 3.2.6-1~backport1.1~xenial package is part of the get-iplayer
ppa, which as I said before causes no problems in my other 2 Xenial PCs..

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1755144

Title:
No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
New
Status in pulseaudio package in Ubuntu:
Invalid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1755144/+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

[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

Apologies. I forgot to attach the log. I'm so used to Thunderbird where
it reminds you if you forget to make an attachment identified as needing
one from the email.

** Attachment added: "vlc-ffplay Verbose Terminal.txt"

https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1755144/+attachment/5085988/+files/vlc-ffplay%20Verbose%20Terminal.txt

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1755144

Title:
No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
New
Status in pulseaudio package in Ubuntu:
Invalid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1755144/+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

[Touch-packages] [Bug 1757280] Re: Night Light only on one Monitor

2018-03-21 Thread Paul White

** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu)

** Bug watch added: GNOME Bug Tracker #780167
   https://bugzilla.gnome.org/show_bug.cgi?id=780167

** Also affects: gnome-control-center via
   https://bugzilla.gnome.org/show_bug.cgi?id=780167
   Importance: Unknown
   Status: Unknown

** Summary changed:

- Night Light only on one Monitor
+ Night Light only works on one Monitor

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1757280

Title:
  Night Light only works on one Monitor

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  
  Hi

  If I activate the Night Light mode with an external monitor connected,
  the mode is only on the external monitor activated.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Mar 20 23:12:36 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2018-03-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319)
  MachineType: LENOVO 20HF0016MZ
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET45W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF0016MZ
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET45W(1.24):bd02/26/2018:svnLENOVO:pn20HF0016MZ:pvrThinkPadT470s:rvnLENOVO:rn20HF0016MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HF0016MZ
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1757280/+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

[Touch-packages] [Bug 1756987] Re: chrony install does not stop systemd-timesyncd

2018-03-21 Thread ChristianEhrhardt

The way the newer versions solve this is to have a native systemd
service and in there there is:

Conflicts=systemd-timesyncd.service openntpd.service

That ensures only one of these can be started.

Xenial has no systemd service at all, it has sysV and uses the systemd 
generator.
So there is no "just add the line" fix available.

Xenial as-is
$ timedatectl status
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no
systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
   └─disable-with-time-daemon.conf
   Active: active (running) since Wed 2018-03-21 16:00:19 UTC; 1min 30s ago

This isn't even fully protected if you install ntp (not chrony) as it
was the ntp server back in Xenial. (Right after install it still runs).

What stops it there for NTPd is that this uses a config dir which pulls in:
  /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

So any further starts will be blocked:
# don't run timesyncd if we have another NTP daemon installed
ConditionFileIsExecutable=!/usr/sbin/ntpd
ConditionFileIsExecutable=!/usr/sbin/openntpd
ConditionFileIsExecutable=!/usr/sbin/chronyd
ConditionFileIsExecutable=!/usr/sbin/VBoxService

You see that if you check systemd-timesyncd.service:
$ systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
   └─disable-with-time-daemon.conf
   Active: inactive (dead)
Condition: start condition failed at Wed 2018-03-21 16:06:42 UTC; 44s ago
   ConditionFileIsExecutable=!/usr/sbin/ntpd was not met

After installing Chrony this is the same:

Condition: start condition failed at Wed 2018-03-21 16:11:37 UTC; 1s ago
   ConditionFileIsExecutable=!/usr/sbin/chronyd was not met

That is good (no special issue to chrony) and bad (actually all
timeservers "collide" right after install).

A reboot or restart will pick that up.
OTOH it is discouraged to start/stop/restart other packages services form a 
postinst - as the first thought would be to do refresh for that condition after 
installing any of these.

Given that there was not a single complaint about it in 2 years of
Xenial other than us now looking for it in detail I'd rate it low, but
it is a valid issue.

** Also affects: ntp (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: openntpd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ntp (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: ntp (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: chrony (Ubuntu Bionic)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1756987

Title:
  chrony install does not stop systemd-timesyncd

Status in chrony package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in chrony source package in Xenial:
  New
Status in ntp source package in Xenial:
  Confirmed
Status in openntpd source package in Xenial:
  New
Status in chrony source package in Artful:
  New
Status in ntp source package in Artful:
  New
Status in openntpd source package in Artful:
  New
Status in chrony source package in Bionic:
  Fix Released
Status in ntp source package in Bionic:
  New
Status in openntpd source package in Bionic:
  New

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  root@ubuntu:~# uname -a
  Linux ubuntu 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  2. 
  root@ubuntu:~# apt-cache policy systemd
  systemd:
Installed: 229-4ubuntu21.1
Candidate: 229-4ubuntu21.1
Version table:
   *** 229-4ubuntu21.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  root@ubuntu:~# apt-cache policy chrony
  chrony:
Installed: 2.1.1-1
Candidate: 2.1.1-1
Version table:
   *** 2.1.1-1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  3. installing chrony should stop systemd-timesyncd so they both don't
  try to adjust time

  4. after chrony is installed both systemd-timesyncd and chronyd are
  running.

  root@ubuntu:~# ps aux | egrep "(chrony|timesync)"
  systemd+  1086  0.

[Touch-packages] [Bug 1757470] Re: apport autopkgtests broken (valgrind error) LXC regression?