[Touch-packages] [Bug 1859080] [NEW] NetworkMonitor.get_default() hangs consuming 100% of a core, blocking unattended-upgrades

2020-01-09 Thread Clint Armstrong
Public bug reported:

On an Ubuntu Server operating as a BGP router with over 800k routes, the
call to NetworkMonitor.get_default() invoked by unattended-upgrades will
hang indefinitely consuming a cpu core.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: python3-gi 3.20.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
Date: Thu Jan  9 16:03:20 2020
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm-kitty
 PATH=(custom, no user)
 LANG=en_US
 LANGUAGE=en_US:
SourcePackage: pygobject
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pygobject (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  NetworkMonitor.get_default() hangs consuming 100% of a core, blocking
  unattended-upgrades

Status in pygobject package in Ubuntu:
  New

Bug description:
  On an Ubuntu Server operating as a BGP router with over 800k routes,
  the call to NetworkMonitor.get_default() invoked by unattended-
  upgrades will hang indefinitely consuming a cpu core.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: python3-gi 3.20.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Thu Jan  9 16:03:20 2020
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm-kitty
   PATH=(custom, no user)
   LANG=en_US
   LANGUAGE=en_US:
  SourcePackage: pygobject
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1859080/+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 1826406] [NEW] Plymouth text overlaps

2019-04-25 Thread Clint Armstrong
Public bug reported:

When unattended-upgrades sends it's status to plymouth it sends a multi-
line string which causes plymouth to display overlapping text, because
plymouth only scrolls one line when the message is sent.

The attached patch fixes this issue.

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "unattended-upgrade-shutdown.patch"
   
https://bugs.launchpad.net/bugs/1826406/+attachment/5259032/+files/unattended-upgrade-shutdown.patch

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

Title:
  Plymouth text overlaps

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  When unattended-upgrades sends it's status to plymouth it sends a
  multi-line string which causes plymouth to display overlapping text,
  because plymouth only scrolls one line when the message is sent.

  The attached patch fixes this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1826406/+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 1675163] Re: Don't attempt to create devices in LXC containers

2018-04-06 Thread Clint Armstrong
This also affects containers running in systemd-nspawn containers

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

Title:
  Don't attempt to create devices in LXC containers

Status in makedev package in Ubuntu:
  Fix Released
Status in makedev source package in Precise:
  Fix Released
Status in makedev source package in Trusty:
  Fix Released
Status in makedev source package in Xenial:
  Fix Released
Status in makedev source package in Yakkety:
  Fix Released
Status in makedev source package in Zesty:
  Fix Released

Bug description:
  Right now the "makedev" postinst script will attempt to create a
  number of devices in /dev, failing the package upgrade should any of
  those mknod calls fail.

  LXC containers, especially unprivileged ones do not allow the use of
  mknod, making it impossible to upgrade makedev in those containers and
  preventing Ubuntu release upgrades.

  The fix is quite simple, detect that we are running in an LXC
  container and skip the rest of the postinst script as is done in a
  number of other cases.

  = SRU
  == Rationale
  This issue prevents release to release upgrades in unprivileged LXC 
containers when makedev is part of the upgraded set. This is currently visible 
when upgrading from Ubuntu 12.04 to Ubuntu 14.04.

  == Testcase
  Install the new package in an unprivileged container. With LXD, simply use 
"lxc launch ubuntu: test" to create the container.

  Prior to this fix, the upgrade will fail on some mknod errors, after
  it, it'll go on after printing a message indicating that LXC was
  detected.

  == Regression potential
  The detection logic is based on PID 1's environment containing a 
container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the 
makedev upgrade no longer creating extra devices. This is unlikely to really 
matter though since the system is clearly already functioning properly at that 
point.

  Similarly, some privileged LXC containers can be configured in a way
  where mknod is possible, this update will still disable the postinst
  for those cases as short of attempting every mknod ahead of time,
  there is no reliable way to detect any seccomp or apparmor policy in
  play.

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