[Touch-packages] [Bug 1750754] [NEW] package openssh-server 1:7.5p1-10ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Peter McLarty]

Public bug reported:

Not much to report there was an error when this package as to install in
the background

Description:Ubuntu 17.10
Release:17.10


openssh-server:
  Installed: 1:7.5p1-10ubuntu0.1
  Candidate: 1:7.5p1-10ubuntu0.1
  Version table:
 *** 1:7.5p1-10ubuntu0.1 500
500 http://au.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
100 /var/lib/dpkg/status
 1:7.5p1-10 500
500 http://au.archive.ubuntu.com/ubuntu artful/main amd64 Packages

This was automatically being updated and the error occurred

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: openssh-server 1:7.5p1-10ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
AptOrdering:
 chromium-codecs-ffmpeg-extra:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Feb 21 18:47:43 2018
DpkgHistoryLog:
 Start-Date: 2018-02-21  18:47:41
 Commandline: /usr/bin/unattended-upgrade
 Upgrade: chromium-codecs-ffmpeg-extra:amd64 (64.0.3282.140-0ubuntu0.17.10.1, 
64.0.3282.167-0ubuntu0.17.10.1)
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-11-03 (474 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
Missing privilege separation directory: /run/sshd
SourcePackage: openssh
Title: package openssh-server 1:7.5p1-10ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to artful on 2017-12-22 (61 days ago)

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


** Tags: amd64 apport-package artful

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

Title:
  package openssh-server 1:7.5p1-10ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  Not much to report there was an error when this package as to install
  in the background

  Description:  Ubuntu 17.10
  Release:  17.10

  
  openssh-server:
Installed: 1:7.5p1-10ubuntu0.1
Candidate: 1:7.5p1-10ubuntu0.1
Version table:
   *** 1:7.5p1-10ubuntu0.1 500
  500 http://au.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.5p1-10 500
  500 http://au.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  This was automatically being updated and the error occurred

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: openssh-server 1:7.5p1-10ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   chromium-codecs-ffmpeg-extra:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Feb 21 18:47:43 2018
  DpkgHistoryLog:
   Start-Date: 2018-02-21  18:47:41
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: chromium-codecs-ffmpeg-extra:amd64 (64.0.3282.140-0ubuntu0.17.10.1, 
64.0.3282.167-0ubuntu0.17.10.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-03 (474 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /run/sshd
  SourcePackage: openssh
  Title: package openssh-server 1:7.5p1-10ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to artful on 2017-12-22 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1750754/+subscriptions

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

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

[ChristianEhrhardt]

- Tested 2.10.95-0ubuntu2.9 from PPA (working as expected
- Added SRU Template
- Uploaded for consideration by the SRU team

** Description changed:

+ [Impact]
+ 
+  * The base abstraction in xenial  misses some ways programs can push 
+logs to journald
+ 
+  * Backport the fix form Artful to:
+1. get rid of the Denies making logs less readable
+2. get users to see the actual log entries will help to unbreak many 
+   other cases
+ 
+ [Test Case]
+ 
+  * Install one of the affected packages (in a xenial container is enough)
+  * For the case of ntp just install and then run
+systemctl restart ntp
+  * in Dmesg you'll see apparmor Denies like
+  apparmor="DENIED"
+  operation="file_inherit"
+  profile="/usr/sbin/ntpd" 
+  name="/run/systemd/journal/stdout"
+  * Each case is different, in this (ntp) case also some log entries are 
+missed due to the block
+  * After installing the fixed package there is no Deny anymore and 
+programs are able to correctly log.
+ 
+ [Regression Potential]
+ 
+  * The change is in ubuntu as-is since artful and we are only opening up, 
+but not limiting the access - so there should be nothing that is denied 
+after the update that was not before.
+Vice versa there could be changes due to things now working correcrly, 
+but I'd not see that as a regression.
+ 
+ [Other Info]
+  
+  * affects many packages ntp, tor - I even heard examples of mysql.
+But the fix is in apparmor through base abstraction
+ 
+ ---
+ 
  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.

-- 
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:
  [Impact]

   * The base abstraction in xenial  misses some ways programs can push 
 logs to journald

   * Backport the fix form Artful to:
 1. get rid of the Denies making logs less readable
 2. get users to see the actual log entries will help to unbreak many 
other cases

  [Test Case]

   * Install one of the affected packages (in a xenial container is enough)
   * For the case of ntp just install and then run
 systemctl restart ntp
   * in Dmesg you'll see apparmor Denies like
   apparmor="DENIED"
   operation="file_inherit"
   profile="/usr/sbin/ntpd" 
   name="/run/systemd/journal/stdout"
   * Each case is different, in this (ntp) case also some log entries are 
 missed due to the block
   * After installing the fixed package there is no Deny anymore and 
 programs are able to correctly log.

  [Regression Potential]

   * The change is in ubuntu as-is since artful and we are only opening up, 
 but not limiting the access - so there should be nothing that is denied 
 after the update that was not before.
 Vice versa there could be changes due to things now working correcrly, 
 but 

[Touch-packages] [Bug 1750754] Re: package openssh-server 1:7.5p1-10ubuntu0.1 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/1750754

Title:
  package openssh-server 1:7.5p1-10ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  Not much to report there was an error when this package as to install
  in the background

  Description:  Ubuntu 17.10
  Release:  17.10

  
  openssh-server:
Installed: 1:7.5p1-10ubuntu0.1
Candidate: 1:7.5p1-10ubuntu0.1
Version table:
   *** 1:7.5p1-10ubuntu0.1 500
  500 http://au.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.5p1-10 500
  500 http://au.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  This was automatically being updated and the error occurred

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: openssh-server 1:7.5p1-10ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   chromium-codecs-ffmpeg-extra:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Feb 21 18:47:43 2018
  DpkgHistoryLog:
   Start-Date: 2018-02-21  18:47:41
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: chromium-codecs-ffmpeg-extra:amd64 (64.0.3282.140-0ubuntu0.17.10.1, 
64.0.3282.167-0ubuntu0.17.10.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-03 (474 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /run/sshd
  SourcePackage: openssh
  Title: package openssh-server 1:7.5p1-10ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to artful on 2017-12-22 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1750754/+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 1750763] [NEW] local-premount/resume script broken, resume fails

[Bas Zoetekouw]

Public bug reported:

On bionic, the initramfs pre-mount/resume script contains this call to
/bin/resume:

   /bin/resume ${DEV}
 
Unfortunately, the ${DEV} variable is never set, causing all resumes to fail, 
with this error in initramfs.debug:

  + /scripts/local-premount/resume
  + PREREQ=
  + [ -z UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 ] 
  + [ ! -e /sys/power/resume ]
  + . /scripts/functions
  + . /scripts/local
  + wait-for-root UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 5
  + SWAPTYPE=swsuspend
  + [ -x /bin/plymouth ]
  + plymouth --ping
  + [ -n  ]
  + /bin/resume
  Usage: /bin/resume /dev/ [offset]

This seems a porting bug: the Debian version
(https://anonscm.debian.org/cgit/kernel/initramfs-tools.git/tree/scripts
/local-premount/resume) calls local_device_setup(), whioch sets DEV.
This call is missing in the Ubuntu (bionic, 0.130ubuntu2) version.

In my case, a simple

   DEV=$(resolve_device "${resume}")

also solved the issue, but I guess the Debian solution is nicer.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  local-premount/resume script broken, resume fails

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  On bionic, the initramfs pre-mount/resume script contains this call to
  /bin/resume:

 /bin/resume ${DEV}
   
  Unfortunately, the ${DEV} variable is never set, causing all resumes to fail, 
with this error in initramfs.debug:

+ /scripts/local-premount/resume
+ PREREQ=
+ [ -z UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 ] 
+ [ ! -e /sys/power/resume ]
+ . /scripts/functions
+ . /scripts/local
+ wait-for-root UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 5
+ SWAPTYPE=swsuspend
+ [ -x /bin/plymouth ]
+ plymouth --ping
+ [ -n  ]
+ /bin/resume
Usage: /bin/resume /dev/ [offset]

  This seems a porting bug: the Debian version
  (https://anonscm.debian.org/cgit/kernel/initramfs-
  tools.git/tree/scripts/local-premount/resume) calls
  local_device_setup(), whioch sets DEV.  This call is missing in the
  Ubuntu (bionic, 0.130ubuntu2) version.

  In my case, a simple

 DEV=$(resolve_device "${resume}")

  also solved the issue, but I guess the Debian solution is nicer.

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

** No longer affects: bluez

** Also affects: bluez via
   https://bugzilla.kernel.org/show_bug.cgi?id=198819
   Importance: Unknown
   Status: Unknown

-- 
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 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Alex Tu]

verified on Italia (201712-26024) with image X84, it passed with
pulseaudio/1:8.0-0ubuntu3.8

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

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Artful:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1750784] Re: lxc 1.0.10-0ubuntu1.1 ADT test failure with linux-lts-xenial 4.4.0-116.140~14.04.1

[Kleber Sacilotto de Souza]

Testcase fails with several network timeouts:

==
FAIL: lxc-tests: /usr/bin/lxc-test-autostart
---
Setting up the GPG keyring
ERROR: Unable to fetch GPG key from keyserver.
lxc_container: lxccontainer.c: create_run_template: 1092 container creation 
template for lxc-test-auto failed
lxc_container: lxc_create.c: main: 274 Error creating container lxc-test-auto
FAIL
---
==

==
failed to get 
https://cloud-images.ubuntu.com/query/trusty/server/daily-dl.current.txt
There is no download available for release=trusty, stream=daily, arch=ppc64el
lxc_container: lxccontainer.c: create_run_template: 1092 container creation 
template for 82ab30c7-13ae-4502-882e-d67e779b524a failed
lxc_container: lxc_create.c: main: 274 Error creating container 
82ab30c7-13ae-4502-882e-d67e779b524a
Failed creating ubuntu-cloud container
==

This is probably a proxy configuration issue on the test node. (same as
bug 1750778)

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

Title:
  lxc 1.0.10-0ubuntu1.1 ADT test failure with linux-lts-xenial
  4.4.0-116.140~14.04.1

Status in lxc package in Ubuntu:
  New

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/ppc64el/l/lxc/20180221_030606_7df34@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1750784/+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 1750784] [NEW] lxc 1.0.10-0ubuntu1.1 ADT test failure with linux-lts-xenial 4.4.0-116.140~14.04.1

[Kleber Sacilotto de Souza]

Public bug reported:

Testing failed on:
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/ppc64el/l/lxc/20180221_030606_7df34@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  lxc 1.0.10-0ubuntu1.1 ADT test failure with linux-lts-xenial
  4.4.0-116.140~14.04.1

Status in lxc package in Ubuntu:
  New

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/ppc64el/l/lxc/20180221_030606_7df34@/log.gz

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

[Bug Watch Updater]

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

-- 
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:
  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 1494804] Re: evolution-source-registry crashed with SIGABRT in g_assertion_message()

[Edson T. Marques]

Happen again!

** Attachment added: "_usr_lib_evolution_evolution-source-registry.1000.crash"
   
https://bugs.launchpad.net/evolution-data-server/+bug/1494804/+attachment/5059586/+files/_usr_lib_evolution_evolution-source-registry.1000.crash

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

Title:
  evolution-source-registry crashed with SIGABRT in
  g_assertion_message()

Status in evolution-data-server:
  Incomplete
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Random crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: evolution-data-server 3.16.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 11 16:29:44 2015
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2015-09-11 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150911)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  Signal: 6
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   e_source_get_extension () from /usr/lib/libedataserver-1.2.so.20
   ?? () from /usr/lib/libebackend-1.2.so.10
  Title: evolution-source-registry crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1494804/+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 1494804] Re: evolution-source-registry crashed with SIGABRT in g_assertion_message()

[Sebastien Bacher]

What are you doing in bionic to trigger the issue?

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

Title:
  evolution-source-registry crashed with SIGABRT in
  g_assertion_message()

Status in evolution-data-server:
  Incomplete
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Random crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: evolution-data-server 3.16.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 11 16:29:44 2015
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2015-09-11 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150911)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  Signal: 6
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   e_source_get_extension () from /usr/lib/libedataserver-1.2.so.20
   ?? () from /usr/lib/libebackend-1.2.so.10
  Title: evolution-source-registry crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1494804/+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

[Hans Joachim Desserud]

** Tags added: xenial

-- 
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 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]

v231 networkd changes have been introduced in xenial long time ago, and
the referenced patch appears to have been in xenial's networkd for a
long while now.

If this bug is not resolved for you, please reopen it.

** Changed in: systemd (Ubuntu Xenial)
   Status: In Progress => 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/1634855

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

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

