date:20170817

This bug was fixed in the package lxc - 2.0.8-0ubuntu5

---
lxc (2.0.8-0ubuntu5) artful; urgency=medium

  * debian/patches/0012-gcc-7-workaround.patch: workaround for gcc-7 bug
that causes lxc to FTBFS. LP: #1711449. Closes: #853531.

 -- Tiago Stürmer Daitx   Thu, 17 Aug 2017
20:29:29 +

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

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

Title:
  [FTBFS] lxc build fails due to gcc-7

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc package in Debian:
  New

Bug description:
  Currently lxc FTBFS due to a GCC-7 bug.

  There's a upstream report for gcc-7 [1], but meanwhile lxc upstream
  has applied a workaround that fixes the build [1].

  cgroups/cgfsng.c: In function ‘cgfsng_create’:
  cgroups/cgfsng.c:1381:23: error: ‘__builtin___snprintf_chk’ output may be 
truncated before the last format character [-Werror=format-truncation=]
 snprintf(offset, 5, "-%d", idx);
 ^
  In file included from /usr/include/stdio.h:938:0,
   from cgroups/cgfsng.c:44:
  /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: 
‘__builtin___snprintf_chk’ output between 3 and 6 bytes into a destination of 
size 5
 return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
^~~~
  __bos (__s), __fmt, __va_arg_pack ());
  ~
  cc1: all warnings being treated as errors

  [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969
  [2] https://github.com/lxc/lxc/commit/66b66624fce21606d11f24f5b615776074d212ae

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

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

[Touch-packages] [Bug 1680045] Re: AbiWord opens 2 transparent windows on top in Unity8

** Summary changed:

- AbiWord opens 2 transparent windows on top
+ AbiWord opens 2 transparent windows on top in Unity8

** Changed in: canonical-devices-system-image
   Status: New => Won't Fix

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Incomplete

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

Title:
  AbiWord opens 2 transparent windows on top in Unity8

Status in Canonical System Image:
  Won't Fix
Status in abiword package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.04 Unity8

  AbiWord opens 2 transparent windows on top (see screenshot) and if
  closed while the transparent windows are opened it will leave a
  process running 160% cpu forever

  run abiword (without Xmir), close

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1680045/+subscriptions

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

[Touch-packages] [Bug 1710666] Re: No resolution until manually adding a nameserver to resolv.conf

Oh, sorry!
Not
$ sudo systemctl restart systemd-networkd


but
$ sudo systemctl restart systemd-resolved

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

Title:
  No resolution until manually adding a nameserver to resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  I have no resolution until I manually add a `nameserver 8.8.8.8` to
  `/run/resolvconf/resolv.conf`.

  And if `resolvconf` is not installed, I don't know how to add a
  nameserver. So I keep that installed.

  I'm using Network Manager and it should take care of adding
  nameservers.

  I don't know where what is going wrong.

  I'm willing to send any necessary info from this system.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 233-8ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Aug 14 18:58:10 2017
  InstallationDate: Installed on 2010-10-12 (2498 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Supermicro X10SRA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-13-generic 
root=/dev/mapper/root ro nomdmonddf nomdmonisw nomodeset
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-04-29 (107 days ago)
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10SRA
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X10SRA
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

[Touch-packages] [Bug 1710666] Re: No resolution until manually adding a nameserver to resolv.conf

Post the output of
$ sudo systemctl status systemd-resolved

And try:
$ sudo systemctl restart systemd-networkd
Will DNs resolution start working after it?

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

Title:
  No resolution until manually adding a nameserver to resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  I have no resolution until I manually add a `nameserver 8.8.8.8` to
  `/run/resolvconf/resolv.conf`.

  And if `resolvconf` is not installed, I don't know how to add a
  nameserver. So I keep that installed.

  I'm using Network Manager and it should take care of adding
  nameservers.

  I don't know where what is going wrong.

  I'm willing to send any necessary info from this system.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 233-8ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Aug 14 18:58:10 2017
  InstallationDate: Installed on 2010-10-12 (2498 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Supermicro X10SRA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-13-generic 
root=/dev/mapper/root ro nomdmonddf nomdmonisw nomodeset
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-04-29 (107 days ago)
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10SRA
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X10SRA
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

[Touch-packages] [Bug 1710666] Re: No resolution until manually adding a nameserver to resolv.conf

NetworkManager does not take care of DNS resolution, in Ubuntu 17.10
systemd-resolved does it, dnsmasq did it in older Ubuntu releases.

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

Title:
  No resolution until manually adding a nameserver to resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  I have no resolution until I manually add a `nameserver 8.8.8.8` to
  `/run/resolvconf/resolv.conf`.

  And if `resolvconf` is not installed, I don't know how to add a
  nameserver. So I keep that installed.

  I'm using Network Manager and it should take care of adding
  nameservers.

  I don't know where what is going wrong.

  I'm willing to send any necessary info from this system.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 233-8ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Aug 14 18:58:10 2017
  InstallationDate: Installed on 2010-10-12 (2498 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Supermicro X10SRA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-13-generic 
root=/dev/mapper/root ro nomdmonddf nomdmonisw nomodeset
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-04-29 (107 days ago)
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10SRA
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X10SRA
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

[Touch-packages] [Bug 1711474] Re: graphical session and network not start up due to root FS being mounted read-only

Upgraded to artful proposed, now NetworkManager does start, but the system 
still does not boot without
/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="rw"

I made btrfs check, btrfs rescue, btrfs balance, nothing helped.

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

Title:
  graphical session and network not start up due to root FS being
  mounted read-only

Status in systemd package in Ubuntu:
  New

Bug description:
  Kubuntu 17.10, fresh install
  $ systemctl --version
  systemd 233

  Graphical session (sddm.service), systemd-resolved.service and
  NetworkManager.service are not loaded due to system root being mounted
  read-only

  $ journalctl -b0
  авг 18 01:27:45 Kseniya-Desktop kernel: Command line: 
BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic 
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@

  This is the default kernel command line, ro means that the root filesystem 
must be mounted read-only, then fsck is believed to be permormed, after what 
the FS must be remounted rw (read-write)
  But in my system (Ubuntu 17.10) the /home is mouned rw, but the root is still 
ro.

  I added to /etc/default/grub:
  GRUB_CMDLINE_LINUX_DEFAULT="rw"

  Now my kernel command line is:
  авг 18 01:27:45 Kseniya-Desktop kernel: Command line: 
BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic 
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw

  No the root fs is mounted rw and sddm.service starts the graphical
  session automatically.

  BUT: 
  NetworkManager.service is not started automatically and should be started 
manually (sudo systemctl start NetworkManager)
  Due to network offline, network fileshares are not mounted.

  I also noticed that there is no dependency from fsck in -.mount, but
  there is in home.mount

  $ cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  #
  # / was on /dev/sdc1 during installation
  UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e /   btrfs   
subvol=@,defaults,compress=lzo 0   2
  # /home was on /dev/sdc1 during installation
  UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e /home   btrfs   
defaults,discard,compress=lzo,subvol=@home 0   3
  # swap was on /dev/sdc2 during installation
  UUID=cd2ba3e8-5ec9-49b3-aa2d-79082a8b8012 noneswapsw  
0   0

  --
  $ cat /run/systemd/generator/-.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=/
  What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e
  Type=btrfs
  Options=subvol=@,defaults,compress=lzo
  --

  $ cat /run/systemd/generator/home.mount
  # Automatically generated by systemd-fstab-generator

  [Unit]
  SourcePath=/etc/fstab
  Documentation=man:fstab(5) man:systemd-fstab-generator(8)
  Before=local-fs.target
  
Requires=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service
  
After=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service

  [Mount]
  Where=/home
  What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e
  Type=btrfs
  Options=defaults,discard,compress=lzo,subvol=@home

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 233-8ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Aug 18 01:30:46 2017
  InstallationDate: Installed on 2017-07-23 (25 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  MachineType: Gigabyte Technology Co., Ltd. GA-A75M-DS2
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no username)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic 
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: GA-A75M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd03/27/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-DS2:pvr:rvnGigabyteTechnologyCo.,Ltd.:

[Touch-packages] [Bug 1711474] Re: graphical session and network not start up due to root FS being mounted read-only

Forgot to wrte that I do
# mount -o remount,rw /
# systemctl restart sddm systemd-resolved NetworkManager 

and after that I get access to fully working graphical session (except
of network-dependant mounts)

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

Title:
  graphical session and network not start up due to root FS being
  mounted read-only

Status in systemd package in Ubuntu:
  New

Bug description:
  Kubuntu 17.10, fresh install
  $ systemctl --version
  systemd 233

  Graphical session (sddm.service), systemd-resolved.service and
  NetworkManager.service are not loaded due to system root being mounted
  read-only

  $ journalctl -b0
  авг 18 01:27:45 Kseniya-Desktop kernel: Command line: 
BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic 
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@

  This is the default kernel command line, ro means that the root filesystem 
must be mounted read-only, then fsck is believed to be permormed, after what 
the FS must be remounted rw (read-write)
  But in my system (Ubuntu 17.10) the /home is mouned rw, but the root is still 
ro.

  I added to /etc/default/grub:
  GRUB_CMDLINE_LINUX_DEFAULT="rw"

  Now my kernel command line is:
  авг 18 01:27:45 Kseniya-Desktop kernel: Command line: 
BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic 
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw

  No the root fs is mounted rw and sddm.service starts the graphical
  session automatically.

  BUT: 
  NetworkManager.service is not started automatically and should be started 
manually (sudo systemctl start NetworkManager)
  Due to network offline, network fileshares are not mounted.

  I also noticed that there is no dependency from fsck in -.mount, but
  there is in home.mount

  $ cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  #
  # / was on /dev/sdc1 during installation
  UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e /   btrfs   
subvol=@,defaults,compress=lzo 0   2
  # /home was on /dev/sdc1 during installation
  UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e /home   btrfs   
defaults,discard,compress=lzo,subvol=@home 0   3
  # swap was on /dev/sdc2 during installation
  UUID=cd2ba3e8-5ec9-49b3-aa2d-79082a8b8012 noneswapsw  
0   0

  --
  $ cat /run/systemd/generator/-.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=/
  What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e
  Type=btrfs
  Options=subvol=@,defaults,compress=lzo
  --

  $ cat /run/systemd/generator/home.mount
  # Automatically generated by systemd-fstab-generator

  [Unit]
  SourcePath=/etc/fstab
  Documentation=man:fstab(5) man:systemd-fstab-generator(8)
  Before=local-fs.target
  
Requires=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service
  
After=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service

  [Mount]
  Where=/home
  What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e
  Type=btrfs
  Options=defaults,discard,compress=lzo,subvol=@home

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 233-8ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Aug 18 01:30:46 2017
  InstallationDate: Installed on 2017-07-23 (25 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  MachineType: Gigabyte Technology Co., Ltd. GA-A75M-DS2
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no username)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic 
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: GA-A75M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd03/27/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-DS2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-DS

[Touch-packages] [Bug 1711474] [NEW] graphical session and network not start up due to root FS being mounted read-only

Public bug reported:

Kubuntu 17.10, fresh install
$ systemctl --version
systemd 233

Graphical session (sddm.service), systemd-resolved.service and
NetworkManager.service are not loaded due to system root being mounted
read-only

$ journalctl -b0
авг 18 01:27:45 Kseniya-Desktop kernel: Command line: 
BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic 
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@

This is the default kernel command line, ro means that the root filesystem must 
be mounted read-only, then fsck is believed to be permormed, after what the FS 
must be remounted rw (read-write)
But in my system (Ubuntu 17.10) the /home is mouned rw, but the root is still 
ro.

I added to /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="rw"

Now my kernel command line is:
авг 18 01:27:45 Kseniya-Desktop kernel: Command line: 
BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic 
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw

No the root fs is mounted rw and sddm.service starts the graphical
session automatically.

BUT: 
NetworkManager.service is not started automatically and should be started 
manually (sudo systemctl start NetworkManager)
Due to network offline, network fileshares are not mounted.

I also noticed that there is no dependency from fsck in -.mount, but
there is in home.mount

$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sdc1 during installation
UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e /   btrfs   
subvol=@,defaults,compress=lzo 0   2
# /home was on /dev/sdc1 during installation
UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e /home   btrfs   
defaults,discard,compress=lzo,subvol=@home 0   3
# swap was on /dev/sdc2 during installation
UUID=cd2ba3e8-5ec9-49b3-aa2d-79082a8b8012 noneswapsw
  0   0

--
$ cat /run/systemd/generator/-.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=/
What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e
Type=btrfs
Options=subvol=@,defaults,compress=lzo
--

$ cat /run/systemd/generator/home.mount
# Automatically generated by systemd-fstab-generator

[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=local-fs.target
Requires=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service
After=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service

[Mount]
Where=/home
What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e
Type=btrfs
Options=defaults,discard,compress=lzo,subvol=@home

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 233-8ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Aug 18 01:30:46 2017
InstallationDate: Installed on 2017-07-23 (25 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
MachineType: Gigabyte Technology Co., Ltd. GA-A75M-DS2
ProcEnviron:
 LANGUAGE=
 TERM=xterm-256color
 PATH=(custom, no username)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic 
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/27/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: GA-A75M-DS2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd03/27/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-DS2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-A75M-DS2
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** 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/1711474

Title:
  graphical session and network not start up due to root FS being
  mounted read-only

Status in systemd package in Ubuntu:
  New

Bug description:
  Kubuntu 17.10, fresh install
  $ systemctl --version
  systemd 233

  Graphical session (sddm.service), systemd-resolved.service and

[Touch-packages] [Bug 1709193] Please test proposed package

Hello Simon, or anyone else affected,

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

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, details of your
testing will help us make a better decision.

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

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

Title:
  Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

Status in gnutls26 package in Ubuntu:
  Invalid
Status in gnutls28 package in Ubuntu:
  Fix Released
Status in gnutls26 source package in Trusty:
  Fix Committed
Status in gnutls28 source package in Trusty:
  Won't Fix
Status in ssmtp source package in Trusty:
  Invalid
Status in gnutls26 source package in Xenial:
  Invalid
Status in gnutls28 source package in Xenial:
  Fix Committed
Status in ssmtp source package in Xenial:
  Invalid
Status in gnutls26 source package in Zesty:
  Invalid
Status in gnutls28 source package in Zesty:
  Fix Committed
Status in ssmtp source package in Zesty:
  Invalid
Status in gnutls26 source package in Artful:
  Invalid
Status in gnutls28 source package in Artful:
  Fix Released
Status in ssmtp source package in Artful:
  Invalid
Status in gnutls28 package in Debian:
  Fix Released

Bug description:
  [Impact]

  Applications using GnuTLS OpenSSL compat layer [1] are be unable to
  use modern TLS versions (1.1 and 1.2) when relying on the
  SSLv23_{client,server}_method functions.

  There is an industry-wide push to use modern TLS versions, see [2] and
  [3] for example.

  The proposed fix changes the compat layer to use GnuTLS' "NORMAL"
  priority [4] instead of hard-coding which protocol versions and
  ciphers to enable.

  [Test Case]

  1) Setup a mail submission server that uses StartTLS
  2) Setup sSMTP (uses GnuTLS OpenSSL compat layer) to relay
 through the mail relay using StartTLS
  3) Send an email while capturing with tcpdump/tshark
  4) Inspect the submission connection (TCP/587) and look for the protocol
 version negotiated by the client.

  Without the fix, you should see TLSv1.0. With the fix, it should be
  TLSv1.2.

  Please see the original issue description for more details.

  [Regression Potential]

  Regression risk should be low since it's a backport of a simple fix
  that landed in Debian in April 2017.

  [References]

  1: $ apt-cache rdepends libgnutls-openssl27
  libgnutls-openssl27
  Reverse Depends:
libgnutls-dev
libgnutls-dev
zoneminder
yaskkserv
tf5
ssmtp
snowdrop
sngrep
slrnpull
slrn
sipsak
macopix-gtk2
gnss-sdr
gkrellm
freewheeling
boinctui
iputils-ping

  2: https://lists.debian.org/debian-devel-announce/2017/08/msg4.html
  3: https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls
  4: https://gnutls.org/manual/html_node/Priority-Strings.html

  
  [Original issue description]

  sSMTP is limited to using TLSv1.0 and the "old" ciphers that come with
  it. Here's a packet capture when ssmtp connects to
  smtp.sdeziel.info:587 that offers TLSv1.0 and higher:

  $ tshark -ta -Vr submission.pcap | sed -n '/^Frame 14:/,/^Frame 15:/ p' | 
grep -E '^[[:space:]]+(Version|Cipher|Handshake Protocol)'
  Version: TLS 1.0 (0x0301)
  Handshake Protocol: Client Hello
  Version: TLS 1.0 (0x0301)
  Cipher Suites Length: 30
  Cipher Suites (15 suites)
  Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
  Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0041)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0084)
  Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0045)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0088)
  Cipher Suite: TLS_DHE_RSA_WITH_3DES_ED

[Touch-packages] [Bug 1709193] Please test proposed package

Hello Simon, or anyone else affected,

Accepted gnutls28 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/gnutls28/3.4.10-4ubuntu1.4 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: gnutls26 (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-trusty

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

Title:
  Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

Status in gnutls26 package in Ubuntu:
  Invalid
Status in gnutls28 package in Ubuntu:
  Fix Released
Status in gnutls26 source package in Trusty:
  Fix Committed
Status in gnutls28 source package in Trusty:
  Won't Fix
Status in ssmtp source package in Trusty:
  Invalid
Status in gnutls26 source package in Xenial:
  Invalid
Status in gnutls28 source package in Xenial:
  Fix Committed
Status in ssmtp source package in Xenial:
  Invalid
Status in gnutls26 source package in Zesty:
  Invalid
Status in gnutls28 source package in Zesty:
  Fix Committed
Status in ssmtp source package in Zesty:
  Invalid
Status in gnutls26 source package in Artful:
  Invalid
Status in gnutls28 source package in Artful:
  Fix Released
Status in ssmtp source package in Artful:
  Invalid
Status in gnutls28 package in Debian:
  Fix Released

Bug description:
  [Impact]

  Applications using GnuTLS OpenSSL compat layer [1] are be unable to
  use modern TLS versions (1.1 and 1.2) when relying on the
  SSLv23_{client,server}_method functions.

  There is an industry-wide push to use modern TLS versions, see [2] and
  [3] for example.

  The proposed fix changes the compat layer to use GnuTLS' "NORMAL"
  priority [4] instead of hard-coding which protocol versions and
  ciphers to enable.

  [Test Case]

  1) Setup a mail submission server that uses StartTLS
  2) Setup sSMTP (uses GnuTLS OpenSSL compat layer) to relay
 through the mail relay using StartTLS
  3) Send an email while capturing with tcpdump/tshark
  4) Inspect the submission connection (TCP/587) and look for the protocol
 version negotiated by the client.

  Without the fix, you should see TLSv1.0. With the fix, it should be
  TLSv1.2.

  Please see the original issue description for more details.

  [Regression Potential]

  Regression risk should be low since it's a backport of a simple fix
  that landed in Debian in April 2017.

  [References]

  1: $ apt-cache rdepends libgnutls-openssl27
  libgnutls-openssl27
  Reverse Depends:
