[Touch-packages] [Bug 1835181] Bug is not a security issue

[Alex Murray]

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

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

Title:
  OpenLDAP LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between
  ldaps:// and ldap:// with STARTTLS

Status in openldap package in Ubuntu:
  New

Bug description:
  This is the same bug as
  https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1547927 which
  has been closed.

  Tested and confirmed present with vivid, wily, xenial and bionic

  Also logged with openldap as
  http://www.openldap.org/its/index.cgi/Incoming?id=8374 however I think
  that this is a packaging issue caused by using GNUTLS rather than
  OpenSSL.

  Important: to replicate the issue you need to connect to an LDAP
  server which presents a certificate with a CN that DOES NOT MATCH the
  connection URI passed to the OpenLDAP client. In practice, this is
  simple enough to achieve by using the IP address of a server rather
  than the FQDN.

  The core of the issue is that the handling of the
  LDAP_OPT_X_TLS_REQUIRE_CERT option appears to be different between
  servers accessed via ldaps:// and ldap:// (plus STARTTLS) URIs.

  When accessing server with an invalid certificate, the results are:

  ldaps://

  never  OK
  hard   Error: can't contact LDAP server
  demand Error: can't contact LDAP server
  allow  OK
  tryError: can't contact LDAP server

  ldap:// plus explicit ldap_start_tls_s()

  never  OK
  hard   OK
  demand OK
  allow  OK
  tryOK

  Based on all the documentation, the results should be the same between
  approaches.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1835181/+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 1835474] [NEW] When running sudo apt-get remove libasound2 It deletes other apps including brave, gimp, audacity, and more

[R W]

Public bug reported:

I am using ubuntu 18.04

the version of the package was the most up to date, as I ran
sudo apt-get install --reinstall libasound2 right before running 
sudo apt-get remove libasound2

This should not touch other applications, even if they were set up to
use the library.

It deleted several applications before I force closed it.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libasound2 1.1.3-5ubuntu0.2
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul  4 20:10:09 2019
Dependencies:
 gcc-8-base 8.3.0-6ubuntu1~18.04.1
 libasound2-data 1.1.3-5ubuntu0.2
 libc6 2.27-3ubuntu1
 libgcc1 1:8.3.0-6ubuntu1~18.04.1