Bug description:
  [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.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634855/+subscriptions

-- 
Mailing list: https

[Touch-packages] [Bug 1750379] Re: Distortion Realtek ALC887

[fleamour]

Can confirm kernel makes no difference, also present in 17.10.1 &
!6.04.3.

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

[Dimitri John Ledkov]

** Description changed:

+ [Impact]
+ 
+  * When a container is presented with a unified cgroup hierarchy, which
+ is not properly delegated, systemd should not attempt (and fail) to use.
+ This improves compatibility of xenial containers running on unified
+ cgroup hierarchy hosts.
+ 
+ [Test Case]
+ 
+  * Xenial containers should boot, with non-writable unified cgroup
+ hierarchy hosts.
+ 
+ [Regression Potential]
+ 
+  * unified cgroup hierarchy is not in use by default on xenial hosts,
+ thus this is forward compatibility improvment with e.g. bionic hosts
+ running xenial containers.
+ 
+ [Other Info]
+  
+  * Original bug report
+ 
  Hey everyone,
  
  Current systemd versions all fail when the unified cgroup hierarchy is
  not-writable. This is especially problematic in containers where the
  systemd administrator might decide to not delegate the unified hierarchy
  or when running with a liblxc driver that doesn't yet know how to handle
  the unified cgroup hierarchy. I've pushed patches to systemd upstream
  that let systemd ingnore the non-delegated unified hierarchy. The
  relevant commits are:
  
  e07aefbd675b651f8d45b5fb458f2747b04d6e04
  2d56b80a1855836abf1d7458394c345ad9d55382
  1ff654e28b7b8e7d0a0be33522a84069ac6b07c0
  
  These patches will be in 236 but should be backported from xenial
  upwards.
  
  Christian

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

Title:
  systemd: handle undelegated cgroup2 hierarchy

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

Bug description:
  [Impact]

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

  [Test Case]

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

  [Regression Potential]

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

  [Other Info]
   
   * Original bug report

  Hey everyone,

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

  e07aefbd675b651f8d45b5fb458f2747b04d6e04
  2d56b80a1855836abf1d7458394c345ad9d55382
  1ff654e28b7b8e7d0a0be33522a84069ac6b07c0

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

  Christian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734410/+subscriptions

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

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

[Dimitri John Ledkov]

** Description changed:

+ [Impact]
+ 
+  * systemd-sysctl service fails in containers, due to read-only sysfs,
+ which is normal.
+ 
+ [Test Case]
+ 
+  * Ensure systemd-sysctl is successful in containers, e.g. lxc & lxd
+ 
+ [Regression Potential]
+ 
+  * The application of sysctls fails anyway, but at least in this case
+ false-errors are not reported and the container doesn't enter "degraded"
+ state without a good reason.
+ 
+ [Other Info]
+  
+  * Original bug report
+ 
  Hi everyone,
  
  systemd-sysctl in systemd versions prior to 232 will exit with FAILED
  when not being able to apply kernel variables. In containers it should
  simply move on and exit with SUCCESS. Upstream systemd carries
  appropriate patches for this already. The relevant commits are:
  
  411e869f497c7c7bd0688f1e3500f9043bc56e48
  39540de8abe24886693ca29a9caeea85c88089aa
  
  these should be backported to xenial's systemd.
  
  Christian

-- 
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:
  [Impact]

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

  [Test Case]

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

  [Regression Potential]

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

  [Other Info]
   
   * Original bug report

  Hi everyone,

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

  411e869f497c7c7bd0688f1e3500f9043bc56e48
  39540de8abe24886693ca29a9caeea85c88089aa

  these should be backported to xenial's systemd.

  Christian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734409/+subscriptions

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

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

[Dimitri John Ledkov]

I'm slightly perplexed if this is needed in xenial or not.

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

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

Title:
  systemd: handle undelegated cgroup2 hierarchy

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

Bug description:
  [Impact]

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

  [Test Case]

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

  [Regression Potential]

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

  [Other Info]
   
   * Original bug report

  Hey everyone,

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

  e07aefbd675b651f8d45b5fb458f2747b04d6e04
  2d56b80a1855836abf1d7458394c345ad9d55382
  1ff654e28b7b8e7d0a0be33522a84069ac6b07c0

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

  Christian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734410/+subscriptions

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

[Touch-packages] [Bug 1750641] [NEW] vlc/twm/bionic don't interoperate

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

vlc/twm/xenial no problem.
vlc/twm/bionic can't adjust time slider.
vlc/lubuntu/bionic no problem.

When positioning the pointer over the time slider, a little window
appears showing the time under the pointer.  With the vlc/twm/bionic
combination, that little window has a title bar containing "Untitled",
thus the little window hangs down over the time slider, and moves with
the pointer, so clicking on the time slider is impossible.

i doubt twm has changed in years.  That's one of the benefits of using
it.  Along with microscopic footprint, several features still
unimplemented in any other window manager, and still considered the
reference standard window manager implementation for xorg.

my bionic install currently has a networking issue (bug 1748409), so i
filed this bug under xenial, but the bug is in bionic, not xenial.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: vlc 2.2.2-5ubuntu0.16.04.4
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: Tue Feb 20 13:07:55 2018
InstallationDate: Installed on 2016-10-15 (492 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
SourcePackage: vlc
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic
-- 
vlc/twm/bionic don't interoperate
https://bugs.launchpad.net/bugs/1750641
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu.

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

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

[Chris J Arges]

Hello Robie, or anyone else affected,

Accepted apparmor into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.9 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: apparmor (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
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:
  Fix Committed

Bug description:
  [Impact]

   * The base abstraction in xenial  misses some ways programs can push 
 logs to journald

   * Backport the fix form Artful to:
 1. get rid of the Denies making logs less readable
 2. get users to see the actual log entries will help to unbreak many 
other cases

  [Test Case]

   * Install one of the affected packages (in a xenial container is enough)
   * For the case of ntp just install and then run
 systemctl restart ntp
   * in Dmesg you'll see apparmor Denies like
   apparmor="DENIED"
   operation="file_inherit"
   profile="/usr/sbin/ntpd" 
   name="/run/systemd/journal/stdout"
   * Each case is different, in this (ntp) case also some log entries are 
 missed due to the block
   * After installing the fixed package there is no Deny anymore and 
 programs are able to correctly log.

  [Regression Potential]

   * The change is in ubuntu as-is since artful and we are only opening up, 
 but not limiting the access - so there should be nothing that is denied 
 after the update that was not before.
 Vice versa there could be changes due to things now working correcrly, 
 but I'd not see that as a regression.

  [Other Info]
   
   * affects many packages ntp, tor - I even heard examples of mysql.
 But the fix is in apparmor through base abstraction

  ---

  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-packa

[Touch-packages] [Bug 1750641] Re: vlc/twm/bionic don't interoperate

[Sebastian Ramacher]

Reassigned accordingly.

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

** Package changed: vlc (Ubuntu) => qtbase-opensource-src (Ubuntu)

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

Title:
  vlc/twm/bionic don't interoperate

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in twm package in Ubuntu:
  New

Bug description:
  vlc/twm/xenial no problem.
  vlc/twm/bionic can't adjust time slider.
  vlc/lubuntu/bionic no problem.

  When positioning the pointer over the time slider, a little window
  appears showing the time under the pointer.  With the vlc/twm/bionic
  combination, that little window has a title bar containing "Untitled",
  thus the little window hangs down over the time slider, and moves with
  the pointer, so clicking on the time slider is impossible.

  i doubt twm has changed in years.  That's one of the benefits of using
  it.  Along with microscopic footprint, several features still
  unimplemented in any other window manager, and still considered the
  reference standard window manager implementation for xorg.

  my bionic install currently has a networking issue (bug 1748409), so i
  filed this bug under xenial, but the bug is in bionic, not xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vlc 2.2.2-5ubuntu0.16.04.4
  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: Tue Feb 20 13:07:55 2018
  InstallationDate: Installed on 2016-10-15 (492 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1750641/+subscriptions

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

Re: [Touch-packages] [Bug 1750654] [NEW] "lxc-create -B best" fails on non-btrfs/zfs system

[Christian Brauner]

On Tue, Feb 20, 2018 at 08:43:41PM -, Martin Pitt wrote:
> 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:

Hm, is it possible for you to try and reproduce with current master.
Works fine for me:

chb@conventiont|~
> sudo lxc-create -B best --name=autopkgtest-xenial -t ubuntu -- -r xenial
lxc-create: autopkgtest-xenial: storage/btrfs.c: btrfs_create: 861 
Inappropriate ioctl for device - Failed to create btrfs subvolume 
"/var/lib/lxc/autopkgtest-xenial/rootfs"
lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_create: 762 Failed to create 
zfs dataset "zfs:default/lxc/autopkgtest-xenial": The ZFS modules are not 
loaded.
Try running '/sbin/modprobe zfs' as root to load them.
lxc-create: autopkgtest-xenial: storage/lvm.c: do_lvm_create: 183 Failed to 
create logical volume "autopkgtest-xenial":   Volume group "lvm_img" not found
lxc-create: autopkgtest-xenial: storage/lvm.c: lvm_create: 655 Error creating 
new logical volume "lvm:/dev/lvm_img/autopkgtest-xenial" of size "1073741824 
bytes"
Checking cache download in /var/cache/lxc/xenial/rootfs-amd64 ...
Installing packages in template: apt-transport-https,ssh,vim,language-pack-en
Downloading ubuntu xenial minimal ...
W: Target architecture is the same as host architecture; disabling QEMU support
I: Running command: debootstrap --arch amd64 --verbose 
--components=main,universe 
--include=apt-transport-https,ssh,vim,language-pack-en xenial 
/var/cache/lxc/xenial/partial-amd64 http://archive.ubuntu.com/ubuntu
I: Retrieving InRelease
I: Checking Release signature
I: Valid Release signature (key id 790BC7277767219C42C86F933B4FE6ACC0B21F32)
I: Retrieving Packages
I: Validating Packages
I: Retrieving Packages

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

[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Yovan Zhuo Jiawan]

Update: running 'unity' seems to make it work for now.

-- 
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 1750741] Re: Memory leak in g_dbus_proxy_new_for_bus_sync()

[Dan Streetman]

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

-- 
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
Status in glib2.0 source package in Trusty:
  New

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 1750115] Re: libsqlite3-dev package missing on zesty

[Hans Joachim Desserud]

Thank you for reporting this issue to Ubuntu.

Zesty (17.04) reached EOL on January 13, 2018. The repositories that you are 
trying to download from have long since been moved.
See this document for currently supported Ubuntu releases: 
https://wiki.ubuntu.com/Releases
See also https://help.ubuntu.com/community/EOLUpgrades

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

** Tags added: zesty

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

Title:
  libsqlite3-dev package missing on zesty

Status in sqlite3 package in Ubuntu:
  Invalid

Bug description:
  I'm trying to install libsqlite3-dev on zesty and it seems to have
  gone missing.  At the time of writing all the links on
  https://packages.ubuntu.com/zesty/amd64/libsqlite3-dev/download give
  me a 404.

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

[Dan Streetman]

Seyeong, the debdiff patch is very large, and contains more than just
the 1-line memleak fix from the description...can you remove the extra
changes from the debdiff so it only contains the memleak patch?  Or
explain why the other changes are needed?

** Tags added: sts-sponsor-ddstreet

-- 
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
Status in glib2.0 source package in Trusty:
  New

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 1316970] Re: g_dbus memory leak in lrmd

[Dan Streetman]

glib2.0 memleak patch moved over to bug 1750741


** No longer affects: glib2.0 (Ubuntu)

** No longer affects: glib2.0 (Ubuntu Trusty)

-- 
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 pacemaker package in Ubuntu:
  Fix Released
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 >> 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.

  [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 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/pacemaker/+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 1750832] [NEW] xorg crash after coming from suspend

[anirudha banerjee]

Public bug reported:

The problem i'm facing is, whenever my system revives back from
suspended state, xorg crashes and i have restart all the applications
that were running in the previous xorg session.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.15.3-041503-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.6)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed Feb 21 19:42:44 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
   Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
InstallationDate: Installed on 2017-08-15 (189 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: ASUSTeK COMPUTER INC. GL553VD
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.3-041503-generic 
root=UUID=ae3afa91-6139-4a8a-a15b-39b661535c3a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/06/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL553VD.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL553VD
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.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: GL
dmi.product.name: GL553VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.3+16.04.20171116-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.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Feb 21 19:23:46 2018
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  xorg crash after coming from suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  The problem i'm facing is, whenever my system revives back from
  suspended state, xorg crashes and i have restart all the applications
  that were running in the previous xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.15.3-041503-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.6)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Feb 21 19:42:44 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
 Subs

[Touch-packages] [Bug 1747460] Re: [MIR] py-macaroon-bakery, protobuf, pyrfc3339

[Andres Rodriguez]

Added a team subscriber


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

-- 
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:
  New

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 1631241] Re: Name resolution stops working after resume from suspend

[Adriano dos Santos Fernandes]

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

Is the fix released to Xenial or not? I'm having this problem from years
already...

And I'm with Xenial still having the problem.

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

Title:
  Name resolution stops working after resume from suspend

Status in dnsmasq:
  Fix Released
