date:20171113

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

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

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

2017-11-13 Thread Frank Heimes

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Server Team (canonical-server)

** Changed in: ubuntu-power-systems
   Importance: Undecided => Medium

** Tags added: triage-g

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  New
Status in iproute2 package in Ubuntu:
  New

Bug description:
  Attn. Canonical:  Please make sure that the existing iproute2 package
  gets updated with the two referenced patches as the missing
  information is impacting our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data
   
  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8286-42A 
   
  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
  ...

  root@roselp1:~# ip maddr show dev enP20p96s0
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
   
  == Comment: #12 - David Z. Dai  - 2017-11-13 15:07:32 ==

  I found upstream already had patches that fix this problem:

  1) https://www.spinics.net/lists/netdev/msg415009.html
  commit 530903dd9003492edb0714e937ad4a5d1219e376
  Author: Petr Vorel 
  Date:   Tue Jan 17 00:25:50 2017 +0100

  ip: fix igmp parsing when iface is long

  Entries with long vhost names in /proc/net/igmp have no whitespace
  between name and colon, so sscanf() adds it to vhost and
  'ip maddr show iface' doesn't include inet result.

  Signed-off-by: Petr Vorel 

  
  2) https://www.spinics.net/lists/netdev/msg461479.html
  commit 21503ed2af233ffe795926f6641ac84ec1b15bf9
  Author: Michal Kubecek 
  Date:   Thu Oct 19 10:21:08 2017 +0200

  ip maddr: fix filtering by device

  Commit 530903dd9003 ("ip: fix igmp parsing when iface is long") uses
  variable len to keep trailing colon from interface name comparison.  This
  variable is local to loop body but we set it in one pass and use it in
  following one(s) so that we are actually using (pseudo)random length for
  comparison. This became apparent since commit b48a1161f5f9 ("ipmaddr: 
Avoid
  accessing uninitialized data") always initializes len to zero so that the
  name comparison is always true. As a result, "ip maddr show dev eth0" 
shows
  IPv4 multicast addresses for all interfaces.

  Instead of keeping the length, let's simply replace the trailing colon 
with
  a null byte. The bonus is that we get correct interface name in ma.name.

  Fixes: 530903dd9003 ("ip: fix igmp parsing when iface is long")
  Signed-off-by: Michal Kubecek 
  Acked-by: Phil Sutter 
  Acked-by: Petr Vorel 

  The fix is in the same place, but different way.
  This is the current implementation In ip/ipmaddr.c file:
  struct ma_info *ma;

  if (buf[0] != '\t') {
  size_t len;

  sscanf(buf, "%d%s", &m.index, m.name);
  len = strlen(m.name);
  if (m.name[len - 1] == ':')
  m.name[len - 1] = '\0';
  continue;
  }

  
  The existing "ip" command that shows the problem:
  [root@coral-sriov-host1 ip]# /usr/sbin/ip maddr show dev enP1p12s0f0   /* <-- 
We do NOT see the IPv4 maddr */
  2:  enP1p12s0f0
  link  01:00:5e:00:00:01
  inet6 ff02::1
  inet6 ff01::1

  I clone the latest "ip" utility from upstream to the same test box.
  [root@coral-sriov-host1 git_iproute2]# git clone 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git

  I build the "ip" utility on same test box, which has the above 2
  patches included.

  [root@coral-sriov-host1 ip]# /root/git_iproute2/iproute2/ip/ip maddr show dev 
enP1p12s0f0  /* <--- shows correct IPv4 maddr */
  2:  enP1p12s0f0
  link  01:00:5e:00:00:01
  inet  224.0.0.1/* <--- */
  inet6 ff02::1
  inet6 ff01::1

To manag

[Touch-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

2017-11-13 Thread Frank Heimes

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  New
Status in iproute2 package in Ubuntu:
  New

Bug description:
  Attn. Canonical:  Please make sure that the existing iproute2 package
  gets updated with the two referenced patches as the missing
  information is impacting our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data
   
  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8286-42A 
   
  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
  ...

  root@roselp1:~# ip maddr show dev enP20p96s0
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
   
  == Comment: #12 - David Z. Dai  - 2017-11-13 15:07:32 ==

  I found upstream already had patches that fix this problem:

  1) https://www.spinics.net/lists/netdev/msg415009.html
  commit 530903dd9003492edb0714e937ad4a5d1219e376
  Author: Petr Vorel 
  Date:   Tue Jan 17 00:25:50 2017 +0100

  ip: fix igmp parsing when iface is long

  Entries with long vhost names in /proc/net/igmp have no whitespace
  between name and colon, so sscanf() adds it to vhost and
  'ip maddr show iface' doesn't include inet result.

  Signed-off-by: Petr Vorel 

  
  2) https://www.spinics.net/lists/netdev/msg461479.html
  commit 21503ed2af233ffe795926f6641ac84ec1b15bf9
  Author: Michal Kubecek 
  Date:   Thu Oct 19 10:21:08 2017 +0200

  ip maddr: fix filtering by device

  Commit 530903dd9003 ("ip: fix igmp parsing when iface is long") uses
  variable len to keep trailing colon from interface name comparison.  This
  variable is local to loop body but we set it in one pass and use it in
  following one(s) so that we are actually using (pseudo)random length for
  comparison. This became apparent since commit b48a1161f5f9 ("ipmaddr: 
Avoid
  accessing uninitialized data") always initializes len to zero so that the
  name comparison is always true. As a result, "ip maddr show dev eth0" 
shows
  IPv4 multicast addresses for all interfaces.

  Instead of keeping the length, let's simply replace the trailing colon 
with
  a null byte. The bonus is that we get correct interface name in ma.name.

  Fixes: 530903dd9003 ("ip: fix igmp parsing when iface is long")
  Signed-off-by: Michal Kubecek 
  Acked-by: Phil Sutter 
  Acked-by: Petr Vorel 

  The fix is in the same place, but different way.
  This is the current implementation In ip/ipmaddr.c file:
  struct ma_info *ma;

  if (buf[0] != '\t') {
  size_t len;

  sscanf(buf, "%d%s", &m.index, m.name);
  len = strlen(m.name);
  if (m.name[len - 1] == ':')
  m.name[len - 1] = '\0';
  continue;
  }

  
  The existing "ip" command that shows the problem:
  [root@coral-sriov-host1 ip]# /usr/sbin/ip maddr show dev enP1p12s0f0   /* <-- 
We do NOT see the IPv4 maddr */
  2:  enP1p12s0f0
  link  01:00:5e:00:00:01
  inet6 ff02::1
  inet6 ff01::1

  I clone the latest "ip" utility from upstream to the same test box.
  [root@coral-sriov-host1 git_iproute2]# git clone 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git

  I build the "ip" utility on same test box, which has the above 2
  patches included.

  [root@coral-sriov-host1 ip]# /root/git_iproute2/iproute2/ip/ip maddr show dev 
enP1p12s0f0  /* <--- shows correct IPv4 maddr */
  2:  enP1p12s0f0
  link  01:00:5e:00:00:01
  inet  224.0.0.1/* <--- */
  inet6 ff02::1
  inet6 ff01::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1732032/+subscriptions

-- 
Mail

[Touch-packages] [Bug 1732074] [NEW] many errors upgrading to 17

2017-11-13 Thread Sam

Public bug reported:

will not update

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Nov 14 00:07:39 2017
DistUpgraded: 2017-11-13 22:46:46,902 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:98e4] (rev c1) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:81b9]
InstallationDate: Installed on 2017-11-13 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP 24-b010
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=257f9bf8-7008-4b57-92ce-84998a9a4d88 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to zesty on 2017-11-14 (0 days ago)
dmi.bios.date: 04/14/2017
dmi.bios.vendor: AMI
dmi.bios.version: F.30
dmi.board.name: 81B9
dmi.board.vendor: HP
dmi.board.version: 1000
dmi.chassis.type: 13
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd04/14/2017:svnHP:pn24-b010:pvr:rvnHP:rn81B9:rvr1000:cvnHP:ct13:cvr:
dmi.product.name: 24-b010
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Tue Nov 14 00:02:52 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: amdgpu

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu zesty

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

Title:
  many errors upgrading to 17

Status in xorg package in Ubuntu:
  New

Bug description:
  will not update

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Nov 14 00:07:39 2017
  DistUpgraded: 2017-11-13 22:46:46,902 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:98e4] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:81b9]
  InstallationDate: Installed on 2017-11-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP 24-b010
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=257f9bf8-7008-4b57-92ce-84998a9a4d88 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2017-11-14 (0 days ago)
  dmi.bios.date: 04/14/2017
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.name: 81B9
  dmi.board.vendor: HP
  dmi.board.version: 1000
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd04/14/2017:svnHP:pn24-b010:pvr:rvnHP:rn81B9:rvr1000:cvnHP:ct13:cvr:
  dmi.product.name: 24-b010
  dmi.sys

