[Touch-packages] [Bug 1718100] Re: package linux-image-extra-4.4.0-96-generic 4.4.0-96.119 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-4.4.0-96-generic 4.4.0-96.119 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I am not able to upgrade.
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem
  Error occurred during upgrading

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-96-generic 4.4.0-96.119
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2199 F pulseaudio
developer   2483 F pulseaudio
   /dev/snd/controlC0:  gdm2199 F pulseaudio
developer   2483 F pulseaudio
  Date: Tue Sep 19 10:48:00 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=b3c90a6e-1f27-4e6c-8769-59ea38c20b57
  InstallationDate: Installed on 2016-12-28 (264 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: Dell Inc. Latitude 3460
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=881f5268-178a-428c-baec-2a6ad9f54308 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
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-96-generic 4.4.0-96.119 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0XPKP0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/04/2016:svnDellInc.:pnLatitude3460:pvr:rvnDellInc.:rn0XPKP0:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3460
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1718100] [NEW] package linux-image-extra-4.4.0-96-generic 4.4.0-96.119 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Shantanu Kondhalkar]

Public bug reported:

I am not able to upgrade.
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem
Error occurred during upgrading

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-96-generic 4.4.0-96.119
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm2199 F pulseaudio
  developer   2483 F pulseaudio
 /dev/snd/controlC0:  gdm2199 F pulseaudio
  developer   2483 F pulseaudio