InstallationDate: Installed on 2018-06-22 (377 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-lib
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: alsa-lib (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic delete remove

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

Title:
  When running sudo apt-get remove libasound2 It deletes other apps
  including brave, gimp, audacity, and more

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  I am using ubuntu 18.04

  the version of the package was the most up to date, as I ran
  sudo apt-get install --reinstall libasound2 right before running 
  sudo apt-get remove libasound2

  This should not touch other applications, even if they were set up to
  use the library.

  It deleted several applications before I force closed it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libasound2 1.1.3-5ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  4 20:10:09 2019
  Dependencies:
   gcc-8-base 8.3.0-6ubuntu1~18.04.1
   libasound2-data 1.1.3-5ubuntu0.2
   libc6 2.27-3ubuntu1
   libgcc1 1:8.3.0-6ubuntu1~18.04.1
  InstallationDate: Installed on 2018-06-22 (377 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-lib
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1835474/+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 1835257] Re: update tzdata package to 2019b

[Adam Conrad]

Didn't notice this bug until I'd already done the work, so it's not
linked in changelogs, but tzdata has been updated for eoan, disco,
cosmic, bionic, xenial, and trusty-esm and precise-esm.

** Changed in: tzdata (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

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

Title:
  update tzdata package to 2019b

Status in tzdata package in Ubuntu:
  Fix Released

Bug description:
  Update tzdata package to 2019b.

  https://mm.icann.org/pipermail/tz-announce/2019-July/56.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1835257/+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 1835459] Re: libgl1-mesa-glx errors

[Frank Mascarell]

** Summary changed:

- libgl1-mesa-glx
+ libgl1-mesa-glx errors

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

Title:
  libgl1-mesa-glx errors

Status in mesa package in Ubuntu:
  New

Bug description:
  I have a VPS with Ubuntu 18.04 (implementation of pure software,
  Digital Ocean) and I connect through Windows 10 with an X server,
  Xming and I run Google-Chrome Remote. It works well and opens the
  Chrome remote control on my Windows, although it is quite slow, but it
  works. However, it throws some GPU and OpenGL errors that I can not
  solve. I have reported and are quite frequent errors, as recommended,
  I reinstalled the mesa-utils and libgl1-glx-mesa packages, and errors
  persist. Attached capture of these.

  I have installed (bionic):
  libgl1
  libgl1-mesa-dri
  libgl1-mesa-glx
  libglapi-mesa
  libglib2.0-0
  libglib2.0-data
  libglvnd0
  liglx-mesa0
  libglx0

  dbus
  dbus-x11

  I have searched for help in the stackoverflow forums without any
  success.

  OpenGL Propierties:
  ~$ glxinfo | grep "OpenGL versión"

  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  X Error of failed request: GLXBadContext
Major opcode of failed request: 148 (GLX)
Minor opcode of failed request: 6 (X_GLXIsDirect)
Serial number of failed request: 46
Current serial number in output stream: 45

  And the characteristics of the graphics of my VPS:

  ~ $ lspci -vk

  00: 02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic 
card (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc. QEMU Virtual Machine
   Physical Slot: 2
   Flags: fast devsel, IRQ 10
   Memory at f800 (32-bit, non-prefetchable) [size = 64M]
   Memory at fc00 (32-bit, non-prefetchable) [size = 16M]
   Memory at fd05 (32-bit, non-prefetchable) [size = 8K]
   I / O ports at c0a0 [size = 32]
   Expansion ROM at 000c [disabled] [size = 128K]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1835459/+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 1835459] [NEW] libgl1-mesa-glx

[Frank Mascarell]

Public bug reported:

I have a VPS with Ubuntu 18.04 (implementation of pure software, Digital
Ocean) and I connect through Windows 10 with an X server, Xming and I
run Google-Chrome Remote. It works well and opens the Chrome remote
control on my Windows, although it is quite slow, but it works. However,
it throws some GPU and OpenGL errors that I can not solve. I have
reported and are quite frequent errors, as recommended, I reinstalled
the mesa-utils and libgl1-glx-mesa packages, and errors persist.
Attached capture of these.

I have installed (bionic):
libgl1
libgl1-mesa-dri
libgl1-mesa-glx
libglapi-mesa
libglib2.0-0
libglib2.0-data
libglvnd0
liglx-mesa0
libglx0

dbus
dbus-x11

I have searched for help in the stackoverflow forums without any
success.

OpenGL Propierties:
~$ glxinfo | grep "OpenGL versión"

libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
X Error of failed request: GLXBadContext
  Major opcode of failed request: 148 (GLX)
  Minor opcode of failed request: 6 (X_GLXIsDirect)
  Serial number of failed request: 46
  Current serial number in output stream: 45

And the characteristics of the graphics of my VPS:

~ $ lspci -vk

00: 02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card 
(rev 04) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine
 Physical Slot: 2
 Flags: fast devsel, IRQ 10
 Memory at f800 (32-bit, non-prefetchable) [size = 64M]
 Memory at fc00 (32-bit, non-prefetchable) [size = 16M]
 Memory at fd05 (32-bit, non-prefetchable) [size = 8K]
 I / O ports at c0a0 [size = 32]
 Expansion ROM at 000c [disabled] [size = 128K]

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

** Attachment added: "errores-libgl.jpg"
   
https://bugs.launchpad.net/bugs/1835459/+attachment/5275114/+files/errores-libgl.jpg

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

Title:
  libgl1-mesa-glx

Status in mesa package in Ubuntu:
  New

Bug description:
  I have a VPS with Ubuntu 18.04 (implementation of pure software,
  Digital Ocean) and I connect through Windows 10 with an X server,
  Xming and I run Google-Chrome Remote. It works well and opens the
  Chrome remote control on my Windows, although it is quite slow, but it
  works. However, it throws some GPU and OpenGL errors that I can not
  solve. I have reported and are quite frequent errors, as recommended,
  I reinstalled the mesa-utils and libgl1-glx-mesa packages, and errors
  persist. Attached capture of these.

  I have installed (bionic):
  libgl1
  libgl1-mesa-dri
  libgl1-mesa-glx
  libglapi-mesa
  libglib2.0-0
  libglib2.0-data
  libglvnd0
  liglx-mesa0
  libglx0

  dbus
  dbus-x11

  I have searched for help in the stackoverflow forums without any
  success.

  OpenGL Propierties:
  ~$ glxinfo | grep "OpenGL versión"

  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  X Error of failed request: GLXBadContext
Major opcode of failed request: 148 (GLX)
Minor opcode of failed request: 6 (X_GLXIsDirect)
Serial number of failed request: 46
Current serial number in output stream: 45

  And the characteristics of the graphics of my VPS:

  ~ $ lspci -vk

  00: 02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic 
card (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc. QEMU Virtual Machine
   Physical Slot: 2
   Flags: fast devsel, IRQ 10
   Memory at f800 (32-bit, non-prefetchable) [size = 64M]
   Memory at fc00 (32-bit, non-prefetchable) [size = 16M]
   Memory at fd05 (32-bit, non-prefetchable) [size = 8K]
   I / O ports at c0a0 [size = 32]
   Expansion ROM at 000c [disabled] [size = 128K]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1835459/+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 1822776] Re: [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait

[halfgaar]

Sorry for the delay. I had to write a bash script that increased the
hit-chance of the bug. I now have 13 spinning bash on a non-updated test
server. The one with bash 4.20 is working fine.

Bash is also working without issues.

The new script is attached.

So, all good.

** Attachment added: "Script to reproduce the bash crash"
   
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+attachment/5275112/+files/bash-crash-test.sh

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

Title:
  [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  Long running bash loops that create and reap processes will crash,
  hanging at 100% CPU.

  [Test Case]

  A PPA with the proposed fix included is at:

https://launchpad.net/~bryce/+archive/ubuntu/bash-sru-19-010-1

  Install the PPA with the fix via:

sudo add-apt-repository ppa:bryce/bash-sru-19-010-1
sudo apt-get update
sudo apt-get install bash

  Run this loop for a few days/weeks:

    #!/bin/bash
    while true; do
  sleep 0.5 &
  wait
    done

  It will eventually cause the 'wait' statement to hang, consuming 100%
  after some indeterminate amount of time, dependent on how fast PIDs
  are cycled in the machine.

  The Bash bug report mentions longer running loops, but it seems hash
  collisions are the cause, meaning it's just a matter of chance,
  influenced by how fast PIDs are cycled on the machine.

  [Regression Potential]

  The fix has been reviewed and accepted upstream.  The patch adds a
  test at time of pid determination for if the pid is already in use and
  if so, skip it and pick a different one.  This does change behavior
  slightly in that different pid numbers will be generated in rare
  cases, but nothing should depend on how pids are generated, as the
  behavior is not specified to be anything but random.

  The patch adds a new warning message, "bgp_delete: LOOP: psi (%d) ==
  storage[psi].bucket_next", but this only shows when the original bug
  would have been triggered.

  Using 'apt-get source bash' to get the original source version, I
  created a deb that includes the 4.4.20 patch and have been running it
  since April 2nd. The 100% CPU spinning is solved, and no other
  regressions have been observed.

  Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so
  this involves linearly progressing to the next version (so not
  skipping patches).

  [Fix]

  Official patch to fix, and to bump to 4.4.20:

  http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020

  The newest Ubuntu tar.xz with patches I could find at:

  http://archive.ubuntu.com/ubuntu/pool/main/b/bash/

  also didn't have the 4.4.20 patch, so it seems no Ubuntu release has
  the fix yet.

  Although not completely sure, this problem seems to have been
  introduced in the 4.4 version of Bash, so in term of LTS versions,
  18.04 and up are affected.

  [Original Report]
  Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when 
spawning sub processes and waiting for them. There is a fix:

  https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020

  Our application started being affected (locking up) by this since
  migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1),
  Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version',
  because of their unusual versions as patches, apt shows it as
  4.4.18-2ubuntu1).

  The 4.4-020 version needs to be included. I think it's actually quite
  critical.

  A justification for including the fix would be that a standard
  language feature in a script language is broken, and that it's
  indeterminate when it breaks. Considering the wide spread use of bash,
  I'm surprised not more people have reported issues. My and a client
  started having issues with independently of each other very soon after
  upgrading to an affected version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+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 1834400] Re: pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed

[brian_p]

Giving the cupsfilter command was a hint to try it and report back. The
suggestion to use the everywhere model was a also hint to get you
printing without too much effort.

-- 
Brian.

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

Title:
  pc reports that HP OfficeJet Pro 8715 printed file, but nothing has
  printed

Status in HPLIP:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  I attempted to print a file on a network printer which was set up via
  HPLIP. The PC reports that the print job has started and completed on
  the network printer, but in fact the network printer has not printed
  anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1834400/+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 1463169] Re: NetworkManager should disable IPv6 by default with private IP addresses

[Launchpad Bug Tracker]

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

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

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

Title:
  NetworkManager should disable IPv6 by default with private IP
  addresses

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Where I live the only ISP is giving DSL customers a cheap Huawei DSL
  modem/WiFI router combo device. Except that their customers know
  absolutely nothing about configuring it, and when the rare customer
  does ask to configure it they refuse to give them the username and
  password, claiming that the device belongs to the ISP and only being
  "loaned" to the customer. Unfortunately they provide it out of the box
  with IPv6 support enabled over the LAN. The connected WiFI devices
  still receive an IPv4 address in the 192.168.1.x range, but some kind
  of IPv6 support is enable for devices that support it. This does not
  pose a problem for Windows, Android, and iOS devices, apparently
  because they don't support IPv6.

  But unfortunately Ubuntu devices don't work with this configuration. The 
device connects to WiFI and receives a 192.168.1.x address with DNS and default 
gateway correct, but it can't access the Internet. The way to fix it is:
  1. Open NetworkManager "Edit Connections" for the connection
  2. In the "IPv6 Settings" tab, set "Method" dropdown to "Ignore"
  3. Disconnect and re-connect to WiFI, and it can access the Internet.

  These steps are unnecessary. It seems like NetworkManager should
  always disable IPv6 whenever it receives and address in the private IP
  space, because nobody will use IPv6 on a LAN. This issue is becoming
  increasingly common around the world, and it makes Ubuntu look
  "complicated" to new users in comparison with the antiquated
  proprietary systems that don't support IPv6 and therefore work great
  out of the box.

  Thanks for considering this improvement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1463169/+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 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell

[Sebastien Bacher]

** Description changed:

+ * Impact
+ The package force load a bell sound which can conflicts with the user 
configuration
+ 
+ * Test case
+ - Enable a login sound in session
+ - Login into a GNOME/Ubuntu session
+ -> the configured sound should be played
+ 
+ * Regression potential
+ Try other desktop environments to make sure their login sound behaviour isn't 
changed, it shouldn't since the customization dropped was specific to the 
Ubuntu sound theme
+ 
+ ---
+ 
  The package `pulseaudio` installs a startup script in 
`/etc/xdg/autostart/pulseaudio.desktop`,
  which itself runs `/usr/bin/start-pulseaudio-x11`,
  which loads a number of x11 related modules in `pulseaudio`.
  
  One of these modules is `module-x11-bell`,
  which makes `pulseaudio` play a sound each time a system bell is emitted
  (usually by terminal applications, such as bash or vim).
  
  This is redundant with gnome-shell, which is also able to handle the system 
bell
  (through the gsetting key `org.gnome.desktop.sound event-sounds`).
  
  The gnome system bell is directly configurable by the user (Settings > Sound),
  so it should be preferred over pulseaudio's own system bell.
  
  I suggest to patch the `/usr/bin/start-pulseaudio-x11`,
  to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome 
Shell
  (e.g. if GNOME_SHELL_SESSION_MODE is set).

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

Title:
  pulseaudio should not load module-x11-bell in gnome-shell

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  The package force load a bell sound which can conflicts with the user 
configuration

  * Test case
  - Enable a login sound in session
  - Login into a GNOME/Ubuntu session
  -> the configured sound should be played

  * Regression potential
  Try other desktop environments to make sure their login sound behaviour isn't 
changed, it shouldn't since the customization dropped was specific to the 
Ubuntu sound theme

  ---

  The package `pulseaudio` installs a startup script in 
`/etc/xdg/autostart/pulseaudio.desktop`,
  which itself runs `/usr/bin/start-pulseaudio-x11`,
  which loads a number of x11 related modules in `pulseaudio`.

  One of these modules is `module-x11-bell`,
  which makes `pulseaudio` play a sound each time a system bell is emitted
  (usually by terminal applications, such as bash or vim).

  This is redundant with gnome-shell, which is also able to handle the system 
bell
  (through the gsetting key `org.gnome.desktop.sound event-sounds`).

  The gnome system bell is directly configurable by the user (Settings > Sound),
  so it should be preferred over pulseaudio's own system bell.

  I suggest to patch the `/usr/bin/start-pulseaudio-x11`,
  to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome 
Shell
  (e.g. if GNOME_SHELL_SESSION_MODE is set).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+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 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:12.2-2ubuntu4

---
pulseaudio (1:12.2-2ubuntu4) eoan; urgency=medium

  * debian/patches/0006-load-module-x11-bell.patch:
- remove that old distro patch, it's undocumented, not needed since
  GNOME handles the login sound by itself and create issues in some
  cases (duplicate sound, not respecting the UI choice)
  (lp: #1827842)

  [ Hui Wang ]
  * d/p/0800-stream-restore-Don-t-restore-if-the-active_port-is-P.patch:
- Don't restore the streams to sinks/sources with only unavailable ports
  (LP: #1834138)

 -- Sebastien Bacher   Fri, 28 Jun 2019 11:45:10
+0200

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

Title:
  pulseaudio should not load module-x11-bell in gnome-shell

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The package `pulseaudio` installs a startup script in 
`/etc/xdg/autostart/pulseaudio.desktop`,
  which itself runs `/usr/bin/start-pulseaudio-x11`,
  which loads a number of x11 related modules in `pulseaudio`.

  One of these modules is `module-x11-bell`,
  which makes `pulseaudio` play a sound each time a system bell is emitted
  (usually by terminal applications, such as bash or vim).

  This is redundant with gnome-shell, which is also able to handle the system 
bell
  (through the gsetting key `org.gnome.desktop.sound event-sounds`).

  The gnome system bell is directly configurable by the user (Settings > Sound),
  so it should be preferred over pulseaudio's own system bell.

  I suggest to patch the `/usr/bin/start-pulseaudio-x11`,
  to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome 
Shell
  (e.g. if GNOME_SHELL_SESSION_MODE is set).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+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 1831498] Re: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice)

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 19.0.2-1ubuntu1.1

---
mesa (19.0.2-1ubuntu1.1) disco; urgency=medium

  * radeon-rework-gfx9-scissor-workaround.diff: Fix invisible elements
with GTK on Vega/Raven. (LP: #1831498)

 -- Timo Aaltonen   Mon, 03 Jun 2019 23:52:07 +0300

** Changed in: mesa (Ubuntu Disco)
   Status: Fix Committed => 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/1831498

Title:
  radeonsi: GTK elements become invisible in some applications (GIMP,
  LibreOffice)

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in mesa source package in Disco:
  Fix Released

Bug description:
  [impact]

  imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 :

  "I am currently experiencing some issues with GTK elements
  (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice.

  I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64).

  My hardware is a Ryzen 5 2400G APU with vega graphics."

  [test case]

  test that GIMP/Libreoffice work fine on AMD Vega/Raven

  [regression potential]

  the fix/workaround is already in mesa 19.0.4, shouldn't regress
  anything

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831498/+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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:12.2-2ubuntu4

---
pulseaudio (1:12.2-2ubuntu4) eoan; urgency=medium

  * debian/patches/0006-load-module-x11-bell.patch:
- remove that old distro patch, it's undocumented, not needed since
  GNOME handles the login sound by itself and create issues in some
  cases (duplicate sound, not respecting the UI choice)
  (lp: #1827842)

  [ Hui Wang ]
  * d/p/0800-stream-restore-Don-t-restore-if-the-active_port-is-P.patch:
- Don't restore the streams to sinks/sources with only unavailable ports
  (LP: #1834138)

 -- Sebastien Bacher   Fri, 28 Jun 2019 11:45:10
+0200

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

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

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  No, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1

[Mathew Hodson]

** No longer affects: openssl (Ubuntu)

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

Title:
  18.04/Apache2: rejecting client initiated renegotiation due to openssl
  1.1.1

Status in apache2 package in Ubuntu:
  Fix Released
Status in apache2 source package in Bionic:
  Fix Committed
Status in apache2 source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Under the following conditions, https connections using client cert 
authentication will suffer a long delay (about 15s if modreqtimeout is enabled, 
more if it is disabled):
  * TLSv1.2
  * client certificate authentication in use
  * a Location, Directory, or other such block defining the client certificate 
authentication for that block only, differing from the SSL vhost as a whole

  This was triggered by the OpenSSL 1.1.1 SRU and was caused by this
  openssl change in SSL_MODE_AUTO_RETRY from disabled to enabled by
  default:
  
https://github.com/openssl/openssl/blob/a4a90a8a3bdcb9336b5c9c15da419e99a87bc6ed/CHANGES#L121-L130

  [Test Case]

  It helps if you have lxd up and running. Otherwise, a VM or even bare
  metal host also works, as long as you stick to the "ubuntu" hostname.

  Launch a container for the release you are testing. The command below is for 
bionic:
  $ lxc launch ubuntu-daily:bionic ubuntu

  Enter the container as root:
  $ lxc exec ubuntu bash

  Verify hostname is "ubuntu":
  # hostname
  ubuntu

  Install apache2:
  apt update && apt install apache2

  Download the following files from this bug report and place them in 
/etc/apache2:
  cd /etc/apache2
  wget 
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274492/+files/cacert.pem
 
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274493/+files/ubuntu.pem
 
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274494/+files/ubuntu.key

  Adjust permissions of the key file:
  chmod 0640 /etc/apache2/ubuntu.key
  chgrp www-data /etc/apache2/ubuntu.key

  Download the client certificate and key files and place them in /root:
  cd /root
  wget 
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274495/+files/client-auth.pem
 
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274496/+files/client-auth.key

  Create this vhost file (caution, lines may wrap, in particular LogFormat: it 
should be one long line):
  cat > /etc/apache2/sites-available/cert-auth-test.conf <
  
  LogLevel info ssl:warn
  ServerAdmin webmaster@localhost
  DocumentRoot /var/www/html
  LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" 
\"%{User-Agent}i\" protocol=%{SSL_PROTOCOL}x commonName=%{SSL_CLIENT_S_DN_CN}x" 
combined-ssl
  ErrorLog \${APACHE_LOG_DIR}/error.log
  CustomLog \${APACHE_LOG_DIR}/access.log combined-ssl
  SSLEngine on
  SSLCertificateFile  /etc/apache2/ubuntu.pem
  SSLCertificateKeyFile /etc/apache2/ubuntu.key
  SSLCACertificateFile /etc/apache2/cacert.pem
  
  SSLOptions +StdEnvVars
  
  
  SSLOptions +StdEnvVars
  
  
  SSLVerifyClient require
  Require ssl-verify-client
  
  
  
  EOF

  Enable the ssl module and this new vhost we just created:
  a2enmod ssl && a2ensite cert-auth-test.conf

  Restart apache2:
  systemctl restart apache2

  If at this stage you try the following command, it will fail like this 
because no client certificate was provided:
  # curl --output /dev/null https://ubuntu/ --cacert /etc/apache2/cacert.pem
    % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
   Dload  Upload   Total   SpentLeft  Speed
    0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  curl: (56) OpenSSL SSL_read: error:14094410:SSL 
routines:ssl3_read_bytes:sslv3 alert handshake failure, errno 0

  And the apache error log will confirm the reason:
  [Mon Jul 01 14:10:23.312645 2019] [ssl:error] [pid 1685:tid 140326396421888] 
SSL Library Error: error:1417C0C7:SSL 
routines:tls_process_client_certificate:peer did not return a certificate -- No 
CAs known to server for verification?

  Now retry, but providing the client certificate and key files, and forcing 
TLSv1.2 just to be sure. Due to the bug, the command will stall for about 15 
seconds, but the index.html file will be downloaded:
  # rm -f index.html
  # curl --output index.html https://ubuntu/ --cacert /etc/apache2/cacert.pem 
--cert client-auth.pem --key client-auth.key --tlsv1.2
    % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
   Dload  Upload   Total   SpentLeft  Speed
  100 10918  100 10918

[Touch-packages] [Bug 1833231] Re: cups ftbfs in eoan (amd64 only)

[Till Kamppeter]

The log linked in the initial description has been deleted, but I have also 
discovered a build problem when building locally, not being able to identify my 
problem with the one reported here.
I have observed a segfault in pdftoraster during the "make check". I have 
already reported it upstream here:

https://github.com/OpenPrinting/cups-filters/issues/131

The contributor of the current version of pdftoraster should fix it
soon.

** Bug watch added: github.com/OpenPrinting/cups-filters/issues #131
   https://github.com/OpenPrinting/cups-filters/issues/131

** Also affects: cups-filters (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  cups ftbfs in eoan (amd64 only)

Status in cups package in Ubuntu:
  Incomplete
Status in cups-filters package in Ubuntu:
  New

Bug description:
  cups ftbfs in eoan (amd64 only) in a test rebuild:

  https://launchpadlibrarian.net/428250411/buildlog_ubuntu-eoan-
  amd64.cups_2.2.10-6ubuntu1_BUILDING.txt.gz

  E [14/Jun/2019:14:46:57.037970 +] Unknown default SystemGroup "lpadmin".
  PASS: 8 warning messages.
  PASS: 0 notice messages.
  PASS: 760 info messages.
  PASS: 24065 debug messages.
  PASS: 25573 debug2 messages.

  Copied log file "access_log-2019-06-14-buildd" to test directory.
  Copied log file "debug_log-2019-06-14-buildd" to test directory.
  Copied log file "error_log-2019-06-14-buildd" to test directory.
  Copied log file "page_log-2019-06-14-buildd" to test directory.
  Copied report file "cups-str-2019-06-14-buildd.html" to test directory.

  1 tests failed.
  make[2]: *** [Makefile:257: check] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [debian/rules:201: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:17: build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1833231/+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 1832108] Re: unmkinitramfs fails with lz4 compressed initrds

[Dimitri John Ledkov]

lz4

6644040 bytes read in 282 ms (22.5 MiB/s)
4466915 bytes read in 191 ms (22.3 MiB/s)
reboot time 39.49s
2019-07-04T16:54:38.012115+ localhost kernel: Unpacking initramfs...
2019-07-04T16:54:38.012178+ localhost kernel: Initramfs unpacking failed: 
Decoding failed
2019-07-04T16:54:38.012246+ localhost kernel: Freeing initrd memory: 4404K

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

Title:
  unmkinitramfs fails with lz4 compressed initrds

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Cosmic:
  In Progress
Status in initramfs-tools source package in Disco:
  Fix Released
Status in initramfs-tools package in Debian:
  New

Bug description:
  [Impact]

   * Cannot unpack initrds compressed with lz4 due to changes in lz4

  [Test Case]

  $ sudo apt install initramfs-tools lz4 file
  $ mkinitramfs -c lz4 -o foo.img
  $ lsinitramfs foo.img
  cpio: premature end of archive

  [Regression Potential]

   * New lz4cat is more strict w.r.t. enforcing file name extensions,
  thus the fix is to feed a stream to lz4cat instead of asking it to
  open a file. The performance impact should be similar between both
  methods of reading file contents during ls/unmk-initramfs time.

  [Other Info]

  Original bug report:

  unmkinitramfs fails with lz4 compressed initrds

  Note:
  $ lz4cat -t unmkinitramfs_Cz6Yl9
  File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process 
file: unmkinitramfs_Cz6Yl9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832108/+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 1832108] Re: unmkinitramfs fails with lz4 compressed initrds

[Dimitri John Ledkov]

uncompressed:

7330304 bytes read in 311 ms (22.5 MiB/s)
reboot time 39.39s
2019-07-04T16:54:38.050180+ localhost kernel: Unpacking initramfs...
2019-07-04T16:54:38.050253+ localhost kernel: Freeing initrd memory: 7200K

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

Title:
  unmkinitramfs fails with lz4 compressed initrds

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Cosmic:
  In Progress
Status in initramfs-tools source package in Disco:
  Fix Released
Status in initramfs-tools package in Debian:
  New

Bug description:
  [Impact]

   * Cannot unpack initrds compressed with lz4 due to changes in lz4

  [Test Case]

  $ sudo apt install initramfs-tools lz4 file
  $ mkinitramfs -c lz4 -o foo.img
  $ lsinitramfs foo.img
  cpio: premature end of archive

  [Regression Potential]

   * New lz4cat is more strict w.r.t. enforcing file name extensions,
  thus the fix is to feed a stream to lz4cat instead of asking it to
  open a file. The performance impact should be similar between both
  methods of reading file contents during ls/unmk-initramfs time.

  [Other Info]

  Original bug report:

  unmkinitramfs fails with lz4 compressed initrds

  Note:
  $ lz4cat -t unmkinitramfs_Cz6Yl9
  File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process 
file: unmkinitramfs_Cz6Yl9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832108/+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 1832108] Re: unmkinitramfs fails with lz4 compressed initrds

[Dimitri John Ledkov]

gzip

6644040 bytes read in 283 ms (22.4 MiB/s)
3889013 bytes read in 167 ms (22.2 MiB/s)
reboot time 40.31s
2019-07-04T16:54:37.997158+ localhost kernel: Unpacking initramfs...
2019-07-04T16:54:37.997230+ localhost kernel: Freeing initrd memory: 3840K

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

Title:
  unmkinitramfs fails with lz4 compressed initrds

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Cosmic:
  In Progress
Status in initramfs-tools source package in Disco:
  Fix Released
Status in initramfs-tools package in Debian:
  New

Bug description:
  [Impact]

   * Cannot unpack initrds compressed with lz4 due to changes in lz4

  [Test Case]

  $ sudo apt install initramfs-tools lz4 file
  $ mkinitramfs -c lz4 -o foo.img
  $ lsinitramfs foo.img
  cpio: premature end of archive

  [Regression Potential]

   * New lz4cat is more strict w.r.t. enforcing file name extensions,
  thus the fix is to feed a stream to lz4cat instead of asking it to
  open a file. The performance impact should be similar between both
  methods of reading file contents during ls/unmk-initramfs time.

  [Other Info]

  Original bug report:

  unmkinitramfs fails with lz4 compressed initrds

  Note:
  $ lz4cat -t unmkinitramfs_Cz6Yl9
  File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process 
file: unmkinitramfs_Cz6Yl9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832108/+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 1832108] Re: unmkinitramfs fails with lz4 compressed initrds

[Dimitri John Ledkov]

ls -latr initrd-lzma.img initrd-uncompressed.img initrd-gzip.img 
initrd-lz49l.img | sort
-rwxr-xr-x 1 xnox xnox 2852487 Jul  5 00:19 initrd-lzma.img
-rwxr-xr-x 1 xnox xnox 3889013 Jul  5 00:21 initrd-gzip.img
-rwxr-xr-x 1 xnox xnox 4466915 Jul  5 00:22 initrd-lz49l.img
-rwxr-xr-x 1 xnox xnox 7330304 Jul  5 00:20 initrd-uncompressed.img

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

Title:
  unmkinitramfs fails with lz4 compressed initrds

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Cosmic:
  In Progress
Status in initramfs-tools source package in Disco:
  Fix Released
Status in initramfs-tools package in Debian:
  New

Bug description:
  [Impact]

   * Cannot unpack initrds compressed with lz4 due to changes in lz4

  [Test Case]

  $ sudo apt install initramfs-tools lz4 file
  $ mkinitramfs -c lz4 -o foo.img
  $ lsinitramfs foo.img
  cpio: premature end of archive

  [Regression Potential]

   * New lz4cat is more strict w.r.t. enforcing file name extensions,
  thus the fix is to feed a stream to lz4cat instead of asking it to
  open a file. The performance impact should be similar between both
  methods of reading file contents during ls/unmk-initramfs time.

  [Other Info]

  Original bug report:

  unmkinitramfs fails with lz4 compressed initrds

  Note:
  $ lz4cat -t unmkinitramfs_Cz6Yl9
  File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process 
file: unmkinitramfs_Cz6Yl9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832108/+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 1832108] Re: unmkinitramfs fails with lz4 compressed initrds

[Dimitri John Ledkov]

$ file initrd.img 
initrd.img: LZMA compressed data, streamed

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

Title:
  unmkinitramfs fails with lz4 compressed initrds

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Cosmic:
  In Progress
Status in initramfs-tools source package in Disco:
  Fix Released
Status in initramfs-tools package in Debian:
  New

Bug description:
  [Impact]

   * Cannot unpack initrds compressed with lz4 due to changes in lz4

  [Test Case]

  $ sudo apt install initramfs-tools lz4 file
  $ mkinitramfs -c lz4 -o foo.img
  $ lsinitramfs foo.img
  cpio: premature end of archive

  [Regression Potential]

   * New lz4cat is more strict w.r.t. enforcing file name extensions,
  thus the fix is to feed a stream to lz4cat instead of asking it to
  open a file. The performance impact should be similar between both
  methods of reading file contents during ls/unmk-initramfs time.

  [Other Info]

  Original bug report:

  unmkinitramfs fails with lz4 compressed initrds

  Note:
  $ lz4cat -t unmkinitramfs_Cz6Yl9
  File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process 
file: unmkinitramfs_Cz6Yl9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832108/+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 1832108] Re: unmkinitramfs fails with lz4 compressed initrds