libgnutls-dev
libgnutls-dev
zoneminder
yaskkserv
tf5
ssmtp
snowdrop
sngrep
slrnpull
slrn
sipsak
macopix-gtk2
gnss-sdr
gkrellm
freewheeling
boinctui
iputils-ping

  2: https://lists.debian.org/debian-devel-announce/2017/08/msg4.html
  3: https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls
  4: https://gnutls.org/manual/html_node/Priority-Strings.html

  
  [Original issue description]

  sSMTP is limited to using TLSv1.0 and the "old" ciphers that come with
  it. Here's a packet capture when ssmtp connects to
  smtp.sdeziel.info:587 that offers TLSv1.0 and higher:

  $ tshark -ta -Vr submission.pcap | sed -n '/^Frame 14:/,/^Frame 15:/ p' | 
grep -E '^[[:space:]]+(Version|Cipher|Handshake Protocol)'
  Version: TLS 1.0 (0x0301)
  Handshake Protocol: Client Hello
  Version: TLS 1.0 (0x0301)
  Cipher Suites Length: 30
  Cipher Suites (15 suites)
  Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
  Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0041)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0084)
  Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0045)

[Touch-packages] [Bug 1709193] Re: Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

Hello Simon, or anyone else affected,

Accepted gnutls28 into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gnutls28/3.5.6-4ubuntu4.2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

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

** Changed in: gnutls28 (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-zesty

** Changed in: gnutls28 (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

Status in gnutls26 package in Ubuntu:
  Invalid
Status in gnutls28 package in Ubuntu:
  Fix Released
Status in gnutls26 source package in Trusty:
  Fix Committed
Status in gnutls28 source package in Trusty:
  Won't Fix
Status in ssmtp source package in Trusty:
  Invalid
Status in gnutls26 source package in Xenial:
  Invalid
Status in gnutls28 source package in Xenial:
  Fix Committed
Status in ssmtp source package in Xenial:
  Invalid
Status in gnutls26 source package in Zesty:
  Invalid
Status in gnutls28 source package in Zesty:
  Fix Committed
Status in ssmtp source package in Zesty:
  Invalid
Status in gnutls26 source package in Artful:
  Invalid
Status in gnutls28 source package in Artful:
  Fix Released
Status in ssmtp source package in Artful:
  Invalid
Status in gnutls28 package in Debian:
  Fix Released

Bug description:
  [Impact]

  Applications using GnuTLS OpenSSL compat layer [1] are be unable to
  use modern TLS versions (1.1 and 1.2) when relying on the
  SSLv23_{client,server}_method functions.

  There is an industry-wide push to use modern TLS versions, see [2] and
  [3] for example.

  The proposed fix changes the compat layer to use GnuTLS' "NORMAL"
  priority [4] instead of hard-coding which protocol versions and
  ciphers to enable.

  [Test Case]

  1) Setup a mail submission server that uses StartTLS
  2) Setup sSMTP (uses GnuTLS OpenSSL compat layer) to relay
 through the mail relay using StartTLS
  3) Send an email while capturing with tcpdump/tshark
  4) Inspect the submission connection (TCP/587) and look for the protocol
 version negotiated by the client.

  Without the fix, you should see TLSv1.0. With the fix, it should be
  TLSv1.2.

  Please see the original issue description for more details.

  [Regression Potential]

  Regression risk should be low since it's a backport of a simple fix
  that landed in Debian in April 2017.

  [References]

  1: $ apt-cache rdepends libgnutls-openssl27
  libgnutls-openssl27
  Reverse Depends:
libgnutls-dev
libgnutls-dev
zoneminder
yaskkserv
tf5
ssmtp
snowdrop
sngrep
slrnpull
slrn
sipsak
macopix-gtk2
gnss-sdr
gkrellm
freewheeling
boinctui
iputils-ping

  2: https://lists.debian.org/debian-devel-announce/2017/08/msg4.html
  3: https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls
  4: https://gnutls.org/manual/html_node/Priority-Strings.html

  
  [Original issue description]

  sSMTP is limited to using TLSv1.0 and the "old" ciphers that come with
  it. Here's a packet capture when ssmtp connects to
  smtp.sdeziel.info:587 that offers TLSv1.0 and higher:

  $ tshark -ta -Vr submission.pcap | sed -n '/^Frame 14:/,/^Frame 15:/ p' | 
grep -E '^[[:space:]]+(Version|Cipher|Handshake Protocol)'
  Version: TLS 1.0 (0x0301)
  Handshake Protocol: Client Hello
  Version: TLS 1.0 (0x0301)
  Cipher Suites Length: 30
  Cipher Suites (15 suites)
  Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
  Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0041)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0084)
  Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
  Cip

[Touch-packages] [Bug 1710521] Re: New release 3.22.18

2017-08-17 Thread Sebastien Bacher

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  New release 3.22.18

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Hello,

  https://git.gnome.org/browse/gtk+/tag/?h=3.22.18

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgtk-3-0 3.22.17-0ubuntu1
  Uname: Linux 4.13.0-041300rc4-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug 13 20:47:51 2017
  InstallationDate: Installed on 2017-07-05 (39 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to artful on 2017-07-05 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1710521/+subscriptions

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

[Touch-packages] [Bug 1711449] Re: [FTBFS] lxc build fails due to gcc-7

2017-08-17 Thread Bug Watch Updater

** Changed in: lxc (Debian)
   Status: Unknown => New

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

Title:
  [FTBFS] lxc build fails due to gcc-7

Status in lxc package in Ubuntu:
  New
Status in lxc package in Debian:
  New

Bug description:
  Currently lxc FTBFS due to a GCC-7 bug.

  There's a upstream report for gcc-7 [1], but meanwhile lxc upstream
  has applied a workaround that fixes the build [1].

  cgroups/cgfsng.c: In function ‘cgfsng_create’:
  cgroups/cgfsng.c:1381:23: error: ‘__builtin___snprintf_chk’ output may be 
truncated before the last format character [-Werror=format-truncation=]
 snprintf(offset, 5, "-%d", idx);
 ^
  In file included from /usr/include/stdio.h:938:0,
   from cgroups/cgfsng.c:44:
  /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: 
‘__builtin___snprintf_chk’ output between 3 and 6 bytes into a destination of 
size 5
 return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
^~~~
  __bos (__s), __fmt, __va_arg_pack ());
  ~
  cc1: all warnings being treated as errors

  [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969
  [2] https://github.com/lxc/lxc/commit/66b66624fce21606d11f24f5b615776074d212ae

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

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

[Touch-packages] [Bug 1711472] [NEW] package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sorti

2017-08-17 Thread jo59112

Public bug reported:

Hello,
i want you say what this problem isn't today.
I had this problem with ubuntu16.10
And today i have this problem with this new system based on ubuntu.
I wish what you resolved this problem.
Jo

ProblemType: Package
DistroRelease: elementary 0.4.1
Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Aug 17 23:53:18 2017
ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 128
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to 
install/upgrade: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package loki third-party-packages

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

Title:
  package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to
  install/upgrade: le sous-processus script post-installation installé a
  retourné une erreur de sortie d'état 128

Status in gconf package in Ubuntu:
  New

Bug description:
  Hello,
  i want you say what this problem isn't today.
  I had this problem with ubuntu16.10
  And today i have this problem with this new system based on ubuntu.
  I wish what you resolved this problem.
  Jo

  ProblemType: Package
  DistroRelease: elementary 0.4.1
  Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Aug 17 23:53:18 2017
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 128
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to 
install/upgrade: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1711465] [NEW] IP stops returning to arp-scan when sshed into.

2017-08-17 Thread Scott Cohen

Public bug reported:

I posted this on the Ubuntu-MATE bug report before this
(https://bugs.launchpad.net/ubuntu-mate/+bug/1711460), but I don't know
how active that place is so I'm also going to post it here. I also don't
know if this is the right package to post this in, but since there is no
clear way to post bugs with ambiguous sources of problems, I am posting
here.

When I do a scan of my local network via the command arp-scan
--localnet, I find that the IP of the machine which has Ubuntu-MATE on
it shows up in the list of IPs brought back by arp-scan. But when I ssh
to that machine and then issue the command arp-scan --localnet from the
machine that I had sshed from, I find that the IP address of the
computer with Ubuntu-MATE on it is absent from the list. I expect the IP
address with the machine with Ubuntu-MATE to show up. I tested this with
other machines and operating systems and those still returned an IP
address when issued arp-scan --localnet. The Ubuntu-MATE machine was the
only one which didn't.

Description:Ubuntu Artful Aardvark (development branch)
Release:17.10

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.2-1ubuntu2
ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
Uname: Linux 4.11.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
Date: Thu Aug 17 14:19:46 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-01-07 (222 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
IpRoute:
 default via 192.168.1.1 dev wlp7s0 proto static metric 600 
 169.254.0.0/16 dev wlp7s0 scope link metric 1000 
 192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.96 metric 600
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile
 
 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to artful on 2017-08-11 (6 days ago)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
 wlp7s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Windows7Family 2  ea6b04bf-6ea5-4250-9783-f8df31fb090a  
/org/freedesktop/NetworkManager/ActiveConnection/3 
 enp6s0  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

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


** Tags: amd64 apport-bug arp-scan artful broadcast network ssh

** Attachment removed: "nmcli-con.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1711465/+attachment/4934447/+files/nmcli-con.txt

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

Title:
   IP stops returning to arp-scan when sshed into.

Status in network-manager package in Ubuntu:
  New

Bug description:
  I posted this on the Ubuntu-MATE bug report before this
  (https://bugs.launchpad.net/ubuntu-mate/+bug/1711460), but I don't
  know how active that place is so I'm also going to post it here. I
  also don't know if this is the right package to post this in, but
  since there is no clear way to post bugs with ambiguous sources of
  problems, I am posting here.

  When I do a scan of my local network via the command arp-scan
  --localnet, I find that the IP of the machine which has Ubuntu-MATE on
  it shows up in the list of IPs brought back by arp-scan. But when I
  ssh to that machine and then issue the command arp-scan --localnet
  from the machine that I had sshed from, I find that the IP address of
  the computer with Ubuntu-MATE on it is absent from the list. I expect
  the IP address with the machine with Ubuntu-MATE to show up. I tested
  this with other machines and operating systems and those still
  returned an IP address when issued arp-scan --localnet. The Ubuntu-
  MATE machine was the only one which didn't.

  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu2
  ProcVersionSignature:

[Touch-packages] [Bug 1709670] Re: logrotate never recovers if the statefile is corrupted

This bug was fixed in the package logrotate - 3.8.7-1ubuntu1.2

---
logrotate (3.8.7-1ubuntu1.2) trusty; urgency=medium

  * logrotate does not ever recover from a corrupted statefile (LP: #1709670)
- d/p/do-not-treat-failure-of-readState-as-fatal.patch
(Backported from commit b9d82003002c98370e4131a7e43c76afcd23306a)

 -- Eric Desrochers   Wed, 09 Aug 2017
15:55:36 -0400

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

Title:
  logrotate never recovers if the statefile is corrupted

Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate source package in Trusty:
  Fix Released
Status in logrotate source package in Xenial:
  Fix Released
Status in logrotate source package in Zesty:
  Fix Committed
Status in logrotate source package in Artful:
  Fix Released
Status in logrotate package in Debian:
  New

Bug description:
  [Impact]

  logrotate never recovers if the statefile is corrupted unless you
  remove it or fix the corruption by hand.

  Impact scenarios :

  - System could eventually run out of disk space on a separate
  partition if mounted in "/var" or specifically "/var/log" or even
  worst if "/var/log" is on the same partition as "/" it could create
  even more damage if by any chance the partition is running out of free
  space.

  - System keep updating the same files over and over, creating large
  size logfiles.

  - ...

  [Test Case]

  - Install logrotate
  - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate 
the statefile "var/lib/logrotate/status"
  - Modify "/var/lib/logrotate/status" by removing the first line in order to 
corrupt the file
  - Re-run "/etc/cron.daily/logrotate" and one will get the following error : 
"error: bad top line in state file /var/lib/logrotate/status" every time you 
run logrotate

  Unless you remove the statefile and start again or fix the corruption
  by hand.

   * Additionally, I will run the /path_to_source/test/test script as a
  dogfooding that does ~72 tests.

  [Regression Potential]

   * Risk of potential regression is low, and IMHO couldn't be worst
  than the actual situation where logrotate simply doesn't recover from
  a corrupt statefile.

   * The current patch does recover (after verification) and has been
  through some upstream CI validation, community feedbacks, et al.

   * Additionally, I will run the /path_to_source/test/test script as a
  dogfooding that does ~72 tests.

  [Other Info]

  * Upstream commit:
  
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a

  * Upstream bug:
  https://github.com/logrotate/logrotate/issues/45

  * Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592

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

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

[Touch-packages] [Bug 1709670] Re: logrotate never recovers if the statefile is corrupted

This bug was fixed in the package logrotate - 3.8.7-2ubuntu2.16.04.2

---
logrotate (3.8.7-2ubuntu2.16.04.2) xenial; urgency=medium

  * logrotate does not ever recover from a corrupted statefile (LP: #1709670)
- d/p/do-not-treat-failure-of-readState-as-fatal.patch
(Backported from commit b9d82003002c98370e4131a7e43c76afcd23306a)

 -- Eric Desrochers   Wed, 09 Aug 2017
16:02:21 -0400

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

** Changed in: logrotate (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  logrotate never recovers if the statefile is corrupted

Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate source package in Trusty:
  Fix Released
Status in logrotate source package in Xenial:
  Fix Released
Status in logrotate source package in Zesty:
  Fix Committed
Status in logrotate source package in Artful:
  Fix Released
Status in logrotate package in Debian:
  New

Bug description:
  [Impact]

  logrotate never recovers if the statefile is corrupted unless you
  remove it or fix the corruption by hand.

  Impact scenarios :

  - System could eventually run out of disk space on a separate
  partition if mounted in "/var" or specifically "/var/log" or even
  worst if "/var/log" is on the same partition as "/" it could create
  even more damage if by any chance the partition is running out of free
  space.

  - System keep updating the same files over and over, creating large
  size logfiles.

  - ...

  [Test Case]

  - Install logrotate
  - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate 
the statefile "var/lib/logrotate/status"
  - Modify "/var/lib/logrotate/status" by removing the first line in order to 
corrupt the file
  - Re-run "/etc/cron.daily/logrotate" and one will get the following error : 
"error: bad top line in state file /var/lib/logrotate/status" every time you 
run logrotate

  Unless you remove the statefile and start again or fix the corruption
  by hand.

   * Additionally, I will run the /path_to_source/test/test script as a
  dogfooding that does ~72 tests.

  [Regression Potential]

   * Risk of potential regression is low, and IMHO couldn't be worst
  than the actual situation where logrotate simply doesn't recover from
  a corrupt statefile.

   * The current patch does recover (after verification) and has been
  through some upstream CI validation, community feedbacks, et al.

   * Additionally, I will run the /path_to_source/test/test script as a
  dogfooding that does ~72 tests.

  [Other Info]

  * Upstream commit:
  
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a

  * Upstream bug:
  https://github.com/logrotate/logrotate/issues/45

  * Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592

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

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

[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

It was accidentally referenced in the zesty SRU.

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Won't Fix
Status in apt source package in Yakkety:
  Won't Fix
Status in apt source package in Zesty:
  Won't Fix

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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

[Touch-packages] [Bug 1709670] Update Released

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

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

Title:
  logrotate never recovers if the statefile is corrupted

Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate source package in Trusty:
  Fix Committed
Status in logrotate source package in Xenial:
  Fix Released
Status in logrotate source package in Zesty:
  Fix Committed
Status in logrotate source package in Artful:
  Fix Released
Status in logrotate package in Debian:
  New

Bug description:
  [Impact]

  logrotate never recovers if the statefile is corrupted unless you
  remove it or fix the corruption by hand.

  Impact scenarios :

  - System could eventually run out of disk space on a separate
  partition if mounted in "/var" or specifically "/var/log" or even
  worst if "/var/log" is on the same partition as "/" it could create
  even more damage if by any chance the partition is running out of free
  space.

  - System keep updating the same files over and over, creating large
  size logfiles.

  - ...

  [Test Case]

  - Install logrotate
  - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate 
the statefile "var/lib/logrotate/status"
  - Modify "/var/lib/logrotate/status" by removing the first line in order to 
corrupt the file
  - Re-run "/etc/cron.daily/logrotate" and one will get the following error : 
"error: bad top line in state file /var/lib/logrotate/status" every time you 
run logrotate

  Unless you remove the statefile and start again or fix the corruption
  by hand.

   * Additionally, I will run the /path_to_source/test/test script as a
  dogfooding that does ~72 tests.

  [Regression Potential]

   * Risk of potential regression is low, and IMHO couldn't be worst
  than the actual situation where logrotate simply doesn't recover from
  a corrupt statefile.

   * The current patch does recover (after verification) and has been
  through some upstream CI validation, community feedbacks, et al.

   * Additionally, I will run the /path_to_source/test/test script as a
  dogfooding that does ~72 tests.

  [Other Info]

  * Upstream commit:
  
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a

  * Upstream bug:
  https://github.com/logrotate/logrotate/issues/45

  * Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592

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

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

[Touch-packages] [Bug 1711449] Re: [FTBFS] lxc build fails due to gcc-7

2017-08-17 Thread Tiago Stürmer Daitx

** Patch added: "lxc_2.0.8-0ubuntu4_2.0.8-0ubuntu5.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1711449/+attachment/4934433/+files/lxc_2.0.8-0ubuntu4_2.0.8-0ubuntu5.debdiff

** Tags added: artful ftbfs patch

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

Title:
  [FTBFS] lxc build fails due to gcc-7

Status in lxc package in Ubuntu:
  New
Status in lxc package in Debian:
  Unknown

Bug description:
  Currently lxc FTBFS due to a GCC-7 bug.

  There's a upstream report for gcc-7 [1], but meanwhile lxc upstream
  has applied a workaround that fixes the build [1].

  cgroups/cgfsng.c: In function ‘cgfsng_create’:
  cgroups/cgfsng.c:1381:23: error: ‘__builtin___snprintf_chk’ output may be 
truncated before the last format character [-Werror=format-truncation=]
 snprintf(offset, 5, "-%d", idx);
 ^
  In file included from /usr/include/stdio.h:938:0,
   from cgroups/cgfsng.c:44:
  /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: 
‘__builtin___snprintf_chk’ output between 3 and 6 bytes into a destination of 
size 5
 return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
^~~~
  __bos (__s), __fmt, __va_arg_pack ());
  ~
  cc1: all warnings being treated as errors

  [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969
  [2] https://github.com/lxc/lxc/commit/66b66624fce21606d11f24f5b615776074d212ae

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

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

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

2017-08-17 Thread Martin Dünkelmann

Oh, is there already a bug report, where I can add my comment?

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in aptitude package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

@juliank are you sure? This bug is a won't fix, as this bug requested to
"revert back to doing both update & upgrade at peak time".

I believe no further actions are required on /this/ bug. Or did this bug
# got extra-referenced in some SRU?

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Won't Fix
Status in apt source package in Yakkety:
  Won't Fix
Status in apt source package in Zesty:
  Won't Fix

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

-- 
Mailing list: https://launchpad.net/~touch-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-08-17 Thread Ubuntu Foundations Team Bug Bot

The attachment "0001-Disable-fpectl-and-fPIC-on-Modules-_math.c.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 python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1638695

Title:
Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
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

Re: [Touch-packages] [Bug 1711428] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-upgrade.service execution

On Thu, Aug 17, 2017 at 07:59:00PM -, Jim Browne wrote:
> However, is juliank's note about the implementation of After= a concern
> w.r.t. how LP#1693361 was resovled?

I don't think so.  He's correct that the ordering doesn't guarantee that we
don't hit a conflict if the units wrap around and collide in the opposite
direction.  But I believe that locking code is part of the fix that landed.

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

Title:
  cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-
  upgrade.service execution

Status in cloud-init:
  Incomplete
Status in apt package in Ubuntu:
  Incomplete

Bug description:
  This is the same problem as https://bugs.launchpad.net/cloud-
  init/+bug/1693361, but with a different APT invoking service.  In this
  case it is apt-daily-upgrade.service.

  So, I guess add apt-daily-upgrade.service to the Before line in
  /lib/systemd/system/cloud-final.service along side apt-daily.service.

  Or wait for an APT fix.  Or retry APT commands when executing
  "packages:"

  Reporting this to save someone else trouble, but I think we'll be
  rolling back to Trusty at this point.  Hopefully the B LTS will have
  an alternative to systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1711428/+subscriptions

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

[Touch-packages] [Bug 1711204] Re: Remove ubuntu-ui-toolkit from the archive

2017-08-17 Thread Dmitry Shachnev

@Dimitri: url-dispatcher has quite a lot reverse-dependencies itself:

* address-book-service  (for liburl-dispatcher1)
* indicator-bluetooth   (for liburl-dispatcher1)
* indicator-datetime(for liburl-dispatcher1)
* indicator-keyboard(for liburl-dispatcher1)
* indicator-network (for liburl-dispatcher1)
* indicator-power   (for liburl-dispatcher1)
* indicator-session (for liburl-dispatcher1)
* indicator-sound   (for liburl-dispatcher1)
* indicator-transfer-buteo  (for liburl-dispatcher1)
* libertine-scope   (for liburl-dispatcher1)
* qtmir-android [amd64 arm64 armhf i386]  (for liburl-dispatcher1)
* qtmir-desktop [amd64 arm64 armhf i386]  (for liburl-dispatcher1)
* ubuntu-application-api3-desktop [amd64 arm64 armhf i386]  (for 
liburl-dispatcher1)
* ubuntu-application-api3-touch [amd64 arm64 armhf i386]  (for 
liburl-dispatcher1)
* ubuntu-printing-app   (for liburl-dispatcher1)
* ubuntu-ui-toolkit-autopilot [amd64 arm64 armhf i386 ppc64el]  (for 
url-dispatcher-tools)
* unity-greeter-session-broadcast  (for url-dispatcher-tools)

I am not sure what to do with i.e. qtmir-* — I guess we don’t want these
to be removed? Maybe fixing the QML file will be easier?

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

Title:
  Remove ubuntu-ui-toolkit from the archive

Status in checkbox package in Ubuntu:
  Invalid
Status in libertine package in Ubuntu:
  New
Status in notes-app package in Ubuntu:
  New
Status in ubuntu-filemanager-app package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in ubuntu-printing-app package in Ubuntu:
  New
Status in ubuntu-push-qml package in Ubuntu:
  New
Status in ubuntu-settings-components package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in ubuntu-ui-extras package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in ubuntu-ui-toolkit-gles package in Ubuntu:
  New
Status in unity-webapps-qml package in Ubuntu:
  New
Status in url-dispatcher package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The Qt transition is currently blocked by ubuntu-ui-toolkit because
  the version of ubuntu-ui-toolkit in the archive uses Qt 5.7.1 private
  headers that have been since deprecated. ubuntu-ui-toolkit should be
  removed from the archive (unless anyone still needs it, please do make
  your case) and all of it's reverse dependencies (marked as affected on
  this bug report) should either be ported to use native Qt libraries or
  removed from the archive. This is blocking the Qt 5.9 transition, so
  it should be done promptly.

  Full list of reverse dependencies:

  * checkbox-converged(for qml-module-ubuntu-components)
  * libertine-qt-common   (for qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * notes-app (for qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * notes-app-autopilot   (for ubuntu-ui-toolkit-autopilot)
  * qml-module-ubuntu-components-gles [amd64 i386]  (for 
qml-module-ubuntu-components-labs)
  * qml-module-ubuntu-components-gles [amd64 i386]  (for 
ubuntu-ui-toolkit-theme)
  * qml-module-ubuntu-components-labs-gles [amd64 i386]  (for 
ubuntu-ui-toolkit-theme)
  * qml-module-ubuntu-settings-components  (for qml-module-ubuntu-components)
  * qml-module-ubuntu-ui-extras-browser [amd64 arm64 armhf i386]  (for 
qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * qml-module-ubuntu-web [amd64 arm64 armhf i386]  (for 
qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * qtdeclarative5-ubuntu-push-plugin  (for 
qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * qtdeclarative5-ubuntu-ui-extras0.2  (for qml-module-ubuntu-components)
  * ubuntu-filemanager-app(for qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * ubuntu-filemanager-app-autopilot  (for ubuntu-ui-toolkit-autopilot)
  * ubuntu-keyboard-autopilot (for ubuntu-ui-toolkit-autopilot)
  * ubuntu-keyboard-data  (for qml-module-ubuntu-components)
  * ubuntu-printing-app   (for qml-module-ubuntu-components)
  * ubuntu-system-settings(for qml-module-ubuntu-components)
  * ubuntu-system-settings-autopilot  (for ubuntu-ui-toolkit-autopilot)
  * ubuntu-system-settings-online-accounts  (for qml-module-ubuntu-components)
  * unity-webapps-qml [amd64 arm64 armhf i386]  (for 
qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * url-dispatcher(for qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * webapp-container [amd64 arm64 armhf i386]  (for 
qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * webapp-container-autopilot(for ubuntu-ui-toolkit-autopilot)
  * webbrowser-app [amd64 arm64 armhf i386]  (for 
qtdeclarative5-u

[Touch-packages] [Bug 1711449] [NEW] [FTBFS] lxc build fails due to gcc-7

2017-08-17 Thread Tiago Stürmer Daitx

Public bug reported:

Currently lxc FTBFS due to a GCC-7 bug.

There's a upstream report for gcc-7 [1], but meanwhile lxc upstream has
applied a workaround that fixes the build [1].

cgroups/cgfsng.c: In function ‘cgfsng_create’:
cgroups/cgfsng.c:1381:23: error: ‘__builtin___snprintf_chk’ output may be 
truncated before the last format character [-Werror=format-truncation=]
   snprintf(offset, 5, "-%d", idx);
   ^
In file included from /usr/include/stdio.h:938:0,
 from cgroups/cgfsng.c:44:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: 
‘__builtin___snprintf_chk’ output between 3 and 6 bytes into a destination of 
size 5
   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  ^~~~
__bos (__s), __fmt, __va_arg_pack ());
~
cc1: all warnings being treated as errors

[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969
[2] https://github.com/lxc/lxc/commit/66b66624fce21606d11f24f5b615776074d212ae

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

** Affects: lxc (Debian)
 Importance: Unknown
 Status: Unknown

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

** Also affects: lxc (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853531
   Importance: Unknown
   Status: Unknown

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

Title:
  [FTBFS] lxc build fails due to gcc-7

Status in lxc package in Ubuntu:
  New
Status in lxc package in Debian:
  Unknown

Bug description:
  Currently lxc FTBFS due to a GCC-7 bug.

  There's a upstream report for gcc-7 [1], but meanwhile lxc upstream
  has applied a workaround that fixes the build [1].

  cgroups/cgfsng.c: In function ‘cgfsng_create’:
  cgroups/cgfsng.c:1381:23: error: ‘__builtin___snprintf_chk’ output may be 
truncated before the last format character [-Werror=format-truncation=]
 snprintf(offset, 5, "-%d", idx);
 ^
  In file included from /usr/include/stdio.h:938:0,
   from cgroups/cgfsng.c:44:
  /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: 
‘__builtin___snprintf_chk’ output between 3 and 6 bytes into a destination of 
size 5
 return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
^~~~
  __bos (__s), __fmt, __va_arg_pack ());
  ~
  cc1: all warnings being treated as errors

  [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969
  [2] https://github.com/lxc/lxc/commit/66b66624fce21606d11f24f5b615776074d212ae

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

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

[Touch-packages] [Bug 1711428] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-upgrade.service execution

2017-08-17 Thread Jim Browne

> So I think this is something that you will want to fix in your image
> mastering scripts.

I agree and am fine with this being marked INVALID.

However, is juliank's note about the implementation of After= a concern
w.r.t. how LP#1693361 was resovled?

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

Title:
  cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-
  upgrade.service execution

Status in cloud-init:
  Incomplete
Status in apt package in Ubuntu:
  Incomplete

Bug description:
  This is the same problem as https://bugs.launchpad.net/cloud-
  init/+bug/1693361, but with a different APT invoking service.  In this
  case it is apt-daily-upgrade.service.

  So, I guess add apt-daily-upgrade.service to the Before line in
  /lib/systemd/system/cloud-final.service along side apt-daily.service.

  Or wait for an APT fix.  Or retry APT commands when executing
  "packages:"

  Reporting this to save someone else trouble, but I think we'll be
  rolling back to Trusty at this point.  Hopefully the B LTS will have
  an alternative to systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1711428/+subscriptions

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

Re: [Touch-packages] [Bug 1711428] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-upgrade.service execution

On Thu, Aug 17, 2017 at 07:20:20PM -, Jim Browne wrote:
> Hmmm.  I confirm what you see.

> I think this problem is arising because we have Packer run (due to 
> LP#1693361):
> systemctl disable apt-daily.service
> systemctl disable apt-daily.timer

> when building the AMI.

> I guess if apt-daily.service is disabled the Before is not transitive
> from cloud-init to apt-daily-upgrade via apt-daily?  Not seeing anything
> definitive in the docs after a quick glance.

Correct.  Before/After only establishes ordering between enabled services
and is ignored for services that are not enabled.

Fixing this to enforce that apt-daily.service and apt-daily-upgrade.service
are both always enabled/disabled together would be done by adding
'Requires=apt-daily.service' to apt-daily-upgrade.service.  But I think that
is too strict, because one may legitimately choose to disable only one of
the two services for some reason.

So I think this is something that you will want to fix in your image
mastering scripts.

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

Title:
  cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-
  upgrade.service execution

Status in cloud-init:
  Incomplete
Status in apt package in Ubuntu:
  Incomplete

Bug description:
  This is the same problem as https://bugs.launchpad.net/cloud-
  init/+bug/1693361, but with a different APT invoking service.  In this
  case it is apt-daily-upgrade.service.

  So, I guess add apt-daily-upgrade.service to the Before line in
  /lib/systemd/system/cloud-final.service along side apt-daily.service.

  Or wait for an APT fix.  Or retry APT commands when executing
  "packages:"

  Reporting this to save someone else trouble, but I think we'll be
  rolling back to Trusty at this point.  Hopefully the B LTS will have
  an alternative to systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1711428/+subscriptions

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

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

Different issue, Martin, I only fixed the update-notifier task so far.

[Impact]
Cosmetic. Warnings when installing packages using update-notifier downloading 
stuff

[Test case]

Install flashplugin-installer with apt and check that the output does
not contain a message like this:

W: Can't drop privileges for downloading as file '...' couldn't be
accessed by user '_apt'

[Regression Potential]

It just chowns /var/lib/update-notifier/package-data-downloads/partial/
to _apt:root, there should not be any regression.

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in aptitude package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1559482] Re: add-apt-repository manpage does not mention new -u option

This bug was fixed in the package software-properties - 0.96.24.15

---
software-properties (0.96.24.15) artful; urgency=medium

  [Adam Collard]
  * debian/manpages/add-apt-repository.1: Documented --update option
(LP: #1559482)

 -- Brian Murray   Wed, 16 Aug 2017 09:25:36 -0700

** Changed in: software-properties (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  add-apt-repository manpage does not mention new -u option

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  The add-apt-repository tool has apparently gained a new option to
  update the package cache. However, the manpage does not reflect this
  (as seen on http://manpages.ubuntu.com/manpages/wily/en/man1/add-apt-
  repository.1.html or
  http://manpages.ubuntu.com/manpages/xenial/en/man1/add-apt-
  repository.1.html). While the tool's own help text does mention it,
  this should be documented in the manpage as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: software-properties-common 0.96.13
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 19 21:07:41 2016
  InstallationDate: Installed on 2016-02-01 (47 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1711428] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-upgrade.service execution

Not that if B has After=A does not imply that the two don't run at the
same time. If B is already running, A will be started as well. That's
the reason why we added a lock file in apt:

if [ "$1" = "lock_is_held" ]; then
shift
else
# Maintain a lock on fd 3, so we can't run the script twice at the same
# time.
eval $(apt-config shell StateDir Dir::State/d)
exec 3>${StateDir}/daily_lock
if ! flock -w 3600 3; then
echo "E: Could not acquire lock" >&2
exit 1
fi

# We hold the lock.  Rerun this script as a child process, which
# can run without propagating an extra fd to all of its children.
"$0" lock_is_held "$@" 3>&-
exit $?
fi

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

Title:
  cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-
  upgrade.service execution

Status in cloud-init:
  Incomplete
Status in apt package in Ubuntu:
  Incomplete

Bug description:
  This is the same problem as https://bugs.launchpad.net/cloud-
  init/+bug/1693361, but with a different APT invoking service.  In this
  case it is apt-daily-upgrade.service.

  So, I guess add apt-daily-upgrade.service to the Before line in
  /lib/systemd/system/cloud-final.service along side apt-daily.service.

  Or wait for an APT fix.  Or retry APT commands when executing
  "packages:"

  Reporting this to save someone else trouble, but I think we'll be
  rolling back to Trusty at this point.  Hopefully the B LTS will have
  an alternative to systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1711428/+subscriptions

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

[Touch-packages] [Bug 1680045] Re: AbiWord opens 2 transparent windows on top

2017-08-17 Thread Simon Quigley

Hello,

Is this still a problem you have today? I am unable to reproduce this on
a Lubuntu 17.04 install.

If you are still having this problem, please feel free to re-open this
bug.

Thank you!

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

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

Title:
  AbiWord opens 2 transparent windows on top

Status in Canonical System Image:
  New
Status in abiword package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 Unity8

  AbiWord opens 2 transparent windows on top (see screenshot) and if
  closed while the transparent windows are opened it will leave a
  process running 160% cpu forever

  run abiword (without Xmir), close

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1680045/+subscriptions

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

[Touch-packages] [Bug 1711428] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-upgrade.service execution

2017-08-17 Thread Jim Browne

Hmmm.  I confirm what you see.

I think this problem is arising because we have Packer run (due to LP#1693361):
systemctl disable apt-daily.service
systemctl disable apt-daily.timer

when building the AMI.

I guess if apt-daily.service is disabled the Before is not transitive
from cloud-init to apt-daily-upgrade via apt-daily?  Not seeing anything
definitive in the docs after a quick glance.

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

Title:
  cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-
  upgrade.service execution

Status in cloud-init:
  Incomplete
Status in apt package in Ubuntu:
  Incomplete

Bug description:
  This is the same problem as https://bugs.launchpad.net/cloud-
  init/+bug/1693361, but with a different APT invoking service.  In this
  case it is apt-daily-upgrade.service.

  So, I guess add apt-daily-upgrade.service to the Before line in
  /lib/systemd/system/cloud-final.service along side apt-daily.service.

  Or wait for an APT fix.  Or retry APT commands when executing
  "packages:"

  Reporting this to save someone else trouble, but I think we'll be
  rolling back to Trusty at this point.  Hopefully the B LTS will have
  an alternative to systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1711428/+subscriptions

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

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

2017-08-17 Thread Martin Dünkelmann

If https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template is the
right one:

[Impact]

Updating packets via synaptic.
Befor they start OR after fonoshing the installing, the errir appears.

"W: Download is performed unsandboxed as root as file
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. -
pkgAcquire::Run (13: Keine Berechtigung)"

Ubuntu Mate x64 17.04
Synaptic 0.84.2

[Test Case]

Start synaptic.
Update the repositorys.
Go into the updates section.
Double click on every package, which can be updated.
Click on "apply" to install the updates.

[Regression Potential]

Don't know.

[Other Info]
 
Don't know

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in aptitude package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1711428] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-upgrade.service execution

The apt-daily-upgrade service already declares itself to be 'After=apt-
daily.service'.  So there should be strict sequencing here of cloud-
final.service -> apt-daily.service -> apt-daily-upgrade.service.  If
that's not happening, this warrants analysis to understand why so that
it can be fixed in the apt package directly rather than adding more
relationships to the cloud-init unit.

** Changed in: cloud-init
   Status: New => Incomplete

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

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

** Changed in: apt (Ubuntu)
   Importance: Undecided => High

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

Title:
  cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-
  upgrade.service execution

Status in cloud-init:
  Incomplete
Status in apt package in Ubuntu:
  Incomplete

Bug description:
  This is the same problem as https://bugs.launchpad.net/cloud-
  init/+bug/1693361, but with a different APT invoking service.  In this
  case it is apt-daily-upgrade.service.

  So, I guess add apt-daily-upgrade.service to the Before line in
  /lib/systemd/system/cloud-final.service along side apt-daily.service.

  Or wait for an APT fix.  Or retry APT commands when executing
  "packages:"

  Reporting this to save someone else trouble, but I think we'll be
  rolling back to Trusty at this point.  Hopefully the B LTS will have
  an alternative to systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1711428/+subscriptions

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

[Touch-packages] [Bug 1624378] Re: apt-key net-update should use trusted.gpg.d/

I think we reached somewhat of an agreement that net-update is a bad
idea and should not be done. It also depends on gnupg.

We should eventually consider developing something else, but I'm not
sure how that would look like. Currently, there is no way to revoke keys
except through packages, basically, which is a security issue. We need
to provide signed keyfiles on different locations that apt can download
so an attacker cannot use a broken key and MITM exisiting repositories
forever.

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

Title:
  apt-key net-update should use trusted.gpg.d/

Status in apt package in Ubuntu:
  Won't Fix

Bug description:
  apt-key net-update for the new world order

  /etc/apt/trusted.gpg is not longer preffered location for key updates.

  Instead, individual opengpg packets of exported public keys should be
  placed in /etc/apt/trusted.gpg.d

  Debian has already migrated to placing the keys there.

  To comply with /etc/apt/trusted.gpg.d structure, instead of updating
  the keys in the /etc/apt/trusted.gpg, imho apt-key net-update should
  download and place a /etc/apt/trusted.gpg.d/ubuntu-archive-
  netupdate.gpg key.

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

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

[Touch-packages] [Bug 1624378] Re: apt-key net-update should use trusted.gpg.d/

I think we reached somewhat of an agreement that net-update is a bad
idea and should not be done. It also depends on gnupg.

We should eventually consider developing something else, but I'm not
sure how that would look like. Currently, there is no way to revoke keys
except through packages, basically, which is a security issue. We need
to provide signed keyfiles on different locations that apt can download
so an attacker cannot use a broken key and MITM exisiting repositories
forever.

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

Title:
  apt-key net-update should use trusted.gpg.d/

Status in apt package in Ubuntu:
  Won't Fix

Bug description:
  apt-key net-update for the new world order

  /etc/apt/trusted.gpg is not longer preffered location for key updates.

  Instead, individual opengpg packets of exported public keys should be
  placed in /etc/apt/trusted.gpg.d

  Debian has already migrated to placing the keys there.

  To comply with /etc/apt/trusted.gpg.d structure, instead of updating
  the keys in the /etc/apt/trusted.gpg, imho apt-key net-update should
  download and place a /etc/apt/trusted.gpg.d/ubuntu-archive-
  netupdate.gpg key.

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

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

[Touch-packages] [Bug 1642353] Re: package virtualbox-ext-pack 5.1.6-2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

No, that's working fine. If the postinst script exits with an error, the
installation fails. If that were part of a big upgrade, this could break
systems.  So I am reassigning this back, but closing it as 'Opinion', as
there really is nothing that can be done here.

** Package changed: apt (Ubuntu) => virtualbox-ext-pack (Ubuntu)

** Changed in: virtualbox-ext-pack (Ubuntu)
   Status: New => Opinion

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

Title:
  package virtualbox-ext-pack 5.1.6-2 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in virtualbox-ext-pack package in Ubuntu:
  Opinion

Bug description:
  VirtualBox and "extension pack" are working as a charm, this is not a
  but about package virtualbox-ext-pack.

  **This is a something to fix on the crash-reporter process**

  I have pressed CTRL+C or something like that when the installation of
  package virtualbox-ext-pack was displaying me the PUEL licence. And
  the crash-reporter thought I had a problem while installing this
  package. I just wanted to quit the installer (sudo apt install).

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: virtualbox-ext-pack 5.1.6-2
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   virtualbox-ext-pack:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Nov 16 16:51:59 2016
  DpkgTerminalLog:
   Preparing to unpack .../virtualbox-ext-pack_5.1.6-2_all.deb ...
   User did not accept the license.
   [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/virtualbox-ext-pack_5.1.6-2_all.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2016-09-08 (69 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160907)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: virtualbox-ext-pack
  Title: package virtualbox-ext-pack 5.1.6-2 failed to install/upgrade: 
subprocess new pre-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/virtualbox-ext-pack/+bug/1642353/+subscriptions

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

[Touch-packages] [Bug 1682993] Re: package grub-common 2.02~beta2-36ubuntu3.9 failed to install/upgrade: package grub-common is already installed and configured

Probably fixed in zesty or newer with the huge installation ordering
changes, it mostly configures all pending ones in one go now.

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

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

Title:
  package grub-common 2.02~beta2-36ubuntu3.9 failed to install/upgrade:
  package grub-common is already installed and configured

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  I suddenly started getting an error after booting into Ubuntu Desktop.
  Don't really know why Grub is coming up since I am single booting into
  ubuntu with no other OS partitions installed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: grub-common 2.02~beta2-36ubuntu3.9
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Apr 14 22:11:31 2017
  DuplicateSignature:
   package:grub-common:2.02~beta2-36ubuntu3.9
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package chromium-codecs-ffmpeg-extra (--configure):
package chromium-codecs-ffmpeg-extra is already installed and configured
  ErrorMessage: package grub-common is already installed and configured
  InstallationDate: Installed on 2017-03-31 (15 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=b642098a-ea6b-4eb8-bb71-a9524c61be72 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: grub2
  Title: package grub-common 2.02~beta2-36ubuntu3.9 failed to install/upgrade: 
package grub-common is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1631983] Re: package libopencv-gpu2.4v5 (not installed) failed to install/upgrade: no package named 'libopencv-gpu2.4v5' is installed, cannot configure

It's likely this was fixed in zesty and newer, so I'm closing this. It
was a fairly special situation anyway with the huge C++ transition - APT
is not (cannot be) perfect.

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

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

Title:
  package libopencv-gpu2.4v5 (not installed) failed to install/upgrade:
  no package named 'libopencv-gpu2.4v5' is installed, cannot configure

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  actualicé la versión de ubuntu y han salido muchos errores

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libopencv-gpu2.4v5 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Oct  8 18:40:24 2016
  DuplicateSignature:
   package:libopencv-gpu2.4v5:(not installed)
   Setting up python-opencv (2.4.9.1+dfsg-1.5ubuntu1) ...
   dpkg: error processing package libopencv-gpu2.4v5 (--configure):
no package named 'libopencv-gpu2.4v5' is installed, cannot configure
  ErrorMessage: no package named 'libopencv-gpu2.4v5' is installed, cannot 
configure
  InstallationDate: Installed on 2016-05-05 (157 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: opencv
  Title: package libopencv-gpu2.4v5 (not installed) failed to install/upgrade: 
no package named 'libopencv-gpu2.4v5' is installed, cannot configure
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (1 days ago)

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

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

[Touch-packages] [Bug 1676526] Re: package linux-image-4.4.0-70-generic 4.4.0-70.91 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2

Broken system (missing apt.conf.d), as bdmurray found out in previous
comment, so not a bug.

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

Title:
  package linux-image-4.4.0-70-generic 4.4.0-70.91 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 2

Status in apt package in Ubuntu:
  Invalid

Bug description:
  I don't know. It was updating automaticaly.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-70-generic 4.4.0-70.91
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laura  1790 F pulseaudio
  Date: Mon Mar 27 14:06:53 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
  HibernationDevice: RESUME=UUID=cc29bae7-32f4-4568-9f2b-65bda3c1539d
  InstallationDate: Installed on 2016-05-31 (300 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic 
root=UUID=d0f34ed8-f890-4911-be6b-191a080342f7 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.8
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: apt
  Title: package linux-image-4.4.0-70-generic 4.4.0-70.91 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.90
  dmi.board.name: H61M-VG3
  dmi.board.vendor: ASRock
  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.:bvrP1.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-VG3:rvr: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.

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

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

[Touch-packages] [Bug 1644244] Re: Extraneous files left in apt config directories

We now ignore .ucf-dist files. The ".bck" is your problem, that's not
supported, and never will be (use .bak, .save, .orig instead).

apt-pkg/init.cc:   Cnf.Set("Dir::Ignore-Files-Silently::", "~$");
apt-pkg/init.cc:   Cnf.Set("Dir::Ignore-Files-Silently::", "\\.disabled$");
apt-pkg/init.cc:   Cnf.Set("Dir::Ignore-Files-Silently::", "\\.bak$");
apt-pkg/init.cc:   Cnf.Set("Dir::Ignore-Files-Silently::", "\\.dpkg-[a-z]+$");
apt-pkg/init.cc:   Cnf.Set("Dir::Ignore-Files-Silently::", "\\.ucf-[a-z]+$");
apt-pkg/init.cc:   Cnf.Set("Dir::Ignore-Files-Silently::", "\\.save$");
apt-pkg/init.cc:   Cnf.Set("Dir::Ignore-Files-Silently::", "\\.orig$");
apt-pkg/init.cc:   Cnf.Set("Dir::Ignore-Files-Silently::", "\\.distUpgrade$");


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

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

Title:
  Extraneous files left in apt config directories

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  N: Ignoring file '20auto-upgrades.ucf-dist' in directory 
'/etc/apt/apt.conf.d/' as it has an invalid filename extension
  N: Ignoring file 'getdeb.list.bck' in directory '/etc/apt/sources.list.d/' as 
it has an invalid filename extension
  E: The package secondlife needs to be reinstalled, but I can't find an 
archive for it.
  multiverse restricted main' #Added by software-properties
  kimbro-vargas@kimbro-vargas-HP-Pavilion-dv5-Notebook-PC:~$ sudo dpkg --audit
  The following packages are in a mess due to serious problems during
  installation.  They must be reinstalled for them (and any packages
  that depend on them) to function properly:
   secondlife   SecondLife client

  how do I fix it

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

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

[Touch-packages] [Bug 1667569] Re: package linux-image-4.4.0-64-generic 4.4.0-64.85 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2

Your system is broken, it seems you removed /etc/apt/apt.conf.d/

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

Title:
  package linux-image-4.4.0-64-generic 4.4.0-64.85 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 2

Status in apt package in Ubuntu:
  Invalid

Bug description:
  my update option in not working give error message W: Unable to read
  /etc/apt/apt.conf.d/ - DirectoryExists (2: No such file or directory)
  and my wifi option not came how to fix it

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  agnisys03   2084 F pulseaudio
  Date: Thu Feb 23 23:35:05 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
  HibernationDevice: RESUME=UUID=e7184cb7-23c1-4872-afda-17a379043dea
  InstallationDate: Installed on 2016-03-12 (348 days ago)
  InstallationMedia: It
  IwConfig:
   enx64d4da695796  no wireless extensions.
   
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: ASUSTeK Computer Inc. U56E
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=9e60c12c-47c3-42c7-8d17-f6bc68d7897b ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.7
  RfKill:
   0: i2400m-usb:1-1.1:1.0: WiMAX
Soft blocked: yes
Hard blocked: no
  SourcePackage: apt
  Title: package linux-image-4.4.0-64-generic 4.4.0-64.85 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U56E.213
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U56E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU56E.213:bd12/21/2011:svnASUSTeKComputerInc.:pnU56E:pvr1.0:rvnASUSTeKComputerInc.:rnU56E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: U56E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Touch-packages] [Bug 1674568] Re: depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such file or directory

Apparently you have the kernel installed but somehow deleted all its
modules.

** Package changed: apt (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1674568

Title:
  depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic:
  No such file or directory

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Please affect that report to the real package; i've chosen apt by
  default as i've no idea about the faulty one.

  Doing some daily upgrades as usual, and have seen that curious error
  while setting 'initramfs':

  Setting up linux-firmware (1.164) ...
  update-initramfs: Generating /boot/initrd.img-4.10.0-14-generic
  update-initramfs: Generating /boot/initrd.img-4.10.0-13-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-25-generic
  WARNING: missing /lib/modules/4.8.0-25-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No 
such file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.order: No such 
file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.builtin: No 
such file or directory
  update-initramfs: Generating /boot/initrd.img-4.8.0-0-generic
  WARNING: missing /lib/modules/4.8.0-0-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-0-generic: No such 
file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.order: No such 
file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.builtin: No 
such file or directory

  That ZZ installation indeed only has 4.10 kernels installed, and is
  often checked for cleaning (autoremove/bleachbit). Packages are always
  purged when removed.

  So i wonder why and which process/script has left a crappy /boot/ list
  of initrd.img-4.8* to produce the errors above.

  oem@u64:~$ ls -la /boot/
  total 142448
  drwxr-xr-x  4 root root 4096 Mar 21 06:24 .
  drwxr-xr-x 24 root root 4096 Mar 20 19:13 ..
  -rw-r--r--  1 root root  1442575 Mar  9 14:16 abi-4.10.0-13-generic
  -rw-r--r--  1 root root  1442782 Mar  9 21:30 abi-4.10.0-14-generic
  -rw-r--r--  1 root root   204890 Mar  9 14:16 config-4.10.0-13-generic
  -rw-r--r--  1 root root   204890 Mar  9 21:30 config-4.10.0-14-generic
  drwxr-xr-x  3 root root 4096 Mar 20  2016 efi
  drwxr-xr-x  5 root root 4096 Mar 20 19:17 grub
  -rw-r--r--  1 root root 49676849 Mar 21 06:24 initrd.img-4.10.0-13-generic
  -rw-r--r--  1 root root 49672961 Mar 21 06:23 initrd.img-4.10.0-14-generic
  -rw-r--r--  1 root root 10017268 Mar 21 06:24 initrd.img-4.8.0-0-generic
  -rw-r--r--  1 root root 10017066 Mar 21 06:24 initrd.img-4.8.0-25-generic
  -rw-r--r--  1 root root   182704 Jan 28  2016 memtest86+.bin
  -rw-r--r--  1 root root   184380 Jan 28  2016 memtest86+.elf
  -rw-r--r--  1 root root   184840 Jan 28  2016 memtest86+_multiboot.bin
  -rw---  1 root root  3715891 Mar  9 14:16 System.map-4.10.0-13-generic
  -rw---  1 root root  3716749 Mar  9 21:30 System.map-4.10.0-14-generic
  -rw---  1 root root  7558928 Mar  9 14:16 vmlinuz-4.10.0-13-generic
  -rw---  1 root root  7563024 Mar  9 21:30 vmlinuz-4.10.0-14-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-firmware 1.164
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 21 06:28:04 2017
  Dependencies:

  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1687407] Re: dpkg crash, i'm working on it... package apt 1.2.15ubuntu0.2 failed to install/upgrade: end of file on stdin at conffile prompt

dpkg was run in interactive mode, without a place to read interactive
answers from (e.g. with < /dev/null).

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

Title:
  dpkg crash, i'm working on it... package apt 1.2.15ubuntu0.2 failed to
  install/upgrade: end of file on stdin at conffile prompt

Status in apt package in Ubuntu:
  Invalid

Bug description:
  dpkg crash, 
  I used some commands to resurrect dpkg, and now it's giving these errors

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.15ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Apr 30 20:20:49 2017
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-08-04 (270 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: apt
  Title: package apt 1.2.15ubuntu0.2 failed to install/upgrade: end of file on 
stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.cron.daily.apt-compat: 2016-04-05T15:24:43
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2016-04-14T04:45:21
  mtime.conffile..etc.logrotate.d.apt: 2016-04-05T15:24:43

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

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

[Touch-packages] [Bug 1701852] Re: (xenial+) apt-cache fails to run if a single sources.list.d entry is not readable

Fixed in 1.5~beta2, will need a manual sync once it's available in LP.

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

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

Title:
  (xenial+) apt-cache fails to run if a single sources.list.d entry is
  not readable

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  When evaluating:

  https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
  tools/+bug/1700611

  On 16.04 and greater, apt-cache fails to run if a single
  sources.list.d is not readable (by the current user).  On Trusty, the
  behavior was a bit more friendly in that it would run and just not
  show results from the file that cannot be read.

  My expectation is that when run it would warn if any .list file could
  not be read, but show results for everything it can see.

  This terminal interaction shows the problem (trusty and precise behave
  the same here):

  ubuntu@precise-esm:~$ ll 
/etc/apt/sources.list.d/staging-ubuntu-esm-precise.list
  -rw--- 1 root root 200 Jun 7 18:35 
/etc/apt/sources.list.d/staging-ubuntu-esm-precise.list

  ubuntu@precise-esm:~$ apt-cache policy landscape-client
  landscape-client:
Installed: (none)
Candidate: 14.12-0ubuntu0.12.04
Version table:
   14.12-0ubuntu0.12.04 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.04.3-0ubuntu1 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  ubuntu@precise-esm:~$ sudo apt-cache policy landscape-client
  landscape-client:
Installed: (none)
Candidate: 14.12-0ubuntu5.12.04
Version table:
   14.12-0ubuntu5.12.04 0
  500 https://extended.security.staging.ubuntu.com/ubuntu/ precise/main 
amd64 Packages
   14.12-0ubuntu0.12.04 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.04.3-0ubuntu1 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  ubuntu@xenial-test:~$ apt-cache search juju
  E: Opening /etc/apt/sources.list.d/juju-ubuntu-stable-xenial.list - 
ifstream::ifstream (13: Permission denied)
  E: The list of sources could not be read.
  ubuntu@xenial-test:~$

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

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

[Touch-packages] [Bug 1690881] Re: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu13 failed to install/upgrade: dependency problems - leaving triggers unprocessed

Probably fixed in zesty or newer with the huge installation ordering
changes.

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

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

Title:
  package plymouth-theme-ubuntu-text 0.9.2-3ubuntu13 failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  was unable to install new updates

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu13
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May 14 21:31:28 2017
  DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
   Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H110M-S2
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.10ubuntu1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu13 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-S2-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20:bd11/16/2016:svnGigabyteTechnologyCo.,Ltd.:pnH110M-S2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: H110M-S2
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1694623] Re: package apt 1.2.20 failed to install/upgrade: subprocess new pre-removal script returned error exit status 2

For some reason /var/log/apt/term.log was not attached, without it, we
have no chance to see what happens. Please attach.

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

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

Title:
  package apt 1.2.20 failed to install/upgrade: subprocess new pre-
  removal script returned error exit status 2

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Everything apart the System error pop-up at machine start up looks
  fine.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.20
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue May 30 10:17:42 2017
  Df:
   Filesystem 1K-blocks Used Available Use% Mounted on
   /dev/sda1  114752072 48694416  60205496  45% /
   tmpfs 810472 9584800888   2% /run
  DpkgTerminalLog:
   Log ended: 2017-05-29  17:24:19
 Log started: 2017-05-30  10:17:40
  ErrorMessage: subprocess new pre-removal script returned error exit status 2
  InstallationDate: Installed on 2017-04-11 (49 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: apt
  Title: package apt 1.2.20 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1710531] Re: package linux-image-4.4.0-91-generic 4.4.0-91.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2

I'm not entirely sure what is going on your system but it fails with
sort not understanding --version-sort - this has been introduced in
coreutils 7.0, released in 2008.  Your coreutils are 8.25 however, so I
have no idea what's going on.

* Did you install another sort binary?
* Are you using a weird shell where sort is a builtin for /bin/sh?

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

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

Title:
  package linux-image-4.4.0-91-generic 4.4.0-91.114 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 2

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  package linux-image-4.4.0-91-generic 4.4.0-91.114 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 2

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-91-generic 4.4.0-91.114
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ra059746   2176 F pulseaudio
  Date: Sun Aug 13 23:30:30 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
  HibernationDevice: RESUME=UUID=26cb4e4c-de55-4871-a29e-e47c9cf17400
  InstallationDate: Installed on 2016-04-22 (478 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Houter Oro PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-89-generic root=/dev/sda8 ro 
quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: apt
  Title: package linux-image-4.4.0-91-generic 4.4.0-91.114 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Oro PC
  dmi.board.vendor: Houter
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Houter
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd12/15/2010:svnHouter:pnOroPC:pvrTobefilledbyO.E.M.:rvnHouter:rnOroPC:rvrTobefilledbyO.E.M.:cvnHouter:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Oro PC
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Houter

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

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

[Touch-packages] [Bug 1710399] Re: Unable to install packages

The files went away from the mirror, but are listed as available.
Reassigning to launchpad.

** Package changed: apt (Ubuntu) => launchpad

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

Title:
  non {amd64,i386} files vanished from security.u.c

Status in Launchpad itself:
  New

Bug description:
  We use docker and qemu-static to build our project for all supported
  arch-es in travis. But a few days ago a ppc job started to fail with
  this error:

  Status: Downloaded newer image for ppc64le/ubuntu:trusty
   ---> 52071895775c
  Step 2 : ENV QEMU_CPU POWER8
   ---> Running in 4d3df022afff
   ---> 755937024d05
  Removing intermediate container 4d3df022afff
  Step 3 : COPY scripts/build/qemu-user-static/usr/bin/qemu-ppc64le-static 
/usr/bin/qemu-ppc64le-static
   ---> 188daa3f7494
  Removing intermediate container 472eb3b49e8e
  Step 4 : ARG CC=gcc
   ---> Running in 8f626dc61623
   ---> 20139f6cb27c
  Removing intermediate container 8f626dc61623
  Step 5 : ARG ENV1=FOOBAR
   ---> Running in 2767f0ce96a6
   ---> 8a7ea42bae39
  Removing intermediate container 2767f0ce96a6
  Step 6 : RUN apt-get update && apt-get install -y 
build-essential protobuf-c-compiler 
libprotobuf-c0-dev libprotobuf-dev bsdmainutils 
protobuf-compiler python-minimal
 libaio-dev libcap-dev iptables 
libnl-3-dev libselinux-dev pkg-config   
  git-core  libnet-dev  ccache $CC
   ---> Running in ae68ad78ec81
  Ign http://ports.ubuntu.com trusty InRelease
  Get:1 http://security.ubuntu.com trusty-security InRelease [65.9 kB]
  Get:2 http://ports.ubuntu.com trusty-updates InRelease [65.9 kB]
  Get:3 http://ports.ubuntu.com trusty-backports InRelease [65.9 kB]
  Get:4 http://ports.ubuntu.com trusty Release.gpg [933 B]
  Get:5 http://ports.ubuntu.com trusty Release [58.5 kB]
  Get:6 http://security.ubuntu.com trusty-security/universe Sources [73.1 kB]
  Get:7 http://ports.ubuntu.com trusty-updates/universe Sources [236 kB]
  Get:8 http://ports.ubuntu.com trusty-updates/main ppc64el Packages [993 kB]
  Err http://security.ubuntu.com trusty-security/main ppc64el Packages
404  Not Found [IP: 91.189.88.149 80]
  Get:9 http://ports.ubuntu.com trusty-updates/restricted ppc64el Packages [40 
B]
  Err http://security.ubuntu.com trusty-security/restricted ppc64el Packages
404  Not Found [IP: 91.189.88.149 80]
  Get:10 http://ports.ubuntu.com trusty-updates/universe ppc64el Packages [499 
kB]
  Err http://security.ubuntu.com trusty-security/universe ppc64el Packages
404  Not Found [IP: 91.189.88.149 80]
  Get:11 http://ports.ubuntu.com trusty-updates/multiverse ppc64el Packages 
[6925 B]
  Err http://security.ubuntu.com trusty-security/multiverse ppc64el Packages
404  Not Found [IP: 91.189.88.149 80]
  Get:12 http://ports.ubuntu.com trusty-backports/main ppc64el Packages [14.0 
kB]
  Get:13 http://ports.ubuntu.com trusty-backports/restricted ppc64el Packages 
[40 B]
  Get:14 http://ports.ubuntu.com trusty-backports/universe ppc64el Packages 
[48.0 kB]
  Get:15 http://ports.ubuntu.com trusty-backports/multiverse ppc64el Packages 
[573 B]
  Get:16 http://ports.ubuntu.com trusty/universe Sources [7926 kB]
  Get:17 http://ports.ubuntu.com trusty/main ppc64el Packages [1615 kB]
  Get:18 http://ports.ubuntu.com trusty/restricted ppc64el Packages [40 B]
  Get:19 http://ports.ubuntu.com trusty/universe ppc64el Packages [7014 kB]
  Get:20 http://ports.ubuntu.com trusty/multiverse ppc64el Packages [135 kB]
  Fetched 18.8 MB in 10s (1771 kB/s)
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/trusty-security/main/binary-ppc64el/Packages
  404  Not Found [IP: 91.189.88.149 80]
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/trusty-security/restricted/binary-ppc64el/Packages
  404  Not Found [IP: 91.189.88.149 80]
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/trusty-security/universe/binary-ppc64el/Packages
  404  Not Found [IP: 91.189.88.149 80]
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/trusty-security/multiverse/binary-ppc64el/Packages
  404  Not Found [IP: 91.189.88.149 80]
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.

  Here is a full log:
  https://travis-ci.org/xemul/criu/jobs/263720066

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

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

[Touch-packages] [Bug 1679220] Re: Installer pulls packages from other releases in the pool

I don't understand the problem, sorry. Can you expand on that? I don't
use anything other than http(s) repositories. How are the USB sticks
used?

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

Title:
  Installer pulls packages from other releases in the pool

Status in apt package in Ubuntu:
  New

Bug description:
  Frequently people reuse a USB stick to install another release, and
  the install fails because apt tries to pull packages from the wrong
  release.  Apt should only be looking in the pool for the current
  release rather than everything it can find.

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

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

[Touch-packages] [Bug 1709603] Re: apt {upgrade, install, source} require an update call first

** Summary changed:

- apt {upgrade,install} require an update call first
+ apt {upgrade,install, source} require an update call first

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

Title:
  apt {upgrade,install, source} require an update call first

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  I think that this should be tracked in its own separate bug tracking
  my specific UX objection to the current status quo.

  See
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/5,
  subsequent discussion and
  https://twitter.com/chr1sa/status/894048628284604416

  We think that the updating of indexes should be an implementation
  detail of "apt upgrade" and "apt install", rather than something
  exposed to the user. If updating is judged be required (for example
  the index is more than X old), then it should be done automatically
  before the requested operation commences.

  Here's one proposed implementation:

  1) Fix bug 1429285 ("apt-get update --if-necessary").

  2) Add an option to have "apt install" and "apt upgrade" (also "apt
  full-upgrade", etc?) automatically and internally call the
  implementation of "apt-get update --if-necessary" first.

  3) Enable the option by default on Ubuntu.

  This would change the behaviour of "apt", which AIUI is intended to be
  the user focused CLI. It wouldn't change the behaviour of "apt-get",
  which AIUI needs to retain behavioural backwards compatibility for
  existing scripts.

  Then we could promote "apt install" and "apt upgrade" as much simpler
  commands to operate.

  Note that Julian disagreed with this proposed behaviour change in
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/7.
  I think that the very user-focused Ubuntu perspective should be to
  focus on the common use case for "apt". Hence my (compromise)
  suggestion that we implement this as an option upstream, and then
  leave it to distros to choose the default behaviour for their users.

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

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

[Touch-packages] [Bug 1711254] Re: 16.04.3 deployments include non-existent directories in $PATH

2017-08-17 Thread Jeff Lane

@Steve, I don't disagree, and I've already merged a patch to fix that
issue in the cert suite.

For context, what happens isn't a test case, but a resource that
enumerates the binaries in the system so that the suite can validate
requirements for executing the tests.

e.g., it enumerates a list that contains "/usr/bin/iperf3" for example,
and the network test then has a constraint to only execute if
"/usr/bin/iperf3" actually exists.

The failure was that the enumeration just executes a 'find', the example
noted in the summary is almost exactly the command the resource job
uses, and find exits with a fail code because the directories listed in
$PATH didn't exist.  I couldn't find a way to tell find to simply ignore
non-existent things, without turning a shell oneliner into a more
complex script, so in the end, the resource job now always returns
"true" regardless of the exit code from 'find'.

But since customers started voicing concern about it, and because it
just seemed odd to me for us to be automatically injecting false data
into $PATH (for whatever reason, I read the bug Adam pointed out, and I
can understand now why this happened) I thought it was worth raising a
bug, even if the ultimate answer is "there were reasons for doing it
that couldn't be avoided".

** Description changed:

  Noticed this while doing regression testing on 16.04.3, and a number of
  customers have asked with concerns as well during their testing.
  
  I don't know exactly when this started, but we just started noticing it
  with 16.04.3 (4.10) but $PATH by default now includes several
  directories that do not exist:
  
- 
- ubuntu@above-ox:~$ find $(echo "$PATH" | sed -e 's/:/ /g') -maxdepth 1 -type 
dfind: ‘/home/ubuntu/bin’: No such file or directory
+ ubuntu@above-ox:~$ find $(echo "$PATH" | sed -e 's/:/ /g') -maxdepth 1 -type d
+ find: ‘/home/ubuntu/bin’: No such file or directory
  find: ‘/home/ubuntu/.local/bin’: No such file or directory
  /usr/local/sbin
  /usr/local/bin
  /usr/sbin
  /usr/bin
  /sbin
  /bin
  /usr/games
  /usr/local/games
  find: ‘/snap/bin’: No such file or directory
  
  We noticed this because it was causing a resource job in the
  certification suite to suddenly start failing (the failure was not
  catastrophic, but it did appear to customers who were concerned.
  
  I've verified this on both s390x and amd64 16.04.3 deployments via MAAS
  2.2.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic s390x
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: s390x
  Date: Wed Aug 16 18:59:34 2017
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en.US_UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en.US_UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  16.04.3 deployments include non-existent directories in $PATH

Status in bash package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  New

Bug description:
  Noticed this while doing regression testing on 16.04.3, and a number
  of customers have asked with concerns as well during their testing.

  I don't know exactly when this started, but we just started noticing
  it with 16.04.3 (4.10) but $PATH by default now includes several
  directories that do not exist:

  ubuntu@above-ox:~$ find $(echo "$PATH" | sed -e 's/:/ /g') -maxdepth 1 -type d
  find: ‘/home/ubuntu/bin’: No such file or directory
  find: ‘/home/ubuntu/.local/bin’: No such file or directory
  /usr/local/sbin
  /usr/local/bin
  /usr/sbin
  /usr/bin
  /sbin
  /bin
  /usr/games
  /usr/local/games
  find: ‘/snap/bin’: No such file or directory

  We noticed this because it was causing a resource job in the
  certification suite to suddenly start failing (the failure was not
  catastrophic, but it did appear to customers who were concerned.

  I've verified this on both s390x and amd64 16.04.3 deployments via
  MAAS 2.2.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic s390x
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: s390x
  Date: Wed Aug 16 18:59:34 2017
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en.US_UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-

[Touch-packages] [Bug 1711254] Re: 16.04.3 deployments include non-existent directories in $PATH

~/.bin and ~/.local/bin are added to the path by /etc/skel/.profile
which is shipped in the bash package.

It's debatable whether these should be added to the path
unconditionally, or only if they exist.  It is convenient to have the
directories automatically available on the path as soon as they are
created, without having to relogin / re-source the shell config;
conversely, it means a couple of extra pointless stats on every exec()
call.

Regardless, though, I don't think it's correct that your certification
suite should throw errors as a result of directories on the PATH not
being present on the filesystem.

** Package changed: base-files (Ubuntu) => bash (Ubuntu)

** Changed in: bash (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  16.04.3 deployments include non-existent directories in $PATH

Status in bash package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  New

Bug description:
  Noticed this while doing regression testing on 16.04.3, and a number
  of customers have asked with concerns as well during their testing.

  I don't know exactly when this started, but we just started noticing
  it with 16.04.3 (4.10) but $PATH by default now includes several
  directories that do not exist:

  
  ubuntu@above-ox:~$ find $(echo "$PATH" | sed -e 's/:/ /g') -maxdepth 1 -type 
dfind: ‘/home/ubuntu/bin’: No such file or directory
  find: ‘/home/ubuntu/.local/bin’: No such file or directory
  /usr/local/sbin
  /usr/local/bin
  /usr/sbin
  /usr/bin
  /sbin
  /bin
  /usr/games
  /usr/local/games
  find: ‘/snap/bin’: No such file or directory

  We noticed this because it was causing a resource job in the
  certification suite to suddenly start failing (the failure was not
  catastrophic, but it did appear to customers who were concerned.

  I've verified this on both s390x and amd64 16.04.3 deployments via
  MAAS 2.2.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic s390x
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: s390x
  Date: Wed Aug 16 18:59:34 2017
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en.US_UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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-08-17 Thread Elvis Pranskevichus

We'll need the package maintainers to chime in on this. Attached is a
patch that disables harmful settings.

** Patch added: "0001-Disable-fpectl-and-fPIC-on-Modules-_math.c.patch"

https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+attachment/4934301/+files/0001-Disable-fpectl-and-fPIC-on-Modules-_math.c.patch

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

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 1710397] Re: Unable to identify package based on windows for some applications

2017-08-17 Thread Jean-Baptiste Lallement

** Tags added: wayland

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

** Changed in: apport (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Unable to identify package based on windows for some applications

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When running ubuntu-bug -w the following message is output to
  terminal:

  Gtk-Message: GtkDialog mapped without a transient parent. This is
  discouraged.

  Clicking on windows from GNOME Terminal or Backups has not effect.
  Clicking on a Firefox window however, will trigger the expected
  behavior. It seems ubuntu-bug -w is only recognizing some windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4.5
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CrashReports: 640:1000:122:995835:2017-08-12 12:30:28.203223748 
-0400:2017-08-12 12:30:27.252524580 
-0400:/var/crash/_usr_bin_update-notifier.1000.crash
  CurrentDesktop: GNOME
  Date: Sat Aug 12 13:40:46 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-08-12 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1588562] Re: Please add ~/.local/bin to the default $PATH

This was landed in a xenial SRU and fixed in yakkety, but the change
appears to have silently fallen out of zesty and later in a Debian
merge.

If this is a deliberate change because .local/bin is no longer needed in
zesty and later, feel free to re-close this bug.  Please also check
whether the path change on xenial should be reverted.

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

** Changed in: bash (Ubuntu)
 Assignee: (unassigned) => Matthias Klose (doko)

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

Title:
  Please add ~/.local/bin to the default $PATH

Status in bash package in Ubuntu:
  Triaged
Status in bash source package in Xenial:
  Fix Released
Status in bash package in Debian:
  Fix Released

Bug description:
  Starting in Xenial, 'pip install' by default places executables into
  ~/.local/bin. This is the de-facto standard place to put per-user
  executables -- for example, Fedora/Redhat puts it on the $PATH by
  default, and PEP 370 makes it the standard place for unprivileged
  installs of Python packages to put their scripts.

  But unfortunately, Ubuntu's does *not* add this directory to $PATH by
  default, which means that 'pip install' doesn't actually work -- any
  scripts that are installed are inaccessible, and every user has to
  manually add this to their PATH.

  Ubuntu should put ~/.local/bin onto PATH by default.

  Minor details (discussed with @doko at the PyCon sprints):

  - this should go at the beginning of PATH rather than the end, in accordance 
with Debian policy saying that more-local paths go before more-upstream paths. 
(This is inconsistent with how Fedora/RH do it, but consistent with how Python 
itself searches for packages.)
  - this will be added to /etc/skel/profile, so that it won't change any 
existing user accounts; it will only be applied to user accounts created 
*after* this change lands
  - unlike ~/bin (which Debian/Ubuntu have supported for ages), it will be 
added to PATH unconditionally, even if the directory doesn't exist. This is 
important to avoid a nasty trap for new users, where the first time they try to 
install a Python package they have to restart their shell. Since this only 
applies to new accounts, the directory will always start out nonexistent/empty, 
so having it in $PATH won't cause any unexpected changes in behavior.
  - possibly it would make sense to set this in /etc/environment or 
/etc/skel/.gnomerc or similar, so that it would also apply to non-shell 
processes (e.g. if the user wants to add a global key-binding to launch a 
Python program, then generally ~/.profile *doesn't* affect the environment 
where this command gets executed, and that can frustrate and confuse users if a 
command works fine from the terminal but not from a keybinding). But we should 
defer this discussion for the future, because even if this is a good idea, it 
isn't a good idea in a Xenial stable update.

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856

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

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

[Touch-packages] [Bug 1588562] Re: Please add ~/.local/bin to the default $PATH

2017-08-17 Thread Adam Conrad

See also https://bugs.launchpad.net/ubuntu/+source/base-
files/+bug/1711254

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

Title:
  Please add ~/.local/bin to the default $PATH

Status in bash package in Ubuntu:
  Triaged
Status in bash source package in Xenial:
  Fix Released
Status in bash package in Debian:
  Fix Released

Bug description:
  Starting in Xenial, 'pip install' by default places executables into
  ~/.local/bin. This is the de-facto standard place to put per-user
  executables -- for example, Fedora/Redhat puts it on the $PATH by
  default, and PEP 370 makes it the standard place for unprivileged
  installs of Python packages to put their scripts.

  But unfortunately, Ubuntu's does *not* add this directory to $PATH by
  default, which means that 'pip install' doesn't actually work -- any
  scripts that are installed are inaccessible, and every user has to
  manually add this to their PATH.

  Ubuntu should put ~/.local/bin onto PATH by default.

  Minor details (discussed with @doko at the PyCon sprints):

  - this should go at the beginning of PATH rather than the end, in accordance 
with Debian policy saying that more-local paths go before more-upstream paths. 
(This is inconsistent with how Fedora/RH do it, but consistent with how Python 
itself searches for packages.)
  - this will be added to /etc/skel/profile, so that it won't change any 
existing user accounts; it will only be applied to user accounts created 
*after* this change lands
  - unlike ~/bin (which Debian/Ubuntu have supported for ages), it will be 
added to PATH unconditionally, even if the directory doesn't exist. This is 
important to avoid a nasty trap for new users, where the first time they try to 
install a Python package they have to restart their shell. Since this only 
applies to new accounts, the directory will always start out nonexistent/empty, 
so having it in $PATH won't cause any unexpected changes in behavior.
  - possibly it would make sense to set this in /etc/environment or 
/etc/skel/.gnomerc or similar, so that it would also apply to non-shell 
processes (e.g. if the user wants to add a global key-binding to launch a 
Python program, then generally ~/.profile *doesn't* affect the environment 
where this command gets executed, and that can frustrate and confuse users if a 
command works fine from the terminal but not from a keybinding). But we should 
defer this discussion for the future, because even if this is a good idea, it 
isn't a good idea in a Xenial stable update.

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856

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

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

[Touch-packages] [Bug 1711254] Re: 16.04.3 deployments include non-existent directories in $PATH

2017-08-17 Thread Adam Conrad

The user bin bits of this are due to
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1588562

We can have it one way or the other, but not both ways.  Not sure I
agree with having nonexistent paths in PATH, but it's shouldn't
technically break anything either.

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

Title:
  16.04.3 deployments include non-existent directories in $PATH

Status in base-files package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  Noticed this while doing regression testing on 16.04.3, and a number
  of customers have asked with concerns as well during their testing.

  I don't know exactly when this started, but we just started noticing
  it with 16.04.3 (4.10) but $PATH by default now includes several
  directories that do not exist:

  
  ubuntu@above-ox:~$ find $(echo "$PATH" | sed -e 's/:/ /g') -maxdepth 1 -type 
dfind: ‘/home/ubuntu/bin’: No such file or directory
  find: ‘/home/ubuntu/.local/bin’: No such file or directory
  /usr/local/sbin
  /usr/local/bin
  /usr/sbin
  /usr/bin
  /sbin
  /bin
  /usr/games
  /usr/local/games
  find: ‘/snap/bin’: No such file or directory

  We noticed this because it was causing a resource job in the
  certification suite to suddenly start failing (the failure was not
  catastrophic, but it did appear to customers who were concerned.

  I've verified this on both s390x and amd64 16.04.3 deployments via
  MAAS 2.2.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic s390x
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: s390x
  Date: Wed Aug 16 18:59:34 2017
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en.US_UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1710654] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

2017-08-17 Thread Iain Lane

1) 2.0.10 (xenial-updates)
2) max_user_instances = 128

I think this should have been enough, but we had a problem where there
were stale lxd containers (both RUNNING and STOPPED) piling up. I
cleaned all of those out; hopefully if you retry it'll work.

Maybe we should still roll out the sysctl.d change to be extra safe
though.

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

Title:
  systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz

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

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

[Touch-packages] [Bug 1692870] Re: gzip compression broken in UniFi (built-in tomcat)

** Changed in: zlib (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

** Changed in: zlib (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  gzip compression broken in UniFi (built-in tomcat)

Status in zlib package in Ubuntu:
  Fix Committed
Status in zlib source package in Zesty:
  Confirmed
Status in zlib source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Since I upgraded from Ubuntu 16.10 to 17.04, my Guest portal for my UniFi 
system was broken (https://www.ubnt.com/download/unifi/).

  Curl gave me the following response:
  # curl - --compress localhost:8880/guest/s/default/
  *   Trying ::1...
  * TCP_NODELAY set
  * Connected to localhost (::1) port 8880 (#0)
  > GET /guest/s/default/ HTTP/1.1
  > Host: localhost:8880
  > User-Agent: curl/7.52.1
  > Accept: */*
  > Accept-Encoding: deflate, gzip
  >
  < HTTP/1.1 200 OK
  < Server: Apache-Coyote/1.1
  < Content-Type: text/html;charset=utf-8
  < Transfer-Encoding: chunked
  < Content-Encoding: gzip
  < Vary: Accept-Encoding
  < Date: Tue, 23 May 2017 11:19:22 GMT
  <
  * Error while processing content unencoding: invalid code lengths set
  * Failed writing data
  * Curl_http_done: called premature == 1
  * Closing connection 0
  curl: (23) Error while processing content unencoding: invalid code lengths set

  [Test Case]
  - Install UniFi controller on Ubuntu 17.04 
(http://dl.ubnt.com/unifi/5.4.16/unifi_sysvinit_all.deb)
  - Go to https://:8443/manage/site/default/settings/guestcontrol
  - Or do: curl - --compress :8880/guest/s/default/

  When compression is enabled, its broken.
  When disabling compression in curl, it works fine.

  After some debugging, I found out that downgrading to zlib 1:1.2.8
  .dfsg-2ubuntu5.1 was a workaround.

  Now after digging into the issue some more, I found the following upstream 
patch (unreleased version), fixes the issue:
  https://github.com/madler/zlib/commit/f9694097dd69354b03cb8af959094c7f260db0a1

  [Regression Potential]
  Everybody upgrading from 16.10 (or previous) to 17.04 will be affected by 
this.

  The patch is taken from upstream, so this isn't a change we will need
  to keep different from upstream.

  I've already created a new package (see debdiff) that fixes the issue.

  [Other Info]
  Now as the UniFi controller is just some Tomcat, which relies on Java 
(OpenJDK), which uses zlib for its built-in Compression/Decompression. I guess 
even more java related tools can be broken. But I didn't have time to test this.

  At least some other people using UniFi have the same issue, see:
  
https://community.ubnt.com/t5/UniFi-Wireless/ERR-CONTENT-DECODING-FAILED-on-guest-portal-customisation/td-p/1903419

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

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

[Touch-packages] [Bug 1708051] Re: v234 seems to fail to reboot 5 times in a row on s390x, and crashes amd64/i386 instances

2017-08-17 Thread Iain Lane

xnox and I debugged this together, and it seems like the upload of 234
in Debian switched to Meson, and there was a bug introduced here where
KillUserProcesses was set back to `yes' instead of `no' as it's meant to
be. To reboot the machine, autopkgtest runs `sh -c (sleep 3; reboot) &'
over SSH. When we background this and then end the SSH connection - and
logind session - systemd kills the sleep and the reboot is never run, so
we see a system that has come up but never gone down.

I found this by entering a machine in the bad state and looking at the
journal. In future I suggest that systemd's autopkgtests output the
journal to their log so that this would be debuggable without admin
access next time.

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

Title:
  v234 seems to fail to reboot 5 times in a row on s390x, and crashes
  amd64/i386 instances

Status in systemd package in Ubuntu:
  New

Bug description:
  ppc64el is fine.

  Given that everything is fixed to start containers and vms non-
  degraded, let's enforce that we boot not degraded.

  Also network online timeout is 30s, thus it makes no sense to only
  give the boot 10s. Especially since machines can be overcommitted with
  capacity.

  update: tests were improved somewhat, to be more deterministic and
  always wait for the boot to fully finish before rebooting. On the
  infrastructure - all but i386/amd64 pass. But locally it is not
  reproducible. It almost feels like openstack-nova-autopkgtest-reboot-
  marker integration is broken; or systemd fails to reboot in
  scalingstack.

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

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

[Touch-packages] [Bug 1692870] Re: gzip compression broken in UniFi (built-in tomcat)

** Also affects: zlib (Ubuntu Artful)
   Importance: High
   Status: Confirmed

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

Title:
  gzip compression broken in UniFi (built-in tomcat)

Status in zlib package in Ubuntu:
  Confirmed
Status in zlib source package in Zesty:
  Confirmed
Status in zlib source package in Artful:
  Confirmed

Bug description:
  [Impact]
  Since I upgraded from Ubuntu 16.10 to 17.04, my Guest portal for my UniFi 
system was broken (https://www.ubnt.com/download/unifi/).

  Curl gave me the following response:
  # curl - --compress localhost:8880/guest/s/default/
  *   Trying ::1...
  * TCP_NODELAY set
  * Connected to localhost (::1) port 8880 (#0)
  > GET /guest/s/default/ HTTP/1.1
  > Host: localhost:8880
  > User-Agent: curl/7.52.1
  > Accept: */*
  > Accept-Encoding: deflate, gzip
  >
  < HTTP/1.1 200 OK
  < Server: Apache-Coyote/1.1
  < Content-Type: text/html;charset=utf-8
  < Transfer-Encoding: chunked
  < Content-Encoding: gzip
  < Vary: Accept-Encoding
  < Date: Tue, 23 May 2017 11:19:22 GMT
  <
  * Error while processing content unencoding: invalid code lengths set
  * Failed writing data
  * Curl_http_done: called premature == 1
  * Closing connection 0
  curl: (23) Error while processing content unencoding: invalid code lengths set

  [Test Case]
  - Install UniFi controller on Ubuntu 17.04 
(http://dl.ubnt.com/unifi/5.4.16/unifi_sysvinit_all.deb)
  - Go to https://:8443/manage/site/default/settings/guestcontrol
  - Or do: curl - --compress :8880/guest/s/default/

  When compression is enabled, its broken.
  When disabling compression in curl, it works fine.

  After some debugging, I found out that downgrading to zlib 1:1.2.8
  .dfsg-2ubuntu5.1 was a workaround.

  Now after digging into the issue some more, I found the following upstream 
patch (unreleased version), fixes the issue:
  https://github.com/madler/zlib/commit/f9694097dd69354b03cb8af959094c7f260db0a1

  [Regression Potential]
  Everybody upgrading from 16.10 (or previous) to 17.04 will be affected by 
this.

  The patch is taken from upstream, so this isn't a change we will need
  to keep different from upstream.

  I've already created a new package (see debdiff) that fixes the issue.

  [Other Info]
  Now as the UniFi controller is just some Tomcat, which relies on Java 
(OpenJDK), which uses zlib for its built-in Compression/Decompression. I guess 
even more java related tools can be broken. But I didn't have time to test this.

  At least some other people using UniFi have the same issue, see:
  
https://community.ubnt.com/t5/UniFi-Wireless/ERR-CONTENT-DECODING-FAILED-on-guest-portal-customisation/td-p/1903419

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

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

[Touch-packages] [Bug 1692870] Re: gzip compression broken in UniFi (built-in tomcat)

** Tags removed: rls-aa-incoming

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

Title:
  gzip compression broken in UniFi (built-in tomcat)

Status in zlib package in Ubuntu:
  Confirmed
Status in zlib source package in Zesty:
  Confirmed
Status in zlib source package in Artful:
  Confirmed

Bug description:
  [Impact]
  Since I upgraded from Ubuntu 16.10 to 17.04, my Guest portal for my UniFi 
system was broken (https://www.ubnt.com/download/unifi/).

  Curl gave me the following response:
  # curl - --compress localhost:8880/guest/s/default/
  *   Trying ::1...
  * TCP_NODELAY set
  * Connected to localhost (::1) port 8880 (#0)
  > GET /guest/s/default/ HTTP/1.1
  > Host: localhost:8880
  > User-Agent: curl/7.52.1
  > Accept: */*
  > Accept-Encoding: deflate, gzip
  >
  < HTTP/1.1 200 OK
  < Server: Apache-Coyote/1.1
  < Content-Type: text/html;charset=utf-8
  < Transfer-Encoding: chunked
  < Content-Encoding: gzip
  < Vary: Accept-Encoding
  < Date: Tue, 23 May 2017 11:19:22 GMT
  <
  * Error while processing content unencoding: invalid code lengths set
  * Failed writing data
  * Curl_http_done: called premature == 1
  * Closing connection 0
  curl: (23) Error while processing content unencoding: invalid code lengths set

  [Test Case]
  - Install UniFi controller on Ubuntu 17.04 
(http://dl.ubnt.com/unifi/5.4.16/unifi_sysvinit_all.deb)
  - Go to https://:8443/manage/site/default/settings/guestcontrol
  - Or do: curl - --compress :8880/guest/s/default/

  When compression is enabled, its broken.
  When disabling compression in curl, it works fine.

  After some debugging, I found out that downgrading to zlib 1:1.2.8
  .dfsg-2ubuntu5.1 was a workaround.

  Now after digging into the issue some more, I found the following upstream 
patch (unreleased version), fixes the issue:
  https://github.com/madler/zlib/commit/f9694097dd69354b03cb8af959094c7f260db0a1

  [Regression Potential]
  Everybody upgrading from 16.10 (or previous) to 17.04 will be affected by 
this.

  The patch is taken from upstream, so this isn't a change we will need
  to keep different from upstream.

  I've already created a new package (see debdiff) that fixes the issue.

  [Other Info]
  Now as the UniFi controller is just some Tomcat, which relies on Java 
(OpenJDK), which uses zlib for its built-in Compression/Decompression. I guess 
even more java related tools can be broken. But I didn't have time to test this.

  At least some other people using UniFi have the same issue, see:
  
https://community.ubnt.com/t5/UniFi-Wireless/ERR-CONTENT-DECODING-FAILED-on-guest-portal-customisation/td-p/1903419

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

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

[Touch-packages] [Bug 1692870] Re: gzip compression broken in UniFi (built-in tomcat)

Sorry, you already addressed this in comment #4.

** Changed in: zlib (Ubuntu)
   Importance: Undecided => High

** Changed in: zlib (Ubuntu Zesty)
   Importance: Undecided => High

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

Title:
  gzip compression broken in UniFi (built-in tomcat)

Status in zlib package in Ubuntu:
  Confirmed
Status in zlib source package in Zesty:
  Confirmed
Status in zlib source package in Artful:
  Confirmed

Bug description:
  [Impact]
  Since I upgraded from Ubuntu 16.10 to 17.04, my Guest portal for my UniFi 
system was broken (https://www.ubnt.com/download/unifi/).

  Curl gave me the following response:
  # curl - --compress localhost:8880/guest/s/default/
  *   Trying ::1...
  * TCP_NODELAY set
  * Connected to localhost (::1) port 8880 (#0)
  > GET /guest/s/default/ HTTP/1.1
  > Host: localhost:8880
  > User-Agent: curl/7.52.1
  > Accept: */*
  > Accept-Encoding: deflate, gzip
  >
  < HTTP/1.1 200 OK
  < Server: Apache-Coyote/1.1
  < Content-Type: text/html;charset=utf-8
  < Transfer-Encoding: chunked
  < Content-Encoding: gzip
  < Vary: Accept-Encoding
  < Date: Tue, 23 May 2017 11:19:22 GMT
  <
  * Error while processing content unencoding: invalid code lengths set
  * Failed writing data
  * Curl_http_done: called premature == 1
  * Closing connection 0
  curl: (23) Error while processing content unencoding: invalid code lengths set

  [Test Case]
  - Install UniFi controller on Ubuntu 17.04 
(http://dl.ubnt.com/unifi/5.4.16/unifi_sysvinit_all.deb)
  - Go to https://:8443/manage/site/default/settings/guestcontrol
  - Or do: curl - --compress :8880/guest/s/default/

  When compression is enabled, its broken.
  When disabling compression in curl, it works fine.

  After some debugging, I found out that downgrading to zlib 1:1.2.8
  .dfsg-2ubuntu5.1 was a workaround.

  Now after digging into the issue some more, I found the following upstream 
patch (unreleased version), fixes the issue:
  https://github.com/madler/zlib/commit/f9694097dd69354b03cb8af959094c7f260db0a1

  [Regression Potential]
  Everybody upgrading from 16.10 (or previous) to 17.04 will be affected by 
this.

  The patch is taken from upstream, so this isn't a change we will need
  to keep different from upstream.

  I've already created a new package (see debdiff) that fixes the issue.

  [Other Info]
  Now as the UniFi controller is just some Tomcat, which relies on Java 
(OpenJDK), which uses zlib for its built-in Compression/Decompression. I guess 
even more java related tools can be broken. But I didn't have time to test this.

  At least some other people using UniFi have the same issue, see:
  
https://community.ubnt.com/t5/UniFi-Wireless/ERR-CONTENT-DECODING-FAILED-on-guest-portal-customisation/td-p/1903419

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

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

[Touch-packages] [Bug 1692870] Re: gzip compression broken in UniFi (built-in tomcat)

For SRU, this is going to need a better test case.

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

Title:
  gzip compression broken in UniFi (built-in tomcat)

Status in zlib package in Ubuntu:
  Confirmed
Status in zlib source package in Zesty:
  Confirmed
Status in zlib source package in Artful:
  Confirmed

Bug description:
  [Impact]
  Since I upgraded from Ubuntu 16.10 to 17.04, my Guest portal for my UniFi 
system was broken (https://www.ubnt.com/download/unifi/).

  Curl gave me the following response:
  # curl - --compress localhost:8880/guest/s/default/
  *   Trying ::1...
  * TCP_NODELAY set
  * Connected to localhost (::1) port 8880 (#0)
  > GET /guest/s/default/ HTTP/1.1
  > Host: localhost:8880
  > User-Agent: curl/7.52.1
  > Accept: */*
  > Accept-Encoding: deflate, gzip
  >
  < HTTP/1.1 200 OK
  < Server: Apache-Coyote/1.1
  < Content-Type: text/html;charset=utf-8
  < Transfer-Encoding: chunked
  < Content-Encoding: gzip
  < Vary: Accept-Encoding
  < Date: Tue, 23 May 2017 11:19:22 GMT
  <
  * Error while processing content unencoding: invalid code lengths set
  * Failed writing data
  * Curl_http_done: called premature == 1
  * Closing connection 0
  curl: (23) Error while processing content unencoding: invalid code lengths set

  [Test Case]
  - Install UniFi controller on Ubuntu 17.04 
(http://dl.ubnt.com/unifi/5.4.16/unifi_sysvinit_all.deb)
  - Go to https://:8443/manage/site/default/settings/guestcontrol
  - Or do: curl - --compress :8880/guest/s/default/

  When compression is enabled, its broken.
  When disabling compression in curl, it works fine.

  After some debugging, I found out that downgrading to zlib 1:1.2.8
  .dfsg-2ubuntu5.1 was a workaround.

  Now after digging into the issue some more, I found the following upstream 
patch (unreleased version), fixes the issue:
  https://github.com/madler/zlib/commit/f9694097dd69354b03cb8af959094c7f260db0a1

  [Regression Potential]
  Everybody upgrading from 16.10 (or previous) to 17.04 will be affected by 
this.

  The patch is taken from upstream, so this isn't a change we will need
  to keep different from upstream.

  I've already created a new package (see debdiff) that fixes the issue.

  [Other Info]
  Now as the UniFi controller is just some Tomcat, which relies on Java 
(OpenJDK), which uses zlib for its built-in Compression/Decompression. I guess 
even more java related tools can be broken. But I didn't have time to test this.

  At least some other people using UniFi have the same issue, see:
  
https://community.ubnt.com/t5/UniFi-Wireless/ERR-CONTENT-DECODING-FAILED-on-guest-portal-customisation/td-p/1903419

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

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

[Touch-packages] [Bug 1692870] Re: gzip compression broken in UniFi (built-in tomcat)

Why does your debdiff drop the use-dso patch?  Can you confirm that
*not* disabling the use-dso patch still lets this work for you?

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

Title:
  gzip compression broken in UniFi (built-in tomcat)

Status in zlib package in Ubuntu:
  Confirmed
Status in zlib source package in Zesty:
  Confirmed
Status in zlib source package in Artful:
  Confirmed

Bug description:
  [Impact]
  Since I upgraded from Ubuntu 16.10 to 17.04, my Guest portal for my UniFi 
system was broken (https://www.ubnt.com/download/unifi/).

  Curl gave me the following response:
  # curl - --compress localhost:8880/guest/s/default/
  *   Trying ::1...
  * TCP_NODELAY set
  * Connected to localhost (::1) port 8880 (#0)
  > GET /guest/s/default/ HTTP/1.1
  > Host: localhost:8880
  > User-Agent: curl/7.52.1
  > Accept: */*
  > Accept-Encoding: deflate, gzip
  >
  < HTTP/1.1 200 OK
  < Server: Apache-Coyote/1.1
  < Content-Type: text/html;charset=utf-8
  < Transfer-Encoding: chunked
  < Content-Encoding: gzip
  < Vary: Accept-Encoding
  < Date: Tue, 23 May 2017 11:19:22 GMT
  <
  * Error while processing content unencoding: invalid code lengths set
  * Failed writing data
  * Curl_http_done: called premature == 1
  * Closing connection 0
  curl: (23) Error while processing content unencoding: invalid code lengths set

  [Test Case]
  - Install UniFi controller on Ubuntu 17.04 
(http://dl.ubnt.com/unifi/5.4.16/unifi_sysvinit_all.deb)
  - Go to https://:8443/manage/site/default/settings/guestcontrol
  - Or do: curl - --compress :8880/guest/s/default/

  When compression is enabled, its broken.
  When disabling compression in curl, it works fine.

  After some debugging, I found out that downgrading to zlib 1:1.2.8
  .dfsg-2ubuntu5.1 was a workaround.

  Now after digging into the issue some more, I found the following upstream 
patch (unreleased version), fixes the issue:
  https://github.com/madler/zlib/commit/f9694097dd69354b03cb8af959094c7f260db0a1

  [Regression Potential]
  Everybody upgrading from 16.10 (or previous) to 17.04 will be affected by 
this.

  The patch is taken from upstream, so this isn't a change we will need
  to keep different from upstream.

  I've already created a new package (see debdiff) that fixes the issue.

  [Other Info]
  Now as the UniFi controller is just some Tomcat, which relies on Java 
(OpenJDK), which uses zlib for its built-in Compression/Decompression. I guess 
even more java related tools can be broken. But I didn't have time to test this.

  At least some other people using UniFi have the same issue, see:
  
https://community.ubnt.com/t5/UniFi-Wireless/ERR-CONTENT-DECODING-FAILED-on-guest-portal-customisation/td-p/1903419

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

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

[Touch-packages] [Bug 1706558] Re: Japanese Input Method doesn't work by default in Ubuntu 17.10 daily build.

2017-08-17 Thread Sickly Life

I understand.
Thank you for your explanation.
I like fcitx better than ibus. But...hmm...

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

Title:
  Japanese Input Method doesn't work by default in Ubuntu 17.10 daily
  build.

Status in ibus package in Ubuntu:
  Invalid
Status in mozc package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I installed Ubuntu Desktop 17.10 daily build (selected Japanese
  Language), but ibus-mozc (Japanese Input Method) is not installed when
  installing Ubuntu 17.10 daily build.

  Fcitx and fcitx-mozc are installed when installing Ubuntu 17.10 daily build.
  But the default is ibus.

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

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

[Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-08-17 Thread Eric Desrochers

Hi iiro,

Could you please give it a try with the following test package I have
prepare for you :

sudo add-apt-repository ppa:slashd/cupsupgrade
sudo apt-get update

Use the same exact reproducer but instead of upgrading from xenial-
proposed like you normally do, please upgrade from this PPA.

Let me know the outcome.

- Eric

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Triaged
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  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/cups/+bug/1642966/+subscriptions

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

[Touch-packages] [Bug 1710684] Re: Debian merge 2.1.27~101-g0780600+dfsg-3

This bug was fixed in the package cyrus-sasl2 - 2.1.27~101-g0780600
+dfsg-3ubuntu1

---
cyrus-sasl2 (2.1.27~101-g0780600+dfsg-3ubuntu1) artful; urgency=medium

  * Merge with Debian unstable (LP: #1710684). Remaining changes:
- debian/patches/0033-Missing-definition-of-OPENSSL_zalloc.patch: Grab patch
  from upstream Git to fix FTBFS with older versions of OpenSSL.
  + LP #1672941

 -- Andreas Hasenack   Mon, 14 Aug 2017 15:11:41
-0300

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Debian merge 2.1.27~101-g0780600+dfsg-3

Status in cyrus-sasl2 package in Ubuntu:
  Fix Released

Bug description:
  Please merge Debian's cyrus-sasl into ubuntu.

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

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

[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

Changed from verification-failed to verification-needed-zesty so we can
eventually mark this as done when bug 1686470 is verified.

** Tags removed: verification-failed
** Tags added: verification-needed-zesty

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Won't Fix
Status in apt source package in Yakkety:
  Won't Fix
Status in apt source package in Zesty:
  Won't Fix

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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

[Touch-packages] [Bug 1710911] Re: apt-ftparchive does not correctly cache filesizes for packages > 4GB

Removed the patch tag here and there, as the patch is incomplete.

** Tags removed: patch

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

Title:
  apt-ftparchive does not correctly cache filesizes for packages > 4GB

Status in apt package in Ubuntu:
  New
Status in apt package in Debian:
  Unknown

Bug description:
  Release: 16.04
  Version: 1.2.19

  apt-ftparchive is a utility for, among other things, generating a
  Packages file from a set of .deb packages.

  Because generating Packages files for a large directory tree of .deb
  packages is expensive, it can cache the properties of .deb packages it
  has already inspected in a Berkeley database file.

  Historically, apt-ftparchive stored the size of a .deb package as a
  32-bit unsigned integer in network byte-order in this cache.  This
  field was later enlarged to 64-bits - which caused other problems;
  see: LP #1274466.

  However, even after this integer field was enlarged, apt-ftparchive
  continued to use the htonl() and ntohl() libc functions to convert
  file-sizes to and from network byte-order when reading and writing to
  its cache.  These functions unconditionally emit 32-bit unsigned
  integers, which means that apt-ftparchive remained unable to correctly
  record the file-sizes for packages > 32bits (i.e. > 4GB).

  Consequently, if apt-ftparchive is asked (with caching enabled) to
  generate a Packages file for a .deb package larger than 4GB, it will
  produce a Packages file with the correct Size: field the first time,
  but with incorrect Size: fields subsequently.

  I have developed a small patch which replaces the use of the ntohl()
  family of functions with suitable replacements from .  This
  produces correct output on new installations.

  However, caution is necessary: the existing code is incorrectly
  storing the 32 least significant bits of a 64-bit number in the upper
  32-bits of a 64-bit field, in big-endian byte order.  The application
  of this patch will cause new values to be stored correctly, but in a
  binary-incompatible way with existing caches.

  For example, a package of size 7162161474 bytes will today have the
  following sequence of bytes stored in its cache entry:

  \xaa\xe5\xe9\x42\x00\x00\x00\x00

  (When re-read, this will produce a file-size value of 7162161474 mod
  32bits, i.e. 2867194178.)

  With this patch applied, apt-ftparchive will correctly store this
  entry:

  \x00\x00\x00\x01\xaa\xe5\xe9\x42

  However, this correct cache entry, when interpreted by the current
  broken code, will return a file-size of 1 byte.  Worse, the existing
  broken entry will be interpreted by my fixed code as containing the
  value 12314505225791602688.

  It would be good to have this patch, or some derivative of it, applied
  to the main APT code-base.  Before this can happen, however, some
  mechanism to detect and correct broken cache entries will be needed if
  we are to avoid a repeat of LP #1274466.

  I would suggest this could be done by checking the trailing four bytes
  of the 64-bit filesize field: if they are all zero, then the cache
  entry is broken, and should be rewritten.

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

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

[Touch-packages] [Bug 1710911] Re: apt-ftparchive does not correctly cache filesizes for packages > 4GB

2017-08-17 Thread David McBride

** Also affects: apt (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872334
   Importance: Unknown
   Status: Unknown

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

Title:
  apt-ftparchive does not correctly cache filesizes for packages > 4GB

Status in apt package in Ubuntu:
  New
Status in apt package in Debian:
  Unknown

Bug description:
  Release: 16.04
  Version: 1.2.19

  apt-ftparchive is a utility for, among other things, generating a
  Packages file from a set of .deb packages.

  Because generating Packages files for a large directory tree of .deb
  packages is expensive, it can cache the properties of .deb packages it
  has already inspected in a Berkeley database file.

  Historically, apt-ftparchive stored the size of a .deb package as a
  32-bit unsigned integer in network byte-order in this cache.  This
  field was later enlarged to 64-bits - which caused other problems;
  see: LP #1274466.

  However, even after this integer field was enlarged, apt-ftparchive
  continued to use the htonl() and ntohl() libc functions to convert
  file-sizes to and from network byte-order when reading and writing to
  its cache.  These functions unconditionally emit 32-bit unsigned
  integers, which means that apt-ftparchive remained unable to correctly
  record the file-sizes for packages > 32bits (i.e. > 4GB).

  Consequently, if apt-ftparchive is asked (with caching enabled) to
  generate a Packages file for a .deb package larger than 4GB, it will
  produce a Packages file with the correct Size: field the first time,
  but with incorrect Size: fields subsequently.

  I have developed a small patch which replaces the use of the ntohl()
  family of functions with suitable replacements from .  This
  produces correct output on new installations.

  However, caution is necessary: the existing code is incorrectly
  storing the 32 least significant bits of a 64-bit number in the upper
  32-bits of a 64-bit field, in big-endian byte order.  The application
  of this patch will cause new values to be stored correctly, but in a
  binary-incompatible way with existing caches.

  For example, a package of size 7162161474 bytes will today have the
  following sequence of bytes stored in its cache entry:

  \xaa\xe5\xe9\x42\x00\x00\x00\x00

  (When re-read, this will produce a file-size value of 7162161474 mod
  32bits, i.e. 2867194178.)

  With this patch applied, apt-ftparchive will correctly store this
  entry:

  \x00\x00\x00\x01\xaa\xe5\xe9\x42

  However, this correct cache entry, when interpreted by the current
  broken code, will return a file-size of 1 byte.  Worse, the existing
  broken entry will be interpreted by my fixed code as containing the
  value 12314505225791602688.

  It would be good to have this patch, or some derivative of it, applied
  to the main APT code-base.  Before this can happen, however, some
  mechanism to detect and correct broken cache entries will be needed if
  we are to avoid a repeat of LP #1274466.

  I would suggest this could be done by checking the trailing four bytes
  of the 64-bit filesize field: if they are all zero, then the cache
  entry is broken, and should be rewritten.

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

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

[Touch-packages] [Bug 1711367] [NEW] New release 1.27.2

2017-08-17 Thread Cristian Aravena Romero

Public bug reported:

Hello,

https://git.busybox.net/busybox/tag/?h=1_27_2

Regards,
--
Cristian

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: busybox (not installed)
ProcVersionSignature: Ubuntu 4.13.0-6.7-generic 4.13.0-rc5
Uname: Linux 4.13.0-6-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Aug 17 10:46:48 2017
InstallationDate: Installed on 2017-07-05 (42 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: busybox
UpgradeStatus: Upgraded to artful on 2017-07-05 (42 days ago)

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


** Tags: amd64 apport-bug artful upgrade-software-version

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

Title:
  New release 1.27.2

Status in busybox package in Ubuntu:
  New

Bug description:
  Hello,

  https://git.busybox.net/busybox/tag/?h=1_27_2

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: busybox (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-6.7-generic 4.13.0-rc5
  Uname: Linux 4.13.0-6-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug 17 10:46:48 2017
  InstallationDate: Installed on 2017-07-05 (42 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: busybox
  UpgradeStatus: Upgraded to artful on 2017-07-05 (42 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-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-08-17 Thread Major Hayden

Thanks for the deep dive, Elvis! :) Is it possible to adjust some of
these settings in the Ubuntu packages, or is just the way it will be
going forward?

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

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 1711011] Re: fsck.jfs may be attempted before multipath devices are available

2017-08-17 Thread Mathieu Trudel-Lapierre

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

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

Title:
  fsck.jfs may be attempted before multipath devices are available

Status in initramfs-tools package in Ubuntu:
  New
Status in jfsutils package in Ubuntu:
  Invalid

Bug description:
  Detected machine type: 0101
  command line: BOOT_IMAGE=/boot/vmlinux-4.11.0-13-generic 
root=UUID=8c6162e8-9bb1-4171-a901-30e001222a14 ro splash quiet
  Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0762
alloc_top: 3000
alloc_top_hi : 00078000
rmo_top  : 3000
ram_top  : 00078000
  instantiating rtas at 0x2fff... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0763 -> 0x076309e6
  Device tree struct  0x0764 -> 0x0765
  Quiescing Open Firmware ...
  Booting Linux via __start() @ 0x0200 ...
   -> smp_release_cpus()
  spinning_secondaries = 7
   <- smp_release_cpus()
  Linux ppc64le
  #19-Ubuntu SMP T[0.970009] Unable to open file: /etc/keys/x509_ima.der 
(-2)
  [0.970011] Unable to open file: /etc/keys/x509_evm.der (-2)
  fsck: error 2 (No such file or directory) while executing fsck.jfs for 
/dev/mapper/mpatha-part2
  fsck exited with status code 8

  
  I haven't investigated more than that, it looks like jfsutils does not 
include anything to copy fsck.jfs to the initramfs. Clearly hooks/fsck in 
initramfs-tools appears to not be doing its job in this case.

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

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

[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2017-08-17 Thread Zinx

Any updates? The same is happening here in my laptop. :(

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1710715] Re: tracker 1.99.2 transition

This bug was fixed in the package tracker-miners - 1.99.2-0ubuntu1

---
tracker-miners (1.99.2-0ubuntu1) artful; urgency=medium

  * Initial release (Closes: #871738) (LP: #1710715)

 -- Jeremy Bicha   Mon, 14 Aug 2017 17:02:24 -0400

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

Title:
  tracker 1.99.2 transition

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker-miners package in Ubuntu:
  Fix Released
Status in tracker package in Debian:
  New

Bug description:
  Tracker bug for tracker!

  GNOME 3.26 includes tracker which bumps the libraries to tracker2.

  Also, tracker-miners is a new source package split from the old
  tracker source package.

  I have done test rebuilds for all packages that will need to be
  rebuilt for this transition in the GNOME3 Staging PPA.

  One nice benefit of the split source packages is that I believe we
  will be able to sync from Debian once Debian packages the new
  versions.

  Debian packaged 1.99.1 but the split happened in 1.99.2 and the Debian
  maintainers haven't had time yet to handle the 1.99.2 uploads. But
  Ubuntu needs this before Ubuntu Feature Freeze so I'm uploading to
  Ubuntu now.

  Debian ITP bug is attached.

  Setting block-proposed flags because I don't want src:tracker to
  migrate to artful this time without src:tracker-miners.

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

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

[Touch-packages] [Bug 1710715] Re: tracker 1.99.2 transition

This bug was fixed in the package tracker - 1.99.2-0ubuntu1

---
tracker (1.99.2-0ubuntu1) artful; urgency=medium

  * Sync with Debian.
  * New upstream release (LP: #1710715)
- tracker-extract and tracker-miner-fs are now provided by the
  tracker-miners source package.
  * Drop all patches, obsolete
  * Dropped change, no longer applicable
- Disable universe dependencies:
  + libencai, libiptcdata, libstemmer

tracker (1.99.1-1) experimental; urgency=medium

  * New upstream version 1.99.1
  * Track unstable releases
  * Drop tracker-miner-evolution
  * Drop tracker-gui
  * Drop obsolete configure switches
  * Rename packages for the API bump from 1.0 → 2.0
  * Drop tracker-miner-user-guides related files
  * Update symbols files
  * Add a Build-Depends-Package field to all symbols files
  * Fix format-security issue in libtracker-data
  * Remove leftover @LIBTRACKER_MINER_PC_REQUIRES@ from tracker-miner.pc.in
  * Install default domain ontology

tracker (1.12.1-1) unstable; urgency=medium

  * New upstream version 1.12.1
  * Bump Standards-Version to 4.0.0

 -- Jeremy Bicha   Mon, 14 Aug 2017 16:58:03 -0400

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

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

Title:
  tracker 1.99.2 transition

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker-miners package in Ubuntu:
  Fix Released
Status in tracker package in Debian:
  New

Bug description:
  Tracker bug for tracker!

  GNOME 3.26 includes tracker which bumps the libraries to tracker2.

  Also, tracker-miners is a new source package split from the old
  tracker source package.

  I have done test rebuilds for all packages that will need to be
  rebuilt for this transition in the GNOME3 Staging PPA.

  One nice benefit of the split source packages is that I believe we
  will be able to sync from Debian once Debian packages the new
  versions.

  Debian packaged 1.99.1 but the split happened in 1.99.2 and the Debian
  maintainers haven't had time yet to handle the 1.99.2 uploads. But
  Ubuntu needs this before Ubuntu Feature Freeze so I'm uploading to
  Ubuntu now.

  Debian ITP bug is attached.

  Setting block-proposed flags because I don't want src:tracker to
  migrate to artful this time without src:tracker-miners.

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

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

[Touch-packages] [Bug 1711067] Re: totem is unable to play .mp4. and some .avi, works fine with .webm. Same videos are played successfully by VLC

2017-08-17 Thread corrado venturini

same .avi and .mp4 are also played successfully by mpv Media Player.
Some .avi are played also by totem and his thumbnails are displayed
correctly.

** Summary changed:

- totem is unable to play .avi and .mp4. works fine with .webm. Same videos are 
played successfully by VLC
+ totem is unable to play .mp4. and some .avi, works fine with .webm. Same 
videos are played successfully by VLC

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

Title:
  totem is unable to play .mp4. and some .avi, works fine with .webm.
  Same videos are played successfully by VLC

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Problem: totem is unable to play .avi and .mp4. works fine with .webm. Same 
videos are played successfully by VLC media player. totem does not crash, but 
just remains with a black screen.
  Another symptom (of same problem?) is avi and mp4 thumbnails are not resolved 
in images.
  I found the problem with an installation from daily 20170807 and have the 
same problem with daily 20170815. 
  How to reproduce problem: try open a .avi or .mp4 (with videos/totem) results 
in a black screen. Here the output starting it from terminal:

  corrado@corrado-HP-aa-0815:~$ cd /media/corrado/dati1/linux/ArtfulBugs/totem
  corrado@corrado-HP-aa-0815:/media/corrado/dati1/linux/ArtfulBugs/totem$ ls
  cagax.avi  prova  vid.mp4
  corrado@corrado-HP-aa-0815:/media/corrado/dati1/linux/ArtfulBugs/totem$ totem 
cagax.avi
  ** Message: Missing plugin: gstreamer|1.0|totem|MPEG-1 Layer 3 (MP3) 
decoder|decoder-audio/mpeg, mpegversion=(int)1, mpegaudioversion=(int)1, 
layer=(int)3 (MPEG-1 Layer 3 (MP3) decoder)
  ** Message: Missing plugin: gstreamer|1.0|totem|MPEG-4 Video 
decoder|decoder-video/mpeg, mpegversion=(int)4, systemstream=(boolean)false 
(MPEG-4 Video decoder)
  ** Message: Automatic missing codec installation not supported (helper script 
missing)

  (totem:8899): Totem-WARNING **: Failed to reset the playback rate to 1.0
  corrado@corrado-HP-aa-0815:/media/corrado/dati1/linux/ArtfulBugs/totem$ totem 
vid.mp4
  ** Message: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC 
decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)1, 
base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
  ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (Constrained Baseline 
Profile) decoder|decoder-video/x-h264, level=(string)3, 
profile=(string)constrained-baseline (H.264 (Constrained Baseline Profile) 
decoder)
  ** Message: Automatic missing codec installation not supported (helper script 
missing)

  (totem:8917): Totem-WARNING **: Failed to reset the playback rate to 1.0
  corrado@corrado-HP-aa-0815:/media/corrado/dati1/linux/ArtfulBugs/totem$ 

  corrado@corrado-HP-aa-0815:/media/corrado/dati1/linux/ArtfulBugs/totem$ apt 
policy totem
  totem:
Installed: 3.25.90.1-0ubuntu1
Candidate: 3.25.90.1-0ubuntu1
Version table:
   *** 3.25.90.1-0ubuntu1 100
  100 /var/lib/dpkg/status
  corrado@corrado-HP-aa-0815:/media/corrado/dati1/linux/ArtfulBugs/totem$ uname 
-a
  Linux corrado-HP-aa-0815 4.11.0-13-generic #19-Ubuntu SMP Thu Aug 3 15:14:11 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  corrado@corrado-HP-aa-0815:/media/corrado/dati1/linux/ArtfulBugs/totem$

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.2-1
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug 16 10:00:26 2017
  InstallationDate: Installed on 2017-08-10 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1711067/+subscriptions

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

[Touch-packages] [Bug 1709708] Re: Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on NUC6CAYH

I was slightly surprised to see the word "Broxton" since Intel canceled
that product line before it was ever released. However that just seems
to be an incorrect label arising from multiple Intel product lines
sharing chipsets... The system is really a J3455 (Apollo Lake) and
shares some silicon with the Broxton line.

Still, since you have a very new system you might find success in using
a newer kernel. So try installing package 'linux-image-generic-
hwe-16.04-edge'. If that does not solve the problem then please try the
very latest from here: http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.12.8/

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

Title:
  Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on NUC6CAYH

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  9 21:48:39 2017
  InstallationDate: Installed on 2017-08-06 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085

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

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

[Touch-packages] [Bug 1607075] Re: systemd 229-4ubuntu7 ADT test failure with linux 4.4.0-33.52

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

** Changed in: console-setup (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  systemd 229-4ubuntu7 ADT test failure with linux 4.4.0-33.52

Status in Auto Package Testing:
  Fix Released
Status in autopkgtest package in Ubuntu:
  Fix Released
Status in console-setup package in Ubuntu:
  New

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/s/systemd/20160727_170251@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1607075/+subscriptions

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

[Touch-packages] [Bug 1709708] Re: Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on NUC6CAYH

2017-08-17 Thread Neilen Marais

Also see askubuntu question: https://askubuntu.com/questions/944735
/silent-hdmi-sound-with-
nuc6cayh-16-04?noredirect=1#comment1505598_944735

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

Title:
  Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on NUC6CAYH

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  9 21:48:39 2017
  InstallationDate: Installed on 2017-08-06 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085

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

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

Re: [Touch-packages] [Bug 1711204] Re: Remove ubuntu-ui-toolkit from the archive

On 16 August 2017 at 22:46, Sebastien Bacher  wrote:
> The components listed on that bug are indeed unmaintained and it doesn't
> make sense to keep them in the archive. +1 from the desktop team to
> remove them but somebody should check the rdepends first, looking at the
> list url-dispatcher could be problematic since it provides a library
> which is used by e.g the unity indicators which we don't plan to remove
> since unity7 is going to remain available in universe
>

Or the indicators in question can drop the unity8 portion of their
profiles that use url-dispatcher.
My understanding was that url-dispatcher / ubuntu-settings apps
codepaths are only used for the touch/unity8 profile, and not the
unity7 profile.


-- 
Regards,

Dimitri.

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

Title:
  Remove ubuntu-ui-toolkit from the archive

Status in checkbox package in Ubuntu:
  Invalid
Status in libertine package in Ubuntu:
  New
Status in notes-app package in Ubuntu:
  New
Status in ubuntu-filemanager-app package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in ubuntu-printing-app package in Ubuntu:
  New
Status in ubuntu-push-qml package in Ubuntu:
  New
Status in ubuntu-settings-components package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in ubuntu-ui-extras package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in ubuntu-ui-toolkit-gles package in Ubuntu:
  New
Status in unity-webapps-qml package in Ubuntu:
  New
Status in url-dispatcher package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The Qt transition is currently blocked by ubuntu-ui-toolkit because
  the version of ubuntu-ui-toolkit in the archive uses Qt 5.7.1 private
  headers that have been since deprecated. ubuntu-ui-toolkit should be
  removed from the archive (unless anyone still needs it, please do make
  your case) and all of it's reverse dependencies (marked as affected on
  this bug report) should either be ported to use native Qt libraries or
  removed from the archive. This is blocking the Qt 5.9 transition, so
  it should be done promptly.

  Full list of reverse dependencies:

  * checkbox-converged(for qml-module-ubuntu-components)
  * libertine-qt-common   (for qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * notes-app (for qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * notes-app-autopilot   (for ubuntu-ui-toolkit-autopilot)
  * qml-module-ubuntu-components-gles [amd64 i386]  (for 
qml-module-ubuntu-components-labs)
  * qml-module-ubuntu-components-gles [amd64 i386]  (for 
ubuntu-ui-toolkit-theme)
  * qml-module-ubuntu-components-labs-gles [amd64 i386]  (for 
ubuntu-ui-toolkit-theme)
  * qml-module-ubuntu-settings-components  (for qml-module-ubuntu-components)
  * qml-module-ubuntu-ui-extras-browser [amd64 arm64 armhf i386]  (for 
qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * qml-module-ubuntu-web [amd64 arm64 armhf i386]  (for 
qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * qtdeclarative5-ubuntu-push-plugin  (for 
qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * qtdeclarative5-ubuntu-ui-extras0.2  (for qml-module-ubuntu-components)
  * ubuntu-filemanager-app(for qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * ubuntu-filemanager-app-autopilot  (for ubuntu-ui-toolkit-autopilot)
  * ubuntu-keyboard-autopilot (for ubuntu-ui-toolkit-autopilot)
  * ubuntu-keyboard-data  (for qml-module-ubuntu-components)
  * ubuntu-printing-app   (for qml-module-ubuntu-components)
  * ubuntu-system-settings(for qml-module-ubuntu-components)
  * ubuntu-system-settings-autopilot  (for ubuntu-ui-toolkit-autopilot)
  * ubuntu-system-settings-online-accounts  (for qml-module-ubuntu-components)
  * unity-webapps-qml [amd64 arm64 armhf i386]  (for 
qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * url-dispatcher(for qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * webapp-container [amd64 arm64 armhf i386]  (for 
qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * webapp-container-autopilot(for ubuntu-ui-toolkit-autopilot)
  * webbrowser-app [amd64 arm64 armhf i386]  (for 
qtdeclarative5-ubuntu-ui-toolkit-plugin)
  * webbrowser-app-autopilot  (for ubuntu-ui-toolkit-autopilot)

  Packages without architectures listed are reverse-dependencies in:
  amd64, arm64, armhf, i386, ppc64el, s390x

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

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

[Touch-packages] [Bug 1711254] Re: 16.04.3 deployments include non-existent directories in $PATH

~/bin ~/.local/bin used to be added in a user path only if they exist.
/snap/bin may or or may not exist, but could be a bug in snapd.

** Package changed: linux-hwe (Ubuntu) => base-files (Ubuntu)

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

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

Title:
  16.04.3 deployments include non-existent directories in $PATH

Status in base-files package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  Noticed this while doing regression testing on 16.04.3, and a number
  of customers have asked with concerns as well during their testing.

  I don't know exactly when this started, but we just started noticing
  it with 16.04.3 (4.10) but $PATH by default now includes several
  directories that do not exist:

  
  ubuntu@above-ox:~$ find $(echo "$PATH" | sed -e 's/:/ /g') -maxdepth 1 -type 
dfind: ‘/home/ubuntu/bin’: No such file or directory
  find: ‘/home/ubuntu/.local/bin’: No such file or directory
  /usr/local/sbin
  /usr/local/bin
  /usr/sbin
  /usr/bin
  /sbin
  /bin
  /usr/games
  /usr/local/games
  find: ‘/snap/bin’: No such file or directory

  We noticed this because it was causing a resource job in the
  certification suite to suddenly start failing (the failure was not
  catastrophic, but it did appear to customers who were concerned.

  I've verified this on both s390x and amd64 16.04.3 deployments via
  MAAS 2.2.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic s390x
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: s390x
  Date: Wed Aug 16 18:59:34 2017
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en.US_UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1711087] Re: ad2p sink profile mic not available

I agree, desktop Linux Bluetooth audio support is a bit immature still,
in places.

However the Bluetooth, audio, and application software interfaces are
all very different between desktop Linux and Android. Android and
desktop Linux (like Ubuntu) don't have much in common there, so of
course they might have different capabilities.

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1711254] [NEW] 16.04.3 deployments include non-existent directories in $PATH

You have been subscribed to a public bug:

Noticed this while doing regression testing on 16.04.3, and a number of
customers have asked with concerns as well during their testing.

I don't know exactly when this started, but we just started noticing it
with 16.04.3 (4.10) but $PATH by default now includes several
directories that do not exist:


ubuntu@above-ox:~$ find $(echo "$PATH" | sed -e 's/:/ /g') -maxdepth 1 -type 
dfind: ‘/home/ubuntu/bin’: No such file or directory
find: ‘/home/ubuntu/.local/bin’: No such file or directory
/usr/local/sbin
/usr/local/bin
/usr/sbin
/usr/bin
/sbin
/bin
/usr/games
/usr/local/games
find: ‘/snap/bin’: No such file or directory

We noticed this because it was causing a resource job in the
certification suite to suddenly start failing (the failure was not
catastrophic, but it did appear to customers who were concerned.

I've verified this on both s390x and amd64 16.04.3 deployments via MAAS
2.2.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic s390x
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: s390x
Date: Wed Aug 16 18:59:34 2017
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en.US_UTF-8
 SHELL=/bin/bash
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug s390x xenial
-- 
16.04.3 deployments include non-existent directories in $PATH
https://bugs.launchpad.net/bugs/1711254
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to base-files 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 1706598] Re: Update bluez to 5.46 in artful

This bug was fixed in the package bluez - 5.46-0ubuntu1

---
bluez (5.46-0ubuntu1) artful; urgency=medium

  [ Konrad Zapałowicz ]
  * New upstream version (lp: #1706598)

  [ Daniel van Vugt ]
  * debian/control:
- update the vcs information

 -- Simon Fels   Wed, 19 Jul 2017 11:46:21
+0200

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

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

Title:
  Update bluez to 5.46 in artful

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The new bluez version is being packaged for artful

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

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

[Touch-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2017-08-17 Thread Jeroen

PS Sorry I didn't mean to be disrespectful, I love (K)ubuntu, it has
been my main operating system for a decade now. Just a bit disappointed
that the relatively new android operating system is more mature here. I
will provide more info later. Thanks for the help so far.

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2017-08-17 Thread Jeroen

not a bug but a feature then lol?

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1711087] Re: ad2p sink profile mic not available

If you could tell us what applications you're using to make calls in
Ubuntu then it's possible someone might be able to reproduce the issue.

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1711087] Re: ad2p sink profile mic not available

That depends what you mean by perfect...

If perfect means Android is switching between A2DP and HFP/HSP
automatically then that's because it's different software you're using
in Android compared to Ubuntu and only the apps you're using in Ubuntu
lack the triggers to switch PulseAudio automatically. Hence application
bug.

If perfect means your hardware is capable of A2DP input and output
simultaneously then I don't know... In that case it's possibly a
shortcoming (missing feature) in BlueZ.

The answer really depends on what your hardware is capable of and what
BlueZ is capable of, and I'm not sure what the answer to either of those
is. You would need to find out more technical details about your Bose
device and possibly contact the developers at bluez.org.

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

Title:
ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
Invalid

Bug description:
I have a bose soundsport bluetooth headset. When I select the ad2p
sink profile there is no microphone available. Only with the HSP
profile my microphone is available.

It's really annoying to have to switch between profiles to make a call
or to listen to normal quality music.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jeroen 3801 F pulseaudio
/dev/snd/controlC0: jeroen 3801 F pulseaudio
CurrentDesktop: KDE
Date: Wed Aug 16 11:02:37 2017
InstallationDate: Installed on 2017-05-10 (98 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1773IMS.106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-1773
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.B
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
dmi.product.name: GS70 2QE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1653892] Re: apport-collect complains about local variable 'browser_obj' referenced before assignment

2017-08-17 Thread Po-Hsu Lin

Can be reproduced on one s390x zVM server as well.
$ apport-cli --version
2.20.4

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

Title:
  apport-collect complains about local variable 'browser_obj' referenced
  before assignment

Status in apport package in Ubuntu:
  New

Bug description:
  While trying to run apport-collect on a arm64 Yakkety server, it
  complains that:

  The authorization page:
   
(https://launchpad.net/+authorize-token?oauth_token=TOKENID_HIDDEN&allow_permission=DESKTOP_INTEGRATION)
  should be opening in your browser. Use your browser to authorize
  this program to access Launchpad on your behalf.
  Waiting to hear from Launchpad about your decision...
  ERROR: connecting to Launchpad failed: local variable 'browser_obj' 
referenced before assignment
  You can reset the credentials by removing the file 
"/home/ubuntu/.cache/apport/launchpad.credentials"

  $ apport-cli --version
  2.20.3

  I connect to this server via ssh, this server is behind a firewall
  with proxy 10.245.64.1 but I can still ping launchpad without any
  problem.

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

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

[Touch-packages] [Bug 1706598] Re: Update bluez to 5.46 in artful

2017-08-17 Thread Sebastien Bacher

Thanks Daniel and sorry about that, I started from what was in the ppa
because that the version that was tested but it missed content from git
and I merged those changes by hand on top, next time I try building from
git directly instead

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

Title:
  Update bluez to 5.46 in artful

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  The new bluez version is being packaged for artful

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

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

[Touch-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2017-08-17 Thread Jeroen

Then why is it that it works perfectly in android?

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1711085] Re: battery icon is distorded under GNOME Shell

This bug was fixed in the package indicator-power -
12.10.6+17.10.20170817-0ubuntu1

---
indicator-power (12.10.6+17.10.20170817-0ubuntu1) artful; urgency=medium

  * Try using unity-* prepended icons before real ones. As the battery
icons in ubuntu-mono aren't square, we want to special case them
(LP: #1711085).
  * Adapt test for the above change.

 -- Didier Roche   Thu, 17 Aug 2017 08:30:02 +0200

** Changed in: indicator-power (Ubuntu)
   Status: New => Fix Released

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

Title:
  battery icon is distorded under GNOME Shell

Status in indicator-power package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Even if https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  themes/+bug/1693155 is fixed, the icon is still distorded in non Hi-
  DPI environment. The issue is that the icons aren't really square.
  Let's use the upstrema indicator icons, while still preserving them in
  the Unity session.

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

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

[Touch-packages] [Bug 1711302] Re: systemd-resolved crashed with SIGSEGV in internal_hashmap_iterate()

2017-08-17 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-resolved crashed with SIGSEGV in internal_hashmap_iterate()

Status in systemd package in Ubuntu:
  New

Bug description:
  random crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 233-8ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Aug 17 09:38:53 2017
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2017-05-19 (89 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  MachineType: TOSHIBA TECRA Z50-A
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-11-generic 
root=UUID=e258a8fb-763e-4568-b5e9-b4ebbddb079e ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7efd738fc16a:movzbl 0x2f(%rdi),%eax
   PC (0x7efd738fc16a) ok
   source "0x2f(%rdi)" (0x48b00750134) not located in a known VMA region 
(needed readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? () from /lib/systemd/libsystemd-shared-233.so
   internal_hashmap_iterate () from /lib/systemd/libsystemd-shared-233.so
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-resolved crashed with SIGSEGV in internal_hashmap_iterate()
  UpgradeStatus: Upgraded to artful on 2017-08-07 (9 days ago)
  UserGroups:
   
  dmi.bios.date: 09/02/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 4.20
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA Z50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion4.20:bd09/02/2015:svnTOSHIBA:pnTECRAZ50-A:pvrPT544E-04S02SDU:rvnTOSHIBA:rnTECRAZ50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA Z50-A
  dmi.product.version: PT544E-04S02SDU
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

2017-08-17 Thread Kushal

Thanks a lot Robert, your fix worked for me on HP AU113TX as well! I
hope this gets fixed in upcoming kernel updates as I don't see HP fixing
it from their end in case it requires vendor fix.

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.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_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

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

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

[Touch-packages] [Bug 1702378] Re: package bsdutils 1:2.27.1-6ubuntu3 [modified: usr/bin/logger usr/bin/renice usr/bin/script usr/bin/scriptreplay usr/bin/wall usr/share/doc/bsdutils/changelog.Debian.