Status in dnsmasq package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
  suspend DNS resolution stops working.

  * Also affect Xenial (Unity/GnomeFlashback)since Network-Manager stack
  was upgraded to 1.2.6.

  After resuming, systemd-resolved is running and libnss-resolve is
  installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
  name server. The dnsmasq-base package is installed since it is pulled
  in by both network-manager and lxc1, and both NM and libvirt have
  spawned instances of dnsmasq:

  >  1155 pts/2S+ 0:00 grep dnsmasq
  >  2724 ?S  0:00 dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
  >  2992 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  >  2993 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  > 22879 ?S  0:00 /usr/sbin/dnsmasq --no-resolv 
--keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d

  Let me know if you need any extra info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 13:52:40 2016
  InstallationDate: Installed on 2015-07-22 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dnsmasq/+bug/1631241/+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 1750851] [NEW] re-add cloud-initramfs-dyn-netconf to ubuntu-server

[Scott Moser]

Public bug reported:

I (smoser) removed cloud-initramfs-dyn-netconf from ubuntu-server meta
package.  That package provides functionality needed by MAAS and cause bug
1748875.  Under that bug we re-added cloud-initramfs-dyn-netconf to the
initramfs that MAAS publishes.

We subsequently saw failure in open-iscsi tests, which utilize that same
function.

My commit message to the fix of maas-images is below for informational
purposes [1]:
  [1] 
https://code.launchpad.net/~smoser/maas-images/trunk.lp1749019-re-add-cloud-intramfs-dyn-netconf/+merge/337605

'b' is *also* used by the open-iscsi use case.  It boots with a slightly
different form than maas images:
  BOOTIF_DEFAULT=eth0 and ip=:name:BOOTIF

Here, 'BOOTIF' will be replaced with 'eth0'.

| Re-add cloud-initramfs-dyn-netconf. Needed by maas for BOOTIF in ip=.
|
| The previous commit to trunk dropped cloud-initramfs-dyn-netconf from
| the maas image in releases newer than xenial.
| 
| That caused errors in MAAS. cloud-initramfs-dyn-netconf does 2 things:
| a.) writes /run/network/dynamic-interfaces
| this is a ENI style file with data retrived from ipconfig
| b.) convert 'BOOTIF' string in the value of IP
|   Example:
| ip=foobar:BOOTIF BOOTIF=01-00-22-68-10-c1-e6
|   will be effectively rendered as:
| ip=foobar:eth0
|
| 'b' is still required by maas.
|
| Note: in maas v3 images, the squashfs image is re-used pristine
| from cloud-images. Because of this, the installation into the image
| affects initramfs creation, but does not affect the image. That is
| correct in that this package is not needed in the image but only
| in the initramfs.

Related bugs:
 * bug 1748875:  Unable to deploy Bionic on bare-metals with MaaS 2.3.0

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  re-add cloud-initramfs-dyn-netconf to ubuntu-server

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I (smoser) removed cloud-initramfs-dyn-netconf from ubuntu-server meta
  package.  That package provides functionality needed by MAAS and cause bug
  1748875.  Under that bug we re-added cloud-initramfs-dyn-netconf to the
  initramfs that MAAS publishes.

  We subsequently saw failure in open-iscsi tests, which utilize that same
  function.

  My commit message to the fix of maas-images is below for informational
  purposes [1]:
[1] 
https://code.launchpad.net/~smoser/maas-images/trunk.lp1749019-re-add-cloud-intramfs-dyn-netconf/+merge/337605

  'b' is *also* used by the open-iscsi use case.  It boots with a slightly
  different form than maas images:
BOOTIF_DEFAULT=eth0 and ip=:name:BOOTIF

  Here, 'BOOTIF' will be replaced with 'eth0'.

  | Re-add cloud-initramfs-dyn-netconf. Needed by maas for BOOTIF in ip=.
  |
  | The previous commit to trunk dropped cloud-initramfs-dyn-netconf from
  | the maas image in releases newer than xenial.
  | 
  | That caused errors in MAAS. cloud-initramfs-dyn-netconf does 2 things:
  | a.) writes /run/network/dynamic-interfaces
  | this is a ENI style file with data retrived from ipconfig
  | b.) convert 'BOOTIF' string in the value of IP
  |   Example:
  | ip=foobar:BOOTIF BOOTIF=01-00-22-68-10-c1-e6
  |   will be effectively rendered as:
  | ip=foobar:eth0
  |
  | 'b' is still required by maas.
  |
  | Note: in maas v3 images, the squashfs image is re-used pristine
  | from cloud-images. Because of this, the installation into the image
  | affects initramfs creation, but does not affect the image. That is
  | correct in that this package is not needed in the image but only
  | in the initramfs.

  Related bugs:
   * bug 1748875:  Unable to deploy Bionic on bare-metals with MaaS 2.3.0

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

Xenial as is on ntp restart:
[2618636.253807] audit: type=1400 audit(1519220834.240:5311): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-x_" 
profile="/usr/sbin/ntpd" name="/run/systemd/journal/stdout" pid=24452 
comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=100 ouid=100
[2618636.253817] audit: type=1400 audit(1519220834.240:5312): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-x_" 
profile="/usr/sbin/ntpd" name="/run/systemd/journal/stdout" pid=24452 
comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=100 ouid=100

With updates from proposed
# sudo apt install apparmor
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'sudo apt autoremove' to remove it.
Suggested packages:
  apparmor-profiles apparmor-profiles-extra apparmor-docs apparmor-utils
The following packages will be upgraded:
  apparmor
1 upgraded, 0 newly installed, 0 to remove and 29 not upgraded.
Need to get 450 kB of archives.
After this operation, 1024 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 apparmor 
amd64 2.10.95-0ubuntu2.9 [450 kB]
Fetched 450 kB in 0s (2291 kB/s)
Preconfiguring packages ...
(Reading database ... 25611 files and directories currently installed.)
Preparing to unpack .../apparmor_2.10.95-0ubuntu2.9_amd64.deb ...
Unpacking apparmor (2.10.95-0ubuntu2.9) over (2.10.95-0ubuntu2.8) ...
Processing triggers for systemd (229-4ubuntu21.1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up apparmor (2.10.95-0ubuntu2.9) ...
Installing new version of config file /etc/apparmor.d/abstractions/base ...
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd


# No issues anymore when restarting the service.
Also found no other apparmor related issues restarting a few services that I 
had on there.

** Tags removed: verification-needed verification-needed-xenial
** 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 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:
  Fix Committed

Bug description:
  [Impact]

   * The base abstraction in xenial  misses some ways programs can push 
 logs to journald

   * Backport the fix form Artful to:
 1. get rid of the Denies making logs less readable
 2. get users to see the actual log entries will help to unbreak many 
other cases

  [Test Case]

   * Install one of the affected packages (in a xenial container is enough)
   * For the case of ntp just install and then run
 systemctl restart ntp
   * in Dmesg you'll see apparmor Denies like
   apparmor="DENIED"
   operation="file_inherit"
   profile="/usr/sbin/ntpd" 
   name="/run/systemd/journal/stdout"
   * Each case is different, in this (ntp) case also some log entries are 
 missed due to the block
   * After installing the fixed package there is no Deny anymore and 
 programs are able to correctly log.

  [Regression Potential]

   * The change is in ubuntu as-is since artful and we are only opening up, 
 but not limiting the access - so there should be nothing that is denied 
 after the update that was not before.
 Vice versa there could be changes due to things now working correcrly, 
 but I'd not see that as a regression.

  [Other Info]
   
   * affects many packages ntp, tor - I even heard examples of mysql.
 But the fix is in apparmor through base abstraction

  ---

  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" 

[Touch-packages] [Bug 1750379] Re: Distortion Realtek ALC887

[fleamour]

Just by way of reference it is present in pretty much all modern
distros.

-- 
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 1750610] Re: cupsd crashed with SIGSEGV in ippCopyAttribute()

[Jean-Baptiste Lallement]

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

** This bug is no longer a duplicate of private bug 1750603
** This bug has been marked a duplicate of bug 1750514
   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/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 1750603] Re: cupsd crashed with SIGSEGV in ippCopyAttribute()

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1750514
   cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → 
get_printer_attrs → cupsdProcessIPPRequest

** Information type changed from Private to Public

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

Title:
  cupsd crashed with SIGSEGV in ippCopyAttribute()

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  The CUPS Daemon crashed when my machine is connected to a rather large
  corporate network.

  I was not using CUPS nor printing anything.

  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
  CrashCounter: 1
  Date: Tue Feb 20 09:56:44 2018
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2013-12-27 (1515 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: TOSHIBA SATELLITE L50-A-1CU
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=392cca54-560c-4712-be6b-586150b9b6ad ro quiet splash vt.handoff=1
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=392cca54-560c-4712-be6b-586150b9b6ad ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x7fda912e8db3 : addl   
$0x1,0x38(%rdx)
   PC (0x7fda912e8db3) 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-02-09 (10 days ago)
  UserGroups:
   
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSATELLITEL50-A-1CU:pvrPSKK6E-03M06DIT:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: SATELLITE L50-A-1CU
  dmi.product.version: PSKK6E-03M06DIT
  dmi.sys.vendor: TOSHIBA
  modified.conffile..etc.default.cups: [deleted]
  modified.conffile..etc.init.cups.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1750603/+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 1750851] Re: re-add cloud-initramfs-dyn-netconf to ubuntu-server

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/ubuntu-seeds/ubuntu.bionic

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

Title:
  re-add cloud-initramfs-dyn-netconf to ubuntu-server

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I (smoser) removed cloud-initramfs-dyn-netconf from ubuntu-server meta
  package.  That package provides functionality needed by MAAS and cause bug
  1748875.  Under that bug we re-added cloud-initramfs-dyn-netconf to the
  initramfs that MAAS publishes.

  We subsequently saw failure in open-iscsi tests, which utilize that same
  function.

  My commit message to the fix of maas-images is below for informational
  purposes [1]:
[1] 
https://code.launchpad.net/~smoser/maas-images/trunk.lp1749019-re-add-cloud-intramfs-dyn-netconf/+merge/337605

  'b' is *also* used by the open-iscsi use case.  It boots with a slightly
  different form than maas images:
BOOTIF_DEFAULT=eth0 and ip=:name:BOOTIF

  Here, 'BOOTIF' will be replaced with 'eth0'.

  | Re-add cloud-initramfs-dyn-netconf. Needed by maas for BOOTIF in ip=.
  |
  | The previous commit to trunk dropped cloud-initramfs-dyn-netconf from
  | the maas image in releases newer than xenial.
  | 
  | That caused errors in MAAS. cloud-initramfs-dyn-netconf does 2 things:
  | a.) writes /run/network/dynamic-interfaces
  | this is a ENI style file with data retrived from ipconfig
  | b.) convert 'BOOTIF' string in the value of IP
  |   Example:
  | ip=foobar:BOOTIF BOOTIF=01-00-22-68-10-c1-e6
  |   will be effectively rendered as:
  | ip=foobar:eth0
  |
  | 'b' is still required by maas.
  |
  | Note: in maas v3 images, the squashfs image is re-used pristine
  | from cloud-images. Because of this, the installation into the image
  | affects initramfs creation, but does not affect the image. That is
  | correct in that this package is not needed in the image but only
  | in the initramfs.

  Related bugs:
   * bug 1748875:  Unable to deploy Bionic on bare-metals with MaaS 2.3.0

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

[Jean-Baptiste Lallement]

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

** Information type changed from Private to Public

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

Title:
  cupsd crashed with SIGSEGV in ippCopyAttribute()

Status in cups package in Ubuntu:
  New

Bug description:
  no idea, sorry

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  Uname: Linux 4.15.3-041503-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CupsErrorLog:
   E [20/Feb/2018:00:08:11 +0100] Filter \"brftopagedbrf\" not found.
   E [20/Feb/2018:00:08:11 +0100] Filter \"brftopagedbrf\" not found.
   E [20/Feb/2018:01:02:30 +0100] Filter \"brftopagedbrf\" not found.
   E [20/Feb/2018:01:02:30 +0100] Filter \"brftopagedbrf\" not found.
  Date: Sun Feb 18 19:21:03 2018
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2017-10-31 (111 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lpstat:
   device for CUPS-BRF-Printer: cups-brf:/
   device for PDF: cups-pdf:/
   device for Samsung_C460_Series_SEC001599EC1A13_: 
ipp://SEC001599EC1A13.local:631/ipp/printer
  MachineType: LENOVO 7458E44
  Papersize: a4
  PpdFiles:
   PDF: Generic CUPS-PDF Printer (w/ options)
   Samsung_C460_Series_SEC001599EC1A13_: C460 Series
   CUPS-BRF-Printer: Generic Text-Only Printer
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.3-041503-generic 
root=/dev/mapper/ubuntu--vg-root ro kopt=root=/dev/mapper/vgubuntu-root noquiet 
nosplash
  ProcEnviron:
   LANG=de_CH.UTF-8
   LANGUAGE=de_CH:de
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.3-041503-generic 
root=/dev/mapper/ubuntu--vg-root ro kopt=root=/dev/mapper/vgubuntu-root noquiet 
nosplash
  SegvAnalysis:
   Segfault happened at: 0x7fb16af0fdb3 : addl   
$0x1,0x38(%rdx)
   PC (0x7fb16af0fdb3) 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-02-05 (14 days ago)
  UserGroups:
   
  dmi.bios.date: 09/07/2016
  dmi.bios.vendor: coreboot
  dmi.bios.version: CBET4000 370b885
  dmi.board.name: 7458E44
  dmi.board.vendor: LENOVO
  dmi.board.version: ThinkPad X200
  dmi.chassis.type: 9
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvncoreboot:bvrCBET4000370b885:bd09/07/2016:svnLENOVO:pn7458E44:pvrThinkPadX200:rvnLENOVO:rn7458E44:rvrThinkPadX200:cvnLENOVO:ct9:cvr:
  dmi.product.name: 7458E44
  dmi.product.version: ThinkPad X200
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1750470/+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 1750784] Re: lxc 1.0.10-0ubuntu1.1 ADT test failure with linux-lts-xenial 4.4.0-116.140~14.04.1

