[Touch-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

[Seyeong Kim]

** Description changed:

  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty
  
  affected to pacemaker 1.1.10.
- affected to glib2.0 2.40.2-0ubuntu1
+ affected to glib2.0 2.40.2-0ubuntu1 >> for glib2.0 created new lp [3]
  
  Please note that patch for pacemaker is created myself.
  
  [Test Case]
  
- 1. deploy 3 trusty instance.
- 2. install corosync, pacemaker, mysql.
- 3. setting with below info
- 3.1 corosync.conf, proper setting for 3 node
- 3.2 crm configure < setup.crm ( which has upstart:mysql setting )
- 3.3 monitor lrmd daemon's memory usage
+ https://pastebin.ubuntu.com/p/fqK6Cx3SKK/
+ you can check memory leak with this script
  
  [Regression]
- Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
- For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.
+ Restarting daemon after upgrading this pkg will be needed. this patch adds 
free for non-freed dynamic allocated memory. so it solves memory leak. 
  
  [Others]
  
- Related commits.
+ this patch is from my self with testing.
  
- [1] commit a7b61e276120184c7586a3217ed3571a982f5017
- Author: Andrew Beekhof 
- Date:   Fri Aug 23 16:25:35 2013 +1000
- 
- Refactor: attrd: Move to its own directory and create a stub for
- attrd-ng
- 
- --
- $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
- Pacemaker-1.1.11-rc3
- 
- $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
- Pacemaker-1.1.11-rc1~168
- 
- $ rmadison pacemaker
-  pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
-  pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
-  pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates
- 
-  pacemaker | 1.1.14-2ubuntu1   | xenial
-  pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
-  pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
-  pacemaker | 1.1.16-1ubuntu1   | zesty
-  pacemaker | 1.1.16-1ubuntu1   | artful
-  pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
- --
- 
- For glib
- [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
- [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
- [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
- [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a
+ Please review carefully if it is ok.
  
  [Original Description]
  
  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.
  
  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused by
  the g_dbus API, the use of which was removed in Pacemaker 1.11.
  
  I've also attached the Valgrind output from the run that exposed the
  issue.
  
  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).
  
  If not, can you advise which version of the OS will be the first to take
  1.11 please?

** Description changed:

  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty
  
  affected to pacemaker 1.1.10.
- affected to glib2.0 2.40.2-0ubuntu1 >> for glib2.0 created new lp [3]
+ affected to glib2.0 2.40.2-0ubuntu1 >> for glib2.0 created new lp [1]
  
  Please note that patch for pacemaker is created myself.
  
  [Test Case]
  
  https://pastebin.ubuntu.com/p/fqK6Cx3SKK/
  you can check memory leak with this script
  
  [Regression]
- Restarting daemon after upgrading this pkg will be needed. this patch adds 
free for non-freed dynamic allocated memory. so it solves memory leak. 
+ Restarting daemon after upgrading this pkg will be needed. this patch adds 
free for non-freed dynamic allocated memory. so it solves memory leak.
  
  [Others]
  
  this patch is from my self with testing.
  
  Please review carefully if it is ok.
+ 
+ [1] https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741
  
  [Original Description]
  
  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.
  
  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused by
  the g_dbus API, the use of which was removed in Pacemaker 1.11.
  
  I've also attached the Valgrind 

[Touch-packages] [Bug 1750741] Re: Memory leak in g_dbus_proxy_new_for_bus_sync()

[Seyeong Kim]

** Patch added: "lp1750741_trusty_glib2.0.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741/+attachment/5059468/+files/lp1750741_trusty_glib2.0.debdiff

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

Title:
  Memory leak in g_dbus_proxy_new_for_bus_sync()

Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  This issue is found while debugging pacemaker lrmd memory leak

  glib2.0 gio function g_dbus_proxy_new_for_bus_sync has leak as [1]
  said

  this is affected to Trusty

  [Test Case]

  https://pastebin.ubuntu.com/p/fqK6Cx3SKK/
  you can check memory leak with this script

  [Regression]
  This patch is affected to library pkg. so related daemon should be restarted 
after patching. patch itself is very simple and old. it seems verified for few 
years.

  [Others]

  original commit

  
https://gitlab.gnome.org/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741/+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 1750741] [NEW] Memory leak in g_dbus_proxy_new_for_bus_sync()

[Seyeong Kim]

Public bug reported:

[Impact]

This issue is found while debugging pacemaker lrmd memory leak

glib2.0 gio function g_dbus_proxy_new_for_bus_sync has leak as [1] said

this is affected to Trusty

[Test Case]

https://pastebin.ubuntu.com/p/fqK6Cx3SKK/
you can check memory leak with this script

[Regression]
This patch is affected to library pkg. so related daemon should be restarted 
after patching. patch itself is very simple and old. it seems verified for few 
years.

[Others]

original commit

https://gitlab.gnome.org/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: Fix Released


** Tags: sts sts-sru-needed

** Tags added: sts sts-sru-needed

** Also affects: glib2.0 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: pacemaker (Ubuntu)

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Memory leak in g_dbus_proxy_new_for_bus_sync()

Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  This issue is found while debugging pacemaker lrmd memory leak

  glib2.0 gio function g_dbus_proxy_new_for_bus_sync has leak as [1]
  said

  this is affected to Trusty

  [Test Case]

  https://pastebin.ubuntu.com/p/fqK6Cx3SKK/
  you can check memory leak with this script

  [Regression]
  This patch is affected to library pkg. so related daemon should be restarted 
after patching. patch itself is very simple and old. it seems verified for few 
years.

  [Others]

  original commit

  
https://gitlab.gnome.org/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741/+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 1747354] Re: Update bluez to version 5.48 in bionic

[Daniel van Vugt]

** Attachment added: "bluez_5.48-0ubuntu3.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+attachment/5059466/+files/bluez_5.48-0ubuntu3.dsc

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1747354] Re: Update bluez to version 5.48 in bionic

[Daniel van Vugt]

Updated to version 5.48-0ubuntu3 to fix bug 1750308.

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1747354] Re: Update bluez to version 5.48 in bionic

[Daniel van Vugt]

** Attachment added: "bluez_5.48-0ubuntu3.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+attachment/5059465/+files/bluez_5.48-0ubuntu3.debian.tar.xz

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1747354] Re: Update bluez to version 5.48 in bionic

[Daniel van Vugt]

** Patch added: "bluez_5.48-0ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+attachment/5059464/+files/bluez_5.48-0ubuntu3.debdiff

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1750308] Re: python-dbusmock: FAIL: test_one_adapter (__main__.TestBlueZ5)

[Daniel van Vugt]

https://git.launchpad.net/~bluetooth/bluez/commit/?id=c09f8f6d3e853fed7499a986e967cc4d8c96d344


