[Touch-packages] [Bug 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers

[Simon Déziel]

I'm hitting the same problem when using a Bionic host with a Bionic
container when using the 5.0 HWE kernel.

@paelzer, I'd appreciate if this could be SRU'ed to Bionic, please :)

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

Title:
  [apparmor] missing 'mr' on binary for usage on containers

Status in rsyslog package in Ubuntu:
  Fix Released

Bug description:
  Issue description:

  Enabling the rsyslog (disabled by default) Apparmor profile causes
  rsyslog to fail to start when running *inside a container*.

  Steps to reproduce:

  1) Create a 'eoan' container called rs1 here:
lxc launch ubuntu-daily:e rs1
  2) Enter the container
lxc shell rs1
  3) Enable apparmor profile
rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
systemctl restart rsyslog
  4) notice rsyslog failed to start
systemctl status rsyslog

  Workaround:

echo '  /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd
apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
systemctl restart rsyslog

  
  Additional information:

  root@rs1:~# uname -a
  Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
  root@rs1:~# lsb_release -rd
  Description:  Ubuntu Eoan EANIMAL (development branch)
  Release:  19.10
  root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog'
  ii  apparmor 2.13.2-9ubuntu6  amd64user-space parser utility for 
AppArmor
  ii  rsyslog  8.32.0-1ubuntu7  amd64reliable system and kernel logging 
daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: rsyslog 8.32.0-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed May  1 17:36:29 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1846844] [NEW] Procps: top -b does not display the correct CPU percentages

[Simon Tideswell]

Public bug reported:

Affects: 2:3.3.12-3ubuntu1.2 (bionic) & 2:3.3.10-4ubuntu2.4 (xenial)

If I run 'top -b -n 1' the CPU percentages are the same every single
time. If I run with more iterations the CPU percentages of subsequent
iterations update in real time. If I run top interactively then the CPU
percentages correctly update in real time. Here's an example.

1) With n=1 the same CPU percentages are always displayed.

while true ; do top -b -n 1 | grep -E "^%Cpu" ; sleep 10; done
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st

2) With n=2 the second iteration shows a changing CPU percentage, but
the first is still clearly wrong.

while true ; do top -b -n 2 | grep -E "^%Cpu" ; sleep 10; done
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 27.3 us,  1.7 sy,  0.0 ni, 70.5 id,  0.0 wa,  0.0 hi,  0.4 si,  0.0 st
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 50.9 us,  5.4 sy,  0.0 ni, 42.2 id,  0.1 wa,  0.0 hi,  1.4 si,  0.0 st
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 63.3 us,  5.2 sy,  0.0 ni, 29.2 id,  0.1 wa,  0.0 hi,  2.2 si,  0.0 st
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 43.3 us,  2.9 sy,  0.0 ni, 52.4 id,  0.1 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 38.0 us,  3.7 sy,  0.0 ni, 56.8 id,  0.2 wa,  0.0 hi,  1.4 si,  0.0 st
%Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 st
%Cpu(s): 47.9 us,  3.5 sy,  0.0 ni, 47.2 id,  0.1 wa,  0.0 hi,  1.2 si,  0.0 st

This affects both Xenial and Bionic.

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


** Tags: batch procps top

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

Title:
  Procps: top -b does not display the correct CPU percentages

Status in procps package in Ubuntu:
  New

Bug description:
  Affects: 2:3.3.12-3ubuntu1.2 (bionic) & 2:3.3.10-4ubuntu2.4 (xenial)

  If I run 'top -b -n 1' the CPU percentages are the same every single
  time. If I run with more iterations the CPU percentages of subsequent
  iterations update in real time. If I run top interactively then the
  CPU percentages correctly update in real time. Here's an example.

  1) With n=1 the same CPU percentages are always displayed.

  while true ; do top -b -n 1 | grep -E "^%Cpu" ; sleep 10; done
  %Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 
st
  %Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 
st
  %Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 
st
  %Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 
st
  %Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 
st
  %Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 
st
  %Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 
st
  %Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 
st
  %Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 
st

  2) With n=2 the second iteration shows a changing CPU percentage, but
  the first is still clearly wrong.

  while true ; do top -b -n 2 | grep -E "^%Cpu" ; sleep 10; done
  %Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 
st
  %Cpu(s): 27.3 us,  1.7 sy,  0.0 ni, 70.5 id,  0.0 wa,  0.0 hi,  0.4 si,  0.0 
st
  %Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 
st
  %Cpu(s): 50.9 us,  5.4 sy,  0.0 ni, 42.2 id,  0.1 wa,  0.0 hi,  1.4 si,  0.0 
st
  %Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 
st
  %Cpu(s): 63.3 us,  5.2 sy,  0.0 ni, 29.2 id,  0.1 wa,  0.0 hi,  2.2 si,  0.0 
st
  %Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 
st
  %Cpu(s): 43.3 us,  2.9 sy,  0.0 ni, 52.4 id,  0.1 wa,  0.0 hi,  1.2 si,  0.0 
st
  %Cpu(s): 46.1 us,  4.1 sy,  0.2 ni, 48.1 id,  0.2 wa,  0.0 hi,  1.2 si,  0.0 
st
  %Cpu(s): 38.0 us,  3.7 sy,  0.0 ni, 56.8 id,  0.2 wa,  

[Touch-packages] [Bug 1286836] Re: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostp

[pablo]

** Changed in: libav (Ubuntu)
 Assignee: (unassigned) => pablo (pablostar)

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

Title:
  package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to
  install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch:
  no) is not co-installable with libpostproc52 which has multiple
  installed instances

Status in libav package in Ubuntu:
  Triaged
Status in libpostproc package in Ubuntu:
  Triaged

Bug description:
   -

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpostproc52 6:0.8.10-0ubuntu0.13.10.1
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Mon Mar  3 00:57:47 2014
  Dependencies:
   gcc-4.9-base 4.9-20140222-0ubuntu1
   libavutil51 6:0.8.10-0ubuntu0.13.10.1 [origin: unknown]
   libc6 2.19-0ubuntu2
   libgcc1 1:4.9-20140222-0ubuntu1
   multiarch-support 2.19-0ubuntu2
  ErrorMessage: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not 
co-installable with libpostproc52 which has multiple installed instances
  InstallationDate: Installed on 2013-12-12 (79 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: libav
  Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to 
install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not 
co-installable with libpostproc52 which has multiple installed instances
  UpgradeStatus: Upgraded to trusty on 2014-03-02 (0 days ago)

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

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

[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-budgie-meta - 0.53

---
ubuntu-budgie-meta (0.53) eoan; urgency=medium

  * Refreshed dependencies
  * Added zfsutils-linux to desktop-recommends (LP: #1843768)

 -- David Mohammed   Fri, 04 Oct 2019 20:45:05
+0100

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

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

Title:
  [FFe] Ubiquity with zfs install option

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Part of the 19.10 feature announcement is zfs experimental support in
  the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
  ubuntu-19-10-an-introduction). We modified ubiquity to present an
  “EXPERIMENTAL” (with warning) ZSYS install option. This option is only
  visible is zfsutils-linux is installed on the system. So, it won't be
  available for derivatives that use ubiquity but do not seed zfsutils-
  linux.

  Update as of 20/09/2019: the plan is to not seed zsys (security review
  will take a while), but to only seed zfsutils-linux. People can then
  opt-in to zsys which should be available by default next cycle.

  This option takes an entire disk and have a fix set of dataset
  installed. There is no support but we need this to make an official
  install option for the next LTS.

  The patch has been created to be as minimal as possible. Partman does
  a full disk partitioning, and then the script zsys-setup the first
  non-ESP partition and replaces with zfs pools.

  4 partitions are created:
  1. if GPT partitioning: ESP partition. This one is done by partman directly.
  2. bpool (for boot), pool with older zfs compatible version to be readable by 
grub)
  3. rpool (for / and userdataset)
  4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on 
moved to the ESP)

  Additionaly if a swap file has been created by ubiquity, it is
  recreated as a ZFS volume. If the script fails to execute, the final
  installation is an ext4 installation on entire disk.

  Note that the implementation is slightly different from the
  specification due to a difficult cohabitation with partman in the
  custom partitioning page.

  Please find attached the MP on ubiquity as well as the package build
  log.

  https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
  amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz

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

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

[Touch-packages] [Bug 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

[Eric Desrochers]

** Tags added: sts-sponsor-ddstreet

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

Title:
  systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  In Progress

Bug description:
  I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't 
exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the 
following steps:
  1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size.
  2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit.
  3. Ask upstream for SOA of test.asdf. with EDNS0.
  4. Ask upstream for SOA of test.asdf. without EDNS0.
  5. Repeat 1-4 for DS of test.asdf.
  6. Repeat 1-5 for asdf.
  7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size.
  8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size.

  The upstream returns an unfragmented NXDOMAIN response for steps 1-6,
  an unfragmented NOERROR response for step 7 and a fragmented NOERROR
  response for step 8 which is the correct behaviour. DNSSEC records are
  included in the response if the DO-bit in the request was set.

  systemd-resolved should take the response from step 1 and start with
  validation instead of starting useless retries with reduced feture
  set. Step 3 and 4 are completely useless and probably lead to the
  SERVFAIL because I have configured it with DNSSEC=yes to prevent
  downgrade attacks.

  This regression seems to be caused by the patch resolved-Mitigate-
  DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic
  should only be executed if it is configured as DNSSEC=allow-downgrade
  or DNSSEC=no. See also
  https://github.com/systemd/systemd/pull/8608#issuecomment-396927885.

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

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

[Touch-packages] [Bug 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)

[Brian Murray]

** Tags added: rls-ee-incoming

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0)

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5

  ---

  Session suddenly stopped and came back to login screen, all opened
  windows lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

[Balint Reczey]

I'm adding this patch to the next upload I'm preparing in
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3797/+packages .

** Changed in: systemd (Ubuntu)
 Assignee: Dimitri John Ledkov (xnox) => Balint Reczey (rbalint)

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

Title:
  systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  In Progress

Bug description:
  I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't 
exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the 
following steps:
  1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size.
  2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit.
  3. Ask upstream for SOA of test.asdf. with EDNS0.
  4. Ask upstream for SOA of test.asdf. without EDNS0.
  5. Repeat 1-4 for DS of test.asdf.
  6. Repeat 1-5 for asdf.
  7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size.
  8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size.

  The upstream returns an unfragmented NXDOMAIN response for steps 1-6,
  an unfragmented NOERROR response for step 7 and a fragmented NOERROR
  response for step 8 which is the correct behaviour. DNSSEC records are
  included in the response if the DO-bit in the request was set.

  systemd-resolved should take the response from step 1 and start with
  validation instead of starting useless retries with reduced feture
  set. Step 3 and 4 are completely useless and probably lead to the
  SERVFAIL because I have configured it with DNSSEC=yes to prevent
  downgrade attacks.

  This regression seems to be caused by the patch resolved-Mitigate-
  DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic
  should only be executed if it is configured as DNSSEC=allow-downgrade
  or DNSSEC=no. See also
  https://github.com/systemd/systemd/pull/8608#issuecomment-396927885.

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

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

[Touch-packages] [Bug 1846821] [NEW] Qt print dialog has wrong default page size

[Maciej Puzio]

Public bug reported:

Please backport Qt patch 213677 to qtbase-opensource-src
https://codereview.qt-project.org/c/qt/qtbase/+/213677

In Qt5 applications, print dialog (Printer Properties) always defaults
to A4 paper size, even when Letter is set as a default in all system and
KDE preferences. After changing manually, Letter-size pages print
correctly, but the setting does not stick. The issue also affects other
print settings, e.g. margins, though the aforementioned patch does not
deal with these. A similar issue regarding the duplex setting was
reported as Launchpad bug 1776173, and subsequently fixed, but other
print settings continue to cause problems.

Behavior expected: Print dialog would default to Letter paper size,
which is set in all available system and KDE preferences, and that was
selected for previous prints.

Behavior observed: Print dialog always defaults to A4, and page size
needs to be changed manually before every print.

Software versions:
lsb_release: Ubuntu 18.04.3 LTS
libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
Kernel: 5.0.0-25-generic

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


** Tags: bionic

** Summary changed:

- Qt print dialog does not remember page size
+ Qt print dialog has wrong default page size

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

Title:
  Qt print dialog has wrong default page size

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