[Stéphane Graber]

Yeah, that's a network issue, bouncing it usually makes it pass
eventually.

http://autopkgtest.ubuntu.com/packages/l/lxc/trusty/amd64 shows recent
success there.

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

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

Title:
  lxc 1.0.10-0ubuntu1.1 ADT test failure with linux-lts-xenial
  4.4.0-116.140~14.04.1

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/ppc64el/l/lxc/20180221_030606_7df34@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1750784/+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 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Scott Moser]

Hi,

cloud-init has never updated resolv.conf directly.
/etc/resolv.conf in 16.04 is managed via resolvconf through 
/etc/network/interfaces.
/etc/resolv.conf in 18.04 is managed via systemd-resolve (netplan -> 
systemd-networkd -> systemd-resolve).

Can you provide the content of:
   systemd-resolve --status --no-pager

And does this happen in the ephemeral environment, the installed
environment, or both?

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Invalid
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas

  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 10.90.90.1
  search maaslab maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+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 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Andres Rodriguez]

ubuntu@node03:~$ systemd-resolve --status --no-pager
Global
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 3 (br0)
  Current Scopes: LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 2 (enp0s25)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.90.90.1
  DNS Domain: maaslab
  maas

** Description changed:

  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see that
  netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.
  
  Resolv.conf should really be configured to use the provided DNS
- server(s)
+ server(s). That said, despite that fact, DNS resolution doesn't work
+ with the local address.
  
  Bionic
  --
  
  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53
  
  search maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution
  
- 
  [...]
- 
  
  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1
  
  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms
  
  =
  Xenial
  ==
  
  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas
  
  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 10.90.90.1
  search maaslab maas

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

[Touch-packages] [Bug 1750889] Re: GNOME Terminal scrollbar looks weird on clean GNOME session under Wayland

[AsciiWolf]

** Attachment added: "gnome_terminal_2.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1750889/+attachment/5059915/+files/gnome_terminal_2.png

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

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

Title:
  GNOME Terminal scrollbar looks weird on clean GNOME session under
  Wayland

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  When using a clean GNOME session (with Adwaita theme) in combination
  with Wayland, the scrollbar in GNOME Terminal looks weird (see
  screenshot 1). The window also looks like it does not have a focus,
  but it does. Clicking anywhere on the menu bar fixes the focus issue,
  but the scrollbar still looks weird (see screenshot 2).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1750889/+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 1750884] [NEW] [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Andres Rodriguez]

Public bug reported:

When deploying Bionic, /etc/resolv.conf is not configured correctly,
which leads to no DNS resolution. In the output below, you will see that
netplan config is correctly to the 10.90.90.1 nameserver, but in
resolv.conf that's a local address.

Resolv.conf should really be configured to use the provided DNS
server(s). That said, despite that fact, DNS resolution doesn't work
with the local address.

Bionic
--

ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by
# the datasource.  Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
enp0s25:
match:
macaddress: b8:ae:ed:7d:17:d2
mtu: 1500
nameservers:
addresses:
- 10.90.90.1
search:
- maaslab
- maas
set-name: enp0s25
bridges:
br0:
addresses:
- 10.90.90.3/24
gateway4: 10.90.90.1
interfaces:
- enp0s25
parameters:
forward-delay: 15
stp: false
ubuntu@node01:~$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53

search maaslab maas
ubuntu@node01:~$ ping google.com
ping: google.com: Temporary failure in name resolution

[...]

ubuntu@node01:~$ sudo vim /etc/resolv.conf
ubuntu@node01:~$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 10.90.90.1

search maaslab maas
ubuntu@node01:~$ ping google.com
PING google.com (172.217.0.174) 56(84) bytes of data.
64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

=
Xenial
==

ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource.  Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
dns-nameservers 10.90.90.1
dns-search maaslab maas

auto enp0s25
iface enp0s25 inet static
address 10.90.90.162/24
gateway 10.90.90.1
mtu 1500
ubuntu@node05:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.90.90.1
search maaslab maas

** Affects: cloud-init
 Importance: Undecided
 Status: New

** Affects: maas
 Importance: Undecided
 Status: Invalid

** Affects: nplan (Ubuntu)
 Importance: Critical
 Status: New

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

** Also affects: cloud-init
   Importance: Undecided
   Status: New

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

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

** Changed in: nplan (Ubuntu)
   Importance: Undecided => Critical

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Critical

** Changed in: maas
   Status: New => Incomplete

** Changed in: maas
   Status: Incomplete => Invalid

** Description changed:

  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see that
  netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.
  
+ Resolv.conf should really be configured to use the provided DNS
+ server(s)
  
  Bionic
  --
  
  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
- version: 2
- ethernets:
- enp0s25:
- match:
- macaddress: b8:ae:ed:7d:17:d2
- mtu: 1500
- nameservers:
- addresses:
- - 10.90.90.1
- search:
- -

[Touch-packages] [Bug 1750883] [NEW] X session does no more start after upgrade - hybrid-gfx no such file or directory

[Dash]

Public bug reported:

Hi,

Xorg.log finish with

[   104.348] (II) config/udev: Adding input device HID 046d:c31b 
(/dev/input/mouse0)
[   104.348] (II) No input driver specified, ignoring this device.
init: Failed to spawn hybrid-gfx main process: unable to execute: No such file 
or directory

as previous one which started OK finished with

[87.952] (II) config/udev: Adding input device HID 046d:c31b 
(/dev/input/mouse0) 
 
[87.952] (II) No input driver specified, ignoring this device. 
[87.952] (II) This device may have been added with another device file. 

  
[   101.619] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-79DA8A0BAEB4CF1B2497C5C30BA2CA0B8D85.xkm
 
[   101.629] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-79DA8A0BAEB4CF1B2497C5C30BA2CA0B8D85.xkm
 
[   103.104] (II) evdev: HID 046d:c31b: Close   

  
[   103.104] (II) UnloadModule: "evdev" 

  
[   103.104] (II) evdev: HID 046d:c31b: Close   

  
[   103.104] (II) UnloadModule: "evdev" 

  
[   103.104] (II) evdev: HID 046d:c31b: Close   

  
[   103.104] (II) UnloadModule: "evdev" 

  
[   103.104] (II) evdev: Power Button: Close

  
[   103.104] (II) UnloadModule: "evdev" 

  
[   103.428] (II) MGA(0): UNMAPPING framebuffer 0x7F8E49569000, 0x7F.   

  
[   103.483] (EE) Server terminated successfully (0). Closing log file. 

/etc/init/hybrid-gfx.conf
start on (starting lightdm
  or starting kdm
  or starting xdm
  or starting lxdm)
task
exec hybrid-detect

But no hybrid-detect script or binary

dh@srvfwstr:/etc/init$ lsb_release -rd
Description:Ubuntu 14.04.5 LTS
Release:14.04

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Wed Feb 21 18:59:15 2018
DistUpgraded: 2017-11-04 16:16:22,019 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:04dd]
MachineType: Dell Inc. PowerEdge R210 II
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/vg0-DomU0 ro
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2017-11-04 (109 days ago)
dmi.bios.date: 07/11/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.1
dmi.board.name: 03X6X0
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd07/11/2013:svnDellInc.:pnPowerEdgeR210II:pvr:rvnDellInc.:rn03X6X0:rvrA06:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R210 II
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic

[Andres Rodriguez]

This is pretty critical to MAAS as this yield Bionic deployments without
DNS resolution.

** Description changed:

  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see that
  netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.
  
  Resolv.conf should really be configured to use the provided DNS
  server(s)
  
  Bionic
  --
  
  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53
  
  search maaslab maas
+ ubuntu@node01:~$ ping google.com
+ ping: google.com: Temporary failure in name resolution
+ 
+ 
+ [...]
+ 
+ 
+ ubuntu@node01:~$ sudo vim /etc/resolv.conf
+ ubuntu@node01:~$ cat /etc/resolv.conf
+ # This file is managed by man:systemd-resolved(8). Do not edit.
+ #
+ # 127.0.0.53 is the systemd-resolved stub resolver.
+ # run "systemd-resolve --status" to see details about the actual nameservers.
+ nameserver 10.90.90.1
+ 
+ search maaslab maas
+ ubuntu@node01:~$ ping google.com
+ PING google.com (172.217.0.174) 56(84) bytes of data.
+ 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
+ 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms
  
  =
  Xenial
  ==
  
  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas
  
  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 10.90.90.1
  search maaslab maas

** Summary changed:

- [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic
+ [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to 
no DNS resolution

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Invalid
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  namese

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Andres Rodriguez]

@Mathieu,

Good catch.

@Scott:

Network config MAAS sent is correect, it is the same config sent to
xenial: https://pastebin.canonical.com/p/rjBgzKjdxR/

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Invalid
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas

  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 10.90.90.1
  search maaslab maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+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 1749261] Re: Add amd64/i386 retpoline support

[Steve Beattie]

** Summary changed:

- Add amd64/i386 support
+ Add amd64/i386 retpoline support

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

Title:
  Add amd64/i386 retpoline support

Status in gcc-4.8 package in Ubuntu:
  New
Status in gcc-4.8 source package in Trusty:
  Fix Committed

Bug description:
  To mitigate Spectre Variant 2, gcc needs to have retpoline support
  (-mindirect-branch and -mfunction-return arguments on amd64 and i386).

  Packages with this will go into the proposed pockets but need to be
  published in the -security pockets for their respective releases.

  Patches for gcc-4.8 were pulled from H.J. Lu's backport branch to 4.9,
  available at https://github.com/hjl-tools/gcc/tree/hjl/indirect/gcc-
  4_9-branch/master . Upstream GCC does not seem to be applying patches
  to anything older than the gcc-6-branch. H.J. Lu is the author of the
  upstream retpoline commits as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1749261/+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 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Mathieu Trudel-Lapierre]

Why aren't the nameservers set under the br0 interface, if the interface
is supposed to be in a bridge?

The /e/n/i config and netplan configs here are not equivalent. I expect
that systemd-resolved should be happy with the config as it is anyway,
but this may be a special case where systemd thinks the interface is not
really up?

If you run 'systemd-resolve google.com', what happens?

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Invalid
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas

  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 10.90.90.1
  search maaslab maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+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 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Scott Moser]

MAAS is sending a "global" nameserver, and a ethernet device on a bridge.
cloud-init is rendering that nameserver onto the ethernet device rather
than on the bridge or as a "global" entry.


$ cat my.yaml
network:
  config: [
   {"id": "enp0s25", "type": "physical", "name": "enp0s25",
"mac_address": "b8:ae:ed:7d:16:d0", "mtu": 1500,
"subnets": [{"type": "manual"}]},
   {"id": "br0", "type": "bridge", "name": "br0",
"mac_address": "b8:ae:ed:7d:16:d0", "bridge_interfaces": ["enp0s25"],
"mtu": 1500, "params": {'bridge_fd': 15, 'bridge_stp': 0},
"subnets": [
   {"type": "static", "address": "10.90.90.4/24", "dns_nameservers": [],
"gateway": "10.90.90.1"}
 ]},
   {"type": "nameserver", "address": ["10.90.90.1"],
"search": ["maaslab", "maas"]},
  ]
  version: 1

$ PYTHONPATH=$PWD python3 ./tools/net-convert.py \
   --network-data=my.yaml  --kind=yaml --output-kind=netplan --directory=out.d

$ cat out.d/etc/netplan/50-cloud-init.yaml

network:
version: 2
ethernets:
enp0s25:
match:
macaddress: b8:ae:ed:7d:16:d0
mtu: 1500
nameservers:
addresses:
- 10.90.90.1
search:
- maaslab
- maas
set-name: enp0s25
bridges:
br0:
addresses:
- 10.90.90.4/24
gateway4: 10.90.90.1
interfaces:
- enp0s25
parameters:
forward-delay: 15
stp: false

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Invalid
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas

  auto enp0s25
  iface enp0s

[Touch-packages] [Bug 1735932] Re: package util-linux 2.30.2-0.1ubuntu1 failed to install/upgrade: installed util-linux package post-installation script subprocess returned error exit status 1

[Phillip Susi]