** Changed in: bluez (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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1750308

Title:
  python-dbusmock: FAIL: test_one_adapter (__main__.TestBlueZ5)

Status in Bluez Utilities:
  Unknown
Status in bluez package in Ubuntu:
  Fix Committed
Status in python-dbusmock package in Ubuntu:
  Invalid

Bug description:
  When bluez 5.48 is installed, we see this failure:

  ==
  FAIL: test_one_adapter (__main__.TestBlueZ5)
  --
  Traceback (most recent call last):
File "test_bluez5.py", line 128, in test_one_adapter
  self.assertIn('Controller ' + address, out)
  AssertionError: 'Controller 00:01:02:03:04:05' not found in ['Waiting to 
connect to bluetoothd...', '[\x1b[0;92mNEW\x1b[0m] Controller 00:01:02:03:04:05 
my-computer [default]', '[SIGNAL] org.freedesktop.DBus.Mock.MethodCalled', 
'Agent registered', 'Controller 00:01:02:03:04:05 my-computer [default]', 
'Agent unregistered', '[\x1b[0;91mDEL\x1b[0m] Controller 00:01:02:03:04:05 
my-computer [default]']

  --

  However the failure only occurs in the Ubuntu package of python-
  dbusmock. It does not occur with the upstream git repo (run as 'tests
  /run-ubuntu-chroot').

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python-dbusmock 0.17-1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Mon Feb 19 11:42:48 2018
  InstallationDate: Installed on 2017-12-12 (68 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  PackageArchitecture: all
  SourcePackage: python-dbusmock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1750308/+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 1747354] Re: Update bluez to version 5.48 in bionic

[Daniel van Vugt]

** Attachment removed: "bluez_5.48-0ubuntu2.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+attachment/5049024/+files/bluez_5.48-0ubuntu2.debian.tar.xz

** Attachment removed: "bluez_5.48-0ubuntu2.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+attachment/5049025/+files/bluez_5.48-0ubuntu2.dsc

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1750308] Re: FAIL: test_one_adapter (__main__.TestBlueZ5)

[Daniel van Vugt]

** Changed in: python-dbusmock (Ubuntu)
   Status: In Progress => Invalid

** Changed in: python-dbusmock (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

** Summary changed:

- FAIL: test_one_adapter (__main__.TestBlueZ5)
+ python-dbusmock: FAIL: test_one_adapter (__main__.TestBlueZ5)

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

Title:
  python-dbusmock: FAIL: test_one_adapter (__main__.TestBlueZ5)

Status in Bluez Utilities:
  Unknown
Status in bluez package in Ubuntu:
  In Progress
Status in python-dbusmock package in Ubuntu:
  Invalid

Bug description:
  When bluez 5.48 is installed, we see this failure:

  ==
  FAIL: test_one_adapter (__main__.TestBlueZ5)
  --
  Traceback (most recent call last):
File "test_bluez5.py", line 128, in test_one_adapter
  self.assertIn('Controller ' + address, out)
  AssertionError: 'Controller 00:01:02:03:04:05' not found in ['Waiting to 
connect to bluetoothd...', '[\x1b[0;92mNEW\x1b[0m] Controller 00:01:02:03:04:05 
my-computer [default]', '[SIGNAL] org.freedesktop.DBus.Mock.MethodCalled', 
'Agent registered', 'Controller 00:01:02:03:04:05 my-computer [default]', 
'Agent unregistered', '[\x1b[0;91mDEL\x1b[0m] Controller 00:01:02:03:04:05 
my-computer [default]']

  --

  However the failure only occurs in the Ubuntu package of python-
  dbusmock. It does not occur with the upstream git repo (run as 'tests
  /run-ubuntu-chroot').

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python-dbusmock 0.17-1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Mon Feb 19 11:42:48 2018
  InstallationDate: Installed on 2017-12-12 (68 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  PackageArchitecture: all
  SourcePackage: python-dbusmock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1750308/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Yovan Zhuo Jiawan]

Although a month has passed since 17 Jan 2018, this compiz segfault
surface up today on 21 February 12:20 pm GMT +8 on my lenovo T400. I am
sorry if i have necroposted now, but this bug is annoying and i seek all
of your kind assistance.

Details are:

$sudo lshw -c video
 *-display   
   description: VGA compatible controller
   product: RV620/M82 [Mobility Radeon HD 3450/3470]
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@:01:00.0
   version: 00
   width: 32 bits
   clock: 33MHz
   capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
   configuration: driver=radeon latency=0
   resources: irq:30 memory:d000-dfff ioport:2000(size=256) 
memory:cfff-cfff memory:cff0-cff1

$lsb_release -a 
LSB Version:
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

$apt policy xserver-xorg-core
xserver-xorg-core:
  Installed: 2:1.18.4-0ubuntu0.7
  Candidate: 2:1.18.4-0ubuntu0.7
  Version table:
 *** 2:1.18.4-0ubuntu0.7 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages
100 /var/lib/dpkg/status
 2:1.18.3-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

$apt policy libgl1-mesa-dri
libgl1-mesa-dri:
  Installed: 17.2.8-0ubuntu0~16.04.1
  Candidate: 17.2.8-0ubuntu0~16.04.1
  Version table:
 *** 17.2.8-0ubuntu0~16.04.1 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 11.2.0-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

$dmesg | grep compiz
compiz: segfault at 38 ip 7f98dd4ac240 sp 7ffc01ba0410 error 4 in 
libmove.so[7f98dd4a1000+15000]

>From what i have read above about ppa purge and adding ppa/proposed,
does it still apply to my system?

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1750717] Re: package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  sshd issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.4
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Feb 20 06:34:34 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-07-25 (210 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.ssh.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1750717/+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 1750717] [NEW] package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[mahendra s]

Public bug reported:

sshd issue

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.4
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Tue Feb 20 06:34:34 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-07-25 (210 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: openssh
Title: package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.ssh.conf: [deleted]

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


** Tags: amd64 apport-package xenial

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  sshd issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.4
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Feb 20 06:34:34 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-07-25 (210 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.ssh.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1750717/+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 1750625] Re: update misinterprets 304 response on Packages.gz

[robocoder]

** Attachment added: "Minimal /dists folder for testing"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1750625/+attachment/5059382/+files/freight.tar.gz

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

Title:
  update misinterprets 304 response on Packages.gz

Status in apt package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ii  apt  1.2.24   
   amd64commandline package manager
  ii  apt-transport-https  1.2.24   
   amd64https download transport for APT
  ii  apt-utils1.2.24   
   amd64package management related utility programs
  ii  libapt-inst2.0:amd64 1.2.24   
   amd64deb package format runtime library
  ii  libapt-pkg5.0:amd64  1.2.24   
   amd64package management runtime library

  Expected behaviour:

  If apt-get gets a 304 Not Modified when requesting Packages.gz, it
  should ignore the package list (i.e., there's no update).

  Observed behaviour:

  Added a local repository to
  /etc/apt/sources.list.d/instafreight_php.list:

  > deb [arch=amd64 trusted=yes] http://ubuntu/instafreight xenial php

  The first time running apt-get update succeeds; in addition,
  apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:01:39 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 200
  745 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  I am able to install packages from that repo without error.

  Running apt-get a 2nd time succeeds. apache.log doesn't show a request
  for Packages.gz

  Running apt-get a 3rd time, apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:04:45 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 304
  124 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  However, on the console where I ran apt-get, the corresponding output
  is:

  > Err:15 http://ubuntu/instafreight xenial/php amd64 Packages
  >   404  Not Found
  > ...
  > E: Failed to fetch 
http://ubuntu/instafreight/dists/xenial/php/binary-amd64/Packages.gz  404  Not 
Found
  > E: Some index files failed to download. They have been ignored, or old ones 
used instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1750625/+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 1746807] Re: 18.04 daily installer fails missing kernel

[Simon Quigley]

\o/

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

Title:
  18.04 daily installer fails missing kernel

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  "No installable kernel was found in the defined APT sources.

  You may try to continue without a kernel, and manually install your own 
kernel later.
  This is only recommended for experts, otherwise you will likely end up with a 
machine
  that doesn't boot.

  Continue without installing a kernel."

  Lubuntu Daily 18.04 dated 2018-February 1.

  note: yesterdays (Jan 31) install works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1746807/+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 1746807] Re: 18.04 daily installer fails missing kernel

[Jb]

Lubuntu Alternate 20180220 = works

Looks good! :)

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

Title:
  18.04 daily installer fails missing kernel

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  "No installable kernel was found in the defined APT sources.

  You may try to continue without a kernel, and manually install your own 
kernel later.
  This is only recommended for experts, otherwise you will likely end up with a 
machine
  that doesn't boot.

  Continue without installing a kernel."

  Lubuntu Daily 18.04 dated 2018-February 1.

  note: yesterdays (Jan 31) install works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1746807/+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 1749472] Re: mesa 18.0.0 will cause rendering errors in Qt applications

[Simon Quigley]

block-proposed still belongs for mesa, having it blocked for other
reasons isn't good enough because this bug will break the Kubuntu and
Lubuntu Next desktops.

** No longer affects: qtbase-opensource-src (Ubuntu Bionic)

** No longer affects: qtbase-opensource-src (Ubuntu)

** Tags added: block-proposed

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

Title:
  mesa 18.0.0 will cause rendering errors in Qt applications

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Bionic:
  New

Bug description:
  From: https://bugreports.qt.io/browse/QTBUG-66348

  ** extract **

  The `QOpenGLShaderProgram` class in Qt can be used to compile and link
  OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is
  available, it can cache those shaders on disk
  (~/.cache/qtshadercache). The i965 driver in Mesa supports this
  extension since version 18.0.0.

  When the shader is loaded using the `glProgramBinary` function, OpenGL
  can refuse it if for example some hardware or software component
  changed. Mesa refuses binaries that were created by any other build of
  Mesa (using among other things the build_id of the library).

  If the shader is refused, Qt should fallback to compiling it from
  sources, but it incorrectly calls glLinkProgram first. The
  glLinkProgram succeeds, because it actually links 0 shaders together.
  That is allowed in OpenGL compatibility profile and the resulting
  program works as a fixed pipeline. Which of course does not render as
  expected.

  This causes rendering errors in Qt applications every time Mesa is
  updated since version 18.0.0. For example white screen in sddm.

  This issue was originally reported in openSUSE
  (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578).

  ** end extract **

  As this potentially effects Qt applications, and could even render
  display manager login unusable, this should be a blocking bug in mesa
  and Qt until Qt mitigations patches pass codereview and can be
  included in Qtbase for 18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749472/+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 1750697] [NEW] package systemd 237-3ubuntu2 failed to install/upgrade: hi ha un bucle d'activadors, s'ha abandonat

[franz666es]

Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu2
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: Mon Feb 19 19:56:38 2018
ErrorMessage: hi ha un bucle d'activadors, s'ha abandonat
InstallationDate: Installed on 2018-01-07 (44 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
MachineType: ASUSTeK COMPUTER INC. X550CL
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=672ecde1-6dcc-440c-9577-518064d2bff2 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.6~alpha7ubuntu2
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 2 overridden configuration files found.
Title: package systemd 237-3ubuntu2 failed to install/upgrade: hi ha un bucle 
d'activadors, s'ha abandonat
UpgradeStatus: Upgraded to bionic on 2018-02-19 (1 days ago)
dmi.bios.date: 07/10/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550CL.207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550CL
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CL.207:bd07/10/2014:svnASUSTeKCOMPUTERINC.:pnX550CL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X550CL
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-package bionic

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

Title:
  package systemd 237-3ubuntu2 failed to install/upgrade: hi ha un bucle
  d'activadors, s'ha abandonat

Status in systemd package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu2
  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: Mon Feb 19 19:56:38 2018
  ErrorMessage: hi ha un bucle d'activadors, s'ha abandonat
  InstallationDate: Installed on 2018-01-07 (44 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: ASUSTeK COMPUTER INC. X550CL
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=672ecde1-6dcc-440c-9577-518064d2bff2 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.6~alpha7ubuntu2
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 237-3ubuntu2 failed to install/upgrade: hi ha un bucle 
d'activadors, s'ha abandonat
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (1 days ago)
  dmi.bios.date: 07/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CL.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CL
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CL.207:bd07/10/2014:svnASUSTeKCOMPUTERINC.:pnX550CL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550CL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750697/+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 1748652] Re: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Apport retracing service]

*** This bug is a duplicate of bug 1725628 ***
https://bugs.launchpad.net/bugs/1725628

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1725628, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1725628
   package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1

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

Title:
  package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  New

Bug description:
  Since this version of ubuntu, i am really not happy, a lot of bug...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.5
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Feb 10 13:40:45 2018
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-05-21 (630 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-09-28 (499 days ago)
  VisudoCheck:
   /etc/sudoers : analyse grammaticale réussie
   /etc/sudoers.d/README : analyse grammaticale réussie

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1748652/+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 1644975] Re: Resume from disk (swapfile) fails

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.130ubuntu3

---
initramfs-tools (0.130ubuntu3) bionic; urgency=medium

  * Fix resuming a hibernate session from a swapfile (LP: #1644975)

 -- Mario Limonciello   Tue, 20 Feb 2018
15:34:46 -0600

** Changed in: initramfs-tools (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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1644975

Title:
  Resume from disk (swapfile) fails

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+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 1725628] Re: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  Remove A software to see this bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.5
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   gksu: Remove
   ubuntu-minimal: Remove
   sudo: Remove
   y-ppa-manager: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Oct 21 15:16:12 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-10-16 (4 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1725628/+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 1748500] Re: package libdrm-intel1:amd64 2.4.83-1~16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libdrm-intel1:amd64 2.4.83-1~16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libdrm package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libdrm-intel1:amd64 2.4.83-1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog: [  OK  ] Started LSB: Speech Dispatcher.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Feb  9 15:35:42 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgHistoryLog:
   Start-Date: 2018-02-09  15:35:37
   Commandline: apt-get -f install
   Requested-By: saurabh (1000)
   Upgrade: libc6:amd64 (2.23-0ubuntu9, 2.23-0ubuntu10)
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0782]
 Subsystem: Dell GM108M [GeForce 940MX] [1028:0782]
  InstallationDate: Installed on 2017-07-22 (202 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.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 0c45:6a05 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed 
root=UUID=729ec207-e355-4551-92bc-3dba92f4b65f ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: libdrm
  Title: package libdrm-intel1:amd64 2.4.83-1~16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 07PJP0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd09/11/2017:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn07PJP0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 7560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Feb  9 17:33:56 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5600 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1748500/+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 1748652] Re: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Seth Arnold]

*** This bug is a duplicate of bug 1725628 ***
https://bugs.launchpad.net/bugs/1725628

I see in the logs that 'yum' is installed. Did you perchance try to use
yum to install software that isn't built for Ubuntu?

Thanks

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

Title:
  package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  New

Bug description:
  Since this version of ubuntu, i am really not happy, a lot of bug...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.5
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Feb 10 13:40:45 2018
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-05-21 (630 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-09-28 (499 days ago)
  VisudoCheck:
   /etc/sudoers : analyse grammaticale réussie
   /etc/sudoers.d/README : analyse grammaticale réussie

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1748652/+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 1748500] Re: package libdrm-intel1:amd64 2.4.83-1~16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

[Seth Arnold]

Hello, this machine is spewing Machine Check Events. I strongly
recommend installing the mcelog tool and keeping a very close eye on the
/var/log/mcelog file. This might represent hardware issues. (Perhaps as
simple as a clogged heatsink, perhaps failing hardware.)

Thanks

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

Title:
  package libdrm-intel1:amd64 2.4.83-1~16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libdrm package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libdrm-intel1:amd64 2.4.83-1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog: [  OK  ] Started LSB: Speech Dispatcher.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Feb  9 15:35:42 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgHistoryLog:
   Start-Date: 2018-02-09  15:35:37
   Commandline: apt-get -f install
   Requested-By: saurabh (1000)
   Upgrade: libc6:amd64 (2.23-0ubuntu9, 2.23-0ubuntu10)
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0782]
 Subsystem: Dell GM108M [GeForce 940MX] [1028:0782]
  InstallationDate: Installed on 2017-07-22 (202 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.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 0c45:6a05 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed 
root=UUID=729ec207-e355-4551-92bc-3dba92f4b65f ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: libdrm
  Title: package libdrm-intel1:amd64 2.4.83-1~16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 07PJP0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd09/11/2017:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn07PJP0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 7560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Feb  9 17:33:56 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5600 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1748500/+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 1748652] Re: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Seth Arnold]

*** This bug is a duplicate of bug 1725628 ***
https://bugs.launchpad.net/bugs/1725628

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  New

Bug description:
  Since this version of ubuntu, i am really not happy, a lot of bug...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.5
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Feb 10 13:40:45 2018
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-05-21 (630 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-09-28 (499 days ago)
  VisudoCheck:
   /etc/sudoers : analyse grammaticale réussie
   /etc/sudoers.d/README : analyse grammaticale réussie

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1748652/+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 1748063] Re: package clamav-base 0.99.3+addedllvm-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package clamav-base 0.99.3+addedllvm-0ubuntu0.14.04.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 128

Status in clamav package in Ubuntu:
  New
Status in debconf package in Ubuntu:
  New

Bug description:
  My computer used to continually freeze after about thirty (30) seconds
  or so such that neither my mouse nor my keyboard worked because they
  froze, which required me to repeatedly restart my computer, but not
  first without disconnecting my computer from its internet connection,
  given that my understanding is and/or was that there are or were
  security problems in permitting the grub loader to be seen and,
  therefore, its key to be read by eavesdropper(s) on the other end of
  the internet cable.  Nevertheless, it also appears, after having
  reviewed my computer's files and folder that criminal hacker(s) have
  and continue to attempt to infiltrate my computer by means of two (2)
  known files, Namely, .pki and .esd_auth .  Given that my computer was
  hacked a day or two ago, thereby rendering it useless to the point of
  my computer being unable to boot, I assert and maintain that these
  vulnerabilities ought to be addressed to prevent further security
  breaches in an otherwise excellent operating system.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: clamav-base 0.99.3+addedllvm-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.2.0-121.164-generic-pae 3.2.79
  Uname: Linux 3.2.0-121-generic-pae i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Wed Feb  7 20:46:24 2018
  DuplicateSignature: 
package:clamav-base:0.99.3+addedllvm-0ubuntu0.14.04.1:subprocess installed 
post-installation script returned error exit status 128
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-02-16 (356 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  PackageArchitecture: all
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-121-generic-pae 
root=UUID=120b07c7-e971-4a45-bc46-a15f8eefc5e1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: clamav
  Title: package clamav-base 0.99.3+addedllvm-0ubuntu0.14.04.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 128
  UpgradeStatus: Upgraded to trusty on 2017-07-29 (194 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1748063/+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 1748063] Re: package clamav-base 0.99.3+addedllvm-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

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

Title:
  package clamav-base 0.99.3+addedllvm-0ubuntu0.14.04.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 128

Status in clamav package in Ubuntu:
  New
Status in debconf package in Ubuntu:
  New

Bug description:
  My computer used to continually freeze after about thirty (30) seconds
  or so such that neither my mouse nor my keyboard worked because they
  froze, which required me to repeatedly restart my computer, but not
  first without disconnecting my computer from its internet connection,
  given that my understanding is and/or was that there are or were
  security problems in permitting the grub loader to be seen and,
  therefore, its key to be read by eavesdropper(s) on the other end of
  the internet cable.  Nevertheless, it also appears, after having
  reviewed my computer's files and folder that criminal hacker(s) have
  and continue to attempt to infiltrate my computer by means of two (2)
  known files, Namely, .pki and .esd_auth .  Given that my computer was
  hacked a day or two ago, thereby rendering it useless to the point of
  my computer being unable to boot, I assert and maintain that these
  vulnerabilities ought to be addressed to prevent further security
  breaches in an otherwise excellent operating system.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: clamav-base 0.99.3+addedllvm-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.2.0-121.164-generic-pae 3.2.79
  Uname: Linux 3.2.0-121-generic-pae i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Wed Feb  7 20:46:24 2018
  DuplicateSignature: 
package:clamav-base:0.99.3+addedllvm-0ubuntu0.14.04.1:subprocess installed 
post-installation script returned error exit status 128
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-02-16 (356 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  PackageArchitecture: all
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-121-generic-pae 
root=UUID=120b07c7-e971-4a45-bc46-a15f8eefc5e1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: clamav
  Title: package clamav-base 0.99.3+addedllvm-0ubuntu0.14.04.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 128
  UpgradeStatus: Upgraded to trusty on 2017-07-29 (194 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1748063/+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 1644975] Re: Resume from disk (swapfile) fails

[Mario Limonciello]

** Bug watch added: Debian Bug tracker #890950
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890950

** Changed in: initramfs-tools (Debian)
   Importance: Undecided => Unknown

** Changed in: initramfs-tools (Debian)
   Status: New => Unknown

** Changed in: initramfs-tools (Debian)
 Remote watch: None => Debian Bug tracker #890950

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

Title:
  Resume from disk (swapfile) fails

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+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 1542471] Re: Playing mp3 files causes: Problem occurred without error being set. This is a bug in Rhythmbox or GStreamer.

[fermulator]

(had this tab open in a really old browser session ... doing some clean
up ...)

retested on Fedora 26, it works! (bug no longer present)

{{{
$ sudo zfs list | grep music
zstorage/music 7.40G  84.9G  7.40G  /zstorage/music
}}}

rhythmbox opens, music library on that pool, music plays

{{{
4.14.14-200.fc26.x86_64, zfs-0.7.5-1.fc26.x86_64, rhythmbox-3.4.1-3.fc26.x86_64
}}}

** Attachment added: "rbox_zfs_pool_source.png"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1542471/+attachment/5059243/+files/rbox_zfs_pool_source.png

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

Title:
  Playing mp3 files causes: Problem occurred without error being set.
  This is a bug in Rhythmbox or GStreamer.

Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  I get the following error in the console when trying to play a mp3
  file using Rhythmbox:

  (21:23:27) [0x832a60] [rb_shell_player_error] rb-shell-player.c:2443:
  playback error while playing: Problem occurred without error being
  set. This is a bug in Rhythmbox or GStreamer.

  I don't get the same error while trying to play the same file using
  'Video's. I installed the required codec using the 'Video's
  application as it told me to install a codec.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.7.1-1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  5 21:24:05 2016
  ExecutablePath: /usr/bin/rhythmbox
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1542471/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[David Britton]

@xnox: not as of yet, no.  it's still in our backlog.

** Changed in: landscape-client (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: landscape-client (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  Used Landscape (Paid Canonical Subscription) to upgrade one of my
  machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1644975] Re: Resume from disk (swapfile) fails

[Mario Limonciello]

Thanks for those of you who added the various patches for this.  I've
updated them relative to 0.130 and i'm uploading them to bionic.

I've also submitted a bug to Debian with the patch for this (but I
haven't gotten the BTS email yet).


** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Mario Limonciello (superm1)

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

Title:
  Resume from disk (swapfile) fails

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools package in Debian:
  New

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+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 1750654] [NEW] "lxc-create -B best" fails on non-btrfs/zfs system

[Martin Pitt]

Public bug reported:

As per documentation, the `-B best` option should automatically select
the best backingstore, falling back all the way to dir.

But apparently it doesn't, at least not in artful's 2.1.0-0ubuntu1:

$ sudo lxc-create -B best --name=autopkgtest-xenial -t ubuntu -- -r xenial
lxc-create: autopkgtest-xenial: storage/btrfs.c: btrfs_create: 860 
Inappropriate ioctl for device - Failed to create btrfs subvolume 
"/var/lib/lxc/autopkgtest-xenial/rootfs"
lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_create: 758 Failed to create 
zfs dataset "zfs:lxc/autopkgtest-xenial": lxc-create: autopkgtest-xenial: 
utils.c: run_command: 2326 failed to exec command
lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_mount: 256 No such file or 
directory - Failed to mount "lxc/autopkgtest-xenial" on 
"/usr/lib/x86_64-linux-gnu/lxc"
lxc-create: autopkgtest-xenial: lxccontainer.c: create_run_template: 1294 
Failed to mount rootfs
lxc-create: autopkgtest-xenial: lxccontainer.c: create_run_template: 1473 
container creation template for autopkgtest-xenial failed
lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_destroy: 613 Failed to 
detect zfs dataset "lxc/autopkgtest-xenial": lxc-create: autopkgtest-xenial:
lxc-create: autopkgtest-xenial: lxccontainer.c: container_destroy: 2653 Error 
destroying rootfs for autopkgtest-xenial
lxc-create: autopkgtest-xenial: tools/lxc_create.c: main: 326 Error creating 
container autopkgtest-xenial

Moreover, it creates cruft which is hard to clean up again:

$ sudo lxc-ls -f
NAME   STATE   AUTOSTART GROUPS IPV4 IPV6 
autopkgtest-xenial STOPPED 0 -  --

$ sudo lxc-destroy -n autopkgtest-xenial
lxc-destroy: autopkgtest-xenial: storage/zfs.c: zfs_destroy: 613 Failed to 
detect zfs dataset "lxc/autopkgtest-xenial": lxc-destroy: autopkgtest-xenial: 
utils.c: run_command: 2326 failed to exec command
lxc-destroy: autopkgtest-xenial: lxccontainer.c: container_destroy: 2653 Error 
destroying rootfs for autopkgtest-xenial
Destroying autopkgtest-xenial failed

$ sudo ls -lR /var/lib/lxc/autopkgtest-xenial
/var/lib/lxc/autopkgtest-xenial:
total 8
-rw-r--r-- 1 root root  149 Feb 20 20:41 config
drwxr-xr-x 2 root root 4096 Feb 20 20:41 rootfs

/var/lib/lxc/autopkgtest-xenial/rootfs:
total 0

This can only be cleaned up with `sudo rm -r`.

autopkgtest-build-lxc uses this option to get performant containers out
of the box. Arguably `-B best` is a sort of "unbreak my containers"
option and should always implicitly be used, but is there something else
that I should do here?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: lxc 2.1.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Tue Feb 20 20:38:55 2018
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
PackageArchitecture: all
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
 lxc.net.0.type = veth
 lxc.net.0.link = lxcbr0
 lxc.net.0.flags = up
 lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx
lxcsyslog:

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


** Tags: amd64 apparmor apport-bug artful

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

Title:
  "lxc-create -B best" fails on non-btrfs/zfs system

Status in lxc package in Ubuntu:
  New

Bug description:
  As per documentation, the `-B best` option should automatically select
  the best backingstore, falling back all the way to dir.

  But apparently it doesn't, at least not in artful's 2.1.0-0ubuntu1:

  $ sudo lxc-create -B best --name=autopkgtest-xenial -t ubuntu -- -r xenial
  lxc-create: autopkgtest-xenial: storage/btrfs.c: btrfs_create: 860 
Inappropriate ioctl for device - Failed to create btrfs subvolume 
"/var/lib/lxc/autopkgtest-xenial/rootfs"
  lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_create: 758 Failed to 
create zfs dataset "zfs:lxc/autopkgtest-xenial": lxc-create: 
autopkgtest-xenial: utils.c: run_command: 2326 failed to exec command
  lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_mount: 256 No such file or 
directory - Failed to mount "lxc/autopkgtest-xenial" on 
"/usr/lib/x86_64-linux-gnu/lxc"
  lxc-create: autopkgtest-xenial: lxccontainer.c: create_run_template: 1294 
Failed to mount rootfs
  lxc-create: autopkgtest-xenial: lxccontainer.c: create_run_template: 1473 
container creation template for autopkgtest-xenial failed
  lxc-create: autopkgtest-xenial: 

[Touch-packages] [Bug 1734586] Re: Merge NetworkManager with Debian 1.10.0-1

[Sebastien Bacher]

the python-dbusmock fix has been commited upstream, now the n-m one
needs to be resolved

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

Title:
  Merge NetworkManager with Debian 1.10.0-1

Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  Debian has packaged the latest major release of NetworkManager, 1.10.
  We should update to this version for Ubuntu 18.04 "bionic".

  I have prepared the merge at
  https://git.launchpad.net/network-manager?h=bionic

  The only thing missing is that this patch needs to be rebased or dropped:
  
https://git.launchpad.net/network-manager/tree/debian/patches/dns-manager-don-t-merge-split-DNS-search-domains.patch?h=bionic

  Otherwise, the build will fail:

  src/.libs/libNetworkManagerTest.a(src_libNetworkManager_la-nm-dns-manager.o):
  In function `merge_one_ip_config_data':
  ./src/dns/nm-dns-manager.c:417: undefined reference to
  `nm_ip4_config_get_never_default'
  ./src/dns/nm-dns-manager.c:419: undefined reference to
  `nm_ip4_config_get_never_default'

  There's been a lot of refactoring, but this commit looks important:
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=5c29945

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1734586/+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 1750638] Re: Network Manager Can't Interact With Qualcomm Atheros QCA6174 despite WICD working and native kernel support

[Justin]

Marked as confirmed based on several other reports on the internet:

https://askubuntu.com/questions/929027/qualcomm-atheros-qca6174-802
-11ac-wireless-network-adapter-168c003e-rev-32

https://ubuntuforums.org/showthread.php?t=2323812

etc

Fun update:
Bluetooth from the same card works perfectly fine once airplane mode is 
disabled.

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

Title:
   Network Manager Can't Interact With Qualcomm Atheros QCA6174 despite
  WICD working and native kernel support

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This fails in a similar manner from 16.04 to 18.04, in both gnome and
  unity where applicable. Details of failure in 18.04:

  System always boots in airplane mode, no matter what. When you disable
  it and go to turn the wifi on in system settings, it hangs while doing
  so, but sometimes works and shows wifi, though it usually doesn't. I
  can't reproduce the cause of success of failure, but the wifi settings
  menu does immediately stop updating new networks after this point no
  matter what. The wifi menu in the top right never works at all.

  How I know it's not a hardware issue:
  It works in windows
  It works in WICD
  People say it works in other distros
  It shows up under lshw -C network as expected

  How I know it's not a firmware issue:
  It works in other distros
  It works in WICD

  How I know it's not a driver issue:
  It's natively supported in the kernel after an open source driver that worked 
for everyone was merged (which no one could get properly with Ubuntu's network 
manager)
  It shows up under lshw -C network as expected
  It works with WICD

  This is the default wifi card for a ton of new Lenovo laptops, so this
  is actually a serious issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1750638/+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 1750638] [NEW] Network Manager Can't Interact With Qualcomm Atheros QCA6174 despite WICD working and native kernel support

[Justin]

Public bug reported:

This fails in a similar manner from 16.04 to 18.04, in both gnome and
unity where applicable. Details of failure in 18.04:

System always boots in airplane mode, no matter what. When you disable
it and go to turn the wifi on in system settings, it hangs while doing
so, but sometimes works and shows wifi, though it usually doesn't. I
can't reproduce the cause of success of failure, but the wifi settings
menu does immediately stop updating new networks after this point no
matter what. The wifi menu in the top right never works at all.

How I know it's not a hardware issue:
It works in windows
It works in WICD
People say it works in other distros
It shows up under lshw -C network as expected

How I know it's not a firmware issue:
It works in other distros
It works in WICD

How I know it's not a driver issue:
It's natively supported in the kernel after an open source driver that worked 
for everyone was merged (which no one could get properly with Ubuntu's network 
manager)
It shows up under lshw -C network as expected
It works with WICD

This is the default wifi card for a ton of new Lenovo laptops, so this
is actually a serious issue.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
   Network Manager Can't Interact With Qualcomm Atheros QCA6174 despite
  WICD working and native kernel support

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This fails in a similar manner from 16.04 to 18.04, in both gnome and
  unity where applicable. Details of failure in 18.04:

  System always boots in airplane mode, no matter what. When you disable
  it and go to turn the wifi on in system settings, it hangs while doing
  so, but sometimes works and shows wifi, though it usually doesn't. I
  can't reproduce the cause of success of failure, but the wifi settings
  menu does immediately stop updating new networks after this point no
  matter what. The wifi menu in the top right never works at all.

  How I know it's not a hardware issue:
  It works in windows
  It works in WICD
  People say it works in other distros
  It shows up under lshw -C network as expected

  How I know it's not a firmware issue:
  It works in other distros
  It works in WICD

  How I know it's not a driver issue:
  It's natively supported in the kernel after an open source driver that worked 
for everyone was merged (which no one could get properly with Ubuntu's network 
manager)
  It shows up under lshw -C network as expected
  It works with WICD

  This is the default wifi card for a ton of new Lenovo laptops, so this
  is actually a serious issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1750638/+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 1724152] Re: ISST-LTE: pVM: aureport couldn't get the right auid from the audit log on ubuntu16.04

[Launchpad Bug Tracker]

This bug was fixed in the package audit - 1:2.4.5-1ubuntu2.1

---
audit (1:2.4.5-1ubuntu2.1) xenial; urgency=medium

  * debian/patches/02-print-loginuid-in-login-report.patch: Display the
loginuid when using aureport to display a login report (LP: #1724152)

 -- Tyler Hicks   Tue, 17 Oct 2017 20:03:34 +

** Changed in: audit (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 audit in Ubuntu.
https://bugs.launchpad.net/bugs/1724152

Title:
  ISST-LTE: pVM: aureport couldn't get the right auid from the audit log
  on ubuntu16.04

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in audit package in Ubuntu:
  Invalid
Status in audit source package in Xenial:
  Fix Released
Status in audit source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

  The aureport command, part of the audit userspace utilities,
  incorrectly reports the user id of successful logins. "-1" is printed
  instead of the expected user id.

  [Test Case]

  As root, run `login`. Proceed as follows:

  1. Login with a blank username and any password
  2. Login with an invalid username and any password
  3. Login with a valid username and an invalid password
  4. Login with a valid username and a valid password
  5. Exit from the login shell
  6. Run `aureport -l` and examine the last for login records

  An unpatched aureport will print the following:

  
  # date time auid host term exe success event
  
  ...
  2. 10/17/2017 23:45:32 UNKNOWN ? /dev/pts/8 /bin/login no 97
  3. 10/17/2017 23:45:39 UNKNOWN ? /dev/pts/8 /bin/login no 99
  4. 10/17/2017 23:45:45 tyhicks ? /dev/pts/8 /bin/login no 101
  5. 10/17/2017 23:45:49 -1 ? /dev/pts/8 /bin/login yes 107

  A patch aureport will print the correct output:

  Login Report
  
  # date time auid host term exe success event
  
  ...
  2. 10/17/2017 23:52:44 UNKNOWN ? /dev/pts/8 /bin/login no 165
  3. 10/17/2017 23:52:52 UNKNOWN ? /dev/pts/8 /bin/login no 167
  4. 10/17/2017 23:52:58 tyhicks ? /dev/pts/8 /bin/login no 169
  5. 10/17/2017 23:53:02 1000 ? /dev/pts/8 /bin/login yes 175

  Note the "1000" in the auid column on the #5 row. It should *not* be
  "-1".

  [Regression Potential]

  The regression potential is limited due to the change only affecting a
  single line of code, the fix comes from upstream, and that the
  aureport utility is not critical.

  [Original Report]

  == Comment: #0 - Miao Tao Feng  - 2016-11-23 02:46:25 ==
  When we develop new testcase for audit, we found that command "aureport -l" 
print out wrong auid "-1"  on ubuntu16.04  and it should be 1000 according to 
the audit.log.

  The following are details:

  root@roselp2:~# aureport -l

  Login Report
  
  # date time auid host term exe success event
  
  1. 11/23/2016 02:20:12 -1 10.33.24.118 /dev/pts/0 /usr/sbin/sshd yes 18

  The auid "-1" on the above line should be "1000? according to the
  audit.log.

  root@roselp2:~# grep ":18" /var/log/audit/audit.log
  type=USER_LOGIN msg=audit(1479889212.292:18): pid=4177 uid=0 auid=1000 ses=4 
msg='op=login id=1000 exe="/usr/sbin/sshd" hostname=10.33.24.118 
addr=10.33.24.118 terminal=/dev/pts/0 res=success'

  root@roselp2:~# dpkg -s auditd
  Package: auditd
  Status: install ok installed
  Priority: extra
  Section: admin
  Installed-Size: 1051
  Maintainer: Ubuntu Developers 
  Architecture: ppc64el
  Source: audit
  Version: 1:2.4.5-1ubuntu2
  Depends: lsb-base (>= 3.0-6), mawk | gawk, init-system-helpers (>= 1.18~), 
libaudit1 (>= 1:2.4.2), libauparse0 (>= 1:2.3.1), libc6 (>= 2.17)
  Suggests: audispd-plugins

  root@roselp2:~# uname -a
  Linux roselp2 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:38:24 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@roselp2:~# service auditd status
  ? auditd.service - Security Auditing Service
     Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: e
     Active: active (running) since Wed 2016-11-23 02:19:21 CST; 19s ago
   Main PID: 4085 (auditd)
     CGroup: /system.slice/auditd.service
     ??4085 /sbin/auditd -n

  Nov 23 02:19:21 roselp2 auditctl[4086]: enabled 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: failure 1
  Nov 23 02:19:21 roselp2 auditctl[4086]: pid 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: rate_limit 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_limit 320
  Nov 23 02:19:21 roselp2 auditctl[4086]: lost 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_wait_time 15000
  Nov 23 02:19:21 roselp2 

[Touch-packages] [Bug 1724152] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for audit 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 audit in Ubuntu.
https://bugs.launchpad.net/bugs/1724152

Title:
  ISST-LTE: pVM: aureport couldn't get the right auid from the audit log
  on ubuntu16.04

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in audit package in Ubuntu:
  Invalid
Status in audit source package in Xenial:
  Fix Released
Status in audit source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

  The aureport command, part of the audit userspace utilities,
  incorrectly reports the user id of successful logins. "-1" is printed
  instead of the expected user id.

  [Test Case]

  As root, run `login`. Proceed as follows:

  1. Login with a blank username and any password
  2. Login with an invalid username and any password
  3. Login with a valid username and an invalid password
  4. Login with a valid username and a valid password
  5. Exit from the login shell
  6. Run `aureport -l` and examine the last for login records

  An unpatched aureport will print the following:

  
  # date time auid host term exe success event
  
  ...
  2. 10/17/2017 23:45:32 UNKNOWN ? /dev/pts/8 /bin/login no 97
  3. 10/17/2017 23:45:39 UNKNOWN ? /dev/pts/8 /bin/login no 99
  4. 10/17/2017 23:45:45 tyhicks ? /dev/pts/8 /bin/login no 101
  5. 10/17/2017 23:45:49 -1 ? /dev/pts/8 /bin/login yes 107

  A patch aureport will print the correct output:

  Login Report
  
  # date time auid host term exe success event
  
  ...
  2. 10/17/2017 23:52:44 UNKNOWN ? /dev/pts/8 /bin/login no 165
  3. 10/17/2017 23:52:52 UNKNOWN ? /dev/pts/8 /bin/login no 167
  4. 10/17/2017 23:52:58 tyhicks ? /dev/pts/8 /bin/login no 169
  5. 10/17/2017 23:53:02 1000 ? /dev/pts/8 /bin/login yes 175

  Note the "1000" in the auid column on the #5 row. It should *not* be
  "-1".

  [Regression Potential]

  The regression potential is limited due to the change only affecting a
  single line of code, the fix comes from upstream, and that the
  aureport utility is not critical.

  [Original Report]

  == Comment: #0 - Miao Tao Feng  - 2016-11-23 02:46:25 ==
  When we develop new testcase for audit, we found that command "aureport -l" 
print out wrong auid "-1"  on ubuntu16.04  and it should be 1000 according to 
the audit.log.

  The following are details:

  root@roselp2:~# aureport -l

  Login Report
  
  # date time auid host term exe success event
  
  1. 11/23/2016 02:20:12 -1 10.33.24.118 /dev/pts/0 /usr/sbin/sshd yes 18

  The auid "-1" on the above line should be "1000? according to the
  audit.log.

  root@roselp2:~# grep ":18" /var/log/audit/audit.log
  type=USER_LOGIN msg=audit(1479889212.292:18): pid=4177 uid=0 auid=1000 ses=4 
msg='op=login id=1000 exe="/usr/sbin/sshd" hostname=10.33.24.118 
addr=10.33.24.118 terminal=/dev/pts/0 res=success'

  root@roselp2:~# dpkg -s auditd
  Package: auditd
  Status: install ok installed
  Priority: extra
  Section: admin
  Installed-Size: 1051
  Maintainer: Ubuntu Developers 
  Architecture: ppc64el
  Source: audit
  Version: 1:2.4.5-1ubuntu2
  Depends: lsb-base (>= 3.0-6), mawk | gawk, init-system-helpers (>= 1.18~), 
libaudit1 (>= 1:2.4.2), libauparse0 (>= 1:2.3.1), libc6 (>= 2.17)
  Suggests: audispd-plugins

  root@roselp2:~# uname -a
  Linux roselp2 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:38:24 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@roselp2:~# service auditd status
  ? auditd.service - Security Auditing Service
     Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: e
     Active: active (running) since Wed 2016-11-23 02:19:21 CST; 19s ago
   Main PID: 4085 (auditd)
     CGroup: /system.slice/auditd.service
     ??4085 /sbin/auditd -n

  Nov 23 02:19:21 roselp2 auditctl[4086]: enabled 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: failure 1
  Nov 23 02:19:21 roselp2 auditctl[4086]: pid 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: rate_limit 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_limit 320
  Nov 23 02:19:21 roselp2 auditctl[4086]: lost 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_wait_time 

[Touch-packages] [Bug 1750625] Re: update misinterprets 304 response on Packages.gz

[robocoder]

In trusty, this works as expected.

ii  apt  1.0.1ubuntu2.1 
  amd64commandline package manager
ii  apt-transport-https  1.0.1ubuntu2.1 
  amd64https download transport for APT
ii  apt-utils1.0.1ubuntu2.1 
  amd64package management related utility programs
ii  libapt-inst1.5:amd64 1.0.1ubuntu2.1 
  amd64deb package format runtime library
ii  libapt-pkg4.12:amd64 1.0.1ubuntu2.1 
  amd64package management runtime library

Running "apt-get update" the first time, apache returns 200:

> 10.0.4.72 - - [20/Feb/2018:13:49:27 -0500] "GET
/instafreight/dists/trusty/php/binary-amd64/Packages.gz HTTP/1.1" 200
951 "-" "Debian APT-HTTP/1.3 (1.0.1ubuntu2)"

Running "apt-get update" the second time:

> 10.0.4.72 - - [20/Feb/2018:13:49:53 -0500] "GET
/instafreight/dists/trusty/php/binary-amd64/Packages.gz HTTP/1.1" 304
124 "-" "Debian APT-HTTP/1.3 (1.0.1ubuntu2)"

> Hit http://ubuntu.pp trusty/php amd64 Packages

... and third time:

> 10.0.4.72 - - [20/Feb/2018:13:49:59 -0500] "GET
/instafreight/dists/trusty/php/binary-amd64/Packages.gz HTTP/1.1" 304
124 "-" "Debian APT-HTTP/1.3 (1.0.1ubuntu2)"

> Hit http://ubuntu.pp trusty/main amd64 Packages

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

Title:
  update misinterprets 304 response on Packages.gz

Status in apt package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ii  apt  1.2.24   
   amd64commandline package manager
  ii  apt-transport-https  1.2.24   
   amd64https download transport for APT
  ii  apt-utils1.2.24   
   amd64package management related utility programs
  ii  libapt-inst2.0:amd64 1.2.24   
   amd64deb package format runtime library
  ii  libapt-pkg5.0:amd64  1.2.24   
   amd64package management runtime library

  Expected behaviour:

  If apt-get gets a 304 Not Modified when requesting Packages.gz, it
  should ignore the package list (i.e., there's no update).

  Observed behaviour:

  Added a local repository to
  /etc/apt/sources.list.d/instafreight_php.list:

  > deb [arch=amd64 trusted=yes] http://ubuntu/instafreight xenial php

  The first time running apt-get update succeeds; in addition,
  apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:01:39 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 200
  745 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  I am able to install packages from that repo without error.

  Running apt-get a 2nd time succeeds. apache.log doesn't show a request
  for Packages.gz

  Running apt-get a 3rd time, apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:04:45 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 304
  124 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  However, on the console where I ran apt-get, the corresponding output
  is:

  > Err:15 http://ubuntu/instafreight xenial/php amd64 Packages
  >   404  Not Found
  > ...
  > E: Failed to fetch 
http://ubuntu/instafreight/dists/xenial/php/binary-amd64/Packages.gz  404  Not 
Found
  > E: Some index files failed to download. They have been ignored, or old ones 
used instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1750625/+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 1750625] Re: update misinterprets 304 response on Packages.gz

[robocoder]

Still occurring in xenial with apt 1.2.25

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

Title:
  update misinterprets 304 response on Packages.gz

Status in apt package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ii  apt  1.2.24   
   amd64commandline package manager
  ii  apt-transport-https  1.2.24   
   amd64https download transport for APT
  ii  apt-utils1.2.24   
   amd64package management related utility programs
  ii  libapt-inst2.0:amd64 1.2.24   
   amd64deb package format runtime library
  ii  libapt-pkg5.0:amd64  1.2.24   
   amd64package management runtime library

  Expected behaviour:

  If apt-get gets a 304 Not Modified when requesting Packages.gz, it
  should ignore the package list (i.e., there's no update).

  Observed behaviour:

  Added a local repository to
  /etc/apt/sources.list.d/instafreight_php.list:

  > deb [arch=amd64 trusted=yes] http://ubuntu/instafreight xenial php

  The first time running apt-get update succeeds; in addition,
  apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:01:39 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 200
  745 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  I am able to install packages from that repo without error.

  Running apt-get a 2nd time succeeds. apache.log doesn't show a request
  for Packages.gz

  Running apt-get a 3rd time, apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:04:45 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 304
  124 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  However, on the console where I ran apt-get, the corresponding output
  is:

  > Err:15 http://ubuntu/instafreight xenial/php amd64 Packages
  >   404  Not Found
  > ...
  > E: Failed to fetch 
http://ubuntu/instafreight/dists/xenial/php/binary-amd64/Packages.gz  404  Not 
Found
  > E: Some index files failed to download. They have been ignored, or old ones 
used instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1750625/+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 1750379] Re: Distortion Realtek ALC887

[Jason Harvey]

This started affecting me with the kernel update to 4.4.0-112-generic on
xenial. I booted the old kernel and the issue went away. Tried a few
times back and forth and the 4.4.0-112 kernel consistently has the sound
dropouts, while 4.4.0-108 does not.

Also tested with 3 different audio cards (by varying manufacturers),
same result on each.

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

Title:
  Distortion Realtek ALC887

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Sounds can distort even when not amplified. Amplification worked well
  for years before recent PulseAudio update. The audio is Realtek ALC887
  under an IntelG41 Chipset with GA-G41M-Combo main board;

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  I am seeking to engage upstream for April LTS release. Windows have
  abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user
  going!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fleamour   1049 F pulseaudio
   /dev/snd/controlC2:  fleamour   1049 F pulseaudio
   /dev/snd/controlC0:  fleamour   1049 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 13:54:33 2018
  InstallationDate: Installed on 2018-02-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750379/+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 1576420] Re: [H55M-D2H, Realtek ALC887, Green Line Out, Rear] Underruns, dropouts or crackling sound

[Jason Harvey]

This started affecting me with the kernel update to 4.4.0-112-generic on
xenial. I booted the old kernel and the issue went away. Tried a few
times back and forth and the 4.4.0-112 kernel consistently has the sound
dropouts, while 4.4.0-108 does not.

Also tested with 3 different audio cards (by varying manufacturers),
same result on each.

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

Title:
  [H55M-D2H, Realtek ALC887, Green Line Out, Rear] Underruns, dropouts
  or crackling sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  crackling and noisy audio out of only LH speaker.  Only recently
  started on upgrade to 16.04.  Previous versions worked correctly with
  no changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tron   1912 F pulseaudio
   /dev/snd/controlC0:  tron   1912 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Apr 29 07:17:59 2016
  InstallationDate: Installed on 2016-04-24 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [H55M-D2H, Realtek ALC887, Green Line Out, Rear] Underruns, dropouts 
or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/04/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: H55M-D2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd05/04/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-D2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-D2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H55M-D2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576420/+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 1750627] [NEW] Upgrade TZ do address 2018-19's Brazilian DST

[faleiros]

Public bug reported:

Please upgrade Xenial and Trusty tzdata package to 2018c to address
changes in 2018-2019 Brazil's DST.

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

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

Title:
  Upgrade TZ do address 2018-19's Brazilian DST

Status in tzdata package in Ubuntu:
  New

Bug description:
  Please upgrade Xenial and Trusty tzdata package to 2018c to address
  changes in 2018-2019 Brazil's DST.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1750627/+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 1750625] [NEW] update misinterprets 304 response on Packages.gz

[robocoder]

Public bug reported:

Description:Ubuntu 16.04.3 LTS
Release:16.04

ii  apt  1.2.24 
 amd64commandline package manager
ii  apt-transport-https  1.2.24 
 amd64https download transport for APT
ii  apt-utils1.2.24 
 amd64package management related utility programs
ii  libapt-inst2.0:amd64 1.2.24 
 amd64deb package format runtime library
ii  libapt-pkg5.0:amd64  1.2.24 
 amd64package management runtime library

Expected behaviour:

If apt-get gets a 304 Not Modified when requesting Packages.gz, it
should ignore the package list (i.e., there's no update).

Observed behaviour:

Added a local repository to
/etc/apt/sources.list.d/instafreight_php.list:

> deb [arch=amd64 trusted=yes] http://ubuntu/instafreight xenial php

The first time running apt-get update succeeds; in addition, apache.log
shows:

> 10.0.4.72 - - [20/Feb/2018:12:01:39 -0500] "GET
/instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 200
745 "-" "Debian APT-HTTP/1.3 (1.2.24)"

I am able to install packages from that repo without error.

Running apt-get a 2nd time succeeds. apache.log doesn't show a request
for Packages.gz

Running apt-get a 3rd time, apache.log shows:

> 10.0.4.72 - - [20/Feb/2018:12:04:45 -0500] "GET
/instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 304
124 "-" "Debian APT-HTTP/1.3 (1.2.24)"

However, on the console where I ran apt-get, the corresponding output
is:

> Err:15 http://ubuntu/instafreight xenial/php amd64 Packages
>   404  Not Found
> ...
> E: Failed to fetch 
> http://ubuntu/instafreight/dists/xenial/php/binary-amd64/Packages.gz  404  
> Not Found
> E: Some index files failed to download. They have been ignored, or old ones 
> used instead.

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

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

Title:
  update misinterprets 304 response on Packages.gz

Status in apt package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ii  apt  1.2.24   
   amd64commandline package manager
  ii  apt-transport-https  1.2.24   
   amd64https download transport for APT
  ii  apt-utils1.2.24   
   amd64package management related utility programs
  ii  libapt-inst2.0:amd64 1.2.24   
   amd64deb package format runtime library
  ii  libapt-pkg5.0:amd64  1.2.24   
   amd64package management runtime library

  Expected behaviour:

  If apt-get gets a 304 Not Modified when requesting Packages.gz, it
  should ignore the package list (i.e., there's no update).

  Observed behaviour:

  Added a local repository to
  /etc/apt/sources.list.d/instafreight_php.list:

  > deb [arch=amd64 trusted=yes] http://ubuntu/instafreight xenial php

  The first time running apt-get update succeeds; in addition,
  apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:01:39 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 200
  745 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  I am able to install packages from that repo without error.

  Running apt-get a 2nd time succeeds. apache.log doesn't show a request
  for Packages.gz

  Running apt-get a 3rd time, apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:04:45 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 304
  124 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  However, on the console where I ran apt-get, the corresponding output
  is:

  > Err:15 http://ubuntu/instafreight xenial/php amd64 Packages
  >   404  Not Found
  > ...
  > E: Failed to fetch 
http://ubuntu/instafreight/dists/xenial/php/binary-amd64/Packages.gz  404  Not 
Found
  > E: Some index files failed to download. They have been ignored, or old ones 
used instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1750625/+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 1750586] Re: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: python-defaults (Ubuntu)
   Status: New => Confirmed

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

Title:
  package python-minimal 2.7.12-1~16.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python-defaults package in Ubuntu:
  Confirmed

Bug description:
  There seems to be a dependency snarl:

  python-minimal is already the newest version (2.7.12-1~16.04).
  python-minimal set to manually installed.
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   python : PreDepends: python-minimal (= 2.7.11-1) but 2.7.12-1~16.04 is to be 
installed
   python-all : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
   python-all-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
Depends: libpython-all-dev (= 2.7.12-1~16.04) but 2.7.11-1 
is to be installed
   python-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
Depends: libpython-dev (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
  E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify 
a solution).

  apt-get -f install tries to set up python-minimal (2.7.12-1~16.04) and
  returns 1.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-minimal 2.7.12-1~16.04
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Feb 20 08:48:01 2018
  DuplicateSignature:
   package:python-minimal:2.7.12-1~16.04
   Setting up python-minimal (2.7.12-1~16.04) ...
   dpkg: error processing package python-minimal (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-23 (484 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1750586/+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 1749472] Re: mesa 18.0.0 will cause rendering errors in Qt applications

[Dimitri John Ledkov]

mesa is blocked, in addition to this bug, by other issues, and qtbase is
unrelated (e.g. migrating qtbase will not regress this further, nor fix
this issue). Thus removing block-proposed tag to migrate qtbase update.

** Tags removed: block-proposed

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

Title:
  mesa 18.0.0 will cause rendering errors in Qt applications

Status in mesa package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in mesa source package in Bionic:
  New
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  From: https://bugreports.qt.io/browse/QTBUG-66348

  ** extract **

  The `QOpenGLShaderProgram` class in Qt can be used to compile and link
  OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is
  available, it can cache those shaders on disk
  (~/.cache/qtshadercache). The i965 driver in Mesa supports this
  extension since version 18.0.0.

  When the shader is loaded using the `glProgramBinary` function, OpenGL
  can refuse it if for example some hardware or software component
  changed. Mesa refuses binaries that were created by any other build of
  Mesa (using among other things the build_id of the library).

  If the shader is refused, Qt should fallback to compiling it from
  sources, but it incorrectly calls glLinkProgram first. The
  glLinkProgram succeeds, because it actually links 0 shaders together.
  That is allowed in OpenGL compatibility profile and the resulting
  program works as a fixed pipeline. Which of course does not render as
  expected.

  This causes rendering errors in Qt applications every time Mesa is
  updated since version 18.0.0. For example white screen in sddm.

  This issue was originally reported in openSUSE
  (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578).

  ** end extract **

  As this potentially effects Qt applications, and could even render
  display manager login unusable, this should be a blocking bug in mesa
  and Qt until Qt mitigations patches pass codereview and can be
  included in Qtbase for 18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749472/+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 1749472] Re: mesa 18.0.0 will cause rendering errors in Qt applications

[Dimitri John Ledkov]

why is this filed with "block-proposed" tag? Do you intend to prevent
mesa from migrating or qt? At the moment this bug is blocking qtbase
migration, which is a rebuild against openssl1.1 and I do not see how
that change can be related to this bug report.

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

Title:
  mesa 18.0.0 will cause rendering errors in Qt applications

Status in mesa package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in mesa source package in Bionic:
  New
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  From: https://bugreports.qt.io/browse/QTBUG-66348

  ** extract **

  The `QOpenGLShaderProgram` class in Qt can be used to compile and link
  OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is
  available, it can cache those shaders on disk
  (~/.cache/qtshadercache). The i965 driver in Mesa supports this
  extension since version 18.0.0.

  When the shader is loaded using the `glProgramBinary` function, OpenGL
  can refuse it if for example some hardware or software component
  changed. Mesa refuses binaries that were created by any other build of
  Mesa (using among other things the build_id of the library).

  If the shader is refused, Qt should fallback to compiling it from
  sources, but it incorrectly calls glLinkProgram first. The
  glLinkProgram succeeds, because it actually links 0 shaders together.
  That is allowed in OpenGL compatibility profile and the resulting
  program works as a fixed pipeline. Which of course does not render as
  expected.

  This causes rendering errors in Qt applications every time Mesa is
  updated since version 18.0.0. For example white screen in sddm.

  This issue was originally reported in openSUSE
  (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578).

  ** end extract **

  As this potentially effects Qt applications, and could even render
  display manager login unusable, this should be a blocking bug in mesa
  and Qt until Qt mitigations patches pass codereview and can be
  included in Qtbase for 18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749472/+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 1735784] Re: package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

[Phillip Susi]

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

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

Title:
  package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  it always shows a massage that is : "Package operation failed - this
  installation or removal of a software package failed"

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Fri Dec  1 21:14:54 2017
  DpkgHistoryLog:
   Start-Date: 2017-12-01  21:13:48
   Commandline: aptdaemon role='role-commit-packages' sender=':1.94'
   Upgrade: thunderbird-gnome-support:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 
1:52.5.0+build1-0ubuntu0.16.04.1), dpkg:amd64 (1.18.4ubuntu1.2, 
1.18.4ubuntu1.3), thunderbird-locale-en-us:amd64 
(1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), 
firefox-locale-en:amd64 (57.0+build4-0ubuntu0.16.04.6, 
57.0.1+build2-0ubuntu0.16.04.1), thunderbird:amd64 
(1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), 
firefox:amd64 (57.0+build4-0ubuntu0.16.04.6, 57.0.1+build2-0ubuntu0.16.04.1), 
libdpkg-perl:amd64 (1.18.4ubuntu1.2, 1.18.4ubuntu1.3), 
thunderbird-locale-en:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 
1:52.5.0+build1-0ubuntu0.16.04.1), dpkg-dev:amd64 (1.18.4ubuntu1.2, 
1.18.4ubuntu1.3)
  DuplicateSignature:
   package:uuid-runtime:2.27.1-6ubuntu3.3
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package uuid-runtime (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-08-26 (96 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: util-linux
  Title: package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1735784/+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 1718568] Re: dhclient-script fails to wait for link-local address

[Dan Streetman]

** Patch added: "lp1718568-bionic.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1718568/+attachment/5059088/+files/lp1718568-bionic.debdiff

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

Title:
  dhclient-script fails to wait for link-local address

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  In Progress
Status in isc-dhcp source package in Zesty:
  Won't Fix
Status in isc-dhcp source package in Artful:
  In Progress
Status in isc-dhcp source package in Bionic:
  In Progress
Status in isc-dhcp package in Debian:
  New

Bug description:
  [impact]

  bug 1633479 made a change to isc-dhcp to wait for an interface's link-local 
ipv6 address to switch from 'tentative' to normal, because all link-local 
addresses briefly go through a 'tentative' state while the kernel is performing 
ipv6 link-local 'duplicate address detection' (DAD).  While in the 'tentative' 
state, dhclient can't take over the interface and send out
  dhcpv6 requests; it must wait until DAD completes.

  However, the change made in that bug does not account for the case
  where the 'tentative' check is done before the interface has even set
  up a link-local address; its case statement assumes if there is no
  'tentative' or 'dadfailed' string in the output, the link-local
  address is ready to use.  When the address check finds no address at
  all, this will return as successful, even though it shouldn't, and
  dhclient will fail to get the dhcpv6 address.

  [test case]

  on a system that is configured for dhcpv6 on one or more of its
  interfaces, repeatedly try to get the dhcpv6 address.  For interfaces
  that are slower to actually set up their initial tentative link-local
  address, they will occasionally fail, since the current code is a race
  between the kernel adding the tentative link-local address, and the
  dhclient-script.linux code checking the interface for a tentative
  address.

  with the patch to correct this, even interfaces slow to add their
  tentative link-local address should correctly wait for the address to
  get added, and then transition from tentative to normal, and then
  begin the dhcpv6 process.

  [regression potential]

  errors in this function can cause dhclient to fail to get a ipv6
  address for an interface; regression would happen if this patch makes
  it fail more than it already is failing, but would not cause other
  failures or problems after getting an ipv6 address; this patch will
  affect only startup-time.

  [other info]

  related bug 1633479

  
  [original description]

  
  Summary:
  

  If a interface does not yet have a link-local address (as it may have
  just been brought up), dhclient -6  will fail. The built-in
  "wait for link-local address" loop does not function properly, causing
  DHCP failure.

  Discussion:
  ===

  In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on
  Ubuntu 17.04, I was finding that on boot I was getting failures with
  the logged message "no link-local IPv6 address for "

  I found that it took several seconds for the link-local address to be
  assigned when the interface came up (in this case, the ISP/modem-
  facing interface), and worked around it with a script that looks at

    /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20'

  and loops for a fixed number of times for that to be successful.

  On looking at /sbin/dhclient-script it appears that it *tries* to do
  the same thing in

    # set the link up and wait for ipv6 link local dad to finish
    ipv6_link_up_and_dad()

  this code sets

    out=$(ip -6 -o address show dev "$dev" scope link)

  then checks it with a case statement inside of a loop for

  case " $out " in
  *\ dadfailed\ *)
  error "$dev: ipv6 dad failed."
  return 1;;
  *\ tentative\ *) :;;
  *) return 0;;
  esac

  If there is no link-local address, $out will be empty. The default
  case is taken, and the loop exits immediately:

  $ echo "'$out'" ; case " $out " in
  > *\ dadfailed\ *)
  > echo "dadfailed"
  > ;;
  > *\ tentative\ *)
  > echo "tentative"
  > ;;
  > *)
  > echo "default"
  > esac
  ''
  default

  As a result, there is no "wait for link-local address" and when there
  is no link-local address, dhclient fails later on.

  Possible Fix:
  =

  Adding "the missing case" for "no address" case that continues the
  loop is one possible solution.

  .case " $out " in
  .*\ dadfailed\ *)
  .error "$dev: ipv6 dad failed."
  .return 1;;
  .*\ tentative\ *) :;;
  +    "  ")
  +    :
  +    

[Touch-packages] [Bug 1670408] Re: apparmor base abstraction needs backport of rev 3658 to fix several denies (tor, ntp, ...)

[ChristianEhrhardt]

Thanks Jamie, I'm now testing the fix from https://launchpad.net/~ci-
train-ppa-service/+archive/ubuntu/3169 before pushing as SRU.

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

Title:
  apparmor base abstraction needs backport of rev 3658 to fix several
  denies (tor, ntp, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Triaged

Bug description:
  Using tor 0.2.9.9-1ubuntu1 with Linux 4.10.0-9-generic on Zesty, tor
  fails to start after installing the tor package. "systemctl status
  tor@default" reports:

  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Main process exited, 
code=killed, status=11/SEGV
  Mar 06 16:04:00 zesty systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Unit entered failed 
state.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Failed with result 
'signal'.

  There are two AppArmor denials in the kernel log:

  Mar  6 15:53:12 zesty-test kernel: [  102.699647] audit: type=1400
  audit(1488815592.268:35): apparmor="DENIED" operation="file_inherit"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/run/systemd/journal/stdout" pid=3520 comm="tor"
  requested_mask="wr" denied_mask="wr" fsuid=10 ouid=10

  Mar  6 15:53:12 zesty-test kernel: [  102.702418] audit: type=1400
  audit(1488815592.272:37): apparmor="DENIED" operation="file_mmap"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/usr/bin/tor" pid=3520 comm="tor" requested_mask="m"
  denied_mask="m" fsuid=10 ouid=10

  Workaround: add the following two lines to /etc/apparmor.d/system_tor:

  /usr/bin/tor m,
  /run/systemd/journal/stdout rw,

  I couldn't remember how to that that profile reloaded, so I rebooted,
  and after the reboot tor does start up successfully. "systemctl
  tor@default" reports it as running.

  I haven't checked to see if only one or other rule is actually
  required.

  Importance -> High since this bug makes the package unusable in its
  default configuration on Zesty. Since the AppArmor profile comes from
  Debian's 0.2.9.9-1, this should probably be fixed in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1670408/+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 1200296] Re: [MIR] spice-vdagent

[Jeremy Bicha]

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  [MIR] spice-vdagent

Status in spice-vdagent package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Committed

Bug description:
  Availability
  
  Built for all supported architectures.

  In sync with Debian except for one cherry-picked patch to hide spice-
  vdagent from Startup Applications.

  Rationale
  =
  "spice-vdagent adds some nice features to guest systems running over SPICE: 
copy and paste between guest and host, arbitrary resolution support, ... It's 
also very tiny (40kB compressed, less than 200kB installed) and won't startup 
when not running in a SPICE guest.
  Shipping it on the desktop ISOs will improve the user experience when using 
SPICE (eg in GNOME Boxes), and will have no impact on other use cases, so it 
would be really nice to add this package to the ISO."

  Ubuntu GNOME 16.10 and 17.04 included it in the default install.

  Security
  
  No known open security vulnerabilities.

  https://rhn.redhat.com/errata/RHSA-2013-0924.html (CVE-2013-2152)

  Quality assurance
  =
  Bug subscriber: Ubuntu Desktop Bugs

  https://bugs.launchpad.net/ubuntu/+source/spice-vdagent
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=spice-vdagent
  https://bugs.freedesktop.org/buglist.cgi?bug_status=__open__=unix 
agent=Spice

  No tests.

  Dependencies
  
  check-mir reports all other binary dependencies are in main

  Standards compliance
  
  3.9.8

  Maintenance
  ===
  - Actively developed upstream
  https://cgit.freedesktop.org/spice/linux/vd_agent/log/
  https://anonscm.debian.org/git/collab-maint/spice-vdagent.git

  - Maintained in Debian by the same Debian Developer who maintains the
  other Spice packages.

  short dh7 style rules, dh compat 10

  Background information
  ==
  N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1200296/+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 1670408] Re: apparmor base abstraction needs backport of rev 3658 to fix several denies (tor, ntp, ...)

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  apparmor base abstraction needs backport of rev 3658 to fix several
  denies (tor, ntp, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Triaged

Bug description:
  Using tor 0.2.9.9-1ubuntu1 with Linux 4.10.0-9-generic on Zesty, tor
  fails to start after installing the tor package. "systemctl status
  tor@default" reports:

  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Main process exited, 
code=killed, status=11/SEGV
  Mar 06 16:04:00 zesty systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Unit entered failed 
state.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Failed with result 
'signal'.

  There are two AppArmor denials in the kernel log:

  Mar  6 15:53:12 zesty-test kernel: [  102.699647] audit: type=1400
  audit(1488815592.268:35): apparmor="DENIED" operation="file_inherit"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/run/systemd/journal/stdout" pid=3520 comm="tor"
  requested_mask="wr" denied_mask="wr" fsuid=10 ouid=10

  Mar  6 15:53:12 zesty-test kernel: [  102.702418] audit: type=1400
  audit(1488815592.272:37): apparmor="DENIED" operation="file_mmap"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/usr/bin/tor" pid=3520 comm="tor" requested_mask="m"
  denied_mask="m" fsuid=10 ouid=10

  Workaround: add the following two lines to /etc/apparmor.d/system_tor:

  /usr/bin/tor m,
  /run/systemd/journal/stdout rw,

  I couldn't remember how to that that profile reloaded, so I rebooted,
  and after the reboot tor does start up successfully. "systemctl
  tor@default" reports it as running.

  I haven't checked to see if only one or other rule is actually
  required.

  Importance -> High since this bug makes the package unusable in its
  default configuration on Zesty. Since the AppArmor profile comes from
  Debian's 0.2.9.9-1, this should probably be fixed in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1670408/+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 1750610] Re: cupsd crashed with SIGSEGV in ippCopyAttribute()

[Apport retracing service]

*** This bug is a duplicate of bug 1750603 ***
https://bugs.launchpad.net/bugs/1750603

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1750603, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1750610/+attachment/5059065/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1750610/+attachment/5059068/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1750610/+attachment/5059077/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1750610/+attachment/5059079/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1750610/+attachment/5059080/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1750610/+attachment/5059081/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1750610/+attachment/5059082/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1750603

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  cupsd crashed with SIGSEGV in ippCopyAttribute()

Status in cups package in Ubuntu:
  New

Bug description:
  Logged in after desktop being idle for more than 8 hours with crash
  report ready to send.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CupsErrorLog:
   E [20/Feb/2018:00:09:49 +0200] Filter \"brftopagedbrf\" not found.
   E [20/Feb/2018:00:09:49 +0200] Filter \"brftopagedbrf\" not found.
  Date: Tue Feb 20 10:10:43 2018
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2016-10-25 (482 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  KernLog:
   
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: MSI MS-7850
  Papersize: a4
  PpdFiles:
   HP-LaserJet-400-MFP-M425dn: HP LaserJet 400 MFP M425 Postscript (recommended)
   HP_LaserJet_400_MFP_M425dn_195BDA_: HP LaserJet 400 MFP M425dn, driverless, 
cups-filters 1.20.0
   HP_Color_LaserJet_M452dn_B587F1_: Color LaserJet M452dn
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=de66cbe2-16ea-4c60-9081-ed9a0306f7af ro quiet splash vt.handoff=1
  ProcEnviron:
   LANG=en_ZA.UTF-8
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=de66cbe2-16ea-4c60-9081-ed9a0306f7af ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x7fe80e9a1db3 : addl   
$0x1,0x38(%rdx)
   PC (0x7fe80e9a1db3) ok
   source "$0x1" ok
   destination "0x38(%rdx)" (0x0038) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ippCopyAttribute () from /usr/lib/x86_64-linux-gnu/libcups.so.2
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in ippCopyAttribute()
  UpgradeStatus: Upgraded to bionic on 2018-01-24 (26 days ago)
  UserGroups:
   
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V5.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97 PC Mate(MS-7850)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV5.9:bd02/16/2016:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnH97PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7850
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1750610/+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 1316970] Re: g_dbus memory leak in lrmd

[Dan Streetman]

Seyeong,

can you check this updated debdiff to verify it still fixes the mem
leak?

I reverted the free->g_free changes that I previously suggested, as you
were correct - the existing code uses chars and normal free() so we
should stick with that, i was wrong to suggest using g_free().

Also I removed one of the free() that did not seem correct per the docs.

** Patch added: "lp1316970_trusty_pacemaker_v4.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1316970/+attachment/5059064/+files/lp1316970_trusty_pacemaker_v4.debdiff

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New
Status in pacemaker source package in Trusty:
  In Progress

Bug description:
  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty

  affected to pacemaker 1.1.10.
  affected to glib2.0 2.40.2-0ubuntu1

  Please note that patch for pacemaker is created myself.

  [Test Case]

  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage

  [Regression]
  Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
  For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.

  [Others]

  Related commits.

  [1] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000

  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng

  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3

  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168

  $ rmadison pacemaker
   pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates

   pacemaker | 1.1.14-2ubuntu1   | xenial
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
   pacemaker | 1.1.16-1ubuntu1   | zesty
   pacemaker | 1.1.16-1ubuntu1   | artful
   pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
  --

  For glib
  [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
  [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
  [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
  [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a

  [Original Description]

  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.

  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused
  by the g_dbus API, the use of which was removed in Pacemaker 1.11.

  I've also attached the Valgrind output from the run that exposed the
  issue.

  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).

  If not, can you advise which version of the OS will be the first to
  take 1.11 please?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+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 1724152] Re: ISST-LTE: pVM: aureport couldn't get the right auid from the audit log on ubuntu16.04

[Tyler Hicks]

This SRU has been stuck in xenial-proposed for too long so I decided to
go ahead and verify it myself. The zesty SRU is no longer valid since
zesty has went EoL. The xenial SRU works as expected using the Test Case
described in the bug description.

** Tags removed: verification-needed verification-needed-xenial 
verification-needed-zesty
** Tags added: verification-done verification-done-xenial

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

Title:
  ISST-LTE: pVM: aureport couldn't get the right auid from the audit log
  on ubuntu16.04

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in audit package in Ubuntu:
  Invalid
Status in audit source package in Xenial:
  Fix Committed
Status in audit source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

  The aureport command, part of the audit userspace utilities,
  incorrectly reports the user id of successful logins. "-1" is printed
  instead of the expected user id.

  [Test Case]

  As root, run `login`. Proceed as follows:

  1. Login with a blank username and any password
  2. Login with an invalid username and any password
  3. Login with a valid username and an invalid password
  4. Login with a valid username and a valid password
  5. Exit from the login shell
  6. Run `aureport -l` and examine the last for login records

  An unpatched aureport will print the following:

  
  # date time auid host term exe success event
  
  ...
  2. 10/17/2017 23:45:32 UNKNOWN ? /dev/pts/8 /bin/login no 97
  3. 10/17/2017 23:45:39 UNKNOWN ? /dev/pts/8 /bin/login no 99
  4. 10/17/2017 23:45:45 tyhicks ? /dev/pts/8 /bin/login no 101
  5. 10/17/2017 23:45:49 -1 ? /dev/pts/8 /bin/login yes 107

  A patch aureport will print the correct output:

  Login Report
  
  # date time auid host term exe success event
  
  ...
  2. 10/17/2017 23:52:44 UNKNOWN ? /dev/pts/8 /bin/login no 165
  3. 10/17/2017 23:52:52 UNKNOWN ? /dev/pts/8 /bin/login no 167
  4. 10/17/2017 23:52:58 tyhicks ? /dev/pts/8 /bin/login no 169
  5. 10/17/2017 23:53:02 1000 ? /dev/pts/8 /bin/login yes 175

  Note the "1000" in the auid column on the #5 row. It should *not* be
  "-1".

  [Regression Potential]

  The regression potential is limited due to the change only affecting a
  single line of code, the fix comes from upstream, and that the
  aureport utility is not critical.

  [Original Report]

  == Comment: #0 - Miao Tao Feng  - 2016-11-23 02:46:25 ==
  When we develop new testcase for audit, we found that command "aureport -l" 
print out wrong auid "-1"  on ubuntu16.04  and it should be 1000 according to 
the audit.log.

  The following are details:

  root@roselp2:~# aureport -l

  Login Report
  
  # date time auid host term exe success event
  
  1. 11/23/2016 02:20:12 -1 10.33.24.118 /dev/pts/0 /usr/sbin/sshd yes 18

  The auid "-1" on the above line should be "1000? according to the
  audit.log.

  root@roselp2:~# grep ":18" /var/log/audit/audit.log
  type=USER_LOGIN msg=audit(1479889212.292:18): pid=4177 uid=0 auid=1000 ses=4 
msg='op=login id=1000 exe="/usr/sbin/sshd" hostname=10.33.24.118 
addr=10.33.24.118 terminal=/dev/pts/0 res=success'

  root@roselp2:~# dpkg -s auditd
  Package: auditd
  Status: install ok installed
  Priority: extra
  Section: admin
  Installed-Size: 1051
  Maintainer: Ubuntu Developers 
  Architecture: ppc64el
  Source: audit
  Version: 1:2.4.5-1ubuntu2
  Depends: lsb-base (>= 3.0-6), mawk | gawk, init-system-helpers (>= 1.18~), 
libaudit1 (>= 1:2.4.2), libauparse0 (>= 1:2.3.1), libc6 (>= 2.17)
  Suggests: audispd-plugins

  root@roselp2:~# uname -a
  Linux roselp2 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:38:24 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@roselp2:~# service auditd status
  ? auditd.service - Security Auditing Service
     Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: e
     Active: active (running) since Wed 2016-11-23 02:19:21 CST; 19s ago
   Main PID: 4085 (auditd)
     CGroup: /system.slice/auditd.service
     ??4085 /sbin/auditd -n

  Nov 23 02:19:21 roselp2 auditctl[4086]: enabled 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: failure 1
  Nov 23 02:19:21 roselp2 auditctl[4086]: pid 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: rate_limit 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_limit 320
  Nov 23 02:19:21 roselp2 auditctl[4086]: lost 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_wait_time 15000
  Nov 23 02:19:21 roselp2 systemd[1]: Started Security 

[Touch-packages] [Bug 1750608] [NEW] Fixup ADT tests

[Dimitri John Ledkov]

Public bug reported:

[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

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: systemd (Ubuntu Artful)
 Importance: Undecided
 Status: New

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

** Changed in: systemd (Ubuntu)
   Status: New => 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/1750608

Title:
  Fixup ADT tests

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

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 1725348] Re: Systemd - Bypassing MemoryDenyWriteExecution policy

[Dimitri John Ledkov]

** Description changed:

+ [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, 
+ Sincerely,
  Thomas IMBERT

-- 
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:
  In Progress
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 1670408] Re: apparmor base abstraction needs backport of rev 3658 to fix several denies (tor, ntp, ...)

[Jamie Strandboge]

This is fine for SRU. 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/1670408

Title:
  apparmor base abstraction needs backport of rev 3658 to fix several
  denies (tor, ntp, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Triaged

Bug description:
  Using tor 0.2.9.9-1ubuntu1 with Linux 4.10.0-9-generic on Zesty, tor
  fails to start after installing the tor package. "systemctl status
  tor@default" reports:

  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Main process exited, 
code=killed, status=11/SEGV
  Mar 06 16:04:00 zesty systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Unit entered failed 
state.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Failed with result 
'signal'.

  There are two AppArmor denials in the kernel log:

  Mar  6 15:53:12 zesty-test kernel: [  102.699647] audit: type=1400
  audit(1488815592.268:35): apparmor="DENIED" operation="file_inherit"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/run/systemd/journal/stdout" pid=3520 comm="tor"
  requested_mask="wr" denied_mask="wr" fsuid=10 ouid=10

  Mar  6 15:53:12 zesty-test kernel: [  102.702418] audit: type=1400
  audit(1488815592.272:37): apparmor="DENIED" operation="file_mmap"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/usr/bin/tor" pid=3520 comm="tor" requested_mask="m"
  denied_mask="m" fsuid=10 ouid=10

  Workaround: add the following two lines to /etc/apparmor.d/system_tor:

  /usr/bin/tor m,
  /run/systemd/journal/stdout rw,

  I couldn't remember how to that that profile reloaded, so I rebooted,
  and after the reboot tor does start up successfully. "systemctl
  tor@default" reports it as running.

  I haven't checked to see if only one or other rule is actually
  required.

  Importance -> High since this bug makes the package unusable in its
  default configuration on Zesty. Since the AppArmor profile comes from
  Debian's 0.2.9.9-1, this should probably be fixed in Debian.

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

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Zesty)
   Status: New => Won't Fix

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

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

-- 
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:
  In Progress
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  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 1722481] Re: systemd should sync disks, before killing all processes on shutdown

[Dimitri John Ledkov]

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

-- 
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:
  In Progress

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 1734409] Re: systemd-sysctl: exit gracefully on EPERM/EACCESS

[Dimitri John Ledkov]

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

-- 
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:
  In Progress

Bug description:
  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 1734410] Re: systemd: handle undelegated cgroup2 hierarchy

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Zesty)
   Status: New => Won't Fix

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

-- 
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:
  In Progress
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  In Progress
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  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 1732803] Re: systemd-journald RateLimitBurst is sometimes divided by 4

[Dimitri John Ledkov]

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

-- 
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:
  In Progress

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 1737570] Re: Add support for RequiredForOnline in networkd

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Zesty)
   Status: Confirmed => Won't Fix

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

-- 
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:
  In Progress
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  In Progress
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  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 1736955] Re: dep8 test systemd-fsckd fails on s390

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Zesty)
   Status: New => Won't Fix

-- 
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:
  In Progress

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 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Zesty)
   Status: Confirmed => Won't Fix

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

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

-- 
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:
  In Progress
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  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 696435] Re: wait-for-root fails to detect nbd root

[Dimitri John Ledkov]

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

-- 
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:
  In Progress

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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Zesty)
   Status: New => Won't Fix

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

-- 
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:
  In Progress
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  In Progress

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 only the new ip address on the 
network interface and the ping toward an outside host work properly.

  During the test the dhcp server records correctly leases and their
  duration.

  We check directly from console the network interface setting with the
  tool ip, checking continuously the value for ip address and 

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

[Dimitri John Ledkov]

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

-- 
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:
  In Progress
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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[Dimitri John Ledkov]

Ping, has above been implemented in landscape? to attempt poweroff, then
-f poweroff, then -ff poweroff?

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in landscape-client source package in Xenial:
  New
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  Used Landscape (Paid Canonical Subscription) to upgrade one of my
  machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

[Dimitri John Ledkov]

** Description changed:

+ [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.

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

-- 
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:
  In Progress

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 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

[Dimitri John Ledkov]

** Description changed:

+ [Impact]
+ 
+  * networkd aborts, whilst failing to update address for a
+ failed/lingering link.
+ 
+ [Test Case]
+ 
+  * Sending invalid or flooding the system with RA requests typically
+ reproduces this bug.
+ 
+ Examples:
+ https://github.com/systemd/systemd/issues/2977
+ https://github.com/systemd/systemd/issues/2228
+ https://github.com/systemd/systemd/issues/3204
+ 
+ 
+ [Regression Potential] 
+ 
+  * This patch is a cherrypick form upstream, which adds additional
+ checks to prevent attempts to configure a link which is not ready yet.
+ This patch is present in v230+ thus the code path should have been well
+ exercised in Ubuntu by now, in later releases.
+ 
+ Otherwise, the code behaviour is not changed. Simply, in case of broken
+ links, address update is not attempted and error is returned.
+ 
+ 
https://github.com/systemd/systemd/commit/7209086d8a0df862d04428877c2d2b9e562034f1
+ 
+ 
+ [Other Info]
+  
+  * Original bug report
+ 
  Hi,
  
  the net of my PC is configured via systemd-networkd + systemd-resolved.
  And last two weeks I faced with the problem when my net is down.
  "journalctl -xe" helped to detect this issue:
  
  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  
- 
- When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.
+ When I type "systemctl restart systemd-networkd", nothing happens, net
+ is still down. When I type "systemctl restart systemd-resolved", it's
+ all starting to work fine, as usual.
  
  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224
  
  Looks like this issue was fixed in systemd-230. So can you backport this
  patch to systemd package?
  
  I can patch it and test it myself, actually, but it would be really nice
  if there will be no need to.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
-  [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
-  [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
-  [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
-  
-  3 overridden configuration files found.
+  [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
+  [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
+  [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
+ 
+  3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  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.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1750593] [NEW] Misspelled word in description-en for unity-scopes-runner

[Jeremy Nation]

Public bug reported:

For package "unity-scopes-runner", version
"7.1.4+16.04.20180209.1-0ubuntu1", the "Description-en" value is:

```
Description-en: desktop runner for misceallenous scopes
 The scope runner is a handy tool for wrapping on a desktop the various
 scoped installed on the system.
```

"misceallenous" should be spelled "miscellaneous".

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

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

Title:
  Misspelled word in description-en for unity-scopes-runner

Status in libunity package in Ubuntu:
  New

Bug description:
  For package "unity-scopes-runner", version
  "7.1.4+16.04.20180209.1-0ubuntu1", the "Description-en" value is:

  ```
  Description-en: desktop runner for misceallenous scopes
   The scope runner is a handy tool for wrapping on a desktop the various
   scoped installed on the system.
  ```

  "misceallenous" should be spelled "miscellaneous".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1750593/+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 1534191] Re: video replay should resume after user confirms high volume

[Matthew Paul Thomas]

** Changed in: indicator-sound (Ubuntu)
 Assignee: Matthew Paul Thomas (mpt) => (unassigned)

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

Title:
  video replay should resume after user confirms high volume

Status in indicator-sound package in Ubuntu:
  Incomplete
Status in mediaplayer-app package in Ubuntu:
  Confirmed

Bug description:
  A followup to bug #1504065 suggested by davmor2 in #phablet.

   charles, jhodapp: with silo 46 I have an issue. On first
  boot and possibly every day after that, if you try and watch a video
  from the device, you get a popup saying audio is loud accept or what
  ever, this popup takes focus from the media player and therefore
  pauses the video, when you click on yes is there a way we can continue
  playback for the audio warnings?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1534191/+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 789479]

[PJBrs]

Oops, copying the microsoft file does not fix the fonts. Sorry for the
spam!

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

Title:
  Improper encoding of the "Symbol" font

Status in Wine:
  New
Status in poppler package in Ubuntu:
  Invalid
Status in wine1.2 package in Ubuntu:
  Fix Released
Status in wine1.3 package in Ubuntu:
  Fix Released

Bug description:
  The characters 'm' and 'p' are mapped to wrong glphys in the base-14
  font "Symbol". This problem has not occurred in maverick.

  I'm attaching a pdf-file that uses all base-14 fonts without embedding
  them, and screenshots from maverick and natty. Note the differences in
  the 5th word in the "Symbol" line. The screenshots were made in
  TeXworks which is based on poppler-qt4 (evince in natty gives the same
  result as TeXworks, but I don't have a maverick-screenshot of it at
  hand).

  $ lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  $apt-cache policy libpoppler-qt4-3 
  libpoppler-qt4-3:
Installed: 0.16.4-0ubuntu1.1
Candidate: 0.16.4-0ubuntu1.1
Version table:
   *** 0.16.4-0ubuntu1.1 0
  500 http://gd.tuwien.ac.at/opsys/linux/ubuntu/archive/ 
natty-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.16.4-0ubuntu1 0
  500 http://gd.tuwien.ac.at/opsys/linux/ubuntu/archive/ natty/main 
amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/wine/+bug/789479/+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 1670408] Re: apparmor base abstraction needs backport of rev 3658 to fix several denies (tor, ntp, ...)

[ChristianEhrhardt]

More or less adirect backport of Jamies changes in Artful.
Only opening up rules slightly, so regression risk low.
But I clearly want a security Team ack/review before sponsoring it.

** Patch added: "Backport of 2.11.0-2ubuntu5 fix to Xenial to fix 1670408"
   
https://bugs.launchpad.net/ubuntu/+source/tor/+bug/1670408/+attachment/5058995/+files/xenial-base-journald-updates.debdiff

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

Title:
  apparmor base abstraction needs backport of rev 3658 to fix several
  denies (tor, ntp, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Triaged

Bug description:
  Using tor 0.2.9.9-1ubuntu1 with Linux 4.10.0-9-generic on Zesty, tor
  fails to start after installing the tor package. "systemctl status
  tor@default" reports:

  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Main process exited, 
code=killed, status=11/SEGV
  Mar 06 16:04:00 zesty systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Unit entered failed 
state.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Failed with result 
'signal'.

  There are two AppArmor denials in the kernel log:

  Mar  6 15:53:12 zesty-test kernel: [  102.699647] audit: type=1400
  audit(1488815592.268:35): apparmor="DENIED" operation="file_inherit"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/run/systemd/journal/stdout" pid=3520 comm="tor"
  requested_mask="wr" denied_mask="wr" fsuid=10 ouid=10

  Mar  6 15:53:12 zesty-test kernel: [  102.702418] audit: type=1400
  audit(1488815592.272:37): apparmor="DENIED" operation="file_mmap"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/usr/bin/tor" pid=3520 comm="tor" requested_mask="m"
  denied_mask="m" fsuid=10 ouid=10

  Workaround: add the following two lines to /etc/apparmor.d/system_tor:

  /usr/bin/tor m,
  /run/systemd/journal/stdout rw,

  I couldn't remember how to that that profile reloaded, so I rebooted,
  and after the reboot tor does start up successfully. "systemctl
  tor@default" reports it as running.

  I haven't checked to see if only one or other rule is actually
  required.

  Importance -> High since this bug makes the package unusable in its
  default configuration on Zesty. Since the AppArmor profile comes from
  Debian's 0.2.9.9-1, this should probably be fixed in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1670408/+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 1670408] Re: apparmor base abstraction needs backport of rev 3658 to fix several denies (tor, ntp, ...)

[ChristianEhrhardt]

This is already fixed as backport in other releases - here apparmor
2.11.0-2ubuntu5 in Artful

apparmor (2.11.0-2ubuntu5) artful; urgency=medium   
 

 
  * debian/patches/base-journald-updates.patch: update base abstraction for 
 
additional journald sockets 
 

 
 -- Jamie Strandboge   Thu, 27 Apr 2017 16:09:50 +

We can use that as it already has some adaption for backports don (like
var, run)

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

Title:
  apparmor base abstraction needs backport of rev 3658 to fix several
  denies (tor, ntp, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Triaged

Bug description:
  Using tor 0.2.9.9-1ubuntu1 with Linux 4.10.0-9-generic on Zesty, tor
  fails to start after installing the tor package. "systemctl status
  tor@default" reports:

  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Main process exited, 
code=killed, status=11/SEGV
  Mar 06 16:04:00 zesty systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Unit entered failed 
state.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Failed with result 
'signal'.

  There are two AppArmor denials in the kernel log:

  Mar  6 15:53:12 zesty-test kernel: [  102.699647] audit: type=1400
  audit(1488815592.268:35): apparmor="DENIED" operation="file_inherit"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/run/systemd/journal/stdout" pid=3520 comm="tor"
  requested_mask="wr" denied_mask="wr" fsuid=10 ouid=10

  Mar  6 15:53:12 zesty-test kernel: [  102.702418] audit: type=1400
  audit(1488815592.272:37): apparmor="DENIED" operation="file_mmap"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/usr/bin/tor" pid=3520 comm="tor" requested_mask="m"
  denied_mask="m" fsuid=10 ouid=10

  Workaround: add the following two lines to /etc/apparmor.d/system_tor:

  /usr/bin/tor m,
  /run/systemd/journal/stdout rw,

  I couldn't remember how to that that profile reloaded, so I rebooted,
  and after the reboot tor does start up successfully. "systemctl
  tor@default" reports it as running.

  I haven't checked to see if only one or other rule is actually
  required.

  Importance -> High since this bug makes the package unusable in its
  default configuration on Zesty. Since the AppArmor profile comes from
  Debian's 0.2.9.9-1, this should probably be fixed in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1670408/+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 1670408] Re: apparmor base abstraction needs backport of rev 3658 to fix several denies (tor, ntp, ...)

[ChristianEhrhardt]

@jdstrand - I subscribed you and would ask for your review of the
proposed debdiff.

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

Title:
  apparmor base abstraction needs backport of rev 3658 to fix several
  denies (tor, ntp, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Triaged

Bug description:
  Using tor 0.2.9.9-1ubuntu1 with Linux 4.10.0-9-generic on Zesty, tor
  fails to start after installing the tor package. "systemctl status
  tor@default" reports:

  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Main process exited, 
code=killed, status=11/SEGV
  Mar 06 16:04:00 zesty systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Unit entered failed 
state.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Failed with result 
'signal'.

  There are two AppArmor denials in the kernel log:

  Mar  6 15:53:12 zesty-test kernel: [  102.699647] audit: type=1400
  audit(1488815592.268:35): apparmor="DENIED" operation="file_inherit"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/run/systemd/journal/stdout" pid=3520 comm="tor"
  requested_mask="wr" denied_mask="wr" fsuid=10 ouid=10

  Mar  6 15:53:12 zesty-test kernel: [  102.702418] audit: type=1400
  audit(1488815592.272:37): apparmor="DENIED" operation="file_mmap"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/usr/bin/tor" pid=3520 comm="tor" requested_mask="m"
  denied_mask="m" fsuid=10 ouid=10

  Workaround: add the following two lines to /etc/apparmor.d/system_tor:

  /usr/bin/tor m,
  /run/systemd/journal/stdout rw,

  I couldn't remember how to that that profile reloaded, so I rebooted,
  and after the reboot tor does start up successfully. "systemctl
  tor@default" reports it as running.

  I haven't checked to see if only one or other rule is actually
  required.

  Importance -> High since this bug makes the package unusable in its
  default configuration on Zesty. Since the AppArmor profile comes from
  Debian's 0.2.9.9-1, this should probably be fixed in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1670408/+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 1750586] Re: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python-minimal 2.7.12-1~16.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  There seems to be a dependency snarl:

  python-minimal is already the newest version (2.7.12-1~16.04).
  python-minimal set to manually installed.
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   python : PreDepends: python-minimal (= 2.7.11-1) but 2.7.12-1~16.04 is to be 
installed
   python-all : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
   python-all-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
Depends: libpython-all-dev (= 2.7.12-1~16.04) but 2.7.11-1 
is to be installed
   python-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
Depends: libpython-dev (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
  E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify 
a solution).

  apt-get -f install tries to set up python-minimal (2.7.12-1~16.04) and
  returns 1.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-minimal 2.7.12-1~16.04
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Feb 20 08:48:01 2018
  DuplicateSignature:
   package:python-minimal:2.7.12-1~16.04
   Setting up python-minimal (2.7.12-1~16.04) ...
   dpkg: error processing package python-minimal (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-23 (484 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1750586/+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 1750586] [NEW] package python-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Stephan Samuel]

Public bug reported:

There seems to be a dependency snarl:

python-minimal is already the newest version (2.7.12-1~16.04).
python-minimal set to manually installed.
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 python : PreDepends: python-minimal (= 2.7.11-1) but 2.7.12-1~16.04 is to be 
installed
 python-all : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be installed
 python-all-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
  Depends: libpython-all-dev (= 2.7.12-1~16.04) but 2.7.11-1 is 
to be installed
 python-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be installed
  Depends: libpython-dev (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a 
solution).

apt-get -f install tries to set up python-minimal (2.7.12-1~16.04) and
returns 1.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-minimal 2.7.12-1~16.04
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Tue Feb 20 08:48:01 2018
DuplicateSignature:
 package:python-minimal:2.7.12-1~16.04
 Setting up python-minimal (2.7.12-1~16.04) ...
 dpkg: error processing package python-minimal (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-10-23 (484 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: python-defaults
Title: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package python-minimal 2.7.12-1~16.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  There seems to be a dependency snarl:

  python-minimal is already the newest version (2.7.12-1~16.04).
  python-minimal set to manually installed.
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   python : PreDepends: python-minimal (= 2.7.11-1) but 2.7.12-1~16.04 is to be 
installed
   python-all : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
   python-all-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
Depends: libpython-all-dev (= 2.7.12-1~16.04) but 2.7.11-1 
is to be installed
   python-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
Depends: libpython-dev (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
  E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify 
a solution).

  apt-get -f install tries to set up python-minimal (2.7.12-1~16.04) and
  returns 1.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-minimal 2.7.12-1~16.04
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Feb 20 08:48:01 2018
  DuplicateSignature:
   package:python-minimal:2.7.12-1~16.04
   Setting up python-minimal (2.7.12-1~16.04) ...
   dpkg: error processing package python-minimal (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-23 (484 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1750586/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

[Dan Streetman]

Ok, in that case, can you open a separate lp bug for the glib2.0 memory
leak?  I think it will be easier to track just fixing the pacemaker mem
leaks in this bug, and track fixing the glib2.0 mem leak in a separate
bug.

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New
Status in pacemaker source package in Trusty:
  In Progress

Bug description:
  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty

  affected to pacemaker 1.1.10.
  affected to glib2.0 2.40.2-0ubuntu1

  Please note that patch for pacemaker is created myself.

  [Test Case]

  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage

  [Regression]
  Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
  For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.

  [Others]

  Related commits.

  [1] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000

  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng

  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3

  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168

  $ rmadison pacemaker
   pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates

   pacemaker | 1.1.14-2ubuntu1   | xenial
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
   pacemaker | 1.1.16-1ubuntu1   | zesty
   pacemaker | 1.1.16-1ubuntu1   | artful
   pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
  --

  For glib
  [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
  [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
  [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
  [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a

  [Original Description]

  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.

  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused
  by the g_dbus API, the use of which was removed in Pacemaker 1.11.

  I've also attached the Valgrind output from the run that exposed the
  issue.

  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).

  If not, can you advise which version of the OS will be the first to
  take 1.11 please?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+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 1747460] Re: [MIR] py-macaroon-bakery, protobuf, pyrfc3339

[Mathieu Trudel-Lapierre]

python-nacl is missing a team subscriber.

I'm reviewing these source packages.

** Changed in: python-nacl (Ubuntu)
   Status: New => Incomplete

** Changed in: pyrfc3339 (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: py-macaroon-bakery (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: python-nacl (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: pyrfc3339 (Ubuntu)
   Status: New => Triaged

** Changed in: py-macaroon-bakery (Ubuntu)
   Status: New => Triaged

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

Title:
  [MIR] py-macaroon-bakery, protobuf, pyrfc3339

Status in protobuf package in Ubuntu:
  Invalid
Status in py-macaroon-bakery package in Ubuntu:
  Triaged
Status in pyrfc3339 package in Ubuntu:
  Triaged
Status in python-nacl package in Ubuntu:
  Incomplete

Bug description:
  py-macaroon-bakery
  ==

  1. Availability: all

  2. Rationale:
  Macaroons is a new form of authorization mechanism. The macaroon bakery 
builds on pymacaroons, which allows it working at a higher level.

  In order for MAAS (and other projects) to support macaroon based
  authentication, this needs to be in main. This will allow projects to
  support remote/centralized authentication based on macaroons.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:

  Dependencies in universe:
   - python3-pymacaroons (MIR LP: #1746772)
   - python3-nacl
   - python3-protobuf
   - python3-rfc3339

  7. Standards:
  No lintian errors.

  Packaged with debhelper. Source format is 3.0 (quilt)

  Standards version: 4.4.1

  8. Maintenance:
  Easy.

  9. Background information:
  This is a required dependency to implement third party/centralized 
authentication alongside with pymacaroons. This is a new dependency that's 
required by MAAS.

  python3-protobuf
  ==

  1. Availability: any

  2. Rationale:
  Dependency of python3-macaroonbakery. The library from this same source 
package, libprotobuf10, is already in main.

  3. Security:
  No CVE's

  4. QA:
  protobuf source, 10 bugs in debian, 11 ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors.

  Packaged with debhelper. Source format is 3.0 (quilt)

  Standards version: 3.9.8

  8. Maintenance:
  Easy.

  9. Background information:
  protobuf source already has binaries in main. This is just the python 
bindings that are required by macaroonbakery.

  rfc3339
  ==

  1. Availability: all

  2. Rationale:
  Dependency of python3-macaroonbakery.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors. 1 warning:
  W: pyrfc3339 source: ancient-standards-version 3.9.6 (released 2014-09-17) 
(current is 4.1.3)

  Packaged with debhelper. Source format is 3.0 (quilt)

  8. Maintenance:
  Easy.

  9. Background information:
  Parser and generator of RFC 3339-compliant timestamps. This is a dependency 
for python3-macaroonbakery.

  
  python-nacl
  ==

  1. Availability: any

  2. Rationale:
  Dependency of python3-macaroonbakery.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors.

  Uses standards version 3.9.8

  Packaged with debhelper. Source format is 3.0 (quilt)

  8. Maintenance:
  Easy.

  9. Background information:
  PyNaCl is a Python binding to the Networking and Cryptography library. This 
is a dependency for python3-macaroonbakery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/1747460/+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 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Kai-Heng Feng]

Please attach full dmesg if possible.

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for gdomap.service: Transport endpoint is not connected

  When the user purged laptop-mode-tools the system starts successfully
  on battery.

  The user installed a fresh instance of 17.10 on a 2nd M2 

[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed

[AsciiWolf]

I don't have the ETH anymore, but I will send $600 via PayPal to the one
who fixes this issue.

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

Title:
  gnome software leaves dependencies installed

Status in GNOME Software:
  Invalid
Status in Release Notes for Ubuntu:
  Fix Released
Status in aptdaemon package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  Triaged
Status in packagekit package in Ubuntu:
  New

Bug description:
  Using gnome software (or another PackageKit or aptdaemon based UI) to
  install an application - removal of that package leaves behind
  dependencies

  Installing an application with ubuntu software centre only leaves
  behind config files (seen in synaptic labelled for complete removal).

  After installing and then removing alarm clock with USC -

  sudo apt-get autoremove
  [sudo] password for wolf:
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

  After cleaning up and then reinstalling with gnome software, followed
  by the removal

  sudo apt-get autoremove
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED
    libappindicator1 libindicator7
  0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade.
  After this operation, 184 kB disk space will be freed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar  3 16:23:45 2016
  InstallationDate: Installed on 2015-10-29 (126 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1552792/+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 1630860] Re: [HDA-Intel - HDA Intel PCH, playback] Playback problem

[Bruno Katzengold]

same here
ubuntu 16.04

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Playback problem

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  New

Bug description:
  Lenovo Thinkpad P50 with docking station

  Issues: Headphone jack on station not detected; no sound (works without 
docking station)
  Issues: Sound via HDMI on station not detected; no sound (works without 
docking station)

  Since all outputs are routed via the Thunderbolt chip, my guess is
  that it's related to the pin setup (lenovo-dock) in Alsa. Without the
  dock, everything works, headphone/mic jack on the P50 itself is
  hotplug (switches from speaker to headphones right away).

  Screenshots (with and without docking station) attached.

  Thanks and LG,
  Wolfgang

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: symap_custom_dkms_x86_64 nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wjl2943 F pulseaudio
   /dev/snd/controlC0:  wjl2943 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Oct  5 14:14:02 2016
  InstallationDate: Installed on 2016-09-10 (24 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: HDA NVidia - HDA NVidia
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET52W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS1EH0B
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET52W(1.26):bd05/10/2016:svnLENOVO:pn20EQS1EH0B:pvrThinkPadP50:rvnLENOVO:rn20EQS1EH0B:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EQS1EH0B
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-10-04T12:48:36.270399

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1630860/+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 1733557] Re: Login screen showing Authentication Failure Switch to greeter...

[Eugene Romanenko]

Appears on 16.04.3 after updating Unity to latest packages.
Also on 17.10 with installed unity-session.

For me, this issue appears after switching to another user.

Steps to reproduce (must be more than one local users on system, eg. "bob", 
"alice"):
1. Login under bob.
2. Via upper-right menu switch to "alice".
3. On greeter screen setect "alice", login under alice.
4. Logout, return to greeter screen.
5. Select bob (already logged in). Enter password.
6. Lock screen. Issue appeared.
Issue appeared on every screen lock.

Messages in syslog:

Jan 6 17:15:33 eugene-Lenovo-Flex-2-14 systemd[1411]: Stopped Backing Service 
for the Unity Panel in Lockscreen mode.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 
unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication 
process. Retrying for 1 time.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 
unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication 
process. Retrying for 2 time.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Starting Backing Service 
for the Unity Panel in Lockscreen mode...
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 
unity.glib.dbus.proxy GLibDBusProxy.cpp:487 Calling method "EmitEvent" on 
object path: "/com/ubuntu/Upstart" failed: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.canonical.Unity.Test.Upstart was not provided by any .service files
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd-prestart-check[3804]: grep: 
/usr/share/gnome-session/sessions/ubuntu.session: Нет такого файла или каталога
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Started Backing Service 
for the Unity Panel in Lockscreen mode.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Reached target A target 
that, when running, represents the screen being locked.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 
unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication 
process. Retrying for 3 time.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 
unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication 
process. Retrying for 4 time.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 
unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication 
process. Retrying for 5 time.


** Summary changed:

- Login screen showing Authentication Failed Switch to greeter...
+ Login screen showing Authentication Failure Switch to greeter...

** Package changed: lightdm (Ubuntu) => unity (Ubuntu)

** Tags added: 16.04 17.10 unity xenial

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

Title:
  Login screen showing Authentication Failure Switch to greeter...

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  When I lock my machine, the login screen shows my current user with
  the message: "Authentication Failed"

  ..and in the position when the password normally exists, the option
  "Switch to greeter..."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Nov 21 10:28:47 2017
  InstallationDate: Installed on 2017-04-17 (217 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-10-23 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1733557/+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 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

[Daniel van Vugt]

We have made efforts to improve Bluetooth audio support over the past
year, but most of the fixes are in Ubuntu 17.10 and 18.04 only. We've
backported some to 16.04 but unfortunately can't backport everything.

Please try 17.10/18.04 and if you have any ongoing issues then open a
new bug.

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

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+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 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

[brett hetherington]

I installed 14 alongside 16. İf I need telephony I load 14.. if I need
googleearth I load 16. sorry but some dunderhead left hsp bluetooth
outta 16. ask the bluez folks... any version of bluez 4 has twice the
functionality of bluez5. maybe some bright spark could copy and paste
the functioning lines from bluez4 to bluez5. and then tell us all what
to do.

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

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+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 1750532] [NEW] package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Rohit Kumar]

Public bug reported:

Not working proper

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-32-generic 4.13.0-32.35
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rohit  1642 F pulseaudio
Date: Tue Feb 20 15:31:30 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
HibernationDevice: RESUME=UUID=4d934564-93f4-44fa-a0a2-40391da06695
InstallationDate: Installed on 2018-01-29 (22 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
IwConfig:
 enp3s0no wireless extensions.
 
 lono wireless extensions.
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7d503abe-28c9-44cd-9fb8-b357ae7619cd ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.5, Python 3.5.2, python3-minimal, 3.5.1-3
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7.1
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UpgradeStatus: Upgraded to artful on 2018-02-13 (7 days ago)
dmi.bios.date: 11/11/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: WVG4110H.86A.0015.2010..1718
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DG41WV
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE90316-104
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrWVG4110H.86A.0015.2010..1718:bd11/11/2010:svn:pn:pvr:rvnIntelCorporation:rnDG41WV:rvrAAE90316-104:cvn:ct3:cvr:

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful third-party-packages

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

Title:
  package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Not working proper

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rohit  1642 F pulseaudio
  Date: Tue Feb 20 15:31:30 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=4d934564-93f4-44fa-a0a2-40391da06695
  InstallationDate: Installed on 2018-01-29 (22 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7d503abe-28c9-44cd-9fb8-b357ae7619cd ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.5, Python 3.5.2, python3-minimal, 3.5.1-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7.1
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to artful on 2018-02-13 (7 days ago)
  dmi.bios.date: 11/11/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WVG4110H.86A.0015.2010..1718
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DG41WV
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE90316-104
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrWVG4110H.86A.0015.2010..1718:bd11/11/2010:svn:pn:pvr:rvnIntelCorporation:rnDG41WV:rvrAAE90316-104:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1750532/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : 

[Touch-packages] [Bug 1715062] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for python-defaults 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 python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1715062

Title:
  package python-six 1.10.0-3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in python-defaults package in Ubuntu:
  Fix Released
Status in python-defaults source package in Xenial:
  Fix Released
Status in python-defaults source package in Zesty:
  Fix Committed

Bug description:
  SRU: Replacing the shebang from python to python2 should not have
  regression potential. The python2 symlink is available in xenial, and
  earlier releases (trusty, wily), so there shouldn't be any upgrade
  issues.

  
  kflkt

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-six 1.10.0-3
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Sep  5 06:44:23 2017
  Dependencies:

  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-08-03 (32 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: six
  Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1715062/+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 1591895] Re: SRU: backport python 2.7.12 to 16.04 LTS

[Launchpad Bug Tracker]

This bug was fixed in the package python-defaults - 2.7.12-1~16.04

---
python-defaults (2.7.12-1~16.04) xenial-proposed; urgency=medium

  * SRU.
  * Bump version to 2.7.12. LP: #1591895.
  * pycompile, pyclean, pyversions: Use python2 as the shebang to guard
against people fiddling around with the python symlink or having a
python3 installed as python in /usr/local. LP: #1715062.

 -- Matthias Klose   Thu, 23 Nov 2017 12:47:42 +0100

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

Title:
  SRU: backport python 2.7.12 to 16.04 LTS

Status in python-defaults package in Ubuntu:
  Fix Released
Status in python-stdlib-extensions package in Ubuntu:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python-defaults source package in Xenial:
  Fix Released
Status in python-stdlib-extensions source package in Xenial:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Released
Status in python-defaults source package in Zesty:
  New

Bug description:
  SRU: backport python 2.7.12 to 16.04 LTS

  The idea is to ship a released version with the first point release of
  16.04 LTS.  We updated python2.7 from the the 2.7 branch up to the
  final 2.7.12 release, and then made a test rebuild of the archive
  using the new python2.7 (and some other toolchain packages).

  The test rebuild was done using the release candidate of 2.7.12,
  however the only changes between the rc and the final release are
  Windows related, and include one change in the idle lib. From my point
  of view we don't need another test rebuild.

  The evaluation of the test rebuild is found in LP: #1586673. I'm
  pretty sure that none of the possible regressions can be attributed to
  the python2.7 update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1591895/+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 1591895] Re: SRU: backport python 2.7.12 to 16.04 LTS

[Launchpad Bug Tracker]

This bug was fixed in the package python-stdlib-extensions -
2.7.12-1~16.04

---
python-stdlib-extensions (2.7.12-1~16.04) xenial-proposed; urgency=medium

  * SRU: LP: #1591895. Backport 2.7.12 to 16.04 LTS.

 -- Matthias Klose   Thu, 23 Nov 2017 13:02:55 +0100

** Changed in: python-stdlib-extensions (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: python-defaults (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 python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1591895

Title:
  SRU: backport python 2.7.12 to 16.04 LTS

Status in python-defaults package in Ubuntu:
  Fix Released
Status in python-stdlib-extensions package in Ubuntu:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python-defaults source package in Xenial:
  Fix Released
Status in python-stdlib-extensions source package in Xenial:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Released
Status in python-defaults source package in Zesty:
  New

Bug description:
  SRU: backport python 2.7.12 to 16.04 LTS

  The idea is to ship a released version with the first point release of
  16.04 LTS.  We updated python2.7 from the the 2.7 branch up to the
  final 2.7.12 release, and then made a test rebuild of the archive
  using the new python2.7 (and some other toolchain packages).

  The test rebuild was done using the release candidate of 2.7.12,
  however the only changes between the rc and the final release are
  Windows related, and include one change in the idle lib. From my point
  of view we don't need another test rebuild.

  The evaluation of the test rebuild is found in LP: #1586673. I'm
  pretty sure that none of the possible regressions can be attributed to
  the python2.7 update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1591895/+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 1591895] Re: SRU: backport python 2.7.12 to 16.04 LTS

[Łukasz Zemczak]

I have checked all of the ADT regressions and confirmed that they're
either flaky tests or failing with the release pocket as well.

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

Title:
  SRU: backport python 2.7.12 to 16.04 LTS

Status in python-defaults package in Ubuntu:
  Fix Released
Status in python-stdlib-extensions package in Ubuntu:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python-defaults source package in Xenial:
  Fix Released
Status in python-stdlib-extensions source package in Xenial:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Released
Status in python-defaults source package in Zesty:
  New

Bug description:
  SRU: backport python 2.7.12 to 16.04 LTS

  The idea is to ship a released version with the first point release of
  16.04 LTS.  We updated python2.7 from the the 2.7 branch up to the
  final 2.7.12 release, and then made a test rebuild of the archive
  using the new python2.7 (and some other toolchain packages).

  The test rebuild was done using the release candidate of 2.7.12,
  however the only changes between the rc and the final release are
  Windows related, and include one change in the idle lib. From my point
  of view we don't need another test rebuild.

  The evaluation of the test rebuild is found in LP: #1586673. I'm
  pretty sure that none of the possible regressions can be attributed to
  the python2.7 update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1591895/+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 1715062] Re: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Launchpad Bug Tracker]

This bug was fixed in the package python-defaults - 2.7.12-1~16.04

---
python-defaults (2.7.12-1~16.04) xenial-proposed; urgency=medium

  * SRU.
  * Bump version to 2.7.12. LP: #1591895.
  * pycompile, pyclean, pyversions: Use python2 as the shebang to guard
against people fiddling around with the python symlink or having a
python3 installed as python in /usr/local. LP: #1715062.

 -- Matthias Klose   Thu, 23 Nov 2017 12:47:42 +0100

** Changed in: python-defaults (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 python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1715062

Title:
  package python-six 1.10.0-3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in python-defaults package in Ubuntu:
  Fix Released
Status in python-defaults source package in Xenial:
  Fix Released
Status in python-defaults source package in Zesty:
  Fix Committed

Bug description:
  SRU: Replacing the shebang from python to python2 should not have
  regression potential. The python2 symlink is available in xenial, and
  earlier releases (trusty, wily), so there shouldn't be any upgrade
  issues.

  
  kflkt

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-six 1.10.0-3
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Sep  5 06:44:23 2017
  Dependencies:

  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-08-03 (32 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: six
  Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1715062/+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 1750514] Re: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest

[Jean-Baptiste Lallement]

** Summary changed:

- 
/usr/sbin/cupsd:11:ippCopyAttribute:copy_attrs:copy_printer_attrs:get_printer_attrs:cupsdProcessIPPRequest
+ cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → 
get_printer_attrs → cupsdProcessIPPRequest

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

Title:
  cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs →
  get_printer_attrs → cupsdProcessIPPRequest

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
cups.  This problem was most recently seen with package version 2.2.6-5, the 
problem page at 
https://errors.ubuntu.com/problem/1b152bc770a7f1c23d7cae98db205bf7a7f45feb 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1750514/+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 1750514] Re: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest

[Jean-Baptiste Lallement]

** Changed in: cups (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs →
  get_printer_attrs → cupsdProcessIPPRequest

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
cups.  This problem was most recently seen with package version 2.2.6-5, the 
problem page at 
https://errors.ubuntu.com/problem/1b152bc770a7f1c23d7cae98db205bf7a7f45feb 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1750514/+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 1750514] Re: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs →
  get_printer_attrs → cupsdProcessIPPRequest

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
cups.  This problem was most recently seen with package version 2.2.6-5, the 
problem page at 
https://errors.ubuntu.com/problem/1b152bc770a7f1c23d7cae98db205bf7a7f45feb 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1750514/+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 1750514] [NEW] cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
cups.  This problem was most recently seen with package version 2.2.6-5, the 
problem page at 
https://errors.ubuntu.com/problem/1b152bc770a7f1c23d7cae98db205bf7a7f45feb 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: cups (Ubuntu)
 Importance: Medium
 Status: Confirmed


** Tags: artful bionic

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

Title:
  cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs →
  get_printer_attrs → cupsdProcessIPPRequest

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
cups.  This problem was most recently seen with package version 2.2.6-5, the 
problem page at 
https://errors.ubuntu.com/problem/1b152bc770a7f1c23d7cae98db205bf7a7f45feb 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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