[Dimitri John Ledkov]

Testing on cm3

switch to partitions #0, OK
mmc0(part 0) is current device
LOADBOOTENV
** Unable to read file uEnv.txt **
Running uenvcmd ...
ENVCMD
6644040 bytes read in 282 ms (22.5 MiB/s) (this is kernel)
2852487 bytes read in 123 ms (22.1 MiB/s) (this is initrd)
FAT: Misaligned buffer address (023b8687)
42049 bytes read in 14 ms (2.9 MiB/s)

2019-07-04T15:35:05.998027+ localhost kernel: Unpacking initramfs...
2019-07-04T15:35:05.998089+ localhost kernel: Freeing initrd memory: 2828K

(not sure if above is true gzip decompression speed of initramfs or not)

Watching telnet, from reboot until "Press enter to configure" took
41.84s (42.25s 41.50s).

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

Title:
  unmkinitramfs fails with lz4 compressed initrds

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Cosmic:
  In Progress
Status in initramfs-tools source package in Disco:
  Fix Released
Status in initramfs-tools package in Debian:
  New

Bug description:
  [Impact]

   * Cannot unpack initrds compressed with lz4 due to changes in lz4

  [Test Case]

  $ sudo apt install initramfs-tools lz4 file
  $ mkinitramfs -c lz4 -o foo.img
  $ lsinitramfs foo.img
  cpio: premature end of archive

  [Regression Potential]

   * New lz4cat is more strict w.r.t. enforcing file name extensions,
  thus the fix is to feed a stream to lz4cat instead of asking it to
  open a file. The performance impact should be similar between both
  methods of reading file contents during ls/unmk-initramfs time.

  [Other Info]

  Original bug report:

  unmkinitramfs fails with lz4 compressed initrds

  Note:
  $ lz4cat -t unmkinitramfs_Cz6Yl9
  File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process 