You have a third party boot script named "tpeap" installed, and this
script is broken ( it has no LSB headers ).  You will need to remove or
repair it.


** Changed in: util-linux (Ubuntu)
   Status: New => Invalid

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

Title:
  package util-linux 2.30.2-0.1ubuntu1 failed to install/upgrade:
  installed util-linux package post-installation script subprocess
  returned error exit status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Ran  sudo do-release-upgrade -d.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.30.2-0.1ubuntu1
  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: Sat Dec  2 17:48:12 2017
  ErrorMessage: installed util-linux package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-08-08 (481 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.2.24
  SourcePackage: util-linux
  Title: package util-linux 2.30.2-0.1ubuntu1 failed to install/upgrade: 
installed util-linux package post-installation script subprocess returned error 
exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-12-02 (0 days ago)

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

pyrfc3339 looks good and straightforward to me; MIR approved.

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

-- 
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:
  Fix Committed
Status in python-nacl package in Ubuntu:
  New

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 1749247] Re: Spurious SEGV running inside kvm

[Howard Chu]

I think we can close this out, we were able to reproduce the issue
without kvm. Sorry for the false alarm.

** Changed in: qemu (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: openldap (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: openldap (Ubuntu)
   Status: Invalid => In Progress

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

Title:
  Spurious SEGV running inside kvm

Status in openldap package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  Running a continuous stream of operations against OpenLDAP slapd
  eventually causes a SEGV in liblber, in a segment of code that cannot
  fail:

   gdb /opt/symas/lib64/slapd CoreDump 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /opt/symas/lib64/slapd...done.
  [New LWP 5472]
  [New LWP 5468]
  [New LWP 5524]
  [New LWP 5471]
  [New LWP 5469]
  [New LWP 5507]
  [New LWP 5510]
  [New LWP 5470]
  [New LWP 5506]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/opt/symas/lib64/slapd -u root -g root -h ldap:///'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f4e2c9f0160 in ber_dupbv_x (dst=0x196b268, src=0x7f25f8001070, 
ctx=0x0) at /home/build/git/sold-master/openldap/libraries/liblber/memory.c:513
  513 new->bv_val[src->bv_len] = '\0';
  [Current thread is 1 (Thread 0x7f260e242700 (LWP 5472))]
  (gdb) l 500
  495 if(( new = ber_memalloc_x( sizeof(struct berval), ctx 
)) == NULL ) {
  496 return NULL;
  497 }
  498 }
  499
  500 if ( src->bv_val == NULL ) {
  501 new->bv_val = NULL;
  502 new->bv_len = 0;
  503 return new;
  504 }
  (gdb) 
  505
  506 if(( new->bv_val = ber_memalloc_x( src->bv_len + 1, ctx )) == 
NULL ) {
  507 if ( !dst )
  508 ber_memfree_x( new, ctx );
  509 return NULL;
  510 }
  511
  512 AC_MEMCPY( new->bv_val, src->bv_val, src->bv_len );
  513 new->bv_val[src->bv_len] = '\0';
  514 new->bv_len = src->bv_len;
  (gdb) p *new
  $1 = {bv_len = 0, bv_val = 0x0}
  (gdb) p *src
  $2 = {bv_len = 36, bv_val = 0x7f268ccc7bee }
  (gdb) 

  
  At line 506 we allocate some memory and check for a failure (returning NULL) 
and leave the function at line 509 if there was a failure. The allocation is 
for 37 bytes of memory and a memcpy into that memory succeeds on line 512. The 
SEGV occurs at line 513 and the pointer that was just returned from the 
allocator is NULL at this point. There are no other active threads that could 
be stomping on memory, there's no stack overrun or any other misbehavior that 
can account for it. Also, the identical test sequence completes without 
incident when running on the host OS instead of under kvm.
  (The src->bv_val pointer points to valid data at the time of the crash; it's 
just residing in a mmap'd file and that mapping isn't preserved in the 
coredump. So ignore gdb's error there.)

  Something in kvm is writing zeroes over a field of memory after we
  already checked that it was non-zero.

  This is on 
  Linux anvil1 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Both the host and the guest VM are on identical OS revision.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1749247/+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 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Andres Rodriguez]

@Matthieu,

ubuntu@node01:~$ systemd-resolve google.com
google.com: resolve call failed: No appropriate name servers or networks for 
name found

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Invalid
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas

  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 10.90.90.1
  search maaslab maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+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 1750851] Re: re-add cloud-initramfs-dyn-netconf to ubuntu-server

[Scott Moser]

Marked as 'fix-committed' as I pushed to the seed branch.
I need to wait for some server side things to happen before I can upload 
ubuntu-meta,

but any  ubuntu-meta > 1.411 should have this fix.


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

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  re-add cloud-initramfs-dyn-netconf to ubuntu-server

Status in ubuntu-meta package in Ubuntu:
  Fix Committed

Bug description:
  I (smoser) removed cloud-initramfs-dyn-netconf from ubuntu-server meta
  package.  That package provides functionality needed by MAAS and cause bug
  1748875.  Under that bug we re-added cloud-initramfs-dyn-netconf to the
  initramfs that MAAS publishes.

  We subsequently saw failure in open-iscsi tests, which utilize that same
  function.

  My commit message to the fix of maas-images is below for informational
  purposes [1]:
[1] 
https://code.launchpad.net/~smoser/maas-images/trunk.lp1749019-re-add-cloud-intramfs-dyn-netconf/+merge/337605

  'b' is *also* used by the open-iscsi use case.  It boots with a slightly
  different form than maas images:
BOOTIF_DEFAULT=eth0 and ip=:name:BOOTIF

  Here, 'BOOTIF' will be replaced with 'eth0'.

  | Re-add cloud-initramfs-dyn-netconf. Needed by maas for BOOTIF in ip=.
  |
  | The previous commit to trunk dropped cloud-initramfs-dyn-netconf from
  | the maas image in releases newer than xenial.
  | 
  | That caused errors in MAAS. cloud-initramfs-dyn-netconf does 2 things:
  | a.) writes /run/network/dynamic-interfaces
  | this is a ENI style file with data retrived from ipconfig
  | b.) convert 'BOOTIF' string in the value of IP
  |   Example:
  | ip=foobar:BOOTIF BOOTIF=01-00-22-68-10-c1-e6
  |   will be effectively rendered as:
  | ip=foobar:eth0
  |
  | 'b' is still required by maas.
  |
  | Note: in maas v3 images, the squashfs image is re-used pristine
  | from cloud-images. Because of this, the installation into the image
  | affects initramfs creation, but does not affect the image. That is
  | correct in that this package is not needed in the image but only
  | in the initramfs.

  Related bugs:
   * bug 1748875:  Unable to deploy Bionic on bare-metals with MaaS 2.3.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1750851/+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 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Scott Moser]

It seems to me that each of maas, cloud-init and netplan could do better
here.

a.) maas declares 'global' nameserver/dns info.
this is kind of silly in that such a thing doesn't really exist.
maas has the information necessary to declare the nameserver on the
device with the address that has a route to it.

b.) cloud-init is currently sticking that global definition on an
interface that doesnt have an address.  so cloud-init could do better.

c.) netplan or systemd-networkd could realize enp0s25 interface is "up"
and that it should have its nameservers used.

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Invalid
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas

  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 10.90.90.1
  search maaslab maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+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 1726608] Re: Alt+Arrow in gnome-shell unexpectedly switches VTs

[Brian Murray]

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

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

Title:
  Alt+Arrow in gnome-shell unexpectedly switches VTs

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Trusty:
  Confirmed
Status in console-setup source package in Xenial:
  Confirmed
Status in console-setup source package in Zesty:
  Won't Fix

Bug description:
  I'm experiencing a bug similar to bug 1710637 with Ubuntu 17.10 again.

  Test Case
  -
  schroot -u root -c trusty-amd64
  edit /etc/apt/sources.list to xenial
  apt-get update
  apt-get install console-setup
  use alt+tab to bring up the window switcher
  then use alt+arrow to switch windows

  I then end up at the gdm login screen or a virtual tty.

  Installing a different set of packages, via apt-get dist-upgrade,
  actually ended up killing my desktop session.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 14:30:16 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['sound-output-device-choo...@kgshank.net', 'multi-monitors-add-on@spin83', 
'datetime-for...@daniel-khodabakhsh.github.com', 
'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'terminator.desktop', 'virt-manager.desktop', 'chromium-browser.desktop', 
'firefox.desktop', 'simple-scan.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2013-01-16 (1741 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1726608/+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 1749247] Re: Spurious SEGV running inside kvm

[David Britton]

Hi Howard, I assigned this to you since you marked it as 'in progress'
(as is convention).  If that is not correct, you can unassign yourself
and set it back to 'triaged' or 'confirmed' to allow someone else to
pick it up.

Thanks!

** Changed in: openldap (Ubuntu)
 Assignee: (unassigned) => Howard Chu (hyc)

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

Title:
  Spurious SEGV running inside kvm

Status in openldap package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  Running a continuous stream of operations against OpenLDAP slapd
  eventually causes a SEGV in liblber, in a segment of code that cannot
  fail:

   gdb /opt/symas/lib64/slapd CoreDump 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /opt/symas/lib64/slapd...done.
  [New LWP 5472]
  [New LWP 5468]
  [New LWP 5524]
  [New LWP 5471]
  [New LWP 5469]
  [New LWP 5507]
  [New LWP 5510]
  [New LWP 5470]
  [New LWP 5506]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/opt/symas/lib64/slapd -u root -g root -h ldap:///'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f4e2c9f0160 in ber_dupbv_x (dst=0x196b268, src=0x7f25f8001070, 
ctx=0x0) at /home/build/git/sold-master/openldap/libraries/liblber/memory.c:513
  513 new->bv_val[src->bv_len] = '\0';
  [Current thread is 1 (Thread 0x7f260e242700 (LWP 5472))]
  (gdb) l 500
  495 if(( new = ber_memalloc_x( sizeof(struct berval), ctx 
)) == NULL ) {
  496 return NULL;
  497 }
  498 }
  499
  500 if ( src->bv_val == NULL ) {
  501 new->bv_val = NULL;
  502 new->bv_len = 0;
  503 return new;
  504 }
  (gdb) 
  505
  506 if(( new->bv_val = ber_memalloc_x( src->bv_len + 1, ctx )) == 
NULL ) {
  507 if ( !dst )
  508 ber_memfree_x( new, ctx );
  509 return NULL;
  510 }
  511
  512 AC_MEMCPY( new->bv_val, src->bv_val, src->bv_len );
  513 new->bv_val[src->bv_len] = '\0';
  514 new->bv_len = src->bv_len;
  (gdb) p *new
  $1 = {bv_len = 0, bv_val = 0x0}
  (gdb) p *src
  $2 = {bv_len = 36, bv_val = 0x7f268ccc7bee }
  (gdb) 

  
  At line 506 we allocate some memory and check for a failure (returning NULL) 
and leave the function at line 509 if there was a failure. The allocation is 
for 37 bytes of memory and a memcpy into that memory succeeds on line 512. The 
SEGV occurs at line 513 and the pointer that was just returned from the 
allocator is NULL at this point. There are no other active threads that could 
be stomping on memory, there's no stack overrun or any other misbehavior that 
can account for it. Also, the identical test sequence completes without 
incident when running on the host OS instead of under kvm.
  (The src->bv_val pointer points to valid data at the time of the crash; it's 
just residing in a mmap'd file and that mapping isn't preserved in the 
coredump. So ignore gdb's error there.)

  Something in kvm is writing zeroes over a field of memory after we
  already checked that it was non-zero.

  This is on 
  Linux anvil1 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Both the host and the guest VM are on identical OS revision.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1749247/+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 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq

[David Britton]

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

** Changed in: resolvconf (Ubuntu)
   Status: New => Incomplete

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

Title:
  Non existent host causes 100% cpu utilization by systemd-resolved and
  dnsmasq

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364/+subscriptions

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

[Touch-packages] [Bug 1747744] Re: [regression] Video playback in totem is corrupted in X11

[Bug Watch Updater]

** Changed in: mesa
   Status: In Progress => Fix Released

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1747744/+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 1502045] Re: Move from consolekit to logind

[Bug Watch Updater]

** Changed in: lxdm (Debian)
   Status: New => Fix Released

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

Title:
  Move from consolekit to logind

Status in lxdm package in Ubuntu:
  Fix Released
Status in lxsession package in Ubuntu:
  Fix Released
Status in mate-power-manager package in Ubuntu:
  Triaged
Status in openssh package in Ubuntu:
  Fix Released
Status in polkit-qt-1 package in Ubuntu:
  Triaged
Status in solaar package in Ubuntu:
  Triaged
Status in sugar package in Ubuntu:
  Triaged
Status in tcosmonitor package in Ubuntu:
  Fix Released
Status in ulatencyd package in Ubuntu:
  Triaged
Status in lxdm package in Debian:
  Fix Released
Status in tcosmonitor package in Debian:
  Fix Released