Bug description:
  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677

  In Qt5 applications, print dialog (Printer Properties) always defaults
  to A4 paper size, even when Letter is set as a default in all system
  and KDE preferences. After changing manually, Letter-size pages print
  correctly, but the setting does not stick. The issue also affects
  other print settings, e.g. margins, though the aforementioned patch
  does not deal with these. A similar issue regarding the duplex setting
  was reported as Launchpad bug 1776173, and subsequently fixed, but
  other print settings continue to cause problems.

  Behavior expected: Print dialog would default to Letter paper size,
  which is set in all available system and KDE preferences, and that was
  selected for previous prints.

  Behavior observed: Print dialog always defaults to A4, and page size
  needs to be changed manually before every print.

  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

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

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

[Touch-packages] [Bug 1818243] Re: systemd-logind takes 25s to stop when rebooting

[Torsten Schönfeld]

Can you explain why this issue was closed with "won't fix"?  I still see
it in Disco.

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

Title:
  systemd-logind takes 25s to stop when rebooting

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  During reboot:

  Mar 01 14:15:52 P8lpar5 systemd[1]: Stopping Login Service...
  [...]
  Mar 01 14:16:17 P8lpar5 systemd-logind[2756]: Failed to abandon session 
scope, ignoring: Connection timed out
  Mar 01 14:16:17 P8lpar5 systemd-logind[2756]: Session 5 logged out. Waiting 
for processes to exit.
  Mar 01 14:16:17 P8lpar5 dbus-daemon[2855]: [system] Failed to activate 
service 'org.freedesktop.systemd1': timed out (service_start_timeout=
  25000ms)
  Mar 01 14:16:17 P8lpar5 systemd[1]: Stopped Login Service.

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

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

[Touch-packages] [Bug 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

[Victor Tapia]

** Patch removed: "eoan.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+attachment/5294401/+files/eoan.debdiff

** Patch added: "eoan.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+attachment/5294438/+files/eoan.debdiff

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

Title:
  systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  In Progress

Bug description:
  I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't 
exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the 
following steps:
  1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size.
  2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit.
  3. Ask upstream for SOA of test.asdf. with EDNS0.
  4. Ask upstream for SOA of test.asdf. without EDNS0.
  5. Repeat 1-4 for DS of test.asdf.
  6. Repeat 1-5 for asdf.
  7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size.
  8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size.

  The upstream returns an unfragmented NXDOMAIN response for steps 1-6,
  an unfragmented NOERROR response for step 7 and a fragmented NOERROR
  response for step 8 which is the correct behaviour. DNSSEC records are
  included in the response if the DO-bit in the request was set.

  systemd-resolved should take the response from step 1 and start with
  validation instead of starting useless retries with reduced feture
  set. Step 3 and 4 are completely useless and probably lead to the
  SERVFAIL because I have configured it with DNSSEC=yes to prevent
  downgrade attacks.

  This regression seems to be caused by the patch resolved-Mitigate-
  DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic
  should only be executed if it is configured as DNSSEC=allow-downgrade
  or DNSSEC=no. See also
  https://github.com/systemd/systemd/pull/8608#issuecomment-396927885.

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

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

[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131

[Andreas Hasenack]

Xenial verification

No warnings or errors during upgrade:
Get:1 http://azure.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
base-files amd64 9.4ubuntu4.11 [67.5 kB]
Fetched 67.5 kB in 0s (1,082 kB/s)
(Reading database ... 78928 files and directories currently installed.)
Preparing to unpack .../base-files_9.4ubuntu4.11_amd64.deb ...
Unpacking base-files (9.4ubuntu4.11) over (9.4ubuntu4.8) ...
Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.5) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for install-info (6.1.0.dfsg.1-5) ...
Processing triggers for initramfs-tools (0.122ubuntu8.15) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-1060-azure
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Setting up base-files (9.4ubuntu4.11) ...


The motd-news.timer is installed and will run in 7h:
ubuntu@xenial-motd:~$ systemctl list-timers
NEXT LEFT LAST PASSED   
UNIT ACTIVATES
Sat 2019-10-05 02:13:08 UTC  7h left  n/a  n/a  
motd-news.timer  motd-news.service
Sat 2019-10-05 06:01:07 UTC  11h left n/a  n/a  
apt-daily.timer  apt-daily.service
Sat 2019-10-05 06:35:02 UTC  12h left n/a  n/a  
apt-daily-upgrade.timer  apt-daily-upgrade.service
Sat 2019-10-05 18:14:55 UTC  23h left Fri 2019-10-04 18:14:55 UTC  6min ago 
systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service

4 timers listed.
Pass --all to see loaded but inactive timers, too.


motd message is now displayed:
ubuntu@xenial-motd:~$ sudo sh /etc/update-motd.d/50-motd-news --force

 * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
   Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

 https://ubuntu.com/kubernetes/docs/release-notes


Confirmed upon logging in:
andreas@nsnx:~$ ssh ubuntu@13.90.92.78
Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 4.15.0-1057-azure x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

 * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
   Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

 https://ubuntu.com/kubernetes/docs/release-notes

26 packages can be updated.
0 updates are security updates.

New release '18.04.2 LTS' available.
Run 'do-release-upgrade' to upgrade to it.


*** System restart required ***
Last login: Fri Oct  4 18:15:19 2019 from 187.107.24.4


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

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

Title:
  9.4ubuntu4.9: Broken package because of missing "#" @
  /var/lib/dpkg/info/base-files.postinst +131

Status in base-files package in Ubuntu:
  Invalid
Status in base-files source package in Xenial:
  Fix Committed

Bug description:
  Trying to install this on xenial results in:

  
  Setting up base-files (9.4ubuntu4.9) ...
  /var/lib/dpkg/info/base-files.postinst: 131: 
/var/lib/dpkg/info/base-files.postinst: Automatically: not found
  dpkg: error processing package base-files (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   base-files
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Because there is a missing comment "#" at the beginning of line 131 of 
/var/lib/dpkg/info/base-files.postinst, ie:

  Automatically added by dh_systemd_start
  ^-- # ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions

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

[Touch-packages] [Bug 1840946] Re: Include cloud-id in user-agent string

[Andreas Hasenack]

Xenial verification: passed

Summary of tests:
No errors or warnings during package upgrade
a) motd message is now displayed
a.1) motd message displayed on login
b) cloud_id set to $cloudname in user-agent
c) motd-news.timer scheduled to run

Tested on: lxd, aws, gce, azure

Using package base-files 9.4ubuntu4.11 from xenial-proposed

Detailed test logs attached.

** Attachment added: "xenial-verification.txt"
   
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+attachment/5294436/+files/xenial-verification.txt

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

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

Title:
  Include cloud-id in user-agent string

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one
  is available.

  [Test Case]
  a) confirm that the motd message is still displayed:
  $ sudo sh /etc/update-motd.d/50-motd-news --force

   * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
     Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

   https://ubuntu.com/kubernetes/docs/release-notes

  b) confirm that cloud_id is set in the user-agent. This should be
  tested in lxd, gce, aws, and azure. Here is an example for lxd:

  $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1| grep -E "curl 
.*cloud_id/"
  + curl --connect-timeout 60 --max-time 60 -A curl/7.47.0-1ubuntu2.14 
Ubuntu/16.04.6/LTS GNU/Linux/4.15.0-64-generic/x86_64 
Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz uptime/921.00/900.00 cloud_id/lxd -o- 
https://motd.ubuntu.com

  For each of the mentioned clouds, we expect cloud_id to be set to
  their short names: aws, gce, azure.

  For xenial, there is an extra test case:
  c) list the timers to confirm motd-news is active, and will run sometime in 
the next 12h following the installation of the updated package:
  $ systemctl list-timers
  NEXT LEFT LAST PASSED
UNIT ACTIVATES
  Mon 2019-09-30 19:38:55 UTC  6h left  n/a  n/a   
motd-news.timer  motd-news.service
  Mon 2019-09-30 22:45:13 UTC  9h left  n/a  n/a   
apt-daily.timer  apt-daily.service
  Tue 2019-10-01 06:12:11 UTC  16h left n/a  n/a   
apt-daily-upgrade.timer  apt-daily-upgrade.service
  Tue 2019-10-01 13:11:41 UTC  23h left Mon 2019-09-30 13:11:41 UTC  14min ago 
systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service

  [Regression Potential]
  This change adds a new parameter to the already existing user-agent string. 
This relies on the cloud-id tool from cloud-init. Even though it's considered 
trusted to some degree, it may be possible for some clouds to override their 
name in the data fed to cloud-init, which is what cloud-id parses. Therefore 
some precautions were taken when handling its contents:
  - set value to unknown if cloud-id fails, doesn't exist, or produce an empty 
value
  - sanitize the output of cloud-id, and truncate it to a maximum length
  - use a tempfile to store the intermediate output of cloud-id instead of a 
shell variable. One reason being avoiding storing a potentially large amount of 
data in a shell variable, and the other is to avoid mistakes when manipulating 
a shell variable that could contain shell metacharacters.

  [Other Info]
  For xenial, this is also finishing the fix for bug #1637800 which was stuck 
in the SRU queue due to it failing checks. Since the xenial package isn't using 
debhelper, manual dh snippets were added to the maintainer scripts, but they 
missed the dh_systemd_enable chunks. I'm also skipping starting 
motd-news.service, since the timer unit will handle that. This avoids an 
annoying error message about trying to start a unit that is not enabled.

  [Original Description]
  I'm preemptively filing this bug in case this isn't uploaded before the 
feature freeze.

  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one
  is available.

  There is an MP for this already at
  https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git
  /base-files/+merge/371370

To manage notifications about this bug go to:

[Touch-packages] [Bug 1840946] Re: Include cloud-id in user-agent string

[Andreas Hasenack]

Bionic verification: passed

Summary of tests:
a) motd message still displayed
b) cloud_id set to $cloudname in user-agent

Tested on: lxd, aws, gce, azure

Using package base-files 10.1ubuntu2.7 from bionic-proposed

Detailed test logs attached.

** Attachment added: "bionic-verification.txt"
   
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+attachment/5294435/+files/bionic-verification.txt

** 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 base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1840946

Title:
  Include cloud-id in user-agent string

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one
  is available.

  [Test Case]
  a) confirm that the motd message is still displayed:
  $ sudo sh /etc/update-motd.d/50-motd-news --force

   * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
     Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

   https://ubuntu.com/kubernetes/docs/release-notes

  b) confirm that cloud_id is set in the user-agent. This should be
  tested in lxd, gce, aws, and azure. Here is an example for lxd:

  $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1| grep -E "curl 
.*cloud_id/"
  + curl --connect-timeout 60 --max-time 60 -A curl/7.47.0-1ubuntu2.14 
Ubuntu/16.04.6/LTS GNU/Linux/4.15.0-64-generic/x86_64 
Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz uptime/921.00/900.00 cloud_id/lxd -o- 
https://motd.ubuntu.com

  For each of the mentioned clouds, we expect cloud_id to be set to
  their short names: aws, gce, azure.

  For xenial, there is an extra test case:
  c) list the timers to confirm motd-news is active, and will run sometime in 
the next 12h following the installation of the updated package:
  $ systemctl list-timers
  NEXT LEFT LAST PASSED
UNIT ACTIVATES
  Mon 2019-09-30 19:38:55 UTC  6h left  n/a  n/a   
motd-news.timer  motd-news.service
  Mon 2019-09-30 22:45:13 UTC  9h left  n/a  n/a   
apt-daily.timer  apt-daily.service
  Tue 2019-10-01 06:12:11 UTC  16h left n/a  n/a   
apt-daily-upgrade.timer  apt-daily-upgrade.service
  Tue 2019-10-01 13:11:41 UTC  23h left Mon 2019-09-30 13:11:41 UTC  14min ago 
systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service

  [Regression Potential]
  This change adds a new parameter to the already existing user-agent string. 
This relies on the cloud-id tool from cloud-init. Even though it's considered 
trusted to some degree, it may be possible for some clouds to override their 
name in the data fed to cloud-init, which is what cloud-id parses. Therefore 
some precautions were taken when handling its contents:
  - set value to unknown if cloud-id fails, doesn't exist, or produce an empty 
value
  - sanitize the output of cloud-id, and truncate it to a maximum length
  - use a tempfile to store the intermediate output of cloud-id instead of a 