Date: Tue Sep 19 10:48:00 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=b3c90a6e-1f27-4e6c-8769-59ea38c20b57
InstallationDate: Installed on 2016-12-28 (264 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
MachineType: Dell Inc. Latitude 3460
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=881f5268-178a-428c-baec-2a6ad9f54308 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
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.4.0-96-generic 4.4.0-96.119 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/04/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0XPKP0
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/04/2016:svnDellInc.:pnLatitude3460:pvr:rvnDellInc.:rn0XPKP0:rvrA02:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude 3460
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  package linux-image-extra-4.4.0-96-generic 4.4.0-96.119 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I am not able to upgrade.
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem
  Error occurred during upgrading

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-96-generic 4.4.0-96.119
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2199 F pulseaudio
developer   2483 F pulseaudio
   /dev/snd/controlC0:  gdm2199 F pulseaudio
developer   2483 F pulseaudio
  Date: Tue Sep 19 10:48:00 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=b3c90a6e-1f27-4e6c-8769-59ea38c20b57
  InstallationDate: Installed on 2016-12-28 (264 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: Dell Inc. Latitude 3460
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=881f5268-178a-428c-baec-2a6ad9f54308 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
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-96-generic 4.4.0-96.119 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0XPKP0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/04/2016:svnDellInc.:pnLatitude3460:pvr:rvnDellInc.:rn0XPKP0:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3460
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1718099] Re: package python3-minimal 3.6.2-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python3-minimal 3.6.2-1ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  showed update via update-manager failed. I had --fix missing via
  terminal.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: python3-minimal 3.6.2-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Mon Sep 18 23:10:19 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-07-18 (62 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.2-1ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~rc4
  SourcePackage: python3-defaults
  Title: package python3-minimal 3.6.2-1ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to artful on 2017-08-13 (36 days ago)

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

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

[Touch-packages] [Bug 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration

[Steve Langasek]

avahi-autoipd's dhclient hook exists for stopping and restarting the
avahi-autoipd daemon while other dhclient hooks are running.  I don't
know why exactly it does this but I don't think there's going to be a
relevant equivalent in systemd-networkd.

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

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

Title:
  replacement of isc-dhcp-client with with systemd-networkd for dhclient
  needs integration

Status in avahi package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  New
Status in controlaula package in Ubuntu:
  New
Status in ddclient package in Ubuntu:
  New
Status in maas package in Ubuntu:
  New
Status in madwimax package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in samba package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  dhclient has been used as the dhcp client in Ubuntu and debian for
  many years. Over time, many packages have integrated with dhclient.
  The list below is of packages that have declared a dependency and
  those that have shipped hooks to be invoked by dhclient.

  As we move to systemd-networkd these will have to be addressed.

  # ./get-rdeps isc-dhcp-client | sort -u
  breaks - initramfs-tools (initramfs-tools)
  depends - dracut (dracut-network)
  depends - isc-dhcp (isc-dhcp-client-ddns)
  depends - libguestfs (libguestfs0)
  depends - maas (python3-maas-provisioningserver)
  depends - netscript-2.4 (netscript-2.4)
  depends - network-manager (network-manager)
  depends - ubuntu-meta (ubuntu-minimal)
  depends - walinuxagent (walinuxagent)
  depends - whereami (whereami)
  depends - wicd (wicd-daemon)
  depends - wifi-radar (wifi-radar)
  enhances - resolvconf (resolvconf)
  recommends - avahi (avahi-autoipd)
  recommends - ifupdown (ifupdown)
  recommends - ifupdown2 (ifupdown2)
  recommends - madwimax (madwimax)

  $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u
  avahi-autoipd
  cloud-init
  controlaula
  ddclient
  isc-dhcp-client
  ntp
  ntpdate
  openresolv
  resolvconf
  samba-common
  sendmail-base
  systemd
  whereami

  Another possible integration point that is not likely listed in the package
  dependencies is reading of the leases file for additional information.
  As an example, Azure advertises the location of its http based metadata
  service as an option in a dhclient response.  cloud-init will read the
  lease files to find the correct address.

  Related bugs:
   * bug 1713803: replacement of resolvconf with systemd needs integration 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: isc-dhcp-client 4.3.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 12:46:31 2017
  DhclientLeases:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (788 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718099] [NEW] package python3-minimal 3.6.2-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[starkus]

Public bug reported:

showed update via update-manager failed. I had --fix missing via
terminal.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: python3-minimal 3.6.2-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
Date: Mon Sep 18 23:10:19 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-07-18 (62 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.2-1ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5~rc4
SourcePackage: python3-defaults
Title: package python3-minimal 3.6.2-1ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to artful on 2017-08-13 (36 days ago)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful need-duplicate-check package-from-proposed

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

Title:
  package python3-minimal 3.6.2-1ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  showed update via update-manager failed. I had --fix missing via
  terminal.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: python3-minimal 3.6.2-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Mon Sep 18 23:10:19 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-07-18 (62 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.2-1ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~rc4
  SourcePackage: python3-defaults
  Title: package python3-minimal 3.6.2-1ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to artful on 2017-08-13 (36 days ago)

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

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

[Touch-packages] [Bug 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration

[Steve Langasek]

resolvconf is being dropped at the same time as ifupdown/isc-dhcp-client; there 
is no need to integrate it with systemd-networkd.
openresolv is an alternative implementation of resolvconf which has never been 
used in Ubuntu.

** Changed in: resolvconf (Ubuntu)
   Status: New => Won't Fix

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

Title:
  replacement of isc-dhcp-client with with systemd-networkd for dhclient
  needs integration

Status in avahi package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  New
Status in controlaula package in Ubuntu:
  New
Status in ddclient package in Ubuntu:
  New
Status in maas package in Ubuntu:
  New
Status in madwimax package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in samba package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  dhclient has been used as the dhcp client in Ubuntu and debian for
  many years. Over time, many packages have integrated with dhclient.
  The list below is of packages that have declared a dependency and
  those that have shipped hooks to be invoked by dhclient.

  As we move to systemd-networkd these will have to be addressed.

  # ./get-rdeps isc-dhcp-client | sort -u
  breaks - initramfs-tools (initramfs-tools)
  depends - dracut (dracut-network)
  depends - isc-dhcp (isc-dhcp-client-ddns)
  depends - libguestfs (libguestfs0)
  depends - maas (python3-maas-provisioningserver)
  depends - netscript-2.4 (netscript-2.4)
  depends - network-manager (network-manager)
  depends - ubuntu-meta (ubuntu-minimal)
  depends - walinuxagent (walinuxagent)
  depends - whereami (whereami)
  depends - wicd (wicd-daemon)
  depends - wifi-radar (wifi-radar)
  enhances - resolvconf (resolvconf)
  recommends - avahi (avahi-autoipd)
  recommends - ifupdown (ifupdown)
  recommends - ifupdown2 (ifupdown2)
  recommends - madwimax (madwimax)

  $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u
  avahi-autoipd
  cloud-init
  controlaula
  ddclient
  isc-dhcp-client
  ntp
  ntpdate
  openresolv
  resolvconf
  samba-common
  sendmail-base
  systemd
  whereami

  Another possible integration point that is not likely listed in the package
  dependencies is reading of the leases file for additional information.
  As an example, Azure advertises the location of its http based metadata
  service as an option in a dhclient response.  cloud-init will read the
  lease files to find the correct address.

  Related bugs:
   * bug 1713803: replacement of resolvconf with systemd needs integration 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: isc-dhcp-client 4.3.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 12:46:31 2017
  DhclientLeases:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (788 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration

[Steve Langasek]

madwimax is a network driver package (not a network manager) that
invokes dhclient directly on events.  That looks like something that
should be integrated with systemd-networkd somehow.

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

** No longer affects: walinuxagent (Ubuntu)

** No longer affects: whereami (Ubuntu)

** No longer affects: libguestfs (Ubuntu)

** No longer affects: netscript-2.4 (Ubuntu)

** No longer affects: initramfs-tools (Ubuntu)

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

** No longer affects: wifi-radar (Ubuntu)

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

Title:
  replacement of isc-dhcp-client with with systemd-networkd for dhclient
  needs integration

Status in avahi package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in controlaula package in Ubuntu:
  New
Status in ddclient package in Ubuntu:
  New
Status in maas package in Ubuntu:
  New
Status in madwimax package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in samba package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  dhclient has been used as the dhcp client in Ubuntu and debian for
  many years. Over time, many packages have integrated with dhclient.
  The list below is of packages that have declared a dependency and
  those that have shipped hooks to be invoked by dhclient.

  As we move to systemd-networkd these will have to be addressed.

  # ./get-rdeps isc-dhcp-client | sort -u
  breaks - initramfs-tools (initramfs-tools)
  depends - dracut (dracut-network)
  depends - isc-dhcp (isc-dhcp-client-ddns)
  depends - libguestfs (libguestfs0)
  depends - maas (python3-maas-provisioningserver)
  depends - netscript-2.4 (netscript-2.4)
  depends - network-manager (network-manager)
  depends - ubuntu-meta (ubuntu-minimal)
  depends - walinuxagent (walinuxagent)
  depends - whereami (whereami)
  depends - wicd (wicd-daemon)
  depends - wifi-radar (wifi-radar)
  enhances - resolvconf (resolvconf)
  recommends - avahi (avahi-autoipd)
  recommends - ifupdown (ifupdown)
  recommends - ifupdown2 (ifupdown2)
  recommends - madwimax (madwimax)

  $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u
  avahi-autoipd
  cloud-init
  controlaula
  ddclient
  isc-dhcp-client
  ntp
  ntpdate
  openresolv
  resolvconf
  samba-common
  sendmail-base
  systemd
  whereami

  Another possible integration point that is not likely listed in the package
  dependencies is reading of the leases file for additional information.
  As an example, Azure advertises the location of its http based metadata
  service as an option in a dhclient response.  cloud-init will read the
  lease files to find the correct address.

  Related bugs:
   * bug 1713803: replacement of resolvconf with systemd needs integration 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: isc-dhcp-client 4.3.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 12:46:31 2017
  DhclientLeases:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (788 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1703068] Re: Badly broken rendering of text views

[Launchpad Bug Tracker]

[Expired for gtk+3.0 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Badly broken rendering of text views

Status in gtk+3.0 package in Ubuntu:
  Expired

Bug description:
  Applications utilizing gtk3 text views display terrible rendering
  artifacts on my system. A portion of the canvas immediately below the
  drawn text view gets redrawn (or perhaps more accurately *not*
  redrawn), and then text gets drawn over the top. Subsequent updates to
  the text view will just draw on top of the existing text.

  This is visible in (among other things) gtk3-demo (from
  gtk-3-examples), gnome-calculator, EiskaltDC++ Gtk3. A screenshot
  comparing gtk3-demo and gtk-demo (via gtk2.0-examples) is attached.

  It's a distinct possibility that the real issue is in the video driver
  or compiz or something, but this was my best guess for a starting
  point, since I've isolated the issue to [seemingly] gtk3 text views
  (and possibly also transparency overlay? the top right and bottom left
  of Overlay -> Decorative Overlay exhibits the problem, along with
  Transparency also in the Overlay section of gtk3-demo).

  Kernel: 4.10.0-26-generic
  xorg-server 2:1.19.3-1ubuntu1
  OpenGL vendor string:   Intel Open Source Technology Center
  OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop
  OpenGL version string:  3.0 Mesa 17.0.3

  Although I haven't tried a fresh install, I have confirmed the
  behavior persists in a guest session. The issue had briefly gone away
  a month or two ago, but I didn't have time to closely track what
  changed (presumably: what updates were installed?).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libgtk-3-0 3.22.11-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Jul  7 23:07:37 2017
  InstallationDate: Installed on 2014-11-29 (951 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (85 days ago)

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

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

[Touch-packages] [Bug 1705526] Re: Attempting to print any file through libreoffice fails. the print job is "held", and ultimatly aborted. Successfully printed test page though setting.

[Launchpad Bug Tracker]

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Attempting to print any file through libreoffice fails. the print job
  is "held", and ultimatly aborted. Successfully printed test page
  though setting.

Status in cups package in Ubuntu:
  Expired

Bug description:
  check summary

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CupsErrorLog:
   E [20/Jul/2017:12:03:52 -0400] [Job 468] Aborting job because it has no 
files.
   E [20/Jul/2017:12:04:08 -0400] [Job 469] Aborting job because it has no 
files.
   E [20/Jul/2017:12:11:54 -0400] [Job 471] Aborting job because it has no 
files.
   E [20/Jul/2017:12:19:00 -0400] [Job 472] Aborting job because it has no 
files.
  CurrentDesktop: Unity
  Date: Thu Jul 20 12:20:33 2017
  InstallationDate: Installed on 2015-10-26 (633 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lpstat: device for HP-ENVY-4500-series2: 
hp:/net/ENVY_4500_series?zc=HP3464A98C1A74
  MachineType: Hewlett-Packard p6-2011
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-ENVY-4500-series2.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-ENVY-4500-series2.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=49431aef-63ad-4411-b9ce-5620b8ca8766 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2016-08-06 (347 days ago)
  dmi.bios.date: 08/11/2011
  dmi.bios.vendor: AMI
  dmi.bios.version: 7.14
  dmi.board.name: 2AC2
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 2.00
  dmi.chassis.asset.tag: MXU1400083
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr7.14:bd08/11/2011:svnHewlett-Packard:pnp6-2011:pvr2.00:rvnPEGATRONCORPORATION:rn2AC2:rvr2.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6-2011
  dmi.product.version: 2.00
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1705301] Re: package python-six 1.10.0-3 failed to install/upgrade: підпроцес встановлено post-installation сценарій повернув статус помилку 1

[Launchpad Bug Tracker]

[Expired for six (Ubuntu) because there has been no activity for 60
days.]

** Changed in: six (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package python-six 1.10.0-3 failed to install/upgrade: підпроцес
  встановлено post-installation сценарій повернув статус помилку 1

Status in six package in Ubuntu:
  Expired

Bug description:
  python-six
   python-wrapt
   python-pkg-resources
   python-pyflakes
   pyflakes
   python-lazy-object-proxy
   python-logilab-common
   python-astroid
   pylint
   python-cairo
   python-gobject-2
   python-gtk2
   python-vte
   python-apt
   python-configparser
   python-egenix-mxtools
   python-egenix-mxdatetime
   python-glade2
   python-numpy
   python-pil:amd64
   python-pil.imagetk:amd64
   python-pip
   python-pygame
   python-wheel
   pypar2
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-six 1.10.0-3
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Jul 19 18:54:34 2017
  Dependencies:
   
  ErrorMessage: підпроцес встановлено post-installation сценарій повернув 
статус помилку 1
  InstallationDate: Installed on 2017-02-17 (151 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: six
  Title: package python-six 1.10.0-3 failed to install/upgrade: підпроцес 
встановлено post-installation сценарій повернув статус помилку 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration

[Steve Langasek]

Packages which depend on isc-dhcp-client do so because they invoke the
dhcp client directly for their own purposes.  This will not change;
systemd-networkd does not expose a dhcp client for direct use by other
callers.

** No longer affects: dracut (Ubuntu)

** No longer affects: isc-dhcp (Ubuntu)

** No longer affects: network-manager (Ubuntu)

** No longer affects: ifupdown (Ubuntu)

** No longer affects: ifupdown2 (Ubuntu)

** No longer affects: wicd (Ubuntu)

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

Title:
  replacement of isc-dhcp-client with with systemd-networkd for dhclient
  needs integration

Status in avahi package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in controlaula package in Ubuntu:
  New
Status in ddclient package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in libguestfs package in Ubuntu:
  New
Status in maas package in Ubuntu:
  New
Status in madwimax package in Ubuntu:
  Triaged
Status in netscript-2.4 package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in samba package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in wifi-radar package in Ubuntu:
  New

Bug description:
  dhclient has been used as the dhcp client in Ubuntu and debian for
  many years. Over time, many packages have integrated with dhclient.
  The list below is of packages that have declared a dependency and
  those that have shipped hooks to be invoked by dhclient.

  As we move to systemd-networkd these will have to be addressed.

  # ./get-rdeps isc-dhcp-client | sort -u
  breaks - initramfs-tools (initramfs-tools)
  depends - dracut (dracut-network)
  depends - isc-dhcp (isc-dhcp-client-ddns)
  depends - libguestfs (libguestfs0)
  depends - maas (python3-maas-provisioningserver)
  depends - netscript-2.4 (netscript-2.4)
  depends - network-manager (network-manager)
  depends - ubuntu-meta (ubuntu-minimal)
  depends - walinuxagent (walinuxagent)
  depends - whereami (whereami)
  depends - wicd (wicd-daemon)
  depends - wifi-radar (wifi-radar)
  enhances - resolvconf (resolvconf)
  recommends - avahi (avahi-autoipd)
  recommends - ifupdown (ifupdown)
  recommends - ifupdown2 (ifupdown2)
  recommends - madwimax (madwimax)

  $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u
  avahi-autoipd
  cloud-init
  controlaula
  ddclient
  isc-dhcp-client
  ntp
  ntpdate
  openresolv
  resolvconf
  samba-common
  sendmail-base
  systemd
  whereami

  Another possible integration point that is not likely listed in the package
  dependencies is reading of the leases file for additional information.
  As an example, Azure advertises the location of its http based metadata
  service as an option in a dhclient response.  cloud-init will read the
  lease files to find the correct address.

  Related bugs:
   * bug 1713803: replacement of resolvconf with systemd needs integration 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: isc-dhcp-client 4.3.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 12:46:31 2017
  DhclientLeases:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (788 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718095] Re: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in libxml2 package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Sep 19 11:55:43 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-21 (121 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: libxml2
  Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718042] Re: Fail to upgrade due to error

[dino99]

That newer version now upgrade as expected:

python3-defaults (3.6.2-1ubuntu2) artful; urgency=medium

  * Fix old-versions and unsupported-versions variables in
debian_defaults.

 -- Adam Conrad   Mon, 18 Sep 2017 14:57:07 -0600

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

Title:
  Fail to upgrade due to error

Status in python3-defaults package in Ubuntu:
  Fix Released

Bug description:
  Unpacking python3-minimal (3.6.2-1ubuntu1) over (3.6.1-0ubuntu3) ...
  Setting up python3-minimal (3.6.2-1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 34, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python3/debpython/version.py", line 46, in 
  _config.read('/usr/share/python3/debian_defaults')
File "/usr/lib/python3.6/configparser.py", line 697, in read
  self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1092, in _read
  fpname, lineno)
  configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
  dpkg: error processing package python3-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   python3-minimal
  W: Download is performed unsandboxed as root as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  A package failed to install.  Trying to recover:
  Setting up python3-minimal (3.6.2-1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 34, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python3/debpython/version.py", line 46, in 
  _config.read('/usr/share/python3/debian_defaults')
File "/usr/lib/python3.6/configparser.py", line 697, in read
  self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1092, in _read
  fpname, lineno)
  configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
  dpkg: error processing package python3-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for man-db (2.7.6.1-2) ...
  Errors were encountered while processing:
   python3-minimal

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: python3-minimal 3.6.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 22:52:36 2017
  EcryptfsInUse: Yes
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718095] [NEW] package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[frank shi]

Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Sep 19 11:55:43 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-05-21 (121 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: libxml2
Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in libxml2 package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Sep 19 11:55:43 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-21 (121 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: libxml2
  Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

[Launchpad Bug Tracker]

This bug was fixed in the package xubuntu-meta - 2.216

---
xubuntu-meta (2.216) artful; urgency=medium

  * Refreshed dependencies
  * Added xserver-xorg-input-synaptics to core-recommends, desktop-
recommends (LP: #1686081)
  * Update Standards-Version to 4.0.0
- debian/control

 -- Sean Davis   Mon, 18 Sep 2017 20:44:45
-0400

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

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in xorg package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

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

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

[Touch-packages] [Bug 1718089] Re: package libsystemd0:i386 229-4ubuntu19 failed to install/upgrade: package libsystemd0:i386 is already installed and configured

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libsystemd0:i386 229-4ubuntu19 failed to install/upgrade:
  package libsystemd0:i386 is already installed and configured

Status in systemd package in Ubuntu:
  New

Bug description:
  new ubunt installed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsystemd0:i386 229-4ubuntu19
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  CrashReports:
   600:0:116:482909:2017-09-18 22:16:02.783586740 -0400:2017-09-18 
22:16:03.783586740 -0400:/var/crash/libxau6:i386.0.crash
   600:0:116:482922:2017-09-18 22:16:02.615631103 -0400:2017-09-18 
22:16:03.615631103 -0400:/var/crash/libsystemd0:i386.0.crash
   640:0:116:112106:2017-09-18 16:17:02.395902395 -0400:2017-09-18 
16:17:03.395902395 -0400:/var/crash/_usr_sbin_cron.0.crash
   600:0:116:482919:2017-09-18 22:16:03.671616324 -0400:2017-09-18 
22:16:03.619630059 -0400:/var/crash/libjson-c2:i386.0.crash
  Date: Mon Sep 18 22:16:02 2017
  DuplicateSignature:
   package:libsystemd0:i386:229-4ubuntu19
   Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
   Rebuilding /usr/share/applications/bamf-2.index...
   dpkg: error processing package libsystemd0:i386 (--configure):
package libsystemd0:i386 is already installed and configured
  ErrorMessage: package libsystemd0:i386 is already installed and configured
  InstallationDate: Installed on 2017-09-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: systemd
  Title: package libsystemd0:i386 229-4ubuntu19 failed to install/upgrade: 
package libsystemd0:i386 is already installed and configured
  UpgradeStatus: Upgraded to xenial on 2017-09-18 (0 days ago)

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

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

[Touch-packages] [Bug 1717992] Re: Sound silently plays to "Dummy Output"

[Carlos Eduardo Moreira dos Santos]

The previous kernel I see in /boot is 4.10.0-33. Tomorrow or in the day
after, I'll boot in the older kernel to check whether it's working.

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

Title:
  Sound silently plays to "Dummy Output"

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
  detected, but pavucontrol has only "Dummy Output". Bar animation shows
  audio is playing, but no sound is heard. alsamixer is working fine,
  but audio still can't be heard. Configuration tab says "No cards
  available for configuration".

  $ lspci -v
  0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  # aplay -L
  default
  Playback/recording through the PulseAudio sound server
  null
  Discard all samples (playback) or generate zero samples (capture)
  pulse
  PulseAudio Sound Server
  sysdefault:CARD=PCH
  HDA Intel PCH, ALC3246 Analog
  Default Audio Device
  front:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Front speakers
  surround21:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  2.1 Surround output to Front and Subwoofer speakers
  surround40:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.0 Surround output to Front and Rear speakers
  surround41:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.1 Surround output to Front, Rear and Subwoofer speakers
  surround50:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.0 Surround output to Front, Center and Rear speakers
  surround51:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  surround71:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  hdmi:CARD=PCH,DEV=0
  HDA Intel PCH, HDMI 0
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=1
  HDA Intel PCH, HDMI 1
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=2
  HDA Intel PCH, HDMI 2
  HDMI Audio Output
  dmix:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample mixing device
  dmix:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample mixing device
  dmix:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample mixing device
  dmix:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample mixing device
  dsnoop:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample snooping device
  hw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct hardware device without any conversions
  plughw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Hardware device with all software conversions
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=0bcd17dc-d971-4048-8c1f-d2bb48e8a157
  InstallationDate: Installed on 2017-08-18 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 7460
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic.efi.signed 

[Touch-packages] [Bug 1718089] [NEW] package libsystemd0:i386 229-4ubuntu19 failed to install/upgrade: package libsystemd0:i386 is already installed and configured

[Miguel]

Public bug reported:

new ubunt installed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libsystemd0:i386 229-4ubuntu19
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
CrashReports:
 600:0:116:482909:2017-09-18 22:16:02.783586740 -0400:2017-09-18 
22:16:03.783586740 -0400:/var/crash/libxau6:i386.0.crash
 600:0:116:482922:2017-09-18 22:16:02.615631103 -0400:2017-09-18 
22:16:03.615631103 -0400:/var/crash/libsystemd0:i386.0.crash
 640:0:116:112106:2017-09-18 16:17:02.395902395 -0400:2017-09-18 
16:17:03.395902395 -0400:/var/crash/_usr_sbin_cron.0.crash
 600:0:116:482919:2017-09-18 22:16:03.671616324 -0400:2017-09-18 
22:16:03.619630059 -0400:/var/crash/libjson-c2:i386.0.crash
Date: Mon Sep 18 22:16:02 2017
DuplicateSignature:
 package:libsystemd0:i386:229-4ubuntu19
 Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
 Rebuilding /usr/share/applications/bamf-2.index...
 dpkg: error processing package libsystemd0:i386 (--configure):
  package libsystemd0:i386 is already installed and configured
ErrorMessage: package libsystemd0:i386 is already installed and configured
InstallationDate: Installed on 2017-09-18 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: systemd
Title: package libsystemd0:i386 229-4ubuntu19 failed to install/upgrade: 
package libsystemd0:i386 is already installed and configured
UpgradeStatus: Upgraded to xenial on 2017-09-18 (0 days ago)

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


** Tags: already-installed apport-package i386 xenial

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

Title:
  package libsystemd0:i386 229-4ubuntu19 failed to install/upgrade:
  package libsystemd0:i386 is already installed and configured

Status in systemd package in Ubuntu:
  New

Bug description:
  new ubunt installed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsystemd0:i386 229-4ubuntu19
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  CrashReports:
   600:0:116:482909:2017-09-18 22:16:02.783586740 -0400:2017-09-18 
22:16:03.783586740 -0400:/var/crash/libxau6:i386.0.crash
   600:0:116:482922:2017-09-18 22:16:02.615631103 -0400:2017-09-18 
22:16:03.615631103 -0400:/var/crash/libsystemd0:i386.0.crash
   640:0:116:112106:2017-09-18 16:17:02.395902395 -0400:2017-09-18 
16:17:03.395902395 -0400:/var/crash/_usr_sbin_cron.0.crash
   600:0:116:482919:2017-09-18 22:16:03.671616324 -0400:2017-09-18 
22:16:03.619630059 -0400:/var/crash/libjson-c2:i386.0.crash
  Date: Mon Sep 18 22:16:02 2017
  DuplicateSignature:
   package:libsystemd0:i386:229-4ubuntu19
   Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
   Rebuilding /usr/share/applications/bamf-2.index...
   dpkg: error processing package libsystemd0:i386 (--configure):
package libsystemd0:i386 is already installed and configured
  ErrorMessage: package libsystemd0:i386 is already installed and configured
  InstallationDate: Installed on 2017-09-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: systemd
  Title: package libsystemd0:i386 229-4ubuntu19 failed to install/upgrade: 
package libsystemd0:i386 is already installed and configured
  UpgradeStatus: Upgraded to xenial on 2017-09-18 (0 days ago)

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

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

[Touch-packages] [Bug 1718023] Re: RM: obsolete product

[Daniel van Vugt]

** Changed in: unity-system-compositor (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  RM: obsolete product

Status in unity-system-compositor package in Ubuntu:
  Triaged

Bug description:
  unity-system-compositor was a component of Ubuntu Phone which is no
  longer developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:unity-system-compositor
  No reverse dependencies found

  $ reverse-depends -b src:unity-system-compositor
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1718023/+subscriptions

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

[Touch-packages] [Bug 1717992] Re: Sound silently plays to "Dummy Output"

[Daniel van Vugt]

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

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

Title:
  Sound silently plays to "Dummy Output"

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
  detected, but pavucontrol has only "Dummy Output". Bar animation shows
  audio is playing, but no sound is heard. alsamixer is working fine,
  but audio still can't be heard. Configuration tab says "No cards
  available for configuration".

  $ lspci -v
  0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  # aplay -L
  default
  Playback/recording through the PulseAudio sound server
  null
  Discard all samples (playback) or generate zero samples (capture)
  pulse
  PulseAudio Sound Server
  sysdefault:CARD=PCH
  HDA Intel PCH, ALC3246 Analog
  Default Audio Device
  front:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Front speakers
  surround21:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  2.1 Surround output to Front and Subwoofer speakers
  surround40:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.0 Surround output to Front and Rear speakers
  surround41:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.1 Surround output to Front, Rear and Subwoofer speakers
  surround50:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.0 Surround output to Front, Center and Rear speakers
  surround51:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  surround71:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  hdmi:CARD=PCH,DEV=0
  HDA Intel PCH, HDMI 0
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=1
  HDA Intel PCH, HDMI 1
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=2
  HDA Intel PCH, HDMI 2
  HDMI Audio Output
  dmix:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample mixing device
  dmix:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample mixing device
  dmix:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample mixing device
  dmix:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample mixing device
  dsnoop:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample snooping device
  hw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct hardware device without any conversions
  plughw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Hardware device with all software conversions
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=0bcd17dc-d971-4048-8c1f-d2bb48e8a157
  InstallationDate: Installed on 2017-08-18 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 7460
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic.efi.signed 
root=/dev/mapper/ubu-root ro quiet splash zswap.enabled=1 vt.handoff=7
  

[Touch-packages] [Bug 1717984] Re: [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] Pulseaudio fails to detect card

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1623200
   [Precision 5510, Realtek ALC3266, Speaker, Internal] No sound at all. Or 
underruns, dropouts, crackling sound

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

Title:
  [Precision 5510, Realtek ALC3266, Black Headphone Out, Left]
  Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I can not get audio out. I try the headphone jack, the headphone jack
  on my HDMI display, internal speakers, no nothing zip nada.

  In Miltimedia > PulseAudio Volume Control > Output Devices, there are
  no audio devices. If I Show All Output Devices then a device called
  "silence" is listed. I can turn up the volume on that and see the
  level jumping around but nothing in my ears. The Configuration tab
  says no cards available.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Mon Sep 18 10:27:49 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-14 (339 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Title: [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] 
Pulseaudio fails to detect card
  UpgradeStatus: Upgraded to xenial on 2016-10-14 (339 days ago)
  dmi.bios.date: 08/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.13
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.13:bd08/08/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Launchpad Bug Tracker]

This bug was fixed in the package console-setup - 1.166ubuntu5

---
console-setup (1.166ubuntu5) artful; urgency=medium

  * Don't use console-setup-tty or its udev rule. This dates back to lucid and
now systemd is apparently able to handle this correctly. It's now actively
breaking graphical sessions. (LP: #1710637)

 -- Mathieu Trudel-Lapierre   Mon, 18 Sep 2017
16:36:50 -0400

** Changed in: console-setup (Ubuntu)
   Status: Triaged => Fix Released

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

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

Status in Snappy:
  New
Status in console-setup package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  = Test Cases =

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

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

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

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

  = Original Description =

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

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

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

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

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

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

[Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

[Sean Davis]

Xfce still needs -synaptics, addressed with http://bazaar.launchpad.net
/~xubuntu-dev/ubuntu-seeds/xubuntu.artful/revision/1015

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

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in xorg package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

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

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

[Touch-packages] [Bug 1718042] Re: Fail to upgrade due to error

[P.D.]

Seems to be fixed.

** Changed in: python3-defaults (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Fail to upgrade due to error

Status in python3-defaults package in Ubuntu:
  Fix Released

Bug description:
  Unpacking python3-minimal (3.6.2-1ubuntu1) over (3.6.1-0ubuntu3) ...
  Setting up python3-minimal (3.6.2-1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 34, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python3/debpython/version.py", line 46, in 
  _config.read('/usr/share/python3/debian_defaults')
File "/usr/lib/python3.6/configparser.py", line 697, in read
  self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1092, in _read
  fpname, lineno)
  configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
  dpkg: error processing package python3-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   python3-minimal
  W: Download is performed unsandboxed as root as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  A package failed to install.  Trying to recover:
  Setting up python3-minimal (3.6.2-1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 34, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python3/debpython/version.py", line 46, in 
  _config.read('/usr/share/python3/debian_defaults')
File "/usr/lib/python3.6/configparser.py", line 697, in read
  self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1092, in _read
  fpname, lineno)
  configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
  dpkg: error processing package python3-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for man-db (2.7.6.1-2) ...
  Errors were encountered while processing:
   python3-minimal

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: python3-minimal 3.6.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 22:52:36 2017
  EcryptfsInUse: Yes
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718042] Re: Fail to upgrade due to error

[Launchpad Bug Tracker]

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

** Changed in: python3-defaults (Ubuntu)
   Status: New => Confirmed

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

Title:
  Fail to upgrade due to error

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Unpacking python3-minimal (3.6.2-1ubuntu1) over (3.6.1-0ubuntu3) ...
  Setting up python3-minimal (3.6.2-1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 34, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python3/debpython/version.py", line 46, in 
  _config.read('/usr/share/python3/debian_defaults')
File "/usr/lib/python3.6/configparser.py", line 697, in read
  self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1092, in _read
  fpname, lineno)
  configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
  dpkg: error processing package python3-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   python3-minimal
  W: Download is performed unsandboxed as root as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  A package failed to install.  Trying to recover:
  Setting up python3-minimal (3.6.2-1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 34, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python3/debpython/version.py", line 46, in 
  _config.read('/usr/share/python3/debian_defaults')
File "/usr/lib/python3.6/configparser.py", line 697, in read
  self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1092, in _read
  fpname, lineno)
  configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
  dpkg: error processing package python3-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for man-db (2.7.6.1-2) ...
  Errors were encountered while processing:
   python3-minimal

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: python3-minimal 3.6.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 22:52:36 2017
  EcryptfsInUse: Yes
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1715641] Re: network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet doesn't depend on recent enough glibc

[Bug Watch Updater]

** Changed in: binutils
   Status: Unknown => Confirmed

** Changed in: binutils
   Importance: Unknown => Medium

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

Title:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

Status in binutils:
  Confirmed
Status in binutils package in Ubuntu:
  Triaged
Status in debhelper package in Ubuntu:
  Invalid
Status in dpkg package in Ubuntu:
  Triaged
Status in glibc package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Triaged
Status in dpkg package in Debian:
  New

Bug description:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

  # cat debian/network-manager.substvars 
  misc:Breaks=ppp (<< 2.4.7-1+~), ppp (>= 2.4.7-2~)
  misc:Depends=init-system-helpers (>= 1.18~)
  misc:Pre-Depends=
  shlibs:Depends=libaudit1 (>= 1:2.2.1), libbluetooth3 (>= 4.91), libc6 (>= 
2.17), libcurl3-gnutls (>= 7.16.3), libglib2.0-0 (>= 2.43.2), libgnutls30 (>= 
3.5.0), libjansson4 (>= 2.0.1), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), 
libnewt0.52, libnl-3-200 (>= 3.2.21), libnm0 (>= 1.8.0), libpolkit-agent-1-0 
(>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libpsl5 (>= 0.13.0), libreadline7 
(>= 6.0), libselinux1 (>= 1.32), libsystemd0 (>= 221), libudev1 (>= 183), 
libuuid1 (>= 2.16)

  
  # grep GLIBC_2.25 -r .
  Binary file ./debian/tmp/usr/sbin/NetworkManager matches
  Binary file ./debian/tmp/usr/lib/NetworkManager/nm-iface-helper matches
  Binary file ./debian/network-manager/usr/sbin/NetworkManager matches
  Binary file ./debian/network-manager/usr/lib/NetworkManager/nm-iface-helper 
matches
  Binary file ./src/NetworkManager matches
  Binary file ./src/nm-iface-helper matches
  Binary file ./src/devices/wifi/tests/test-general matches
  Binary file ./src/devices/tests/test-lldp matches
  Binary file ./src/dhcp/tests/test-dhcp-utils matches
  Binary file ./src/dhcp/tests/test-dhcp-dhclient matches
  Binary file ./src/tests/test-resolvconf-capture matches
  Binary file ./src/tests/test-ip4-config matches
  Binary file ./src/tests/test-ip6-config matches
  Binary file ./src/tests/test-general matches
  Binary file ./src/tests/test-systemd matches
  Binary file ./src/tests/config/test-config matches
  Binary file ./src/settings/plugins/keyfile/tests/test-keyfile matches

  # ldd /usr/sbin/NetworkManager   
  /usr/sbin/NetworkManager: /lib/x86_64-linux-gnu/libc.so.6: version 
`GLIBC_2.25' not found (required by /usr/sbin/NetworkManager)

  I will add a manual dep to network-manager but this is weird.

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

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

[Touch-packages] [Bug 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device

[Dan Streetman]

this applies only to trusty; initramfs-tools in later releases is fixed
already.

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

Title:
  update-initramfs fails for MODULES=dep when root is on LVM wich uses
  nvme device

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  [impact]

  On a trusty system, if using MODULES=dep with lvm-on-nvme then update-
  initramfs fails to rebuild the initramfs.  This prevents using
  MODULES=dep for building an initramfs on trusty, with a rootfs that
  uses lvm on nvme.

  [test case]

  install a system where the rootfs uses a LVM logical volume that is
  located on a physical volume on a NVMe drive.  Edit the /etc
  /initramfs-tools/initramfs.conf file and change the MODULES line to
  MODULES=dep and save the file.  Then run sudo update-initramfs -u
  which will fail with:

  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic
  mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry
  mkinitramfs: workaround is MODULES=most
  mkinitramfs: Error please report the bug
  update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1.

  
  [regression potential]

  This changes initramfs creation for rootfs that are on nvme or lvm, so
  has the potential to break it for any system with its rootfs on either
  or both of those.  It is likely to only break initramfs creation, not
  system booting.

  [other info]

  related to bug 1532146

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

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

[Touch-packages] [Bug 1718055] [NEW] update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device

[Dan Streetman]

Public bug reported:

[impact]

On a trusty system, if using MODULES=dep with lvm-on-nvme then update-
initramfs fails to rebuild the initramfs.  This prevents using
MODULES=dep for building an initramfs on trusty, with a rootfs that uses
lvm on nvme.

[test case]

install a system where the rootfs uses a LVM logical volume that is
located on a physical volume on a NVMe drive.  Edit the /etc/initramfs-
tools/initramfs.conf file and change the MODULES line to MODULES=dep and
save the file.  Then run sudo update-initramfs -u which will fail with:

$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic
mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry
mkinitramfs: workaround is MODULES=most
mkinitramfs: Error please report the bug
update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1.


[regression potential]

This changes initramfs creation for rootfs that are on nvme or lvm, so
has the potential to break it for any system with its rootfs on either
or both of those.  It is likely to only break initramfs creation, not
system booting.

[other info]

related to bug 1532146

** Affects: initramfs-tools (Ubuntu)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  update-initramfs fails for MODULES=dep when root is on LVM wich uses
  nvme device

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  [impact]

  On a trusty system, if using MODULES=dep with lvm-on-nvme then update-
  initramfs fails to rebuild the initramfs.  This prevents using
  MODULES=dep for building an initramfs on trusty, with a rootfs that
  uses lvm on nvme.

  [test case]

  install a system where the rootfs uses a LVM logical volume that is
  located on a physical volume on a NVMe drive.  Edit the /etc
  /initramfs-tools/initramfs.conf file and change the MODULES line to
  MODULES=dep and save the file.  Then run sudo update-initramfs -u
  which will fail with:

  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic
  mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry
  mkinitramfs: workaround is MODULES=most
  mkinitramfs: Error please report the bug
  update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1.

  
  [regression potential]

  This changes initramfs creation for rootfs that are on nvme or lvm, so
  has the potential to break it for any system with its rootfs on either
  or both of those.  It is likely to only break initramfs creation, not
  system booting.

  [other info]

  related to bug 1532146

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

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

[Touch-packages] [Bug 1718042] Re: Fail to upgrade due to error

[Dmitry Shachnev]

** Changed in: python3-defaults (Ubuntu)
   Importance: Low => High

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

Title:
  Fail to upgrade due to error

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Unpacking python3-minimal (3.6.2-1ubuntu1) over (3.6.1-0ubuntu3) ...
  Setting up python3-minimal (3.6.2-1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 34, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python3/debpython/version.py", line 46, in 
  _config.read('/usr/share/python3/debian_defaults')
File "/usr/lib/python3.6/configparser.py", line 697, in read
  self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1092, in _read
  fpname, lineno)
  configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
  dpkg: error processing package python3-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   python3-minimal
  W: Download is performed unsandboxed as root as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  A package failed to install.  Trying to recover:
  Setting up python3-minimal (3.6.2-1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 34, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python3/debpython/version.py", line 46, in 
  _config.read('/usr/share/python3/debian_defaults')
File "/usr/lib/python3.6/configparser.py", line 697, in read
  self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1092, in _read
  fpname, lineno)
  configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
  dpkg: error processing package python3-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for man-db (2.7.6.1-2) ...
  Errors were encountered while processing:
   python3-minimal

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: python3-minimal 3.6.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 22:52:36 2017
  EcryptfsInUse: Yes
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1717946] Re: UIFe: Drop xterm and xdiagnose from default install

[Gunnar Hjalmarsson]

Not a problem from a docs POV.

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

Title:
  UIFe: Drop xterm and xdiagnose from default install

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Impact
  ==
  I'm proposing to drop 3 apps from the default Ubuntu 17.10 install:
  XTerm
  UXTerm
  xdiagnose

  These are visible in the Show Applications view of the Activities
  Overview so this could impact screenshots.

  Justification
  =
  These were only in the default install because of the FailsafeX feature.
  Timo Aaltonen (tjaalton), maintainer of Ubuntu's X stack and co-maintainer in 
Debian, has said that feature isn't important any more, considering the 
transition to Wayland.

  xdiagnose also provided some apport hooks for diagnosing display
  problems but that was moved to xorg itself earlier this release cycle.

  xdiagnose currently doesn't run in the Ubuntu session on Wayland.

  https://irclogs.ubuntu.com/2017/09/18/%23ubuntu-desktop.html#t14:18

  Discussed earlier in the cycle:
  https://lists.ubuntu.com/archives/ubuntu-desktop/2017-June/004980.html
  https://lists.ubuntu.com/archives/ubuntu-desktop/2017-July/005059.html

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html
  
https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html

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

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

[Touch-packages] [Bug 1718035] Re: python 3.5 and 2.7 don't provide update-alternatives

[Matthias Klose]

no. it's not just python, but a whole bunch of packages depending on one
of the interpreters. you are breaking the ABI when changing the
alternatives.

please get used to typing python2 or pyhton3.


** Changed in: python2.7 (Ubuntu)
   Status: New => Invalid

** Changed in: python3.5 (Ubuntu)
   Status: New => Invalid

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

Title:
  python 3.5 and 2.7 don't provide update-alternatives

Status in python2.7 package in Ubuntu:
  Invalid
Status in python3.5 package in Ubuntu:
  Invalid

Bug description:
  Python 3.5 and python 2.7 don't currently install themselves as
  alternatives.  Furthermore, install packages that depend on python2
  don't call python2 during their install process and instead call
  python.  When architecting solutions that depend on python pointing to
  python3, this can cause problems installing updates and packages
  through apt as well.  Python system should be updated to always call
  python2 or python3 and not generic python, and python3 and python2
  should provide alternatives by default.

  lsb_release -rd
  Description:Ubuntu 16.04.3 LTS
  Release:16.04

  apt-cache policy python python3
  python:
Installed: 2.7.11-1
Candidate: 2.7.11-1
Version table:
   *** 2.7.11-1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  python3:
Installed: 3.5.1-3
Candidate: 3.5.1-3
Version table:
   *** 3.5.1-3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Expected behaviour:
  Install Python, Install Python 3.
  sudo update-alternatives --config python
  There are 3 choices for the alternative python (providing /usr/bin/python).

SelectionPath Priority   Status
  
0/usr/bin/python2.740auto mode
  * 1/usr/bin/python2.740manual mode
2/usr/bin/python3.540manual mode
3/usr/bin/python3.5m   30manual mode

  Press  to keep the current choice[*], or type selection number:
  2

  sudo apt-get install python-somepackagewhichusespython2;
  apt-get installs successfully here

  What actually happens:
  Install Python, Install Python 3.
  sudo update-alternatives --config python
  Some absurd message about python not being an alternative.

  sudo update-alternatives --install python /usr/bin/python /usr/bin/python2.7 
40
  sudo update-alternatives --install python /usr/bin/python /usr/bin/python3.5 
40
  sudo update-alternatives --install python /usr/bin/python /usr/bin/python3.5m 
30
  sudo update-alternatives --config python
  There are 3 choices for the alternative python (providing /usr/bin/python).

SelectionPath Priority   Status
  
0/usr/bin/python2.740auto mode
  * 1/usr/bin/python2.740manual mode
2/usr/bin/python3.540manual mode
3/usr/bin/python3.5m   30manual mode

  Press  to keep the current choice[*], or type selection number:
  2

  sudo apt-get install python-somepackagewhichusespython2;
  apt-get just blatantly fails here because python points to python 3 now and 
someone didn't think to make them use python2

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

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

[Touch-packages] [Bug 1467588] Re: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (proces

[DiagonalArg]

Specifically, I am trying to use "apport-collect 1718047", but I am getting 
this bug, which causes apport to produce a window saying "No Additional 
Information Collected" and, in the terminal: 
"Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged."


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

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

Title:
  Gtk-Message: GtkDialog mapped without a transient parent. This is
  discouraged. Gtk-Message: GtkDialog mapped without a transient parent.
  This is discouraged.  (process:17035): GLib-CRITICAL **:
  g_slice_set_config: assertion 'sys_page_size == 0' failed

Status in Unity:
  Expired
Status in apport package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in zenity package in Ubuntu:
  Confirmed

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

  (process:17035): GLib-CRITICAL **: g_slice_set_config: assertion
  'sys_page_size == 0' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun 22 16:56:16 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-18-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-20-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1854]
  InstallationDate: Installed on 2015-06-02 (20 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP 2000 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=9ac32e8e-1bbd-4aa9-8f25-2b79e4052d96 ro quiet splash
  SourcePackage: unity
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.3A
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.2A
  dmi.chassis.asset.tag: 5CG3400HTV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.3A:bd06/13/2013:svnHewlett-Packard:pnHP2000NotebookPC:pvr088F130059160:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 2000 Notebook PC
  dmi.product.version: 088F130059160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Mon Jun 22 15:28:27 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 845 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Serhiy Zahoriya]

It's in the DKMS itself. Not sure what the main branch is, but here is an 
example from some branch:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/dkms/vivid-updates/view/head:/dkms#L277

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1700100] Re: Dimmed text is very hard to see

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+17.10.20170918-0ubuntu1

---
ubuntu-themes (16.10+17.10.20170918-0ubuntu1) artful; urgency=medium

  [ Carlo Lobrano ]
  * Added support for GtkTextView::monospace (LP: #1700218)
  * Fixes support GtkTreeView separators (LP: #1701512)
  * Made dimmed text more visible in Gnome Boxes with Ambiance (LP:
#1700100)
  * Added support for vertically linked buttons (LP: #1708141)

  [ Marco Trevisan (Treviño) ]
  * Radiance: use proper button border-image-source for headerbar
elements (LP: #1692925)
  * Ambiance, Radiance: ignore titlebutton theming for appmenu
  * Ambiance, Radiance: add better definition for button destructive-
action (LP: #1697900)

 -- Marco Trevisan (Treviño)   Mon, 18 Sep 2017 18:25:27
+

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

Title:
  Dimmed text is very hard to see

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  To reproduce:
  1- Install gnome-boxes
  2- Start gnome-boxes
  3- Select New -> Enter URL

  There is a dimmed text, which is very hard to see. It starts with
  'Example:...'.

  I believe all GTK text that is styled as "dim-label" are very hard to
  see. This is also apparent in the warning bars in Firefox.

  Here is the line of code of the referred string in gnome-boxes upstream:
  
https://git.gnome.org/browse/gnome-boxes/tree/data/ui/wizard-source.ui?id=f3f581886ead85d5bfcbc71016f37825ed6ee90c#n291

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: light-themes 14.04+16.04.20161024-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 23 16:47:09 2017
  InstallationDate: Installed on 2017-06-21 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1708141] Re: Vertically linked button borders incorrect in Ambiance

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+17.10.20170918-0ubuntu1

---
ubuntu-themes (16.10+17.10.20170918-0ubuntu1) artful; urgency=medium

  [ Carlo Lobrano ]
  * Added support for GtkTextView::monospace (LP: #1700218)
  * Fixes support GtkTreeView separators (LP: #1701512)
  * Made dimmed text more visible in Gnome Boxes with Ambiance (LP:
#1700100)
  * Added support for vertically linked buttons (LP: #1708141)

  [ Marco Trevisan (Treviño) ]
  * Radiance: use proper button border-image-source for headerbar
elements (LP: #1692925)
  * Ambiance, Radiance: ignore titlebutton theming for appmenu
  * Ambiance, Radiance: add better definition for button destructive-
action (LP: #1697900)

 -- Marco Trevisan (Treviño)   Mon, 18 Sep 2017 18:25:27
+

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

Title:
  Vertically linked button borders incorrect in Ambiance

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  GNOME Maps has vertically linked buttons for zoom control.  Looks fine
  with Adwaita, but with Ambiance the border doesn't align when joined
  vertically.  See attached screenshots.

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

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

[Touch-packages] [Bug 1700218] Re: Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+17.10.20170918-0ubuntu1

---
ubuntu-themes (16.10+17.10.20170918-0ubuntu1) artful; urgency=medium

  [ Carlo Lobrano ]
  * Added support for GtkTextView::monospace (LP: #1700218)
  * Fixes support GtkTreeView separators (LP: #1701512)
  * Made dimmed text more visible in Gnome Boxes with Ambiance (LP:
#1700100)
  * Added support for vertically linked buttons (LP: #1708141)

  [ Marco Trevisan (Treviño) ]
  * Radiance: use proper button border-image-source for headerbar
elements (LP: #1692925)
  * Ambiance, Radiance: ignore titlebutton theming for appmenu
  * Ambiance, Radiance: add better definition for button destructive-
action (LP: #1697900)

 -- Marco Trevisan (Treviño)   Mon, 18 Sep 2017 18:25:27
+

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

Title:
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  As found by
  https://github.com/gtimelog/gtimelog/issues/81#issuecomment-170923964,
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace. It
  causes issues on some apps. Gitg is affected as well.

  My temporary workaround: https://quan.hoabinh.vn/blog/2017/6/46-fix-
  gitg-doesn-t-use-monospace-font-in-ubuntu

  Please fix it.

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

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

[Touch-packages] [Bug 1692925] Re: Dark button border in Nautilus CSD with Radiance theme

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+17.10.20170918-0ubuntu1

---
ubuntu-themes (16.10+17.10.20170918-0ubuntu1) artful; urgency=medium

  [ Carlo Lobrano ]
  * Added support for GtkTextView::monospace (LP: #1700218)
  * Fixes support GtkTreeView separators (LP: #1701512)
  * Made dimmed text more visible in Gnome Boxes with Ambiance (LP:
#1700100)
  * Added support for vertically linked buttons (LP: #1708141)

  [ Marco Trevisan (Treviño) ]
  * Radiance: use proper button border-image-source for headerbar
elements (LP: #1692925)
  * Ambiance, Radiance: ignore titlebutton theming for appmenu
  * Ambiance, Radiance: add better definition for button destructive-
action (LP: #1697900)

 -- Marco Trevisan (Treviño)   Mon, 18 Sep 2017 18:25:27
+

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

Title:
  Dark button border in Nautilus CSD with Radiance theme

Status in ubuntu-themes package in Ubuntu:
  Fix Released

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

  $ apt-cache policy light-themes
  light-themes:
Installed: 16.10+17.04.20170406-0ubuntu1
Candidate: 16.10+17.04.20170406-0ubuntu1
Version table:
   *** 16.10+17.04.20170406-0ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://it.archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status

  
  As in the attached picture, the button borders in Nautilus look too dark for 
Radiance theme

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: light-themes 16.10+17.04.20170406-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 23 17:03:30 2017
  InstallationDate: Installed on 2017-04-20 (33 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1701512] Re: Ambiance and Radiance Gtk theme do not properly support GtkTreeView separators

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+17.10.20170918-0ubuntu1

---
ubuntu-themes (16.10+17.10.20170918-0ubuntu1) artful; urgency=medium

  [ Carlo Lobrano ]
  * Added support for GtkTextView::monospace (LP: #1700218)
  * Fixes support GtkTreeView separators (LP: #1701512)
  * Made dimmed text more visible in Gnome Boxes with Ambiance (LP:
#1700100)
  * Added support for vertically linked buttons (LP: #1708141)

  [ Marco Trevisan (Treviño) ]
  * Radiance: use proper button border-image-source for headerbar
elements (LP: #1692925)
  * Ambiance, Radiance: ignore titlebutton theming for appmenu
  * Ambiance, Radiance: add better definition for button destructive-
action (LP: #1697900)

 -- Marco Trevisan (Treviño)   Mon, 18 Sep 2017 18:25:27
+

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

Title:
  Ambiance and Radiance Gtk theme do not properly support GtkTreeView
  separators

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  When using a GtkTreeView with separators (via set_row_separator_func),
  the Ambiance (and Radiance) themes do not render the treeview
  correctly, and it glitches the rows as you move your mouse over it.
  This issue is not present with the default Gtk+ theme, Adwaita.

  A simple python script to show a treeview that exhibits the bug is
  attached.

  Behavior is exhibited on Ubuntu 17.04
  (https://github.com/exaile/exaile/issues/362#issuecomment-308685640)

  Originally reported to the Exaile project at
  https://github.com/exaile/exaile/issues/362.

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

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

[Touch-packages] [Bug 1697900] Re: Small graphical glitch in Nautilus "Delete" button border

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+17.10.20170918-0ubuntu1

---
ubuntu-themes (16.10+17.10.20170918-0ubuntu1) artful; urgency=medium

  [ Carlo Lobrano ]
  * Added support for GtkTextView::monospace (LP: #1700218)
  * Fixes support GtkTreeView separators (LP: #1701512)
  * Made dimmed text more visible in Gnome Boxes with Ambiance (LP:
#1700100)
  * Added support for vertically linked buttons (LP: #1708141)

  [ Marco Trevisan (Treviño) ]
  * Radiance: use proper button border-image-source for headerbar
elements (LP: #1692925)
  * Ambiance, Radiance: ignore titlebutton theming for appmenu
  * Ambiance, Radiance: add better definition for button destructive-
action (LP: #1697900)

 -- Marco Trevisan (Treviño)   Mon, 18 Sep 2017 18:25:27
+

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

Title:
  Small graphical glitch in Nautilus "Delete" button border

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Glitch in the "Delete" button (see the attached screenshots).

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

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

[Touch-packages] [Bug 1718042] Re: upgrading error

[dino99]

'Low' is not the appropriate level here as it cant be upgraded at all;
its a blocker.

** Summary changed:

- upgrading error
+ Fail to upgrade due to error

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

Title:
  Fail to upgrade due to error

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Unpacking python3-minimal (3.6.2-1ubuntu1) over (3.6.1-0ubuntu3) ...
  Setting up python3-minimal (3.6.2-1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 34, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python3/debpython/version.py", line 46, in 
  _config.read('/usr/share/python3/debian_defaults')
File "/usr/lib/python3.6/configparser.py", line 697, in read
  self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1092, in _read
  fpname, lineno)
  configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
  dpkg: error processing package python3-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   python3-minimal
  W: Download is performed unsandboxed as root as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  A package failed to install.  Trying to recover:
  Setting up python3-minimal (3.6.2-1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 34, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python3/debpython/version.py", line 46, in 
  _config.read('/usr/share/python3/debian_defaults')
File "/usr/lib/python3.6/configparser.py", line 697, in read
  self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1092, in _read
  fpname, lineno)
  configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
  dpkg: error processing package python3-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for man-db (2.7.6.1-2) ...
  Errors were encountered while processing:
   python3-minimal

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: python3-minimal 3.6.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 22:52:36 2017
  EcryptfsInUse: Yes
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718042] Re: upgrading error

[Ahmed Shams]

** Changed in: python3-defaults (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Fail to upgrade due to error

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Unpacking python3-minimal (3.6.2-1ubuntu1) over (3.6.1-0ubuntu3) ...
  Setting up python3-minimal (3.6.2-1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 34, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python3/debpython/version.py", line 46, in 
  _config.read('/usr/share/python3/debian_defaults')
File "/usr/lib/python3.6/configparser.py", line 697, in read
  self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1092, in _read
  fpname, lineno)
  configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
  dpkg: error processing package python3-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   python3-minimal
  W: Download is performed unsandboxed as root as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  A package failed to install.  Trying to recover:
  Setting up python3-minimal (3.6.2-1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 34, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python3/debpython/version.py", line 46, in 
  _config.read('/usr/share/python3/debian_defaults')
File "/usr/lib/python3.6/configparser.py", line 697, in read
  self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1092, in _read
  fpname, lineno)
  configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
  dpkg: error processing package python3-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for man-db (2.7.6.1-2) ...
  Errors were encountered while processing:
   python3-minimal

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: python3-minimal 3.6.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 22:52:36 2017
  EcryptfsInUse: Yes
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Brian Murray]

While I've uploaded this fix to Artful for dkms, its not quite clear to
me how the extra files end up getting created.  I've a couple of systems
using dkms and nvidia and I don't see any .old-dkms files on them. For
this to SRU'ed, which I'm happy to do, we'd need a test case which
describes how to recreate the issue. Could someone provide some
information on how to recreate the issue of .old-dkms files filling up
/boot? Thanks in advance!

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1544942] Re: Marks unneeded packages as manually installed, if --dry-run is used

[Brian Murray]

I've uploaded this fix to the SRU queue for Xenial.

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: unattended-upgrades (Ubuntu Xenial)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  Marks unneeded packages as manually installed, if --dry-run is used

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  In Progress

Bug description:
  
  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded:
  marking linux-headers-4.2.0-16-generic for remove
  marking linux-headers-4.2.0-16 for remove
  marking linux-image-4.2.0-16-generic for remove
  marking linux-image-extra-4.2.0-16-generic for remove
  Packages that are auto removed: 'linux-headers-4.2.0-16-generic 
linux-headers-4.2.0-16 linux-image-4.2.0-16-generic 
linux-image-extra-4.2.0-16-generic'
  /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove 
linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all 
linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64
  /usr/bin/dpkg --status-fd 11 --configure --pending
  Packages were successfully auto-removed
  InstCount=0 DelCount=4 BrokenCount=0

  $ apt-mark showauto linux-headers-4.2.0-16-generic:amd64 linux-
  headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux-
  image-4.2.0-16-generic:amd64

  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  No packages found that can be upgraded unattended and no pending auto-removals

  Expect the packages to remain automatically installed after each `sudo
  unattended-upgrade --dry-run -d`.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unattended-upgrades 0.86.2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Feb 12 13:58:29 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-24 (18 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2016-02-12T13:53:13.426454

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

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

[Touch-packages] [Bug 1718042] [NEW] upgrading error

[dino99]

Public bug reported:

Unpacking python3-minimal (3.6.2-1ubuntu1) over (3.6.1-0ubuntu3) ...
Setting up python3-minimal (3.6.2-1ubuntu1) ...
Traceback (most recent call last):
  File "/usr/bin/py3compile", line 34, in 
from debpython.version import SUPPORTED, debsorted, vrepr, \
  File "/usr/share/python3/debpython/version.py", line 46, in 
_config.read('/usr/share/python3/debian_defaults')
  File "/usr/lib/python3.6/configparser.py", line 697, in read
self._read(fp, filename)
  File "/usr/lib/python3.6/configparser.py", line 1092, in _read
fpname, lineno)
configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
dpkg: error processing package python3-minimal (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 python3-minimal
W: Download is performed unsandboxed as root as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up python3-minimal (3.6.2-1ubuntu1) ...
Traceback (most recent call last):
  File "/usr/bin/py3compile", line 34, in 
from debpython.version import SUPPORTED, debsorted, vrepr, \
  File "/usr/share/python3/debpython/version.py", line 46, in 
_config.read('/usr/share/python3/debian_defaults')
  File "/usr/lib/python3.6/configparser.py", line 697, in read
self._read(fp, filename)
  File "/usr/lib/python3.6/configparser.py", line 1092, in _read
fpname, lineno)
configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
dpkg: error processing package python3-minimal (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
 python3-minimal

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: python3-minimal 3.6.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Sep 18 22:52:36 2017
EcryptfsInUse: Yes
SourcePackage: python3-defaults
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful package-from-proposed wayland-session

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

Title:
  upgrading error

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Unpacking python3-minimal (3.6.2-1ubuntu1) over (3.6.1-0ubuntu3) ...
  Setting up python3-minimal (3.6.2-1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 34, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python3/debpython/version.py", line 46, in 
  _config.read('/usr/share/python3/debian_defaults')
File "/usr/lib/python3.6/configparser.py", line 697, in read
  self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1092, in _read
  fpname, lineno)
  configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
  dpkg: error processing package python3-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   python3-minimal
  W: Download is performed unsandboxed as root as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  A package failed to install.  Trying to recover:
  Setting up python3-minimal (3.6.2-1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 34, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python3/debpython/version.py", line 46, in 
  _config.read('/usr/share/python3/debian_defaults')
File "/usr/lib/python3.6/configparser.py", line 697, in read
  self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1092, in _read
  fpname, lineno)
  configparser.DuplicateOptionError: While reading from 
'/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in 
section 'DEFAULT' already exists
  dpkg: error processing package python3-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers 

[Touch-packages] [Bug 1718035] [NEW] python 3.5 and 2.7 don't provide update-alternatives

[Christ Schlacta]

Public bug reported:

Python 3.5 and python 2.7 don't currently install themselves as
alternatives.  Furthermore, install packages that depend on python2
don't call python2 during their install process and instead call python.
When architecting solutions that depend on python pointing to python3,
this can cause problems installing updates and packages through apt as
well.  Python system should be updated to always call python2 or python3
and not generic python, and python3 and python2 should provide
alternatives by default.

lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04

apt-cache policy python python3
python:
  Installed: 2.7.11-1
  Candidate: 2.7.11-1
  Version table:
 *** 2.7.11-1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
python3:
  Installed: 3.5.1-3
  Candidate: 3.5.1-3
  Version table:
 *** 3.5.1-3 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status


Expected behaviour:
Install Python, Install Python 3.
sudo update-alternatives --config python
There are 3 choices for the alternative python (providing /usr/bin/python).

  SelectionPath Priority   Status

  0/usr/bin/python2.740auto mode
* 1/usr/bin/python2.740manual mode
  2/usr/bin/python3.540manual mode
  3/usr/bin/python3.5m   30manual mode

Press  to keep the current choice[*], or type selection number: 2

sudo apt-get install python-somepackagewhichusespython2;
apt-get installs successfully here

What actually happens:
Install Python, Install Python 3.
sudo update-alternatives --config python
Some absurd message about python not being an alternative.

sudo update-alternatives --install python /usr/bin/python /usr/bin/python2.7 40
sudo update-alternatives --install python /usr/bin/python /usr/bin/python3.5 40
sudo update-alternatives --install python /usr/bin/python /usr/bin/python3.5m 30
sudo update-alternatives --config python
There are 3 choices for the alternative python (providing /usr/bin/python).

  SelectionPath Priority   Status

  0/usr/bin/python2.740auto mode
* 1/usr/bin/python2.740manual mode
  2/usr/bin/python3.540manual mode
  3/usr/bin/python3.5m   30manual mode

Press  to keep the current choice[*], or type selection number: 2

sudo apt-get install python-somepackagewhichusespython2;
apt-get just blatantly fails here because python points to python 3 now and 
someone didn't think to make them use python2

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: python3.5 (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: python2.7 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  python 3.5 and 2.7 don't provide update-alternatives

Status in python2.7 package in Ubuntu:
  New
Status in python3.5 package in Ubuntu:
  New

Bug description:
  Python 3.5 and python 2.7 don't currently install themselves as
  alternatives.  Furthermore, install packages that depend on python2
  don't call python2 during their install process and instead call
  python.  When architecting solutions that depend on python pointing to
  python3, this can cause problems installing updates and packages
  through apt as well.  Python system should be updated to always call
  python2 or python3 and not generic python, and python3 and python2
  should provide alternatives by default.

  lsb_release -rd
  Description:Ubuntu 16.04.3 LTS
  Release:16.04

  apt-cache policy python python3
  python:
Installed: 2.7.11-1
Candidate: 2.7.11-1
Version table:
   *** 2.7.11-1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  python3:
Installed: 3.5.1-3
Candidate: 3.5.1-3
Version table:
   *** 3.5.1-3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Expected behaviour:
  Install Python, Install Python 3.
  sudo update-alternatives --config python
  There are 3 choices for the alternative python (providing /usr/bin/python).

SelectionPath Priority   Status
  
0/usr/bin/python2.740auto mode
  * 1/usr/bin/python2.740manual mode
2/usr/bin/python3.540manual mode
3/usr/bin/python3.5m   

[Touch-packages] [Bug 1544942] Re: Marks unneeded packages as manually installed, if --dry-run is used

[Brian Murray]

** Also affects: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Marks unneeded packages as manually installed, if --dry-run is used

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  New

Bug description:
  
  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded:
  marking linux-headers-4.2.0-16-generic for remove
  marking linux-headers-4.2.0-16 for remove
  marking linux-image-4.2.0-16-generic for remove
  marking linux-image-extra-4.2.0-16-generic for remove
  Packages that are auto removed: 'linux-headers-4.2.0-16-generic 
linux-headers-4.2.0-16 linux-image-4.2.0-16-generic 
linux-image-extra-4.2.0-16-generic'
  /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove 
linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all 
linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64
  /usr/bin/dpkg --status-fd 11 --configure --pending
  Packages were successfully auto-removed
  InstCount=0 DelCount=4 BrokenCount=0

  $ apt-mark showauto linux-headers-4.2.0-16-generic:amd64 linux-
  headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux-
  image-4.2.0-16-generic:amd64

  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  No packages found that can be upgraded unattended and no pending auto-removals

  Expect the packages to remain automatically installed after each `sudo
  unattended-upgrade --dry-run -d`.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unattended-upgrades 0.86.2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Feb 12 13:58:29 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-24 (18 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2016-02-12T13:53:13.426454

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

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

[Touch-packages] [Bug 1718030] Re: libhybris fails to build with glibc 2.26

[Steve Langasek]

Simon, you appear to still be committing changes upstream in
.  Do you care about this being
fixed in Ubuntu 17.10?

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

Title:
  libhybris fails to build with glibc 2.26

Status in libhybris package in Ubuntu:
  New

Bug description:
  The libhybris package fails to build against glibc 2.26:

  In file included from hooks.c:42:0:
  /usr/include/dirent.h:183:12: note: declared here
   extern int readdir_r (DIR *__restrict __dirp,
  ^
  hooks.c: At top level:
  hooks.c:2368:15: error: ‘cfree’ undeclared here (not in a function); did you 
mean ‘free’?
   {"cfree", cfree },
 ^
 free
  hooks.c:2618:16: error: ‘writev’ undeclared here (not in a function); did you 
mean ‘write’?
   {"writev", writev},
  ^~
  write
  Makefile:537: recipe for target 'libhybris_common_la-hooks.lo' failed
  make[4]: *** [libhybris_common_la-hooks.lo] Error 1

  
https://launchpad.net/ubuntu/+source/libhybris/0.1.0+git20151016+6d424c9-0ubuntu25

  Because libhybris has a strict versioned dependency against glibc, it
  cannot be included in Ubuntu 17.10 without resolving this build
  failure.

  I see that there is an active upstream, so perhaps they would like to
  fix this build failure and continue to include libhybris in Ubuntu
  17.10.

  It is also possible that there is no longer any interest in
  maintaining libhybris in Ubuntu because there is no longer an Ubuntu
  Touch product based on this, and therefore this package should be
  removed.

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

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

[Touch-packages] [Bug 1718029] [NEW] cloudstack and azure datasources broken when using netplan/systemd-networkd

[Scott Moser]

Public bug reported:

In Ubuntu artful, cloud-init renders network configuration through netplan.
This means that there is no dhclient and thus no /var/lib/dhclient/*.leases.

Azure and CloudStack both are reading those leases file to get useful
information about the platform.

Specifically:
 * Azure reads option-245 from the dhclient response to find the IP address of 
the metadata service.
 * CloudStack reads the 'dhcp-server-identifier' option in the dhclient 
response to get the address of the virtual router (metadata service). [1]

In ubuntu this happens to be done with systemd-networkd, so cloud-init
can possibly probably interact over the dbus with systemd-networkd to
get information.  However that is less than ideal, as ultimately cloud-
init should not need to know that it systemd-networkd is involved.  It
should be hidden via netplan.  So there should be an interface to get
current networking configuratoin information from netplan including dhcp
lease response info.


--
[1] 
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.8/virtual_machines/user-data.html

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: cloud-init 0.7.9-280-ge626966e-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CloudName: Amazon - Ec2
Date: Mon Sep 18 19:56:40 2017
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)
user_data.txt:
 #cloud-config
 {}

** Affects: netplan
 Importance: Undecided
 Status: New

** Affects: cloud-init (Ubuntu)
 Importance: Critical
 Status: Confirmed

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

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


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

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

** Also affects: netplan
   Importance: Undecided
   Status: New

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

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Critical

** Changed in: cloud-init (Ubuntu)
   Status: New => Confirmed

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

Title:
  cloudstack and azure datasources broken when using netplan/systemd-
  networkd

Status in netplan:
  New
Status in cloud-init package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  In Ubuntu artful, cloud-init renders network configuration through netplan.
  This means that there is no dhclient and thus no /var/lib/dhclient/*.leases.

  Azure and CloudStack both are reading those leases file to get useful
  information about the platform.

  Specifically:
   * Azure reads option-245 from the dhclient response to find the IP address 
of the metadata service.
   * CloudStack reads the 'dhcp-server-identifier' option in the dhclient 
response to get the address of the virtual router (metadata service). [1]

  In ubuntu this happens to be done with systemd-networkd, so cloud-init
  can possibly probably interact over the dbus with systemd-networkd to
  get information.  However that is less than ideal, as ultimately
  cloud-init should not need to know that it systemd-networkd is
  involved.  It should be hidden via netplan.  So there should be an
  interface to get current networking configuratoin information from
  netplan including dhcp lease response info.

  
  --
  [1] 
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.8/virtual_machines/user-data.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cloud-init 0.7.9-280-ge626966e-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CloudName: Amazon - Ec2
  Date: Mon Sep 18 19:56:40 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)
  user_data.txt:
   #cloud-config
   {}

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

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

[Touch-packages] [Bug 1718030] [NEW] libhybris fails to build with glibc 2.26

[Steve Langasek]

Public bug reported:

The libhybris package fails to build against glibc 2.26:

In file included from hooks.c:42:0:
/usr/include/dirent.h:183:12: note: declared here
 extern int readdir_r (DIR *__restrict __dirp,
^
hooks.c: At top level:
hooks.c:2368:15: error: ‘cfree’ undeclared here (not in a function); did you 
mean ‘free’?
 {"cfree", cfree },
   ^
   free
hooks.c:2618:16: error: ‘writev’ undeclared here (not in a function); did you 
mean ‘write’?
 {"writev", writev},
^~
write
Makefile:537: recipe for target 'libhybris_common_la-hooks.lo' failed
make[4]: *** [libhybris_common_la-hooks.lo] Error 1

https://launchpad.net/ubuntu/+source/libhybris/0.1.0+git20151016+6d424c9-0ubuntu25

Because libhybris has a strict versioned dependency against glibc, it
cannot be included in Ubuntu 17.10 without resolving this build failure.

I see that there is an active upstream, so perhaps they would like to
fix this build failure and continue to include libhybris in Ubuntu
17.10.

It is also possible that there is no longer any interest in maintaining
libhybris in Ubuntu because there is no longer an Ubuntu Touch product
based on this, and therefore this package should be removed.

** Affects: libhybris (Ubuntu)
 Importance: Undecided
 Assignee: Simon Fels (morphis)
 Status: New

** Changed in: libhybris (Ubuntu)
 Assignee: (unassigned) => Simon Fels (morphis)

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

Title:
  libhybris fails to build with glibc 2.26

Status in libhybris package in Ubuntu:
  New

Bug description:
  The libhybris package fails to build against glibc 2.26:

  In file included from hooks.c:42:0:
  /usr/include/dirent.h:183:12: note: declared here
   extern int readdir_r (DIR *__restrict __dirp,
  ^
  hooks.c: At top level:
  hooks.c:2368:15: error: ‘cfree’ undeclared here (not in a function); did you 
mean ‘free’?
   {"cfree", cfree },
 ^
 free
  hooks.c:2618:16: error: ‘writev’ undeclared here (not in a function); did you 
mean ‘write’?
   {"writev", writev},
  ^~
  write
  Makefile:537: recipe for target 'libhybris_common_la-hooks.lo' failed
  make[4]: *** [libhybris_common_la-hooks.lo] Error 1

  
https://launchpad.net/ubuntu/+source/libhybris/0.1.0+git20151016+6d424c9-0ubuntu25

  Because libhybris has a strict versioned dependency against glibc, it
  cannot be included in Ubuntu 17.10 without resolving this build
  failure.

  I see that there is an active upstream, so perhaps they would like to
  fix this build failure and continue to include libhybris in Ubuntu
  17.10.

  It is also possible that there is no longer any interest in
  maintaining libhybris in Ubuntu because there is no longer an Ubuntu
  Touch product based on this, and therefore this package should be
  removed.

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

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

[Touch-packages] [Bug 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install

[Brian Murray]

I followed the test case in the bug description and installed python
version 3.5.1 in /usr/local/bin and did receive the traceback from the
description when reinstalling python3.5.  I then modified my
/etc/apt/sources.list file to enable -proposed ran 'apt-get update' and
then installed python3.5 from zesty-proposed.

Get:1 http://archive.ubuntu.com/ubuntu zesty-proposed/main amd64 libpython3.5 
amd64 3.5.3-1ubuntu0~17.04.1 [1,372 kB]
Get:2 http://archive.ubuntu.com/ubuntu zesty-proposed/main amd64 python3.5 
amd64 3.5.3-1ubuntu0~17.04.1 [175 kB]
Get:3 http://archive.ubuntu.com/ubuntu zesty-proposed/main amd64 
libpython3.5-stdlib amd64 3.5.3-1ubuntu0~17.04.1 [2,167 kB]
Get:4 http://archive.ubuntu.com/ubuntu zesty-proposed/main amd64 
python3.5-minimal amd64 3.5.3-1ubuntu0~17.04.1 [1,635 kB]
Get:5 http://archive.ubuntu.com/ubuntu zesty-proposed/main amd64 
libpython3.5-minimal amd64 3.5.3-1ubuntu0~17.04.1 [529 kB]
Fetched 5,877 kB in 1s (3,560 kB/s)
(Reading database ... 229111 files and directories currently installed.)
Preparing to unpack .../libpython3.5_3.5.3-1ubuntu0~17.04.1_amd64.deb ...
Unpacking libpython3.5:amd64 (3.5.3-1ubuntu0~17.04.1) over 
(3.5.3-1ubuntu0~17.04.0) ...
Preparing to unpack .../python3.5_3.5.3-1ubuntu0~17.04.1_amd64.deb ...
Unpacking python3.5 (3.5.3-1ubuntu0~17.04.1) over (3.5.3-1ubuntu0~17.04.0) ...
Preparing to unpack .../libpython3.5-stdlib_3.5.3-1ubuntu0~17.04.1_amd64.deb ...
Unpacking libpython3.5-stdlib:amd64 (3.5.3-1ubuntu0~17.04.1) over 
(3.5.3-1ubuntu0~17.04.0) ...
Preparing to unpack .../python3.5-minimal_3.5.3-1ubuntu0~17.04.1_amd64.deb ...
Unpacking python3.5-minimal (3.5.3-1ubuntu0~17.04.1) over 
(3.5.3-1ubuntu0~17.04.0) ...
Preparing to unpack .../libpython3.5-minimal_3.5.3-1ubuntu0~17.04.1_amd64.deb 
...
Unpacking libpython3.5-minimal:amd64 (3.5.3-1ubuntu0~17.04.1) over 
(3.5.3-1ubuntu0~17.04.0) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
Processing triggers for bamfdaemon (0.5.3+17.04.20170406-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for libc-bin (2.24-9ubuntu2.2) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu5) ...
Setting up libpython3.5-minimal:amd64 (3.5.3-1ubuntu0~17.04.1) ...
Setting up libpython3.5-stdlib:amd64 (3.5.3-1ubuntu0~17.04.1) ...
Setting up python3.5-minimal (3.5.3-1ubuntu0~17.04.1) ...
Setting up python3.5 (3.5.3-1ubuntu0~17.04.1) ...
Setting up libpython3.5:amd64 (3.5.3-1ubuntu0~17.04.1) ...
Processing triggers for libc-bin (2.24-9ubuntu2.2) ...

No traceback!

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

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

Title:
  python3 in /usr/local/bin can cause python3 packages to fail to
  install

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.5 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  New
Status in python3.5 source package in Xenial:
  Fix Committed
Status in python2.7 source package in Zesty:
  New
Status in python3.5 source package in Zesty:
  Fix Committed
Status in python3.5 package in Debian:
  Fix Released

Bug description:
  [Impact]
  An upgrade of python3.5 will fail if someone has installed a different 
version of python3.5 in their path e.g. in /usr/local/bin. This is because the 
postinst scripts do not specify the complete path to python3.5.

  [Test Case]
  1) Ensure the version of python3.5 from the release pocket is installed
  2) Install python3 using the instructions at 
https://passingcuriosity.com/2015/installing-python-from-source/
  3) Confirm that python3.5 from /usr/local/bin/ is being used / the default
  4) Upgrade to a newer version of python3.5 from -proposed

  Observe the following Traceback:

  Setting up python3.5-minimal (3.5.3-1) ...
  Traceback (most recent call last):
File "/usr/lib/python3.5/py_compile.py", line 6, in 
  import importlib._bootstrap_external
File "/usr/lib/python3.5/importlib/__init__.py", line 57, in 
  import types
File "/usr/lib/python3.5/types.py", line 166, in 
  import functools as _functools
File "/usr/lib/python3.5/functools.py", line 23, in 
  from weakref import WeakKeyDictionary
File "/usr/lib/python3.5/weakref.py", line 12, in 
  from _weakref import (
  ImportError: cannot import name '_remove_dead_weakref'
  dpkg: error processing package python3.5-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of python3-minimal:
   python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
Package python3.5-minimal is not configured yet.

  dpkg: error processing package python3-minimal 

[Touch-packages] [Bug 1718027] [NEW] RM: obsolete product

[Dimitri John Ledkov]

Public bug reported:

libusermetrics was a component of Ubuntu Phone which is no longer
developed.

Please remove this package from the Ubuntu Archive.

$ reverse-depends src:libusermetrics
No reverse dependencies found

$ reverse-depends -b src:libusermetrics
No reverse dependencies found

** Affects: libusermetrics (Ubuntu)
 Importance: Undecided
 Status: Triaged


** Tags: u8rm

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

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

Title:
  RM: obsolete product

Status in libusermetrics package in Ubuntu:
  Triaged

Bug description:
  libusermetrics was a component of Ubuntu Phone which is no longer
  developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:libusermetrics
  No reverse dependencies found

  $ reverse-depends -b src:libusermetrics
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1717992] Re: Sound silently plays to "Dummy Output"

[Sebastien Bacher]

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

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

Title:
  Sound silently plays to "Dummy Output"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
  detected, but pavucontrol has only "Dummy Output". Bar animation shows
  audio is playing, but no sound is heard. alsamixer is working fine,
  but audio still can't be heard. Configuration tab says "No cards
  available for configuration".

  $ lspci -v
  0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  # aplay -L
  default
  Playback/recording through the PulseAudio sound server
  null
  Discard all samples (playback) or generate zero samples (capture)
  pulse
  PulseAudio Sound Server
  sysdefault:CARD=PCH
  HDA Intel PCH, ALC3246 Analog
  Default Audio Device
  front:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Front speakers
  surround21:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  2.1 Surround output to Front and Subwoofer speakers
  surround40:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.0 Surround output to Front and Rear speakers
  surround41:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.1 Surround output to Front, Rear and Subwoofer speakers
  surround50:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.0 Surround output to Front, Center and Rear speakers
  surround51:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  surround71:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  hdmi:CARD=PCH,DEV=0
  HDA Intel PCH, HDMI 0
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=1
  HDA Intel PCH, HDMI 1
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=2
  HDA Intel PCH, HDMI 2
  HDMI Audio Output
  dmix:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample mixing device
  dmix:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample mixing device
  dmix:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample mixing device
  dmix:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample mixing device
  dsnoop:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample snooping device
  hw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct hardware device without any conversions
  plughw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Hardware device with all software conversions

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

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

[Touch-packages] [Bug 1716137] Re: Error message using easy-codec-install (gstreamer1.0-packagekit) is not useful & confusing

[Doug McMahon]

On 09/18/2017 08:40 AM, Sebastien Bacher wrote:
> Thanks, could you describe what you do exactly though/what steps you
> take to trigger the action?
>
> ** Changed in: packagekit (Ubuntu)
> Importance: Undecided => Low
>
Updated description on how..


** Description changed:

  See attached screen
+ 
+ Test case:
+ On a fresh install or if on existing make sure the gst bad, ugly, libav & 
vaapi plugins aren't installed.
+ Try to open a h.264 video or .mp3, .m4a in totem
+ When prompted click on the find in Software button
+ Error message will appear at top of Software window
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gstreamer1.0-packagekit 1.1.6-2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  9 10:56:17 2017
  InstallationDate: Installed on 2017-09-07 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: packagekit
  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 packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1716137

Title:
  Error message using easy-codec-install (gstreamer1.0-packagekit) is
  not useful & confusing

Status in packagekit package in Ubuntu:
  New

Bug description:
  See attached screen

  Test case:
  On a fresh install or if on existing make sure the gst bad, ugly, libav & 
vaapi plugins aren't installed.
  Try to open a h.264 video or .mp3, .m4a in totem
  When prompted click on the find in Software button
  Error message will appear at top of Software window

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gstreamer1.0-packagekit 1.1.6-2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  9 10:56:17 2017
  InstallationDate: Installed on 2017-09-07 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718022] [NEW] RM: obsolete product

[Dimitri John Ledkov]

Public bug reported:

telepathy-ofono was a component of Ubuntu Phone which is no longer
developed.

Please remove this package from the Ubuntu Archive.

$ reverse-depends src:telepathy-ofono
No reverse dependencies found

$ reverse-depends -b src:telepathy-ofono
No reverse dependencies found

** Affects: telepathy-ofono (Ubuntu)
 Importance: Undecided
 Status: Triaged


** Tags: u8rm

** Changed in: telepathy-ofono (Ubuntu)
   Status: New => Triaged

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

Title:
  RM: obsolete product

Status in telepathy-ofono package in Ubuntu:
  Triaged

Bug description:
  telepathy-ofono was a component of Ubuntu Phone which is no longer
  developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:telepathy-ofono
  No reverse dependencies found

  $ reverse-depends -b src:telepathy-ofono
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1718023] [NEW] RM: obsolete product

[Dimitri John Ledkov]

Public bug reported:

unity-system-compositor was a component of Ubuntu Phone which is no
longer developed.

Please remove this package from the Ubuntu Archive.

$ reverse-depends src:unity-system-compositor
No reverse dependencies found

$ reverse-depends -b src:unity-system-compositor
No reverse dependencies found

** Affects: unity-system-compositor (Ubuntu)
 Importance: Undecided
 Status: Triaged


** Tags: u8rm

** Changed in: unity-system-compositor (Ubuntu)
   Status: New => Triaged

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

Title:
  RM: obsolete product

Status in unity-system-compositor package in Ubuntu:
  Triaged

Bug description:
  unity-system-compositor was a component of Ubuntu Phone which is no
  longer developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:unity-system-compositor
  No reverse dependencies found

  $ reverse-depends -b src:unity-system-compositor
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1718023/+subscriptions

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

[Touch-packages] [Bug 1717649] Re: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: 설치한 post-installation 스크립트 하위 프로세스가 오류 1번을 리턴했습니다

[Leonidas S. Barbosa]

Hi,

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

I checked your logs and by this line in VarLogDistupgradeApttermlog
"gzip: stdout: No space left on device" seems you run out of space and
that could be the cause.


** Information type changed from Private Security to Public

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

Title:
  package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: 설치한
  post-installation 스크립트 하위 프로세스가 오류 1번을 리턴했습니다

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  ..

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 3.2.0-64.97-generic 3.2.59
  Uname: Linux 3.2.0-64-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Sat Sep 16 15:33:23 2017
  DuplicateSignature: package:initramfs-tools:0.103ubuntu4.7:설치한 
post-installation 스크립트 하위 프로세스가 오류 1번을 리턴했습니다
  ErrorMessage: 설치한 post-installation 스크립트 하위 프로세스가 오류 1번을 리턴했습니다
  InstallationDate: Installed on 2012-08-28 (1845 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: 설치한 
post-installation 스크립트 하위 프로세스가 오류 1번을 리턴했습니다
  UpgradeStatus: Upgraded to trusty on 2017-09-16 (0 days ago)

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

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

[Touch-packages] [Bug 1717649] Re: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: 설치한 post-installation 스크립트 하위 프로세스가 오류 1번을 리턴했습니다

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: 설치한
  post-installation 스크립트 하위 프로세스가 오류 1번을 리턴했습니다

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  ..

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 3.2.0-64.97-generic 3.2.59
  Uname: Linux 3.2.0-64-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Sat Sep 16 15:33:23 2017
  DuplicateSignature: package:initramfs-tools:0.103ubuntu4.7:설치한 
post-installation 스크립트 하위 프로세스가 오류 1번을 리턴했습니다
  ErrorMessage: 설치한 post-installation 스크립트 하위 프로세스가 오류 1번을 리턴했습니다
  InstallationDate: Installed on 2012-08-28 (1845 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: 설치한 
post-installation 스크립트 하위 프로세스가 오류 1번을 리턴했습니다
  UpgradeStatus: Upgraded to trusty on 2017-09-16 (0 days ago)

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

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

[Touch-packages] [Bug 1717997] Re: cannot log off new user in test case

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1717997

** Tags added: iso-testing

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

Title:
  cannot log off new user in test case

Status in lightdm package in Ubuntu:
  New

Bug description:
  during post install test case .. cannot log off new user .. but all
  else works just fine

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lightdm 1.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Sep 18 14:35:50 2017
  InstallationDate: Installed on 2017-09-18 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install

[Brian Murray]

I tried recreating the bug as described in the description and
py_compile.py in the version of python3.5 on Xenial does not import
_remove_dead_weakref so there is not Traceback when trying to reinstall
python3.5 after installing python3.5 in /usr/local/bin.  However, its
still possible to verify the fix by confirming that the file
/var/lib/dpkg/python3.5.postinst and other postinst scripts now use the
full path to python3.5 when calling py_compile.py e.g.:

bdmurray@clean-xenial-amd64:/var/lib/dpkg/info$ grep "py_compile.py" *.postinst
python2.7-minimal.postinst: python2.7 -E -S 
/usr/lib/python2.7/py_compile.py $files
python2.7-minimal.postinst: python2.7 -E -S -O 
/usr/lib/python2.7/py_compile.py $files
python2.7.postinst: python2.7 -E -S /usr/lib/python2.7/py_compile.py 
$files
python2.7.postinst: python2.7 -E -S -O 
/usr/lib/python2.7/py_compile.py $files
python3.5-minimal.postinst: /usr/bin/python3.5 -E -S 
/usr/lib/python3.5/py_compile.py $files
python3.5-minimal.postinst: /usr/bin/python3.5 -E -S -O 
/usr/lib/python3.5/py_compile.py $files
python3.5.postinst: /usr/bin/python3.5 -E -S 
/usr/lib/python3.5/py_compile.py $files
python3.5.postinst: /usr/bin/python3.5 -E -S -O 
/usr/lib/python3.5/py_compile.py $files

We can see this is fixed for python3.5 but not python2.7 so setting to
verification-done for xenial.

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

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

Title:
  python3 in /usr/local/bin can cause python3 packages to fail to
  install

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.5 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  New
Status in python3.5 source package in Xenial:
  Fix Committed
Status in python2.7 source package in Zesty:
  New
Status in python3.5 source package in Zesty:
  Fix Committed
Status in python3.5 package in Debian:
  Fix Released

Bug description:
  [Impact]
  An upgrade of python3.5 will fail if someone has installed a different 
version of python3.5 in their path e.g. in /usr/local/bin. This is because the 
postinst scripts do not specify the complete path to python3.5.

  [Test Case]
  1) Ensure the version of python3.5 from the release pocket is installed
  2) Install python3 using the instructions at 
https://passingcuriosity.com/2015/installing-python-from-source/
  3) Confirm that python3.5 from /usr/local/bin/ is being used / the default
  4) Upgrade to a newer version of python3.5 from -proposed

  Observe the following Traceback:

  Setting up python3.5-minimal (3.5.3-1) ...
  Traceback (most recent call last):
File "/usr/lib/python3.5/py_compile.py", line 6, in 
  import importlib._bootstrap_external
File "/usr/lib/python3.5/importlib/__init__.py", line 57, in 
  import types
File "/usr/lib/python3.5/types.py", line 166, in 
  import functools as _functools
File "/usr/lib/python3.5/functools.py", line 23, in 
  from weakref import WeakKeyDictionary
File "/usr/lib/python3.5/weakref.py", line 12, in 
  from _weakref import (
  ImportError: cannot import name '_remove_dead_weakref'
  dpkg: error processing package python3.5-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of python3-minimal:
   python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
Package python3.5-minimal is not configured yet.

  dpkg: error processing package python3-minimal (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

Errors were encountered while processing:
   python3.5-minimal
   python3-minimal

  With the version of python3.5 from -proposed this Traceback will not
  be encountered.

  [Regression Potential]
  It's possible I missed a postinst script so other python3.5 binary packages 
should be installed to ensure they are all fixed e.g. python3.5-dbg.

  [Original Description]
  Got this error while using "Transmageddon Video Transcoder" and again while 
updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: 

[Touch-packages] [Bug 1581425] Re: gdebi details window don't show packages

[cement_head]

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

How do you modify the glade file?

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

Title:
  gdebi details window don't show packages

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I'm using gdebi (gtk GUI)
  and when i install some package and show the 'detail' window, i don't see any 
packages, may by some widget doesn't expand properly.

  System: Ubuntu Gnome 16.04 64bits

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

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

[Touch-packages] [Bug 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects

[Dimitri John Ledkov]

Could you paste the output from
$ systemd-resolved --status
when the system is in a bad state? That is, system mentions the domains in 
/etc/resolv.conf when it should not have.

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

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

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

Title:
  extra domains not removed from resolv.conf when VPN disconnects

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN (network manager "vpnc" config) to connect to my work
  network.  The gateway is "webvpn.purestorage.com".  When I connect, I
  get "purestorage.com" added to the "search" line in my
  /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) -
  which makes perfect sense, the VPN passes this info to me and then I
  can connect to systems within the work network without having to use a
  FQDN.

  The bug (which is a regression from older versions of Ubuntu) is that
  when I lose my connection to the VPN (either because I disconnect
  explicitly, or because the network goes down or I suspend my laptop),
  the "purestorage.com" domain is not removed from those "search" lines.
  And for some reason this prevents me from resolving
  webvpn.purestorage.com (which prevents me from reconnecting to the
  VPN).

  In particular, if I connect and disconnect my VPN, I get:

   $ systemd-resolve webvpn.purestorage.com
  webvpn.purestorage.com: resolve call failed: No appropriate name servers or 
networks for name found

  If I then edit /etc/resolv.conf by hand to remove all the
  purestorage.com entries from the search line - in other words, change

   $ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  search home.digitalvampire.org purestorage.com dev.purestorage.com

  to

   $ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  search home.digitalvampire.org

  and change nothing else, then:

   $ systemd-resolve webvpn.purestorage.com
  webvpn.purestorage.com: 192.30.189.1
  (vpn.purestorage.com)

  -- Information acquired via protocol DNS in 25.9ms.
  -- Data is authenticated: no

  
  I'm not sure if the bug is in systemd, network manager, or some other 
package, but I'm happy to try any debugging that is helpful to resolve this (no 
pun intended).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu10
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 11:20:17 2017
  InstallationDate: Installed on 2016-09-01 (381 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901)
  MachineType: LENOVO 20FRS2FK00
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic 
root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-07-26 (53 days ago)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET53W (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2FK00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FRS2FK00
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1700218] Re: Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

[Juraj]

I disagree that a monospace context menu is expected - this is not the
case anywhere in the rest of the OS, it shouldn't matter that the text
editing font is monospaced. But sure, that can be moved to a separate
issue.

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

Title:
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  As found by
  https://github.com/gtimelog/gtimelog/issues/81#issuecomment-170923964,
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace. It
  causes issues on some apps. Gitg is affected as well.

  My temporary workaround: https://quan.hoabinh.vn/blog/2017/6/46-fix-
  gitg-doesn-t-use-monospace-font-in-ubuntu

  Please fix it.

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

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

[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Mathieu Trudel-Lapierre]

Indeed, it looks like systemd is handling this properly by itself. I'll
do some more testing but it looks like removing that is probably the
best thing to do. At least font/keymaps are set properly.

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

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

Status in Snappy:
  New
Status in console-setup package in Ubuntu:
  Triaged
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  = Test Cases =

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

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

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

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

  = Original Description =

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

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

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

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

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

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

[Touch-packages] [Bug 1709823] Re: Installation of libgles1-mesa (12.0.6-0ubuntu0.16.04.1) failed

[Dimitri John Ledkov]

Attempted to install libgles1-mesa and it failed.

Enabled proposed and it passed.

Verification done:

# apt install libgles1-mesa
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgles1-mesa : Depends: libglapi-mesa (= 12.0.6-0ubuntu0.16.04.1) but it is 
not going to be installed
E: Unable to correct problems, you have held broken packages.

# sudo nano /etc/apt/sources.list
# sudo apt update
...
# apt install libgles1-mesa
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
The following NEW packages will be installed:
  libgles1-mesa
0 upgraded, 1 newly installed, 0 to remove and 30 not upgraded.
Need to get 3310 B of archives.
After this operation, 14.3 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 libgles1-mesa 
all 17.0.7-0ubuntu0.16.04.2 [3310 B]
Fetched 3310 B in 0s (4140 B/s) 
YSelecting previously unselected package libgles1-mesa.
(Reading database ... 25532 files and directories currently installed.)
Preparing to unpack .../libgles1-mesa_17.0.7-0ubuntu0.16.04.2_all.deb ...
Unpacking libgles1-mesa (17.0.7-0ubuntu0.16.04.2) ...
Setting up libgles1-mesa (17.0.7-0ubuntu0.16.04.2) ...


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

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

Title:
  Installation of libgles1-mesa (12.0.6-0ubuntu0.16.04.1) failed

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  Installation of libgles1-mesa (12.0.6-0ubuntu0.16.04.1) on Ubuntu 16.04 LTS 
failed - it needs the package libglapi-mesa (12.0.6-0buntu0.16.04.1), which 
does not exist. The current version of libglapi-mesa is 17.0.7-0ubuntu0.16.04.1 
(xenial-updates), which does not support the installation of libgles1-mesa.

  [Test case]
  Try to install the package from 
  
https://01.org/linuxgraphics/downloads/intel-graphics-update-tool-linux-os-v2.0.2

  [Regression potential]
  none, it just adds a dummy package to fix broken/unnecessary dependencies in 
3rd party packages

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

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

[Touch-packages] [Bug 1717997] [NEW] cannot log off new user in test case

[ventrical]

Public bug reported:

during post install test case .. cannot log off new user .. but all else
works just fine

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: lightdm 1.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Sep 18 14:35:50 2017
InstallationDate: Installed on 2017-09-18 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918.1)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lightdm (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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1717997

Title:
  cannot log off new user in test case

Status in lightdm package in Ubuntu:
  New

Bug description:
  during post install test case .. cannot log off new user .. but all
  else works just fine

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lightdm 1.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Sep 18 14:35:50 2017
  InstallationDate: Installed on 2017-09-18 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

[Balint Reczey]

@Ethan: Thanks for the test and the logs.

Those show that the fix works but the move to minimal steps slowed down u-u a 
lot. I tried fixing the slowdown by finishing the concept of pre-calculating 
the steps then performing them but IMO this direction is not safe and can 
potentially leave packages not-upgraded due to inter-dependencies between 
pre-calculated upgrade steps:
https://github.com/mvo5/unattended-upgrades/tree/feature/minimal-upgrades-speedup2

I'm now profiling u-u instead to find where the slowdown is coming from
and try fixing that instead of pre-calculating the steps.

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

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged
Status in unattended-upgrades source package in Xenial:
  New
Status in apt source package in Zesty:
  Triaged
Status in unattended-upgrades source package in Zesty:
  New

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions

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

[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

[Balint Reczey]

It is also worth noting that users should rarely meet such slow upgrade
as the number of packages to upgrade with each run is usually much
lower.

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

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged
Status in unattended-upgrades source package in Xenial:
  New
Status in apt source package in Zesty:
  Triaged
Status in unattended-upgrades source package in Zesty:
  New

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions

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

[Touch-packages] [Bug 1717977] Re: package libgdk-pixbuf2.0-common 2.32.2-1ubuntu1.3 failed to install/upgrade: пакет libgdk-pixbuf2.0-common уже установлен и настроен

[Leonidas S. Barbosa]

** Information type changed from Private Security to Public

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

Title:
  package libgdk-pixbuf2.0-common 2.32.2-1ubuntu1.3 failed to
  install/upgrade: пакет libgdk-pixbuf2.0-common уже установлен и
  настроен

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
   I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgdk-pixbuf2.0-common 2.32.2-1ubuntu1.3
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Sep 18 19:53:25 2017
  Dependencies:
   
  ErrorMessage: пакет libgdk-pixbuf2.0-common уже установлен и настроен
  InstallationDate: Installed on 2017-09-07 (10 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf2.0-common 2.32.2-1ubuntu1.3 failed to 
install/upgrade: пакет libgdk-pixbuf2.0-common уже установлен и настроен
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1717995] [NEW] extra domains not removed from resolv.conf when VPN disconnects

[Roland Dreier]

Public bug reported:

I use a VPN (network manager "vpnc" config) to connect to my work
network.  The gateway is "webvpn.purestorage.com".  When I connect, I
get "purestorage.com" added to the "search" line in my /etc/resolv.conf
(and /run/resolvconf/interface/systemd-resolved) - which makes perfect
sense, the VPN passes this info to me and then I can connect to systems
within the work network without having to use a FQDN.

The bug (which is a regression from older versions of Ubuntu) is that
when I lose my connection to the VPN (either because I disconnect
explicitly, or because the network goes down or I suspend my laptop),
the "purestorage.com" domain is not removed from those "search" lines.
And for some reason this prevents me from resolving
webvpn.purestorage.com (which prevents me from reconnecting to the VPN).

In particular, if I connect and disconnect my VPN, I get:

 $ systemd-resolve webvpn.purestorage.com
webvpn.purestorage.com: resolve call failed: No appropriate name servers or 
networks for name found

If I then edit /etc/resolv.conf by hand to remove all the
purestorage.com entries from the search line - in other words, change

 $ cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53
search home.digitalvampire.org purestorage.com dev.purestorage.com

to

 $ cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53
search home.digitalvampire.org

and change nothing else, then:

 $ systemd-resolve webvpn.purestorage.com
webvpn.purestorage.com: 192.30.189.1
(vpn.purestorage.com)

-- Information acquired via protocol DNS in 25.9ms.
-- Data is authenticated: no


I'm not sure if the bug is in systemd, network manager, or some other package, 
but I'm happy to try any debugging that is helpful to resolve this (no pun 
intended).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu10
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Sep 18 11:20:17 2017
InstallationDate: Installed on 2016-09-01 (381 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901)
MachineType: LENOVO 20FRS2FK00
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic 
root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to artful on 2017-07-26 (53 days ago)
dmi.bios.date: 07/13/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET53W (1.27 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FRS2FK00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
dmi.product.family: ThinkPad X1 Yoga 1st
dmi.product.name: 20FRS2FK00
dmi.product.version: ThinkPad X1 Yoga 1st
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  extra domains not removed from resolv.conf when VPN disconnects

Status in systemd package in Ubuntu:
  New

Bug description:
  I use a VPN (network manager "vpnc" config) to connect to my work
  network.  The gateway is "webvpn.purestorage.com".  When I connect, I
  get "purestorage.com" added to the "search" line in my
  /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) -
  which makes perfect sense, the VPN passes this info to me and then I
  can connect to systems within the work network without having to use a
  FQDN.

  The bug (which is a regression from older versions of Ubuntu) is that
  when I lose my connection to the VPN (either because I disconnect
  explicitly, or because the network goes down or I suspend my laptop),
  the "purestorage.com" domain is not removed from those "search" lines.
  And for some reason this prevents me from resolving
  webvpn.purestorage.com (which prevents me from reconnecting to the
  

[Touch-packages] [Bug 1696735] Re: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[Andreas Hasenack]

You should go to a terminal and run these commands:

sudo apt update
sudo apt -f install

Then we can see which package is causing problems.

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

Title:
  package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in krb5 package in Ubuntu:
  Expired

Bug description:
  unknown

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  8 08:22:46 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-02-12 (481 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-05-22 (381 days ago)

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

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

[Touch-packages] [Bug 1717992] [NEW] Sound silently plays to "Dummy Output"

[Carlos Eduardo Moreira dos Santos]

Public bug reported:

Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
detected, but pavucontrol has only "Dummy Output". Bar animation shows
audio is playing, but no sound is heard. alsamixer is working fine, but
audio still can't be heard. Configuration tab says "No cards available
for configuration".

$ lspci -v
0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

# aplay -L
default
Playback/recording through the PulseAudio sound server
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
sysdefault:CARD=PCH
HDA Intel PCH, ALC3246 Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
Front speakers
surround21:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
hdmi:CARD=PCH,DEV=0
HDA Intel PCH, HDMI 0
HDMI Audio Output
hdmi:CARD=PCH,DEV=1
HDA Intel PCH, HDMI 1
HDMI Audio Output
hdmi:CARD=PCH,DEV=2
HDA Intel PCH, HDMI 2
HDMI Audio Output
dmix:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
Direct sample mixing device
dmix:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct sample mixing device
dmix:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct sample mixing device
dmix:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct sample mixing device
dsnoop:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
Direct sample snooping device
dsnoop:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct sample snooping device
dsnoop:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct sample snooping device
dsnoop:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct sample snooping device
hw:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
Direct hardware device without any conversions
hw:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct hardware device without any conversions
hw:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct hardware device without any conversions
hw:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct hardware device without any conversions
plughw:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
Hardware device with all software conversions
plughw:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Hardware device with all software conversions
plughw:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Hardware device with all software conversions
plughw:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Hardware device with all software conversions

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

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

Title:
  Sound silently plays to "Dummy Output"

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
  detected, but pavucontrol has only "Dummy Output". Bar animation shows
  audio is playing, but no sound is heard. alsamixer is working fine,
  but audio still can't be heard. Configuration tab says "No cards
  available for configuration".

  $ lspci -v
  0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  # aplay -L
  default
  Playback/recording through the PulseAudio sound server
  null
  Discard all samples (playback) or generate zero samples (capture)
  pulse
  PulseAudio Sound Server
  sysdefault:CARD=PCH
  HDA Intel PCH, ALC3246 Analog
  Default Audio Device
  front:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Front speakers
  surround21:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 

[Touch-packages] [Bug 1717991] [NEW] file returns "name use count (30) exceeded"

[Suzanka]

Public bug reported:

In Ubuntu 17.04 there seems to be a problem with "file":

$ file test.jpg 
test.jpg: ERROR: JPEG image data, JFIF standard 1.01, resolution (DPI), density 
240x240, segment length 16, Exif Standard: [TIFF image data, big-endian, 
direntries=8, description=Picture saved with settings embedded., 
orientation=upper-left, xresolution=148, yresolution=156, resolutionunit=2, 
software=Adobe Photoshop Lightroom 6.1.1 (Windows), datetime=2017:08:17 
11:16:47] name use count (30) exceeded

This problem was reported in Fedora a couple of years ago:
https://bugzilla.redhat.com/show_bug.cgi?id=1201630

I found out about the problem when the Astrometry program suddenly
stopped working on jpegs that it was previously able to process. I
cannot say how "file" is supposed to normally output the data. I only
found out about this when the program suddenly broke without any obvious
reason after the upgrade from Ubuntu 16.04 to 17.04. Since there is
another case reported for Fedora I tend to believe that the problem is
indeed caused by "file".

The required data:

$ lsb_release -rd
Description:Ubuntu 17.04
Release:17.04


$ apt-cache policy file
file:
  Installed: 1:5.29-3ubuntu0.1
  Candidate: 1:5.29-3ubuntu0.1
  Version table:
 *** 1:5.29-3ubuntu0.1 500
500 http://fi.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 Packages
100 /var/lib/dpkg/status
 1:5.29-3 500
500 http://fi.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: file 1:5.29-3ubuntu0.1
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
NonfreeKernelModules: sep4_0 socperf2_0 pax
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Mon Sep 18 20:36:35 2017
InstallationDate: Installed on 2016-01-18 (609 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: file
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug file jpeg jpg zesty

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

Title:
  file returns "name use count (30) exceeded"

Status in file package in Ubuntu:
  New

Bug description:
  In Ubuntu 17.04 there seems to be a problem with "file":

  $ file test.jpg 
  test.jpg: ERROR: JPEG image data, JFIF standard 1.01, resolution (DPI), 
density 240x240, segment length 16, Exif Standard: [TIFF image data, 
big-endian, direntries=8, description=Picture saved with settings embedded., 
orientation=upper-left, xresolution=148, yresolution=156, resolutionunit=2, 
software=Adobe Photoshop Lightroom 6.1.1 (Windows), datetime=2017:08:17 
11:16:47] name use count (30) exceeded

  This problem was reported in Fedora a couple of years ago:
  https://bugzilla.redhat.com/show_bug.cgi?id=1201630

  I found out about the problem when the Astrometry program suddenly
  stopped working on jpegs that it was previously able to process. I
  cannot say how "file" is supposed to normally output the data. I only
  found out about this when the program suddenly broke without any
  obvious reason after the upgrade from Ubuntu 16.04 to 17.04. Since
  there is another case reported for Fedora I tend to believe that the
  problem is indeed caused by "file".

  The required data:

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  
  $ apt-cache policy file
  file:
Installed: 1:5.29-3ubuntu0.1
Candidate: 1:5.29-3ubuntu0.1
Version table:
   *** 1:5.29-3ubuntu0.1 500
  500 http://fi.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.29-3 500
  500 http://fi.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: file 1:5.29-3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: sep4_0 socperf2_0 pax
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Sep 18 20:36:35 2017
  InstallationDate: Installed on 2016-01-18 (609 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: file
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1717991] Re: file returns "name use count (30) exceeded"

[Suzanka]

The file test.jpg that I used is attached. The problem occurs with other
jpeg images, too.

** Attachment added: "test.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/file/+bug/1717991/+attachment/4952354/+files/test.jpg

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

Title:
  file returns "name use count (30) exceeded"

Status in file package in Ubuntu:
  New

Bug description:
  In Ubuntu 17.04 there seems to be a problem with "file":

  $ file test.jpg 
  test.jpg: ERROR: JPEG image data, JFIF standard 1.01, resolution (DPI), 
density 240x240, segment length 16, Exif Standard: [TIFF image data, 
big-endian, direntries=8, description=Picture saved with settings embedded., 
orientation=upper-left, xresolution=148, yresolution=156, resolutionunit=2, 
software=Adobe Photoshop Lightroom 6.1.1 (Windows), datetime=2017:08:17 
11:16:47] name use count (30) exceeded

  This problem was reported in Fedora a couple of years ago:
  https://bugzilla.redhat.com/show_bug.cgi?id=1201630

  I found out about the problem when the Astrometry program suddenly
  stopped working on jpegs that it was previously able to process. I
  cannot say how "file" is supposed to normally output the data. I only
  found out about this when the program suddenly broke without any
  obvious reason after the upgrade from Ubuntu 16.04 to 17.04. Since
  there is another case reported for Fedora I tend to believe that the
  problem is indeed caused by "file".

  The required data:

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  
  $ apt-cache policy file
  file:
Installed: 1:5.29-3ubuntu0.1
Candidate: 1:5.29-3ubuntu0.1
Version table:
   *** 1:5.29-3ubuntu0.1 500
  500 http://fi.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.29-3 500
  500 http://fi.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: file 1:5.29-3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: sep4_0 socperf2_0 pax
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Sep 18 20:36:35 2017
  InstallationDate: Installed on 2016-01-18 (609 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: file
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

[Scott Moser]

** Description changed:

  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)
  
  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".
  
  The list of Depends/Suggests/Recommends on resolvconf.
  
  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation
  
  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
-  * bug 1714308: dns does not work in initramfs after configure_networking
+  * bug 1714308: dns does not work in initramfs after configure_networking
+  * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in cloud-initramfs-tools package in Ubuntu:
  New
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  New
Status in dnscrypt-proxy package in Ubuntu:
  New
Status in dnsmasq package in Ubuntu:
  New
Status in dnssec-trigger package in Ubuntu:
  New
Status in fetchmail package in Ubuntu:
  New
Status in freedombox-setup package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  New
Status in ndisc6 package in Ubuntu:
  New
Status in netscript-2.4 package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  New
Status in pump package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  New
Status in vpnc-scripts package in Ubuntu:
  New
Status in whereami package in Ubuntu:
  New

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; 

[Touch-packages] [Bug 1717983] [NEW] replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration

[Scott Moser]

Public bug reported:

dhclient has been used as the dhcp client in Ubuntu and debian for
many years. Over time, many packages have integrated with dhclient.
The list below is of packages that have declared a dependency and
those that have shipped hooks to be invoked by dhclient.

As we move to systemd-networkd these will have to be addressed.

# ./get-rdeps isc-dhcp-client | sort -u
breaks - initramfs-tools (initramfs-tools)
depends - dracut (dracut-network)
depends - isc-dhcp (isc-dhcp-client-ddns)
depends - libguestfs (libguestfs0)
depends - maas (python3-maas-provisioningserver)
depends - netscript-2.4 (netscript-2.4)
depends - network-manager (network-manager)
depends - ubuntu-meta (ubuntu-minimal)
depends - walinuxagent (walinuxagent)
depends - whereami (whereami)
depends - wicd (wicd-daemon)
depends - wifi-radar (wifi-radar)
enhances - resolvconf (resolvconf)
recommends - avahi (avahi-autoipd)
recommends - ifupdown (ifupdown)
recommends - ifupdown2 (ifupdown2)
recommends - madwimax (madwimax)

$ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u
avahi-autoipd
cloud-init
controlaula
ddclient
isc-dhcp-client
ntp
ntpdate
openresolv
resolvconf
samba-common
sendmail-base
systemd
whereami

Another possible integration point that is not likely listed in the package
dependencies is reading of the leases file for additional information.
As an example, Azure advertises the location of its http based metadata
service as an option in a dhclient response.  cloud-init will read the
lease files to find the correct address.

Related bugs:
 * bug 1713803: replacement of resolvconf with systemd needs integration 


ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: isc-dhcp-client 4.3.5-3ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Sep 18 12:46:31 2017
DhclientLeases:

EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (788 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: isc-dhcp
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

** Affects: netscript-2.4 (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

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

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

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

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

** Affects: wifi-radar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apparmor apport-bug artful

** Attachment added: "get-rdeps: script to dump reverse dependencies from 
apt-cache data"
   https://bugs.launchpad.net/bugs/1717983/+attachment/4952319/+files/get-rdeps

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

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

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

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

** Also affects: netscript-2.4 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also 

[Touch-packages] [Bug 1544942] Re: Marks unneeded packages as manually installed, if --dry-run is used

[Brian Murray]

** Tags added: full-boot

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

Title:
  Marks unneeded packages as manually installed, if --dry-run is used

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  
  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded:
  marking linux-headers-4.2.0-16-generic for remove
  marking linux-headers-4.2.0-16 for remove
  marking linux-image-4.2.0-16-generic for remove
  marking linux-image-extra-4.2.0-16-generic for remove
  Packages that are auto removed: 'linux-headers-4.2.0-16-generic 
linux-headers-4.2.0-16 linux-image-4.2.0-16-generic 
linux-image-extra-4.2.0-16-generic'
  /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove 
linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all 
linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64
  /usr/bin/dpkg --status-fd 11 --configure --pending
  Packages were successfully auto-removed
  InstCount=0 DelCount=4 BrokenCount=0

  $ apt-mark showauto linux-headers-4.2.0-16-generic:amd64 linux-
  headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux-
  image-4.2.0-16-generic:amd64

  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  No packages found that can be upgraded unattended and no pending auto-removals

  Expect the packages to remain automatically installed after each `sudo
  unattended-upgrade --dry-run -d`.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unattended-upgrades 0.86.2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Feb 12 13:58:29 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-24 (18 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2016-02-12T13:53:13.426454

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

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

[Touch-packages] [Bug 1717984] [NEW] [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] Pulseaudio fails to detect card

[Danny Howard]

Public bug reported:

I can not get audio out. I try the headphone jack, the headphone jack on
my HDMI display, internal speakers, no nothing zip nada.

In Miltimedia > PulseAudio Volume Control > Output Devices, there are no
audio devices. If I Show All Output Devices then a device called
"silence" is listed. I can turn up the volume on that and see the level
jumping around but nothing in my ears. The Configuration tab says no
cards available.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: XFCE
Date: Mon Sep 18 10:27:49 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-10-14 (339 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Title: [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] Pulseaudio 
fails to detect card
UpgradeStatus: Upgraded to xenial on 2016-10-14 (339 days ago)
dmi.bios.date: 08/08/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.13
dmi.board.name: 0N8J4R
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.13:bd08/08/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision 5510
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  [Precision 5510, Realtek ALC3266, Black Headphone Out, Left]
  Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I can not get audio out. I try the headphone jack, the headphone jack
  on my HDMI display, internal speakers, no nothing zip nada.

  In Miltimedia > PulseAudio Volume Control > Output Devices, there are
  no audio devices. If I Show All Output Devices then a device called
  "silence" is listed. I can turn up the volume on that and see the
  level jumping around but nothing in my ears. The Configuration tab
  says no cards available.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Mon Sep 18 10:27:49 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-14 (339 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Title: [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] 
Pulseaudio fails to detect card
  UpgradeStatus: Upgraded to xenial on 2016-10-14 (339 days ago)
  dmi.bios.date: 08/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.13
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.13:bd08/08/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1717241] Re: nautilus crashed with signal 5 in _XReply() - drag and drop crash

[Rodrigo Alconchel]

** No longer affects: apport (Ubuntu)

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

Title:
  nautilus crashed with signal 5 in _XReply() - drag and drop crash

Status in nautilus package in Ubuntu:
  New

Bug description:
  To reproduce on a fully updated Ubuntu Desktop 16.04 system with
  Unity:

  Step 1: Start nautilus

  Step 2: Drag and drop a file to any target: to a different folder in
  the same nautilus window, to another folder in a different nautilus
  window, etc. ... The target is irrelevant.

  Expected to happen: File successfully copied or moved.

  Actually happened: Mouse pointer changes to a hand with a plus sign.
  Source file moves only slightly and then freezes, never makes it to
  the target. Application locks up for a few seconds, and then the
  application window vanishes. Crash report is then generated.

  Ubuntu release: Ubuntu 16.04.3 LTS

  Nautilus package version: Installed: 1:3.18.4.is.3.14.3-0ubuntu6

  Additional (and maybe relevant) notes:

  1) Drag and drop function seems broken generally, across applications,
  not just in nautilus. For instance, same behavior appears when trying
  to drag and drop a Thunderbird message to another Thunderbird folder,
  or when trying to drag and drop a cell or a range of cells within the
  same Libreoffice Calc spreadsheet.

  2) Interestingly, application windows can be dragged and dropped
  across display monitors (3 monitor setup), without any problems.

  3) I am using proprietary NVIDIA drivers, but please do not suggest
  using nouveau drivers, because they work horribly (heavy display
  corruption, pixelated screen, and constant mouse flickering)

  4) Graphics setup: NVIDIA Quadro NVS 450 card with twin GPU and 4
  heads. NVIDIA propietary driver version 340.102 (installed from ubuntu
  repositories, not from proprietary NVIDIA installer; correct driver
  for this card according to NVIDIA documentation). 3 monitors connected
  in a simple horizontal layout.

  5) Nautilus extension installed: nautilus-share  0.7.3-2ubuntu1

  6) Attaching a nautilus debugging log from terminal command:
  G_DEBUG="all" NAUTILUS_DEBUG ="All" nautilus

  7) Attaching X Org log file with -logverbose 6 option

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports: 640:1000:116:10641522:2017-09-14 12:49:07.088649823 
+0200:2017-09-14 12:27:03.381461842 
+0200:/var/crash/_usr_bin_nautilus.1000.crash
  CurrentDesktop: Unity
  Date: Thu Sep 14 11:02:40 2017
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1481715745
  PackageArchitecture: all
  ProcCmdline: nautilus
  ProcCwd: /var/crash
  Signal: 5
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XShapeGetRectangles () from /usr/lib/x86_64-linux-gnu/libXext.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2017-09-14T09:20:26.397971

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

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

[Touch-packages] [Bug 1208508] Re: unable to update an bug with an existing .crash file

[Manoj Iyer]

This would be a very useful feature for cases where bugs are mirrored
from a bug tracking tool like bugzilla to launchpad, usually servers are
behind firewalls, so .apport could be collected offline and later (the
mirrored lp bug could be) updated with .apport information.

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

Title:
  unable to update an bug with an existing .crash file

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  New

Bug description:
  I may be misunderstanding the man pages, but I was assuming that if I
  ran the following...

  $ sudo apport-cli --save /tmp/linux.crash linux

  ... then copied linux.crash to a local system, I would be able to
  append the meta-data in linux.crash to an *existing* bug report like
  this:

  $ apport-cli  --update-report $bug --crash-file linux.report

  However, that doesn't work:

  Usage: apport-cli [options] [symptom|pid|package|program
  path|.apport/.crash file]

  apport-cli: error: -u/--update-bug option cannot be used together
  with options for a new report

  This looks like a bug since I've specified '--update-report', hence
  this is not a new report.

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

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

[Touch-packages] [Bug 1208508] Re: unable to update an bug with an existing .crash file

[Brian Murray]

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

** Tags added: rls-bb-incoming

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

Title:
  unable to update an bug with an existing .crash file

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  New

Bug description:
  I may be misunderstanding the man pages, but I was assuming that if I
  ran the following...

  $ sudo apport-cli --save /tmp/linux.crash linux

  ... then copied linux.crash to a local system, I would be able to
  append the meta-data in linux.crash to an *existing* bug report like
  this:

  $ apport-cli  --update-report $bug --crash-file linux.report

  However, that doesn't work:

  Usage: apport-cli [options] [symptom|pid|package|program
  path|.apport/.crash file]

  apport-cli: error: -u/--update-bug option cannot be used together
  with options for a new report

  This looks like a bug since I've specified '--update-report', hence
  this is not a new report.

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

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

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Drew Freiberger]

Trusty versions of packages affected (I see there is a systemd update
229-4ubuntu19.  Does this include the backported fixes from v230/v231
mentioned in comment #4?):

ii  dbus 1.10.6-1ubuntu3.1  
amd64simple interprocess messaging system (daemon and utilities)
ii  libdbus-1-3:amd641.10.6-1ubuntu3.1  
amd64simple interprocess messaging system (library)
ii  libdbus-glib-1-2:amd64   0.106-1
amd64simple interprocess messaging system (GLib-based shared library)
ii  python3-dbus 1.2.0-3
amd64simple interprocess messaging system (Python 3 interface)
ii  libpam-systemd:amd64 229-4ubuntu12  
amd64system and service manager - PAM module
ii  libsystemd0:amd64229-4ubuntu12  
amd64systemd utility library
ii  python3-systemd  231-2build1
amd64Python 3 bindings for systemd
ii  systemd  229-4ubuntu12  
amd64system and service manager
ii  systemd-sysv 229-4ubuntu12  
amd64system and service manager - SysV links

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Fix Released
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Won't Fix
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  The bug affects multiple users and introduces an user visible delay
  (~25 seconds) on SSH connections after a large number of sessions have
  been processed. This has a serious impact on big systems and servers
  running our software.

  The currently proposed fix is actually a safe workaround for the bug
  as proposed by the dbus upstream. The workaround makes uid 0 immune to
  the pending_fd_timeout limit that kicks in and causes the original
  issue.

  [Test Case]

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  Then checking the log file if there are any ssh sessions that are
  taking 25+ seconds to complete.

  Multiple instances of the same script can be used at the same time.

  [Regression Potential]

  The fix has a rather low regression potential as the workaround is a
  very small change only affecting one particular case - handling of uid
  0. The fix has been tested by multiple users and has been around in
  zesty for a while, with multiple people involved in reviewing the
  change. It's also a change that has been proposed by upstream.

  [Original Description]

  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dan Streetman]

Also, this upstream udev bug has caused trouble before, e.g.:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1549456

that does a udev reload too, but only when specific devices are found.
Hopefully this change to update-dev will cover more cases where this
upstream udev bug will cause failures, but since it's a racy 0-3 second
window of stale data that udev uses, and they refuse to fix it upstream,
it will be really hard to test for and/or reproduce.

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Fix Released
Status in debian-installer package in Ubuntu:
  New
Status in debian-installer-utils package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix
Status in debian-installer source package in Trusty:
  New
Status in debian-installer source package in Xenial:
  New
Status in debian-installer source package in Zesty:
  New
Status in debian-installer source package in Artful:
  New

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Drew Freiberger]

** Tags added: canonical-bootstack canonical-is

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Fix Released
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Won't Fix
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  The bug affects multiple users and introduces an user visible delay
  (~25 seconds) on SSH connections after a large number of sessions have
  been processed. This has a serious impact on big systems and servers
  running our software.

  The currently proposed fix is actually a safe workaround for the bug
  as proposed by the dbus upstream. The workaround makes uid 0 immune to
  the pending_fd_timeout limit that kicks in and causes the original
  issue.

  [Test Case]

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  Then checking the log file if there are any ssh sessions that are
  taking 25+ seconds to complete.

  Multiple instances of the same script can be used at the same time.

  [Regression Potential]

  The fix has a rather low regression potential as the workaround is a
  very small change only affecting one particular case - handling of uid
  0. The fix has been tested by multiple users and has been around in
  zesty for a while, with multiple people involved in reviewing the
  change. It's also a change that has been proposed by upstream.

  [Original Description]

  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Oliver Grawert]

might be that we need it on Ubuntu Core (and server) though ... so
installing the rule at all should probably be conditional ...

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

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

Status in Snappy:
  New
Status in console-setup package in Ubuntu:
  Triaged
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  = Test Cases =

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

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

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

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

  = Original Description =

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

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

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

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

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

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

[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Iain Lane]

Not sure why you would if systemd is setting the mode up correctly on
its own?

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

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

Status in Snappy:
  New
Status in console-setup package in Ubuntu:
  Triaged
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  = Test Cases =

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

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

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

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

  = Original Description =

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

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

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

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

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

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

[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Iain Lane]

^- forgot to say, that was with those udev rules commented out - you
could equally (upstreamable - this bug should apply to Debian too) do
something like

if [ -d /run/systemd/system ]; then
  exit 0
fi

at the top of console-setup-tty

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

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

Status in Snappy:
  New
Status in console-setup package in Ubuntu:
  Triaged
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  = Test Cases =

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

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

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

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

  = Original Description =

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

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

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

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

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

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

[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Iain Lane]

...or stop using this rule completely? I think systemd does thing
properly these days - see:

laney@artful-vm-gdm:~$ sudo ~/temp/a.out # displaying gdm
[sudo] password for laney: 
K_OFF
laney@artful-vm-gdm:~$ sudo ~/temp/a.out # switch to vt3, login: prompt
K_UNICODE

...which looks set up correctly to me.

@Janne - I don't know why this would be specific to Wayland. I think
it'd happen if you were running your graphical environment on
/dev/tty[1-6] regardless of the Xness or Waylandness of 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/1710637

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

Status in Snappy:
  New
Status in console-setup package in Ubuntu:
  Triaged
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  = Test Cases =

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

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

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

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

  = Original Description =

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

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

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

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

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

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

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Drew Freiberger]

Can we get this backported to trusty?

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Fix Released
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Won't Fix
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  The bug affects multiple users and introduces an user visible delay
  (~25 seconds) on SSH connections after a large number of sessions have
  been processed. This has a serious impact on big systems and servers
  running our software.

  The currently proposed fix is actually a safe workaround for the bug
  as proposed by the dbus upstream. The workaround makes uid 0 immune to
  the pending_fd_timeout limit that kicks in and causes the original
  issue.

  [Test Case]

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  Then checking the log file if there are any ssh sessions that are
  taking 25+ seconds to complete.

  Multiple instances of the same script can be used at the same time.

  [Regression Potential]

  The fix has a rather low regression potential as the workaround is a
  very small change only affecting one particular case - handling of uid
  0. The fix has been tested by multiple users and has been around in
  zesty for a while, with multiple people involved in reviewing the
  change. It's also a change that has been proposed by upstream.

  [Original Description]

  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Janne Snabb]

I have this problem on Ubuntu Gnome 17.04 running in virtualbox. I
believe it is not using Wayland.

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

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

Status in Snappy:
  New
Status in console-setup package in Ubuntu:
  Triaged
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  = Test Cases =

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

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

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

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

  = Original Description =

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

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

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

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

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

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

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dan Streetman]

> Here is a sample patch against debian-installer-utils to try.

yes i think it at least needs to go here, to handle this very specific
case.  It may be better to put it into the if $TRIGGER section, as I
don't think it is needed for only the settle case, but either way should
work.

This was reported to me, so I'll ask the reporter to test with this
change to verify it fixes for them; I have not been able to reproduce it
myself.

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Fix Released
Status in debian-installer package in Ubuntu:
  New
Status in debian-installer-utils package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix
Status in debian-installer source package in Trusty:
  New
Status in debian-installer source package in Xenial:
  New
Status in debian-installer source package in Zesty:
  New
Status in debian-installer source package in Artful:
  New

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Iain Lane]

Indeed changing it to [3-7] fixes it. Or should that be [3-6]?
cyphermox?

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

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

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

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

** Changed in: console-setup (Ubuntu)
   Status: Fix Released => Triaged

** Changed in: console-setup (Ubuntu)
   Importance: Undecided => High

** Changed in: console-setup (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1710637

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

Status in Snappy:
  New
Status in console-setup package in Ubuntu:
  Triaged
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  = Test Cases =

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

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

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

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

  = Original Description =

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

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

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

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

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

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

[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Iain Lane]

/lib/udev/rules.d/85-keyboard-configuration.rules:SUBSYSTEM=="tty", 
KERNEL=="tty[1-6]", RUN+="console-setup-tty /dev/%k"
/lib/udev/rules.d/85-keyboard-configuration.rules:SUBSYSTEM=="graphics", 
KERNEL=="fbcon", RUN+="console-setup-tty fbcon"

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

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

Status in Snappy:
  New
Status in console-setup package in Ubuntu:
  Triaged
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  = Test Cases =

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

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

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

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

  = Original Description =

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

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

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

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

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

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

[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Iain Lane]

^- this thing is the thing that breaks 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/1710637

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

Status in Snappy:
  New
Status in console-setup package in Ubuntu:
  Triaged
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  = Test Cases =

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

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

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

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

  = Original Description =

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

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

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

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

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

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

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dan Streetman]

> Changed in systemd:
> status:   New → Fix Released

for clarification, this is not Fix Released upstream, it has been
rejected as Won't Fix upstream, systemd/udev believes it isn't their
problem.

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Fix Released
Status in debian-installer package in Ubuntu:
  New
Status in debian-installer-utils package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix
Status in debian-installer source package in Trusty:
  New
Status in debian-installer source package in Xenial:
  New
Status in debian-installer source package in Zesty:
  New
Status in debian-installer source package in Artful:
  New

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

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

[Łukasz Zemczak]

Hello Brian, or anyone else affected,

Accepted python3.5 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python3.5/3.5.2-2ubuntu0~16.04.3 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!

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

Title:
  python3 in /usr/local/bin can cause python3 packages to fail to
  install

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.5 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  New
Status in python3.5 source package in Xenial:
  Fix Committed
Status in python2.7 source package in Zesty:
  New
Status in python3.5 source package in Zesty:
  Fix Committed
Status in python3.5 package in Debian:
  Fix Released

Bug description:
  [Impact]
  An upgrade of python3.5 will fail if someone has installed a different 
version of python3.5 in their path e.g. in /usr/local/bin. This is because the 
postinst scripts do not specify the complete path to python3.5.

  [Test Case]
  1) Ensure the version of python3.5 from the release pocket is installed
  2) Install python3 using the instructions at 
https://passingcuriosity.com/2015/installing-python-from-source/
  3) Confirm that python3.5 from /usr/local/bin/ is being used / the default
  4) Upgrade to a newer version of python3.5 from -proposed

  Observe the following Traceback:

  Setting up python3.5-minimal (3.5.3-1) ...
  Traceback (most recent call last):
File "/usr/lib/python3.5/py_compile.py", line 6, in 
  import importlib._bootstrap_external
File "/usr/lib/python3.5/importlib/__init__.py", line 57, in 
  import types
File "/usr/lib/python3.5/types.py", line 166, in 
  import functools as _functools
File "/usr/lib/python3.5/functools.py", line 23, in 
  from weakref import WeakKeyDictionary
File "/usr/lib/python3.5/weakref.py", line 12, in 
  from _weakref import (
  ImportError: cannot import name '_remove_dead_weakref'
  dpkg: error processing package python3.5-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of python3-minimal:
   python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
Package python3.5-minimal is not configured yet.

  dpkg: error processing package python3-minimal (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

Errors were encountered while processing:
   python3.5-minimal
   python3-minimal

  With the version of python3.5 from -proposed this Traceback will not
  be encountered.

  [Regression Potential]
  It's possible I missed a postinst script so other python3.5 binary packages 
should be installed to ensure they are all fixed e.g. python3.5-dbg.

  [Original Description]
  Got this error while using "Transmageddon Video Transcoder" and again while 
updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install

[Łukasz Zemczak]

Hello Brian, or anyone else affected,

Accepted python3.5 into zesty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python3.5/3.5.3-1ubuntu0~17.04.1 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: python3.5 (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

** Changed in: python3.5 (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 python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1682934

Title:
  python3 in /usr/local/bin can cause python3 packages to fail to
  install

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.5 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  New
Status in python3.5 source package in Xenial:
  Fix Committed
Status in python2.7 source package in Zesty:
  New
Status in python3.5 source package in Zesty:
  Fix Committed
Status in python3.5 package in Debian:
  Fix Released

Bug description:
  [Impact]
  An upgrade of python3.5 will fail if someone has installed a different 
version of python3.5 in their path e.g. in /usr/local/bin. This is because the 
postinst scripts do not specify the complete path to python3.5.

  [Test Case]
  1) Ensure the version of python3.5 from the release pocket is installed
  2) Install python3 using the instructions at 
https://passingcuriosity.com/2015/installing-python-from-source/
  3) Confirm that python3.5 from /usr/local/bin/ is being used / the default
  4) Upgrade to a newer version of python3.5 from -proposed

  Observe the following Traceback:

  Setting up python3.5-minimal (3.5.3-1) ...
  Traceback (most recent call last):
File "/usr/lib/python3.5/py_compile.py", line 6, in 
  import importlib._bootstrap_external
File "/usr/lib/python3.5/importlib/__init__.py", line 57, in 
  import types
File "/usr/lib/python3.5/types.py", line 166, in 
  import functools as _functools
File "/usr/lib/python3.5/functools.py", line 23, in 
  from weakref import WeakKeyDictionary
File "/usr/lib/python3.5/weakref.py", line 12, in 
  from _weakref import (
  ImportError: cannot import name '_remove_dead_weakref'
  dpkg: error processing package python3.5-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of python3-minimal:
   python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
Package python3.5-minimal is not configured yet.

  dpkg: error processing package python3-minimal (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

Errors were encountered while processing:
   python3.5-minimal
   python3-minimal

  With the version of python3.5 from -proposed this Traceback will not
  be encountered.

  [Regression Potential]
  It's possible I missed a postinst script so other python3.5 binary packages 
should be installed to ensure they are all fixed e.g. python3.5-dbg.

  [Original Description]
  Got this error while using "Transmageddon Video Transcoder" and again while 
updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  

[Touch-packages] [Bug 1717946] Re: UIFe: Drop xterm and xdiagnose from default install

[Jeremy Bicha]

** Description changed:

  Impact
  ==
  I'm proposing to drop 3 apps from the default Ubuntu 17.10 install:
  XTerm
  UXTerm
  xdiagnose
  
  These are visible in the Show Applications view of the Activities
  Overview so this could impact screenshots.
  
  Justification
  =
  These were only in the default install because of the FailsafeX feature.
  Timo Aaltonen (tjaalton), maintainer of Ubuntu's X stack and co-maintainer in 
Debian, has said that feature isn't important any more, considering the 
transition to Wayland.
  
  xdiagnose also provided some apport hooks for diagnosing display
  problems but that was moved to xorg itself earlier this release cycle.
  
  xdiagnose currently doesn't run in the Ubuntu session on Wayland.
  
  https://irclogs.ubuntu.com/2017/09/18/%23ubuntu-desktop.html#t14:18
  
  Discussed earlier in the cycle:
  https://lists.ubuntu.com/archives/ubuntu-desktop/2017-June/004980.html
  https://lists.ubuntu.com/archives/ubuntu-desktop/2017-July/005059.html
  
  List Notifications
  ==
+ https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html
+ 
https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html

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

Title:
  UIFe: Drop xterm and xdiagnose from default install

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Impact
  ==
  I'm proposing to drop 3 apps from the default Ubuntu 17.10 install:
  XTerm
  UXTerm
  xdiagnose

  These are visible in the Show Applications view of the Activities
  Overview so this could impact screenshots.

  Justification
  =
  These were only in the default install because of the FailsafeX feature.
  Timo Aaltonen (tjaalton), maintainer of Ubuntu's X stack and co-maintainer in 
Debian, has said that feature isn't important any more, considering the 
transition to Wayland.

  xdiagnose also provided some apport hooks for diagnosing display
  problems but that was moved to xorg itself earlier this release cycle.

  xdiagnose currently doesn't run in the Ubuntu session on Wayland.

  https://irclogs.ubuntu.com/2017/09/18/%23ubuntu-desktop.html#t14:18

  Discussed earlier in the cycle:
  https://lists.ubuntu.com/archives/ubuntu-desktop/2017-June/004980.html
  https://lists.ubuntu.com/archives/ubuntu-desktop/2017-July/005059.html

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html
  
https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html

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

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

[Touch-packages] [Bug 1715278] Re: [FFe] LXC 2.1

[Andy Whitcroft]

On the presumption it is backwards compatible as claimed, this seems ok.
The new features all seem optional, and existing configs all are
supported.  +1.

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

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

Title:
  [FFe] LXC 2.1

Status in lxc package in Ubuntu:
  Triaged

Bug description:
  LXC upstream just released LXC 2.1. This was meant to happen right
  before the Ubuntu feature freeze but we ran a bit late due to last
  minute bugfixes and cleanups.

  LXC 2.1 is generally backward compatible all the way down to LXC 1.0
  and higher, including at the ABI level (new symbols got added but none
  were changed or removed since LXC 1.0). So getting LXC 2.1 in Ubuntu
  17.04 wouldn't require any porting or changes to any downstream
  software in the archive.

  
  This release is meant as a transitional release between the 2.0 and 3.0 
series of LXC. A great number of configuration options were changed and a 
number of tools and commands have now been marked as deprecated. But all this 
without actually removing any of those, instead LXC 2.1 is issuing warnings and 
providing tooling to automatically convert the needed configuration files.

  This will give some time for our users to notice anything that needs
  updating and get it done before they upgrade to LXC 3.0 and things
  will stop working until they do those changes then.

  
  Detailed on the LXC 2.1 release are here: 
https://discuss.linuxcontainers.org/t/lxc-2-1-has-been-released/487

  We have packages ready to upload to artful and that have been used
  during development in our various PPAs. We therefore don't expect any
  significant issues with this hitting the Ubuntu archive.

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

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

[Touch-packages] [Bug 1717689] Re: package systemd-sysv 232-21ubuntu6 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package systemd-sysv 232-21ubuntu6 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  never happens me before...

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: systemd-sysv 232-21ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Sat Sep 16 14:30:43 2017
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 2
  InstallationDate: Installed on 2015-11-12 (674 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: systemd
  Title: package systemd-sysv 232-21ubuntu6 failed to install/upgrade: 
subprocess installed post-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/systemd/+bug/1717689/+subscriptions

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

[Touch-packages] [Bug 1717951] [NEW] UIFe: Drop imagemagick-display from the default install

[Jeremy Bicha]

Public bug reported:

Impact
==
I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10.

It is visible in the Show Applications view of the Activities Overview
so this could impact screenshots.

Justification
=
imagemagick is a collection of commandline utilities for working with images, 
photos, etc. It is a required dependency for many things and will still be 
installed by default.

Bundled with imagemagick is the "display" app, which is an app with an
unusual, difficult-to-use UI. It was not intentionally included in the
default Ubuntu install but was only there because it was packaged
together.

I am proposing splitting the display app to a separate binary package so
that it is available for install for the few who do want to use the app.

I tried proposing this to Debian. See comment #60 on the attached Debian
bug but the Debian maintainer doesn't seem interested in accepting my
proposal any time soon. (I emailed him directly a few months ago too.)

List Notifications
==
https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html
https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html

Other Info
==
I will be attaching a patch for review by the Desktop Team here soon.

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

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

** Package changed: ubuntu-meta (Ubuntu) => imagemagick (Ubuntu)

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

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

** Description changed:

  Impact
  ==
  I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10.
  
  It is visible in the Show Applications view of the Activities Overview
  so this could impact screenshots.
  
  Justification
  =
  imagemagick is a collection of commandline utilities for working with images, 
photos, etc. It is a required dependency for many things.
  
  Bundled with imagemagick is the "display" app, which is an app with an
  unusual, difficult-to-use UI. It was not intentionally included in the
  default Ubuntu install but was only there because it was packaged
  together.
  
  I am proposing splitting the display app to a separate binary package so
  that it is available for install for the few who do want to use the app.
  
- I tried proposing this to Debian. See the final comment on the attached
- Debian bug but the Debian maintainer doesn't seem to see the problem. (I
- emailed him directly a few months ago but he didn't seem that interested
- in fixing the issue any time soon.)
+ I tried proposing this to Debian. See comment #60 on the attached Debian
+ bug but the Debian maintainer doesn't seem interested in accepting my
+ proposal any time soon. (I emailed him directly a few months ago too.)
  
  List Notifications
  ==

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

Title:
  UIFe: Drop imagemagick-display from the default install

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

Bug description:
  Impact
  ==
  I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10.

  It is visible in the Show Applications view of the Activities Overview
  so this could impact screenshots.

  Justification
  =
  imagemagick is a collection of commandline utilities for working with images, 
photos, etc. It is a required dependency for many things and will still be 
installed by default.

  Bundled with imagemagick is the "display" app, which is an app with an
  unusual, difficult-to-use UI. It was not intentionally included in the
  default Ubuntu install but was only there because it was packaged
  together.

  I am proposing splitting the display app to a separate binary package
  so that it is available for install for the few who do want to use the
  app.

  I tried proposing this to Debian. See comment #60 on the attached
  Debian bug but the Debian maintainer doesn't seem interested in
  accepting my proposal any time soon. (I emailed him directly a few
  months ago too.)

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html
  
https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html

  Other Info
  ==
  I will be attaching a patch for review by the Desktop Team here soon.

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

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