Bug description:
  consolekit has been dead upstream for a long time. Ubuntu moved to
  logind in saucy (13.10), and we don't support consolekit any more.
  There are a few packages which still depend on it, most notably
  openssh, lxdm, and lxsession{,-logout}. For Ubuntu 16.04 we really
  should get rid of CK.

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

[Launchpad Bug Tracker]

This bug was fixed in the package bluez - 5.48-0ubuntu3

---
bluez (5.48-0ubuntu3) bionic; urgency=medium

  * Add fix-lp1750308-upstream-commit-1bf03369.patch to fix command piping
regression (mostly affecting python-dbusmock). (LP: #1750308)

 -- Daniel van Vugt   Wed, 21 Feb 2018
15:08:50 +0800

** Changed in: bluez (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 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 Released
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 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Mathieu Trudel-Lapierre]

Ok, I'm opening the tasks for Xenial and Trusty, and we can decide
exactly where it makes sense to do the SRU for these changes.

Plus, I understand maybe it was still reproducible in some form on
bionic, so it this should be revisited in general.

** Also affects: console-setup (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: gnome-shell (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Also affects: console-setup (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: mutter (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: gdm3 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

Title:
  Input falls through to gdm3 and terminates the session on Ctrl+C after
  udevadm trigger is executed under wayland

Status in Snappy:
  Won't Fix
Status in console-setup package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in console-setup source package in Trusty:
  New
Status in gdm3 source package in Trusty:
  New
Status in gnome-shell source package in Trusty:
  New
Status in mutter source package in Trusty:
  New
Status in systemd source package in Trusty:
  New
Status in console-setup source package in Xenial:
  New
Status in gdm3 source package in Xenial:
  New
Status in gnome-shell source package in Xenial:
  New
Status in mutter source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  = Test Cases =

  Test Case 1:
  - Login under Wayland (session Ubuntu)
  - Open a terminal
  - snap install gimp
  - Wait until installation finishes successfully
  - In the terminal window press CTRL+C

  Result:
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  Test Case 2:
  - Login under Wayland (session Ubuntu)
  - Open a terminal and type the following command:
    $ sudo udevadm trigger
  - In the terminal window press CTRL+C

  Result
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  = Original Description =

  Multiple times a day I find myself without a session after hitting
  Ctrl+C in a terminal, it seems the input falls through the
  Ubuntu/GNOME session and to gdm, which itself decides to terminate.

  Even worse, when this happens, you can briefly see your login password
  in plaintext in the virtual terminal. You can see the password however
  long you want if you stop the gdm service when this happens.

  I don't have a good way to reproduce, but it seems locking the session
  with a keyboard shortcut, subsequently unlocking it, maybe suspending,
  at some point brings this behaviour into the picture, until the
  session dies with a Ctrl+C.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 14 15:54:34 2017
  InstallationDate: Installed on 2016-05-06 (464 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1710637/+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 819995] Re: "Print to file" PDF metadata broken

[gna]

I have tried some solutions before i found this bug,

An extract of metadata made with exiftool (libimage-exiftool-perl
9.46-1) shows an important difference on a document that displaying
dates right, and one sample print-to-file, the tags for PDF related date
info is totally missing:

-PDF:CreateDate=
-PDF:ModifyDate=


Example command:
exiftool -args -G1 --filename --directory PDF_FILE_NAME.PDF

Example output of Print-to-File:
-ExifTool:ExifToolVersion=9.46
-System:FileSize=107 kB
-System:FileModifyDate=2018:02:22 00:56:18+01:00
-System:FileAccessDate=2018:02:22 00:56:40+01:00
-System:FileInodeChangeDate=2018:02:22 01:30:18+01:00
-System:FilePermissions=rw-rw-r--
-File:FileType=PDF
-File:MIMEType=application/pdf
-PDF:PDFVersion=1.5
-PDF:Linearized=No
-PDF:PageCount=1
-PDF:Creator=cairo 1.13.1 (http://cairographics.org)
-PDF:Producer=cairo 1.13.1 (http://cairographics.org)

Example output of PDF with working dates:
-ExifTool:ExifToolVersion=9.46
-System:FileSize=3.2 MB
-System:FileModifyDate=2015:11:02 14:37:59+01:00
-System:FileAccessDate=2018:02:22 01:49:42+01:00
-System:FileInodeChangeDate=2015:11:02 14:37:59+01:00
-System:FilePermissions=rw-r-
-File:FileType=PDF
-File:MIMEType=application/pdf
-PDF:PDFVersion=1.5
-PDF:Linearized=No
-PDF:PageCount=89
-PDF:Language=en-US
-PDF:TaggedPDF=Yes
-PDF:Title=XenServer 6.x Best Practices
-PDF:Author=Daily, Camille
-PDF:Keywords=Minimum Restrictions, No Restrictions
-PDF:Creator=Microsoft® Word 2013
-PDF:CreateDate=2013:10:30 08:44:27-05:00
-PDF:ModifyDate=2013:10:30 08:44:27-05:00
-PDF:Producer=Microsoft® Word 2013



evince 3.10.3-0ubuntu10.4 amd64
libcairo2 1.13.0~20140204-0ubuntu1.1 amd64
Description:Ubuntu 14.04.5 LTS
Kernel: Linux 3.13.0-142-generic #191-Ubuntu SMP x86_64

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

Title:
  "Print to file" PDF metadata broken

Status in cairo package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 11.04 Natty Narwhal 64bit

  libgnomeprint2.2-0 - 2.18.8-0ubuntu1

  It seems libgnomeprint sends wrong date, Jan 1st 1970 to PDF metadata when 
printing to file (PDF)
  This behaviour is reproducible for me on both 64bit and 32bit versions of 
11.04
   
  Using dialog "print to file" choosing PDF as output format "Creation Date" 
and "Last edited" is always set to  "Thu 01 Jän 1970 00:59:59 CET" which is 
afaik Date 0 for Unices.
  I am using german localization but in case of needed screenshots I can of 
course change to english.
  This behaviour happens on my main machine (64bit) and my old notebook (32bit) 
looking to my self produced PDFs from 10.10 definitely show the same behaviour, 
I could also look on old backups for even older version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/819995/+subscriptions

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

[Touch-packages] [Bug 1750937] [NEW] 14.04 Kernel update on 2/21 breaks Nvidia drivers

[Bill Miller]

Public bug reported:

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

Rebooted into 4.4.0-112 kernel and all was well.

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

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


** Tags: amd64 apport-bug possible-manual-nvidia-install resolution trusty 
ubuntu

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

Title:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

Status in xorg package in Ubuntu:
  New

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

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])

[Touch-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Hui Wang]

** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Artful:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

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

[Daniel van Vugt]

OK, please try some older (or much newer) kernels then:
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

-- 
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 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Johan Marius Wesselink]

I tested the proposed package on Lubuntu 17.10.

I tested some example programs they use either:
GLProfile glp = GLProfile.getDefault();
Or they use the GLCanvas default constructor.

Before this version all these examples emitted the typical error found
in the previous version of jogl2. The new package RESOLVED this problem.

I noticed after some experimenting that replacing getDefault with 
get(GLProfile.GL2);
also solved the problem. Then I found this thread.

I build scilab from source using the git repository. This is the master
and future 6.1 version it has the same problem. However, scilab 6 and
higher have the jogl2 library prebuild and distributed as a thirdparty
library. Removing this library doesn't work. The problem is that the
scirender module and the gui modules depend on the old syntax. The Java
path in the past was javax.media. In newer version of jogl2 this changed
to com.jogamp. This means that besides removing the faulty library from
scilab the modules scirender and gui need to be patched. I did just this
in the last days. The git master branch version 6.1 build and works with
the new jogl2 version. I noticed however one regression bug the cursor
selection in the plot window work kind of inverted. This is an old bug
which I have seen before.

So, yes this fixes the jogl2 bug. But, no likely not the scilab bug.
Depends how you get scilab and which version probably.

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in scilab package in Ubuntu:
  Invalid
Status in libjogl2-java source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Invalid
Status in scilab source package in Xenial:
  Invalid
Status in libjogl2-java source package in Artful:
  Fix Committed
Status in mesa source package in Artful:
  Invalid
Status in scilab source package in Artful:
  Invalid
Status in scilab package in Debian:
  Fix Released

Bug description:
  [Impact]

  Software that use libjogl2-java (Scilab, Matlab,...) fail to run,
  because Mesa dropped 'Gallium' from the renderer string.

  [Test case]
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped
   at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
   at com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
   at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
   at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
   at java.security.AccessController.doPrivileged(Native Method)
   at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
   at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
   at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
   at org.scilab.modules.gui.SwingView.(Unknown Source)
   at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
   at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  [Regression potential]
  The fix is a simple oneliner that allows libjogl2-java to detect Mesa with 
both new and original version of Mesa.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1742894/+subscriptions

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

[Touch-packages] [Bug 1750937] Re: 14.04 Kernel update on 2/21 breaks Nvidia drivers

[Bill Miller]

In the kernel log when I booted with the -116 kernel, I found this

nvidia: version magic '4.4.0-116-generic SMP mod_unload modversions '
should be '4.4.0-116-generic SMP mod_unload modversions retpoline '

This line doesn't occur in the kernel log for the -112 kernel, the case
when the driver works.

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

Title:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

Status in xorg package in Ubuntu:
  New

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

  Rebooted into 4.4.0-112 kernel and all was well.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1750937/+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 1689444] Re: gatttool crashed with SIGSEGV in g_source_remove from interactive from main

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

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

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

Title:
  gatttool crashed with SIGSEGV in g_source_remove from interactive from
  main

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.37-0ubuntu5, 
the problem page at 
https://errors.ubuntu.com/problem/edf93ae590df75746d783c408e6b879a4111444a 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689444/+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 1690014] Re: bluetoothd crashed with SIGSEGV in sprintf() from ba2str() from update_bredr_services() from browse_cb() from search_completed_cb()

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  bluetoothd crashed with SIGSEGV in sprintf() from ba2str() from
  update_bredr_services() from browse_cb() from search_completed_cb()

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.37-0ubuntu5, 
the problem page at 
https://errors.ubuntu.com/problem/d0e23498400d17e447422015c7abe1b8224c36b0 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1690014/+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 1689439] Re: bluetoothd crashed with SIGSEGV in set_ct_player from player_remove from g_slist_foreach from g_slist_free_full from avrcp_get_media_player_list_rsp

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

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

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

Title:
  bluetoothd crashed with SIGSEGV in set_ct_player from player_remove
  from g_slist_foreach from g_slist_free_full from
  avrcp_get_media_player_list_rsp

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.37-0ubuntu5, 
the problem page at 
https://errors.ubuntu.com/problem/58231706469af54317bae2161b3fc6e0b066388d 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689439/+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 1689466] Re: bluetoothd crashing with SIGSEGV in encrypt_notify from g_io_unix_dispatch from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  bluetoothd crashing with SIGSEGV in encrypt_notify from
  g_io_unix_dispatch from g_main_dispatch from g_main_context_dispatch
  from g_main_context_iterate

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.37-0ubuntu5, 
the problem page at 
https://errors.ubuntu.com/problem/51e27350205066877db9eee38a77d852664027f7 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689466/+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 1689441] Re: obexd crashed with SIGABRT - ERROR:gobex/gobex-header.c:110:g_obex_header_encode: assertion failed (utf16_len + 3 == header->hlen): (77 == 75)

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

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

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

Title:
  obexd crashed with SIGABRT - ERROR:gobex/gobex-
  header.c:110:g_obex_header_encode: assertion failed (utf16_len + 3 ==
  header->hlen): (77 == 75)

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.37-0ubuntu5, 
the problem page at 
https://errors.ubuntu.com/problem/eba4dce1246a1f2b6202414791cee579566ae3dc 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689441/+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 1681517] Re: bluetoothd crashed with SIGSEGV in avdtp_open from endpoint_open_cb from endpoint_reply from complete_pending_call_and_unlock from dbus_connection_dispatch

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  bluetoothd crashed with SIGSEGV in avdtp_open from endpoint_open_cb
  from endpoint_reply from complete_pending_call_and_unlock from
  dbus_connection_dispatch

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.41-0ubuntu3, 
the problem page at 
https://errors.ubuntu.com/problem/8a866d2144eff926b451cc11c9018d9c402eceda 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1681517/+subscriptions

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

[Touch-packages] [Bug 1750947] [NEW] pulseaudio crashed when selecting unavailable profile

[Hui Wang]

Public bug reported:

Only pulseaudio-xenial has this problem.

we need to backport this commit to pulseaudio-xenial.

https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

** Affects: pulseaudio (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: New

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

Title:
  pulseaudio crashed when selecting unavailable profile

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947/+subscriptions

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

[Touch-packages] [Bug 1493498] Re: bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch

[Daniel van Vugt]

Fix released (no crashes reported after 15.04)

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from
  avdtp_abort_resp from avdtp_parse_resp from session_cb from
  g_main_dispatch

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding bluez.  This problem was most recently seen with version
  4.101-0ubuntu25, the problem page at
  https://errors.ubuntu.com/problem/89c2536156cfe1ec74b64298c4d38b4e320baac4
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493498/+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 1596791] Re: bluetoothd crashed with SIGABRT: "double free or corruption (out)"

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  bluetoothd crashed with SIGABRT: "double free or corruption (out)"

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding bluez.  This problem was most recently seen with version
  5.37-0ubuntu5, the problem page at
  https://errors.ubuntu.com/problem/2f3495bc3150aeabb5e60969cd2b856f8627b35f
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1596791/+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 1694455] Re: Bluetooth: Cannot receive files

[Daniel van Vugt]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: gnome-bluetooth (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Bluetooth: Cannot receive files

Status in bluez package in Ubuntu:
  Invalid
Status in gnome-bluetooth package in Ubuntu:
  Invalid

Bug description:
  # Use case

  Ubuntu 17.04, quite fresh installation, updated.

  Bluetooth file transmission

  I want to send files to my smartphone, and receive files sent by my
  smartphone via bluetooth. I pair both devices, initiate file transfer
  from one of the devices, and the other device asks me what to do.

  # Problems

  This is a mix from usability and technical issues.

  1. OBEX disabled (bug 1645631)

  The bluetooth file transmission service OBEX was not started. I started and 
enabled OBEX:
  `systemctl --user start obex`
  `systemctl --user enable obex`

  ```
  Mai 30 14:47:55 tp systemd[1661]: Starting Bluetooth OBEX service...
  Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43
  ```

  2. OBEX silently fails (this bug)

  After having OBEX enabled, I was able to transmit files from laptop to
  smartphone, yet I could not receive files on the laptop. In the system
  log, you could see that OBEX fails (please note `FORBIDDEN`):

  ```
  Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43
  Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x)
  Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x0)
  Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), (null)(0x)
  Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), FORBIDDEN(0x43)
  Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), (null)(0x)
  Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20)
  Mai 30 14:48:04 tp obexd[8168]: disconnected: Transport got disconnected
  ```

  I did not receive a popup notification asking me to receive the file
  or not.

  In the file sharing preferences `gnome-file-share-properties`, there
  is a setting to automatically receive files via bluetooth. With this
  box checked, you're finally able to receive files from your
  smartphone.

  Successful log for comparison:
  ```
  Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x)
  Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x0)
  Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), (null)(0x)
  Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), CONTINUE(0x10)
  Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), (null)(0x)
  Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20)
  Mai 30 14:56:28 tp obexd[8168]: disconnected: Transport got disconnected
  ```

  # Expected behaviour

  OBEX is started by default to handle bluetooth file transfers.

  If no automatic file receipt is configured, a popup notification asks
  me if I want to receive the file or not.

  If this is not possible, there should be a notification pointing the
  user to the configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1694455/+subscriptions

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

[Touch-packages] [Bug 1750947] Re: pulseaudio crashed when selecting unavailable profile

[Daniel van Vugt]

If this is a crash then it's very likely we already have a bug report
for it.

Can you find a stack trace of the crash?

** Changed in: pulseaudio (Ubuntu)
   Status: New => Incomplete

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

Title:
  pulseaudio crashed when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+subscriptions

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

[Touch-packages] [Bug 1690056] Re: pulseaudio crashed with SIGABRT in sink_input_detach() from pa_sink_process_msg() from asyncmsgq_read_work() from pa_rtpoll_run() from thread_func()

[Daniel van Vugt]

Fix released (no crashes reported after 16.10)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  pulseaudio crashed with SIGABRT in sink_input_detach() from
  pa_sink_process_msg() from asyncmsgq_read_work() from pa_rtpoll_run()
  from thread_func()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/5f657ed114d93f711b0cd115f59362cb8728ac14 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690056/+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 1690070] Re: pulseaudio crashed with SIGSEGV in pa_msgobject_isinstance() from pa_msgobject_cast() from adjust_rates() from sink_input_process_msg_cb() from pa_asyncmsgq_dispatch

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  pulseaudio crashed with SIGSEGV in pa_msgobject_isinstance() from
  pa_msgobject_cast() from adjust_rates() from
  sink_input_process_msg_cb() from pa_asyncmsgq_dispatch()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/002d0b29f2768aae27e98aeb96eaf53d46605a33 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690070/+subscriptions

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

[Touch-packages] [Bug 1750947] Re: pulseaudio crashed when selecting unavailable profile

[Hui Wang]

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Critical

** Tags added: originate-from-1737727 somerville

** Changed in: hwe-next
   Importance: Undecided => Critical

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

Title:
  pulseaudio crashed when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+subscriptions

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

[Touch-packages] [Bug 1690049] Re: pulseaudio crashed with SIGABRT in memcpy() from tdb_read() from tdb_needs_recovery() from tdb_lock_list() from tdb_lock()

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  pulseaudio crashed with SIGABRT in memcpy() from tdb_read() from
  tdb_needs_recovery() from tdb_lock_list() from tdb_lock()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/b27e6406aff54551cee511b54ee62a5447f3c98a 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690049/+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 1690069] Re: pulseaudio crashed with SIGABRT in __memcpy_avx_unaligned() from memcpy() from tdb_read() from tdb_transaction_recover() from tdb_open_ex()

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  pulseaudio crashed with SIGABRT in __memcpy_avx_unaligned() from
  memcpy() from tdb_read() from tdb_transaction_recover() from
  tdb_open_ex()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/1ff87d46ce1a224f74b97b5ccaa8a4eb12bad180 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690069/+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 1662253] Re: pulseaudio crashed with SIGSEGV in pa_bluetooth_device_any_transport_connected() from transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_se