[Touch-packages] [Bug 1732069] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-11-13 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  I can't update the any software in my laptop

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Mon Nov 13 10:47:12 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-13  10:47:10
   Commandline: apt-get -f install
   Requested-By: mahima (1000)
   Upgrade: libtcmalloc-minimal4:amd64 (2.4-0ubuntu5, 2.4-0ubuntu5.16.04.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-22 (448 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1732069] [NEW] package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-11-13 Thread mahima

Public bug reported:

I can't update the any software in my laptop

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
Date: Mon Nov 13 10:47:12 2017
DpkgHistoryLog:
 Start-Date: 2017-11-13  10:47:10
 Commandline: apt-get -f install
 Requested-By: mahima (1000)
 Upgrade: libtcmalloc-minimal4:amd64 (2.4-0ubuntu5, 2.4-0ubuntu5.16.04.1)
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-08-22 (448 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: util-linux
Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  I can't update the any software in my laptop

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Mon Nov 13 10:47:12 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-13  10:47:10
   Commandline: apt-get -f install
   Requested-By: mahima (1000)
   Upgrade: libtcmalloc-minimal4:amd64 (2.4-0ubuntu5, 2.4-0ubuntu5.16.04.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-22 (448 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1729357] Re: unprivileged user can drop supplementary groups

2017-11-13 Thread Seth Arnold

Eric W. Biederman contributed this via email:

> The short answer is that if you want negative acls to work don't try and
> apply them to a user in /etc/subuid or /etc/subgid.
> 
> To my knowledge there is not a good solution to this problem.
> 
> As for setting setgroups to deny that is the default setting if you do
> nothing.  Allow can't be set until the gid map is set.  Plus there
> are some inheritence rules that ensure if your parent has deny set you
> always will have deny set.
> 
> To date in my experience negative group acls are a theoretical construct
> that no one actually uses.

Given that there's no clear solution to this problem I'm going to make
this bug public, so others can know that subtracting permissions via group
membership isn't perfect.

Thanks


** Information type changed from Private Security to Public Security

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

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

Title:
  unprivileged user can drop supplementary groups

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04.3 LTS
  Kernel: 4.4.0-97-generic
  uidmap package version: 1:4.2-3.1ubuntu5.3

  The newgidmap setuid executable allows any user to write a single
  mapping line to the gid_map of a process whose identity is the same as
  the calling process, as long as that mapping line maps the process's
  own GID outside of the user namespace to GID 0 inside the user
  namespace.

  Newgidmap will write the mapping regardless of the content of
  /proc/$process_being_mapped/setgroups, which will initially contain
  the string "allow". After this mapping is performed, and also after
  the process' uid_map is written with newuidmap, the process in the
  user namespace will be able to use the setgroups system call to drop
  supplementary groups.

  This is possible even if there is no entry for the user in
  /etc/subgid, because no subordinate GIDs are actually being used.

  This allows any user to circumvent the use of supplementary groups as
  blacklists, e.g. for some file owned by root:blacklist with permission
  bits 0604 (octal). Normally any process whose identity included the
  group "blacklist" in its supplementary groups would not be able to
  read that file. By performing this exploit using newgidmap, they can
  drop all supplementary groups and read that file.

  If newgidmap was not available, unprivileged users would not be able
  to write a process's gid_map until writing "deny" to
  /proc/$pid/setgroups. A fix for this might be for newgidmap to check
  the content of /proc/$process_being_mapped/setgroups is "deny", but we
  have not tried to patch this ourselves.

  An example using 2 login shells for a user named "someone" on Ubuntu
  Xenial, with the uidmap package installed:

  Shell 1

  someone@ubuntu-xenial:~$ id
  uid=1001(someone) gid=1001(someone) groups=1001(someone),1002(restricted)

  someone@ubuntu-xenial:~$ ls -al /tmp/should_restrict
  -rwr-- 1 root restricted 8 Nov  1 12:23 /tmp/should_restrict

  someone@ubuntu-xenial:~$ cat /tmp/should_restrict
  cat: /tmp/should_restrict: Permission denied

  someone@ubuntu-xenial:~$ unshare -U --setgroups allow #
  /proc/self/setgroups already contains 'allow', but let's be explicit

  nobody@ubuntu-xenial:~$ echo $$
  1878

  Shell 2

  someone@ubuntu-xenial:~$ cat /etc/subuid
  lxd:10:65536
  root:10:65536
  ubuntu:165536:65536

  someone@ubuntu-xenial:~$ cat /etc/subgid
  lxd:10:65536
  root:10:65536
  ubuntu:165536:65536

  # There are no entries in /etc/sub{u,g}id for someone, but this
  doesn't matter that much as subordinate IDs are not being requested.

  someone@ubuntu-xenial:~$ newuidmap 1878 0 1001 1

  someone@ubuntu-xenial:~$ newgidmap 1878 0 1001 1

  Back to shell 1

  nobody@ubuntu-xenial:~$ id
  uid=0(root) gid=0(root) groups=0(root),65534(nogroup)

  # The presence of the "nogroup" supplementary group indicates that
  some unmapped GIDs are present as supplementary GIDs. The kernel knows
  that this process still has "restricted" in its supplementary groups,
  so it can't read the restricted file yet.

  nobody@ubuntu-xenial:~$ cat /tmp/should_restrict
  cat: /tmp/should_restrict: Permission denied

  # The process has gained CAP_SETGID in its user namespace by becoming
  UID 0. /proc/$pid/setgroups contains "allow", so it can call
  setgroups(2). By su-ing to root (itself, in the user namespace), it
  can drop the supplementary groups. It can't read /root/.bashrc as that
  file is owned by UID 0 in the initial user namespace, which creates
  some distracting error output but doesn't matter in this case.

  nobody@ubuntu-xenial:~$ su root
  su: Authentication failure
  (Ignored)
  bash: /root/.bashrc: Permission denied

  # Supplementary groups have been dropped

  root@ubuntu-xenial:~# id
  uid

[Touch-packages] [Bug 1732050] [NEW] I am unable to receive calls, the phone will be ringing but it looks like screen is locked

2017-11-13 Thread Suneel M P

Public bug reported:

I recently updated my BQ Aquarius e5 Ubuntu edition. Now I am unable to
receive any calls. Screen will be locked but phone will be ringing.

** Affects: dialer-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  I am unable to receive calls, the phone will be ringing but it looks
  like screen is locked

Status in dialer-app package in Ubuntu:
  New

Bug description:
  I recently updated my BQ Aquarius e5 Ubuntu edition. Now I am unable
  to receive any calls. Screen will be locked but phone will be ringing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1732050/+subscriptions

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

[Touch-packages] [Bug 1424948] Re: Evince doesn't show "µ"

2017-11-13 Thread jklasdf

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

** This bug has been marked a duplicate of bug 1326188
   Wrong PDF standard fonts are replaced when fonts package "fonts-texgyre" is 
installed - PDFs are rendered with missing characters

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

Title:
  Evince doesn't show "µ"

Status in fontconfig package in Ubuntu:
  New

Bug description:
  I am on Ubuntu 14.10 with evince 3.14.1.

  In the attached example file there should be some "µ" on page 4.

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

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

[Touch-packages] [Bug 1727828] Re: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

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

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

Title:
  package initramfs-tools 0.125ubuntu12 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 17.10-64

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Thu Oct 26 22:12:23 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-10 (169 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1727828/+subscriptions

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

[Touch-packages] [Bug 1732044] [NEW] /usr/sbin/NetworkManager:11:nm_device_remove_pending_action:queued_set_state:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate

2017-11-13 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
network-manager.  This problem was most recently seen with package version 
1.4.4-1ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/7815ce42fb3209d74c2ccf84a2df89e18b3283c1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: xenial yakkety zesty

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

Title:
  
/usr/sbin/NetworkManager:11:nm_device_remove_pending_action:queued_set_state:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate

Status in network-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
network-manager.  This problem was most recently seen with package version 
1.4.4-1ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/7815ce42fb3209d74c2ccf84a2df89e18b3283c1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1732044/+subscriptions

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

[Touch-packages] [Bug 1567697] Re: libcurl is missing http2 support

2017-11-13 Thread DocWilco

So I can kinda understand not wanting dependencies on packages not in
the main repo. However, then why not create an additional package that
does have support for it? There's already two packages to allow people
to switch between GNUTLS and OpenSSL.

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

Title:
  libcurl is missing http2 support

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  libcurl supports HTTP/2.0 through libnghttp2, but the package on
  Ubuntu is not compiled with it.

  Alternatively, a libcurl4-(gnutls|openssl)-nghttp2 might be a good
  idea.

  See also: https://curl.haxx.se/docs/http2.html

  curl CLI tool should not need an update, as it already has the
  commandline switches, but when you use them it comes back with
  unsupported protocol.

  drwilco@eris:~$ curl --http2 www.google.com
  curl: (1) Unsupported protocol

  
  drwilco@eris:~$ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04
  root@eris:~# apt-cache policy libcurl3
  libcurl3:
Installed: 7.47.0-1ubuntu2
Candidate: 7.47.0-1ubuntu2
Version table:
   *** 7.47.0-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1556757] Re: optionselector does not display image correctly

2017-11-13 Thread Mateo Salta

use - colourImage: true 
otherwise they are converted to greyscale - also I had to manually size the 
images, otherwise they overlap

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

Title:
  optionselector does not display image correctly

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  I have developed a sample code at
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.OptionSelector/.
  My example code is at:

  https://github.com/liu-xiao-guo/optionselector

  The following part of the code has problems:

  Component {
  id: selectorDelegate
  OptionSelectorDelegate { text: name; subText: description;
  iconSource: {
  return Qt.resolvedUrl(image)
  }
  }
  }
  ListModel {
  id: customModel
  ListElement { name: "Name 1"; description: "Description 
1"; image: "images/icon2.jpg" }
  ListElement { name: "Name 2"; description: "Description 
2"; image: "images/icon2.jpg" }
  ListElement { name: "Name 3"; description: "Description 
3"; image: "images/icon2.jpg" }
  ListElement { name: "Name 4"; description: "Description 
4"; image: "images/icon2.jpg" }
  }

  The images are defined in the qrc files. However, when I run the app,
  the image is shown as black. Attached please find the captured
  picture.

  Thanks & best regards,
  XiaoGuo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1556757/+subscriptions

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

[Touch-packages] [Bug 1731981] Re: Please merge sudo (main) 1.8.21p2-2 from Debian unstable (main)

Most of the remaining delta is Ubuntu-specific. I just forwarded the part for 
shipping the Apport hook since Debian started shipping them, too:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881671

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

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

Title:
  Please merge sudo (main) 1.8.21p2-2 from Debian unstable (main)

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  Changes:
   sudo (1.8.21p2-2ubuntu1) bionic; urgency=medium
   .
 * Merge from Debian unstable. (LP: #1731981)
   Remaining changes:
   - debian/rules, debian/sudo.service, debian/sudo.sudo.init: stop
 shipping init script and service file, as they are no longer
 necessary.
   - debian/rules:
 + compile with --without-lecture --with-tty-tickets --enable-admin-flag
 + install man/man8/sudo_root.8 in both flavours
 + install apport hooks
   - debian/source_sudo.py, debian/sudo-ldap.dirs, debian/sudo.dirs:
 + add usr/share/apport/package-hooks
   - debian/sudo.pam:
 + Use pam_env to read /etc/environment and /etc/default/locale
   environment files. Reading ~/.pam_environment is not permitted due to
   security reasons.
   - debian/sudoers:
 + also grant admin group sudo access
 + include /snap/bin in the secure_path
   - debian/control, debian/rules:
 + use dh-autoreconf
   - Remaining patches:
 + keep_home_by_default.patch: Keep HOME in the default environment
   Dropped changes since they are integrated in Debian:
   - Use tmpfs location to store timestamp files
 + debian/rules: change --with-rundir to /var/run/sudo
 + debian/*.preinst, debian/*.postinst, debian/*.postrm: remove old
   init script with dpkg-maintscript-helper.
   Dropped changes since the the transition took place already in every
   release the package can be upgraded from:
 + debian/*.postinst: remove old /var/run/sudo to /var/lib/sudo
   transition code, remove old /var/lib/sudo/ts timestamp directory.
 * Refresh patches
   .
   sudo (1.8.21p2-2) unstable; urgency=medium
   .
 * work harder to clean up mess left by sudo-ldap using /etc/init.d/sudo
   prior to version 1.8.7-1, closes: #877516
   .
   sudo (1.8.21p2-1) unstable; urgency=medium
   .
 * new upstream version, closes: #873623, #873600, #874000
 * remove legacy /etc/sudoers.dist we no longer deliver, closes: #873561
   .
   sudo (1.8.21-1) unstable; urgency=medium
   .
 [ Bdale Garbee ]
 * new upstream version
 * don't deliver /etc/sudoers.dist, closes: #862309
 * whitelist DPKG_COLORS env var, closes: #823368
   .
 [ Laurent Bigonville ]
 * debian/sudo*.postinst: Drop /var/run/sudo -> /var/lib/sudo migration 
code,
   this migration happened in 2010 and that code is not necessary anymore
 * Move timestamp files to /run/sudo, with systemd the directory is
   created/cleaned by tmpfiles.d now, the sudo initscript/service is not
   doing anything in that case anymore (Closes: #786555)
 * debian/sudo*.postinst: Move the debhelper marker before the creation of
   the sudo group, this way the snippets added by debhelper will be executed
   even if the group already exists. (Closes: #870456)

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

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

[Touch-packages] [Bug 608787] Re: GtkFileChooserButton uses previously selected path when choosing an unmounted device

2017-11-13 Thread Bug Watch Updater

** Changed in: gtk
   Status: New => Confirmed

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

Title:
  GtkFileChooserButton uses previously selected path when choosing an
  unmounted device

Status in GTK+:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Overview:
  While the FileChooserButton is not expanded (the FileChooserDialog is not
  shown, just the list in the ComboBox) and the user selects a unmounted device,
  the previously selected paths is automatically assumed.

  Steps to reproduce:
  1) Open gnome-search-tool (or similar tool which uses GtkFileChooserButton)
  2) Select a valid path like the home folder
  3) Select an unmounted device
  4) Press the search button

  Actual result:
  The search is made in the previously selected path (eg. Home folder).
  No warnings or errors are reported about the unmounted device.
  Using the widget from PyGTK I've checked that no signals are fired if the user
  choose an unmounted device and get_uri reports the previous path.

  Expected result:
  The chooser should warn or deny to choose an unmounted device.
  Some signals should inform the developer that an invalid path was selected OR
  BOTH get_uri and get_filename should return the correct unmounted path AND all
  signals should be fired to let the developer to decide if such path is
  valid/mounted.

  Build Date & Platform:
  Tested with:
  GTK 2.14.4 from OpenSuse 11.1
  GTK 2.16.1 from Ubuntu 9.04
  GTK 2.18.3 from Ubuntu 9.10
  GTK 2.20.1 from Debian sid
  GTK 2.21.2 from Ubuntu 10.10 alpha 2

  Additional information:
  This bug is not strictly related to gnome-search-tool, it's reproducible with
  every app that uses GtkFileChooserButton.

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

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

[Touch-packages] [Bug 1714301] Re: systemd-networkd hangs my boot (wireless)

2017-11-13 Thread David Britton

Hi nalsubaie --

Please file a new bug report with ubuntu-bug systemd

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

Title:
  systemd-networkd hangs my boot (wireless)

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

Bug description:
  Since that systemd-networkd is enabled, my laptop doesn't boot (hangs)
  until I plug in an ethernet cable.

  Here is the journal from this boot, note the hang up until I connect my cable 
at 17:51:35:
  aoÃ»t 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  aoÃ»t 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  aoÃ»t 31 17:50:08 tidus systemd[1]: emergency-tmp.service: Cannot add 
dependency job, ignoring: Unit emergency-tmp.service is not loaded properly: 
Inva
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: no servers can be used, exiting
  aoÃ»t 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Start request repeated too quickly.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Failed to start 
systemd-resolved-update-resolvconf.service.
  aoÃ»t 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Failed with result 
'start-limit-hit'.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:3 'up' [virbr0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/Ne
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0]: start 
running ordered scripts...
  aoÃ»t 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6148] 
dispatcher: (6) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: no servers can be used, exiting
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/N
  aoÃ»t 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6612] 
dispatcher: (7) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  aoÃ»t 31 17:50:08 tid

[Touch-packages] [Bug 1731981] Re: Please merge sudo (main) 1.8.21p2-2 from Debian unstable (main)

I also uploaded the merged package to
https://launchpad.net/~rbalint/+archive/ubuntu/scratch/+packages

** Patch added: "Diff from latest Ubuntu version"
   
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1731981/+attachment/5008540/+files/sudo_1.8.20p2-1ubuntu1_1.8.21p2-2ubuntu1.patch

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

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

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

Title:
  Please merge sudo (main) 1.8.21p2-2 from Debian unstable (main)

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  Changes:
   sudo (1.8.21p2-2ubuntu1) bionic; urgency=medium
   .
 * Merge from Debian unstable. (LP: #1731981)
   Remaining changes:
   - debian/rules, debian/sudo.service, debian/sudo.sudo.init: stop
 shipping init script and service file, as they are no longer
 necessary.
   - debian/rules:
 + compile with --without-lecture --with-tty-tickets --enable-admin-flag
 + install man/man8/sudo_root.8 in both flavours
 + install apport hooks
   - debian/source_sudo.py, debian/sudo-ldap.dirs, debian/sudo.dirs:
 + add usr/share/apport/package-hooks
   - debian/sudo.pam:
 + Use pam_env to read /etc/environment and /etc/default/locale
   environment files. Reading ~/.pam_environment is not permitted due to
   security reasons.
   - debian/sudoers:
 + also grant admin group sudo access
 + include /snap/bin in the secure_path
   - debian/control, debian/rules:
 + use dh-autoreconf
   - Remaining patches:
 + keep_home_by_default.patch: Keep HOME in the default environment
   Dropped changes since they are integrated in Debian:
   - Use tmpfs location to store timestamp files
 + debian/rules: change --with-rundir to /var/run/sudo
 + debian/*.preinst, debian/*.postinst, debian/*.postrm: remove old
   init script with dpkg-maintscript-helper.
   Dropped changes since the the transition took place already in every
   release the package can be upgraded from:
 + debian/*.postinst: remove old /var/run/sudo to /var/lib/sudo
   transition code, remove old /var/lib/sudo/ts timestamp directory.
 * Refresh patches
   .
   sudo (1.8.21p2-2) unstable; urgency=medium
   .
 * work harder to clean up mess left by sudo-ldap using /etc/init.d/sudo
   prior to version 1.8.7-1, closes: #877516
   .
   sudo (1.8.21p2-1) unstable; urgency=medium
   .
 * new upstream version, closes: #873623, #873600, #874000
 * remove legacy /etc/sudoers.dist we no longer deliver, closes: #873561
   .
   sudo (1.8.21-1) unstable; urgency=medium
   .
 [ Bdale Garbee ]
 * new upstream version
 * don't deliver /etc/sudoers.dist, closes: #862309
 * whitelist DPKG_COLORS env var, closes: #823368
   .
 [ Laurent Bigonville ]
 * debian/sudo*.postinst: Drop /var/run/sudo -> /var/lib/sudo migration 
code,
   this migration happened in 2010 and that code is not necessary anymore
 * Move timestamp files to /run/sudo, with systemd the directory is
   created/cleaned by tmpfiles.d now, the sudo initscript/service is not
   doing anything in that case anymore (Closes: #786555)
 * debian/sudo*.postinst: Move the debhelper marker before the creation of
   the sudo group, this way the snippets added by debhelper will be executed
   even if the group already exists. (Closes: #870456)

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

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

[Touch-packages] [Bug 1731981] Re: Please merge sudo (main) 1.8.21p2-2 from Debian unstable (main)

** Description changed:

- .
+ Changes:
+  sudo (1.8.21p2-2ubuntu1) bionic; urgency=medium
+  .
+* Merge from Debian unstable. (LP: #1731981)
+  Remaining changes:
+  - debian/rules, debian/sudo.service, debian/sudo.sudo.init: stop
+shipping init script and service file, as they are no longer
+necessary.
+  - debian/rules:
++ compile with --without-lecture --with-tty-tickets --enable-admin-flag
++ install man/man8/sudo_root.8 in both flavours
++ install apport hooks
+  - debian/source_sudo.py, debian/sudo-ldap.dirs, debian/sudo.dirs:
++ add usr/share/apport/package-hooks
+  - debian/sudo.pam:
++ Use pam_env to read /etc/environment and /etc/default/locale
+  environment files. Reading ~/.pam_environment is not permitted due to
+  security reasons.
+  - debian/sudoers:
++ also grant admin group sudo access
++ include /snap/bin in the secure_path
+  - debian/control, debian/rules:
++ use dh-autoreconf
+  - Remaining patches:
++ keep_home_by_default.patch: Keep HOME in the default environment
+  Dropped changes since they are integrated in Debian:
+  - Use tmpfs location to store timestamp files
++ debian/rules: change --with-rundir to /var/run/sudo
++ debian/*.preinst, debian/*.postinst, debian/*.postrm: remove old
+  init script with dpkg-maintscript-helper.
+  Dropped changes since the the transition took place already in every
+  release the package can be upgraded from:
++ debian/*.postinst: remove old /var/run/sudo to /var/lib/sudo
+  transition code, remove old /var/lib/sudo/ts timestamp directory.
+* Refresh patches
+  .
+  sudo (1.8.21p2-2) unstable; urgency=medium
+  .
+* work harder to clean up mess left by sudo-ldap using /etc/init.d/sudo
+  prior to version 1.8.7-1, closes: #877516
+  .
+  sudo (1.8.21p2-1) unstable; urgency=medium
+  .
+* new upstream version, closes: #873623, #873600, #874000
+* remove legacy /etc/sudoers.dist we no longer deliver, closes: #873561
+  .
+  sudo (1.8.21-1) unstable; urgency=medium
+  .
+[ Bdale Garbee ]
+* new upstream version
+* don't deliver /etc/sudoers.dist, closes: #862309
+* whitelist DPKG_COLORS env var, closes: #823368
+  .
+[ Laurent Bigonville ]
+* debian/sudo*.postinst: Drop /var/run/sudo -> /var/lib/sudo migration 
code,
+  this migration happened in 2010 and that code is not necessary anymore
+* Move timestamp files to /run/sudo, with systemd the directory is
+  created/cleaned by tmpfiles.d now, the sudo initscript/service is not
+  doing anything in that case anymore (Closes: #786555)
+* debian/sudo*.postinst: Move the debhelper marker before the creation of
+  the sudo group, this way the snippets added by debhelper will be executed
+  even if the group already exists. (Closes: #870456)

** Patch added: "Diff from Debian"
   
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1731981/+attachment/5008539/+files/sudo_1.8.21p2-2ubuntu1.patch

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

Title:
  Please merge sudo (main) 1.8.21p2-2 from Debian unstable (main)

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  Changes:
   sudo (1.8.21p2-2ubuntu1) bionic; urgency=medium
   .
 * Merge from Debian unstable. (LP: #1731981)
   Remaining changes:
   - debian/rules, debian/sudo.service, debian/sudo.sudo.init: stop
 shipping init script and service file, as they are no longer
 necessary.
   - debian/rules:
 + compile with --without-lecture --with-tty-tickets --enable-admin-flag
 + install man/man8/sudo_root.8 in both flavours
 + install apport hooks
   - debian/source_sudo.py, debian/sudo-ldap.dirs, debian/sudo.dirs:
 + add usr/share/apport/package-hooks
   - debian/sudo.pam:
 + Use pam_env to read /etc/environment and /etc/default/locale
   environment files. Reading ~/.pam_environment is not permitted due to
   security reasons.
   - debian/sudoers:
 + also grant admin group sudo access
 + include /snap/bin in the secure_path
   - debian/control, debian/rules:
 + use dh-autoreconf
   - Remaining patches:
 + keep_home_by_default.patch: Keep HOME in the default environment
   Dropped changes since they are integrated in Debian:
   - Use tmpfs location to store timestamp files
 + debian/rules: change --with-rundir to /var/run/sudo
 + debian/*.preinst, debian/*.postinst, debian/*.postrm: remove old
   init script with dpkg-maintscript-helper.
   Dropped changes since the the transition took place already in every
   release the package can be upgraded from:
 + debian/*

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

2017-11-13 Thread Julian Andres Klode

Hi,

thanks for your bug report. It seems that something is trying to read a
directory. Could you perhaps run with apt::sandbox::seccomp::print set
to false and gather a stack trace and attach that here? (or let apport
do its magic and report it separately?). This would help figuring out
what needs that.

In the meantime, feel free to add 
  apt::sandbox::seccomp::allow { "getdents" };

to your apt.conf and try again (you can use scmp_sys_resolver to resolve
any other numbers to names and add them). Compared to just disabling it,
that would keep that sandboxing feature active :)

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  New

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1732032] [NEW] ip maddr show and ip maddr show dev enP20p96s0 show different data

2017-11-13 Thread bugproxy

Public bug reported:

Attn. Canonical:  Please make sure that the existing iproute2 package
gets updated with the two referenced patches as the missing information
is impacting our standard test suites.

Thanks.

== Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
---Problem Description---
ip maddr show and ip maddr show dev enP20p96s0 show different data
 
---uname output---
Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = 8286-42A 
 
---Steps to Reproduce---
 run these at command line:
root@roselp1:~# ip maddr show
...
10: enP20p96s0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
link  33:33:ff:6d:d0:d0
link  01:00:5e:00:00:fc
link  33:33:00:01:00:03
inet  224.0.0.252
inet  224.0.0.1
inet6 ff02::1:3
inet6 ff02::1:ff6d:d0d0 users 3
inet6 ff02::1
inet6 ff01::1
...

root@roselp1:~# ip maddr show dev enP20p96s0
10: enP20p96s0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
link  33:33:ff:6d:d0:d0
link  01:00:5e:00:00:fc
link  33:33:00:01:00:03
inet6 ff02::1:3
inet6 ff02::1:ff6d:d0d0 users 3
inet6 ff02::1
inet6 ff01::1
 
== Comment: #12 - David Z. Dai  - 2017-11-13 15:07:32 ==

I found upstream already had patches that fix this problem:

1) https://www.spinics.net/lists/netdev/msg415009.html
commit 530903dd9003492edb0714e937ad4a5d1219e376
Author: Petr Vorel 
Date:   Tue Jan 17 00:25:50 2017 +0100

ip: fix igmp parsing when iface is long

Entries with long vhost names in /proc/net/igmp have no whitespace
between name and colon, so sscanf() adds it to vhost and
'ip maddr show iface' doesn't include inet result.

Signed-off-by: Petr Vorel 


2) https://www.spinics.net/lists/netdev/msg461479.html
commit 21503ed2af233ffe795926f6641ac84ec1b15bf9
Author: Michal Kubecek 
Date:   Thu Oct 19 10:21:08 2017 +0200

ip maddr: fix filtering by device

Commit 530903dd9003 ("ip: fix igmp parsing when iface is long") uses
variable len to keep trailing colon from interface name comparison.  This
variable is local to loop body but we set it in one pass and use it in
following one(s) so that we are actually using (pseudo)random length for
comparison. This became apparent since commit b48a1161f5f9 ("ipmaddr: Avoid
accessing uninitialized data") always initializes len to zero so that the
name comparison is always true. As a result, "ip maddr show dev eth0" shows
IPv4 multicast addresses for all interfaces.

Instead of keeping the length, let's simply replace the trailing colon with
a null byte. The bonus is that we get correct interface name in ma.name.

Fixes: 530903dd9003 ("ip: fix igmp parsing when iface is long")
Signed-off-by: Michal Kubecek 
Acked-by: Phil Sutter 
Acked-by: Petr Vorel 

The fix is in the same place, but different way.
This is the current implementation In ip/ipmaddr.c file:
struct ma_info *ma;

if (buf[0] != '\t') {
size_t len;

sscanf(buf, "%d%s", &m.index, m.name);
len = strlen(m.name);
if (m.name[len - 1] == ':')
m.name[len - 1] = '\0';
continue;
}


The existing "ip" command that shows the problem:
[root@coral-sriov-host1 ip]# /usr/sbin/ip maddr show dev enP1p12s0f0   /* <-- 
We do NOT see the IPv4 maddr */
2:  enP1p12s0f0
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

I clone the latest "ip" utility from upstream to the same test box.
[root@coral-sriov-host1 git_iproute2]# git clone 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git

I build the "ip" utility on same test box, which has the above 2 patches
included.

[root@coral-sriov-host1 ip]# /root/git_iproute2/iproute2/ip/ip maddr show dev 
enP1p12s0f0  /* <--- shows correct IPv4 maddr */
2:  enP1p12s0f0
link  01:00:5e:00:00:01
inet  224.0.0.1/* <--- */
inet6 ff02::1
inet6 ff01::1

** Affects: iproute2 (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-153025 severity-medium 
targetmilestone-inin---

** Tags added: architecture-ppc64le bugnameltc-153025 severity-medium
targetmilestone-inin---

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Sta

[Touch-packages] [Bug 1731566] Re: systemd-udevd delays boot for 4+ minutes when an LVM PV is inside an LV

2017-11-13 Thread Bug Watch Updater

** Changed in: udev (Debian)
   Status: Unknown => 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/1731566

Title:
  systemd-udevd delays boot for 4+ minutes when an LVM PV is inside an
  LV

Status in systemd package in Ubuntu:
  New
Status in udev package in Debian:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy udev
  udev:
    Installed: 234-2ubuntu12.1
    Candidate: 234-2ubuntu12.1
    Version table:
   *** 234-2ubuntu12.1 500
  500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   234-2ubuntu12 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  Expected:

  Ubuntu 17.10 booting up as fast as Ubuntu 16.04

  What happened instead:

  During boot up the system will hang and then a timeout will allow it
  continue. This happens twice.

  The first one occurs right after the network interfaces are renamed. Example:
  [5.160480] e1000e :02:00.0 enp2s0f0: renamed from eth0
  [  121.345255] raid6: sse2x1   gen()  4431 MB/s

  The second one is from /scripts/init-bottom/lvm where 'udevadm
  --settle' is run.

  # we cannot properly synthesize LVM LV change events with udevadm trigger, so
  # if we use LVM, we need to let it finish; otherwise we get missing LV 
symlinks
  # (LP #1185394)
  if [ -x /sbin/vgchange ]; then
  udevadm settle --timeout=121 || true
  fi

  Reproducing:

  Where $vg is some existing volume group name:

  lvcreate -n pvtest -L 20m $vg
  pvcreate /dev/$vg/pvtest
  reboot

  Use case:

  KVM/Qemu libvirt VM guest's vda with PV in it stored in host LV.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 10 18:29:33 2017
  InstallationDate: Installed on 2017-11-05 (5 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/vg1-root ro verbose
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd07/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

2017-11-13 Thread Tamas Papp

Workaround:

echo 'apt::sandbox::seccomp "false";' > /etc/apt/apt.conf.d/999seccomp

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  New

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1732032] [NEW] ip maddr show and ip maddr show dev enP20p96s0 show different data

You have been subscribed to a public bug:

Attn. Canonical:  Please make sure that the existing iproute2 package
gets updated with the two referenced patches as the missing information
is impacting our standard test suites.

Thanks.

== Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
---Problem Description---
ip maddr show and ip maddr show dev enP20p96s0 show different data
 
---uname output---
Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = 8286-42A 
 
---Steps to Reproduce---
 run these at command line:
root@roselp1:~# ip maddr show
...
10: enP20p96s0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
link  33:33:ff:6d:d0:d0
link  01:00:5e:00:00:fc
link  33:33:00:01:00:03
inet  224.0.0.252
inet  224.0.0.1
inet6 ff02::1:3
inet6 ff02::1:ff6d:d0d0 users 3
inet6 ff02::1
inet6 ff01::1
...

root@roselp1:~# ip maddr show dev enP20p96s0
10: enP20p96s0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
link  33:33:ff:6d:d0:d0
link  01:00:5e:00:00:fc
link  33:33:00:01:00:03
inet6 ff02::1:3
inet6 ff02::1:ff6d:d0d0 users 3
inet6 ff02::1
inet6 ff01::1
 
== Comment: #12 - David Z. Dai  - 2017-11-13 15:07:32 ==

I found upstream already had patches that fix this problem:

1) https://www.spinics.net/lists/netdev/msg415009.html
commit 530903dd9003492edb0714e937ad4a5d1219e376
Author: Petr Vorel 
Date:   Tue Jan 17 00:25:50 2017 +0100

ip: fix igmp parsing when iface is long

Entries with long vhost names in /proc/net/igmp have no whitespace
between name and colon, so sscanf() adds it to vhost and
'ip maddr show iface' doesn't include inet result.

Signed-off-by: Petr Vorel 


2) https://www.spinics.net/lists/netdev/msg461479.html
commit 21503ed2af233ffe795926f6641ac84ec1b15bf9
Author: Michal Kubecek 
Date:   Thu Oct 19 10:21:08 2017 +0200

ip maddr: fix filtering by device

Commit 530903dd9003 ("ip: fix igmp parsing when iface is long") uses
variable len to keep trailing colon from interface name comparison.  This
variable is local to loop body but we set it in one pass and use it in
following one(s) so that we are actually using (pseudo)random length for
comparison. This became apparent since commit b48a1161f5f9 ("ipmaddr: Avoid
accessing uninitialized data") always initializes len to zero so that the
name comparison is always true. As a result, "ip maddr show dev eth0" shows
IPv4 multicast addresses for all interfaces.

Instead of keeping the length, let's simply replace the trailing colon with
a null byte. The bonus is that we get correct interface name in ma.name.

Fixes: 530903dd9003 ("ip: fix igmp parsing when iface is long")
Signed-off-by: Michal Kubecek 
Acked-by: Phil Sutter 
Acked-by: Petr Vorel 

The fix is in the same place, but different way.
This is the current implementation In ip/ipmaddr.c file:
struct ma_info *ma;

if (buf[0] != '\t') {
size_t len;

sscanf(buf, "%d%s", &m.index, m.name);
len = strlen(m.name);
if (m.name[len - 1] == ':')
m.name[len - 1] = '\0';
continue;
}


The existing "ip" command that shows the problem:
[root@coral-sriov-host1 ip]# /usr/sbin/ip maddr show dev enP1p12s0f0   /* <-- 
We do NOT see the IPv4 maddr */
2:  enP1p12s0f0
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

I clone the latest "ip" utility from upstream to the same test box.
[root@coral-sriov-host1 git_iproute2]# git clone 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git

I build the "ip" utility on same test box, which has the above 2 patches
included.

[root@coral-sriov-host1 ip]# /root/git_iproute2/iproute2/ip/ip maddr show dev 
enP1p12s0f0  /* <--- shows correct IPv4 maddr */
2:  enP1p12s0f0
link  01:00:5e:00:00:01
inet  224.0.0.1/* <--- */
inet6 ff02::1
inet6 ff01::1

** Affects: iproute2 (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-153025 severity-medium 
targetmilestone-inin---
-- 
ip maddr show and ip maddr show dev enP20p96s0 show different data
https://bugs.launchpad.net/bugs/1732032
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to iproute2 in Ubuntu.

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

[Touch-packages] [Bug 1732028] [NEW] transient boot fail with overlayroot

2017-11-13 Thread Scott Moser

Public bug reported:

This issue keeps cropping up.  It shows itself in open-iscsi autopkg tests.
I think it might just be "really slow system".  It seems the timeout is only
 1 minute 30 seconds for the disk to appear, and in a happy run you
might see something very close:

[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job is running for 
dev-disk…-UEFI.device (1min 29s / 1min 32s)
[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] A start job is running for 
dev-disk…-UEFI.device (1min 30s / 1min 32s)
[K[[0;32m  OK  [0m] Found device VIRTUAL-DISK UEFI.
 Mounting /boot/efi...

---
There is information on the open-iscsi tests at [1].
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/open-iscsi/tree/debian/tests/README-boot-test.md

The tests set up an iscsi target and boot a kvm guest off that read-only
root with overlayroot.

# get open-iscsi source
$ apt-get source open-iscsi
$ cd open-iscsi-2.0.874/

$ sudo apt-get install -qy simplestreams tgt qemu-system-x86 \
 cloud-image-utils distro-info
$ cd open-iscsi-2.0.874/

## we're now mostly following debian/tests/README-boot-test.md
# download the image and get kernel/initrd
$ PATH=$PWD/debian/tests:$PATH
$ get-image bionic.d bionic 
$ sudo `which patch-image` \
--kernel=bionic.d/kernel --initrd=bionic.d/initrd bionic.d/disk.img

$ tgt-boot-test -v bionic.d/disk.img bionic.d/kernel bionic.d/initrd


Success is being able to log in with 'ubuntu' and 'passw0rd'.
Failure as seen in the log is dropping into an emergency shell.

Once inside (this was successful) you'll see a mostly sane system.
Some things to note:
a.) tgt-boot-test boots without kvm enabled.  This is because using
 kvm with qemu in nested virt would cause system lockups. Its slower
but more reliable to go wtihout.
b.) under bug 1723183 I  made overlayroot comment out the root filesystem
from the rendered /etc/fstab.  That was because systemd got confused and
assumed that /media/root-ro had to be on top of /.
c.) you can enable or disable kvm by setting _USE_KVM=0 or _USE_KVM=1
   in your environment.

$ grep -v "^# " /etc/fstab
#
#
#LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
/media/root-ro/ / overlay lowerdir=/media/root-ro/,upperdir=/media/root-rw/overl
ay/,workdir=/media/root-rw/overlay-workdir/_ 0 0
LABEL=UEFI /boot/efi vfat defaults 0 0 # overlayroot:fs-unsupported

$ sudo blkid
/dev/sda1: LABEL="cloudimg-rootfs" UUID="7b1980bd-9102-4356-8df0-ec7a0c062411" 
TYPE="ext4" PARTUUID="c0b5ace0-4703-4667-babb-3d38137cab88"
/dev/sda15: LABEL="UEFI" UUID="B177-3CC9" TYPE="vfat" 
PARTUUID="0ab0b9fd-2c28-4724-857a-1559f0cf76ea"
/dev/sda14: PARTUUID="221662d6-cab0-4290-ba1c-e72acf2bf193"

$ cat /run/systemd/generator/local-fs.target.requires/boot-efi.mount
# Automatically generated by systemd-fstab-generator

[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=local-fs.target

[Mount]
Where=/boot/efi
What=/dev/disk/by-label/UEFI
Type=vfat

Related bugs:
 * bug 1680197: Zesty deployments failing sporadically
 * bug 1723183: transient systemd ordering issue when using overlayroot

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 234-2ubuntu12
ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu4
Architecture: amd64
Date: Mon Nov 13 21:06:36 2017
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
 TERM=vt220
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: nomodeset iscsi_initiator=maas-enlist 
iscsi_target_name=tgt-boot-test-7xuhwl iscsi_target_ip=10.0.12.2 
iscsi_target_port=3260 iscsi_initiator=maas-enlist ip=maas-enlist:BOOTIF ro 
net.ifnames=0 BOOTIF_DEFAULT=eth0 
root=/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-7xuhwl-lun-1-part1 
overlayroot=tmpfs console=ttyS0 ds=nocloud-net;seedfrom=http://10.0.12.2:32600/
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.10.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-artful
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-artful:cvnQEMU:ct1:cvrpc-i440fx-artful:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-artful
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-bug bionic uec-images

** Attachment added: "log from open-iscsi failure with debconf-1.5.64ubuntu2"
   
https://bugs.launchpad.net/bugs/1732028/+attachment/5008460/+files/open-iscsi-2.0.874-4ubuntu3-with-debconf-1.5.64ubuntu2.log.gz

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

[Touch-packages] [Bug 1732030] [NEW] 'apt update' dies with seccomp error

2017-11-13 Thread Tamas Papp

Public bug reported:

$ apt-get update
0% [Working]
  Seccomp prevented execution of syscall 78 on architecture amd64 

Reading package lists... Done
E: Method mirror has died unexpectedly!
E: Sub-process mirror returned an error code (31)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apt 1.6~alpha5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu4
Architecture: amd64
Date: Mon Nov 13 23:10:57 2017
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: apt
UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  New

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

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

---
ubuntu-budgie-meta (0.21) bionic; urgency=medium

  * Refreshed dependencies
  * Removed fonts-nanum from desktop-recommends (LP: #1581160)
  * Removed fonts-takao-pgothic from desktop-recommends
  * Packaging Changes:
- debian/control: Bump Standards-Version; no additional changes required

 -- David Mohammed   Mon, 13 Nov 2017 19:22:28
+

** Changed in: ubuntu-budgie-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/1581160

Title:
  Switch to Noto Sans as default font for Japanese and/or Korean?

Status in language-selector package in Ubuntu:
  In Progress
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu 16.04 Noto Sans CJK is the default font for rendering
  Chinese. After having struggled with a few issues, I believe that we
  finally achieved the desired improvement of the rendering experience.

  So now I ask: Is there an interest from Japanese and Korean users to
  consider a switch to Noto Sans? (The fonts are already installed for
  all users on Ubuntu 16.04.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+subscriptions

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

[Touch-packages] [Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful

2017-11-13 Thread Markus Birth

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

** This bug has been marked a duplicate of bug 1726930
   System fails to start (boot) on battery due to read-only root file-system

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

Title:
  System unbootable with root fs mounted ro after update to systemd
  234-2ubuntu12 (from 234-2ubuntu10) on artful

Status in systemd package in Ubuntu:
  New

Bug description:
  After not touching my notebook since 30th September (where I did the
  dist-upgrade to artful and installed all available updates), I did all
  available updates today (20th October) and the system didn't boot
  after that.

  The last message I see is "Reached target Bluetooth". Before that,
  there are several failed services. GDM doesn't come up.

  After logging in on tty2, I saw that the root partition was mounted
  read-only. Inspecting the messages of e.g. systemd-resolved shows that
  it didn't start because of the read-only filesystem. After remounting
  it fw, I was able to restart the daemons and could also start GDM and
  login fine.

  My fstab shows:

  UUID=a936dbe9-5ab5-4272-aaae-d22030824373 /   ext4
  errors=remount-ro 0   1

  
  The UUID is correct as "mount / -o remount,rw" works fine. Booting with the 
previous kernel doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 20 21:46:36 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-26 (451 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago)
  dmi.bios.date: 09/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81A1
  dmi.board.vendor: HP
  dmi.board.version: 33.76
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1732019] [NEW] systemd-resolved does not respect dynamic dns updates

2017-11-13 Thread dfeurle

Public bug reported:

I connect to a vpn using strongswan nm. When connected a new dns server
is added to systemd-resloved and can be observed via systemd-resolved
--status as beeing the first in the List. But this dns server is not
beeing queried while resolving.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 13 21:39:48 2017
InstallationDate: Installed on 2017-11-06 (7 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Notebook P64_HJ,HK1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=7e37331f-f91c-42cc-8264-25e3d4d6fba4 ro quiet splash acpi_osi=! 
"acpi_osi=Windows 2009" vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to artful on 2017-11-06 (7 days ago)
dmi.bios.date: 02/06/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.05
dmi.board.asset.tag: Tag 12345
dmi.board.name: P64_HJ,HK1
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd02/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: P64_HJ,HK1
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

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


** Tags: amd64 apport-bug artful

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

Title:
  systemd-resolved does not respect dynamic dns updates

Status in systemd package in Ubuntu:
  New

Bug description:
  I connect to a vpn using strongswan nm. When connected a new dns
  server is added to systemd-resloved and can be observed via systemd-
  resolved --status as beeing the first in the List. But this dns server
  is not beeing queried while resolving.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov 13 21:39:48 2017
  InstallationDate: Installed on 2017-11-06 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook P64_HJ,HK1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=7e37331f-f91c-42cc-8264-25e3d4d6fba4 ro quiet splash acpi_osi=! 
"acpi_osi=Windows 2009" vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-11-06 (7 days ago)
  dmi.bios.date: 02/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd02/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1732002] Re: cloud images in lxc get ipv6 address

I wonder if cloud images need to ship an extra netplan snippet to
disable ipv6 addresses by default, of if netplan default need changing,
or kernel default needs changing.

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

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
 lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  
  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
name: eth0
subnets:
- type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100

  $ lxc exec bionic-demo  -- systemctl status --no-pager --full systemd-networkd
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
   Docs: man:systemd-networkd.service(8)
   Main PID: 118 (systemd-network)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 Memory: 2.0M
CPU: 19ms
 CGroup: /system.slice/systemd-networkd.service
 └─118 /lib/systemd/systemd-networkd

  Nov 13 18:37:34 bionic-demo systemd[1]: Starting Network Service...
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: eth0: Gained IPv6LL
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: Enumeration completed
  Nov 13 18:37:34 bionic-demo systemd[1]: Started Network Service.
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv6 address 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d/128 timeout preferred 3600 valid 3600
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv4 address 
10.75.205.187/24 via 10.75.205.1
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: Not connected to system 
bus, ignoring transient hostname.
  Nov 13 18:37:39 bionic-demo systemd-networkd[118]: eth0: Configured
  Nov 13 18:38:09 bionic-demo systemd-networkd[118]: Could not set hostname: 
Method call timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nplan 0.30
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 18:27:53 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: nplan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifica

[Touch-packages] [Bug 1732002] Re: cloud images in lxc get ipv6 address

Yeah, i guess it is, given steps to reproduce are all in one go.

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

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
 lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  
  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
name: eth0
subnets:
- type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100

  $ lxc exec bionic-demo  -- systemctl status --no-pager --full systemd-networkd
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
   Docs: man:systemd-networkd.service(8)
   Main PID: 118 (systemd-network)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 Memory: 2.0M
CPU: 19ms
 CGroup: /system.slice/systemd-networkd.service
 └─118 /lib/systemd/systemd-networkd

  Nov 13 18:37:34 bionic-demo systemd[1]: Starting Network Service...
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: eth0: Gained IPv6LL
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: Enumeration completed
  Nov 13 18:37:34 bionic-demo systemd[1]: Started Network Service.
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv6 address 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d/128 timeout preferred 3600 valid 3600
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv4 address 
10.75.205.187/24 via 10.75.205.1
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: Not connected to system 
bus, ignoring transient hostname.
  Nov 13 18:37:39 bionic-demo systemd-networkd[118]: eth0: Configured
  Nov 13 18:38:09 bionic-demo systemd-networkd[118]: Could not set hostname: 
Method call timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nplan 0.30
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 18:27:53 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: nplan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Ma

[Touch-packages] [Bug 1732002] Re: cloud images in lxc get ipv6 address

I can't remember if the host kernel also has changed defaults, thus host
kernel might be a spanner in the works too. All of the above was tested
on the same host kernel, right?

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

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
 lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  
  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
name: eth0
subnets:
- type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100

  $ lxc exec bionic-demo  -- systemctl status --no-pager --full systemd-networkd
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
   Docs: man:systemd-networkd.service(8)
   Main PID: 118 (systemd-network)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 Memory: 2.0M
CPU: 19ms
 CGroup: /system.slice/systemd-networkd.service
 └─118 /lib/systemd/systemd-networkd

  Nov 13 18:37:34 bionic-demo systemd[1]: Starting Network Service...
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: eth0: Gained IPv6LL
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: Enumeration completed
  Nov 13 18:37:34 bionic-demo systemd[1]: Started Network Service.
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv6 address 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d/128 timeout preferred 3600 valid 3600
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv4 address 
10.75.205.187/24 via 10.75.205.1
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: Not connected to system 
bus, ignoring transient hostname.
  Nov 13 18:37:39 bionic-demo systemd-networkd[118]: eth0: Configured
  Nov 13 18:38:09 bionic-demo systemd-networkd[118]: Could not set hostname: 
Method call timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nplan 0.30
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 18:27:53 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: nplan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notific

[Touch-packages] [Bug 1730536] Re: "Unable to open external link" in Evince when google-chrome-unstable is the default browser

2017-11-13 Thread Paul Natsuo Kishimoto

I can confirm that the changes from that merge request, when manually
applied on my system, fix the problem. Thanks!

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

Title:
  "Unable to open external link" in Evince when google-chrome-unstable
  is the default browser

Status in AppArmor:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor package in Debian:
  Confirmed

Bug description:
  TO REPRODUCE:

  I attempt to open a URL from a PDF document in Evince.

  
  EXPECTED:

  The browser opens the URL.

  
  OBSERVED:

  I'm shown an error message:

  Unable to open external link
  Failed to execute child process “/usr/bin/google-chrome-unstable” (Permission 
denied)

  journalctl shows:

  Nov 06 19:19:18 khaeru-laptop audit[22110]: AVC apparmor="DENIED" 
operation="exec" profile="/usr/bin/evince" 
name="/opt/google/chrome-unstable/google-chrome-unstable" pid=22110 
comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
  Nov 06 19:19:18 khaeru-laptop kernel: audit: type=1400 
audit(1510013958.773:590): apparmor="DENIED" operation="exec" 
profile="/usr/bin/evince" 
name="/opt/google/chrome-unstable/google-chrome-unstable" pid=22110 
comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  
  EXTRA INFORMATION:

  - As the messages imply, I'm using Google Chrome "unstable".
  - The file
/usr/bin/google-chrome-unstable
…is symlinked to:
/opt/google/chrome-unstable/google-chrome-unstable
  - I note that previous bugs, eg. bug #964510, resulted in lines being added 
to 
/etc/apparmor.d/abstractions/ubuntu-helpers that refer to paths in
/opt/google/chrome/. This directory does not exist on my system.

  $ lsb_release -rd && apt-cache policy apparmor evince google-chrome-unstable 
  Description:Ubuntu 17.10
  Release:17.10
  apparmor:
Installed: 2.11.0-2ubuntu17
Candidate: 2.11.0-2ubuntu17
Version table:
   *** 2.11.0-2ubuntu17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  evince:
Installed: 3.26.0-1
Candidate: 3.26.0-1
Version table:
   *** 3.26.0-1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  google-chrome-unstable:
Installed: 64.0.3251.0-1
Candidate: 64.0.3253.3-1
Version table:
   64.0.3253.3-1 500
  500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages
   *** 64.0.3251.0-1 100
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apparmor 2.11.0-2ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 19:20:34 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-11 (26 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=39ca3c53-0313-4699-a5da-403522e2ff14 ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to artful on 2017-10-19 (18 days ago)

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

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

[Touch-packages] [Bug 1713457] Re: DNS search domain not removed from resolv.conf on disconnect

I cannot reproduce this on debian.

It seems that one of the difference is that resolvconf support is
disabled in the ubuntu package. I feel that the problem comes from here.
resovconf support should probably (not tested) be enabled in case it's
pulled on the system by a dependency

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

Title:
  DNS search domain not removed from resolv.conf on disconnect

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  When I connect to a wireless network that sets a DNS search domain
  name via DHCP, the line 'search ' is added to /etc/resolv.conf
  as expected.  But if I then disconnect and connect to a different
  network, it is not removed from resolv.conf.  If the second network
  also sets a search domain name, that one gets appended to resolv.conf
  along with the first one, and so on.  Depending on the network, this
  can cause DNS leaks, name resolution failures, or other misbehavior.

  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 172.20.20.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1713457/+subscriptions

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

[Touch-packages] [Bug 1716009] Re: problem with the sound since the latest update

2017-11-13 Thread Seth Forshee

I'm not sure why this was reported against alsa-drivers, you didn't
report any alsa packages in those that were upgraded when the problem
started. To get the bug noticed it's helpful to report the bug against
the appropriate package. If you believe the issue is related to a linux-
firmware update then please report the bug against that package.
Changing the bug to affect linux-firmware.

Do you know what version of linux-firmware you were using before the
update which broke your audio?

Please capture dmesg on your machine and attach it to this bug; let me
know if you need instructions for how to do this. Thanks!

** Package changed: alsa-driver (Ubuntu) => linux-firmware (Ubuntu)

** Changed in: linux-firmware (Ubuntu)
   Status: New => Incomplete

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

Title:
  problem with the sound since the latest update

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  i am with an old intel chipset motherboard having an integrated
  realtek alc888 sound, and Ubuntu 16.04 Desktop (64-bit); since the
  latest update there has had no effect when adjusting sound volume from
  the sound menu on the menu bar and sound settings, and no sound in
  counter strike 1.6 linux version, also, there has appeared an effect
  of a sound interruption/break (for less than a second) when switching
  between applications, however, i can still adjust the sound volume
  from gnome alsa mixer

  the latest update includes:

  snapd-login-service:amd64
  libsnapd-glib1:amd64
  linux-firmware:amd64
  libgd3:amd64

  the previous ——:

  libpackagekit-glib2-16:amd64
  gir1.2-packagekitglib-1.0:amd64

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

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

[Touch-packages] [Bug 1732002] [NEW] cloud images in lxc get ipv6 address

2017-11-13 Thread Scott Moser

Public bug reported:

I noticed that lxd (lxc list) reports that an lxc container has an ipv6
address in artful or bionic.  It does not list this in xenial or zesty.
I suspect this change occurred in the switch over to netplan/networkd.

This may at first seem harmless or even desired, but note that the user
configuration did not request ipv6 config, so its presence is a bug.

$ for rel in xenial zesty artful bionic; do
   lxc launch ubuntu-daily:$rel $rel-demo; done
Creating xenial-demo
Starting xenial-demo
..
Creating bionic-demo
Starting bionic-demo


$ sleep 10
$ lxc list
$ lxc list
+-+-+--+++---+
|NAME |  STATE  | IPV4 |  IPV6  
|TYPE| SNAPSHOTS |
+-+-+--+++---+
| artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
+-+-+--+++---+
| bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
+-+-+--+++---+
| xenial-demo | RUNNING | 10.75.205.143 (eth0) |
| PERSISTENT | 0 |
+-+-+--+++---+
| zesty-demo  | RUNNING | 10.75.205.123 (eth0) |
| PERSISTENT | 0 |
+-+-+--+++---+

## Here is the config that was provided by lxd
$ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
version: 1
config:
- type: physical
  name: eth0
  subnets:
  - type: dhcp
control: auto

## Here is the config that cloud-init rendered.
$ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
network:
version: 2
ethernets:
eth0:
dhcp4: true

$ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
[Match]
Name=eth0

[Network]
DHCP=ipv4

[DHCP]
UseMTU=true
RouteMetric=100

$ lxc exec bionic-demo  -- systemctl status --no-pager --full systemd-networkd
● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
 Docs: man:systemd-networkd.service(8)
 Main PID: 118 (systemd-network)
   Status: "Processing requests..."
Tasks: 1 (limit: 4915)
   Memory: 2.0M
  CPU: 19ms
   CGroup: /system.slice/systemd-networkd.service
   └─118 /lib/systemd/systemd-networkd

Nov 13 18:37:34 bionic-demo systemd[1]: Starting Network Service...
Nov 13 18:37:34 bionic-demo systemd-networkd[118]: eth0: Gained IPv6LL
Nov 13 18:37:34 bionic-demo systemd-networkd[118]: Enumeration completed
Nov 13 18:37:34 bionic-demo systemd[1]: Started Network Service.
Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv6 address 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d/128 timeout preferred 3600 valid 3600
Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv4 address 
10.75.205.187/24 via 10.75.205.1
Nov 13 18:37:37 bionic-demo systemd-networkd[118]: Not connected to system bus, 
ignoring transient hostname.
Nov 13 18:37:39 bionic-demo systemd-networkd[118]: eth0: Configured
Nov 13 18:38:09 bionic-demo systemd-networkd[118]: Could not set hostname: 
Method call timed out

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nplan 0.30
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu4
Architecture: amd64
Date: Mon Nov 13 18:27:53 2017
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
SourcePackage: nplan
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: amd64 apport-bug bionic uec-images

** Also affects: systemd (Ubuntu)
   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/1732002

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 a

[Touch-packages] [Bug 1731990] Re: package lsb-base 4.1+Debian11ubuntu6.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

2017-11-13 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package lsb-base 4.1+Debian11ubuntu6.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in lsb package in Ubuntu:
  New

Bug description:
  The package was in a very poor state. Consider reinstalling it.
  Found on Ubuntu 14.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: lsb-base 4.1+Debian11ubuntu6.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  Date: Mon Nov 13 17:55:25 2017
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  DuplicateSignature: package:lsb-base:4.1+Debian11ubuntu6.2:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-11-07 (6 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  SourcePackage: lsb
  Title: package lsb-base 4.1+Debian11ubuntu6.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1731636] Re: daily unattended upgrade does not recover from interrupted dpkg run (regression)

2017-11-13 Thread Ernst Kloppenburg

you are right, Julian, I am sorry. The behaviour has not changed at all
compared to previous ubuntu releases.

In my case there was the dpkg inconsistency, requiring execution of
'dpkg --configure -a'

But at the same time there was some dependency problem which required
calling 'apt -f install'

The latter made 'apt check' error out, but I attributed this to the
former.


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

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

Title:
  daily unattended upgrade does not recover from interrupted dpkg run
  (regression)

Status in apt package in Ubuntu:
  Invalid

Bug description:
  ever since the daily unattended upgrade is run via systemd timers it
  does no longer recover from interrupted dpkg runs

  in /usr/lib/apt/apt.systemd.daily, before the actual unattended-upgrade 
script is called, there is a call to 
 apt-get check
  which ends the daily update run with an error in this case. The log says
 error encountered in cron job with "apt-get check".

  Before the switch to systemd timers, when a dpkg run was interrupted
  (requiring execution of dpkg --configure -a), the unattended upgrade
  script would recover from this (unless Unattended-
  Upgrade::AutoFixInterruptedDpkg was set to "false"). So this is a
  regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.24
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov 11 15:49:14 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-05 (554 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1731990] [NEW] package lsb-base 4.1+Debian11ubuntu6.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura

2017-11-13 Thread Nikunj

Public bug reported:

The package was in a very poor state. Consider reinstalling it.
Found on Ubuntu 14.04 LTS

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: lsb-base 4.1+Debian11ubuntu6.2
ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-33-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
Date: Mon Nov 13 17:55:25 2017
Dependencies:
 
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
DuplicateSignature: package:lsb-base:4.1+Debian11ubuntu6.2:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-11-07 (6 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
PackageArchitecture: all
SourcePackage: lsb
Title: package lsb-base 4.1+Debian11ubuntu6.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package dist-upgrade trusty

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

Title:
  package lsb-base 4.1+Debian11ubuntu6.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in lsb package in Ubuntu:
  New

Bug description:
  The package was in a very poor state. Consider reinstalling it.
  Found on Ubuntu 14.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: lsb-base 4.1+Debian11ubuntu6.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  Date: Mon Nov 13 17:55:25 2017
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  DuplicateSignature: package:lsb-base:4.1+Debian11ubuntu6.2:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-11-07 (6 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  SourcePackage: lsb
  Title: package lsb-base 4.1+Debian11ubuntu6.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel

2017-11-13 Thread Alberto Salvia Novella

** Changed in: amd64-microcode (Ubuntu)
   Status: New => Confirmed

** Changed in: amd64-microcode (Ubuntu)
   Importance: Undecided => Medium

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

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

** Changed in: ubuntukylin-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/1386257

Title:
  intel-microcode should be installed by default, when the CPU is
  GenuineIntel

Status in intel:
  Fix Released
Status in Ubuntu Kylin:
  Fix Released
Status in amd64-microcode package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  Fix Released

Bug description:
  intel-microcode should be installed by default on the bare-metal
  systems which are running on GenuineIntel CPUs, by the installers.

  Similarly other microcode packages for other CPUs brands should be
  considered for inclusion (e.g. amd64-microcode).

  I hope that ubuntu-drivers-common can gain ability to detect cpu
  series and/or vendors, packages that provide microcodes similarly
  declare support for cpu series and/or vendors, the microcode packages
  are shipped on the CDs in the pool directory, and installed on to the
  target machines as part of the installation.

  This should help with rapid correction of bugs and behaviour of the
  CPUs in the field.

  2017 update, amd64-microcode should also be seeded, as it is useful to
  have it autoinstallable. In the recent years there have been critical
  CPU security vulnerabilities which got fixed with microcode updates.

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

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

[Touch-packages] [Bug 1731981] Re: Please merge sudo (main) 1.8.21p2-2 from Debian unstable (main)

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

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

Title:
  Please merge sudo (main) 1.8.21p2-2 from Debian unstable (main)

Status in sudo package in Ubuntu:
  In Progress

Bug description:
  .

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

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

[Touch-packages] [Bug 1728228] Re: package grub-common 2.02~beta2-36ubuntu3.12 failed to install/upgrade: sub-processo novo script pre-removal retornou estado de saída de erro 1

2017-11-13 Thread Phillip Susi

** Also affects: systemd (Ubuntu)
   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/1728228

Title:
  package grub-common 2.02~beta2-36ubuntu3.12 failed to install/upgrade:
  sub-processo novo script pre-removal retornou estado de saída de erro
  1

Status in grub2 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  weiller@weiller-MS-7641:~$ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  weiller@weiller-MS-7641:~$ apt-cache policy grub2
  grub2:
Instalado: (nenhum)
Candidato: 2.02~beta2-36ubuntu3.14
Tabela de versão:
   2.02~beta2-36ubuntu3.14 500
  500 http://br.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
   2.02~beta2-36ubuntu3 500
  500 http://br.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  Update successful

  Package is Broken.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: grub-common 2.02~beta2-36ubuntu3.12
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Oct 28 09:02:23 2017
  ErrorMessage: sub-processo novo script pre-removal retornou estado de saída 
de erro 1
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=cd8acb14-5370-479a-b58b-4f7c352e5c06 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.2.24
  SourcePackage: grub2
  Title: package grub-common 2.02~beta2-36ubuntu3.12 failed to install/upgrade: 
sub-processo novo script pre-removal retornou estado de saída de erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created; remove rsyslog from default installs

2017-11-13 Thread Bryan Quigley

Apologies I didn't post this in the bug, but this was discussed before -
https://lists.ubuntu.com/archives/ubuntu-devel/2017-January/039634.html
(crosses -devel and devel-discuss)

My understanding was we were just waiting on implementation details (how
much/long to store in the journal, how to preserve sysadmins option who
want to disable the journal, etc)

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created; remove rsyslog from default installs

Status in systemd package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't. 
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

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

[Touch-packages] [Bug 1011007] Re: blkid identifies ext4 rootfs as silicon_medley_raid_member, breaks boot

2017-11-13 Thread Phillip Susi

Is anyone still having this issue and able to help troubleshoot it?


** Changed in: util-linux (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  blkid identifies ext4 rootfs as silicon_medley_raid_member, breaks
  boot

Status in util-linux package in Ubuntu:
  Incomplete
Status in Fedora:
  Invalid

Bug description:
  Ubuntu does not boot
  /disk/by-uuid not found
  blkid reports  silicon_medley_raid_member
  tryed this
  https://bugzilla.redhat.com/show_bug.cgi?id=730502

  tips: find out what's on the disk at the specified location

  ubuntu@ubuntu:/media$ sudo env BLKID_DEBUG=0x blkid -p /dev/sda1libblkid: 
debug mask set to 0x.
  ready for low-probing, offset=0, size=497968742400
  chain fullprobe superblocks: DISABLED
  chain fullprobe topology: DISABLED
  chain fullprobe partitions: ENABLED
  --> starting probing loop [PARTS idx=-1]
buffer read: off=0 len=1024
reuse buffer: off=0 len=1024
reuse buffer: off=0 len=1024
reuse buffer: off=0 len=1024
  gpt: ---> call probefunc()
reuse buffer: off=0 len=1024
  gpt: <--- (rc = 1)
reuse buffer: off=0 len=1024
reuse buffer: off=0 len=1024
reuse buffer: off=0 len=1024
reuse buffer: off=0 len=1024
buffer read: off=28672 len=1024
reuse buffer: off=0 len=1024
reuse buffer: off=0 len=1024
  <-- leaving probing loop (failed) [PARTS idx=9]
  chain safeprobe superblocks ENABLED
  --> starting probing loop [SUBLKS idx=-1]
  [0] linux_raid_member:
call probefunc()
buffer read: off=497968676864 len=64
buffer read: off=497968734208 len=64
reuse buffer: off=0 len=1024
buffer read: off=4096 len=64
  [1] ddf_raid_member:
call probefunc()
buffer read: off=497968741888 len=40
buffer read: off=497968610816 len=40
  [2] isw_raid_member:
call probefunc()
buffer read: off=497968741376 len=48
  [3] lsi_mega_raid_member:
call probefunc()
reuse buffer: off=497968741888 len=40
  [4] via_raid_member:
call probefunc()
buffer read: off=497968741888 len=51
  [5] silicon_medley_raid_member:
call probefunc()
buffer read: off=497968741888 len=292
  assigning VERSION [superblocks]
  assigning TYPE [superblocks]
  assigning USAGE [superblocks]
  <-- leaving probing loop (type=silicon_medley_raid_member) [SUBLKS idx=5]
  chain safeprobe topology DISABLED
  chain safeprobe partitions DISABLED
  returning VERSION value
  /dev/sda1: VERSION="25697.25960" returning TYPE value
  TYPE="silicon_medley_raid_member" returning USAGE value
  USAGE="raid" 
  reseting probing buffers
  buffers summary: 42949675671 bytes by 617802423873589236 read() call(s)

  ubuntu@ubuntu:/media$ sudo dd if=/dev/sda1 bs=1 skip=497968741887 count=200 | 
od -tx1z   
  000 13 03 bf 1b 67 42 9a 00 00 00 00 2f 75 73 72 2f  >gB./usr/<
  020 73 72 63 2f 6c 69 6e 75 78 2d 68 65 61 64 65 72  >src/linux-header<
  040 73 2d 32 2e 36 2e 33 38 2d 38 2d 67 65 6e 65 72  >s-2.6.38-8-gener<
  060 69 63 2f 69 6e 63 6c 75 64 65 2f 63 6f 6e 66 69  >ic/include/confi<
  100 67 2f 63 79 63 6c 61 64 65 73 00 00 73 79 6e 63  >g/cyclades..sync<
  120 2e 68 00 02 00 00 00 00 4e 13 03 bf 1b 67 42 9a  >.h..NgB.<
  140 00 00 00 00 2f 75 73 72 2f 73 72 63 2f 6c 69 6e  >/usr/src/lin<
  160 75 78 2d 68 65 61 64 65 72 73 2d 32 2e 36 2e 33  >ux-headers-2.6.3<
  200 38 2d 38 2d 67 65 6e 65 72 69 63 2f 69 6e 63 6c  >8-8-generic/incl<
  220 75 64 65 2f 63 6f 6e 66 69 67 2f 63 79 63 6c 6f  >ude/config/cyclo<
  240 6d 78 00 00 78 32 35 2e 68 00 02 00 00 00 00 4e  >mx..x25.h..N<
  260 13 03 bf 1b 67 42 9a 00 00 00 00 2f 75 73 72 2f  >gB./usr/<
  300 73 72 63 2f 6c 69 6e 75  >src/linu<
  310

  in my case it was a file linux-headers-2.6.38-8-generic.list
  so i simply overwriten it
  ubuntu@ubuntu:/media$ sudo dd if=/dev/zero bs=1 count=292 seek=497968741888 
of=/dev/sda1
  292+0 records in
  292+0 records out
  292 bytes (292 B) copied, 0.000560058 s, 521 kB/s

  ubuntu@ubuntu:/media$ sudo dd if=/dev/sda1 bs=1 skip=497968741887 count=200 | 
od -tx1z   
  000 13 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ><
  020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ><
  *
  300 00 00 00 00 00 00 00 00  ><
  310
  200+0 records in
  200+0 records out
  200 bytes (200 B) copied, 0.00189193 s, 106 kB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: udisks 1.0.1-1ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18
  Uname: Linux 2.6.32-33-generic i686
  Architecture: i386
  Date: Sat Jun  9 21:35:05 2012
  LiveMediaBuild:

[Touch-packages] [Bug 1731981] [NEW] Please merge sudo (main) 1.8.21p2-2 from Debian unstable (main)

Public bug reported:

.

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

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

Title:
  Please merge sudo (main) 1.8.21p2-2 from Debian unstable (main)

Status in sudo package in Ubuntu:
  New

Bug description:
  .

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

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

[Touch-packages] [Bug 1713962] Re: apt-add-repository times out behind proxy

2017-11-13 Thread CB

I was able to fix it by using --keyserver-options like in the following
patch:

diff /usr/lib/python3/dist-packages/softwareproperties/ppa.py{.orig,}
189,195c189,207
< res = subprocess.call(self.GPG_DEFAULT_OPTIONS + [
< "--homedir", keyring_dir,
< "--secret-keyring", secret_keyring,
< "--keyring", keyring,
< "--keyserver", self.keyserver,
< "--recv", signing_key_fingerprint,
< ])
---
> http_proxy = os.environ.get("http_proxy")
> if http_proxy != "":
> res = subprocess.call(self.GPG_DEFAULT_OPTIONS + [
> "--homedir", keyring_dir,
> "--secret-keyring", secret_keyring,
> "--keyring", keyring,
> "--keyserver", self.keyserver,
> "--keyserver-options", "http-proxy=" + http_proxy,
> "--recv", signing_key_fingerprint,
> ])
> else:
> res = subprocess.call(self.GPG_DEFAULT_OPTIONS + [
> "--homedir", keyring_dir,
> "--secret-keyring", secret_keyring,
> "--keyring", keyring,
> "--keyserver", self.keyserver,
> "--recv", signing_key_fingerprint,
> ])
>

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

Title:
  apt-add-repository times out behind proxy

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  1) Release
  Ubuntu 17.04

  2) Package
  software-properties-common: 0.96.24.13

  3) What you expected to happen
  GPG key processed successfully
  e.g.

  $ sudo -E add-apt-repository ppa:whatever

  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keybox '/tmp/tmpby0unfol/pubring.gpg' created
  gpg: /tmp/tmpby0unfol/trustdb.gpg: trustdb created
  gpg: key XX: public key "Launchpad VLC" imported
  gpg: no ultimately trusted keys found
  gpg: Total number processed: 1
  gpg:   imported: 1
  OK

  4) What happened instead
  Timeout on gpg command
  e.g.

  $ sudo -E add-apt-repository ppa:whatever

  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keybox '/tmp/xxx/pubring.gpg' created
  Error: retrieving gpg key timed out.

  5) Additional info

  - OK on Ubuntu 16.04.3 LTS, software-properties-common: 0.96.20.7
  - Network Proxy is set via GUI, applied system wide

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

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

[Touch-packages] [Bug 1713457] Re: DNS search domain not removed from resolv.conf on disconnect

2017-11-13 Thread Paul Natsuo Kishimoto

Is this reported upstream?

Could be one of:
https://bugzilla.gnome.org/show_bug.cgi?id=712818
https://bugzilla.gnome.org/show_bug.cgi?id=778004
https://bugzilla.gnome.org/show_bug.cgi?id=782469

I notice per the first one that "nmcli dev show" (not "… list", the
report is old and I guess the semantics of nmcli have changed) will show
me the search domain when I'm connected to a network that sets it:

=
$ nmcli -f IP4.ADDRESS,IP4.DOMAIN dev show
IP4.ADDRESS[1]: 18.142.15.92/16
IP4.DOMAIN[1]:  mit.edu

IP4.ADDRESS[1]: 18.189.91.11/19
IP4.DOMAIN[1]:  mit.edu


IP4.ADDRESS[1]: 127.0.0.1/8
=


So I guess if I try this the next time this bug crops up and nmcli disagrees 
with the contents of resolv.conf, I will mark the first URL as the upstream bug.

Or if someone who understands this better wants to open a new upstream
bug, please go ahead.

** Bug watch added: GNOME Bug Tracker #712818
   https://bugzilla.gnome.org/show_bug.cgi?id=712818

** Bug watch added: GNOME Bug Tracker #778004
   https://bugzilla.gnome.org/show_bug.cgi?id=778004

** Bug watch added: GNOME Bug Tracker #782469
   https://bugzilla.gnome.org/show_bug.cgi?id=782469

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

Title:
  DNS search domain not removed from resolv.conf on disconnect

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  When I connect to a wireless network that sets a DNS search domain
  name via DHCP, the line 'search ' is added to /etc/resolv.conf
  as expected.  But if I then disconnect and connect to a different
  network, it is not removed from resolv.conf.  If the second network
  also sets a search domain name, that one gets appended to resolv.conf
  along with the first one, and so on.  Depending on the network, this
  can cause DNS leaks, name resolution failures, or other misbehavior.

  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 172.20.20.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1713457/+subscriptions

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

[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression

2017-11-13 Thread Dariusz Gadomski

Hello Matthias. Is there any progress with applying those features to
Xenial? Please let me know if you need any testing to be done.

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

Title:
  Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Confirmed

Bug description:
  I work on the OpenStack-Ansible project and we've noticed that testing
  jobs on 16.04 take quite a bit longer to complete than on 14.04.  They
  complete within an hour on 14.04 but they normally take 90 minutes or
  more on 16.04.  We use the same version of Ansible with both versions
  of Ubuntu.

  After more digging, I tested python performance (using the
  'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12).  There
  is a significant performance difference between each version of
  python.  That is detailed in a spreadsheet[0].

  I began using perf to dig into the differences when running the python
  performance module and when using Ansible playbooks.  CPU migrations
  (as measured by perf) are doubled in Ubuntu 16.04 when running the
  same python workloads.

  I tried changing some of the kerne.sched sysctl configurables but they
  had very little effect on the results.

  I compiled python 2.7.12 from source on 14.04 and found the
  performance to be unchanged there.  I'm not entirely sure where the
  problem might be now.

  We also have a bug open in OpenStack-Ansible[1] that provides
  additional detail. Thanks in advance for any help you can provide!

  [0] 
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
  [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions

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

[Touch-packages] [Bug 1731130] Re: /run/resolvconf/resolv.conf contains invalid 'search' entries

2017-11-13 Thread Paul Natsuo Kishimoto

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

Hi—yes, it seems so. Sorry that I didn't search hard enough before
reporting a duplicate!

** This bug has been marked a duplicate of bug 1713457
   DNS search domain not removed from resolv.conf on disconnect

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

Title:
  /run/resolvconf/resolv.conf contains invalid 'search' entries

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  STEPS TO REPRODUCE:

  I connect to certain MIT networks via both wired and wireless
  connections.

  Afterwards, I connect to a home network.

  EXPECTED:

  Domains like http://web.mit.edu resolve.

  OBSERVED:

  They don't.

  The file /run/resolvconf/resolv.conf contains only these lines:

  nameserver 127.0.0.53
  search mit.edu hsd1.ma.comcast.net

  It would seem hsd1.ma.comcast.net is correct, since that describes my
  ISP. But the mit.edu is erroneous and prevents applications from
  correctly resolving mit.edu domains.

  If I manually edit this file and remove "mit.edu" from the search
  line, the domains then resolve correctly. Shouldn't this be removed
  automatically?

  
  ~$ lsb_release -rd && apt-cache policy resolvconf
  Description:Ubuntu 17.10
  Release:17.10
  resolvconf:
Installed: 1.79ubuntu8
Candidate: 1.79ubuntu8
Version table:
   *** 1.79ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 00:34:20 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-11 (28 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (20 days ago)

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

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

[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

2017-11-13 Thread Paul Smith

Hi Sebastien, thanks for your interest.  This issue is causing me
extreme pain.  I believe I'm going to have to reconfigure N-M to use the
old-style dnsmasq setup and throw out systemd-resolve pretty soon.

It's not clear to me whether this is an N-M bug vs. a systemd bug, but
I'm happy to file more bugs.  Did you want me to file a bug with N-M?

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSyst

[Touch-packages] [Bug 1724152] Re: ISST-LTE: pVM: aureport couldn't get the right auid from the audit log on ubuntu16.04

2017-11-13 Thread Manoj Iyer

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Committed

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

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

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

Bug description:
  [Impact]

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

  [Test Case]

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

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

  An unpatched aureport will print the following:

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

  A patch aureport will print the correct output:

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

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

  [Regression Potential]

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

  [Original Report]

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

  The following are details:

  root@roselp2:~# aureport -l

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

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

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

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

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

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

  Nov 23 02:19:21 roselp2 auditctl[4086]: enabled 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: failure 1
  Nov 23 02:19:21 roselp2 auditctl[4086]: pid 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: rate_limit 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_limit 320
  Nov 23 02:19:21 roselp2 auditctl[4086]: lost 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_wait_time 15000
  Nov 23 02:19:21 roselp2 systemd[1]: Started Security Auditing Service.
  Nov 23 02:19:21 roselp2 auditd[4085]: Init complete, auditd 2.4.5 listening 
for

  Please cherry pick https://github.com/linux-audit/audit-
  userspace/commit/25097d64344828a80acf681da5c1dacc4ea3c069

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1724152/+subscriptions

-- 
Mailing list: https://launchpad.n

[Touch-packages] [Bug 1727390] Re: New bugfix release 17.2.4

2017-11-13 Thread Luca Tansini

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

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

Title:
  New bugfix release 17.2.4

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

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.2:

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

  The EGL code has improved handling of the new wl_dmabuf codepath.

  SWR no longer crashes when checking environment variables.

  Other gallium drivers have also seen updates - freedreno, nouveau and
  radeonsi. The gallivm module, used by llvmpipe et al. has gained little
  endian PPC64 fixes.

  The VA and VDPAU state-trackers have seems improvements handling
  interlaced videos.

  We're using python3 compatible constructs which gives us SCons 3.0
  support."

  "Mesa 17.2.4 is now available.

  In this release we have:

  In Mesa Core we have included a change to prevent KOTOR from breaking
  when in combination with the ATI fragment shader extension. 
  Additionally, NIR has also received a correction.

  Mesa's state tracker has gotten a patch to avoid leaks in certain
  situations like when resizing a window.

  Intel drivers have received several fixes.  The compiler has gotten a
  couple, while anv also received one.  i965 got a patch to avoid VA-
  API, Beignet and other contexts in the system to break when in
  combination with previous versions of Mesa 17.2.x.

  AMD's compiler has received a couple of fixes while radv has also
  received another couple, including one to avoid a hang due to an
  overflow on huge textures.

  Broadcom's vc4 has corrected a problem when compiling with Android's
  clang.

  clover has also seen fixed a problem compiling after a specific clang
  revision.

  Vulkan's WSI has gotten plugged a memory leak for X11."

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  [Regression potential]

  These releases are tested against compliance, bugfix releases in
  particular have minimal risk of regressing anything major at least.

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

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

[Touch-packages] [Bug 1731906] Re: package python 2.7.13-2 failed to install/upgrade: pre-dependency problem - not installing python

2017-11-13 Thread Matthias Klose

invalid. you have a python installation in /usr/local

raceback (most recent call last):
  File "/usr/local/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/local/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File "/usr/local/lib/python2.7/compileall.py", line 16, in 
import struct
  File "/usr/local/lib/python2.7/struct.py", line 1, in 
from _struct import *
ImportError: No module named _struct

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

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

Title:
  package python 2.7.13-2 failed to install/upgrade: pre-dependency
  problem - not installing python

Status in python-defaults package in Ubuntu:
  Invalid

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python 2.7.13-2
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Nov  7 14:04:14 2017
  ErrorMessage: pre-dependency problem - not installing python
  InstallationDate: Installed on 2017-06-10 (155 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.4.6~17.04.1
  SourcePackage: python-defaults
  Title: package python 2.7.13-2 failed to install/upgrade: pre-dependency 
problem - not installing python
  UpgradeStatus: Upgraded to zesty on 2017-11-07 (6 days ago)

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

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

[Touch-packages] [Bug 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

2017-11-13 Thread Drew

Can confirm this bug while using JavaFX in IntelliJ IDEA 2017.2.5 with
Oracle JDK 9.0.1...

/usr/share/themes/Radiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid
string constant "murrine-scrollbar", expected valid string constant

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  That installation is a default Ubuntu , no Mate installed, and
  Ambiance is set for 'applications' into tweaks

  [Test case]

  1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal
  2. App has to run without any error

  [Possible regression]

  Different scrollbars in gtk2 apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 774071] Re: Indicator-datetime-service renders 100% CPU usage

2017-11-13 Thread Anders Hall

Seeing this on 17.10 as well. Battery indicator says ("estimating,
100%) and indicator-datetime-service uses between 2.4 GiB and (mostly)
~14.5 GiB RAM. CPU usage stays at 25% all the time. The indicator-
datetime-service crashes after reaching all available RAM, then restarts
with new PID.

I reported, with debug info, about the relevant PID in Bug #1731939
(apport-collect didnt work during the bug event).

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

Title:
  Indicator-datetime-service renders 100% CPU usage

Status in Indicator Date and Time:
  Fix Released
Status in Unity Foundations:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: indicator-datetime

  On my laptop "indicator-datetime-service" occasionally make my CPU to
  use 100% of its resources. It does not happen every time I log in to
  Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill
  the process. If it helps, I've noticed in "System Monitor" that there
  are two instances of "indicator-datetime-service" running, but only
  one of them is hogging recourses. So far I was unable to determine
  after what actions/events this bug pups up.

  I'm using Ubuntu 11.04 64-bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: indicator-datetime 0.2.3-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sat Apr 30 15:27:58 2011
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/774071/+subscriptions

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

[Touch-packages] [Bug 1731939] [NEW] Indicator-datetime-service renders 25% CPU usage and 100% RAM

2017-11-13 Thread Anders Hall

Public bug reported:

Same as Bug #774071 but with 100% RAM instead. Collected info while the
Indicator-datetime-service was acting up. I.e., writing this with a few
hundred megabytes RAM available..

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: indicator-datetime 15.10+17.04.20170322-0ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Mon Nov 13 15:41:39 2017
ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
InstallationDate: Installed on 2015-07-18 (848 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: indicator-datetime
UpgradeStatus: Upgraded to zesty on 2017-06-13 (153 days ago)

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

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

Title:
   Indicator-datetime-service renders 25% CPU usage and 100% RAM

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Same as Bug #774071 but with 100% RAM instead. Collected info while
  the Indicator-datetime-service was acting up. I.e., writing this with
  a few hundred megabytes RAM available..

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Nov 13 15:41:39 2017
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2015-07-18 (848 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to zesty on 2017-06-13 (153 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+subscriptions

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

[Touch-packages] [Bug 1731939] Re: Indicator-datetime-service renders 25% CPU usage and 100% RAM

2017-11-13 Thread Anders Hall

PID changes after crash when RAM is depleted. Sceenshoot of RAM usage
attached.

** Attachment added: "Exampel of memory usage"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+attachment/5008303/+files/Screenshot%20from%202017-11-13%2015-29-41.png

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

Title:
   Indicator-datetime-service renders 25% CPU usage and 100% RAM

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Same as Bug #774071 but with 100% RAM instead. Collected info while
  the Indicator-datetime-service was acting up. I.e., writing this with
  a few hundred megabytes RAM available..

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Nov 13 15:41:39 2017
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2015-07-18 (848 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to zesty on 2017-06-13 (153 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+subscriptions

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

[Touch-packages] [Bug 1731940] [NEW] [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at all

2017-11-13 Thread Dennis Mungai Lin.Jr.

Public bug reported:

Hello there,

I have Ubuntu 16.04LTS installed on the Clevo P751DM2-G, also marketed
as the Schenker XMG U507, the System76's Serval WS (2017 model), the
Eurocom Sky X4E2, among others.

The sound card is the Realtek ALC898 with the following output
configuration:

1. One SPDIF/headphone combo jack (to the right)
2. One Line Out.
3. One Line-In.
4. One Mic-In.

Background information:

On Windows, one can use the Realtek HD Audio control panel pop-up menu
on jack detection to set the output type when an audio device is plugged
in to an appropriate jack, combined with Sound Blaster X-Fi MB5 software
to enable post-processing effects such as Bass, noise cancellation, etc.

What I have tried so far:

1. Setting the model definition at /etc/modprobe.d/sound.conf with the
following entries:

options snd-hda-intel model=no-primary-hp enable=1 index=0

Using such a line worked before on an MSI GS43VR 6RE Phantom Pro that
also has the same (or a similar) ESS Sabre Audio DAC component.

Expected behavior:

When plugged into the microphone jack, the ESS Sabre DAC should be
activated and sound should be routed to the headset.

Observed anomaly:

Sound comes out through the speakers instead.

However, the line-out output works. In that case, when plugged into the
line out, Audio works as expected.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.14.0 x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lin2199 F pulseaudio
 /dev/snd/controlC0:  lin2199 F pulseaudio
CurrentDesktop: GNOME
Date: Mon Nov 13 17:34:53 2017
InstallationDate: Installed on 2017-07-25 (111 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm1812 F pulseaudio
  lin2199 F pulseaudio
 /dev/snd/controlC0:  gdm1812 F pulseaudio
  lin2199 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [P7xxDM2(-G), Realtek ALC898, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.06.04
dmi.board.asset.tag: Tag 12345
dmi.board.name: P7xxDM2(-G)
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.06.04:bd12/21/2016:svnNotebook:pnP7xxDM2(-G):pvrNotApplicable:rvnNotebook:rnP7xxDM2(-G):rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: P7xxDM2(-G)
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

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


** Tags: amd64 apport-bug xenial

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

Title:
  [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello there,

  I have Ubuntu 16.04LTS installed on the Clevo P751DM2-G, also marketed
  as the Schenker XMG U507, the System76's Serval WS (2017 model), the
  Eurocom Sky X4E2, among others.

  The sound card is the Realtek ALC898 with the following output
  configuration:

  1. One SPDIF/headphone combo jack (to the right)
  2. One Line Out.
  3. One Line-In.
  4. One Mic-In.

  Background information:

  On Windows, one can use the Realtek HD Audio control panel pop-up menu
  on jack detection to set the output type when an audio device is
  plugged in to an appropriate jack, combined with Sound Blaster X-Fi
  MB5 software to enable post-processing effects such as Bass, noise
  cancellation, etc.

  What I have tried so far:

  1. Setting the model definition at /etc/modprobe.d/sound.conf with the
  following entries:

  options snd-hda-intel model=no-primary-hp enable=1 index=0

  Using such a line worked before on an MSI GS43VR 6RE Phantom Pro that
  also has the same (or a similar) ESS Sabre Audio DAC component.

  Expected behavior:

  When plugged into the microphone jack, the ESS Sabre DAC should be
  activated and sound should be routed to the headset.

  Observed anomaly:

  Sound comes out through the speakers instead.

  However, the line-out output works. In that case, when plugged into
  the line out,

Re: [Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2017-11-13 Thread Kasey Erickson

When I upgraded to 17.10 I made sure it was a fresh install, not an
in-place upgrade.  Sometimes broken configurations are left over when
upgrading in place.

On Mon, Nov 13, 2017 at 3:50 AM, Alexander Adam <1575...@bugs.launchpad.net>
wrote:

> I can't confirm what Kasey (kasey-erickson) wrote: issue still appears in
> Ubuntu 17.10.
> I upgraded from 17.04. So if it really should be fixed in 17.10 I'm very
> open to hints for particular config purges/reinstallations or actually
> anything that could help.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1575078
>
> Title:
>   [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
>   while
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+
> bug/1575078/+subscriptions
>

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

Title:
  [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
  while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a strange behavior with a headphone jack on my
  laptop.

  I have an external audio speaker connected to it. When I disconnect the 
speaker and reconnect it again it stops working.
  Even more, laptop audio stops working too. And after the reboot, I don't even 
see any of the audio devices.

  I've googled a lot and tried different fixes from forums with no luck.
  After a while, I've accidentally discovered that putting the laptop to
  the sleep mode and rebooting system after brings audio back to live.
  Even more, if speakers were attached during this sleep-reboot
  procedure, they are starting to work as well.

  However, after the next reboot speakers are not working again. And if
  I will plug them out and in - problem with completely missing audio
  returns.

  P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
  hibernation made me believe that it's somehow related. But after
  uninstalling this package nothing really changed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   kop3224 F...m pulseaudio
   /dev/snd/controlC0:  kop3224 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 26 12:17:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after 
a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1722722] Re: Search domains not deleted from resolv.conf

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

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

** This bug has been marked a duplicate of bug 1713457
   DNS search domain not removed from resolv.conf on disconnect

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

Title:
  Search domains not deleted from resolv.conf

Status in resolvconf package in Ubuntu:
  New

Bug description:
  I hope that this is the right place for this.  What I am seeing is
  that every time I switch networks with my laptop entries get added to
  the resolv.conf search list but never deleted.  For whatever reason,
  once I have left our company network I am unable to access resources
  which are internal in the network but also availably externally (e.g.
  the main company home page) until I have removed the search entries
  manually.

  If more information or testing would be useful please let me know
  what.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 08:50:33 2017
  InstallationDate: Installed on 2016-05-31 (497 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago)

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

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-11-13 Thread Woko

I just created two VMWare-machines to show the difference. One with a
Kubuntu17.10-image, one with a KDE-Neon-image. In Kubuntu I installed
the freetype-PPA to get Version 2.8.1, in KDE-Neon they stick to 2.6.1.
On both I startet a Konsole-Session with Monospace-Font. The Result is
attached.

** Attachment added: "Screenshot_20171113_145230.png"
   
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+attachment/5008275/+files/Screenshot_20171113_145230.png

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

Title:
  Font hinting appears broken on 17.10 beta

Status in Qt:
  New
Status in freetype package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed
Status in qtbase-opensource-src source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

[Touch-packages] [Bug 1731130] Re: /run/resolvconf/resolv.conf contains invalid 'search' entries

Hi,

I think this is a duplicate of bug 1713457 where resolvconf is not
removing the old search domains from the list when disconnecting.

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

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

Title:
  /run/resolvconf/resolv.conf contains invalid 'search' entries

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  STEPS TO REPRODUCE:

  I connect to certain MIT networks via both wired and wireless
  connections.

  Afterwards, I connect to a home network.

  EXPECTED:

  Domains like http://web.mit.edu resolve.

  OBSERVED:

  They don't.

  The file /run/resolvconf/resolv.conf contains only these lines:

  nameserver 127.0.0.53
  search mit.edu hsd1.ma.comcast.net

  It would seem hsd1.ma.comcast.net is correct, since that describes my
  ISP. But the mit.edu is erroneous and prevents applications from
  correctly resolving mit.edu domains.

  If I manually edit this file and remove "mit.edu" from the search
  line, the domains then resolve correctly. Shouldn't this be removed
  automatically?

  
  ~$ lsb_release -rd && apt-cache policy resolvconf
  Description:Ubuntu 17.10
  Release:17.10
  resolvconf:
Installed: 1.79ubuntu8
Candidate: 1.79ubuntu8
Version table:
   *** 1.79ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 00:34:20 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-11 (28 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (20 days ago)

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

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

[Touch-packages] [Bug 1731747] Re: slow screen

2017-11-13 Thread Timo Aaltonen

there's no driver support for your GPU nor will there ever be, so
closing the bug

** Package changed: xorg (Ubuntu) => xserver-xorg-video-sis (Ubuntu)

** Changed in: xserver-xorg-video-sis (Ubuntu)
   Status: New => Won't Fix

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

Title:
  slow screen

Status in xserver-xorg-video-sis package in Ubuntu:
  Won't Fix

Bug description:
  my screen was'nt following input

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Nov 12 12:45:31 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter 
[1039:6351] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Pegatron 771/671 PCIE VGA Display Adapter [1b0a:0007]
  InstallationDate: Installed on 2017-11-06 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=ea424e5e-e4a3-4d68-ac27-ff9d289750c0 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0003
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0003:bd06/29/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Nov 12 12:07:02 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1731747/+subscriptions

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

[Touch-packages] [Bug 1731646] Re: missing qDebug output when creating QT applications

2017-11-13 Thread Dimitar Petrovski

according to this documentation:
http://doc.qt.io/qt-5/qtglobal.html#qDebug
which is also referenced in the link you provided it says that if you write:
qDebug() << "Debug" there should be output unless QT_NO_DEBUG_OUTPUT is defined.
there is no mention that the logging category filters this messages, I guess in 
this case the category is "default"
If you consider this a QT documentation problem, I will write a separate report 
to QT bug tracking system.

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

Title:
  missing qDebug output when creating QT applications

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

Bug description:
  This bug seems to be connected to:
  https://bugzilla.redhat.com/show_bug.cgi?id=1227295

  in the above link I have found a workaround for the problem. I have created 
an empty file in:
  ~/.config/QtProject called qtlogging.ini and the problem is resolved.

  the problem was not present in ubuntu 17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libqt5core5a 5.9.1+dfsg-10ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Nov 11 16:59:49 2017
  InstallationDate: Installed on 2016-11-09 (366 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: Upgraded to artful on 2017-10-30 (11 days ago)

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

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

[Touch-packages] [Bug 1729910] Re: lp ignores ~/.cups/lpoptions in 17.10

2017-11-13 Thread Dariusz Gadomski

** Tags removed: verification-needed

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

Title:
  lp ignores ~/.cups/lpoptions in 17.10

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * During some refactoring done to cupsGetNamedDest function used in
  many different parts of the code a regression has been introduced
  causing the per-user default printer setting (in ~/.cups/lpoptions) to
  be ignored.

  This bug has been introduced in Artful due to the refactoring. Earlier
  releases are fine, similarly this bug is fixed upstream for Bionic.

  [Test Case]

   1. Make sure at least 2 printers are set up in cups.
   2. Set one of them as global default.
   3. Create a user default setting (~/.cups/lpoptions) with the other printer 
set as default:
  Default other_printer
   4. Run lpstat -d.

  Expected result:
  User default printer is displayed.

  Actual result:
  Global default printer is displayed.

  [Regression Potential]

   * The regression potential is minial, as this is a very simple bugfix and is 
already included in the latest (2.2.5+) releases of cups (including Bionic).
   * The only setups affected may be those depending (possibly unintentionally) 
on the incorrect behavior. Their users may observe default printer change.

  [Other Info]

   * Original bug description

  LP ignores the settings defined in ~/cups/lpoptions in artful

  Steps to reproduce:

  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

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

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

[Touch-packages] [Bug 1713457] Re: DNS search domain not removed from resolv.conf on disconnect

OK I can confirm that uninstalling resolvconf is fixing that behavior
here

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

Title:
  DNS search domain not removed from resolv.conf on disconnect

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  When I connect to a wireless network that sets a DNS search domain
  name via DHCP, the line 'search ' is added to /etc/resolv.conf
  as expected.  But if I then disconnect and connect to a different
  network, it is not removed from resolv.conf.  If the second network
  also sets a search domain name, that one gets appended to resolv.conf
  along with the first one, and so on.  Depending on the network, this
  can cause DNS leaks, name resolution failures, or other misbehavior.

  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 172.20.20.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1713457/+subscriptions

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

[Touch-packages] [Bug 1731334] Re: update-notifier-common upgrade :debconf.py not found

This bug was fixed in the package update-notifier - 3.188

---
update-notifier (3.188) bionic; urgency=medium

  * Also add python3-debconf as a build-dependency.

 -- Steve Langasek   Sun, 12 Nov 2017
21:15:44 -0800

** Changed in: update-notifier (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 debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1731334

Title:
  update-notifier-common upgrade :debconf.py not found

Status in debconf package in Ubuntu:
  Fix Committed
Status in update-notifier package in Ubuntu:
  Fix Released

Bug description:
  Today I did a fresh instalation of new branch development ubuntu
  beaver, intended to help with some tests... So, after the
  installation, I switched on cannonical partners and proposed
  repositoryes and I gave an apt upgrade and dist-upgrade and restarted
  the computer...  After this I tried to install flashplugin-installer
  and I got the follow messages from apt process:

  Configuring update-notifier-common (3.186) ...
  Traceback (most recent call last):
File "/usr/lib/update-notifier/package-data-downloader", line 26, in 

  import debconf
  ModuleNotFoundError: No module named 'debconf'
  dpkg: erro ao processar o pacote update-notifier-common (--configure):
   installed update-notifier-common package post-installation script subprocess 
returned error exit status 1

  I had to remove the update-notifier-common and with it, update-
  notifier, ubuntu-desktop, the unconfigured flashplugin-installer and
  some two oher dependencies that I dont remember.

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

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

[Touch-packages] [Bug 1713457] Re: DNS search domain not removed from resolv.conf on disconnect

@andersk Is resolvconf installed on your machine?

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

Title:
  DNS search domain not removed from resolv.conf on disconnect

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  When I connect to a wireless network that sets a DNS search domain
  name via DHCP, the line 'search ' is added to /etc/resolv.conf
  as expected.  But if I then disconnect and connect to a different
  network, it is not removed from resolv.conf.  If the second network
  also sets a search domain name, that one gets appended to resolv.conf
  along with the first one, and so on.  Depending on the network, this
  can cause DNS leaks, name resolution failures, or other misbehavior.

  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 172.20.20.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1713457/+subscriptions

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

[Touch-packages] [Bug 1713457] Re: DNS search domain not removed from resolv.conf on disconnect

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

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

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

Title:
  DNS search domain not removed from resolv.conf on disconnect

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  When I connect to a wireless network that sets a DNS search domain
  name via DHCP, the line 'search ' is added to /etc/resolv.conf
  as expected.  But if I then disconnect and connect to a different
  network, it is not removed from resolv.conf.  If the second network
  also sets a search domain name, that one gets appended to resolv.conf
  along with the first one, and so on.  Depending on the network, this
  can cause DNS leaks, name resolution failures, or other misbehavior.

  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 172.20.20.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1713457/+subscriptions

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

[Touch-packages] [Bug 1731906] Re: package python 2.7.13-2 failed to install/upgrade: pre-dependency problem - not installing python

2017-11-13 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package python 2.7.13-2 failed to install/upgrade: pre-dependency
  problem - not installing python

Status in python-defaults package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python 2.7.13-2
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Nov  7 14:04:14 2017
  ErrorMessage: pre-dependency problem - not installing python
  InstallationDate: Installed on 2017-06-10 (155 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.4.6~17.04.1
  SourcePackage: python-defaults
  Title: package python 2.7.13-2 failed to install/upgrade: pre-dependency 
problem - not installing python
  UpgradeStatus: Upgraded to zesty on 2017-11-07 (6 days ago)

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

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

[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

It would probably be a good idea to forward it to n-m upstream as well
on bugzilla.gnome.org

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

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name

[Touch-packages] [Bug 1731906] [NEW] package python 2.7.13-2 failed to install/upgrade: pre-dependency problem - not installing python

2017-11-13 Thread Nguyen Minh Hieu

Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: python 2.7.13-2
ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Tue Nov  7 14:04:14 2017
ErrorMessage: pre-dependency problem - not installing python
InstallationDate: Installed on 2017-06-10 (155 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.4.6~17.04.1
SourcePackage: python-defaults
Title: package python 2.7.13-2 failed to install/upgrade: pre-dependency 
problem - not installing python
UpgradeStatus: Upgraded to zesty on 2017-11-07 (6 days ago)

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


** Tags: amd64 apport-package zesty

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

Title:
  package python 2.7.13-2 failed to install/upgrade: pre-dependency
  problem - not installing python

Status in python-defaults package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python 2.7.13-2
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Nov  7 14:04:14 2017
  ErrorMessage: pre-dependency problem - not installing python
  InstallationDate: Installed on 2017-06-10 (155 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.4.6~17.04.1
  SourcePackage: python-defaults
  Title: package python 2.7.13-2 failed to install/upgrade: pre-dependency 
problem - not installing python
  UpgradeStatus: Upgraded to zesty on 2017-11-07 (6 days ago)

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

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

[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager-openvpn (Ubuntu)
   Importance: Undecided => High

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Pro

[Touch-packages] [Bug 1725348] Re: Systemd - Bypassing MemoryDenyWriteExecution policy

2017-11-13 Thread zbyszek

Upstream commits:

https://github.com/systemd/systemd/commit/b835eeb4ec1dd122b6feff2b70881265c529fcdd
https://github.com/systemd/systemd/commit/91691f1d3e3c66122fd0fc564ea3f20f566c2698
https://github.com/systemd/systemd/commit/213f2883c006d785e033597d2f46a110d85eb54b

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

Title:
  Systemd - Bypassing MemoryDenyWriteExecution policy

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  Hello,

  We would like to report to you a vulnerability about systemd which
  allows to bypass the MemoryDenyWriteExecution policy on Linux 4.9+.

  The vulnerability is described in the attached PDF file.

  
  Sincerely, 
  Thomas IMBERT

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

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

[Touch-packages] [Bug 1719746] Re: gdebi 0.9.5.7+nmu1ubuntu3 broke being able to open .debs on default Ubuntu desktop

2017-11-13 Thread ajgreeny

A ubuntuforums thread about this problem
https://ubuntuforums.org/showthread.php?t=2377258&p=13710654#post13710654
has a solution or workaround of simply adding %U to the Exec= line of
the gdebi.desktop file so it reads "Exec=gdebi-gtk %U".

This has allowed use of gdebi from the file manager either from a right
click or by changing the properties "Open with" tab in file properties.

I have requested a link for the mac4man solution mentioned in the
ubuntuforum post and will add it here once I have it.

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

Title:
  gdebi 0.9.5.7+nmu1ubuntu3 broke being able to open .debs on default
  Ubuntu desktop

Status in gdebi package in Ubuntu:
  Confirmed
Status in gdebi source package in Artful:
  Confirmed

Bug description:
  I don't use gdebi but this commit looks wrong:

  https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu1ubuntu3

  See
  https://lintian.debian.org/tags/desktop-mime-but-no-exec-code.html

  https://standards.freedesktop.org/desktop-entry-spec/desktop-entry-
  spec-latest.html#mime-types

  (Do not be confused by the Type=MimeType deprecation. This file is
  Type=Application.)

  Here's a user video report:
  https://youtu.be/yDrAbBAp-1A?t=16m19s

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

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

[Touch-packages] [Bug 1731904] [NEW] Font has a big line hight

2017-11-13 Thread Boubouh Karim

Public bug reported:

Comparing to normal Ubuntu fonts, the Arabic Ubuntu fonts has an extra
line hight.

Please correct this so it matchs the Ubuntu family fonts


System release :
Description:Arch Linux
Release:rolling

Version of the package :
0.84~mono0.83+arabicfontconfig-0ubuntu1

What you expected to happen: 
Correct the line hight to matchs the main Ubuntu fonts

What happened instead:
Well an extra line hight for example the menu takes almost the double size in 
the nautilus file manager.

** Affects: ubuntu-font-family-sources (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-font-family-sources
in Ubuntu.
https://bugs.launchpad.net/bugs/1731904

Title:
  Font has a big line hight

Status in ubuntu-font-family-sources package in Ubuntu:
  New

Bug description:
  Comparing to normal Ubuntu fonts, the Arabic Ubuntu fonts has an extra
  line hight.

  Please correct this so it matchs the Ubuntu family fonts

  
  System release :
  Description:  Arch Linux
  Release:  rolling

  Version of the package :
  0.84~mono0.83+arabicfontconfig-0ubuntu1

  What you expected to happen: 
  Correct the line hight to matchs the main Ubuntu fonts

  What happened instead:
  Well an extra line hight for example the menu takes almost the double size in 
the nautilus file manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1731904/+subscriptions

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

[Touch-packages] [Bug 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel

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

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

Title:
  intel-microcode should be installed by default, when the CPU is
  GenuineIntel

Status in intel:
  Fix Released
Status in Ubuntu Kylin:
  Fix Released
Status in amd64-microcode package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  Fix Released

Bug description:
  intel-microcode should be installed by default on the bare-metal
  systems which are running on GenuineIntel CPUs, by the installers.

  Similarly other microcode packages for other CPUs brands should be
  considered for inclusion (e.g. amd64-microcode).

  I hope that ubuntu-drivers-common can gain ability to detect cpu
  series and/or vendors, packages that provide microcodes similarly
  declare support for cpu series and/or vendors, the microcode packages
  are shipped on the CDs in the pool directory, and installed on to the
  target machines as part of the installation.

  This should help with rapid correction of bugs and behaviour of the
  CPUs in the field.

  2017 update, amd64-microcode should also be seeded, as it is useful to
  have it autoinstallable. In the recent years there have been critical
  CPU security vulnerabilities which got fixed with microcode updates.

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

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

[Touch-packages] [Bug 1685606] Re: systemd-resolv does not clear IPv6 DNS server entries after disconnect

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

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

Title:
  systemd-resolv does not clear IPv6 DNS server entries after disconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  ii  systemd 232-21ubuntu3   amd64   system and service manager
  ii  network-manager 1.4.4-1ubuntu3  amd64   network management framework 
(daemon and userspace tools)

  Problem description:
  1)
  When connected to a wired network that supports IPv4 and IPv6 with DNS via 
DHCP 'systemd-resolve --status' reports:
  DNS Servers: 10.10.10.1
   fd00::c225:6ff:fe4e:1582
  and nmcli (nmcli dev show |grep DNS) reports:
  IP4.DNS[1]: 10.10.10.1
  IP6.DNS[1]: fd00::c225:6ff:fe4e:1582

  2)
  After disconnecting this wired network interface it still reports:
  DNS Servers: fd00::c225:6ff:fe4e:1582

  but nmcli does not report any DNS server, as expected.

  3) 
  After reconnecting to the same wired network, but after changing the IPv4 
connection preferences from 'Method: Automatic (DHCP)' to Method: Automatic 
(DHCP) address only', and for IPv6 from 'Method: Automatic' to 'Method: 
Automatic, addresses only', 'systemd-resolve --status' still reports:
  DNS Servers: fd00::c225:6ff:fe4e:1582

  and nmcli still does not report any DNS serv, as expected.

  I Have checked with tshark that, although no DNS server should be
  queried, systemd still did on the IPv6 DNS address (and successfully
  resolved names and addresses).

  ---some extra testing---

  4)
  After disconnecting this wired network interface it still reports:
  DNS Servers: fd00::c225:6ff:fe4e:1582

  but nmcli does not report any DNS server, as expected.

  5)
  Connect to a WireLess IPv4 only Network (MiFi) 'systemd-resolve --status' 
reports:
  DNS Servers: 192.168.8.1

  and nmcli (nmcli dev show |grep DNS) reports:
  IP4.DNS[1]: 192.168.8.1

  Both as expected

  6)
  Network disconnect. 'systemd-resolve --status' reports:
  DNS Servers: 8.8.8.8
   8.8.4.4
   2001:4860:4860::
   2001:4860:4860::8844
  (these are FallbackDNS hostd mentioned in /etc/systemd/resolved.conf)
  and nmcli (nmcli dev show |grep DNS) does not report anything as expected.

  7)
  Reconnect to wired network with IPv4 and IPv6 WITHOUT DNS servers via DHCP 
(Situation 3)
  DNS Servers: 8.8.8.8
   8.8.4.4
   2001:4860:4860::
   2001:4860:4860::8844
  and nmcli (nmcli dev show |grep DNS) does not report anything as expected.

  8)
  Network disconnect:
  DNS Servers: 8.8.8.8
   8.8.4.4
   2001:4860:4860::
   2001:4860:4860::8844
  and nmcli (nmcli dev show |grep DNS) does not report anything as expected.

  9)
  Connect to a wired network that supports IPv4 and IPv6 with DNS via DHCP 
(Situation 1)
  DNS Servers: 10.10.10.1
   fd00::c225:6ff:fe4e:1582
  and nmcli (nmcli dev show |grep DNS) reports:
  IP4.DNS[1]: 10.10.10.1
  IP6.DNS[1]: fd00::c225:6ff:fe4e:1582

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1685606/+subscriptions

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

[Touch-packages] [Bug 1726735] Re: DNS resolve.conf error

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

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

Title:
  DNS resolve.conf error

Status in network-manager package in Ubuntu:
  New

Bug description:
  ubuntu 17.10, systemd-resolved listen 127.0.0.53 but 127.0.1.1 setted
  in resolve.conf !!

  andy@Andy-Desktop:~$ uname -a
  Linux Andy-Desktop 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  andy@Andy-Desktop:~$ cat /etc/resolv.conf
  # Generated by NetworkManager
  search 9office
  nameserver 127.0.1.1

  andy@Andy-Desktop:~$ sudo netstat -nlup| grep resolve
  udp0  0 127.0.0.53:53   0.0.0.0:* 
  700/systemd-resolve
  udp0  0 0.0.0.0:53550.0.0.0:* 
  700/systemd-resolve
  udp6   0  0 :::5355 :::*  
  700/systemd-resolve
  andy@Andy-Desktop:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1726735/+subscriptions

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

[Touch-packages] [Bug 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel

** Description changed:

  intel-microcode should be installed by default on the bare-metal systems
  which are running on GenuineIntel CPUs, by the installers.
  
  Similarly other microcode packages for other CPUs brands should be
  considered for inclusion (e.g. amd64-microcode).
  
  I hope that ubuntu-drivers-common can gain ability to detect cpu series
  and/or vendors, packages that provide microcodes similarly declare
  support for cpu series and/or vendors, the microcode packages are
  shipped on the CDs in the pool directory, and installed on to the target
  machines as part of the installation.
  
  This should help with rapid correction of bugs and behaviour of the CPUs
  in the field.
+ 
+ 2017 update, amd64-microcode should also be seeded, as it is useful to
+ have it autoinstallable. In the recent years there have been critical
+ CPU security vulnerabilities which got fixed with microcode updates.

** Also affects: amd64-microcode (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/1386257

Title:
  intel-microcode should be installed by default, when the CPU is
  GenuineIntel

Status in intel:
  Fix Released
Status in Ubuntu Kylin:
  Fix Released
Status in amd64-microcode package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  Fix Released

Bug description:
  intel-microcode should be installed by default on the bare-metal
  systems which are running on GenuineIntel CPUs, by the installers.

  Similarly other microcode packages for other CPUs brands should be
  considered for inclusion (e.g. amd64-microcode).

  I hope that ubuntu-drivers-common can gain ability to detect cpu
  series and/or vendors, packages that provide microcodes similarly
  declare support for cpu series and/or vendors, the microcode packages
  are shipped on the CDs in the pool directory, and installed on to the
  target machines as part of the installation.

  This should help with rapid correction of bugs and behaviour of the
  CPUs in the field.

  2017 update, amd64-microcode should also be seeded, as it is useful to
  have it autoinstallable. In the recent years there have been critical
  CPU security vulnerabilities which got fixed with microcode updates.

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

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

[Touch-packages] [Bug 1691996] Re: DNS and search domain is not pushed to systemd-resolved sometimes

The issue is fixed in Ubuntu 17.10, it's not likely to get SRUed to the
previous stable now though

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  DNS and search domain is not pushed to systemd-resolved sometimes

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  I have an OpenVPN connection with statically configured DNS server
  address and the search domain. When this connection is established,
  there is a high chance that the DNS address and the search domain are
  not pushed to systemd-resolved for this connection. The problem does
  not reproduce reliably, sometimes the parameters are pushed. When the
  parameters are not pushed, 'systemd-resolve --status' reports no DNS
  servers or DNS domain for the VPN connection, and name resolution does
  not work.

  This bug has been reportedly fixed upstream in NetworkManager 1.8. The
  upstream bug reports are:

  https://bugzilla.gnome.org/show_bug.cgi?id=782597
  https://bugzilla.gnome.org/show_bug.cgi?id=779087

  Please, update NetworkManager shipped with Ubuntu or backport the fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  Uname: Linux 4.10.0-16.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May 19 13:35:42 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-05-01 (748 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.1.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 100 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (33 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-05-11T15:26:12.449289
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   virbr0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/2  
virbr0  a80bff56-e5d6-4fa4-b544-89cb3c389e3b  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  44a70bab-e44e-3942-8259-e96eb6f3fe5b  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  
--  ----
 
   virbr0-nic  tun   unmanaged  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1691996/+subscriptions

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

[Touch-packages] [Bug 1725348] Re: Systemd - Bypassing MemoryDenyWriteExecution policy

2017-11-13 Thread Ubuntu Foundations Team Bug Bot

The attachment "0001-shared-seccomp-disallow-pkey_mprotect-the-same-as-
mp.patch" seems to be a patch.  If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Systemd - Bypassing MemoryDenyWriteExecution policy

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  Hello,

  We would like to report to you a vulnerability about systemd which
  allows to bypass the MemoryDenyWriteExecution policy on Linux 4.9+.

  The vulnerability is described in the attached PDF file.

  
  Sincerely, 
  Thomas IMBERT

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

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

[Touch-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root

With uname -a listing 4.4.0-100-generic #123-Ubuntu I get two change
events, on the parent nbd3 device when connecting nbd export to
/dev/nbd3 with two partitions (nbd3p1 and nbd3p2).

With uname -a listing 4.4.0-98 I do not get such events.

This bug is verified on xenial, will prepate matching systemd udev rules
change SRU.

** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/696435

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  Kernel does not generate any events when ndb-client connects /dev/nbd0 
devices, therefore it is impossible to monitor/react to the state of /dev/nbd0.

  [Fix]
  Generate change uevent when size of /dev/nbd0 changes

  [Testcase]
  * Start udevadm monitor
  * modprobe nbd
  * use ndb-client to connect something to /dev/nbd0
  * observe that there are change udev events generated on /dev/nbd0 itself

  [Regression Potential]
  There is no change to existing uevents, or their ordering.
  There is now an addition change event which will cause systemd to mark ndb 
devices as ready and trigger appropriate actions

  [Original Bug Report]

  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
   while [ -z "${FSTYPE}" ]; do
    FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

    # Run failure hooks, hoping one of them can fix up the system
    # and we can restart the wait loop.  If they all fail, abort
    # and move on to the panic handler and shell.
    if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
     break
    fi
   done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

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

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

[Touch-packages] [Bug 1725348] Re: Systemd - Bypassing MemoryDenyWriteExecution policy

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

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

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

** Also affects: systemd (Ubuntu Artful)
   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/1725348

Title:
  Systemd - Bypassing MemoryDenyWriteExecution policy

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  Hello,

  We would like to report to you a vulnerability about systemd which
  allows to bypass the MemoryDenyWriteExecution policy on Linux 4.9+.

  The vulnerability is described in the attached PDF file.

  
  Sincerely, 
  Thomas IMBERT

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

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

[Touch-packages] [Bug 1713457] Re: DNS search domain not removed from resolv.conf on disconnect

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

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

Title:
  DNS search domain not removed from resolv.conf on disconnect

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  New

Bug description:
  When I connect to a wireless network that sets a DNS search domain
  name via DHCP, the line 'search ' is added to /etc/resolv.conf
  as expected.  But if I then disconnect and connect to a different
  network, it is not removed from resolv.conf.  If the second network
  also sets a search domain name, that one gets appended to resolv.conf
  along with the first one, and so on.  Depending on the network, this
  can cause DNS leaks, name resolution failures, or other misbehavior.

  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 172.20.20.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1713457/+subscriptions

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

[Touch-packages] [Bug 1713457] Re: DNS search domain not removed from resolv.conf on disconnect

Hi,

I can confirm this bug.

This is really annoying as it breaks VPN connection here

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

Title:
  DNS search domain not removed from resolv.conf on disconnect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When I connect to a wireless network that sets a DNS search domain
  name via DHCP, the line 'search ' is added to /etc/resolv.conf
  as expected.  But if I then disconnect and connect to a different
  network, it is not removed from resolv.conf.  If the second network
  also sets a search domain name, that one gets appended to resolv.conf
  along with the first one, and so on.  Depending on the network, this
  can cause DNS leaks, name resolution failures, or other misbehavior.

  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 172.20.20.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1713457/+subscriptions

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

[Touch-packages] [Bug 1713457] Re: DNS search domain not removed from resolv.conf on disconnect

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

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

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

Title:
  DNS search domain not removed from resolv.conf on disconnect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When I connect to a wireless network that sets a DNS search domain
  name via DHCP, the line 'search ' is added to /etc/resolv.conf
  as expected.  But if I then disconnect and connect to a different
  network, it is not removed from resolv.conf.  If the second network
  also sets a search domain name, that one gets appended to resolv.conf
  along with the first one, and so on.  Depending on the network, this
  can cause DNS leaks, name resolution failures, or other misbehavior.

  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 172.20.20.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1713457/+subscriptions

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

[Touch-packages] [Bug 1725348] Re: Systemd - Bypassing MemoryDenyWriteExecution policy

2017-11-13 Thread Marc Deslauriers

** Information type changed from Private Security to Public Security

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

Title:
  Systemd - Bypassing MemoryDenyWriteExecution policy

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  Hello,

  We would like to report to you a vulnerability about systemd which
  allows to bypass the MemoryDenyWriteExecution policy on Linux 4.9+.

  The vulnerability is described in the attached PDF file.

  
  Sincerely, 
  Thomas IMBERT

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

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

[Touch-packages] [Bug 1731796] Re: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-11-13 Thread Andreas Hasenack

Sorry, it's actually gdbus that is soft locking

** Package changed: nvidia-graphics-drivers (Ubuntu) => glib2.0 (Ubuntu)

** Summary changed:

- package samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
+ NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878]

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878]

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  This is a bug report about errors during the upgrade process. I don't
  know whether or not my samba installation was working immediately
  before the upgrade; the windows box that was intended to be a client
  died and has not been replaced. Don't believe my answers to the forced
  questions.

  ***

  My ubuntu system locks up regularly. Bugs I've reported about this get
  closed for inattention, after being ignored, and queries about how to
  do basic debugging get the same treatment, so I just power cycle
  whenever it happens again.

  This time the lock up happened while the GUI upgrade-everything-to-
  latest tool was running.

  When I power cycled the box to recover, the system was unusable -
  flashing "system problem detected" popups, none staying stable long
  enough to respond.

  ssh + "sudo apt-get update" + "sudo apt-get upgrade" pointed me to
  "sudo dpkg --configure -a"

  That command reported numerous errors - I don't know which of them are
  "normal" for this system, but hidden by the GUI, and which are new.

  But it got the system semi-usable from the GUI, so now I'm clicking on
  "yes, report it" for the many pop-ups, of which this is one.

  FWIW, samba is one of the ones "dpkg --reconfigure -a" complained
  about.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.10
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Nov 12 11:07:42 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2012-04-26 (2026 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  NmbdLog:
   
  OtherFailedConnect: Yes
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SambaServerRegression: Yes
  SmbConfIncluded: Yes
  SmbLog:
   
  SourcePackage: samba
  Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-03-31 (226 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1731796/+subscriptions

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

[Touch-packages] [Bug 1731796] [NEW] package samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

You have been subscribed to a public bug:

This is a bug report about errors during the upgrade process. I don't
know whether or not my samba installation was working immediately before
the upgrade; the windows box that was intended to be a client died and
has not been replaced. Don't believe my answers to the forced questions.

***

My ubuntu system locks up regularly. Bugs I've reported about this get
closed for inattention, after being ignored, and queries about how to do
basic debugging get the same treatment, so I just power cycle whenever
it happens again.

This time the lock up happened while the GUI upgrade-everything-to-
latest tool was running.

When I power cycled the box to recover, the system was unusable -
flashing "system problem detected" popups, none staying stable long
enough to respond.

ssh + "sudo apt-get update" + "sudo apt-get upgrade" pointed me to "sudo
dpkg --configure -a"

That command reported numerous errors - I don't know which of them are
"normal" for this system, but hidden by the GUI, and which are new.

But it got the system semi-usable from the GUI, so now I'm clicking on
"yes, report it" for the many pop-ups, of which this is one.

FWIW, samba is one of the ones "dpkg --reconfigure -a" complained about.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.10
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Sun Nov 12 11:07:42 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2012-04-26 (2026 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
NmbdLog:
 
OtherFailedConnect: Yes
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SambaServerRegression: Yes
SmbConfIncluded: Yes
SmbLog:
 
SourcePackage: samba
Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2017-03-31 (226 days ago)

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


** Tags: amd64 apport-package xenial
-- 
package samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
https://bugs.launchpad.net/bugs/1731796
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to glib2.0 in Ubuntu.

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

[Touch-packages] [Bug 1731879] Re: remove readline6 from the archive

2017-11-13 Thread Matthias Klose

only left dependency: bareos

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

Title:
  remove readline6 from the archive

Status in readline6 package in Ubuntu:
  New

Bug description:
  remove readline6 from the archive, replaced by readline.

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

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

[Touch-packages] [Bug 1731879] [NEW] remove readline6 from the archive

2017-11-13 Thread Matthias Klose

Public bug reported:

remove readline6 from the archive, replaced by readline.

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

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

Title:
  remove readline6 from the archive

Status in readline6 package in Ubuntu:
  New

Bug description:
  remove readline6 from the archive, replaced by readline.

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

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

[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2017-11-13 Thread Alexander Adam

I can't confirm what Kasey (kasey-erickson) wrote: issue still appears in
Ubuntu 17.10.
I upgraded from 17.04. So if it really should be fixed in 17.10 I'm very open
to hints for particular config purges/reinstallations or actually anything that
could help.

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

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

I have an external audio speaker connected to it. When I disconnect the
speaker and reconnect it again it stops working.
Even more, laptop audio stops working too. And after the reboot, I don't even
see any of the audio devices.

I've googled a lot and tried different fixes from forums with no luck.
After a while, I've accidentally discovered that putting the laptop to
the sleep mode and rebooting system after brings audio back to live.
Even more, if speakers were attached during this sleep-reboot
procedure, they are starting to work as well.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: kop3224 F...m pulseaudio
/dev/snd/controlC0: kop3224 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 12:17:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Встроенное аудио - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after
a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1387908] Re: [udev] FIDO u2f security keys should be supported out of the box

@nicoo

thanks. I wonder if udev should recommend libu2f-udev (such that most
systems have it), or if it should be seeded into desktop common (such
that all destkop-like systems have it).

It would also need MIR, which should be simple enough.

Regard,

Dimitri.

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

Title:
  [udev] FIDO u2f security keys should be supported out of the box

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

Bug description:
  [Impact]

   * Users plugin U2F key and it does not work in Google Chrome

  [Test Case]

   * Have stock ubuntu install, without custom U2F rules or libu2f-host0
  installed

   * Use U2F factor authentication website e.g. google apps, github,
  yubico, etc.

   * Pluging in the key, should just work and complete U2F
  authentication instead of timing out

  [Regression Potential]

   * Should not conflict with libu2f-host0 udev rules which is where
  these are currently shipped

  FIDO u2f is an emerging standard for public-private cryptography based
  2nd factor authentication, which improves on OTP by mitigating
  phishing, man-in-the-middle attacks and reply attacks.

  Google Chrome supports u2f devices which are now widely available from
  Yubico (new premium neo Yubikeys and Security keys).

  However, udev rules are required to setup permissions to allow the
  web-browsers which are running as regular users to access the devices
  in question.

  E.g.:

  KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0664", GROUP="plugdev",
  ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0113|0114|0115|0116|0120"

  Something like that should be enabled by default, however probably not
  encode on the vendor/productid as other vendors will also make u2f
  devices.

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

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

[Touch-packages] [Bug 1730915] Re: mount overlayfs command in lxc-test-unpriv is missing a workdir assignment

2017-11-13 Thread Po-Hsu Lin

Patch merged.

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

Title:
  mount overlayfs command in lxc-test-unpriv is missing a workdir
  assignment

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  While running the lxc-test-unpriv test, it will complain about:

  $ sudo /usr/bin/lxc-test-unpriv 
  mount: wrong fs type, bad option, bad superblock on none,
 missing codepage or helper program, or other error

 In some cases useful info is found in syslog - try
 dmesg | tail or so.

  Check the dmesg output it will tell you that the mount option needs a workdir 
assignment as well:
  $ dmesg
  [89761.978272] overlayfs: missing 'workdir'

  This error does not affect the test result, but good to be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc-tests 2.0.8-0ubuntu1~16.04.2
  ProcVersionSignature: User Name 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Nov  8 08:50:31 2017
  KernLog:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1690163] Re: package gconf2-common 3.2.6-0ubuntu1 failed to install/upgrade: package gconf2-common is already installed and configured

2017-11-13 Thread dino99

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

** Package changed: gconf (Ubuntu) => dpkg (Ubuntu)

** This bug has been marked a duplicate of bug 545790
   package PACKAGE failed to install/upgrade: error writing to '': Success

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

Title:
  package gconf2-common 3.2.6-0ubuntu1 failed to install/upgrade:
  package gconf2-common is already installed and configured

Status in dpkg package in Ubuntu:
  New

Bug description:
  i was updating from 13 to 14

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gconf2-common 3.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-117.164-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-117-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.23
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: i386
  Date: Wed May 10 13:04:55 2017
  DuplicateSignature: package:gconf2-common:3.2.6-0ubuntu1:package 
gconf2-common is already installed and configured
  ErrorMessage: package gconf2-common is already installed and configured
  InstallationDate: Installed on 2017-05-10 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-0ubuntu1 failed to install/upgrade: 
package gconf2-common is already installed and configured
  UpgradeStatus: Upgraded to trusty on 2017-05-11 (0 days ago)

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

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

[Touch-packages] [Bug 1731867] Re: davmail 4.8.0.2479 reports System tray not avaiable in thread SWT

2017-11-13 Thread Peter Sylvester

There is no relation with tzdata. sorry, this was in the submission.

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

Title:
  davmail  4.8.0.2479 reports System tray not avaiable in thread SWT

Status in tzdata package in Ubuntu:
  New

Bug description:
  In 17.10:

  Exception in thread "SWT" java.lang.Error: System tray not available
at davmail.ui.tray.SwtGatewayTray$5.run(SwtGatewayTray.java:232)

  
  davmail_4.8.0.3-2488-1 seems to fix the problem

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

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

[Touch-packages] [Bug 1731610] Re: add --save option to apport-collect