shell variable. One reason being avoiding storing a potentially large amount of 
data in a shell variable, and the other is to avoid mistakes when manipulating 
a shell variable that could contain shell metacharacters.

  [Other Info]
  For xenial, this is also finishing the fix for bug #1637800 which was stuck 
in the SRU queue due to it failing checks. Since the xenial package isn't using 
debhelper, manual dh snippets were added to the maintainer scripts, but they 
missed the dh_systemd_enable chunks. I'm also skipping starting 
motd-news.service, since the timer unit will handle that. This avoids an 
annoying error message about trying to start a unit that is not enabled.

  [Original Description]
  I'm preemptively filing this bug in case this isn't uploaded before the 
feature freeze.

  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one
  is available.

  There is an MP for this already at
  https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git
  /base-files/+merge/371370

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+subscriptions

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

[Touch-packages] [Bug 1840946] Re: Include cloud-id in user-agent string

[Andreas Hasenack]

Disco verification: passed

Summary of tests:
a) motd message still displayed
b) cloud_id set to $cloudname in user-agent

Tested on: lxd, aws, gce, azure

Using package base-files 10.1ubuntu9.2 from disco-proposed

Detailed test logs attached.

** Attachment added: "disco-verification.txt"
   
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+attachment/5294434/+files/disco-verification.txt

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

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

Title:
  Include cloud-id in user-agent string

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one
  is available.

  [Test Case]
  a) confirm that the motd message is still displayed:
  $ sudo sh /etc/update-motd.d/50-motd-news --force

   * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
     Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

   https://ubuntu.com/kubernetes/docs/release-notes

  b) confirm that cloud_id is set in the user-agent. This should be
  tested in lxd, gce, aws, and azure. Here is an example for lxd:

  $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1| grep -E "curl 
.*cloud_id/"
  + curl --connect-timeout 60 --max-time 60 -A curl/7.47.0-1ubuntu2.14 
Ubuntu/16.04.6/LTS GNU/Linux/4.15.0-64-generic/x86_64 
Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz uptime/921.00/900.00 cloud_id/lxd -o- 
https://motd.ubuntu.com

  For each of the mentioned clouds, we expect cloud_id to be set to
  their short names: aws, gce, azure.

  For xenial, there is an extra test case:
  c) list the timers to confirm motd-news is active, and will run sometime in 
the next 12h following the installation of the updated package:
  $ systemctl list-timers
  NEXT LEFT LAST PASSED
UNIT ACTIVATES
  Mon 2019-09-30 19:38:55 UTC  6h left  n/a  n/a   
motd-news.timer  motd-news.service
  Mon 2019-09-30 22:45:13 UTC  9h left  n/a  n/a   
apt-daily.timer  apt-daily.service
  Tue 2019-10-01 06:12:11 UTC  16h left n/a  n/a   
apt-daily-upgrade.timer  apt-daily-upgrade.service
  Tue 2019-10-01 13:11:41 UTC  23h left Mon 2019-09-30 13:11:41 UTC  14min ago 
systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service

  [Regression Potential]
  This change adds a new parameter to the already existing user-agent string. 
This relies on the cloud-id tool from cloud-init. Even though it's considered 
trusted to some degree, it may be possible for some clouds to override their 
name in the data fed to cloud-init, which is what cloud-id parses. Therefore 
some precautions were taken when handling its contents:
  - set value to unknown if cloud-id fails, doesn't exist, or produce an empty 
value
  - sanitize the output of cloud-id, and truncate it to a maximum length
  - use a tempfile to store the intermediate output of cloud-id instead of a 
shell variable. One reason being avoiding storing a potentially large amount of 
data in a shell variable, and the other is to avoid mistakes when manipulating 
a shell variable that could contain shell metacharacters.

  [Other Info]
  For xenial, this is also finishing the fix for bug #1637800 which was stuck 
in the SRU queue due to it failing checks. Since the xenial package isn't using 
debhelper, manual dh snippets were added to the maintainer scripts, but they 
missed the dh_systemd_enable chunks. I'm also skipping starting 
motd-news.service, since the timer unit will handle that. This avoids an 
annoying error message about trying to start a unit that is not enabled.

  [Original Description]
  I'm preemptively filing this bug in case this isn't uploaded before the 
feature freeze.

  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one
  is available.

  There is an MP for this already at
  https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git
  /base-files/+merge/371370

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+subscriptions

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

[Touch-packages] [Bug 1637800] Re: add a motd script for news

[Andreas Hasenack]

Xenial verification

No warnings or errors during upgrade:
Get:1 http://azure.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
base-files amd64 9.4ubuntu4.11 [67.5 kB]
Fetched 67.5 kB in 0s (1,082 kB/s)
(Reading database ... 78928 files and directories currently installed.)
Preparing to unpack .../base-files_9.4ubuntu4.11_amd64.deb ...
Unpacking base-files (9.4ubuntu4.11) over (9.4ubuntu4.8) ...
Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.5) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for install-info (6.1.0.dfsg.1-5) ...
Processing triggers for initramfs-tools (0.122ubuntu8.15) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-1060-azure
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Setting up base-files (9.4ubuntu4.11) ...


motd message is now displayed:
ubuntu@xenial-motd:~$ sudo sh /etc/update-motd.d/50-motd-news --force

 * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
   Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

 https://ubuntu.com/kubernetes/docs/release-notes



Confirmed upon logging in:
andreas@nsnx:~$ ssh ubuntu@13.90.92.78
Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 4.15.0-1057-azure x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

 * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
   Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

 https://ubuntu.com/kubernetes/docs/release-notes

26 packages can be updated.
0 updates are security updates.

New release '18.04.2 LTS' available.
Run 'do-release-upgrade' to upgrade to it.


*** System restart required ***
Last login: Fri Oct  4 18:15:19 2019 from 187.107.24.4


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

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

Title:
  add a motd script for news

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed

Bug description:
  Add a new update-motd script for printing news and/or important
  notices.

  == SRU ==

  [IMPACT]
  We should add important security messages or other news to the MOTD.

  [TEST CASE]
  Login to the system and ensure that the "news" section of the motd is 
displayed.  Note that you might need to force trigger an update by running 
'sudo update-motd'.

  [REGRESSION POTENTIAL]
  No reasonable regression potential.  The script simply prints 2 lines of text 
to the MOTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions

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

[Touch-packages] [Bug 1840946] Re: Include cloud-id in user-agent string

[Andreas Hasenack]

The verification log is quite extensive and verbose, since it's about 3
ubuntu releases and on 4 clouds: lxd, aws, gce, azure. I'll post a
summary and an attachment with the detailed log for each.

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

Title:
  Include cloud-id in user-agent string

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one
  is available.

  [Test Case]
  a) confirm that the motd message is still displayed:
  $ sudo sh /etc/update-motd.d/50-motd-news --force

   * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
     Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

   https://ubuntu.com/kubernetes/docs/release-notes

  b) confirm that cloud_id is set in the user-agent. This should be
  tested in lxd, gce, aws, and azure. Here is an example for lxd:

  $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1| grep -E "curl 
.*cloud_id/"
  + curl --connect-timeout 60 --max-time 60 -A curl/7.47.0-1ubuntu2.14 
Ubuntu/16.04.6/LTS GNU/Linux/4.15.0-64-generic/x86_64 
Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz uptime/921.00/900.00 cloud_id/lxd -o- 
https://motd.ubuntu.com

  For each of the mentioned clouds, we expect cloud_id to be set to
  their short names: aws, gce, azure.

  For xenial, there is an extra test case:
  c) list the timers to confirm motd-news is active, and will run sometime in 
the next 12h following the installation of the updated package:
  $ systemctl list-timers
  NEXT LEFT LAST PASSED
UNIT ACTIVATES
  Mon 2019-09-30 19:38:55 UTC  6h left  n/a  n/a   
motd-news.timer  motd-news.service
  Mon 2019-09-30 22:45:13 UTC  9h left  n/a  n/a   
apt-daily.timer  apt-daily.service
  Tue 2019-10-01 06:12:11 UTC  16h left n/a  n/a   
apt-daily-upgrade.timer  apt-daily-upgrade.service
  Tue 2019-10-01 13:11:41 UTC  23h left Mon 2019-09-30 13:11:41 UTC  14min ago 
systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service

  [Regression Potential]
  This change adds a new parameter to the already existing user-agent string. 
This relies on the cloud-id tool from cloud-init. Even though it's considered 
trusted to some degree, it may be possible for some clouds to override their 
name in the data fed to cloud-init, which is what cloud-id parses. Therefore 
some precautions were taken when handling its contents:
  - set value to unknown if cloud-id fails, doesn't exist, or produce an empty 
value
  - sanitize the output of cloud-id, and truncate it to a maximum length
  - use a tempfile to store the intermediate output of cloud-id instead of a 
shell variable. One reason being avoiding storing a potentially large amount of 
data in a shell variable, and the other is to avoid mistakes when manipulating 
a shell variable that could contain shell metacharacters.

  [Other Info]
  For xenial, this is also finishing the fix for bug #1637800 which was stuck 
in the SRU queue due to it failing checks. Since the xenial package isn't using 
debhelper, manual dh snippets were added to the maintainer scripts, but they 
missed the dh_systemd_enable chunks. I'm also skipping starting 
motd-news.service, since the timer unit will handle that. This avoids an 
annoying error message about trying to start a unit that is not enabled.

  [Original Description]
  I'm preemptively filing this bug in case this isn't uploaded before the 
feature freeze.

  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one
  is available.

  There is an MP for this already at
  https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git
  /base-files/+merge/371370

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+subscriptions

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

[Touch-packages] [Bug 1846807] [NEW] Xorg crash

[kokoye2007 ]

Public bug reported:

When upgrade (include firmware update)

can't see login screen 
when i use startx 
looping login screen

Upgrade to 19.10 and install lightdm 
still again

when i use wayland is ok.
other gnome, gnome-classic, ubuntu is looping

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct  5 00:50:39 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:225c]
InstallationDate: Installed on 2019-01-22 (254 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190122)
MachineType: LENOVO 20KH007UVA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/02/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET66W (1.41 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KH007UVA
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET66W(1.41):bd09/02/2019:svnLENOVO:pn20KH007UVA:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007UVA:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KH007UVA
dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99+git1909241510.0c4275~oibaf~d
version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1909260954.031752~oibaf~d
version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1909260954.031752~oibaf~d
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug crash eoan third-party-packages ubuntu wayland-session

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  When upgrade (include firmware update)

  can't see login screen 
  when i use startx 
  looping login screen

  Upgrade to 19.10 and install lightdm 
  still again

  when i use wayland is ok.
  other gnome, gnome-classic, ubuntu is looping

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  5 00:50:39 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225c]
  InstallationDate: Installed on 2019-01-22 (254 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190122)
  MachineType: LENOVO 20KH007UVA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET66W (1.41 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH007UVA
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET66W(1.41):bd09/02/2019:svnLENOVO:pn20KH007UVA:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007UVA:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 

[Touch-packages] [Bug 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

[Victor Tapia]

** Patch removed: "eoan debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+attachment/5288416/+files/systemd_241-7ubuntu2.debdiff

** Patch added: "eoan.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+attachment/5294401/+files/eoan.debdiff

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

Title:
  systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  In Progress

Bug description:
  I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't 
exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the 
following steps:
  1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size.
  2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit.
  3. Ask upstream for SOA of test.asdf. with EDNS0.
  4. Ask upstream for SOA of test.asdf. without EDNS0.
  5. Repeat 1-4 for DS of test.asdf.
  6. Repeat 1-5 for asdf.
  7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size.
  8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size.

  The upstream returns an unfragmented NXDOMAIN response for steps 1-6,
  an unfragmented NOERROR response for step 7 and a fragmented NOERROR
  response for step 8 which is the correct behaviour. DNSSEC records are
  included in the response if the DO-bit in the request was set.

  systemd-resolved should take the response from step 1 and start with
  validation instead of starting useless retries with reduced feture
  set. Step 3 and 4 are completely useless and probably lead to the
  SERVFAIL because I have configured it with DNSSEC=yes to prevent
  downgrade attacks.

  This regression seems to be caused by the patch resolved-Mitigate-
  DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic
  should only be executed if it is configured as DNSSEC=allow-downgrade
  or DNSSEC=no. See also
  https://github.com/systemd/systemd/pull/8608#issuecomment-396927885.

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

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

[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option

[fossfreedom]

** Also affects: ubuntu-budgie-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-budgie-meta (Ubuntu)
 Assignee: (unassigned) => fossfreedom (fossfreedom)

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

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

Title:
  [FFe] Ubiquity with zfs install option

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Part of the 19.10 feature announcement is zfs experimental support in
  the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
  ubuntu-19-10-an-introduction). We modified ubiquity to present an
  “EXPERIMENTAL” (with warning) ZSYS install option. This option is only
  visible is zfsutils-linux is installed on the system. So, it won't be
  available for derivatives that use ubiquity but do not seed zfsutils-
  linux.

  Update as of 20/09/2019: the plan is to not seed zsys (security review
  will take a while), but to only seed zfsutils-linux. People can then
  opt-in to zsys which should be available by default next cycle.

  This option takes an entire disk and have a fix set of dataset
  installed. There is no support but we need this to make an official
  install option for the next LTS.

  The patch has been created to be as minimal as possible. Partman does
  a full disk partitioning, and then the script zsys-setup the first
  non-ESP partition and replaces with zfs pools.

  4 partitions are created:
  1. if GPT partitioning: ESP partition. This one is done by partman directly.
  2. bpool (for boot), pool with older zfs compatible version to be readable by 
grub)
  3. rpool (for / and userdataset)
  4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on 
moved to the ESP)

  Additionaly if a swap file has been created by ubiquity, it is
  recreated as a ZFS volume. If the script fails to execute, the final
  installation is an ext4 installation on entire disk.

  Note that the implementation is slightly different from the
  specification due to a difficult cohabitation with partman in the
  custom partitioning page.

  Please find attached the MP on ubiquity as well as the package build
  log.

  https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
  amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz

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

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