file: unmkinitramfs_Cz6Yl9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832108/+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 1835257] Re: update tzdata package to 2019b

[Luiz Vitor Martinez Cardoso]

>
> Card not found.
> This card may be on a private board. If someone gave you this link, they
> may need to invite you to one of their boards or teams.


On Thu, Jul 4, 2019 at 12:26 PM Dimitri John Ledkov 
wrote:

> https://trello.com/c/CVhZRo2o
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1835257
>
> Title:
>   update tzdata package to 2019b
>
> Status in tzdata package in Ubuntu:
>   New
>
> Bug description:
>   Update tzdata package to 2019b.
>
>   https://mm.icann.org/pipermail/tz-announce/2019-July/56.html
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1835257/+subscriptions
>


-- 
*Luiz Vitor Martinez Cardoso*

CEO & Founder at geeksys.com.br
+55 (11) 97351-7097 | Skype: grabberbr

*"If you wanna be successful, you need total dedication, go for your last
limit, give your best and love your love infinitely!"*

*"The only limits are the ones you place upon yourself"*

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

Title:
  update tzdata package to 2019b

Status in tzdata package in Ubuntu:
  New

Bug description:
  Update tzdata package to 2019b.

  https://mm.icann.org/pipermail/tz-announce/2019-July/56.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1835257/+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 1835257] Re: update tzdata package to 2019b

[Dimitri John Ledkov]

https://trello.com/c/CVhZRo2o

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

Title:
  update tzdata package to 2019b

Status in tzdata package in Ubuntu:
  New

Bug description:
  Update tzdata package to 2019b.

  https://mm.icann.org/pipermail/tz-announce/2019-July/56.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1835257/+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 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns

[Till Kamppeter]

I asked on the upstream mailing list and got the following answer:

--
Hi,

the domain specification in the configuration reported on launchpad:

 [Resolve]
 Cache=no
 DNS=127.0.0.54
 Domains=~.local.org.com

is invalid:

 systemd-resolved[13415]: Failed to add search domain '~.local.org.com',
ignoring: Invalid argument

The correct form should be without the dot:

 Domains=~local.org.com

Can you ask to fix that configuration error and try again? Otherwise,
queries for the local.org.com domain are not routed to the local
dnsmasq instance.

Beniamino
--

Could you correct your configuration and try again? Please report back
here, thanks.

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

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

Title:
  network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured
  dns

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Bionic:
  Incomplete