[Daniel van Vugt]

Fix released (no crashes reported after 16.10)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  pulseaudio crashed with SIGSEGV in
  pa_bluetooth_device_any_transport_connected() from
  transport_state_changed_cb() from pa_hook_fire() from
  pa_bluetooth_transport_set_state() from
  pa_bluetooth_transport_unlink()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/611e08e54b2e1bab7707f341fda104668886d193 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1662253/+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 1690027] Re: pulseaudio crashed with SIGABRT in pa_msgobject_isinstance() from pa_msgobject_cast() from adjust_rates() from sink_input_process_msg_cb() from asyncmsgq_read_cb()

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  pulseaudio crashed with SIGABRT in pa_msgobject_isinstance() from
  pa_msgobject_cast() from adjust_rates() from
  sink_input_process_msg_cb() from asyncmsgq_read_cb()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/35253f6f4c1d8bccfe358b8c58fb275c649b935a 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690027/+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 1499113] Re: pulseaudio crashed with SIGSEGV in set_profile_cb() from pa_card_set_profile() from command_set_card_profile() from pa_pdispatch_run() from pstream_packet_callback()

[Daniel van Vugt]

Fix released (no crashes reported after 16.10)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  pulseaudio crashed with SIGSEGV in set_profile_cb() from
  pa_card_set_profile() from command_set_card_profile() from
  pa_pdispatch_run() from pstream_packet_callback()

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/7ccf872ad0cc36d20cf02cc1c1ba6f0d881287cd

  ---

  Connect two devices, celu movil samsung and headphone

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: pulseaudio 1:6.0-0ubuntu12
  ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena  26880 F...m pulseaudio
   /dev/snd/controlC0:  caravena  26880 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Sep 23 20:52:31 2015
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2015-07-26 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  SegvAnalysis:
   Segfault happened at: 0x7f1042baad12:mov0x34(%rax),%eax
   PC (0x7f1042baad12) ok
   source "0x34(%rax)" (0x0055) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/pulse-6.0/modules/module-bluez5-device.so
   pa_card_set_profile () from /usr/lib/libpulsecore-6.0.so
   ?? () from /usr/lib/pulse-6.0/modules/libprotocol-native.so
   pa_pdispatch_run () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-6.0.so
   ?? () from /usr/lib/pulse-6.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGSEGV in pa_card_set_profile()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1499113/+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 1690042] Re: pulseaudio crashed with SIGSEGV in pa_bluetooth_device_any_transport_connected() from transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_se

[Daniel van Vugt]

Fix released (no crashes reported after 16.10)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  pulseaudio crashed with SIGSEGV in
  pa_bluetooth_device_any_transport_connected() from
  transport_state_changed_cb() from pa_hook_fire() from
  pa_bluetooth_transport_set_state() from pa_bluetooth_transport_put()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/182443fe9aecf3b5c56d1bcb8f87b57dd92ed3d9 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690042/+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 1690043] Re: pulseaudio crashed with SIGSEGV in adjust_rates() from sink_input_process_msg_cb() from pa_asyncmsgq_flush() from pa_thread_mq_done() from userdata_free()

[Daniel van Vugt]

Fix released (no crashes reported after 16.10)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  pulseaudio crashed with SIGSEGV in adjust_rates() from
  sink_input_process_msg_cb() from pa_asyncmsgq_flush() from
  pa_thread_mq_done() from userdata_free()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/827c89858820835d0e8f693f69e597145ab65807 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690043/+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 1690061] Re: pulseaudio crashed with SIGABRT in pa_close_pipe() from pa_signal_done() from main()

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  pulseaudio crashed with SIGABRT in pa_close_pipe() from
  pa_signal_done() from main()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/5d3ffc4aab0eaf05067b16645c50d89b3e0c4ae4 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690061/+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 1690057] Re: pulseaudio crashed with SIGABRT in memcpy() from tdb_read() from tdb_rec_read() from tdb_find() from tdb_find_lock_hash()

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  pulseaudio crashed with SIGABRT in memcpy() from tdb_read() from
  tdb_rec_read() from tdb_find() from tdb_find_lock_hash()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/4df1f7ebeed62837d758e11878501d46242405c8 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690057/+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 1690031] Re: pulseaudio crashed in pcm.c:2757: snd_pcm_area_copy: Assertion `src < dst || src >= dst + bytes' failed.

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  pulseaudio crashed in pcm.c:2757: snd_pcm_area_copy: Assertion `src <
  dst || src >= dst + bytes' failed.

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/e21c0bcfff3f6359b38c4cb20a7ba11d2a56ffa0 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690031/+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 1493495] Re: bluetoothd crashed with SIGSEGV in telephony_terminate_call_req from terminate_call from handle_event from rfcomm_io_cb:g_main_dispatch

[Daniel van Vugt]

Fix released (no crashes reported after 15.04)

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  bluetoothd crashed with SIGSEGV in telephony_terminate_call_req from
  terminate_call from handle_event from rfcomm_io_cb:g_main_dispatch

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding bluez.  This problem was most recently seen with version
  4.101-0ubuntu25.1~overlay2, the problem page at
  https://errors.ubuntu.com/problem/5c150a680b51f277c28dee82a9f97a2e16fe671a
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493495/+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 1690017] Re: bluetoothd crashed with SIGSEGV in queue_push_head() from set_and_store_gatt_req() from read_char() from char_discovered_cb:char_discovered_cb()

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  bluetoothd crashed with SIGSEGV in queue_push_head() from
  set_and_store_gatt_req() from read_char() from
  char_discovered_cb:char_discovered_cb()

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.37-0ubuntu5, 
the problem page at 
https://errors.ubuntu.com/problem/0c175d97f5741413757cd4c8449c0ed1b5b788df 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1690017/+subscriptions

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