[Touch-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

[Julian Alarcon]

This bug is present in Ubuntu 19.10 (yes, the beta) with a Lenovo T560.

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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

[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

[Julian Alarcon]

This bug is present in Ubuntu 19.10

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  In Progress
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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

[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.437

---
ubuntu-meta (1.437) eoan; urgency=medium

  * Refreshed dependencies
  * Added fonts-liberation2 to desktop-minimal-recommends, desktop-
recommends (LP: #1844689)
  * Added fonts-noto-color-emoji to desktop-minimal-recommends
  * Added fonts-opensymbol to desktop-minimal-recommends, desktop-
recommends
  * Added zfsutils-linux to desktop-minimal-recommends, desktop-
recommends (LP: #1843768)
  * Removed gdm3 from desktop [s390x], desktop-minimal [s390x]

 -- Didier Roche   Fri, 04 Oct 2019 16:19:27 +0200

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

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

Title:
  [FFe] Ubiquity with zfs install option

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Part of the 19.10 feature announcement is zfs experimental support in
  the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
  ubuntu-19-10-an-introduction). We modified ubiquity to present an
  “EXPERIMENTAL” (with warning) ZSYS install option. This option is only
  visible is zfsutils-linux is installed on the system. So, it won't be
  available for derivatives that use ubiquity but do not seed zfsutils-
  linux.

  Update as of 20/09/2019: the plan is to not seed zsys (security review
  will take a while), but to only seed zfsutils-linux. People can then
  opt-in to zsys which should be available by default next cycle.

  This option takes an entire disk and have a fix set of dataset
  installed. There is no support but we need this to make an official
  install option for the next LTS.

  The patch has been created to be as minimal as possible. Partman does
  a full disk partitioning, and then the script zsys-setup the first
  non-ESP partition and replaces with zfs pools.

  4 partitions are created:
  1. if GPT partitioning: ESP partition. This one is done by partman directly.
  2. bpool (for boot), pool with older zfs compatible version to be readable by 
grub)
  3. rpool (for / and userdataset)
  4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on 
moved to the ESP)

  Additionaly if a swap file has been created by ubiquity, it is
  recreated as a ZFS volume. If the script fails to execute, the final
  installation is an ext4 installation on entire disk.

  Note that the implementation is slightly different from the
  specification due to a difficult cohabitation with partman in the
  custom partitioning page.

  Please find attached the MP on ubiquity as well as the package build
  log.

  https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
  amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz

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

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

[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-mate-meta - 1.254

---
ubuntu-mate-meta (1.254) eoan; urgency=medium

  * Refreshed dependencies
  * Added zfsutils-linux to core, desktop (LP: #1843768)

 -- Martin Wimpress   Fri, 04 Oct 2019 13:26:30
+0100

** Changed in: ubuntu-mate-meta (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 ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1843768

Title:
  [FFe] Ubiquity with zfs install option

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Part of the 19.10 feature announcement is zfs experimental support in
  the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
  ubuntu-19-10-an-introduction). We modified ubiquity to present an
  “EXPERIMENTAL” (with warning) ZSYS install option. This option is only
  visible is zfsutils-linux is installed on the system. So, it won't be
  available for derivatives that use ubiquity but do not seed zfsutils-
  linux.

  Update as of 20/09/2019: the plan is to not seed zsys (security review
  will take a while), but to only seed zfsutils-linux. People can then
  opt-in to zsys which should be available by default next cycle.

  This option takes an entire disk and have a fix set of dataset
  installed. There is no support but we need this to make an official
  install option for the next LTS.

  The patch has been created to be as minimal as possible. Partman does
  a full disk partitioning, and then the script zsys-setup the first
  non-ESP partition and replaces with zfs pools.

  4 partitions are created:
  1. if GPT partitioning: ESP partition. This one is done by partman directly.
  2. bpool (for boot), pool with older zfs compatible version to be readable by 
grub)
  3. rpool (for / and userdataset)
  4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on 
moved to the ESP)

  Additionaly if a swap file has been created by ubiquity, it is
  recreated as a ZFS volume. If the script fails to execute, the final
  installation is an ext4 installation on entire disk.

  Note that the implementation is slightly different from the
  specification due to a difficult cohabitation with partman in the
  custom partitioning page.

  Please find attached the MP on ubiquity as well as the package build
  log.

  https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
  amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz

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

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

[Touch-packages] [Bug 1699360] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Gioele Barabucci]

** Changed in: gnome-software (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: gnome-software (Ubuntu)
   Status: Opinion => Confirmed

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

Title:
  package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in debconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  this all

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libpam-systemd:amd64 232-21ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jun 21 00:45:00 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-19 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1845337] Re: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 242-7ubuntu1

---
systemd (242-7ubuntu1) eoan; urgency=medium

  * Merge from unstable
  * UBUNTU: drop setting fs.protected_regular and fs.protected_fifos from
sysctl defaults shipped by systemd (LP: #1845637)
File: 
debian/patches/debian/UBUNTU-drop-kernel.-settings-from-sysctl-defaults-shipped.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6e583847b04c3f83a50f3bd6947dcae6a73d8388
  * test-execute: Filter /dev/.lxc in exec-dynamicuser-statedir.service.
It appears in nested LXC containers and broke the armhf autopkgtest.
(LP: #1845337)
File: 
debian/patches/test-execute-Filter-dev-.lxc-in-exec-dynamicuser-statedir.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=75af888d5552f706b86182a56f12ccc8e83ca04e

systemd (242-7) unstable; urgency=medium

  * sleep: properly pass verb to sleep script
  * core: factor root_directory application out of apply_working_directory.
Fixes RootDirectory not working when used in combination with User.
(Closes: #939408)
  * shared/bus-util: drop trusted annotation from
bus_open_system_watch_bind_with_description().
This ensures that access controls on systemd-resolved's D-Bus interface
are enforced properly.
(CVE-2019-15718, Closes: #939353)

 -- Balint Reczey   Wed, 02 Oct 2019 14:13:28 +0200

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

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

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

Title:
  Disco autopkgtest @ armhf fails root-unittests -> test-execute ->
  exec-dynamicuser-statedir.service

Status in qemu package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in qemu source package in Disco:
  Triaged
Status in systemd source package in Disco:
  Triaged

Bug description:
  Since the recent few weeks systemd autopkgtest @ armhf @ disco fail
  [1].

  The log is very (very) long and partially interwoven due to concurrent 
execution.
  Somewhere in between we see this subcase is the one failing: root-unittests
  Of this test (which again has many subtests) it is: test-execute
  And of this again it is (always):

  I'll attach bad and good case full and stripped logs.

  
  The diff of those comes down to just:
  1. execute a find in a shell
  2. shell exits
  3. exec-dynamicuser-statedir.service: Main process exited, code=exited, 
status=0/SUCCESS
  vs
  3. exec-dynamicuser-statedir.service: Main process exited, code=exited, 
status=1/FAILURE
  4. in the bad case that triggers an assertion
  The find that fails is:

  find / -path /var/tmp -o -path /tmp -o -path /proc -o -path
  /dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf

  Good and bad case are the same most recent version
  systemd/240-6ubuntu5.7.

  Maybe something is bad in the containers we have for armhf in regard to these 
paths?
  Was there any change we'd know of?

  If there is nothing known, could we force-badtest it to get it out of
  the way of ongoing migrations?

  [1]: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf

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

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

[Touch-packages] [Bug 1845637] Re: Drop setting fs.protected_regular and fs.protected_fifos from sysctl defaults shipped by systemd

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 242-7ubuntu1

---
systemd (242-7ubuntu1) eoan; urgency=medium

  * Merge from unstable
  * UBUNTU: drop setting fs.protected_regular and fs.protected_fifos from
sysctl defaults shipped by systemd (LP: #1845637)
File: 
debian/patches/debian/UBUNTU-drop-kernel.-settings-from-sysctl-defaults-shipped.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6e583847b04c3f83a50f3bd6947dcae6a73d8388
  * test-execute: Filter /dev/.lxc in exec-dynamicuser-statedir.service.
It appears in nested LXC containers and broke the armhf autopkgtest.
(LP: #1845337)
File: 
debian/patches/test-execute-Filter-dev-.lxc-in-exec-dynamicuser-statedir.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=75af888d5552f706b86182a56f12ccc8e83ca04e

systemd (242-7) unstable; urgency=medium

  * sleep: properly pass verb to sleep script
  * core: factor root_directory application out of apply_working_directory.
Fixes RootDirectory not working when used in combination with User.
(Closes: #939408)
  * shared/bus-util: drop trusted annotation from
bus_open_system_watch_bind_with_description().
This ensures that access controls on systemd-resolved's D-Bus interface
are enforced properly.
(CVE-2019-15718, Closes: #939353)

 -- Balint Reczey   Wed, 02 Oct 2019 14:13:28 +0200

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

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

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

Title:
  Drop setting fs.protected_regular and fs.protected_fifos from sysctl
  defaults shipped by systemd

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Those settings are typically set by the kernel in Ubuntu.

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

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

[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[George Davis C]

Is absolutely no one looking into this issue?

This issue has been with Ubuntu since 17.04 and we are in 19.04 at the
moment. I have multiple Ubuntu server clusters and this issue is
breaking every dns name resolution in all of them. I am unable to
reliably collect logs and manage systems over the network.

Please bump the bug importance to Medium. DNS is an absolute necessity
and nothing is more important than DNS if I have 100+ servers in a
cluster but no networking.

I think it is obvious to anyone that this issue needs a resolution ASAP.
Please address this issue with atmost priority.

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

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

[Touch-packages] [Bug 1846787] [NEW] systemd-logind leaves leftover sessions and scope files

[Heitor Alves de Siqueira]

Public bug reported:

[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd

[Description]
The current systemd-logind version present in Xenial can leave abandoned SSH
sessions and scope files in cases where the host sees a lot of concurrent SSH
connections. These leftover sessions can slow down systemd performance
greatly, and can have an impact on sshd handling a great number of concurrent
connections.

To fix this issue, patches are needed in both dbus and systemd. These improve 
the
performance of the communication between dbus and systemd, so that they can
handle a better volume of events (e.g. SSH logins). All of those patches are
already present from Bionic onwards, so we only need those fixes for Xenial.

== Systemd ==
Upstream patches:
- core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification 
(d8fdc62037b5)
- tree-wide: introduce new SOCKADDR_UN_LEN() macro, and use it everywhere 
(fc2fffe7706e)
- journald: stack allocation cannot fail (23be5709e10b)

$ git describe --contains d8fdc62037b5 fc2fffe7706e 23be5709e10b
v230~71^2~2
v230~71^2~1
v230~71^2

$ rmadison systemd
 systemd | 229-4ubuntu4 | xenial  | source, ...
 systemd | 229-4ubuntu21.21 | xenial-security | source, ...
 systemd | 229-4ubuntu21.22 | xenial-updates  | source, ... <
 systemd | 237-3ubuntu10| bionic  | source, ...
 systemd | 237-3ubuntu10.29 | bionic-security | source, ...
 systemd | 237-3ubuntu10.29 | bionic-updates  | source, ...
 systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...

== DBus ==
Upstream patches:
- Only read one message at a time if there are fds pending (892f084eeda0)
- bus: Fix timeout restarts  (529600397bca)
- DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)

$ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
dbus-1.11.10~44
dbus-1.11.10~45
dbus-1.11.16~2

$ rmadison dbus
 dbus | 1.10.6-1ubuntu3| xenial   | source, ...
 dbus | 1.10.6-1ubuntu3.4  | xenial-security  | source, ...
 dbus | 1.10.6-1ubuntu3.4  | xenial-updates   | source, ... <
 dbus | 1.12.2-1ubuntu1| bionic   | source, ...
 dbus | 1.12.2-1ubuntu1.1  | bionic-security  | source, ...
 dbus | 1.12.2-1ubuntu1.1  | bionic-updates   | source, ...

[Test Case]
1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost 
sleep 1 > /dev/null & done

2) Check for leaked sessions in /run/systemd/system/:
multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-116.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-117.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-118.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-119.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-120.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-121.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-122.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-123.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-126.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-131.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-134.scope.d
...

[Regression Potential]
The regression potential is low, as these patches have seen extensive testing
both upstream and in more recent releases of Ubuntu. Nonetheless, these new
packages will be rigorously tested through autopkgtest to avoid any possible
Xenial-specific regressions.

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

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

** Affects: dbus (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Heitor Alves de Siqueira (halves)
 Status: New

** Affects: systemd (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Heitor Alves de Siqueira (halves)
 Status: New


** Tags: sts

[Touch-packages] [Bug 1842437] Re: Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem with udev

[Eric Desrochers]

[STS-Sponsor]

Sponsored in Bionic.

Thanks Mauricio for your great work on this bug and the FTBFS situation.

- Eric

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

Title:
  Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem
  with udev

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * Users / systemd can fail to mount a filesystem by UUID
 (e.g., during boot, triggering emergency shell prompt)
 if the magic bytes for the nilfs filesystem are written
 to the right place in a partition of another filesystem,
 (for whatever reason or coincidence).

   * Note this can happen after the filesystem/mount is working
 correctly, so a change of behavior/problem can potentially
 be noticed when trying to mount the filesystem again, which
 can very well be the next time the system boots.

   * This happens because if udev blkid detects more than one
 filesystem, it does not print the UUID env vars required
 to create the /dev/disk/by-id symlinks and other things.

   * The fix enhances the check for valid nilfs superblock by
 specifically checking a value read from disk to be valid/
 within a value range, which addresses this one occurrence
 and prevents a lot more.

  [Test Case]

   * Synthetic test case written for this problem on comment #6.

  [Regression Potential]

   * Low.  The code is contained in the probe for the nilfs filesystem.

   * This just makes it be more restrictive about the possibly valid
 values for a few bytes read from disk (that now need to be within
 the acceptable range of valid values) so this only decreases false-
 positives, and cannot increase false-negatives of valid filesystems.

  [Original Description]

  The nilfs filesystem has a backup superblock at the end of the device.

  If the magic number is coincidentally found at the right position
  and the filesystem is on a partition/not-wholedisk device,
  the only check left is for checksum verification,
  which is explicitly ignored in 'udev built-in blkid'.

  This causes blkid to detect one actually valid filesystem with a
  superblock at the beginning of the device (e.g., ext4), and then
  an invalid nilfs2 filesystem due to a coincidental magic number
  at the end of the device.

  And this causes blkid to break out of the safeprobe routine
  (which expects a single filesystem to be detected), and not
  print the UUIDs, thus not creating /dev/disk/by-uuid/ links
  which prevent mounting the partition by-uuid at boot time,
  causing emergency shell/boot failures.

  This upstream fix resolved the problem by introducing a check
  for the 'bytes' paramenters in the superblock, which is read
  from disk, and turns out to have an out-of-range value.

  - 'liblkid: Add length check in probe_nilfs2 before crc32'
  
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=ac681a310c32319423297544833932f4d689a7a2

  $ git describe --contains ac681a310c32319423297544833932f4d689a7a2
  v2.29-rc1~172

  Xenial, which is v2.27.1-based, is the only release that needs it.
  Bionic is v2.31.1, so all post-Xenial supported releases have it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1842437/+subscriptions

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

[Touch-packages] [Bug 1846766] [NEW] Segmentation fault for large sequences

[Eguzki]

Public bug reported:

Using meld [0] software, segmentation fault happens when comparing one
file with large sequences. Some base64 encoded data in a yaml file
contains 20k character sequence in a single line.

It is easy to reproduce comparing these two yaml files:


$ cat my.v1.yaml
version: 1.0.0



$ cat my.v0.yaml
version: 0.0.0
data:
  - base64data: 

[Touch-packages] [Bug 1843007] Re: namespace: make MountFlags=shared work again

[Dan Streetman]

> Would you mind to include
https://github.com/systemd/systemd/commit/37ed15d7edaf59a1fc7c9e3552cd93a83f3814ef
into Bionic?

this commit claims to fix a problem introduced by commit
0722b359342d2a9f9e0d453875624387a0ba1be2, but that commit isn't in
Bionic, unless I'm missing something.

Can you provide steps for reproducing your problem?

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

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

Title:
  namespace: make MountFlags=shared work again

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Incomplete

Bug description:
  Systemd in Bionic fails to handle MountFlags correctly. Would you mind
  to include
  
https://github.com/systemd/systemd/commit/37ed15d7edaf59a1fc7c9e3552cd93a83f3814ef
  into Bionic? This bug seriously affects Docker > 18.6, see the Docker
  release notes for 18.09.1 (https://docs.docker.com/engine/release-
  notes/#18091).

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

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

[Touch-packages] [Bug 1842437] Re: Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem with udev

[Mauricio Faria de Oliveira]

And this debdiff / util-linux on xenial builds fine again!
Built on all architectures on PPA [1].

cheers,
Mauricio

[1] https://launchpad.net/~mfo/+archive/ubuntu/lp1842437

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

Title:
  Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem
  with udev

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * Users / systemd can fail to mount a filesystem by UUID
 (e.g., during boot, triggering emergency shell prompt)
 if the magic bytes for the nilfs filesystem are written
 to the right place in a partition of another filesystem,
 (for whatever reason or coincidence).

   * Note this can happen after the filesystem/mount is working
 correctly, so a change of behavior/problem can potentially
 be noticed when trying to mount the filesystem again, which
 can very well be the next time the system boots.

   * This happens because if udev blkid detects more than one
 filesystem, it does not print the UUID env vars required
 to create the /dev/disk/by-id symlinks and other things.

   * The fix enhances the check for valid nilfs superblock by
 specifically checking a value read from disk to be valid/
 within a value range, which addresses this one occurrence
 and prevents a lot more.

  [Test Case]

   * Synthetic test case written for this problem on comment #6.

  [Regression Potential]

   * Low.  The code is contained in the probe for the nilfs filesystem.

   * This just makes it be more restrictive about the possibly valid
 values for a few bytes read from disk (that now need to be within
 the acceptable range of valid values) so this only decreases false-
 positives, and cannot increase false-negatives of valid filesystems.

  [Original Description]

  The nilfs filesystem has a backup superblock at the end of the device.

  If the magic number is coincidentally found at the right position
  and the filesystem is on a partition/not-wholedisk device,
  the only check left is for checksum verification,
  which is explicitly ignored in 'udev built-in blkid'.

  This causes blkid to detect one actually valid filesystem with a
  superblock at the beginning of the device (e.g., ext4), and then
  an invalid nilfs2 filesystem due to a coincidental magic number
  at the end of the device.

  And this causes blkid to break out of the safeprobe routine
  (which expects a single filesystem to be detected), and not
  print the UUIDs, thus not creating /dev/disk/by-uuid/ links
  which prevent mounting the partition by-uuid at boot time,
  causing emergency shell/boot failures.

  This upstream fix resolved the problem by introducing a check
  for the 'bytes' paramenters in the superblock, which is read
  from disk, and turns out to have an out-of-range value.

  - 'liblkid: Add length check in probe_nilfs2 before crc32'
  
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=ac681a310c32319423297544833932f4d689a7a2

  $ git describe --contains ac681a310c32319423297544833932f4d689a7a2
  v2.29-rc1~172

  Xenial, which is v2.27.1-based, is the only release that needs it.
  Bionic is v2.31.1, so all post-Xenial supported releases have it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1842437/+subscriptions

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

[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option

[Martin Wimpress]

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [FFe] Ubiquity with zfs install option

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Part of the 19.10 feature announcement is zfs experimental support in
  the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
  ubuntu-19-10-an-introduction). We modified ubiquity to present an
  “EXPERIMENTAL” (with warning) ZSYS install option. This option is only
  visible is zfsutils-linux is installed on the system. So, it won't be
  available for derivatives that use ubiquity but do not seed zfsutils-
  linux.

  Update as of 20/09/2019: the plan is to not seed zsys (security review
  will take a while), but to only seed zfsutils-linux. People can then
  opt-in to zsys which should be available by default next cycle.

  This option takes an entire disk and have a fix set of dataset
  installed. There is no support but we need this to make an official
  install option for the next LTS.

  The patch has been created to be as minimal as possible. Partman does
  a full disk partitioning, and then the script zsys-setup the first
  non-ESP partition and replaces with zfs pools.

  4 partitions are created:
  1. if GPT partitioning: ESP partition. This one is done by partman directly.
  2. bpool (for boot), pool with older zfs compatible version to be readable by 
grub)
  3. rpool (for / and userdataset)
  4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on 
moved to the ESP)

  Additionaly if a swap file has been created by ubiquity, it is
  recreated as a ZFS volume. If the script fails to execute, the final
  installation is an ext4 installation on entire disk.

  Note that the implementation is slightly different from the
  specification due to a difficult cohabitation with partman in the
  custom partitioning page.

  Please find attached the MP on ubiquity as well as the package build
  log.

  https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
  amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz

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

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

[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option

[Martin Wimpress]

** Changed in: ubuntu-mate-meta (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

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

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: New => In Progress

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

Title:
  [FFe] Ubiquity with zfs install option

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Part of the 19.10 feature announcement is zfs experimental support in
  the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
  ubuntu-19-10-an-introduction). We modified ubiquity to present an
  “EXPERIMENTAL” (with warning) ZSYS install option. This option is only
  visible is zfsutils-linux is installed on the system. So, it won't be
  available for derivatives that use ubiquity but do not seed zfsutils-
  linux.

  Update as of 20/09/2019: the plan is to not seed zsys (security review
  will take a while), but to only seed zfsutils-linux. People can then
  opt-in to zsys which should be available by default next cycle.

  This option takes an entire disk and have a fix set of dataset
  installed. There is no support but we need this to make an official
  install option for the next LTS.

  The patch has been created to be as minimal as possible. Partman does
  a full disk partitioning, and then the script zsys-setup the first
  non-ESP partition and replaces with zfs pools.

  4 partitions are created:
  1. if GPT partitioning: ESP partition. This one is done by partman directly.
  2. bpool (for boot), pool with older zfs compatible version to be readable by 
grub)
  3. rpool (for / and userdataset)
  4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on 
moved to the ESP)

  Additionaly if a swap file has been created by ubiquity, it is
  recreated as a ZFS volume. If the script fails to execute, the final
  installation is an ext4 installation on entire disk.

  Note that the implementation is slightly different from the
  specification due to a difficult cohabitation with partman in the
  custom partitioning page.

  Please find attached the MP on ubiquity as well as the package build
  log.

  https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
  amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz

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

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

[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option

[Martin Wimpress]

** Also affects: ubuntu-mate-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [FFe] Ubiquity with zfs install option

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Part of the 19.10 feature announcement is zfs experimental support in
  the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
  ubuntu-19-10-an-introduction). We modified ubiquity to present an
  “EXPERIMENTAL” (with warning) ZSYS install option. This option is only
  visible is zfsutils-linux is installed on the system. So, it won't be
  available for derivatives that use ubiquity but do not seed zfsutils-
  linux.

  Update as of 20/09/2019: the plan is to not seed zsys (security review
  will take a while), but to only seed zfsutils-linux. People can then
  opt-in to zsys which should be available by default next cycle.

  This option takes an entire disk and have a fix set of dataset
  installed. There is no support but we need this to make an official
  install option for the next LTS.

  The patch has been created to be as minimal as possible. Partman does
  a full disk partitioning, and then the script zsys-setup the first
  non-ESP partition and replaces with zfs pools.

  4 partitions are created:
  1. if GPT partitioning: ESP partition. This one is done by partman directly.
  2. bpool (for boot), pool with older zfs compatible version to be readable by 
grub)
  3. rpool (for / and userdataset)
  4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on 
moved to the ESP)

  Additionaly if a swap file has been created by ubiquity, it is
  recreated as a ZFS volume. If the script fails to execute, the final
  installation is an ext4 installation on entire disk.

  Note that the implementation is slightly different from the
  specification due to a difficult cohabitation with partman in the
  custom partitioning page.

  Please find attached the MP on ubiquity as well as the package build
  log.

  https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
  amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz

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

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

[Touch-packages] [Bug 1840640] Re: sync_file_range fails in nspawn containers on arm, ppc

[Dan Streetman]

> Is it possible arm64 abi is different from armhf (32bit?)

ah, that was it, thanks, I can reproduce it now :)

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

Title:
  sync_file_range fails in nspawn containers on arm, ppc

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  ARM has two sync_file_range syscalls, sync_file_range and
  sync_file_range2. The former is apparently not used, and glibc calls
  the latter whenever a userspace program calls sync_file_range. I'm
  guessing systemd-nspawn doesn't know this, because the follow code
  consistently fails in an nspawn container on ARM:

  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 

  void main()
  {
  int f = open("/tmp/syncrange.test",O_CREAT|O_RDWR,0666);
  int r=sync_file_range(f, 0, 0, 0);
  if (r)
  perror("sync_file_range");
  close(f);
  }

  This seems to be causing problems specifically for borg(backup) and
  postgres:

  https://github.com/borgbackup/borg/issues/4710
  
https://www.postgresql.org/message-id/flat/CA%2BhUKG%2BydOUT4zjxb6QmJWy8U9WbC-q%2BJWV7wLsEY9Df%3Dmw0Mw%40mail.gmail.com#ac8f14897647dc7eae3c7e7cbed36d93

  The solution should be to cherrypick
  https://github.com/systemd/systemd/pull/13352, I am currently waiting
  for systemd to rebuild on a slow ARM box. Any chance of an SRU?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd-container 237-3ubuntu10.24
  Uname: Linux 4.14.66+ armv7l
  NonfreeKernelModules: extcon_usb_gpio
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: armhf
  Date: Mon Aug 19 11:10:48 2019
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1842437] Re: Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem with udev

[Mauricio Faria de Oliveira]

Eric,

The fix to xenial livecd-rootfs / launchpad buildd chroot has been
rolled out.

I just confirmed that /dev/ptmx is OK with a test package build on
Launchpad PPA.

  ...
  dh_clean
  # Check /dev/ptmx|pts/
  ls -l /dev/ptmx
  crw-rw-rw- 1 root root 5, 2 Oct 4 08:13 /dev/ptmx
  ls -l /dev/pts/*
  c- 1 root root 5, 2 Oct 4 11:25 /dev/pts/ptmx
  make[1]: Leaving directory '/<>/test-pkg-1.0+devpts1'
  ...

Now testing a build of util-linux, and hopefully we can move forward
with the SRU again.

cheers,
Mauricio

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

Title:
  Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem
  with udev

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * Users / systemd can fail to mount a filesystem by UUID
 (e.g., during boot, triggering emergency shell prompt)
 if the magic bytes for the nilfs filesystem are written
 to the right place in a partition of another filesystem,
 (for whatever reason or coincidence).

   * Note this can happen after the filesystem/mount is working
 correctly, so a change of behavior/problem can potentially
 be noticed when trying to mount the filesystem again, which
 can very well be the next time the system boots.

   * This happens because if udev blkid detects more than one
 filesystem, it does not print the UUID env vars required
 to create the /dev/disk/by-id symlinks and other things.

   * The fix enhances the check for valid nilfs superblock by
 specifically checking a value read from disk to be valid/
 within a value range, which addresses this one occurrence
 and prevents a lot more.

  [Test Case]

   * Synthetic test case written for this problem on comment #6.

  [Regression Potential]

   * Low.  The code is contained in the probe for the nilfs filesystem.

   * This just makes it be more restrictive about the possibly valid
 values for a few bytes read from disk (that now need to be within
 the acceptable range of valid values) so this only decreases false-
 positives, and cannot increase false-negatives of valid filesystems.

  [Original Description]

  The nilfs filesystem has a backup superblock at the end of the device.

  If the magic number is coincidentally found at the right position
  and the filesystem is on a partition/not-wholedisk device,
  the only check left is for checksum verification,
  which is explicitly ignored in 'udev built-in blkid'.

  This causes blkid to detect one actually valid filesystem with a
  superblock at the beginning of the device (e.g., ext4), and then
  an invalid nilfs2 filesystem due to a coincidental magic number
  at the end of the device.

  And this causes blkid to break out of the safeprobe routine
  (which expects a single filesystem to be detected), and not
  print the UUIDs, thus not creating /dev/disk/by-uuid/ links
  which prevent mounting the partition by-uuid at boot time,
  causing emergency shell/boot failures.

  This upstream fix resolved the problem by introducing a check
  for the 'bytes' paramenters in the superblock, which is read
  from disk, and turns out to have an out-of-range value.

  - 'liblkid: Add length check in probe_nilfs2 before crc32'
  
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=ac681a310c32319423297544833932f4d689a7a2

  $ git describe --contains ac681a310c32319423297544833932f4d689a7a2
  v2.29-rc1~172

  Xenial, which is v2.27.1-based, is the only release that needs it.
  Bionic is v2.31.1, so all post-Xenial supported releases have it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1842437/+subscriptions

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

[Touch-packages] [Bug 1846702] Re: wifi

[Timo Aaltonen]

wifi has nothing to do with xorg

** Package changed: xorg (Ubuntu) => ubuntu

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

Title:
  wifi

Status in Ubuntu:
  Incomplete

Bug description:
  Bonjour, je ne parvient pas à installer la wifi sur mon ordinateur

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Oct  4 11:44:45 2019
  DistUpgraded: 2019-03-02 13:28:53,256 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:124d]
  InstallationDate: Installed on 2019-01-25 (251 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: ASUSTeK COMPUTER INC. X550CA
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=d60ac68b-590e-48c4-b2a0-9ec3efa253d7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-03-02 (215 days ago)
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CA.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Mar  2 11:26:17 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Touch-packages] [Bug 459730] Re: rsyslog doesn't create /dev/xconsole

[johnnyb0y]

$ cat /etc/issue
Linux Mint 17.3 Rosa

$ uname -a
Linux R2D2 4.4.0-138-generic #164~14.04.1-Ubuntu SMP Fri Oct 5 08:56:16 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

Syslog contents showing error:

Oct  4 12:35:31 R2D2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" 
x-pid="13023" x-info="http://www.rsyslog.com;] exiting on signal 15.
Oct  4 12:35:31 R2D2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" 
x-pid="13803" x-info="http://www.rsyslog.com;] start
Oct  4 12:35:31 R2D2 rsyslogd: rsyslogd's groupid changed to 104
Oct  4 12:35:31 R2D2 rsyslogd: rsyslogd's userid changed to 101
Oct  4 12:35:31 R2D2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': 
No such file or directory [try http://www.rsyslog.com/e/2039 ]

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

Title:
  rsyslog doesn't create /dev/xconsole

Status in One Hundred Papercuts:
  Fix Released
Status in rsyslog package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: rsyslog

  Looks like this was missed in the move to upstart.

  This function was called in init.d/rsyslog start:

  create_xconsole() {
  if [ ! -e /dev/xconsole ]
  then
  mknod -m 640 /dev/xconsole p
  chown root:adm /dev/xconsole
  [ -x /sbin/restorecon ] && /sbin/restorecon /dev/xconsole
  fi
  }

  I can't find any reference to it now. If this is old school then it should be 
re
  moved from the config.

  rsyslog:
Installed: 4.2.0-2ubuntu5

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

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

[Touch-packages] [Bug 1846509] Re: networkd doesn't take into account search domain received by DHCP

[Balint Reczey]

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

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

Title:
  networkd doesn't take into account search domain received by DHCP

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Hi,

  When starting a virtual machine with the following command line :

  qemu-system-x86_64 -k fr -m 1024 -smp 1 -display none \
-rtc base=utc -daemonize \ 
-drive if=none,file="my.qcow2",id=hd0 \
-device virtio-blk,drive=hd0 \
-netdev 
user,id=user.0,hostfwd=tcp::32768-:22,dnssearch=dns.companyname.com \
-device virtio-net,netdev=user.0,mac=de:ad:de:01:02:03 \
-vga none

  The system-network doesn't take into account search domain and then
  search fail.

  The same setup does work when using NetworkManager.

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

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

[Touch-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled

[Matthias]

I have the same problem on my Lenovo T480s with Xubuntu 19.04. Disabling 
Bluetooth helps as a workaraound.
I also tried the mainline kernel 5.3.2 with the exact same result.

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

Title:
  System wakes up immediately after suspend if Bluetooth is still
  enabled

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After replacing my USB mouse with a BT mouse, I noticed my machine
  would no longer suspend without immediately waking up. i.e. I suspend
  and see the light go into the slow fade in and out for one cycle and
  then goes solid and the display wakes up again. If I disable BT (via
  blueman applet) suspend works fine.

  I've fixed this by shutting down the BT service before suspend, and
  starting it back up on wake, as indicated here:
  https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately-
  after-suspend

  Perhaps this script should be included in blueZ as suspend issues seem
  very hard to debug and the immediate wake after suspend could be
  caused many any number of things.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1 [modified: 
lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  3 13:16:14 2019
  InstallationDate: Installed on 2019-02-09 (53 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0051.2018.1015.1513
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:BB:60:50:92:5D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1912660 acl:106009 sco:0 events:337 errors:0
TX bytes:12331 acl:74 sco:0 commands:204 errors:0

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

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

[Touch-packages] [Bug 1843887] Re: egfault at ... error 6 in libglib-2.0.so

[Paul White]

** Package changed: ubuntu => glib2.0 (Ubuntu)

** Tags added: disco

** Summary changed:

- egfault at ... error 6 in libglib-2.0.so
+ segfault at ... error 6 in libglib-2.0.so

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

Title:
  segfault at ... error 6 in libglib-2.0.so

Status in glib2.0 package in Ubuntu:
  New

Bug description:

  Ubuntu 19.04

  after waking up I get the following errors. Sometimes the laptop does
  not wake up.  (I expect it to wake up)

  --- BIOS contains WGDS but no WRDS
  --- [ 4695.737914] geoclue[1309]: segfault at 20

  
  this is the dmesg output (only after suspend).

  [ 4690.382631] PM: suspend entry (deep)
  [ 4690.382632] PM: Syncing filesystems ... done.
  [ 4690.641807] rfkill: input handler enabled
  [ 4690.666176] Freezing user space processes ... (elapsed 0.001 seconds) done.
  [ 4690.667819] OOM killer disabled.
  [ 4690.667819] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [ 4690.669009] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 4690.884850] wlp5s0: deauthenticating from 0e:8d:cb:6e:3e:4e by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [ 4691.015894] sd 0:0:0:0: [sda] Synchronizing SCSI cache
  [ 4691.017317] sd 0:0:0:0: [sda] Stopping disk
  [ 4691.420328] ACPI: EC: interrupt blocked
  [ 4691.541129] ACPI: Preparing to enter system sleep state S3
  [ 4691.544137] ACPI: EC: event blocked
  [ 4691.544138] ACPI: EC: EC stopped
  [ 4691.544139] PM: Saving platform NVS memory
  [ 4691.544188] Disabling non-boot CPUs ...
  [ 4691.544807] IRQ 157: no longer affine to CPU1
  [ 4691.545841] smpboot: CPU 1 is now offline
  [ 4691.550093] smpboot: CPU 2 is now offline
  [ 4691.554206] smpboot: CPU 3 is now offline
  [ 4691.558467] smpboot: CPU 4 is now offline
  [ 4691.562523] smpboot: CPU 5 is now offline
  [ 4691.566191] IRQ 128: no longer affine to CPU6
  [ 4691.567207] smpboot: CPU 6 is now offline
  [ 4691.571194] IRQ 125: no longer affine to CPU7
  [ 4691.572245] smpboot: CPU 7 is now offline
  [ 4691.575342] IRQ 124: no longer affine to CPU8
  [ 4691.576453] smpboot: CPU 8 is now offline
  [ 4691.579601] IRQ 23: no longer affine to CPU9
  [ 4691.579606] IRQ 122: no longer affine to CPU9
  [ 4691.580654] smpboot: CPU 9 is now offline
  [ 4691.584036] IRQ 127: no longer affine to CPU10
  [ 4691.584045] IRQ 132: no longer affine to CPU10
  [ 4691.584052] IRQ 152: no longer affine to CPU10
  [ 4691.585080] smpboot: CPU 10 is now offline
  [ 4691.588113] IRQ 123: no longer affine to CPU11
  [ 4691.589175] smpboot: CPU 11 is now offline
  [ 4691.598456] ACPI: Low-level resume complete
  [ 4691.598615] ACPI: EC: EC started
  [ 4691.598616] PM: Restoring platform NVS memory
  [ 4691.604642] Enabling non-boot CPUs ...
  [ 4691.604739] x86: Booting SMP configuration:
  [ 4691.604741] smpboot: Booting Node 0 Processor 1 APIC 0x2
  [ 4691.610214] unchecked MSR access error: WRMSR to 0x10f (tried to write 
0x) at rIP: 0xb9873fc8 (native_write_msr+0x8/0x30)
  [ 4691.610217] Call Trace:
  [ 4691.610228]  intel_pmu_cpu_starting+0x87/0x260
  [ 4691.610235]  ? x86_pmu_dead_cpu+0x30/0x30
  [ 4691.610241]  x86_pmu_starting_cpu+0x1a/0x30
  [ 4691.610247]  cpuhp_invoke_callback+0x99/0x540
  [ 4691.610254]  notify_cpu_starting+0x58/0x70
  [ 4691.610260]  start_secondary+0xed/0x200
  [ 4691.610265]  secondary_startup_64+0xa4/0xb0
  [ 4691.610515]  cache: parent cpu1 should not be sleeping
  [ 4691.610633] intel_pstate: Disabling energy efficiency optimization
  [ 4691.610770] microcode: sig=0x906ea, pf=0x20, revision=0x84
  [ 4691.615411] microcode: updated to revision 0xb4, date = 2019-04-01
  [ 4691.615654] CPU1 is up
  [ 4691.615708] smpboot: Booting Node 0 Processor 2 APIC 0x4
  [ 4691.617138]  cache: parent cpu2 should not be sleeping
  [ 4691.622352] CPU2 is up
  [ 4691.622403] smpboot: Booting Node 0 Processor 3 APIC 0x6
  [ 4691.623838]  cache: parent cpu3 should not be sleeping
  [ 4691.629075] CPU3 is up
  [ 4691.629122] smpboot: Booting Node 0 Processor 4 APIC 0x8
  [ 4691.630557]  cache: parent cpu4 should not be sleeping
  [ 4691.635753] CPU4 is up
  [ 4691.635805] smpboot: Booting Node 0 Processor 5 APIC 0xa
  [ 4691.637241]  cache: parent cpu5 should not be sleeping
  [ 4691.642570] CPU5 is up
  [ 4691.642646] smpboot: Booting Node 0 Processor 6 APIC 0x1
  [ 4691.644329]  cache: parent cpu6 should not be sleeping
  [ 4691.644569] microcode: sig=0x906ea, pf=0x20, revision=0xb4
  [ 4691.645446] CPU6 is up
  [ 4691.645504] smpboot: Booting Node 0 Processor 7 APIC 0x3
  [ 4691.646935]  cache: parent cpu7 should not be sleeping
  [ 4691.647519] CPU7 is up
  [ 4691.647565] smpboot: Booting Node 0 Processor 8 APIC 0x5
  [ 4691.648981]  cache: parent cpu8 should not be sleeping
  [ 4691.649601] CPU8 is up
  [ 4691.649646] smpboot: Booting Node 0 Processor 9 APIC 0x7
  [ 

[Touch-packages] [Bug 1846692] Re: PCI/internal sound card not detected

[Rex Tsai]

** Changed in: alsa-driver (Ubuntu)
 Assignee: (unassigned) => Rex Tsai (chihchun)

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  As discussed with Rex Tsai

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  4 09:43:52 2019
  InstallationDate: Installed on 2019-09-23 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET37W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET37W(1.20):bd09/11/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846692/+subscriptions

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

[Touch-packages] [Bug 1843887] [NEW] egfault at ... error 6 in libglib-2.0.so

[Launchpad Bug Tracker]

You have been subscribed to a public bug:


Ubuntu 19.04

after waking up I get the following errors. Sometimes the laptop does
not wake up.  (I expect it to wake up)

--- BIOS contains WGDS but no WRDS
--- [ 4695.737914] geoclue[1309]: segfault at 20


this is the dmesg output (only after suspend).

[ 4690.382631] PM: suspend entry (deep)
[ 4690.382632] PM: Syncing filesystems ... done.
[ 4690.641807] rfkill: input handler enabled
[ 4690.666176] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 4690.667819] OOM killer disabled.
[ 4690.667819] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[ 4690.669009] printk: Suspending console(s) (use no_console_suspend to debug)
[ 4690.884850] wlp5s0: deauthenticating from 0e:8d:cb:6e:3e:4e by local choice 
(Reason: 3=DEAUTH_LEAVING)
[ 4691.015894] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 4691.017317] sd 0:0:0:0: [sda] Stopping disk
[ 4691.420328] ACPI: EC: interrupt blocked
[ 4691.541129] ACPI: Preparing to enter system sleep state S3
[ 4691.544137] ACPI: EC: event blocked
[ 4691.544138] ACPI: EC: EC stopped
[ 4691.544139] PM: Saving platform NVS memory
[ 4691.544188] Disabling non-boot CPUs ...
[ 4691.544807] IRQ 157: no longer affine to CPU1
[ 4691.545841] smpboot: CPU 1 is now offline
[ 4691.550093] smpboot: CPU 2 is now offline
[ 4691.554206] smpboot: CPU 3 is now offline
[ 4691.558467] smpboot: CPU 4 is now offline
[ 4691.562523] smpboot: CPU 5 is now offline
[ 4691.566191] IRQ 128: no longer affine to CPU6
[ 4691.567207] smpboot: CPU 6 is now offline
[ 4691.571194] IRQ 125: no longer affine to CPU7
[ 4691.572245] smpboot: CPU 7 is now offline
[ 4691.575342] IRQ 124: no longer affine to CPU8
[ 4691.576453] smpboot: CPU 8 is now offline
[ 4691.579601] IRQ 23: no longer affine to CPU9
[ 4691.579606] IRQ 122: no longer affine to CPU9
[ 4691.580654] smpboot: CPU 9 is now offline
[ 4691.584036] IRQ 127: no longer affine to CPU10
[ 4691.584045] IRQ 132: no longer affine to CPU10
[ 4691.584052] IRQ 152: no longer affine to CPU10
[ 4691.585080] smpboot: CPU 10 is now offline
[ 4691.588113] IRQ 123: no longer affine to CPU11
[ 4691.589175] smpboot: CPU 11 is now offline
[ 4691.598456] ACPI: Low-level resume complete
[ 4691.598615] ACPI: EC: EC started
[ 4691.598616] PM: Restoring platform NVS memory
[ 4691.604642] Enabling non-boot CPUs ...
[ 4691.604739] x86: Booting SMP configuration:
[ 4691.604741] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 4691.610214] unchecked MSR access error: WRMSR to 0x10f (tried to write 
0x) at rIP: 0xb9873fc8 (native_write_msr+0x8/0x30)
[ 4691.610217] Call Trace:
[ 4691.610228]  intel_pmu_cpu_starting+0x87/0x260
[ 4691.610235]  ? x86_pmu_dead_cpu+0x30/0x30
[ 4691.610241]  x86_pmu_starting_cpu+0x1a/0x30
[ 4691.610247]  cpuhp_invoke_callback+0x99/0x540
[ 4691.610254]  notify_cpu_starting+0x58/0x70
[ 4691.610260]  start_secondary+0xed/0x200
[ 4691.610265]  secondary_startup_64+0xa4/0xb0
[ 4691.610515]  cache: parent cpu1 should not be sleeping
[ 4691.610633] intel_pstate: Disabling energy efficiency optimization
[ 4691.610770] microcode: sig=0x906ea, pf=0x20, revision=0x84
[ 4691.615411] microcode: updated to revision 0xb4, date = 2019-04-01
[ 4691.615654] CPU1 is up
[ 4691.615708] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 4691.617138]  cache: parent cpu2 should not be sleeping
[ 4691.622352] CPU2 is up
[ 4691.622403] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 4691.623838]  cache: parent cpu3 should not be sleeping
[ 4691.629075] CPU3 is up
[ 4691.629122] smpboot: Booting Node 0 Processor 4 APIC 0x8
[ 4691.630557]  cache: parent cpu4 should not be sleeping
[ 4691.635753] CPU4 is up
[ 4691.635805] smpboot: Booting Node 0 Processor 5 APIC 0xa
[ 4691.637241]  cache: parent cpu5 should not be sleeping
[ 4691.642570] CPU5 is up
[ 4691.642646] smpboot: Booting Node 0 Processor 6 APIC 0x1
[ 4691.644329]  cache: parent cpu6 should not be sleeping
[ 4691.644569] microcode: sig=0x906ea, pf=0x20, revision=0xb4
[ 4691.645446] CPU6 is up
[ 4691.645504] smpboot: Booting Node 0 Processor 7 APIC 0x3
[ 4691.646935]  cache: parent cpu7 should not be sleeping
[ 4691.647519] CPU7 is up
[ 4691.647565] smpboot: Booting Node 0 Processor 8 APIC 0x5
[ 4691.648981]  cache: parent cpu8 should not be sleeping
[ 4691.649601] CPU8 is up
[ 4691.649646] smpboot: Booting Node 0 Processor 9 APIC 0x7
[ 4691.651097]  cache: parent cpu9 should not be sleeping
[ 4691.651760] CPU9 is up
[ 4691.651803] smpboot: Booting Node 0 Processor 10 APIC 0x9
[ 4691.653237]  cache: parent cpu10 should not be sleeping
[ 4691.653932] CPU10 is up
[ 4691.653977] smpboot: Booting Node 0 Processor 11 APIC 0xb
[ 4691.655415]  cache: parent cpu11 should not be sleeping
[ 4691.656156] CPU11 is up
[ 4691.690038] ACPI: Waking up from system sleep state S3
[ 4691.697408] ACPI: button: The lid device is not compliant to SW_LID.
[ 4691.701755] ACPI: EC: interrupt unblocked
[ 4691.754868] ACPI: EC: event unblocked
[ 4691.756283] sd 

[Touch-packages] [Bug 293832]

[Johnruth652]

Thanks for sharing such a informative blog. It is really helpful for us.
Keep sharing such informative blogs again.

Office Com Setup - https://www.office-com-setup.com/

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

Title:
  printer prints page at wrong position, page cut

Status in Poppler:
  Unknown
Status in brother-cups-wrapper-extra package in Ubuntu:
  Invalid
Status in brother-lpr-drivers-extra package in Ubuntu:
  Invalid
Status in cups package in Ubuntu:
  Invalid
Status in poppler package in Ubuntu:
  Fix Released
Status in brother-cups-wrapper-extra source package in Karmic:
  Invalid
Status in brother-lpr-drivers-extra source package in Karmic:
  Invalid
Status in cups source package in Karmic:
  Invalid
Status in poppler source package in Karmic:
  Won't Fix

Bug description:
  After updating to intrepid, my Brother DCP-7025 printed every page
  about 2 cm above the usual position. This leads to pages cut as if
  printing with wrong paper configuration though A4 paper is set
  everywhere (Cups settings, program settings). For example when
  printing a test page with the printer configuration tool I cannot see
  the upper part of the Ubuntu logo.

  I have used both a hardy and an intrepid live cd to test and found out
  that the problem only occurs using intrepid, so I think it's a problem
  with the intrepid driver packages.

  However I found out, that in the printer configuration tool a wrong
  driver "DCP-7025 BR-Script" is loaded. The correct (and working!)
  driver is "DCP-7025 for CUPS". So to manually solve the problem simply
  choose the correct driver in the tool.

  I think that during the installation process of the package "brother-
  cups-wrapper-laser" the correct driver is not set to be used as
  default driver and the system continues to use the wrong driver
  instead.

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

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

[Touch-packages] [Bug 1830146] Re: Checkbox detect an extra webcam "video1"

[Canonical Certification Team]

** Changed in: checkbox-support
   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/1830146

Title:
  Checkbox detect an extra webcam "video1"

Status in Checkbox Support Library:
  Fix Released
Status in systemd package in Ubuntu:
  New

Bug description:
  Summary: System only have 1 webcam (video0) but checkbox detect an
  extra webcam "video1"

  
  -

  system-product-name: Latitude 5501
  GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (rev 02)
  CPU: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12x)
  bios-version: 1.0.0
  system-manufacturer: Dell Inc.
  Image: somerville-bionic-amd64-iso-hybrid-20180608-47

To manage notifications about this bug go to:
https://bugs.launchpad.net/checkbox-support/+bug/1830146/+subscriptions

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

[Touch-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)

[Daniel van Vugt]

So far I can't reproduce any crash in the tests on armhf (or aarch64).
But I haven't tried everything yet...

In the meantime, can anyone reproduce the failure and produce a fresh
log? If so, can you verify for me which binary is crashing?

** Changed in: fftw3 (Ubuntu Eoan)
   Status: In Progress => Incomplete

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

Title:
  fftw3 ftbfs in eoan (armhf only)

Status in fftw3 package in Ubuntu:
  Incomplete
Status in fftw3 source package in Eoan:
  Incomplete

Bug description:
  fftw3 ftbfs in eoan (armhf only).

  https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan-
  armhf.fftw3_3.3.8-2_BUILDING.txt.gz

  ( cd tests ; /usr/bin/make smallcheck )
  make[1]: Entering directory '/<>/tests'
  perl -w ./check.pl -r -c=1 -v `pwd`/bench
  Executing "/<>/tests/bench --verbose=1   --verify 
'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify 
'//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' 
--verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' 
--verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 
'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'"
  ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07
  ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07
  Segmentation fault (core dumped)
  FAILED /<>/tests/bench:  --verify 'ok7e10x12bv29' --verify 
'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' 
--verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' 
--verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify 
'//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 
'ofc2304' --verify 'ifc2304'
  make[1]: *** [Makefile:723: smallcheck] Error 1
  make[1]: Leaving directory '/<>/tests'

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

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

[Touch-packages] [Bug 1846702] Re: wifi

[Chris Guiver]

Thank you for taking the time to report this issue and helping to make
Ubuntu better.

This bug report can be converted to a question (which is aimed at
support). You can also find help with your problem in the support forum
of your local Ubuntu community http://loco.ubuntu.com/ or asking at
https://askubuntu.com or https://ubuntuforums.org, or for more support
options please look at https://discourse.ubuntu.com/t/community-
support/709

The first place I'd for wifi problems is
https://help.ubuntu.com/community/WifiDocs/WirelessTroubleShootingGuide
and if you need help in French/Francais you could try
https://wiki.ubuntu.com/IRC/ChannelList

I've marked this bug incomplete as normal support steps don't appear to
have been tried, or evidence of them hasn't been provided. If you
believe I'm in error, or can provide additional detail of steps done,
please change status back to "New" and leave comment, or additional
information as to what was attempted.

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

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

Title:
  wifi

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Bonjour, je ne parvient pas à installer la wifi sur mon ordinateur

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Oct  4 11:44:45 2019
  DistUpgraded: 2019-03-02 13:28:53,256 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:124d]
  InstallationDate: Installed on 2019-01-25 (251 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: ASUSTeK COMPUTER INC. X550CA
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=d60ac68b-590e-48c4-b2a0-9ec3efa253d7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-03-02 (215 days ago)
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CA.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Mar  2 11:26:17 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Touch-packages] [Bug 1846709] [NEW] pcscd crashed with SIGSEGV in usb_claim_interface()

[Pavel Selivanov]

Public bug reported:

iBank token and driver was used

** Affects: pcsc-lite (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  pcscd crashed with SIGSEGV in usb_claim_interface()

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  iBank token and driver was used

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1846709/+subscriptions

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

[Touch-packages] [Bug 1846702] [NEW] wifi

[lacroix]

Public bug reported:

Bonjour, je ne parvient pas à installer la wifi sur mon ordinateur

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Fri Oct  4 11:44:45 2019
DistUpgraded: 2019-03-02 13:28:53,256 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
 
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:124d]
InstallationDate: Installed on 2019-01-25 (251 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
MachineType: ASUSTeK COMPUTER INC. X550CA
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=d60ac68b-590e-48c4-b2a0-9ec3efa253d7 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-03-02 (215 days ago)
dmi.bios.date: 03/24/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550CA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550CA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CA.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X550CA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat Mar  2 11:26:17 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   17900 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  wifi

Status in xorg package in Ubuntu:
  New

Bug description:
  Bonjour, je ne parvient pas à installer la wifi sur mon ordinateur

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Oct  4 11:44:45 2019
  DistUpgraded: 2019-03-02 13:28:53,256 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:124d]
  InstallationDate: Installed on 2019-01-25 (251 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: ASUSTeK COMPUTER INC. X550CA
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=d60ac68b-590e-48c4-b2a0-9ec3efa253d7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-03-02 (215 days ago)
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CA.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550CA
  

[Touch-packages] [Bug 1845909] Re: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

[Balint Reczey]

Marking as fixed since the issue is not seen anymore in 19.10.

** Summary changed:

- IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4
+ [SRU] IPv6 link local address is assigned even when 
LinkLocalAddressing=no|ipv4

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

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

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

Title:
  [SRU] IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

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

Bug description:
  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

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

[Touch-packages] [Bug 1846509] Re: networkd doesn't take into account search domain received by DHCP

[Balint Reczey]

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

Title:
  networkd doesn't take into account search domain received by DHCP

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  When starting a virtual machine with the following command line :

  qemu-system-x86_64 -k fr -m 1024 -smp 1 -display none \
-rtc base=utc -daemonize \ 
-drive if=none,file="my.qcow2",id=hd0 \
-device virtio-blk,drive=hd0 \
-netdev 
user,id=user.0,hostfwd=tcp::32768-:22,dnssearch=dns.companyname.com \
-device virtio-net,netdev=user.0,mac=de:ad:de:01:02:03 \
-vga none

  The system-network doesn't take into account search domain and then
  search fail.

  The same setup does work when using NetworkManager.

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

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

[Touch-packages] [Bug 1846692] [NEW] PCI/internal sound card not detected

[Lech Sandecki]

Public bug reported:

As discussed with Rex Tsai

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct  4 09:43:52 2019
InstallationDate: Installed on 2019-09-23 (10 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/11/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET37W (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET37W(1.20):bd09/11/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDCTO1WW
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug disco

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  As discussed with Rex Tsai

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  4 09:43:52 2019
  InstallationDate: Installed on 2019-09-23 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET37W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET37W(1.20):bd09/11/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846692/+subscriptions

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

[Touch-packages] [Bug 1846180] Re: 1910 software-properties larger screen size

[Matthew Paul Thomas]

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

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

Title:
  1910 software-properties larger screen size

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  Screen size 1366x768, Russian language.

  Update settings go beyond the edge of the screen. The window cannot be
  reduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1846180/+subscriptions

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

[Touch-packages] [Bug 1846180] Re: 1910 software-properties larger screen size

[Matthew Paul Thomas]

Barabazon, thanks for this report.

This bug would have been avoided by my design from 2016 that combines
the “Ubuntu Software”, “Other Software”, and “Authentication” tabs into
a single “Channels” tab.


As a short-term fix, perhaps the Russian translators could reduce the
problem by using shorter strings for the tab labels. For ample,
“Программное обеспечение Ubuntu” could be just “Ubuntu”, and
“Дополнительные драйверы” could be just “Драйверы”.

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

Title:
  1910 software-properties larger screen size

Status in software-properties package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  Screen size 1366x768, Russian language.

  Update settings go beyond the edge of the screen. The window cannot be
  reduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1846180/+subscriptions

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

[Touch-packages] [Bug 1845909] Re: IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

[Zhang Youfu]

After upgraded to Ubuntu 19.10 with systemd 242-6ubuntu1, the issue I
encountered disappeared.

```
# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eno1:  mtu 1500 qdisc fq_codel state UP group default 
qlen 1000
link/ether 94:c6:91:18:8c:3c brd ff:ff:ff:ff:ff:ff
inet 192.168.50.249/24 brd 192.168.50.255 scope global eno1
   valid_lft forever preferred_lft forever
3: wlp58s0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
link/ether 40:a3:cc:22:45:25 brd ff:ff:ff:ff:ff:ff
4: pppoe@eno1:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether 94:c6:91:18:8c:3c brd ff:ff:ff:ff:ff:ff
```

Now pppoe interface does not get IPv6 link-local address.

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

Title:
  IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

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

Bug description:
  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

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

[Touch-packages] [Bug 1827328] Re: ModemManager does not honor blacklisted ttys (ID_MM_DEVICE_IGNORE)

[Launchpad Bug Tracker]

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

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

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

Title:
  ModemManager does not honor blacklisted ttys (ID_MM_DEVICE_IGNORE)

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 19.04 (and likely earlier) Modem Manager is installed with
  filter policy 'strict' as opposed to 'default', which actually makes
  Modem Manager _less_ strict regarding explicitly blacklisted ttys (see
  man modemmanager).

  This means that ttys, that are explicitly blacklisted from Modem
  Manager by using ENV{ID_MM_DEVICE_IGNORE}="1" in its udev rule is
  still opened and probed by Modem Manager although it should not.

  This is a common cause of problems and frustrations for people working
  with actual serial devices, e.g. within embedded development (e.g.
  Arduino and the like). See https://nick.zoic.org/art/failed-to-set-
  dtr-rts-systemd-modemmanager/ for an example.

  A proposed solution is to change the following line in: 
/lib/systemd/system/ModemManager.service
  from:
  ExecStart=/usr/sbin/ModemManager --filter-policy=strict
  to:
  ExecStart=/usr/sbin/ModemManager --filter-policy=paranoid

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: modemmanager 1.10.0-1 [modified: 
lib/systemd/system/ModemManager.service]
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 15:35:58 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-26 (340 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: modemmanager
  UpgradeStatus: Upgraded to disco on 2019-04-18 (13 days ago)

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

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

[Touch-packages] [Bug 1845909] Re: IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

[Zhang Youfu]

I'm running Ubuntu 19.04 with systemd 240-6ubuntu5.7

systemd-networkd configuration:
```
# eno1.network
[Match]
Name=eno1

[Link]
Multicast=no

[Network]
LinkLocalAddressing=no
Address=192.168.50.249/24
Gateway=192.168.50.1
DNS=192.168.50.1
VLAN=pppoe

# pppoe.netdev
[NetDev]
Name=pppoe
Kind=vlan

[VLAN]
Id=1006

# pppoe.network
[Match]
Name=pppoe

[Link]
Multicast=no
ARP=no

[Network]
LinkLocalAddressing=no
```

result:
```
# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eno1:  mtu 1500 qdisc fq_codel state UP group default 
qlen 1000
link/ether 94:c6:91:18:8c:3c brd ff:ff:ff:ff:ff:ff
inet 192.168.50.249/24 brd 192.168.50.255 scope global eno1
   valid_lft forever preferred_lft forever
3: wlp58s0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
link/ether 40:a3:cc:22:45:25 brd ff:ff:ff:ff:ff:ff
4: pppoe@eno1:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether 94:c6:91:18:8c:3c brd ff:ff:ff:ff:ff:ff
inet6 fe80::96c6:91ff:fe18:8c3c/64 scope link
   valid_lft forever preferred_lft forever
5: docker0:  mtu 1500 qdisc noqueue state 
DOWN group default
link/ether 02:42:3c:35:9c:76 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
   valid_lft forever preferred_lft forever
```

The pppoe interface still got an IPv6 link-local address.

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

Title:
  IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

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

Bug description:
  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

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