Bug description:
  On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1
  1.10.14-0ubuntu2` lead to scoped DNS servers defined in
  `/etc/systemd/resolved.conf.d/*.conf` being ignored.

  Downgrading with `sudo apt-get install network-
  manager=1.10.6-2ubuntu1.1` has resolved the issue for now.

  Example systemd-resolved conf:

  [Resolve]
  Cache=no
  DNS=127.0.0.54
  Domains=~.local.org.com

  Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving
  queries in that subdomain.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+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 1834494] Re: latest bzip2 reports crc errors incorrectly

[Launchpad Bug Tracker]

This bug was fixed in the package bzip2 - 1.0.6-8.1ubuntu0.2

---
bzip2 (1.0.6-8.1ubuntu0.2) bionic-security; urgency=medium

  * SECURITY REGRESSION: bzip2 update for CVE-2019-12900 causes some files 
raises
incorrect CRC error. (LP: #1834494)
- debian/patches/Accept-as-many-selectors-as-selectors*.patch

 -- leo.barb...@canonical.com (Leonidas S. Barbosa)  Thu, 04 Jul 2019
09:35:36 -0300

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  In Progress
Status in bzip2 source package in Xenial:
  Fix Released
Status in bzip2 source package in Bionic:
  Fix Released
Status in bzip2 source package in Cosmic:
  Fix Released
Status in bzip2 source package in Disco:
  Fix Released
Status in bzip2 package in Debian:
  Confirmed

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1834494] Re: latest bzip2 reports crc errors incorrectly

[Launchpad Bug Tracker]

This bug was fixed in the package bzip2 - 1.0.6-9ubuntu0.18.10.1

---
bzip2 (1.0.6-9ubuntu0.18.10.1) cosmic-security; urgency=medium

  * SECURITY REGRESSION: bzip2 update for CVE-2019-12900 causes some files 
raises
incorrect CRC error. (LP: #1834494)
- debian/patches/Accept-as-many-selectors-as-selectors*.patch

 -- leo.barb...@canonical.com (Leonidas S. Barbosa)  Thu, 04 Jul 2019
09:40:45 -0300

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

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

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  In Progress
Status in bzip2 source package in Xenial:
  Fix Released
Status in bzip2 source package in Bionic:
  Fix Released
Status in bzip2 source package in Cosmic:
  Fix Released
Status in bzip2 source package in Disco:
  Fix Released
Status in bzip2 package in Debian:
  Confirmed

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1834494] Re: latest bzip2 reports crc errors incorrectly

[Launchpad Bug Tracker]

This bug was fixed in the package bzip2 - 1.0.6-8ubuntu0.2

---
bzip2 (1.0.6-8ubuntu0.2) xenial-security; urgency=medium

  * SECURITY REGRESSION: bzip2 update for CVE-2019-12900 causes some files 
raises
incorrect CRC error. (LP: #1834494)
- debian/patches/Accept-as-many-selectors-as-selectors*.patch

 -- leo.barb...@canonical.com (Leonidas S. Barbosa)  Thu, 04 Jul 2019
09:27:38 -0300

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

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

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

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  In Progress
Status in bzip2 source package in Xenial:
  Fix Released
Status in bzip2 source package in Bionic:
  Fix Released
Status in bzip2 source package in Cosmic:
  Fix Released
Status in bzip2 source package in Disco:
  Fix Released
Status in bzip2 package in Debian:
  Confirmed

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1834494] Re: latest bzip2 reports crc errors incorrectly

[Launchpad Bug Tracker]

This bug was fixed in the package bzip2 - 1.0.6-9ubuntu0.19.04.1

---
bzip2 (1.0.6-9ubuntu0.19.04.1) disco-security; urgency=medium

  * SECURITY REGRESSION: bzip2 update for CVE-2019-12900 causes some files 
raises
incorrect CRC error. (LP: #1834494)
- debian/patches/Accept-as-many-selectors-as-selectors*.patch

 -- leo.barb...@canonical.com (Leonidas S. Barbosa)  Thu, 04 Jul 2019
09:50:14 -0300

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  In Progress
Status in bzip2 source package in Xenial:
  Fix Released
Status in bzip2 source package in Bionic:
  Fix Released
Status in bzip2 source package in Cosmic:
  Fix Released
Status in bzip2 source package in Disco:
  Fix Released
Status in bzip2 package in Debian:
  Confirmed

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1832123] Re: [SRU] Bugfix release 1.14.5

[Iain Lane]

** No longer affects: gst-omx (Ubuntu)

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

Title:
  [SRU] Bugfix release 1.14.5

Status in gst-libav1.0 package in Ubuntu:
  New
Status in gst-plugins-bad1.0 package in Ubuntu:
  New
Status in gst-plugins-base1.0 package in Ubuntu:
  New
Status in gst-plugins-good1.0 package in Ubuntu:
  New
Status in gst-plugins-ugly1.0 package in Ubuntu:
  New
Status in gst-python1.0 package in Ubuntu:
  New
Status in gst-rtsp-server1.0 package in Ubuntu:
  New
Status in gstreamer-editing-services1.0 package in Ubuntu:
  New
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.
  ---

  Highlighted bugfixes in 1.14.5

  GStreamer core

  -   aggregator: take the pad lock around queue gap event removal
  -   aggregator: don’t leak gap buffer when out of segment
  -   buffer: fix possible memory corruption in gst_buffer_foreach_meta() when 
removing metas
  -   bus: Make removing of signal/bus watches thread-safe
  -   bus: Don’t allow removing signal watches with gst_bus_remove_watch()
  -   controlbinding: Check if the weak pointer was cleared before explicitly 
removing it
  -   ptp clock: Wait for ANNOUNCE before selecting a master; increase 
tolerance for late follow-up and delay-resp
  -   segment: Allow stop == -1 in gst_segment_to_running_time() and negative 
rate
  -   g-i: annotations fixes

  gst-plugins-base

  -   audioconvert: fix endianness conversion for unpacked formats (e.g. 
S24_32BE)
  -   audioringbuffer: Fix wrong memcpy address when reordering channels
  -   decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup
  -   glviewconvert: fix output when a transformation matrix is used
  -   glupload: prevent segfault when updating caps
  -   gl/egl: Determine correct format on dmabuf import
  -   glupload: dmabuf: be explicit about gl formats used
  -   id3tag: validate the year from v1 tags before passing to GstDateTime
  -   rtpbasepayload: fix sequence numbers when using buffer lists
  -   rtspconnection: fix security issue, potential heap overflow 
(CVE-2019-9928)
  -   rtspconnection: fix GError set over the top of a previous GError
  -   rtspconnection: do not duplicate authentication headers
  -   subparse: don’t assert when failing to parse subrip timestamp
  -   video: various convert sample frame fixes
  -   video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, 
A420_10LE/BE to BGRA/RGBA which created corrupted output
  -   video-format: Fix GBRA_10/12 alpha channel pixel strides

  gst-plugins-good

  -   flv: Use 8kHz sample rate for alaw/mulaw audio
  -   flvdemux: Do not error out if the first added and chained pad is not 
linked
  -   flvmux: try harder to make sure timestamps are always increasing
  -   gdkpixbufdec: output a TIME segment which is what’s expected for raw video
  -   matroskademux: fix handling of MS ACM audio
  -   matroska: fix handling of FlagInterlaced
  -   pulsesink: Deal with not being able to convert a format to caps
  -   rtph265depay, rtph264depay; aggregation packet marker handling fixes
  -   rtpmp4gdepay: detect broken senders who send AAC with ADTS frames
  -   rtprawdepay: keep buffer pool around when flushing/seeking
  -   rtpssrcdemux: Forward serialized events to all pads
  -   qmlglsink: Handle OPENGL header guard changes
  -   qtdemux: fix track language code parsing; ignore corrupted CTTS box
  -   qtmux: Correctly set tkhd width/height to the display size
  -   splitmuxsink: various timecode meta handling fixes
  -   splitmuxsink: make work with audio-only encoders as muxers, e.g. wavenc
  -   v4l2sink: fix pool-less allocation query handling
  -   v4l2dec/enc: fix use after free when handling events
  -   vpx: Fix build against libvpx 1.8
  -   webmmux: allow resolutions above 4096

  gst-plugins-ugly

  -   sid: Fix cross-compilation by using AC_TRY_LINK instead of AC_TRY_RUN
  -   x264: Only enable dynamic loading code for x264 before v253

  gst-plugins-bad

  -   assrender: fix disappearing subtitles when seeking back in time
  -   decklinkvideosink: fix segfault when audiosink is closed before videosink
  -   decklinkvideosrc: respect pixel format property even if mode is set to 
auto
  -   d3dvideosink: Fix 

[Touch-packages] [Bug 1835404] [NEW] bzip2 data integrity error when decompressing

[Leon Anavi]

Public bug reported:

Hi,

With the latest version of bzip2, 1.0.6-8.1ubuntu0.1, I am unable to
extract several archives from nvidia.com. For example with archive:
https://developer.download.nvidia.com/embedded/L4T/r32_Release_v1.0/jax-
tx2/BSP/JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2

Exactly the same archives work perfectly fine with bzip2 version 1.0.6-8
(the previous release before 1.0.6-8.1ubuntu0.1.

I am experiencing these issues with bzip2 1.0.6-8.1ubuntu0 on both
Ubuntu 16.04 and 18.04. Here are details to reproduce the issue:

leon@u1804:~$ apt-cache policy bzip2
bzip2:
  Installed: 1.0.6-8.1ubuntu0.1
  Candidate: 1.0.6-8.1ubuntu0.1
  Version table:
 *** 1.0.6-8.1ubuntu0.1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
100 /var/lib/dpkg/status
 1.0.6-8.1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
leon@u1804:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:   bionic
leon@u1804:~$ wget 
https://developer.download.nvidia.com/embedded/L4T/r32_Release_v1.0/jax-tx2/BSP/JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2
--2019-07-04 10:47:12--  
https://developer.download.nvidia.com/embedded/L4T/r32_Release_v1.0/jax-tx2/BSP/JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2
Resolving developer.download.nvidia.com (developer.download.nvidia.com)... 
192.229.221.58, 2606:2800:233:ef6:15dd:1ece:1d50:1e1
Connecting to developer.download.nvidia.com 
(developer.download.nvidia.com)|192.229.221.58|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 125799502 (120M) [application/octet-stream]
Saving to: ‘JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2’

JAX-TX2-Jetson_Linux_R32.1.0_aa
100%[===>] 119.97M
27.6MB/sin 4.4s

2019-07-04 10:47:32 (27.2 MB/s) - ‘JAX-
TX2-Jetson_Linux_R32.1.0_aarch64.tbz2’ saved [125799502/125799502]

leon@u1804:~$ bzip2 -dvv JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2 
  JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2: 
[1: huff+mtf rt+rld]
[2: huff+mtf rt+rld]
[3: huff+mtf rt+rld]
[4: huff+mtf rt+rld]
[5: huff+mtf 
bzip2: Data integrity error when decompressing.
Input file = JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2, output file = 
JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tar

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

bzip2: Deleting output file JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tar, if
it exists.


Best regards,
Leon

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


** Tags: bzip2 tbz2

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

Title:
  bzip2 data integrity error when decompressing

Status in bzip2 package in Ubuntu:
  New

Bug description:
  Hi,

  With the latest version of bzip2, 1.0.6-8.1ubuntu0.1, I am unable to
  extract several archives from nvidia.com. For example with archive:
  https://developer.download.nvidia.com/embedded/L4T/r32_Release_v1.0
  /jax-tx2/BSP/JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2

  Exactly the same archives work perfectly fine with bzip2 version
  1.0.6-8 (the previous release before 1.0.6-8.1ubuntu0.1.

  I am experiencing these issues with bzip2 1.0.6-8.1ubuntu0 on both
  Ubuntu 16.04 and 18.04. Here are details to reproduce the issue:

  leon@u1804:~$ apt-cache policy bzip2
  bzip2:
Installed: 1.0.6-8.1ubuntu0.1
Candidate: 1.0.6-8.1ubuntu0.1
Version table:
   *** 1.0.6-8.1ubuntu0.1 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.6-8.1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  leon@u1804:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic
  leon@u1804:~$ wget 
https://developer.download.nvidia.com/embedded/L4T/r32_Release_v1.0/jax-tx2/BSP/JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2
  --2019-07-04 10:47:12--  
https://developer.download.nvidia.com/embedded/L4T/r32_Release_v1.0/jax-tx2/BSP/JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2
  Resolving developer.download.nvidia.com (developer.download.nvidia.com)... 
192.229.221.58, 2606:2800:233:ef6:15dd:1ece:1d50:1e1
  Connecting to developer.download.nvidia.com 
(developer.download.nvidia.com)|192.229.221.58|:443... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 125799502 (120M) 

[Touch-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

[Hui Wang]

@Sebastien,

I checked the ubuntu eaon also uses pulseaudio_12.2-2ubuntu3 which is
same as the disco uses, so the debdiff in the #5 can be applied to eaon
too, could we apply the #5 to eaon first? or I need to re-generate a
debdiff for eaon?

thx.

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

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

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  No, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1805543] Re: Packaged version of iptables doesn't provide --random-fully flag.

[Todd B]

I found this thread because I ran into a problem with a brand-new
installation of Kubernetes (K8s) running in AWS that was failing a large
number of browser requests being serviced by the K8s cluster. There is a
ton of detail about this problem at https://tech.xing.com/a-reason-for-
unexplained-connection-timeouts-on-kubernetes-docker-abd041cf7e02. To
make a very long story short, we need the 1.6.2+ version of iptables on
Ubuntu because it supports the --random-fully flag. Without this, any
K8s cluster created on Ubuntu is pretty useless if you use local DNS to
resolve cluster services by name (e.g. http://my-backend-microservice),
which is what we do to support namespaces for reverse proxies (nginx).

I manually built iptables 1.6.2 using the instructions at
http://www.linuxfromscratch.org/blfs/view/8.2/postlfs/iptables.html and
my problem appears to be solved. It would be great if the change could
be backported into bionic, but at the minimum getting this into the next
LTS then that would be great. If it makes any difference, iptables in
Debian buster is at 1.8.2-4. They have a planned release in, oh look at
that, two days :-)

As for test cases, in this particular instance it's sufficient that when
using the --random-fully flag to set up a NAT masquerading rule that the
NF_NAT_RANGE_PROTO_RANDOM_FULLY flag is set. I can't say what the
regression potential is, but since it's a minor release then I'd expect
it to be minimal. The diffs are at
https://www.netfilter.org/projects/iptables/files/patch-
iptables-1.6.1-1.6.2.bz2

Here are some details of my installation:

ubuntu@kubernetes-master:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:   bionic

ubuntu@kubernetes-master:~$ uname -a
Linux kubernetes-master 4.15.0-1043-aws #45-Ubuntu SMP Mon Jun 24 14:07:03 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Packaged version of iptables doesn't provide --random-fully flag.

Status in iptables package in Ubuntu:
  Confirmed

Bug description:
  Hello.  This isn't strictly a bug, but more of an upgrade-request on
  the iptables package.  Normally i wouldn't be inclined to submit such
  a bug report, but a user on the ubuntu-devel-discuss mailing list
  encouraged me to submit this anyway [1].  For our production systems,
  we're running into a kernel race condition bug, for which a workaround
  has been made available.  The fix boils down to iptables having a new
  flag which it passes down to the kernel, to enable the workaround.
  However, the version of iptables in Ubuntu (v1.6.1) doesn't support
  that kernel feature yet.  Specifically, it's introduced in this commit
  on the iptables codebase:
  
https://git.netfilter.org/iptables/commit/?id=8b0da2130b8af3890ef20afb2305f11224bb39ec.

  The feature we need from that commit is part of the v1.6.2 and newer
  iptables releases, but it looks like the Bionic, Cosmic, and Disco
  releases of Ubuntu all include v1.6.1 without that patch, so for now
  we're going to have to build iptables from source on our production
  machines.  That shouldn't pose any huge issues, but of course, we'd
  prefer to be able to use the package from package management, or
  perhaps a backported package from a newer Ubuntu release.

  So to summarise, this might be an invalid bug report, but consider it
  a vote to upgrade the packaged version of iptables.  If this bug
  report is entirely inappropriate, then I apologise.

  1. Link to thread on ubuntu-devel-discuss where I describe the problem
  and Nish suggests I file this bug report:
  https://lists.ubuntu.com/archives/ubuntu-devel-
  discuss/2018-November/018181.html

  Ubuntu version we're using: 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  $ apt-cache policy iptables
  iptables:
Installed: 1.6.1-2ubuntu2
Candidate: 1.6.1-2ubuntu2
Version table:
   *** 1.6.1-2ubuntu2 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 
Packages
  100 /var/lib/dpkg/status

  Thanks for your time,

  Paul

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1805543/+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 1770961] Re: Add options to set the snappy refresh schedule

[Matthew Paul Thomas]

The snap-related feature is already implemented, and other issues
concerning the settings GUI are tracked here, so I think this is the
appropriate place for it.

Currently, my design for the update settings starts with a line of
static text:

  Snap packages check for updates four times daily, downloading
automatically.

  For other packages…

There I’m trying to convey that the “Check for updates automatically:”
menu below applies to other packages, not snaps.


I intended that eventually, that line of text would become interactive —
perhaps a menu, followed by another menu or timepickers depending on the
setting, for example:

  Snap packages check for updates: [Every day:^] [4 times daily :^]

  Snap packages check for updates: [Weekdays :^] [between :^] [18:15]
and [19:00]

  Snap packages check for updates: [Custom schedule (“fri5,23:00-01:00”)
:^]

(It’s unfortunate that we need separate settings GUI for snap and deb
updates at all — mainly because snap updates are fully automatic, while
prompting for deb updates that often would be unpleasant. Perhaps we can
combine *some* of the settings in future. But since snaps and debs have
independent configuration under the hood, we’d still need to deal with
cases where their equivalent settings are currently set to different
values.)

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

Title:
  Add options to set the snappy refresh schedule

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Snappy has a feature where the user can state when in a month to
  refresh (update) their snaps. Please provide options in Software &
  Updates to control this.

  https://docs.snapcraft.io/system-options

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun May 13 15:10:07 2018
  InstallationDate: Installed on 2017-08-03 (282 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1770961/+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 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Launchpad Bug Tracker]

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

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

  [ Dan Streetman ]
  * d/t/systemd-fsckd, d/t/cmdline-upstart-boot:
- skip on s390x; requires grub (LP: #1830477)
  * d/p/ask-password-prevent-buffer-overrow-when-reading-fro.patch:
- prevent buffer overflow when reading keyring (LP: #1814373)

  [ Dimitri John Ledkov ]
  * Specify Ubuntu's Vcs-Git

  [ Balint Reczey ]
  * Append /snap/bin to default PATH.
Snapd ships snapd-env-generator, but systemd does not not support
environment generators. Hard-coding /snap/bin is less risky than
backporting environment generator support and since snaps are considered
to be first class packages on Ubuntu /snap/bin can safely added to
the default PATH. (LP: #1771858)

  [ Ioanna Alifieraki ]
  * d/p/systemctl-Replace-check_one_unit-by-get_state_one_un.patch
- Backport upstream PR#2768 needed for next patch
  * d/p/systemctl-load-unit-if-needed-in-systemctl-is-active.patch
- Backport upstream PR#7997 to fix alias service reports inactive while
  aliased is active (LP: #1828892)

 -- Dan Streetman   Wed, 24 Apr 2019 17:15:36
-0400

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

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed
Status in systemd package in Debian:
  Fix Committed

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10.24

---
systemd (237-3ubuntu10.24) bionic; urgency=medium

  [Dimitri John Ledkov ]
  * core: export environment when running generators.
Ensure that manager's environment (including e.g. PATH) is exported when
running generators. Otherwise, one is at a mercy of running without PATH 
which
can lead to buggy generator behaviour. (LP: #1771858)

 -- Balint Reczey   Mon, 24 Jun 2019 14:50:38 +0200

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

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Fix Released
Status in snapd source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Fix Released
Status in snapd source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

   * When a generator started to be provided by systemd, it was
  recognized that $PATH is not correctly set, nonetheless, due to an
  environment bug that systemd generators run in.

  [Testcase]

  # make snapd-env-generator executable if it is not
  $ sudo chmod +x 
/usr/lib/systemd/system-environment-generators/snapd-env-generator

  # reboot, then test the effect of the fix
  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

  Output should contain a complete and a valid PATH, i.e.
  PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" 
or similar.

  [Regression Potential]

   * snapd generator was already fixed separately to cause no harm, when
  running under a broken systemd. With the corrected environment,
  generators will now run with a correct PATH out of the box. A slight
  change of PATH will be observed by all generators, when running in
  containers/initramfs-less boots. However most generators will not be
  affected as they typically do not execute external binaries.

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

[Łukasz Zemczak]

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

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Fix Released
Status in snapd source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Fix Released
Status in snapd source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

   * When a generator started to be provided by systemd, it was
  recognized that $PATH is not correctly set, nonetheless, due to an
  environment bug that systemd generators run in.

  [Testcase]

  # make snapd-env-generator executable if it is not
  $ sudo chmod +x 
/usr/lib/systemd/system-environment-generators/snapd-env-generator

  # reboot, then test the effect of the fix
  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

  Output should contain a complete and a valid PATH, i.e.
  PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" 
or similar.

  [Regression Potential]

   * snapd generator was already fixed separately to cause no harm, when
  running under a broken systemd. With the corrected environment,
  generators will now run with a correct PATH out of the box. A slight
  change of PATH will be observed by all generators, when running in
  containers/initramfs-less boots. However most generators will not be
  affected as they typically do not execute external binaries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Launchpad Bug Tracker]

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

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

  [ Dan Streetman ]
  * d/t/systemd-fsckd, d/t/cmdline-upstart-boot:
- skip on s390x; requires grub (LP: #1830477)
  * d/p/ask-password-prevent-buffer-overrow-when-reading-fro.patch:
- prevent buffer overflow when reading keyring (LP: #1814373)

  [ Dimitri John Ledkov ]
  * Specify Ubuntu's Vcs-Git

  [ Balint Reczey ]
  * Append /snap/bin to default PATH.
Snapd ships snapd-env-generator, but systemd does not not support
environment generators. Hard-coding /snap/bin is less risky than
backporting environment generator support and since snaps are considered
to be first class packages on Ubuntu /snap/bin can safely added to
the default PATH. (LP: #1771858)

  [ Ioanna Alifieraki ]
  * d/p/systemctl-Replace-check_one_unit-by-get_state_one_un.patch
- Backport upstream PR#2768 needed for next patch
  * d/p/systemctl-load-unit-if-needed-in-systemctl-is-active.patch
- Backport upstream PR#7997 to fix alias service reports inactive while
  aliased is active (LP: #1828892)

 -- Dan Streetman   Wed, 24 Apr 2019 17:15:36
-0400

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

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Fix Released
Status in snapd source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Fix Released
Status in snapd source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

   * When a generator started to be provided by systemd, it was
  recognized that $PATH is not correctly set, nonetheless, due to an
  environment bug that systemd generators run in.

  [Testcase]

  # make snapd-env-generator executable if it is not
  $ sudo chmod +x 
/usr/lib/systemd/system-environment-generators/snapd-env-generator

  # reboot, then test the effect of the fix
  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

  Output should contain a complete and a valid PATH, i.e.
  PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" 
or similar.

  [Regression Potential]

   * snapd generator was already fixed separately to cause no harm, when
  running under a broken systemd. With the corrected environment,
  generators will now run with a correct PATH out of the box. A slight
  change of PATH will be observed by all generators, when running in
  containers/initramfs-less boots. However most generators will not be
  affected as they typically do not execute external binaries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1828892] Update Released

[Łukasz Zemczak]

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

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

Title:
  systemctl - alias service reports inactive while aliased is active

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

Bug description:
  [Impact]

  'systemctl is-active' command reports an alias service as inactive even 
though the aliased service
  is active.
  Currently the 'systemctl is-active' command does not load units to minimise 
its effect on the system (i.e. that a monitoring command does not itself alter 
the state of the system).
  However, this behaviour leads to inconsistencies when services are aliased.

  [Test case]

  - Test case 1 - libvirtd

  alias service : libvirtd
  aliased service : libvirt-bin

  /etc/systemd/system$ ls -la libvirtd.service 
  lrwxrwxrwx 1 root root 39 May 13 20:49 libvirtd.service -> 
/lib/systemd/system/libvirt-bin.service

  $ systemctl is-active libvirtd
  inactive

  $ systemctl is-active libvirt-bin
  active

  
  - Test case 2 - sshd

  alias service : sshd
  aliased service : ssh

  /ect/systemd/system$ ls -la sshd.service 
  lrwxrwxrwx 1 root root 31 Mar 19 19:44 sshd.service -> 
/lib/systemd/system/ssh.service

  $ systemctl is-active sshd
  inactive

  $ systemctl is-active ssh
  active

  
  [Regression Potential]

  This fix may result into systemctl reporting inconsistent information
  concerning the status of a service.

  [Other]

  Upstream issue : https://github.com/systemd/systemd/issues/7875
  Upstream fix : https://github.com/systemd/systemd/pull/7997

  Xenial is affected, fix exists on Bionic onward.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  $ apt-cache policy systemd
  systemd:
Installed: 229-4ubuntu21.21
Candidate: 229-4ubuntu21.21

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

[Łukasz Zemczak]

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

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

Title:
  systemd-fsckd, cmdline-upstart-boot tests fail on xenial s390x

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

Bug description:
  [impact]

  these tests require, and modify, grub.  That fails on s390x on xenial
  because it does not use grub.

  [test case]

  run the autopkgtests for xenial on s390x

  [regression potential]

  low; only skipping test cases on s390x.

  [other info]

  in bionic and later, systemd-fsckd has support for zipl (s390x
  bootloader) and cmdline-upstart-boot is removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830477/+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 1828892] Re: systemctl - alias service reports inactive while aliased is active

[Launchpad Bug Tracker]

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

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

  [ Dan Streetman ]
  * d/t/systemd-fsckd, d/t/cmdline-upstart-boot:
- skip on s390x; requires grub (LP: #1830477)
  * d/p/ask-password-prevent-buffer-overrow-when-reading-fro.patch:
- prevent buffer overflow when reading keyring (LP: #1814373)

  [ Dimitri John Ledkov ]
  * Specify Ubuntu's Vcs-Git

  [ Balint Reczey ]
  * Append /snap/bin to default PATH.
Snapd ships snapd-env-generator, but systemd does not not support
environment generators. Hard-coding /snap/bin is less risky than
backporting environment generator support and since snaps are considered
to be first class packages on Ubuntu /snap/bin can safely added to
the default PATH. (LP: #1771858)

  [ Ioanna Alifieraki ]
  * d/p/systemctl-Replace-check_one_unit-by-get_state_one_un.patch
- Backport upstream PR#2768 needed for next patch
  * d/p/systemctl-load-unit-if-needed-in-systemctl-is-active.patch
- Backport upstream PR#7997 to fix alias service reports inactive while
  aliased is active (LP: #1828892)

 -- Dan Streetman   Wed, 24 Apr 2019 17:15:36
-0400

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

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

Title:
  systemctl - alias service reports inactive while aliased is active

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

Bug description:
  [Impact]

  'systemctl is-active' command reports an alias service as inactive even 
though the aliased service
  is active.
  Currently the 'systemctl is-active' command does not load units to minimise 
its effect on the system (i.e. that a monitoring command does not itself alter 
the state of the system).
  However, this behaviour leads to inconsistencies when services are aliased.

  [Test case]

  - Test case 1 - libvirtd

  alias service : libvirtd
  aliased service : libvirt-bin

  /etc/systemd/system$ ls -la libvirtd.service 
  lrwxrwxrwx 1 root root 39 May 13 20:49 libvirtd.service -> 
/lib/systemd/system/libvirt-bin.service

  $ systemctl is-active libvirtd
  inactive

  $ systemctl is-active libvirt-bin
  active

  
  - Test case 2 - sshd

  alias service : sshd
  aliased service : ssh

  /ect/systemd/system$ ls -la sshd.service 
  lrwxrwxrwx 1 root root 31 Mar 19 19:44 sshd.service -> 
/lib/systemd/system/ssh.service

  $ systemctl is-active sshd
  inactive

  $ systemctl is-active ssh
  active

  
  [Regression Potential]

  This fix may result into systemctl reporting inconsistent information
  concerning the status of a service.

  [Other]

  Upstream issue : https://github.com/systemd/systemd/issues/7875
  Upstream fix : https://github.com/systemd/systemd/pull/7997

  Xenial is affected, fix exists on Bionic onward.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  $ apt-cache policy systemd
  systemd:
Installed: 229-4ubuntu21.21
Candidate: 229-4ubuntu21.21

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828892/+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 1830477] Re: systemd-fsckd, cmdline-upstart-boot tests fail on xenial s390x

[Launchpad Bug Tracker]

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

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

  [ Dan Streetman ]
  * d/t/systemd-fsckd, d/t/cmdline-upstart-boot:
- skip on s390x; requires grub (LP: #1830477)
  * d/p/ask-password-prevent-buffer-overrow-when-reading-fro.patch:
- prevent buffer overflow when reading keyring (LP: #1814373)

  [ Dimitri John Ledkov ]
  * Specify Ubuntu's Vcs-Git

  [ Balint Reczey ]
  * Append /snap/bin to default PATH.
Snapd ships snapd-env-generator, but systemd does not not support
environment generators. Hard-coding /snap/bin is less risky than
backporting environment generator support and since snaps are considered
to be first class packages on Ubuntu /snap/bin can safely added to
the default PATH. (LP: #1771858)

  [ Ioanna Alifieraki ]
  * d/p/systemctl-Replace-check_one_unit-by-get_state_one_un.patch
- Backport upstream PR#2768 needed for next patch
  * d/p/systemctl-load-unit-if-needed-in-systemctl-is-active.patch
- Backport upstream PR#7997 to fix alias service reports inactive while
  aliased is active (LP: #1828892)

 -- Dan Streetman   Wed, 24 Apr 2019 17:15:36
-0400

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

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

Title:
  systemd-fsckd, cmdline-upstart-boot tests fail on xenial s390x

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

Bug description:
  [impact]

  these tests require, and modify, grub.  That fails on s390x on xenial
  because it does not use grub.

  [test case]

  run the autopkgtests for xenial on s390x

  [regression potential]

  low; only skipping test cases on s390x.

  [other info]

  in bionic and later, systemd-fsckd has support for zipl (s390x
  bootloader) and cmdline-upstart-boot is removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830477/+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 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1

[Petter A. Urkedal]

apache2.2.4.29-1ubuntu4.7 also fixed the issue for us. Thanks!

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

Title:
  18.04/Apache2: rejecting client initiated renegotiation due to openssl
  1.1.1

Status in apache2 package in Ubuntu:
  Fix Released
Status in openssl package in Ubuntu:
  Invalid
Status in apache2 source package in Bionic:
  Fix Committed
Status in apache2 source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Under the following conditions, https connections using client cert 
authentication will suffer a long delay (about 15s if modreqtimeout is enabled, 
more if it is disabled):
  * TLSv1.2
  * client certificate authentication in use
  * a Location, Directory, or other such block defining the client certificate 
authentication for that block only, differing from the SSL vhost as a whole

  This was triggered by the OpenSSL 1.1.1 SRU and was caused by this
  openssl change in SSL_MODE_AUTO_RETRY from disabled to enabled by
  default:
  
https://github.com/openssl/openssl/blob/a4a90a8a3bdcb9336b5c9c15da419e99a87bc6ed/CHANGES#L121-L130

  [Test Case]

  It helps if you have lxd up and running. Otherwise, a VM or even bare
  metal host also works, as long as you stick to the "ubuntu" hostname.

  Launch a container for the release you are testing. The command below is for 
bionic:
  $ lxc launch ubuntu-daily:bionic ubuntu

  Enter the container as root:
  $ lxc exec ubuntu bash

  Verify hostname is "ubuntu":
  # hostname
  ubuntu

  Install apache2:
  apt update && apt install apache2

  Download the following files from this bug report and place them in 
/etc/apache2:
  cd /etc/apache2
  wget 
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274492/+files/cacert.pem
 
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274493/+files/ubuntu.pem
 
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274494/+files/ubuntu.key

  Adjust permissions of the key file:
  chmod 0640 /etc/apache2/ubuntu.key
  chgrp www-data /etc/apache2/ubuntu.key

  Download the client certificate and key files and place them in /root:
  cd /root
  wget 
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274495/+files/client-auth.pem
 
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274496/+files/client-auth.key

  Create this vhost file (caution, lines may wrap, in particular LogFormat: it 
should be one long line):
  cat > /etc/apache2/sites-available/cert-auth-test.conf <
  
  LogLevel info ssl:warn
  ServerAdmin webmaster@localhost
  DocumentRoot /var/www/html
  LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" 
\"%{User-Agent}i\" protocol=%{SSL_PROTOCOL}x commonName=%{SSL_CLIENT_S_DN_CN}x" 
combined-ssl
  ErrorLog \${APACHE_LOG_DIR}/error.log
  CustomLog \${APACHE_LOG_DIR}/access.log combined-ssl
  SSLEngine on
  SSLCertificateFile  /etc/apache2/ubuntu.pem
  SSLCertificateKeyFile /etc/apache2/ubuntu.key
  SSLCACertificateFile /etc/apache2/cacert.pem
  
  SSLOptions +StdEnvVars
  
  
  SSLOptions +StdEnvVars
  
  
  SSLVerifyClient require
  Require ssl-verify-client
  
  
  
  EOF

  Enable the ssl module and this new vhost we just created:
  a2enmod ssl && a2ensite cert-auth-test.conf

  Restart apache2:
  systemctl restart apache2

  If at this stage you try the following command, it will fail like this 
because no client certificate was provided:
  # curl --output /dev/null https://ubuntu/ --cacert /etc/apache2/cacert.pem
    % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
   Dload  Upload   Total   SpentLeft  Speed
    0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  curl: (56) OpenSSL SSL_read: error:14094410:SSL 
routines:ssl3_read_bytes:sslv3 alert handshake failure, errno 0

  And the apache error log will confirm the reason:
  [Mon Jul 01 14:10:23.312645 2019] [ssl:error] [pid 1685:tid 140326396421888] 
SSL Library Error: error:1417C0C7:SSL 
routines:tls_process_client_certificate:peer did not return a certificate -- No 
CAs known to server for verification?

  Now retry, but providing the client certificate and key files, and forcing 
TLSv1.2 just to be sure. Due to the bug, the command will stall for about 15 
seconds, but the index.html file will be downloaded:
  # rm -f index.html
  # curl --output index.html https://ubuntu/ --cacert /etc/apache2/cacert.pem 
--cert client-auth.pem --key client-auth.key --tlsv1.2
    % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
   

[Touch-packages] [Bug 1835376] Re: package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers looping, abandoned

[Sebastian Ramacher]

>From the log:

chain of packages whose triggers are or may be responsible:
  libgtk2.0-0:amd64 -> libc-bin

reassigning accordingly.

** Package changed: vlc (Ubuntu) => gtk+2.0 (Ubuntu)

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

Title:
  package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers
  looping, abandoned

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  failed when i tried to do a partial upgrade because last upgrade
  already failed.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: libvlc-bin:amd64 3.0.6-1
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Thu Jul  4 10:16:45 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-04-06 (88 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: N/A
  SourcePackage: vlc
  Title: package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1835376/+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 1835376] [NEW] package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers looping, abandoned

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

failed when i tried to do a partial upgrade because last upgrade already
failed.

ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: libvlc-bin:amd64 3.0.6-1
ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
Uname: Linux 4.18.0-18-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
Date: Thu Jul  4 10:16:45 2019
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2019-04-06 (88 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
PythonDetails: N/A
SourcePackage: vlc
Title: package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package disco
-- 
package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers looping, 
abandoned
https://bugs.launchpad.net/bugs/1835376
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+2.0 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 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)

[Dan Streetman]

I rebuilt systemd using the 4.15.0-55 kernel headers:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1821625.2

and the test now passes:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-ddstreet-lp1821625.2/bionic/ppc64el/s/systemd/20190704_021031_ebc9b@/log.gz

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

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

Title:
  systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
  seccomp)

Status in libseccomp package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in libseccomp source package in Bionic:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Invalid

Bug description:
  Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
  failing on Bionic on ppc64el with the error messages:

  Operating on architecture: ppc
  Failed to add n/a() rule for architecture ppc, skipping: Bad address
  Operating on architecture: ppc64
  Failed to add n/a() rule for architecture ppc64, skipping: Bad address
  Operating on architecture: ppc64-le
  Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical 
argument out of domain
  Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413, 
function test_memory_deny_write_execute_mmap(). Aborting.
  memoryseccomp-mmap terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG) 
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function 
test_memory_deny_write_execute_mmap(). Aborting.
  Aborted (core dumped)
  FAIL: test-seccomp (code: 134)

  Full logs at:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz

  The testcase passed with systemd version 237-3ubuntu10.13 running on the same 
4.15.0-45 kernel on ppc64el:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+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 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)

[Dan Streetman]

systemd will require a rebuild to pick up this fix in the kernel
headers, but that happens often enough I don't think a no-change rebuild
is needed.

Also, these packages reverse-dep on the libseccomp-dev package (that
provides the faulty __NR_pkey_mprotect define) so they might need
rebuilding as well, if they use that define for anything:

$ reverse-depends -r bionic -b libseccomp-dev
Reverse-Build-Depends
=
* apt
* chrony
* docker.io
* flatpak
* gnome-desktop3
* golang-github-seccomp-libseccomp-golang
* kscreenlocker
* lxc
* man-db
* ocserv
* qemu
* snapd
* stenographer
* systemd
* tor
* tracker-miners
* usbguard

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

Title:
  systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
  seccomp)

Status in libseccomp package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in libseccomp source package in Bionic:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Invalid

Bug description:
  Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
  failing on Bionic on ppc64el with the error messages:

  Operating on architecture: ppc
  Failed to add n/a() rule for architecture ppc, skipping: Bad address
  Operating on architecture: ppc64
  Failed to add n/a() rule for architecture ppc64, skipping: Bad address
  Operating on architecture: ppc64-le
  Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical 
argument out of domain
  Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413, 
function test_memory_deny_write_execute_mmap(). Aborting.
  memoryseccomp-mmap terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG) 
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function 
test_memory_deny_write_execute_mmap(). Aborting.
  Aborted (core dumped)
  FAIL: test-seccomp (code: 134)

  Full logs at:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz

  The testcase passed with systemd version 237-3ubuntu10.13 running on the same 
4.15.0-45 kernel on ppc64el:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+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 1832651] Re: jackdbus fails to start: cannot allocate memory

[Hauke Wintjen]

I am also affected by this bug as it seems. I am also unable to start
jackd2:

Thu Jul  4 08:17:50 2019: JACK server starting in realtime mode with priority 99
Thu Jul  4 08:17:50 2019: self-connect-mode is "Don't restrict self connect 
requests"
Thu Jul  4 08:17:50 2019: ERROR: Cannot lock down 82280346 byte memory area 
(Cannot allocate memory)

My systemd is:
hcw@nvidion:~$ dpkg -l systemd
+++-==-==--=
ii  systemd240-6ubuntu5.1 amd64system and service manager

So is there a workaround / upgrade path? I dont want do wait 4 months
before i can start podcasting. 8-<

Kind regards

Hauke

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

Title:
  jackdbus fails to start: cannot allocate memory

Status in systemd:
  Fix Released
Status in jackd2 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in jackd2 source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  The `.log/jack/jackdbus.log` shows the following after trying to
  start/restart jack using "Ubuntu Studio Controls" (also tried using
  `jack_control start`):

  ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate
  memory)

  This is a fresh install of Ubuntu Studio 19.04, installed via USB. The
  first thing I did after installing was check to see if jack was
  running, but unfortunately it's not working. The error would seem to
  indicate that I'm not in the `audio` group, however checking `groups`
  shows that I am in the audio group.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: jackd2 1.9.12~dfsg-2build1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6
  Uname: Linux 5.0.0-13-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun 12 18:13:25 2019
  InstallationDate: Installed on 2019-06-12 (0 days ago)
  InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 
(20190416)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: jackd2
  UpgradeStatus: No upgrade log present (probably fresh install)

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