[Touch-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

[Hui Wang]

[ 800.271277] Freezing user space processes ...
[ 820.267656] Freezing of tasks failed after 20.006 seconds (1 tasks refusing 
to freeze, wq_busy=0):
[ 820.267704] alsa-sink-HDMI D 0 1554 1117 0x0004
[ 820.267710] Call Trace:
[ 820.267723] __schedule+0x3c2/0x8b0
[ 820.267727] schedule+0x36/0x80
[ 820.267730] schedule_timeout+0x17a/0x360
[ 820.267735] ? call_timer_fn+0x140/0x140
[ 820.267745] snd_power_wait+0xba/0x110 [snd]
[ 820.267751] ? snd_power_wait+0xba/0x110 [snd]
[ 820.267756] ? wake_up_q+0x70/0x70
[ 820.267766] snd_pcm_common_ioctl1+0x41/0x930 [snd_pcm]
[ 820.267772] snd_pcm_playback_ioctl1+0x13e/0x250 [snd_pcm]
[ 820.26] ? eventfd_ctx_read+0x67/0x210
[ 820.267784] snd_pcm_playback_ioctl+0x28/0x40 [snd_pcm]
[ 820.267789] do_vfs_ioctl+0xa1/0x5f0
[ 820.267792] SyS_ioctl+0x79/0x90
[ 820.267796] entry_SYSCALL_64_fastpath+0x1e/0xa9
[ 820.267798] RIP: 0033:0x7fb4d9bbdf07
[ 820.267800] RSP: 002b:7fb4d5d3cc78 EFLAGS: 0246 ORIG_RAX: 
0010
[ 820.267803] RAX: ffda RBX: 7fb4d5d3cca0 RCX: 7fb4d9bbdf07
[ 820.267805] RDX: 01888d20 RSI: 4122 RDI: 0016
[ 820.267807] RBP: 01888d20 R08: 0043 R09: 0001
[ 820.267808] R10: 0185f870 R11: 0246 R12: 01888d20
[ 820.267810] R13:  R14: 7fb4d5d3a650 R15: 00615080
[ 820.267837] OOM killer enabled.
[ 820.267838] Restarting tasks ... done.

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+subscriptions

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

[Touch-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

[Hui Wang]

E: [alsa-sink-HDMI 0] alsa-util.c: snd_pcm_avail() returned a value that is 
exceptionally large: 26649288 bytes (151073 ms).
E: [alsa-sink-HDMI 0] alsa-util.c: Most likely this is a bug in the ALSA driver 
'snd_hda_intel'. Please report this issue to the ALSA developers.
E: [alsa-sink-HDMI 0] alsa-util.c: snd_pcm_dump():
E: [alsa-sink-HDMI 0] alsa-util.c: Hooks PCM
E: [alsa-sink-HDMI 0] alsa-util.c: Its setup is:
...
E: [alsa-sink-HDMI 0] alsa-util.c: Slave: Hardware PCM card 0 'HD-Audio 
Generic' device 3 subdevice 0
E: [alsa-sink-HDMI 0] alsa-util.c: Its setup is:
...
E: [alsa-sink-HDMI 0] alsa-util.c: snd_pcm_delay() returned a value that is 
exceptionally large: -25928392 bytes (-146986 ms).
E: [alsa-sink-HDMI 0] alsa-util.c: Most likely this is a bug in the ALSA driver 
'snd_hda_intel'. Please report this issue to the ALSA developers.
E: [alsa-sink-HDMI 0] alsa-util.c: snd_pcm_dump():
E: [alsa-sink-HDMI 0] alsa-util.c: Hooks PCM
E: [alsa-sink-HDMI 0] alsa-util.c: Its setup is:
...
E: [alsa-sink-HDMI 0] alsa-util.c: Slave: Hardware PCM card 0 'HD-Audio 
Generic' device 3 subdevice 0
E: [alsa-sink-HDMI 0] alsa-util.c: Its setup is:
...

** Summary changed:

- pulseaudio crashed when selecting unavailable profile
+ pulseaudio print lots of error when selecting unavailable profile

** Description changed:

  Only pulseaudio-xenial has this problem.
  
  we need to backport this commit to pulseaudio-xenial.
  
  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4
+ 
+ After printing out the error logs, the kernel crashes and system hangs.

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+subscriptions

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

[Touch-packages] [Bug 1750955] [NEW] package libopencv-dev 2.4.9.1+dfsg-1.5ubuntu1 failed to install/upgrade: trying to overwrite '/usr/include/opencv/cvaux.hpp', which is also in package libcvaux-dev

[Bruno]

Public bug reported:

Unable to update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libopencv-dev 2.4.9.1+dfsg-1.5ubuntu1
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: Wed Feb 21 21:30:46 2018
DpkgTerminalLog:
 Preparing to unpack .../libopencv-dev_3.3.1_amd64.deb ...
 Unpacking libopencv-dev (3.3.1) over (2.4.9.1+dfsg-1.5ubuntu1) ...
 dpkg: error processing archive 
/home/bruno/Downloads/jetpack/jetpack_download/libopencv-dev_3.3.1_amd64.deb 
(--unpack):
  trying to overwrite '/usr/include/opencv/cvaux.hpp', which is also in package 
libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
DuplicateSignature:
 package:libopencv-dev:2.4.9.1+dfsg-1.5ubuntu1
 Unpacking libopencv-dev (3.3.1) over (2.4.9.1+dfsg-1.5ubuntu1) ...
 dpkg: error processing archive 
/home/bruno/Downloads/jetpack/jetpack_download/libopencv-dev_3.3.1_amd64.deb 
(--unpack):
  trying to overwrite '/usr/include/opencv/cvaux.hpp', which is also in package 
libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
ErrorMessage: trying to overwrite '/usr/include/opencv/cvaux.hpp', which is 
also in package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: opencv
Title: package libopencv-dev 2.4.9.1+dfsg-1.5ubuntu1 failed to install/upgrade: 
trying to overwrite '/usr/include/opencv/cvaux.hpp', which is also in package 
libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
UpgradeStatus: Upgraded to xenial on 2018-02-14 (8 days ago)

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


** Tags: amd64 apport-package package-conflict xenial

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

Title:
  package libopencv-dev 2.4.9.1+dfsg-1.5ubuntu1 failed to
  install/upgrade: trying to overwrite '/usr/include/opencv/cvaux.hpp',
  which is also in package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1

Status in opencv package in Ubuntu:
  New

Bug description:
  Unable to update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libopencv-dev 2.4.9.1+dfsg-1.5ubuntu1
  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: Wed Feb 21 21:30:46 2018
  DpkgTerminalLog:
   Preparing to unpack .../libopencv-dev_3.3.1_amd64.deb ...
   Unpacking libopencv-dev (3.3.1) over (2.4.9.1+dfsg-1.5ubuntu1) ...
   dpkg: error processing archive 
/home/bruno/Downloads/jetpack/jetpack_download/libopencv-dev_3.3.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/include/opencv/cvaux.hpp', which is also in 
package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
  DuplicateSignature:
   package:libopencv-dev:2.4.9.1+dfsg-1.5ubuntu1
   Unpacking libopencv-dev (3.3.1) over (2.4.9.1+dfsg-1.5ubuntu1) ...
   dpkg: error processing archive 
/home/bruno/Downloads/jetpack/jetpack_download/libopencv-dev_3.3.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/include/opencv/cvaux.hpp', which is also in 
package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
  ErrorMessage: trying to overwrite '/usr/include/opencv/cvaux.hpp', which is 
also in package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: opencv
  Title: package libopencv-dev 2.4.9.1+dfsg-1.5ubuntu1 failed to 
install/upgrade: trying to overwrite '/usr/include/opencv/cvaux.hpp', which is 
also in package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
  UpgradeStatus: Upgraded to xenial on 2018-02-14 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1750955/+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 1750955] Re: package libopencv-dev 2.4.9.1+dfsg-1.5ubuntu1 failed to install/upgrade: trying to overwrite '/usr/include/opencv/cvaux.hpp', which is also in package libcvaux-dev:a

[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 opencv in Ubuntu.
https://bugs.launchpad.net/bugs/1750955

Title:
  package libopencv-dev 2.4.9.1+dfsg-1.5ubuntu1 failed to
  install/upgrade: trying to overwrite '/usr/include/opencv/cvaux.hpp',
  which is also in package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1

Status in opencv package in Ubuntu:
  New

Bug description:
  Unable to update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libopencv-dev 2.4.9.1+dfsg-1.5ubuntu1
  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: Wed Feb 21 21:30:46 2018
  DpkgTerminalLog:
   Preparing to unpack .../libopencv-dev_3.3.1_amd64.deb ...
   Unpacking libopencv-dev (3.3.1) over (2.4.9.1+dfsg-1.5ubuntu1) ...
   dpkg: error processing archive 
/home/bruno/Downloads/jetpack/jetpack_download/libopencv-dev_3.3.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/include/opencv/cvaux.hpp', which is also in 
package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
  DuplicateSignature:
   package:libopencv-dev:2.4.9.1+dfsg-1.5ubuntu1
   Unpacking libopencv-dev (3.3.1) over (2.4.9.1+dfsg-1.5ubuntu1) ...
   dpkg: error processing archive 
/home/bruno/Downloads/jetpack/jetpack_download/libopencv-dev_3.3.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/include/opencv/cvaux.hpp', which is also in 
package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
  ErrorMessage: trying to overwrite '/usr/include/opencv/cvaux.hpp', which is 
also in package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: opencv
  Title: package libopencv-dev 2.4.9.1+dfsg-1.5ubuntu1 failed to 
install/upgrade: trying to overwrite '/usr/include/opencv/cvaux.hpp', which is 
also in package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
  UpgradeStatus: Upgraded to xenial on 2018-02-14 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1750955/+subscriptions

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

[Touch-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

[Daniel van Vugt]

Sorry, I missed the part about the crashes being in the kernel.

Still, part of the above sounds like bug 1274115.

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: pulseaudio (Ubuntu)
 Assignee: Hui Wang (hui.wang) => (unassigned)

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+subscriptions

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

[Touch-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

[Daniel van Vugt]

Commit a222a07920731f3c4967faccab7469af50b428a4 is obviously a little
old. So "Fix Released" for current series. Only needs some work to get
it into xenial.

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+subscriptions

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

[Touch-packages] [Bug 1539967] Re: Audio skips (buffer underruns) intermittently but particularly when screen blanks

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1274115
   snd_pcm_avail() returned a value that is exceptionally large
** This bug has been marked a duplicate of bug 1750947
   pulseaudio print lots of error when selecting unavailable profile

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

Title:
  Audio skips (buffer underruns) intermittently but particularly when
  screen blanks

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Audio playback via ALSA (snd_intel_hda) & pulseaudio inevitably
  'skips' (repeats buffer content) intermittently a few times each hour,
  and severely whenever the screen is blanked for inactivity.

  CPU load is low (mostly idle).

  I didn't have this problem with my previous fresh installation of
  Ubuntu (14.04.3 LTS) on this hardware.

  From dmesg, kernel appears to be using the TSC clocksource:
  [ 3.180127] clocksource: Switched to clocksource tsc

  Upon startup, Pulseaudio sees high resolution timers:
  I: [pulseaudio] main.c: Fresh high-resolution timers available! Bon appetit!

  When audio skips, alsa-sink.c logs a massive scheduling delay (e.g.
  1070.00 ms > 15.99 ms) and also that "snd_pcm_avail() returned a value
  that is exceptionally large: 623124 bytes (1177 ms)"

  Currently running Ubuntu 15.10 Wily (fresh install).
  linux-sound-base:
Installed: 1.0.25+dfsg-0ubuntu5
  pulseaudio:
  Installed: 1:6.0-0ubuntu13

  Audio output used is Built-in Audio Analogue Surround 5.1 (motherboard
  audio, Realtek ALC889A)

  Attaching log from pulseaudio -

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl fglrx
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   chinf  7928 F...m pulseaudio
   /dev/snd/controlC0:  chinf  7928 F pulseaudio
   /dev/snd/controlC1:  chinf  7928 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jan 30 18:17:01 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-11 (50 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: Sound works for a while, then breaks
  Title: [GA-MA790GP-DS4H, Realtek ALC889A, Green Line Out, Rear] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-MA790GP-DS4H
  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.:bvrF6:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-DS4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-DS4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790GP-DS4H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-01-12T14:13:00.166647

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1539967/+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 997482] Re: High CPU & IO usage after starting VirtualBox

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1274115
   snd_pcm_avail() returned a value that is exceptionally large
** This bug has been marked a duplicate of bug 1750947
   pulseaudio print lots of error when selecting unavailable profile

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

Title:
  High CPU & IO usage after starting VirtualBox

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Operating system: Ubuntu 12.04 LTS (up-to-date) with kernel 3.2.0-24-generic 
x86_64
  System: HP EliteBook 8440p Core i7-640M / 4g 500gb 14”
  Package version: 1.0.25+dfsg-0ubuntu1

  Occurences: 1 (that's the first time I have this issue)

  Problem:
   - VirtualBox was opened and try to send sound through alsa drivers.
   - System nearly freezes and the harddrive is working hard.
   - When I get the system back, there were some logs in the /var/log/syslog:

  May 10 07:58:15 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: 
snd_pcm_avail() returned a value that is exceptionally large: 866268 bytes 
(4910 ms).
  May 10 07:58:17 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: Most 
likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this 
issue to the ALSA developers.
  May 10 07:58:17 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: 
snd_pcm_dump():
  May 10 07:58:17 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: Soft 
volume PCM
  May 10 07:58:17 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: Control: 
PCM Playback Volume
  May 10 07:58:17 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: min_dB: 
-51
  May 10 07:58:17 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: max_dB: 0
  May 10 07:58:20 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: 
resolution: 256
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: Its 
setup is:
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   stream 
  : PLAYBACK
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   access 
  : MMAP_INTERLEAVED
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   format 
  : S16_LE
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
subformat: STD
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
channels : 2
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   rate   
  : 44100
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   exact 
rate   : 44100 (44100/1)
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   msbits 
  : 16
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
buffer_size  : 16384
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
period_size  : 8192
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
period_time  : 185759
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
tstamp_mode  : ENABLE
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
period_step  : 1
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
avail_min: 8192
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
period_event : 0
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
start_threshold  : -1
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
stop_threshold   : 4611686018427387904
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
silence_threshold: 0
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
silence_size : 0
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
boundary : 4611686018427387904
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: Slave: 
Hardware PCM card 0 'HDA Intel' device 0 subdevice 0
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: Its 
setup is:
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   stream 
  : PLAYBACK
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   access 
  : MMAP_INTERLEAVED
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   format 
  : S16_LE
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
subformat: STD
  May 10 07:58:24 inf-p-ols dbus[1072]: [system] Failed to activate service 
'org.freedesktop.nm_dispatcher': timed out
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
channels : 2
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   rate   
  : 44100
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   exact 
ra