date:20170609

[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/1681158

Title:
  package python-six 1.10.0-3 failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 1

Status in six package in Ubuntu:
  Expired

Bug description:
  It crashed when I had open my laptop.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-six 1.10.0-3
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Mar 21 16:45:06 2017
  Dependencies:
   
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2017-03-15 (24 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: six
  Title: package python-six 1.10.0-3 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 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/1681158/+subscriptions

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

[Touch-packages] [Bug 1680750] Re: pm-hibernate does nothing at all

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

** Changed in: pm-utils (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  pm-hibernate does nothing at all

Status in pm-utils package in Ubuntu:
  Expired

Bug description:
  I have run from a command line:
  # sudo pm-hibernate

  and NOTHING f***ing happens.

  Usually it works (except for lots of issues on resume), but now I have
  tried it twice and it does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: powerman (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  7 10:47:47 2017
  InstallationDate: Installed on 2013-10-11 (1273 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: powerman
  UpgradeStatus: Upgraded to xenial on 2016-12-11 (116 days ago)

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

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

[Touch-packages] [Bug 1637684] Re: package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file on stdin at conffile prompt

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

** Changed in: base-files (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file
  on stdin at conffile prompt

Status in base-files package in Ubuntu:
  Expired
Status in dpkg package in Ubuntu:
  Expired

Bug description:
  I don'know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: base-files 9.4ubuntu4.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 29 02:11:08 2016
  Dependencies:
   
  Df:
   Filesystem 1K-blocks  Used Available Use% Mounted on
   udev 8036636 0   8036636   0% /dev
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-10-29 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: base-files
  Title: package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file 
on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.10-help-text: 2016-09-05T02:11:11

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

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

[Touch-packages] [Bug 1637684] Re: package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file on stdin at conffile prompt

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

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

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

Title:
  package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file
  on stdin at conffile prompt

Status in base-files package in Ubuntu:
  Expired
Status in dpkg package in Ubuntu:
  Expired

Bug description:
  I don'know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: base-files 9.4ubuntu4.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 29 02:11:08 2016
  Dependencies:
   
  Df:
   Filesystem 1K-blocks  Used Available Use% Mounted on
   udev 8036636 0   8036636   0% /dev
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-10-29 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: base-files
  Title: package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file 
on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.10-help-text: 2016-09-05T02:11:11

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

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

[Touch-packages] [Bug 1669250] Re: package apport 2.20.3-0ubuntu8 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

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

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

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

Title:
  package apport 2.20.3-0ubuntu8 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  Expired

Bug description:
  anzhuangshibai

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: apport 2.20.3-0ubuntu8
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportLog:
   ERROR: apport (pid 4749) Thu Mar  2 11:10:01 2017: called for pid 4737, 
signal 11, core limit 0
   ERROR: apport (pid 4749) Thu Mar  2 11:10:01 2017: executable was modified 
after program start, ignoring
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashReports: 600:0:122:253095:2017-03-02 11:40:29.509586811 +0800:2017-03-02 
11:40:30.509586811 +0800:/var/crash/apport.0.crash
  Date: Thu Mar  2 11:40:29 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-03-01 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: apport
  Title: package apport 2.20.3-0ubuntu8 failed to install/upgrade: subprocess 
new pre-removal 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/apport/+bug/1669250/+subscriptions

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

[Touch-packages] [Bug 1681410] Re: fstrim corrupts ocfs2 filesystems when clustered

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

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

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

Title:
  fstrim corrupts ocfs2 filesystems when clustered

Status in util-linux package in Ubuntu:
  Expired

Bug description:
  Recently upgraded from trusty to xenial and found that our ocfs2
  filesystems, which are mounted across a number of nodes
  simultaneously, would become corrupt on the weekend:

  [Sun Apr  9 06:46:35 2017] OCFS2: ERROR (device dm-2): 
ocfs2_validate_gd_self: Group descriptor #516096 has bad signature 
  [Sun Apr  9 06:46:35 2017] On-disk corruption discovered. Please run 
fsck.ocfs2 once the filesystem is unmounted.
  [Sun Apr  9 06:46:35 2017] OCFS2: File system is now read-only.
  [Sun Apr  9 06:46:35 2017] (fstrim,1080,8):ocfs2_trim_fs:7399 ERROR: status = 
-30
  [Sun Apr  9 06:46:35 2017] OCFS2: ERROR (device dm-3): 
ocfs2_validate_gd_self: Group descriptor #516096 has bad signature 
  [Sun Apr  9 06:46:36 2017] On-disk corruption discovered. Please run 
fsck.ocfs2 once the filesystem is unmounted.
  [Sun Apr  9 06:46:36 2017] OCFS2: File system is now read-only.
  [Sun Apr  9 06:46:36 2017] (fstrim,1080,10):ocfs2_trim_fs:7399 ERROR: status 
= -30

  We found the cron.weekly job which is pretty close to the timing:
  47 6* * 7   roottest -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.weekly )

  # cat /etc/cron.weekly/fstrim 
  #!/bin/sh
  # trim all mounted file systems which support it
  /sbin/fstrim --all || true

  
  We have disabled this job across our servers running clustered ocfs2 
filesystems.  I think either the utility or the cronjob should ignore ocfs2 
(gfs too?) filesystems.

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

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

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

2017-06-09 Thread Mathieu Trudel-Lapierre

** Tags removed: patch
** Tags added: patch-needswork

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Trusty:
  Confirmed
Status in isc-dhcp source package in Xenial:
  Confirmed
Status in isc-dhcp source package in Yakkety:
  Confirmed
Status in isc-dhcp source package in Zesty:
  Confirmed
Status in isc-dhcp source package in Artful:
  In Progress
Status in isc-dhcp package in Debian:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

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

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

[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

2017-06-09 Thread Jeremy Bicha

** Description changed:

  Ubuntu Online Accounts is no longer maintained. There is an alternative,
  GNOME Online Accounts for the GNOME desktop.
  
  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.
  
  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-china-photo-scope
  unity-scope-gdrive
  
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud
  
  ubuntu-system-settings
  address-book-app
  address-book-service
  buteo-sync-plugins-contacts-google
  camera-app
  dialer-app
  indicator-transfer
  indicator-transfer-buteo
  libertine
  messaging-app
  ubuntu-experience-tests
  unity-scopes-shell
  unity8
  
  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802
  
- Kubuntu still uses signon-ui
- 
- unity still recommends unity-scope-gdrive because it FTBFS
- https://code.launchpad.net/~jbicha/unity/drop-uoa-recommends/+merge/325097
+ Kubuntu still uses signon-ui.
  
  See also https://code.launchpad.net/~xnox/ubuntu-
  seeds/unity8-removals/+merge/323615

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

Title:
  Please remove obsolete UOA packages

Status in gnome-control-center-signon package in Ubuntu:
  New

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-china-photo-scope
  unity-scope-gdrive

  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud

  ubuntu-system-settings
  address-book-app
  address-book-service
  buteo-sync-plugins-contacts-google
  camera-app
  dialer-app
  indicator-transfer
  indicator-transfer-buteo
  libertine
  messaging-app
  ubuntu-experience-tests
  unity-scopes-shell
  unity8

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui.

  See also https://code.launchpad.net/~xnox/ubuntu-
  seeds/unity8-removals/+merge/323615

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+subscriptions

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

[Touch-packages] [Bug 1697131] [NEW] ailed tpackage gconf2-common 3.2.6-3ubuntu7 fo install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-06-09 Thread Jacob de Lange-Hope

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

Public bug reported:

After installing Ubuntu 17.04 and updating this occurs every time.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Sat Jun 10 15:20:55 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-10 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  ailed tpackage gconf2-common 3.2.6-3ubuntu7 fo install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  After installing Ubuntu 17.04 and updating this occurs every time.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat Jun 10 15:20:55 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-10 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1697131] Re: ailed tpackage gconf2-common 3.2.6-3ubuntu7 fo install/upgrade: subprocess installed post-installation script returned error exit status 128

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  ailed tpackage gconf2-common 3.2.6-3ubuntu7 fo install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  After installing Ubuntu 17.04 and updating this occurs every time.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat Jun 10 15:20:55 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-10 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1697126] [NEW] Popping sound whenever a client connects / disconnects

2017-06-09 Thread Johannes H. Jensen

Public bug reported:

I'm getting an annoying popping sound whenever pulseaudio gets a new
connection or a connection dies. This is especially annoying since
google chrome seems to open new connections rather often for no apparent
reason, interrupting music playback with glitches.

Steps to reproduce:
1. Start playback of some audio with totem or similar
2. Play a silent audio file with paplay silence.wav, I got mine from audacity
3. Observe pops in the playback from totem

Interestingly there are no pops if I use paplay instead of totem for
step 1. Attaching debug output from pulseaudio - during the
reproducer above.

My sound card is a USB DAC:

card 3: DAC [UAC1 DAC], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.2
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  joh   19113 F pulseaudio
 /dev/snd/controlC2:  joh   19113 F pulseaudio
 /dev/snd/controlC1:  joh   19113 F pulseaudio
 /dev/snd/controlC0:  joh   19113 F pulseaudio
CurrentDesktop: GNOME
Date: Sat Jun 10 04:06:46 2017
InstallationDate: Installed on 2011-10-01 (2078 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to xenial on 2016-09-18 (264 days ago)
dmi.bios.date: 09/18/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.7
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97 GAMING 5 (MS-7917)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/18/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7917
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug xenial

** Attachment added: "debug output from pulseaudio - while reproducing the 
issue"
   
https://bugs.launchpad.net/bugs/1697126/+attachment/4893344/+files/pa-popping.log

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

Title:
  Popping sound whenever a client connects / disconnects

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm getting an annoying popping sound whenever pulseaudio gets a new
  connection or a connection dies. This is especially annoying since
  google chrome seems to open new connections rather often for no
  apparent reason, interrupting music playback with glitches.

  Steps to reproduce:
  1. Start playback of some audio with totem or similar
  2. Play a silent audio file with paplay silence.wav, I got mine from audacity
  3. Observe pops in the playback from totem

  Interestingly there are no pops if I use paplay instead of totem for
  step 1. Attaching debug output from pulseaudio - during the
  reproducer above.

  My sound card is a USB DAC:

  card 3: DAC [UAC1 DAC], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  joh   19113 F pulseaudio
   /dev/snd/controlC2:  joh   19113 F pulseaudio
   /dev/snd/controlC1:  joh   19113 F pulseaudio
   /dev/snd/controlC0:  joh   19113 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Jun 10 04:06:46 2017
  InstallationDate: Installed on 2011-10-01 (2078 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to xenial on 2016-09-18 (264 days ago)
  dmi.bios.date: 09/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 5 (MS-7917)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/18/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7917
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To

[Touch-packages] [Bug 1697121] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0] failed to install/upgrade: package

2017-06-09 Thread Thomas W Hardy

Public bug reported:

I am going to investigate w/ synaptic package manager and software.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: 
lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0]
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic i686
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
 libssl1.0.0: Configure
 NULL: ConfigurePending
Architecture: i386
Date: Fri Jun  9 17:40:32 2017
DpkgTerminalLog:
 dpkg: error processing package libssl1.0.0:i386 (--configure):
  package libssl1.0.0:i386 is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package libssl1.0.0:i386 is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2017-05-27 (13 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: 
lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0] 
failed to install/upgrade: package libssl1.0.0:i386 is not ready for 
configuration  cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: lib/i386-linux-
  gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0] failed to
  install/upgrade: package libssl1.0.0:i386 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  I am going to investigate w/ synaptic package manager and software.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: 
lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0]
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libssl1.0.0: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Fri Jun  9 17:40:32 2017
  DpkgTerminalLog:
   dpkg: error processing package libssl1.0.0:i386 (--configure):
package libssl1.0.0:i386 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libssl1.0.0:i386 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-27 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: 
lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0] 
failed to install/upgrade: package libssl1.0.0:i386 is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-09 Thread Nicholas Stommel

Unfortunately my patch is not a good solution for upstream application.
I agree with what Beniamino Galvani mentioned, that "it is wrong to
assume the connection is a VPN based on the link type, since you can
have non-VPN tun/tap/gre/gretap connections as well, and they are
affected by this patch." However, it seems that this issue with DNS
leaks over NM-VPN connections and broken VPN split-horizon DNS using
systemd-resolved still exists upstream and doesn't have a good fix.

I think this issue needs some attention and work from the Gnome-
NM/systemd/Canonical devs, I've reached my limit here. :(

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1691420] Re: package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in packag

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

** Changed in: account-plugins (Ubuntu)
   Status: New => Confirmed

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

Title:
  package account-plugin-google (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/share/accounts/providers/google.provider', which is also in
  package kaccounts-providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  Confirmed

Bug description:
  Not quite sure what triggered this bug

  Description:Ubuntu 16.04.2 LTS
  Release:16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat May 13 22:35:12 2017
  DuplicateSignature:
   package:account-plugin-google:(not installed)
   Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2017-05-13 (4 days ago)
  InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: account-plugins
  Title: package account-plugin-google (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1594296] Re: [USB-Audio - USB Sound Device, playback] Occasional audio playback blips from Sweex 7.1 external USB card

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

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

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

Title:
  [USB-Audio - USB Sound Device, playback] Occasional audio playback
  blips from Sweex 7.1 external USB card

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When playing audio back (from Chrome), I get occasional blips where it
  sounds like the audio is skipping forwards or backwards.  I've
  followed the instructions at https://wiki.ubuntu.com/PulseAudio/Log to
  configure a debug log and I generally see this in the log when it
  happens:

  ( 765.763|   0.194) I: [alsa-source-ALC269VC Analog] alsa-source.c: Overrun!
  ( 767.600|   1.837) I: [alsa-sink-USB Audio] alsa-sink.c: Scheduling delay of 
361.78 ms > 15.99 ms, you might want to investigate this to improve latency...
  ( 767.600|   0.000) I: [alsa-sink-USB Audio] alsa-sink.c: Increasing minimal 
latency to 36.00 ms
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: Latency set to 
36.00ms
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: hwbuf_unused=1029528
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: setting 
avail_min=86677
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] protocol-native.c: max_request 
changed, trying to update from 8680 to 10444.
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] protocol-native.c: Notifying 
client about increased tlength
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: Latency set to 
36.00ms
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: hwbuf_unused=1029528
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: setting 
avail_min=86677
  ( 767.601|   0.000) D: [alsa-sink-USB Audio] protocol-native.c: Implicit 
underrun of 'Playback'
  ( 767.615|   0.014) D: [alsa-sink-USB Audio] protocol-native.c: Requesting 
rewind due to end of underrun.
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: Requested to rewind 
178188 bytes.
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: Limited to 18788 
bytes.
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: before: 1565
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: after: 1565
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: Rewound 18780 bytes.
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] sink.c: Processing rewind...
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] sink-input.c: Have to rewind 
18780 bytes on render memblockq.
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] source.c: Processing rewind...
  ( 768.855|   1.239) I: [alsa-source-ALC269VC Analog] ratelimit.c: 85 events 
suppressed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jun 20 10:04:42 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-27 (53 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Device successful
  Symptom_Card: CM106 Like Sound Device - USB Sound Device
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [USB-Audio - USB Sound Device, playback] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MMLP7AP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd02/19/2014:svnGIGABYTE:pnMMLP7AP-00:pvr1.x:rvnGIGABYTE:rnMMLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: MMLP7AP-00
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

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

[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-06-09 Thread Eric Desrochers

Additionally,

I just noticed that LP: #1696863 is about a "ubuntu4.6" failure on
Precise :

InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.20
SourcePackage: openssl
Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade:

Which is seems odd to me since "ubuntu4.6" is for Trusty only and
precise has "1.0.1-4ubuntu5.39" version.

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Fix Released
Status in openssl source package in Yakkety:
  Fix Released
Status in openssl source package in Zesty:
  Fix Released
Status in openssl source package in Artful:
  Fix Released

Bug description:
  [Impact]

  * Context:

  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
  64bit only (Confirmed with AMD representative). Current OpenSSL
  version in Ryzens still calls SHA for SSSE3 routine as result a number
  of extensions were effectively masked on Ryzen and shows no
  improvement.

  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family : 23
  model : 1
  model name : AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni 
pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

  [2] - sha_ni: SHA1/SHA256 Instruction Extensions

  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...

  * Program to performs the CPUID check:

  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions

  ... Availability of the Intel® SHA Extensions on a particular
  processor can be determined by checking the SHA CPUID bit in
  CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function,
  using inline assembly, performs the CPUID check:

  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;

     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;

     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );

     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --

  On CPU with sha_ni the program return "1". Otherwise it return "0".

  [Test Case]

   * Reproducible with Xenial/Zesty/Artful release.

   * Generated a checksum of a big file (e.g. 5GB file) with openssl
   $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
  SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8

  real  0m12.835s
  user  0m12.344s
  sys   0m0.484s

  * Openssl speed
  $ openssl speed sha1
  Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
  Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
  Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
  Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
  Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
  OpenSSL 1.0.2g 1 Mar 2016
  built on: reproducible build, date unspecified
  options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
  compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT 
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall 
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM 
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
  The 'numbers' are in 1000s of bytes per second processed.
  type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
  sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55

  The performance are clearly better when using the patch which take
  benefit of the sha extension. (See Regression Potential section for
  result with patch)

  [Regression Potential]

   * Note : IRC discussion with infinity :
  
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/comments/8

   * Note from irc

[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-06-09 Thread Eric Desrochers

Seth,

I don't think it is related ... 3 of them are related to package(s)
prior this SRU on version "1.0.2g-1ubuntu4.6" release on "Mon, 30 Jan
2017" and only 1 on "1.0.2g-1ubuntu4.8" for Xenial & another on on
"libssl1.0.0" for Zesty.


Title: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade
1697099

Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade
1692981

Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
1696799

Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade:
1696863
1696930


I also did a couple of upgrade from "ubuntu4.6" to "ubuntu4.8" inside amd64 and 
i386 lxc container myself during the SRU and again today, and I haven't been 
able to reproduce the situation.

As per our irc conversation, it is probably just being some random pile
of noise, but let's keep an eye on it in the next few days.

- Eric

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Fix Released
Status in openssl source package in Yakkety:
  Fix Released
Status in openssl source package in Zesty:
  Fix Released
Status in openssl source package in Artful:
  Fix Released

Bug description:
  [Impact]

  * Context:

  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
  64bit only (Confirmed with AMD representative). Current OpenSSL
  version in Ryzens still calls SHA for SSSE3 routine as result a number
  of extensions were effectively masked on Ryzen and shows no
  improvement.

  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family : 23
  model : 1
  model name : AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni 
pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

  [2] - sha_ni: SHA1/SHA256 Instruction Extensions

  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...

  * Program to performs the CPUID check:

  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions

  ... Availability of the Intel® SHA Extensions on a particular
  processor can be determined by checking the SHA CPUID bit in
  CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function,
  using inline assembly, performs the CPUID check:

  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;

     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;

     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );

     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --

  On CPU with sha_ni the program return "1". Otherwise it return "0".

  [Test Case]

   * Reproducible with Xenial/Zesty/Artful release.

   * Generated a checksum of a big file (e.g. 5GB file) with openssl
   $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
  SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8

  real  0m12.835s
  user  0m12.344s
  sys   0m0.484s

  * Openssl speed
  $ openssl speed sha1
  Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
  Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
  Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
  Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
  Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
  OpenSSL 1.0.2g 1 Mar 2016
  built on: reproducible build, date unspecified
  options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
  compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT 
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall 
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM 
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
  The 'numbers' are in 1000s of bytes per

[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-06-09 Thread Seth Arnold

Some of the bug reports in my previous comment are actually filed
against previous versions of openssl (despite all being filed recently).
Eric noted that only 1692981 (zesty) and 1696799 (xenial) are for this
SRU, and 1696863 1697099 1696930 are for previous updates.

I don't think there's an issue with this SRU; this just appears to be
usual upgrade failure noise with unfortunate timing making me think
there may be a pattern here.

Thanks, and thanks to Eric for the extra research late on a Friday.

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Fix Released
Status in openssl source package in Yakkety:
  Fix Released
Status in openssl source package in Zesty:
  Fix Released
Status in openssl source package in Artful:
  Fix Released

Bug description:
  [Impact]

  * Context:

  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
  64bit only (Confirmed with AMD representative). Current OpenSSL
  version in Ryzens still calls SHA for SSSE3 routine as result a number
  of extensions were effectively masked on Ryzen and shows no
  improvement.

  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family : 23
  model : 1
  model name : AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni 
pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

  [2] - sha_ni: SHA1/SHA256 Instruction Extensions

  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...

  * Program to performs the CPUID check:

  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions

  ... Availability of the Intel® SHA Extensions on a particular
  processor can be determined by checking the SHA CPUID bit in
  CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function,
  using inline assembly, performs the CPUID check:

  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;

     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;

     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );

     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --

  On CPU with sha_ni the program return "1". Otherwise it return "0".

  [Test Case]

   * Reproducible with Xenial/Zesty/Artful release.

   * Generated a checksum of a big file (e.g. 5GB file) with openssl
   $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
  SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8

  real  0m12.835s
  user  0m12.344s
  sys   0m0.484s

  * Openssl speed
  $ openssl speed sha1
  Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
  Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
  Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
  Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
  Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
  OpenSSL 1.0.2g 1 Mar 2016
  built on: reproducible build, date unspecified
  options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
  compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT 
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall 
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM 
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
  The 'numbers' are in 1000s of bytes per second processed.
  type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
  sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55

  The performance are clearly better when using the patch which take
  benefit of the sha extension. (See Regression Potential section for
  result with patch)

  [Regression Potential]

   * Note : IRC discussion with infinity :

[Touch-packages] [Bug 1199460] Re: Printing a #10 envelope truncates return address

2017-06-09 Thread peter gibson

I inserted 3 spaces into the return address field on each line to work
around it.

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

Title:
  Printing a #10 envelope truncates return address

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This bug was first reported by me to Freedesktop (bug 37733)  because
  it only showed up when printing envelopes from LibreOffice writer.
  But we determined that it was apparently a bug in cups, not
  LibreOffice.

  Note:  it is definitely not a problem with printer margins.  In fact,
  I increased that setting, but it still truncated, only further from
  the edge.

  I believe the problem is that the printer needs to be set to a larger
  paper size for a #10 envelope; 9.5 inches vs 8.5. When I print to PDF,
  I can see both the envelope and the document, and the return address
  is truncated right about at the 8.5" edge of the document.  I've
  printed to the same printer using Windows, and noticed that it sets
  the printer to "legal"; in fact, I sometimes got annoyed that it would
  stop and prompt me to "Load legal" on the printer, and I would need to
  press the continue button, whereupon it would print the envelope with
  no problems.

  Printing to a PDF file prints normally, so I think that means the
  actual printer needs to be set.  The PDF file is the correct size, but
  even trying to print from it causes truncation unless it is printed to
  an 8.5 x 11 sheet of paper.

  I first discovered this problem a few years ago, I believe, but gave
  up trying to solve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: cups 1.5.3-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46
  Uname: Linux 3.2.0-49-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Tue Jul  9 10:14:21 2013
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.1)
  Lpstat: device for Deskjet-6940-series: 
dnssd://Deskjet%206940%20series%20%5B8D699B%5D._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Papersize: letter
  PpdFiles: Deskjet-6940-series: HP Deskjet 6940 Series, hpcups 3.12.2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-49-generic 
root=UUID=7dbc17ff-1769-46e6-9470-fe975fa71ed6 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 1604
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision1604:bd12/19/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1199460] Re: Printing a #10 envelope truncates return address

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

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

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

Title:
  Printing a #10 envelope truncates return address

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This bug was first reported by me to Freedesktop (bug 37733)  because
  it only showed up when printing envelopes from LibreOffice writer.
  But we determined that it was apparently a bug in cups, not
  LibreOffice.

  Note:  it is definitely not a problem with printer margins.  In fact,
  I increased that setting, but it still truncated, only further from
  the edge.

  I believe the problem is that the printer needs to be set to a larger
  paper size for a #10 envelope; 9.5 inches vs 8.5. When I print to PDF,
  I can see both the envelope and the document, and the return address
  is truncated right about at the 8.5" edge of the document.  I've
  printed to the same printer using Windows, and noticed that it sets
  the printer to "legal"; in fact, I sometimes got annoyed that it would
  stop and prompt me to "Load legal" on the printer, and I would need to
  press the continue button, whereupon it would print the envelope with
  no problems.

  Printing to a PDF file prints normally, so I think that means the
  actual printer needs to be set.  The PDF file is the correct size, but
  even trying to print from it causes truncation unless it is printed to
  an 8.5 x 11 sheet of paper.

  I first discovered this problem a few years ago, I believe, but gave
  up trying to solve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: cups 1.5.3-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46
  Uname: Linux 3.2.0-49-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Tue Jul  9 10:14:21 2013
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.1)
  Lpstat: device for Deskjet-6940-series: 
dnssd://Deskjet%206940%20series%20%5B8D699B%5D._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Papersize: letter
  PpdFiles: Deskjet-6940-series: HP Deskjet 6940 Series, hpcups 3.12.2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-49-generic 
root=UUID=7dbc17ff-1769-46e6-9470-fe975fa71ed6 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 1604
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision1604:bd12/19/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1697054] Re: vim-gtk3 should not depend on libruby and hold ruby in main

This bug was fixed in the package vim - 2:8.0.0197-4ubuntu2

---
vim (2:8.0.0197-4ubuntu2) artful; urgency=medium

  * Drop ruby from vim-gtk3; we don't want ruby in main in Ubuntu.
LP: #1697054.

 -- Steve Langasek   Fri, 09 Jun 2017
13:55:48 -0700

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

Title:
  vim-gtk3 should not depend on libruby and hold ruby in main

Status in vim package in Ubuntu:
  Fix Released

Bug description:
  Currently ruby is in main not because it's seeded, but because it's a
  runtime dependency of vim-gtk3.  We don't otherwise support ruby and
  should drop this dependency from vim-gtk3.

  vim-gtk can keep this dependency since it's in main.

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

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

[Touch-packages] [Bug 997200] Re: Add NetworkManager connectivity config package

2017-06-09 Thread Bug Watch Updater

** Changed in: network-manager (Debian)
   Status: New => Fix Released

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

Title:
  Add NetworkManager connectivity config package

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Precise:
  Won't Fix
Status in update-manager source package in Precise:
  Won't Fix
Status in network-manager source package in Quantal:
  Won't Fix
Status in update-manager source package in Quantal:
  Won't Fix
Status in network-manager source package in Raring:
  Won't Fix
Status in update-manager source package in Raring:
  Won't Fix
Status in network-manager package in Debian:
  Fix Released

Bug description:
  Feature
  ===
  A separate network-manager-config-connectivity package that contains the 
3-line config snippet to enable NetworkManager's connectivity check. This is 
the same approach taken by Fedora since 2014 (their package is named 
config-connectivity-fedora).

  jbicha would like to have ubuntu-gnome-desktop recommend this package for 
zesty. With this config, GNOME Shell will popup a browser page when a captive 
portal is detected. The browser page is powered by webkit2gtk.
  https://help.gnome.org/misc/release-notes/3.14/#captive-portals

  By making it a separate package, it is very easy for Ubuntu flavors to
  opt in to installing it by default if they choose. And it's very easy
  for users to opt in or out without needing to mess around with system
  configuration files.

  This new feature (and how to opt out) will be mentioned in Ubuntu
  GNOME's Release Notes.

  Enabling the connectivity check by default for all of Ubuntu was discussed 
almost 5 years ago:
  https://lists.ubuntu.com/archives/ubuntu-devel/2012-July/035490.html

  Link to new discussion:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039696.html

  Git merge proposal attached.

  Original Bug Report
  ==
  When in a hotel there is a often a T page that is delivered when 
connecting to the network.  Some combination of network manager and update 
manager (or something else entirely) doesn't seem to be able to handle this, 
and update are left in a non-working state after not being able to read package 
headers file.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Wed May  9 17:27:02 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IpRoute:
   default via 10.155.32.1 dev wlan0  proto static
   10.155.32.0/19 dev wlan0  proto kernel  scope link  src 10.155.38.82  metric 
2
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-03-07 (63 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.4.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-06-09 Thread Seth Arnold

William, Eric, I'm curious if this OpenSSL update may have introduced
issues:

https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697099
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1696930
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1696863
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1696799
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1692981

My own upgrades on the command line went without troubles.

Thanks

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Fix Released
Status in openssl source package in Yakkety:
  Fix Released
Status in openssl source package in Zesty:
  Fix Released
Status in openssl source package in Artful:
  Fix Released

Bug description:
  [Impact]

  * Context:

  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
  64bit only (Confirmed with AMD representative). Current OpenSSL
  version in Ryzens still calls SHA for SSSE3 routine as result a number
  of extensions were effectively masked on Ryzen and shows no
  improvement.

  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family : 23
  model : 1
  model name : AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni 
pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

  [2] - sha_ni: SHA1/SHA256 Instruction Extensions

  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...

  * Program to performs the CPUID check:

  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions

  ... Availability of the Intel® SHA Extensions on a particular
  processor can be determined by checking the SHA CPUID bit in
  CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function,
  using inline assembly, performs the CPUID check:

  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;

     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;

     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );

     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --

  On CPU with sha_ni the program return "1". Otherwise it return "0".

  [Test Case]

   * Reproducible with Xenial/Zesty/Artful release.

   * Generated a checksum of a big file (e.g. 5GB file) with openssl
   $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
  SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8

  real  0m12.835s
  user  0m12.344s
  sys   0m0.484s

  * Openssl speed
  $ openssl speed sha1
  Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
  Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
  Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
  Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
  Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
  OpenSSL 1.0.2g 1 Mar 2016
  built on: reproducible build, date unspecified
  options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
  compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT 
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall 
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM 
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
  The 'numbers' are in 1000s of bytes per second processed.
  type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
  sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55

  The performance are clearly better when using the patch which take
  benefit of the sha extension. (See Regression Potential section for
  result with patch)

  [Regression Potential]

   * Note : IRC discussion with infinity :
  
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/comments/8

   *

[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-06-09 Thread Olcay Korkmaz

Hi,

is llvm-toolchain-4.0 final release looks like it's rc1

llvm-toolchain-4.0_4.0.orig is not same as llvm-4.0.0.src from llvm.org

clang version 4.0.0-1ubuntu1~16.04.1 (tags/RELEASE_400/rc1)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

it make is trouble like when build with 4.0.0-1ubuntu1~16.04.1

terminate called after throwing an instance of 'std::runtime_error'
  what():  Verification failed (e=9): file::write

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  Fix Committed
Status in libxfont2 source package in Xenial:
  Fix Committed
Status in llvm-toolchain-4.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in vulkan source package in Xenial:
  New
Status in wayland source package in Xenial:
  Fix Committed
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

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

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

[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser

I sponsored the click packages from
https://launchpad.net/~sergiusens/+archive/ubuntu/ppa/+packages?field.name_filter=click_filter=published_filter=
which fix this for Yakkety and Zesty. They are in the queue awaiting SRU
team review.

I did not upload the Xenial package because it is an upgrade from 0.4.43
to 0.4.46 and I think that bears some further discussion.

** Also affects: click (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: click (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

Title:
  Break the conflicts with click the optparser

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Yakkety:
  New
Status in click source package in Zesty:
  New

Bug description:
  [Impact]

   * python-click and python-click-package conflict as they use the same
 python package for its implementation.

   * Since python-click-package is an implementation detail for the click 
 package and python3-click is a package meant to be used in other
 implementations it makes sense to break the conflict by moving the
 package name for python-click-package to a different name

   * snapcraft has moved from docopt to python3-click, users that have click
 installed don't have an upgrade path.his bug.

  [Test Case]

   * Where snapcraft 2.30 is present:
 
 - apt install click
 - Install snapcraft << 2.30
 - update to snapcraft >= 2.30
 - the upgrade should not be held on any package.
 - click and snapcraft commands should work.

  * Install python3-click and click should be possible. The click command
should keep working and python3 -c 'from click import group' shall work.

  
  [Regression Potential] 

   * Users depending on click from python-click-package will be importing an
 unexpected click in any scripts they may have.

  [Other Info]
   
   * While unfortunate, click as a technology is deprecated and not used
 anymore. This resolution path was discussed with slangasek and apw prior
 to any work.

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

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

[Touch-packages] [Bug 1697099] [NEW] package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: package openssl is not ready for configuration cannot configure (current status 'half-installed')

2017-06-09 Thread JQ

Public bug reported:

Software update fails to update.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssl 1.0.2g-1ubuntu4.6
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
 deja-dup-backend-gvfs: Install
 openssl: Configure
 deja-dup-backend-gvfs: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Jun  9 15:22:04 2017
DuplicateSignature:
 package:openssl:1.0.2g-1ubuntu4.6
 Unpacking deja-dup-backend-gvfs (34.2-0ubuntu1.1) over (34.2-0ubuntu1) ...
 dpkg: error processing package openssl (--configure):
  package openssl is not ready for configuration
ErrorMessage: package openssl is not ready for configuration  cannot configure 
(current status 'half-installed')
InstallationDate: Installed on 2017-06-09 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
Title: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: package 
openssl is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: package
  openssl is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  Software update fails to update.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   deja-dup-backend-gvfs: Install
   openssl: Configure
   deja-dup-backend-gvfs: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jun  9 15:22:04 2017
  DuplicateSignature:
   package:openssl:1.0.2g-1ubuntu4.6
   Unpacking deja-dup-backend-gvfs (34.2-0ubuntu1.1) over (34.2-0ubuntu1) ...
   dpkg: error processing package openssl (--configure):
package openssl is not ready for configuration
  ErrorMessage: package openssl is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: package 
openssl is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1697099] Re: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: package openssl is not ready for configuration cannot configure (current status 'half-installed')

** Tags removed: need-duplicate-check

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

Title:
  package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: package
  openssl is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  Software update fails to update.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   deja-dup-backend-gvfs: Install
   openssl: Configure
   deja-dup-backend-gvfs: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jun  9 15:22:04 2017
  DuplicateSignature:
   package:openssl:1.0.2g-1ubuntu4.6
   Unpacking deja-dup-backend-gvfs (34.2-0ubuntu1.1) over (34.2-0ubuntu1) ...
   dpkg: error processing package openssl (--configure):
package openssl is not ready for configuration
  ErrorMessage: package openssl is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: package 
openssl is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-09 Thread Nicholas Stommel

Actually I take that back. The issue is not fixed by the commit
referenced on https://bugzilla.gnome.org/show_bug.cgi?id=783569 as it is
already present in the current version of the network-manager. So we
still have a major problem folks.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

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

** Also affects: update-notifier (Ubuntu Artful)
   Importance: Low
   Status: Confirmed

** Also affects: unattended-upgrades (Ubuntu Artful)
   Importance: Low
   Status: Confirmed

** Also affects: linux (Ubuntu Artful)
   Importance: Low
 Assignee: Adam Conrad (adconrad)
   Status: Confirmed

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed
Status in unattended-upgrades source package in Artful:
  Confirmed
Status in update-notifier source package in Artful:
  Confirmed

Bug description:
  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1697098] [NEW] PCI/internal sound card not detected, sound no possible i don't know more.

2017-06-09 Thread stefano

Public bug reported:

sorry i dont speak inglish very well
i am italian
i want only yous my ubuntu now but the audio is not possible :(

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity:Unity7
Date: Fri Jun  9 23:14:51 2017
InstallationDate: Installed on 2017-06-09 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.11
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 827C
dmi.board.vendor: HP
dmi.board.version: 93.22
dmi.chassis.type: 32
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.11:bd09/30/2016:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.22:cvnHP:ct32:cvrChassisVersion:
dmi.product.name: HP x2 Detachable 10-p0XX
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug zesty

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

Title:
  PCI/internal sound card not detected, sound no possible i don't know
  more.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  sorry i dont speak inglish very well
  i am italian
  i want only yous my ubuntu now but the audio is not possible :(

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity:Unity7
  Date: Fri Jun  9 23:14:51 2017
  InstallationDate: Installed on 2017-06-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827C
  dmi.board.vendor: HP
  dmi.board.version: 93.22
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.11:bd09/30/2016:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.22:cvnHP:ct32:cvrChassisVersion:
  dmi.product.name: HP x2 Detachable 10-p0XX
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1639452] Re: systemd ExecStartPre test config

I'm currently scanning through bugs that were dormant for too long.
I must beg your pardon - in particular because I was the (less experienced me 
back then) one who triaged it initially.

Looking back the right decision would have been to ask you to report
this to Debian.

This bug is present in Debian too, and Ubuntu currently doesn't make any 
changes over the Debian package. So this bug would be best fixed directly in 
Debian, and then Ubuntu will pick up the fix automatically.
OTOH I think your request is perfectly valid - the dependency on 
systemd-resolvd as well as the check of the right config.

Therefore it would be great if you could report that to Debian and link the bug 
here.
Once fixed there Ubuntu will automatically pick that up for the next release 
and from there we can consider SRU's.

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

Title:
  systemd ExecStartPre test config

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  The standard configuration file of dnsmasq is complete commented out.
  The real configuration is saved in /etc/dnsmasq.d, so the test of
  systemd is a fake.

  In the Service Section of /lib/systemd/system/dnsmasq.service the
  ExecStartPre directive should be set to "/usr/sbin/dnsmasq --conf-
  dir=/etc/dnsmasq.d --test"

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

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

[Touch-packages] [Bug 1676339] Re: update-manager crashed with AttributeError in show_settings(): 'GdkMirWindow' object has no attribute 'get_xid'

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

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

Title:
  update-manager crashed with AttributeError in show_settings():
  'GdkMirWindow' object has no attribute 'get_xid'

Status in mir package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  Invalid

Bug description:
  In Unity 8, I clicked on the "Show Settings" button in Update Manager,
  and nothing happened. After logging back into Unity 7, I was prompted
  to answer this crash report. That's all.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: update-manager 1:17.04.3
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Aptdaemon:
   
  Architecture: amd64
  CurrentDesktop: Unity:Unity8
  Date: Mon Mar 27 04:58:13 2017
  ExecutablePath: /usr/bin/update-manager
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'787'
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'window-width' b'665'
   b'com.ubuntu.update-manager' b'launch-time' b'int64 1490608674'
  InstallationDate: Installed on 2017-01-30 (56 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/update-manager
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PythonArgs: ['/usr/bin/update-manager']
  SourcePackage: update-manager
  Title: update-manager crashed with AttributeError in show_settings(): 
'GdkMirWindow' object has no attribute 'get_xid'
  UpgradeStatus: Upgraded to zesty on 2017-03-27 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1697093] [NEW] Black Screen after boot.

2017-06-09 Thread Abhiroj

Public bug reported:

Please bear with me as This is the last place to resolve the as I have
tried different resources available for the problem already, but with no
effect.Long story short, Ubuntu 16.04 was working fine for a long time
but since recently, It is showing up the black screen after boot.By
blank screen, I mean:-

**The Problem**:-

After Boot (i.e. after purple screen),

1. There is no mouse pointer.

2. A cursor blinks for a few seconds and screen goes 100% black but
still lit, and then after another few seconds, it goes completely dark
as if it is turned off.

3. I wait and then switch to the command-line screen or tty1 to get the
logs.

**What I have done yet**:-

1. I have updated my system, with `oibaf-drivers` but still no help.
`fglrx` is officially deprecated for Ubuntu 16.04 and `amdgpu-pro`
provided by AMD does not support AMD graphic card of my
system.Currently, the system is using(I don't whether it is perfectly
working or not) `radeon driver` (The OSS driver for AMD). For more info,
here are the specs of GPU on my system:-

Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun LE
[Radeon HD 8550M / R5 M230]

VGA compatible controller: Intel Corporation Haswell-ULT Integrated
Graphics Controller (rev 09)

2. `dmesg | grep -i radeon` shows no error during boot-up.

3. Running the system in `nomodeset`, which is resulting in highly poor
graphics performance. It is much deflected compared to ideal.

4. Not running the system in `nomodeset` but using `startX` in tty1, the
systemUI restarts again but `mouse pointer turns to a cross` and only
folders present on my desktop are visible, but no wallpaper can be seen,
no side-dock, no launcher (after the click) and no status bar.The
desktop is completely absent though desktop folders are visible and can
be opened.

Please suggest a solution.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
BootLog: /dev/sda11: clean, 302776/3129344 files, 2203296/12499968 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Jun 10 01:39:53 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
   Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c]
InstallationDate: Installed on 2017-05-18 (21 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO ACLU12
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic 
root=UUID=f693a857-8102-4f79-a16a-ad0d75fb8edc ro quiet splash nomodeset 
vt.handoff=7
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/02/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 9ACN25WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIUU4
dmi.board.vendor: LENOVO
dmi.board.version: 3196STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: INVALID
dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pnACLU12:pvrINVALID:rvnLENOVO:rnVIUU4:rvr3196STD:cvnLENOVO:ct10:cvrINVALID:
dmi.product.name: ACLU12
dmi.product.version: INVALID
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.81+git1706061830.b6f450~gd~x
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2~git1706091930.d42fc6~gd~x
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2~git1706091930.d42fc6~gd~x
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.9.99+git1705240733.d80d01~gd~x
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1706071933.6babcf~gd~x
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1704220733.a7c190~gd~x
xserver.bootTime: Sat Jun 10 01:35:56 2017
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

** Affects: xorg (Ubuntu)
 Importance: Undecided

[Touch-packages] [Bug 1629021] Re: package clamav-freshclam 0.99.2+addedllvm-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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

Yeah then it really was the known bug around the "Use of uninitialized
value $_[1] in join or string at
/usr/share/perl5/Debconf/DbDriver/Stack.pm"

I'll be dupping this one onto the issue tracking that.

** This bug has been marked a duplicate of bug 1646739
   "Use of uninitialized value" in debconf via update-manager

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

Title:
  package clamav-freshclam 0.99.2+addedllvm-0ubuntu0.14.04.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 128

Status in clamav package in Ubuntu:
  New
Status in debconf package in Ubuntu:
  New

Bug description:
  0.98 was already installed prior to upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: clamav-freshclam 0.99.2+addedllvm-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-96-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Thu Sep 29 10:02:15 2016
  DuplicateSignature: 
package:clamav-freshclam:0.99.2+addedllvm-0ubuntu0.14.04.1:subprocess installed 
post-installation script returned error exit status 128
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2015-01-14 (623 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-96-generic 
root=UUID=37f17f9e-a506-4ead-8d00-47107a0179fb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: clamav
  Title: package clamav-freshclam 0.99.2+addedllvm-0ubuntu0.14.04.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1693038] Re: needs to support restart on Lubuntu and Xubuntu

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: software-properties (Ubuntu)
Milestone: None => ubuntu-17.07

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

Title:
  needs to support restart on Lubuntu and Xubuntu

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  The fix for bug 1241210 only works in gnome-session based sessions.
  Let's make sure that the driver restart button works on Xubuntu and
  Lubuntu.

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

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

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

2017-06-09 Thread Dan Streetman

I should note:

1. The isc-dhcp code is common between dhcpd and dhclient
2. The current system interfaces are enumerated in common/discover.c, and that 
code - in next_iface() - strips the interface alias from all enumerated 
interfaces, so when dhcpd or dhclient is comparing a parameter against an 
existing interface, none of the existing enumerated interface names will have 
aliases
3. The interface parameters are parsed separately for dhcpd and dhclient; my 
patch changes *only* the parsing for dhclient, in client/dhclient.c, so that 
any command line interface names have their alias stripped
4. Other places that parse interface name parameters are dhcpd (in 
server/dhcpd.c), interface hotplug (maybe? in server/mdb.c, not sure about this 
file), and the dhcp relay (in relay/dhcrelay.c); my patch does *not* change any 
of these places, so interface name parameters to dhcpd, the dhcp relay, or in 
mdb.c, will still have interface aliases, and will not match any of the 
internally-enumerated (in common/discover.c) interface names.  However, my 
patch narrowly fixes this specific bug, of 'dhclient -6 eth0:1' not working.

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Trusty:
  Confirmed
Status in isc-dhcp source package in Xenial:
  Confirmed
Status in isc-dhcp source package in Yakkety:
  Confirmed
Status in isc-dhcp source package in Zesty:
  Confirmed
Status in isc-dhcp source package in Artful:
  In Progress
Status in isc-dhcp package in Debian:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

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

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

[Touch-packages] [Bug 1697079] [NEW] glib/glib-autocleanups.h missing from package

2017-06-09 Thread mike-g2

Public bug reported:

I am trying to install R 3.3.1 from source, but it fails due to a lack
of the header file

/usr/include/glib-2.0/glib/glib-autocleanups.h

This file is found in later versions of the libglib2.0-dev but not in
version libglib2.0-dev 2.40.2-0ubuntu1 for 14.04.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  glib/glib-autocleanups.h missing from package

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I am trying to install R 3.3.1 from source, but it fails due to a lack
  of the header file

  /usr/include/glib-2.0/glib/glib-autocleanups.h

  This file is found in later versions of the libglib2.0-dev but not in
  version libglib2.0-dev 2.40.2-0ubuntu1 for 14.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1697079/+subscriptions

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

[Touch-packages] [Bug 1536204] Re: alsa-utils conflicts with bareos-bat

The conflict only needs to be resolved on one side, so by alsa-utils
being fixed the others are now "invalid"

** Changed in: bacula (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: bareos (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  alsa-utils conflicts with bareos-bat

Status in alsa-utils package in Ubuntu:
  Fix Released
Status in bacula package in Ubuntu:
  Invalid
Status in bareos package in Ubuntu:
  Invalid
Status in alsa-utils package in Debian:
  Fix Released

Bug description:
  dcarbone@paperone:~$ sudo aptitude install bareos-bconsole bareos-bat 
bareos-client bareos-tools
  bareos-bconsole è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-client è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-tools è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-bconsole è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-client è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-tools è già installato e si trova alla versione richiesta (14.2.6-2)
  I seguenti pacchetti NUOVI (NEW) saranno installati:
bareos-bat 
  0 pacchetti aggiornati, 1 installati, 0 da rimuovere e 0 non aggiornati.
  È necessario prelevare 0 B/508 kB di archivi. Dopo l'estrazione, verranno 
occupati 1.554 kB.
  (Lettura del database... 214782 file e directory attualmente installati.)
  Preparativi per estrarre .../bareos-bat_14.2.6-2_amd64.deb...
  Estrazione di bareos-bat (14.2.6-2)...
  dpkg: errore nell'elaborare l'archivio 
/var/cache/apt/archives/bareos-bat_14.2.6-2_amd64.deb (--unpack):
   tentata sovrascrittura di "/usr/share/man/man1/bat.1.gz" presente anche nel 
pacchetto alsa-utils 1.1.0-0ubuntu2
  dpkg-deb: errore: il sottoprocesso paste è stato terminato dal segnale (Pipe 
interrotta)
  Elaborazione dei trigger per doc-base (0.10.6)...
  Elaborazione dei trigger per man-db (2.7.5-1)...
  Si sono verificati degli errori nell'elaborazione:
   /var/cache/apt/archives/bareos-bat_14.2.6-2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Failed to perform requested operation on package.  Trying to recover:

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

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

[Touch-packages] [Bug 1536204] Re: alsa-utils conflicts with bareos-bat

I came by cleaning up long time dormant bugs, this is actually already
fixed in 1.1.0-2 and thereby >=Yakkety.

** Changed in: alsa-utils (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  alsa-utils conflicts with bareos-bat

Status in alsa-utils package in Ubuntu:
  Fix Released
Status in bacula package in Ubuntu:
  Invalid
Status in bareos package in Ubuntu:
  Invalid
Status in alsa-utils package in Debian:
  Fix Released

Bug description:
  dcarbone@paperone:~$ sudo aptitude install bareos-bconsole bareos-bat 
bareos-client bareos-tools
  bareos-bconsole è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-client è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-tools è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-bconsole è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-client è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-tools è già installato e si trova alla versione richiesta (14.2.6-2)
  I seguenti pacchetti NUOVI (NEW) saranno installati:
bareos-bat 
  0 pacchetti aggiornati, 1 installati, 0 da rimuovere e 0 non aggiornati.
  È necessario prelevare 0 B/508 kB di archivi. Dopo l'estrazione, verranno 
occupati 1.554 kB.
  (Lettura del database... 214782 file e directory attualmente installati.)
  Preparativi per estrarre .../bareos-bat_14.2.6-2_amd64.deb...
  Estrazione di bareos-bat (14.2.6-2)...
  dpkg: errore nell'elaborare l'archivio 
/var/cache/apt/archives/bareos-bat_14.2.6-2_amd64.deb (--unpack):
   tentata sovrascrittura di "/usr/share/man/man1/bat.1.gz" presente anche nel 
pacchetto alsa-utils 1.1.0-0ubuntu2
  dpkg-deb: errore: il sottoprocesso paste è stato terminato dal segnale (Pipe 
interrotta)
  Elaborazione dei trigger per doc-base (0.10.6)...
  Elaborazione dei trigger per man-db (2.7.5-1)...
  Si sono verificati degli errori nell'elaborazione:
   /var/cache/apt/archives/bareos-bat_14.2.6-2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Failed to perform requested operation on package.  Trying to recover:

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

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

[Touch-packages] [Bug 1681596] Re: UpgradeStatus only checks for ubuntu-release-upgrader upgrades

** Tags removed: rls-aa-incoming

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

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

Title:
  UpgradeStatus only checks for ubuntu-release-upgrader upgrades

Status in apport package in Ubuntu:
  Triaged

Bug description:
  In add_release_info of the generic ubuntu apport hook we can see the
  following:

  log = '/var/log/dist-upgrade/main.log'
  if os.path.exists(log):
  mtime = os.stat(log).st_mtime
  human_mtime = time.strftime('%Y-%m-%d', time.gmtime(mtime))
  delta = time.time() - mtime

  # Would be nice if this also showed which release was originally 
installed
  report['UpgradeStatus'] = 'Upgraded to %s on %s (%d days ago)' % 
(release_codename, human_mtime, delta / 86400)
  else:
  report['UpgradeStatus'] = 'No upgrade log present (probably fresh 
install)'

  UpgradeStatus doesn't take into consideration the possibility that
  people upgraded by editing their sources.list file and ran 'apt-get
  dist-upgrade', so saying it is "probably a fresh install" is wrong.
  Apport can up creating reports with a InstallationMedia of Precise,
  DistroRelease of Yakkety, but then a UpgradeStatus of "No upgrade log
  present..." which is wrong.

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

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

[Touch-packages] [Bug 1682154] Re: loginctl ignoring user given sessions IDs at command-line

** Tags removed: rls-aa-incoming

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

Title:
  loginctl ignoring user given sessions IDs at command-line

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Zesty:
  Triaged

Bug description:
  Kubuntu zesty, 232-21ubuntu2

  See upstream bug https://github.com/systemd/systemd/issues/5733 with
  patch attached.

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

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

[Touch-packages] [Bug 1686803] Re: sudo returns exit code 0 if child is killed with SIGTERM

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

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

Title:
  sudo returns exit code 0 if child is killed with SIGTERM

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Triaged
Status in sudo source package in Artful:
  Triaged

Bug description:
  Please backport upstream sudo changeset 10917:50b988d0c97f "The fix
  for Bug #722 contained a typo/thinko that resulted in the" to xenial,
  yakkety, and zesty versions of sudo.

  This will fix a regression documented by this upstream bug report:
  https://bugzilla.sudo.ws/show_bug.cgi?id=784

  sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is
  running is killed by a signal, sudo will" introduced a regression
  where the exit status is always 0 when a command is killed by a signal
  other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1

  This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f
  "The fix for Bug #722 contained a typo/thinko that resulted in the".
  https://www.sudo.ws/repos/sudo/rev/50b988d0c97f

  trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo
  based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty
  sudo based off 1.8.19 need the fix.

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

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

[Touch-packages] [Bug 1686803] Re: sudo returns exit code 0 if child is killed with SIGTERM

** Also affects: sudo (Ubuntu Artful)
   Importance: Medium
 Assignee: Balint Reczey (rbalint)
   Status: Triaged

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

Title:
  sudo returns exit code 0 if child is killed with SIGTERM

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Triaged
Status in sudo source package in Artful:
  Triaged

Bug description:
  Please backport upstream sudo changeset 10917:50b988d0c97f "The fix
  for Bug #722 contained a typo/thinko that resulted in the" to xenial,
  yakkety, and zesty versions of sudo.

  This will fix a regression documented by this upstream bug report:
  https://bugzilla.sudo.ws/show_bug.cgi?id=784

  sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is
  running is killed by a signal, sudo will" introduced a regression
  where the exit status is always 0 when a command is killed by a signal
  other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1

  This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f
  "The fix for Bug #722 contained a typo/thinko that resulted in the".
  https://www.sudo.ws/repos/sudo/rev/50b988d0c97f

  trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo
  based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty
  sudo based off 1.8.19 need the fix.

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

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

[Touch-packages] [Bug 1531703] Re: virsh save doesn't work for vm with hdd image in non-default location, AppArmor-related error

** No longer affects: apparmor (Ubuntu)

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

Title:
  virsh save doesn't work for vm with hdd image in non-default location,
  AppArmor-related error

Status in libvirt package in Ubuntu:
  Incomplete

Bug description:
  virsh save does work for vm located in /var/lib/libvirt/images, but doesn't 
work for vm located for example in /mnt/storage/data/limages
  Error message:
  ~$ LANG=C virsh save owncloud /mnt/storage/data/images/owncloud.dump
  error: Failed to save domain owncloud to 
/mnt/storage/data/images/owncloud.dump
  error: внутренняя ошибка: не удалось обновить профиль AppArmor 
«libvirt-b9f02241-f8a7-4c11-86de-5eccbdff6511»

  Translation:
  error: internal error: unable to update AppArmor profile  
«libvirt-b9f02241-f8a7-4c11-86de-5eccbdff6511»

  I tried to dumpxml and then define it again from xml, but that doesn't help.
  Ubuntu Server 15.10.

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

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

[Touch-packages] [Bug 1689495] Re: unattended-upgrade crashed with AttributeError in _write(): 'NoneType' object has no attribute 'write'

Robie - Do you have any more information about how this crash occurs and
its effects?

** Tags removed: rls-aa-incoming

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  unattended-upgrade crashed with AttributeError in _write(): 'NoneType'
  object has no attribute 'write'

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  This happened after upgrading it to Artful.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.93.1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu6
  Architecture: amd64
  CrashCounter: 1
  Date: Tue May  9 08:20:24 2017
  ExecutablePath: /usr/bin/unattended-upgrade
  InstallationDate: Installed on 2017-05-05 (3 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/unattended-upgrade -d 3
  ProcEnviron:
   LANGUAGE=en_IE:en
   PATH=(custom, no user)
   LANG=en_IE.UTF-8
  PythonArgs: ['/usr/bin/unattended-upgrade', '-d', '3']
  SourcePackage: unattended-upgrades
  Title: unattended-upgrade crashed with AttributeError in _write(): 'NoneType' 
object has no attribute 'write'
  UpgradeStatus: Upgraded to artful on 2017-05-05 (3 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1697072] [NEW] package libssl1.0.0:amd64 1.0.2g-1ubuntu9.3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

2017-06-09 Thread Jean Louis Schmitz

Public bug reported:

imposible via synaptic either

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libssl1.0.0:amd64 1.0.2g-1ubuntu9.3
Uname: Linux 4.9.10-040910-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu8.3
AptOrdering:
 libssl1.0.0:i386: Install
 libssl1.0.0:amd64: Install
 openssl:amd64: Install
 libpam-cgfs:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Jun  9 14:10:49 2017
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1.1
 apt  1.3.5
SourcePackage: openssl
Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu9.3 failed to install/upgrade: 
el subproceso instalado el script post-installation devolvió el código de 
salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu9.3 failed to install/upgrade:
  el subproceso instalado el script post-installation devolvió el código
  de salida de error 1

Status in openssl package in Ubuntu:
  New

Bug description:
  imposible via synaptic either

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu9.3
  Uname: Linux 4.9.10-040910-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  AptOrdering:
   libssl1.0.0:i386: Install
   libssl1.0.0:amd64: Install
   openssl:amd64: Install
   libpam-cgfs:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jun  9 14:10:49 2017
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu9.3 failed to install/upgrade: 
el subproceso instalado el script post-installation devolvió el código de 
salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1656830] Re: Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved

** Also affects: systemd (Ubuntu Artful)
   Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
   Status: Confirmed

** Tags removed: rls-aa-incoming

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

Title:
  Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved

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

Bug description:
  This is something new in Ubuntu 17.04. Whenever I boot up or upon
  returning from sleep, I don't have DNS resolution available. What I
  have to do is go and shutdown systemd-resolved (sudo service systemd-
  resolved stop) and edit /etc/resolv.conf to point to 192.168.1.1 (my
  router) instead of 127.0.0.53. Then everything works peachy. Otherwise
  any DNS resolution attempt will result in SERVFAIL.

  Since this is a major issue out of the box and I don't see any other
  bug report on this yet, I wanted to report it. This happens both on my
  laptop and my desktop PC, so it's not something strange on a single
  machine, but since no one else is complaining about it yet, it may be
  related to my network configuration. My router forwards DNS requests
  to an ODROID C2 on the same subnet, which then does the DNS resolution
  via dnsmasq. Dnsqmasq is set up to forward the requests to multiple
  DNS servers and respond with whichever one was fastest.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-8
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Jan 16 08:51:43 2017
  InstallationDate: Installed on 2017-01-08 (7 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170107)
  MachineType: LENOVO 7675CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=b64995c7-1fd6-405b-b7ee-de3e56fe0617 ro quiet splash zswap.enabled=1 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7NETC2WW (2.22 )
  dmi.board.name: 7675CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn7675CTO:pvrThinkPadX61:rvnLENOVO:rn7675CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7675CTO
  dmi.product.version: ThinkPad X61
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1656830] Re: Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved

We believe this is most likely a duplicate of bug #1682499 which was
fixed in systemd 232-21ubuntu3.  If you can still reproduce this problem
after upgrading to the zesty-updates version of systemd, please reopen.

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

Title:
  Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved

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

Bug description:
  This is something new in Ubuntu 17.04. Whenever I boot up or upon
  returning from sleep, I don't have DNS resolution available. What I
  have to do is go and shutdown systemd-resolved (sudo service systemd-
  resolved stop) and edit /etc/resolv.conf to point to 192.168.1.1 (my
  router) instead of 127.0.0.53. Then everything works peachy. Otherwise
  any DNS resolution attempt will result in SERVFAIL.

  Since this is a major issue out of the box and I don't see any other
  bug report on this yet, I wanted to report it. This happens both on my
  laptop and my desktop PC, so it's not something strange on a single
  machine, but since no one else is complaining about it yet, it may be
  related to my network configuration. My router forwards DNS requests
  to an ODROID C2 on the same subnet, which then does the DNS resolution
  via dnsmasq. Dnsqmasq is set up to forward the requests to multiple
  DNS servers and respond with whichever one was fastest.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-8
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Jan 16 08:51:43 2017
  InstallationDate: Installed on 2017-01-08 (7 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170107)
  MachineType: LENOVO 7675CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=b64995c7-1fd6-405b-b7ee-de3e56fe0617 ro quiet splash zswap.enabled=1 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7NETC2WW (2.22 )
  dmi.board.name: 7675CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn7675CTO:pvrThinkPadX61:rvnLENOVO:rn7675CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7675CTO
  dmi.product.version: ThinkPad X61
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1696989] Re: package libpam-cgfs 2.0.7-0ubuntu1~17.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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

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

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

Title:
  package libpam-cgfs 2.0.7-0ubuntu1~17.04.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in debconf package in Ubuntu:
  Confirmed
Status in lxcfs package in Ubuntu:
  Confirmed

Bug description:
  Error occurred while updating from terminal:
  W: APT had planned for dpkg to do more than it reported back (40 vs 44).
 Affected packages: libpam-cgfs:amd64

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libpam-cgfs 2.0.7-0ubuntu1~17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri Jun  9 14:49:06 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-03-16 (84 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: lxcfs
  Title: package libpam-cgfs 2.0.7-0ubuntu1~17.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (52 days ago)

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

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

[Touch-packages] [Bug 1687122] Re: /usr/bin/add-apt-repository:OSError:/usr/bin/add-apt-repository@168:add_source_from_shortcut:/usr/bin/add-apt-repository@172

** Changed in: software-properties (Ubuntu)
Milestone: None => ubuntu-17.06

** Also affects: software-properties (Ubuntu Artful)
   Importance: Medium
 Assignee: Dimitri John Ledkov (xnox)
   Status: New

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

Title:
  /usr/bin/add-apt-repository:OSError:/usr/bin/add-apt-
  repository@168:add_source_from_shortcut:/usr/bin/add-apt-
  repository@172

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Artful:
  New

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

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

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

[Touch-packages] [Bug 1696989] Re: package libpam-cgfs 2.0.7-0ubuntu1~17.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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

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

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

Title:
  package libpam-cgfs 2.0.7-0ubuntu1~17.04.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in debconf package in Ubuntu:
  Confirmed
Status in lxcfs package in Ubuntu:
  Confirmed

Bug description:
  Error occurred while updating from terminal:
  W: APT had planned for dpkg to do more than it reported back (40 vs 44).
 Affected packages: libpam-cgfs:amd64

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libpam-cgfs 2.0.7-0ubuntu1~17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri Jun  9 14:49:06 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-03-16 (84 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: lxcfs
  Title: package libpam-cgfs 2.0.7-0ubuntu1~17.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (52 days ago)

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Also affects: network-manager (Ubuntu Artful)
   Importance: Undecided
   Status: Confirmed

** Also affects: systemd (Ubuntu Artful)
   Importance: High
 Assignee: Dimitri John Ledkov (xnox)
   Status: Confirmed

** Tags removed: rls-aa-incoming

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1611363] Re: vim.gtk3 crashes frequently with SIGSEGV in ffi_call_unix64()

** Tags removed: rls-aa-incoming

** Also affects: unity-gtk-module (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  vim.gtk3 crashes frequently with SIGSEGV in ffi_call_unix64()

Status in vim:
  Confirmed
Status in unity-gtk-module package in Ubuntu:
  New
Status in vim package in Ubuntu:
  Confirmed
Status in unity-gtk-module source package in Xenial:
  New
Status in vim source package in Xenial:
  Confirmed

Bug description:
  Hi, vim-gtk3 crashes so often on my system that it's borderline unusable.
  My system is a clean install of Ubuntu 16.04. I also (temporarily) renamed my 
customized ~/.vimrc and ~/.vim. My system is up-to-date as of today 
(2016-08-09); installed vim-gtk3 is 2:7.4.1689-3ubuntu1.1.

  The crash happens only (but very frequently, not always) when I launch
  gvim, either by calling it from a shell or by double-clicking a file
  in Nautilus. Note that the crash is independent of whether I'm opening
  a file or not. (At least I tried both variations from the terminal.)

  There's also a report on vim's bugtracker, but since unity appears in
  the backtrace, the consensus is that it's probably Ubuntu-specific.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: vim-gtk3 2:7.4.1689-3ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  9 14:34:31 2016
  ExecutablePath: /usr/bin/vim.gtk3
  InstallationDate: Installed on 2016-07-10 (29 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: gvim -f 
/home/username/Documents/schoul/2016/1G-TODO/01-systemes-equations-TODO/chap01_systemes-equations-NOTES.tex
  Signal: 11
  SourcePackage: vim
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libunity-gtk3-parser.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: vim.gtk3 crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1624644] Re: Unable to automatically remove packages that become unused in conjunction with updating by other software

** Also affects: unattended-upgrades (Ubuntu Artful)
   Importance: High
   Status: Confirmed

** Tags removed: rls-aa-incoming

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

Title:
  Unable to automatically remove packages that become unused in
  conjunction with updating by other software

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in unattended-upgrades source package in Artful:
  Confirmed

Bug description:
  When using default settings for unattended-upgrades i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false"; 
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; 
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  U-U is unable to remove packages that become unused in conjunction with 
updating by other software such as update-manager or apt full-upgrade. This is 
because U-U compares the list of unneeded packages before and after it upgrades 
packages to detect which packages are new unused ones.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1561647] Re: No mokutil prompt triggered when installing from additional drivers

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

** This bug has been marked a duplicate of bug 1679784
   Changing from Xorg video driver to NVIDIA driver using Software & Updates 
does not display debconf prompt

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

Title:
  No mokutil prompt triggered when installing from additional drivers

Status in software-properties package in Ubuntu:
  New

Bug description:
  STEPS:
  1. On a system with binary blobs
  2. Install xenial daily on a secureboot system
  3. In dash type additional
  4. Click on additional drivers
  5. Install the binary drivers

  EXPECTED:
  Like in the installer or using apt install (binary blob) I expect to see a 
warning telling me in disable secureboot

  ACTUAL:
  I get nothing and the binary modules are installed.

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

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

[Touch-packages] [Bug 1593489] Re: resolvconf postrm is broken, purge breaks DNS

** Changed in: resolvconf (Ubuntu Zesty)
   Importance: High => Low

** Tags added: rls-aa-notfixing

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

Title:
  resolvconf postrm is broken, purge breaks DNS

Status in resolvconf package in Ubuntu:
  Confirmed
Status in resolvconf source package in Xenial:
  New
Status in resolvconf source package in Yakkety:
  New
Status in resolvconf source package in Zesty:
  Confirmed
Status in resolvconf source package in Artful:
  New

Bug description:
  apt-get remove resolvconf incorrectly leaves a symlink from
  /etc/resolv.conf to ../run/resolvconf/resolv.conf.  apt-get purge
  resolvconf leaves that symlink with no target, so DNS is broken.

  The problem is in postrm: it's examining /etc/resolv.conf to see if
  it's a link to /run/resolvconf/resolv.conf, but it's a relative link
  to ../run/resolvconf/resolv.conf, so the comparison fails, resulting
  in the failures above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun 16 23:52:41 2016
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1695638] Re: package krb5-locales 1.15-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-06-09 Thread Andreas Hasenack

Hello,

could you please try reinstalling the package:

sudo apt install --reinstall krb5-locales


If that doesn't help, then remove it and install it again:

sudo dpkg --remove --force-remove-reinstreq krb5-locales

sudo apt-get install krb5-locales

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

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

Title:
  package krb5-locales 1.15-1 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:
  Incomplete

Bug description:
  sometimes the system hangs on

  and its not activating an adapter device ..

  also having a problem when trying to upload ubuntu software .

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: krb5-locales 1.15-1
  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
  AptOrdering:
   firefox:amd64: Install
   firefox-locale-ar:amd64: Install
   firefox-locale-en:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May 27 18:14:20 2017
  Dependencies:
   
  DuplicateSignature:
   package:krb5-locales:1.15-1
   Processing triggers for bamfdaemon (0.5.3+17.04.20170406-0ubuntu1) ...
   Rebuilding /usr/share/applications/bamf-2.index...
   dpkg: error processing package krb5-locales (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-03-16 (78 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: krb5
  Title: package krb5-locales 1.15-1 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to zesty on 2017-05-16 (17 days ago)

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

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

[Touch-packages] [Bug 1697011] Re: package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade: package libssl-doc is not ready for configuration cannot configure (current status 'half-installed')

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

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

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

Title:
  package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  package libssl-doc is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  I tried to update by the ubuntu software and the OS system update did
  not finished. I restarted the pc and ran the command: sudo apt-get -f
  install and showed the error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl-doc 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libssl-doc: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jun  9 12:11:10 2017
  Dependencies:
   
  DpkgTerminalLog:
   dpkg: error processing package libssl-doc (--configure):
package libssl-doc is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libssl-doc is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-04 (36 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
package libssl-doc is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1691096] Re: mysql in lxd fails to start with systemd 233: failed at step KEYRING

** Changed in: systemd (Ubuntu Artful)
Milestone: ubuntu-17.10 => ubuntu-17.07

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

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

Title:
  mysql in lxd fails to start with systemd 233: failed at step KEYRING

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Artful:
  Triaged

Bug description:
  artful unprivileged container on a xenial host

  xnox hinted that
  
https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7
  might be related

  With systemd 233, mysql-server-5.7 in an artful lxd unprivileged
  container fails to start:

    Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
  (code=exited, status=237/KEYRING)

  May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set 
invocation ID on control group /system.slice/mysql.service, ignoring: Operation 
not permitted
  (...)
  May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step 
KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied

  Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We 
start with systemd-232 in the artful lxd:
  ubuntu@intense-sunbeam:~$ apt-cache policy systemd
  systemd:
    Installed: 232-21ubuntu3
    Candidate: 233-6ubuntu1
    Version table:
   233-6ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
   *** 232-21ubuntu3 100
  100 /var/lib/dpkg/status

  Then we install mysql-server-5.7:
  ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7
  ...
  Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ...
  update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf 
(my.cnf) in auto mode
  Renaming removed key_buffer and myisam-recover options (if present)
  Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → 
/lib/systemd/system/mysql.service.
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  Processing triggers for systemd (232-21ubuntu3) ...

  Which starts just fine:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  ...

  We then upgrade systemd:
  ubuntu@intense-sunbeam:~$ sudo apt install systemd
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    libpam-systemd libsystemd0
  (...)
  Setting up libpam-systemd:amd64 (233-6ubuntu1) ...

  mysql is still running:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  (...)

  But restarting mysql fails:
  ubuntu@intense-sunbeam:~$ sudo service mysql restart
  Job for mysql.service failed because the control process exited with error 
code.
  See "systemctl  status mysql.service" and "journalctl  -xe" for details.
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2)

  More logs attached.

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

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

[Touch-packages] [Bug 1691096] Re: mysql in lxd fails to start with systemd 233: failed at step KEYRING

** Changed in: systemd (Ubuntu Artful)
 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/1691096

Title:
  mysql in lxd fails to start with systemd 233: failed at step KEYRING

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Artful:
  Triaged

Bug description:
  artful unprivileged container on a xenial host

  xnox hinted that
  
https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7
  might be related

  With systemd 233, mysql-server-5.7 in an artful lxd unprivileged
  container fails to start:

    Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
  (code=exited, status=237/KEYRING)

  May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set 
invocation ID on control group /system.slice/mysql.service, ignoring: Operation 
not permitted
  (...)
  May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step 
KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied

  Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We 
start with systemd-232 in the artful lxd:
  ubuntu@intense-sunbeam:~$ apt-cache policy systemd
  systemd:
    Installed: 232-21ubuntu3
    Candidate: 233-6ubuntu1
    Version table:
   233-6ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
   *** 232-21ubuntu3 100
  100 /var/lib/dpkg/status

  Then we install mysql-server-5.7:
  ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7
  ...
  Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ...
  update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf 
(my.cnf) in auto mode
  Renaming removed key_buffer and myisam-recover options (if present)
  Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → 
/lib/systemd/system/mysql.service.
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  Processing triggers for systemd (232-21ubuntu3) ...

  Which starts just fine:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  ...

  We then upgrade systemd:
  ubuntu@intense-sunbeam:~$ sudo apt install systemd
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    libpam-systemd libsystemd0
  (...)
  Setting up libpam-systemd:amd64 (233-6ubuntu1) ...

  mysql is still running:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  (...)

  But restarting mysql fails:
  ubuntu@intense-sunbeam:~$ sudo service mysql restart
  Job for mysql.service failed because the control process exited with error 
code.
  See "systemctl  status mysql.service" and "journalctl  -xe" for details.
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2)

  More logs attached.

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

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

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

** Tags added: rls-aa-notfixing

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Trusty:
  Confirmed
Status in isc-dhcp source package in Xenial:
  Confirmed
Status in isc-dhcp source package in Yakkety:
  Confirmed
Status in isc-dhcp source package in Zesty:
  Confirmed
Status in isc-dhcp source package in Artful:
  In Progress
Status in isc-dhcp package in Debian:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

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

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

[Touch-packages] [Bug 1697068] [NEW] package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvo

2017-06-09 Thread Petrus Its

Public bug reported:

Don't know.

Fouten gevonden tijdens verwerken van:
 openssl
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssl 1.0.2g-1ubuntu4.8
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: Fri Jun  9 20:51:04 2017
ErrorMessage: pakket verkeert in een heel slechte en inconsistente staat; u zou 
het  opnieuw moeten installeren alvorens het te configureren.
InstallationDate: Installed on 2016-01-24 (502 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
Title: package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakket 
verkeert in een heel slechte en inconsistente staat; u zou het  opnieuw moeten 
installeren alvorens het te configureren.
UpgradeStatus: Upgraded to xenial on 2017-01-07 (153 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakket
  verkeert in een heel slechte en inconsistente staat; u zou het
  opnieuw moeten installeren alvorens het te configureren.

Status in openssl package in Ubuntu:
  New

Bug description:
  Don't know.

  Fouten gevonden tijdens verwerken van:
   openssl
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.8
  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: Fri Jun  9 20:51:04 2017
  ErrorMessage: pakket verkeert in een heel slechte en inconsistente staat; u 
zou het  opnieuw moeten installeren alvorens het te configureren.
  InstallationDate: Installed on 2016-01-24 (502 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakket 
verkeert in een heel slechte en inconsistente staat; u zou het  opnieuw moeten 
installeren alvorens het te configureren.
  UpgradeStatus: Upgraded to xenial on 2017-01-07 (153 days ago)

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

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

[Touch-packages] [Bug 1629632] Re: Sap driver initialization failed, sap-server: Operation not permitted

2017-06-09 Thread groby

... and on my Lubuntu 17.04

# journalctl -b | grep bluetoothd
[...]
Jun 09 20:31:34 acer bluetoothd[1986]: Failed to obtain handles for "Service 
Changed" characteristic
Jun 09 20:31:34 acer bluetoothd[1986]: Sap driver initialization failed.
Jun 09 20:31:34 acer bluetoothd[1986]: sap-server: Operation not permitted (1)
[...]

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

Title:
  Sap driver initialization failed, sap-server: Operation not permitted

Status in bluez package in Ubuntu:
  Confirmed
Status in bluez package in Debian:
  New

Bug description:
  Hi,

  here are are messages from the bluetooth daemon:

  $ journalctl -b | grep bluetoothd
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 
initialized
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for 
"Service Changed" characteristic
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed.
  Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted 
(1)

  There are at least 2 errors concerning:
   - handles
   - Sap driver/server

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Oct  2 09:59:43 2016
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency 
root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:85:DE:57:27:6F  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:1974 acl:0 sco:0 events:132 errors:0
TX bytes:6033 acl:0 sco:0 commands:132 errors:0

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

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

[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

2017-06-09 Thread Andreas Hasenack

You can try:

sudo apt install --reinstall libgssapi-krb5-2:i386

(I suspect the above won't work either, but it's worth a try)


If that doesn't fix it, then, from that askubuntu question/answer:

sudo dpkg --remove --force-remove-reinstreq libgssapi-krb5-2:i386

sudo apt install libgssapi-krb5-2:i386

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

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 1697054] Re: vim-gtk3 should not depend on libruby and hold ruby in main

** Changed in: vim (Ubuntu)
Milestone: None => ubuntu-17.10

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

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

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

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

Title:
  vim-gtk3 should not depend on libruby and hold ruby in main

Status in vim package in Ubuntu:
  In Progress

Bug description:
  Currently ruby is in main not because it's seeded, but because it's a
  runtime dependency of vim-gtk3.  We don't otherwise support ruby and
  should drop this dependency from vim-gtk3.

  vim-gtk can keep this dependency since it's in main.

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

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

[Touch-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root

Checking the issue that was referred shows it was handled and fixed in
1. Kernel 
https://github.com/torvalds/linux/commit/37091fdd831f28a6509008542174ed324dd645bc
which is 4.6 and thereby fixed in >=Yakkety.
2. Systemd https://github.com/systemd/systemd/pull/2422 that went into systemd 
230 which also means part of >=Yakkety.

I'm filing bug tasks for systemd and kernel to check and maybe consider
for Xenial

** Package changed: initramfs-tools (Ubuntu) => linux (Ubuntu)

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

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

** Changed in: nbd (Ubuntu)
   Status: Confirmed => Invalid

** Also affects: nbd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** No longer affects: nbd (Ubuntu Xenial)

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

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

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

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1 
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
while [ -z "${FSTYPE}" ]; do
FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

# Run failure hooks, hoping one of them can fix up the system
# and we can restart the wait loop.  If they all fail, abort
# and move on to the panic handler and shell.
if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
break
fi
done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

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

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

[Touch-packages] [Bug 1696402] Re: chroot configuration strictly depends on overlayfs

2017-06-09 Thread Leo Arias

** Description changed:

  The kernel changed the module name from overlayfs to overlay, this needs
  to be taken into consideration when creating the chroot.
+ 
+ [Impact]
+ 
+ When trying to create the chroot, it fails like this:
+ Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
+ E: 10mount: mount: wrong fs type, bad option, bad superblock on 
click-ubuntu-sdk-14.04-armhf,
+ E: 10mount:missing codepage or helper program, or other error
+ E: 10mount: 
+ E: 10mount:In some cases useful info is found in syslog - try
+ E: 10mount:dmesg | tail or so.
+ E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot 
setup failed: stage=setup-start
+ Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env 
DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little 
DEB_BUILD_ARCH_ABI
+ =base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu 
DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux 
DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
+ ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu 
DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf 
DEB_BUILD_ARCH_BITS=
+ 64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 
DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu 
DEB_TARGET_GNU_TYPE=arm-linux-gn
+ ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm 
DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm 
DEB_TARGET_ARCH_CPU=arm DEB_B
+ UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf 
DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little 
DEB_HOST_ARCH
+ _CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
+ ERROR
+ 
+ This makes the autopkgtests fail, so it's blocking #1693226.
+ 
+ [Test Case]
+ 
+ Run the click autopkgtests in artful.
+ Check that there are no errors related to the wrong fs type.
+ 
+ [Regression Potential]
+ 
+ Fixing this for artful could make it fail in previous versions.
+ However, this was found by the autopkgtests, so as long as the chroot tests 
pass in the other revisions the fix is correct.
+ 
+ [Other Info]
+ 
+ Click is now longer in active development. These tests were failing for
+ a long time. In here we are just trying to make a small change on the
+ name of the python module so it doesn't conflict with python3-click
+ which is in active development and needed by snapcraft in #1692102.

** Description changed:

  The kernel changed the module name from overlayfs to overlay, this needs
  to be taken into consideration when creating the chroot.
  
  [Impact]
  
  When trying to create the chroot, it fails like this:
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  E: 10mount: mount: wrong fs type, bad option, bad superblock on 
click-ubuntu-sdk-14.04-armhf,
  E: 10mount:missing codepage or helper program, or other error
- E: 10mount: 
+ E: 10mount:
  E: 10mount:In some cases useful info is found in syslog - try
  E: 10mount:dmesg | tail or so.
  E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot 
setup failed: stage=setup-start
  Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env 
DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little 
DEB_BUILD_ARCH_ABI
  =base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu 
DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux 
DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
  ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu 
DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf 
DEB_BUILD_ARCH_BITS=
  64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 
DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu 
DEB_TARGET_GNU_TYPE=arm-linux-gn
  ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm 
DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm 
DEB_TARGET_ARCH_CPU=arm DEB_B
  UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf 
DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little 
DEB_HOST_ARCH
  _CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
  ERROR
  
- This makes the autopkgtests fail, so it's blocking #1693226.
+ This makes the autopkgtests fail, so it's blocking bug #1693226.
  
  [Test Case]
  
  Run the click autopkgtests in artful.
  Check that there are no errors related to the wrong fs type.
  
  [Regression Potential]
  
  Fixing this for artful could make it fail in previous versions.
  However, this was found by the autopkgtests, so as long as the chroot tests 
pass in the other revisions the fix is correct.
  
  [Other Info]
  
  Click is now longer in active development. These tests were failing for
  a long time. In here we are just trying to make a small change on the
  name of the python module so it doesn't conflict with python3-click
- which is

[Touch-packages] [Bug 1493067] Re: ssh-copy-id fails by making assumptions about the default shell on the remote machine

Discussed:
https://github.com/fish-shell/fish-shell/issues/2292

Fixed in:
https://github.com/fish-shell/fish-shell/issues/150

So TL;DR it was more seen as an issue in fish and should work in recent 
versions of fish now.
Reassigning to fish due to that.

The discussions and fixes in fish are very noisy and complex - it would
be great if one could test that on a newer release.

** Bug watch added: github.com/fish-shell/fish-shell/issues #2292
   https://github.com/fish-shell/fish-shell/issues/2292

** Bug watch added: github.com/fish-shell/fish-shell/issues #150
   https://github.com/fish-shell/fish-shell/issues/150

** Package changed: openssh (Ubuntu) => fish (Ubuntu)

** Also affects: fish (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

Title:
  ssh-copy-id fails by making assumptions about the default shell on the
  remote machine

Status in fish package in Ubuntu:
  Fix Released
Status in fish source package in Xenial:
  Confirmed

Bug description:
  ssh-copy-id  10.200.17.160
  /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to 
filter out any that are already installed
  /usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are 
prompted now it is to install the new keys
  foo@10.200.17.160's password: 
  fish: Expected a command name, got token of type “Run job in background”. Did 
you mean “COMMAND; and COMMAND”? See the help section for the “and” builtin 
command by typing “help and”.
  Standard input:   mkdir -p .ssh && cat >> .ssh/authorized_keys || 
exit 1 ;
 ^

  I expected to be able to copy my key.

  An approach I see is for ssh-copy-id to run bash -c 

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openssh-client 1:6.7p1-5ubuntu1.3
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep  7 15:56:44 2015
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.7p1-5ubuntu1.3
  SSHClientVersion: OpenSSH_6.7p1 Ubuntu-5ubuntu1.3, OpenSSL 1.0.1f 6 Jan 2014
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1697054] [NEW] vim-gtk3 should not depend on libruby and hold ruby in main

Public bug reported:

Currently ruby is in main not because it's seeded, but because it's a
runtime dependency of vim-gtk3.  We don't otherwise support ruby and
should drop this dependency from vim-gtk3.

vim-gtk can keep this dependency since it's in main.

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

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

Title:
  vim-gtk3 should not depend on libruby and hold ruby in main

Status in vim package in Ubuntu:
  New

Bug description:
  Currently ruby is in main not because it's seeded, but because it's a
  runtime dependency of vim-gtk3.  We don't otherwise support ruby and
  should drop this dependency from vim-gtk3.

  vim-gtk can keep this dependency since it's in main.

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

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

[Touch-packages] [Bug 1697052] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-06-09 Thread Chandan Kumar Rath

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

Public bug reported:

crashed during software update

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Wed Jun  7 06:06:58 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-06 (3 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  crashed during software update

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jun  7 06:06:58 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-06 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1697052] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  crashed during software update

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jun  7 06:06:58 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-06 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1603620] Re: Package lists are not updated before Unattended upgrades runs automatically.

2017-06-09 Thread Julian Andres Klode

Fix released, AFAP. There's still some issues on resume only machines
that need to be sorted out, but the plan is to deal with that later (it
needs a custom online waiting tool to be written).

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Package lists are not updated before Unattended upgrades runs
  automatically.

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  Newest kernel available currently is 4.4.0-31-generic, but

  $ linux-version list
  4.2.0-38-generic
  4.4.0-24-generic
  4.4.0-28-generic

  `apt-get dist-upgrade` does not upgrade kernel either, unless I run
  `apt-get update` first.

  I wonder why kernel was not upgraded 2016-07-16 morning.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jul 16 11:40:07 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (237 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (21 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "0";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-02-15T22:39:19.560937
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2016-06-24T18:13:45.181749

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

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

[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps

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

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Committed
Status in qtbase-opensource-src source package in Yakkety:
  Confirmed

Bug description:
  Impact
  ==

  This affects all Qt applications on Unity and other desktops which use
  global menu, either via appmenu-qt5 or via native implementation on
  Yakkety.

  Any shortcut is not working if the corresponding action is attached
  only to the menubar (i.e. and not also to the toolbar). It can be
  reproduced with almost any application by removing the toolbar (right-
  clicking on it and deselecting it).

  Test Case
  =

  * Open Qt Assistant;
  * Press Ctrl+T (this action is not on the toolbar).

  Expected: a new tab should be opened. Current result: nothing happens.

  In Yakkety the fix should work both with and without appmenu-qt5.

  Proposed Fix
  

  The proposed fix is a backport of the upstream fix at
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594.

  Actually just the qshortcut.cpp part would be sufficient, but the
  other parts make sure it plays fine together with https://cgit.kde.org
  /plasma-integration.git/commit/?id=aef74e97e2ed462a.

  Regression Potential
  

  The fix is in Zesty for 1½ months now (in upstream even longer), and
  so far nobody complained. People have verified that the fix works (see
  comment #63).

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions

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

[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"

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

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

Title:
Please consider SRU of "xcb: Compress mouse motion and touch update
events"

Status in qtbase-opensource-src package in Ubuntu:
Fix Released
Status in qtbase-opensource-src source package in Xenial:
Fix Committed

Bug description:
Mouse event compression stopped working in Qt 5, a regression from Qt
4:

https://bugreports.qt.io/browse/QTBUG-40889

The bug was fixed in Qt 5.6 https://codereview.qt-
project.org/#/c/126136/ where the fix has been thoroughly tested by
now.

Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a
backport of the 5.6 patch (only one trivial hunk failed, which was
easily fixed).

[Impact]

The bug affects any program that relies on the event compression Qt
normally performs. For example, VTK programs (ParaView, Tomviz, ...)
do their rendering in response to mouse events during camera
movements, and with event compression at the Qt level suddenly gone,
camera movements become very slow, since the application is now
flooded with mouse events and the rendering lags behind.

The problem is not limited to these programs however; it can be
observed by simply putting two regular, slightly slow-to-render,
widgets into a QSplitter and moving the splitter handle. The result is
a syrup-like experience as the widgets try to keep up with the
onslaught of resize events due to the lack of mouse event compression.

[Test Case]

The attached test application can be used to check if event
compression is functioning. It performs some artificial work on each
mouse move and prints a message. Click and drag the mouse a little.
After releasing the mouse, you'll notice that the printouts keeps
coming for quite a while, as the program is catching up with the flood
of events.

With the attached patch (and with Qt 4), the problem is gone - the
mouse event stream is compressed and the printouts are no longer
lagging behind.

[Regression Potential]

There's a small risk that some applications have made workarounds for
the faulty behavior, and that unwanted behavior is introduced if this
bug is fixed. But chances are high that such workarounds will keep
working, as the obvious workaround is to do timer based rendering
instead of event based. The workarounds will then simply become
unnecessary, but shouldn't cause problems.

I'm asking for someone to nominate this bug for an SRU of 16.04 LTS.

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

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

[Touch-packages] [Bug 1655181] Re: P9 support in binutils

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

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

Title:
  P9 support in binutils

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Committed

Bug description:
  [SRU Justification]
  Hardware enablement of new P9 architecture on 16.04 LTS

  [Test case]
  Verify that the binutils testsuite still passes.  This requires manual review 
of the build logs.

  [Regression potential]
  One of the patches changes the behavior around handling of undefined weak 
symbols on ppc64el as a whole.  This behavior change could cause regressions on 
code built for existing ppc64el targets.  This is unlikely because nothing 
should be relying on the current behavior, and this is an upstream patch driven 
by the architecture owner.

  One of the patches changes the set of assembly mnemonics available for
  POWER9 opcodes.  This should have no impact because nothing should be
  relying on the not-yet-finalized P9 support in xenial.

  
  The upstream binutils (2.27 and trunk) is almost complete for POWER9, but 
unfortunately the changes expected to land in DD2 hardware have not yet been 
set in stone.  With that said, the remaining changes are fairly small and will 
only affect user space; there are no kernel dependencies on the unresolved 
architecture changes.

  == Comment: #3 - Peter E. Bergner  - 2016-11-01 10:43:16 
==
  Complete POWER9 support is upstream and exists in trunk and the binutils 2.27 
and 2.26 release branches.

  == Comment: #4 - Breno Henrique Leitao  - 2016-11-21 
12:45:53 ==
  (In reply to comment #3)
  > Complete POWER9 support is upstream and exists in trunk and the binutils
  > 2.27 and 2.26 release branches.

  Binutils version 2.27 is already in Ubuntu 17.04. Is there anything
  else required?

  == Comment: #5 - William J. Schmidt  - 2016-11-21 
13:32:50 ==
  (In reply to comment #4)
  > (In reply to comment #3)
  > > Complete POWER9 support is upstream and exists in trunk and the binutils
  > > 2.27 and 2.26 release branches.
  >
  > Binutils version 2.27 is already in Ubuntu 17.04. Is there anything else
  > required?

  Well, as long as they pick up the backported fixes, nothing else is
  required.  That's what this feature is there to ensure.

  == Comment: #6 - Breno Henrique Leitao  - 2016-11-24 
06:52:51 ==
  Hi,

  > Well, as long as they pick up the backported fixes, nothing else is
  > required.  That's what this feature is there to ensure.

  Do you know, at this time, which are the fixes that will be requested
  to be backported?

  == Comment: #7 - William J. Schmidt  - 2016-11-28 
09:17:01 ==
  (In reply to comment #6)
  > Hi,
  >
  > > Well, as long as they pick up the backported fixes, nothing else is
  > > required.  That's what this feature is there to ensure.
  >
  > Do you know, at this time, which are the fixes that will be requested to be
  > backported?

  Peter, can you please respond to Breno's question?

  == Comment: #8 - Peter E. Bergner  - 2016-11-29 12:08:11 
==
  CC'ing Alan in case he has an extra input.

  Looking through the binutils-2_27-branch log, I see the following
  commits we would want picked up:

  commit 799b679496c98eb1f31625b00bb5db67a6f608d7
  Author: Peter Bergner 
  Date:   Fri Sep 16 16:17:46 2016 -0500

  Backport lastest POWER9 support to match final ISA 3.0
  documentation.

  opcodes/
  Apply from master.
  2016-09-14  Peter Bergner 

  * ppc-opc.c (powerpc_opcodes) : New mnemonic.
  : Delete mnemonics.
  : Rename mnemonic from ...
  : ...to this.
  : Change to a X form instruction.
  : Change to 1 operand form.
  : Delete mnemonic.
  : Rename mnemonic from ...
  : ...to this.
  : Delete mnemonics.
  : Rename mnemonic from ...
  : ...to this.

  gas/
  Apply from master.
  2016-09-14  Peter Bergner 

  * testsuite/gas/ppc/power9.d  New tests.
  : Remove 
tests.
  : Update tests.
  * testsuite/gas/ppc/power9.s: Likewise.

  commit c6a7c521c14e0cc188ccc0388e0d5d21c2042c94
  Author: Alan Modra 
  Date:   Thu Sep 1 14:56:52 2016 +0930

  Don't treat .opd section specially when ELFv2

[Touch-packages] [Bug 1690992] Re: fix for bug #1569649 left NetworkManager-wait-online disabled on some systems

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

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

Title:
  fix for bug #1569649 left NetworkManager-wait-online disabled on some
  systems

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Committed

Bug description:
  [SRU Justification]
  While attempting to verify the usage of NetworkManager-wait-online.service in 
Ubuntu, I have discovered that while the packaging says that this service 
should be enabled (LP: #1569649), it is disabled on my machine.  I believe that 
users who have continuously upgraded their systems, including over pre-releases 
of Ubuntu, may have been left in the same situation, where 
NetworkManager-wait-online.service is inactive and their boot order is 
therefore unreliable.

  This disabled NetworkManager-wait-online due to lack of upgrade fix-up
  may explain other bug reports I've seen around NFS handling, where
  users continue to report that NFS is not correctly mounted at boot.

  Though late, a one-time upgrade fix-up is warranted so that users can
  have consistent handling of the network-online target.

  [Test case]
  1. On an affected system, run 'systemctl status NetworkManager-wait-online'.  
Observe that the unit is listed as disabled.
  2. Install network-manager from -proposed.
  3. Run 'systemctl status NetworkManager-wait-online' again and verify that 
the unit is no longer marked as disabled.
  4. Reboot and verify that the system still boots correctly.

  [Regression potential]
  Since NetworkManager-wait-online uses a 30 second timeout, services that 
depend on network-online.target should see at most a 30 second delay in 
startup.  There should be no functional regressions, only regressions in the 
speed of boot and only on systems where services have explicitly declared that 
they depend on the network and the network is not available at boot.

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-09 Thread Nicholas Stommel

My apologies, it seems like this issue could have already been addressed 
upstream. See https://bugzilla.gnome.org/show_bug.cgi?id=783569
Anyway, I'll see if I can backport the fix provided there and whether or not it 
works. Sorry guys :/

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

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

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1645308] Re: [SRU] Backport zeromq3 4.2.0 to yakkety

Yes, it's on my plate - that's why I didn't release the SRU yet. Just,
ugh, don't have the time to actually look into that deeper.

** Tags removed: verification-done
** Tags added: verification-done-yakkety

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

Title:
  [SRU] Backport zeromq3 4.2.0 to yakkety

Status in zeromq3 package in Ubuntu:
  Fix Released
Status in zeromq3 source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  As per product requirement, we have released a git-snapshot based pre-
  release version of zeromq3 4.2.0 to yakkety
  (4.1.5+git20160811+2fc86bc) as the upstream version was not yet
  available. The agreement was that we will release the snapshot-based
  version only if, once the official update is available we will update
  and switch.

  The rationale for this would be that the snapshot-based version is
  anyway more-or-less feature compatible with the official version. It's
  also not wise to keep shipping a snapshot for long as some bugfixes
  might be missing from the cherry-pick. The generated binaries are
  binary-compatible, with only a few new symbols exported in the main
  4.2.0 version.

  [Test Case]

  No particular test-case - installing the new version and making sure
  that existing reverse-dependencies still work as intended.

  [Regression Potential]

  There is, of course, some regression potential, but as already
  mentioned: there weren't too many commits since the git snapshot that
  our previous version was based off.

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

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

[Touch-packages] [Bug 1696981] Re: fixrtc is ineffective when there is no battery for the RTC

2017-06-09 Thread Ubuntu Foundations Team Bug Bot

The attachment "add-fixrtc-mount.patch" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  fixrtc is ineffective when there is no battery for the RTC

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  When there is no battery for the RTC, fixrtc is not able to find a
  good enough date. To fix the clock, this script is using the last time
  the root filesystem was mounted, but as that is done before there is
  any network, and as after a reboot/poweroff the RTC time is always
  reset (because time is not kept due to lack of battery), the mount
  time will never be good.

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

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

[Touch-packages] [Bug 1603620] Re: Package lists are not updated before Unattended upgrades runs automatically.

2017-06-09 Thread Jarno Suni

https://github.com/Debian/apt/commit/b4f32b13055287d2ac46a08255db475af195b5f7

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

Title:
  Package lists are not updated before Unattended upgrades runs
  automatically.

Status in apt package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Newest kernel available currently is 4.4.0-31-generic, but

  $ linux-version list
  4.2.0-38-generic
  4.4.0-24-generic
  4.4.0-28-generic

  `apt-get dist-upgrade` does not upgrade kernel either, unless I run
  `apt-get update` first.

  I wonder why kernel was not upgraded 2016-07-16 morning.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jul 16 11:40:07 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (237 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (21 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "0";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-02-15T22:39:19.560937
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2016-06-24T18:13:45.181749

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

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

[Touch-packages] [Bug 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Lib

** Tags removed: verification-done
** Tags added: verification-done-xenial verification-done-yakkety 
verification-done-zesty

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

Title:
  unity-system-compositor crashed with SIGSEGV in
  libinput_device_config_accel_is_available() from
  libinput_device_config_accel_set_speed() from
  mir::input::evdev::LibInputDevice::apply_settings()

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in Mir 0.26 series:
  Fix Released
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Committed
Status in unity-system-compositor source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Committed
Status in mir source package in Zesty:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.1+17.04.20170216-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/. 

  It seems that the configuration change is requested just a moment
  before the device gets removed. The change actions are serialized,
  depending on where there memory of mir::input::DefaultDevice is
  allocated the segfault either occurs inside the lambda or inside
  underlying mir::input::LibInputDevice in the platform. The activities
  on input dispatch device removal and reconfiguration are serialized
  inside the input thread, so we just need to clean the action queue (or
  have multiple queues) before removing the devices.

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

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

[Touch-packages] [Bug 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)

** Tags removed: verification-done
** Tags added: verification-done-xenial verification-done-yakkety 
verification-done-zesty

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

Title:
  Mir sending key repeat events continually to nested shell after VT
  switch (causes Unity8 lockup for a while)

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Committed
Status in qtmir source package in Xenial:
  Invalid
Status in unity8 source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Committed
Status in mir source package in Zesty:
  Fix Committed

Bug description:
  Steps:
  * log in to unity8
  * Ctrl+Alt+F* to a different vt, or log in to a different user session
  * go back to the unity8 vt

  Expected:
  * session is locked, but working

  Current:
  * unity8 starts spinning for a time proportional to the period it was inactive
  * if it was inactive long enough, it doesn't seem to recover at all

  It seems it's "catching up" in some way, maybe with input, maybe
  frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)

  Causes:
  The mir::input::KeyRepeatDispatcher is running inside the nested mirserver 
even though there is another instance running inside the host server. A few 
months ago qtmir used to replace the key repeater by replacing mirs  
dispatcher. And key repeat is not disabled within the nested server. So both 
the host and the nested server are producing repeat events.
    Now due to a logic error inside mirserver the key repeat dispatcher is not 
hooked up to the input device hub when running inside the nested server. The 
input device hub would tell the key repeater when devices get removed - i.e. 
due to vt switching. So it never notices that the devices go away continues to 
produce those events indefinitely.

  This applies to all currently pressed buttons. I.e. you can open an
  edit field and press 'w' while simultaneously pressing Ctrl+Alt+FX to
  switch to another VT. On return 'w' will be repeated indefinitely.

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

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

[Touch-packages] [Bug 1677239] Re: mir_demo_standalone_render_overlays fails to link

** Tags removed: verification-done
** Tags added: verification-done-xenial verification-done-yakkety 
verification-done-zesty

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

Title:
  mir_demo_standalone_render_overlays fails to link

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in mir source package in Xenial:
  Fix Committed
Status in mir source package in Yakkety:
  Fix Committed
Status in mir source package in Zesty:
  Fix Committed

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console

  11:41:20 [ 52%] Linking CXX executable 
../../../../bin/mir_demo_standalone_render_overlays.bin
  11:41:20 cd 
/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1
  11:41:20 /usr/lib/ccache/c++ -g -O2 
-fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing 
-pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o 
../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic 
../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 
../../../capnproto/libmircapnproto.a -lkj -lcapnp 
../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system 
-lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 
-L/lib/x86_64-linux-gnu -ludev -ludev
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, 
unsigned long) const@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE'

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

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

[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS

** Tags removed: verification-done
** Tags added: verification-done-xenial verification-done-yakkety 
verification-done-zesty

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

Title:
  [SRU] Mir needs to be updated to 0.26 in 16.04LTS

Status in mir package in Ubuntu:
  In Progress
Status in mir source package in Xenial:
  Fix Committed
Status in mir source package in Yakkety:
  Fix Committed
Status in mir source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Snap development using Mir has been using the "stable phone overlay" PPA 
which is both inconvenient and a legacy of the cancelled Unity8 project.

  It would greatly simplify things if Mir were updated in the Xenial
  archive.

  [Test Case]

  Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
  against "Primary Ubuntu Archive" and deploy as described in
  https://developer.ubuntu.com/en/snappy/guides/mir-snaps/

  Expected: the client apps start and are visible on screen
  Actual: the client apps don't start and are not visible on screen

  [Regression Potential]
  Mir has two categories of dependent project:

    1 Unity8 and unity-system-compositor "server" packages
    2 toolkits and other "clients" of Mir

  "Server" packages from the archive will stop working in the LTS as
  they will continue using the earlier libmirserver.so.38 (from Mir
  0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26.
  This is unimportant as these packages were provided as an "early
  experience", not for serious use.

  "Client" packages are dependent only on libmirclient.so.9 which is ABI
  stable. The principle type of regression would be FTBFS where APIs
  have been deprecated in 0.26. The linked 0.26.3 release has these
  deprecations disabled for 16.04.

  The packages are available in silo:
  https://bileto.ubuntu.com/#/ticket/2736

  notes:

  A recursive search or rdependencies identifies the following packages
  in category 1:

  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

  Anyone wanting these packages should switch to the "unity8-desktop-
  session" preview package in 17.04 where they are far more functional.

  [Alternatives]
  If we want to keep everything working in Xenial, we *could* bump the 
libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 
being NBS, but continuing to work against the Mir servers available in 16.04[*] 
(until and unless they are rebuilt).

  However, this does not enable the desired result for IoT deployments
  of toolkits (GTK, Qt etc) and other clients working against servers
  (specifically miral-kiosk) built against the updated libraries.

  To work for IoT these would need to rebuilt from source - at which
  point they (and their dependencies) would stop working against the
  servers in category 1.

  [*] with the exception of the servers provided in mir-examples, these
  would only work with clients linking against libmirclient.so.10.

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

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

[Touch-packages] [Bug 1675138] Re: Please transition to latest Boost

** Tags removed: verification-done
** Tags added: verification-done-xenial verification-done-yakkety 
verification-done-zesty

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

Title:
  Please transition to latest Boost

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in mir source package in Xenial:
  Fix Committed
Status in mir source package in Yakkety:
  Fix Committed
Status in mir source package in Zesty:
  Fix Committed

Bug description:
  There is an ongoing transition to Boost 1.62 and mir is one of the last 
affected packages:
  http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.62.html

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

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

[Touch-packages] [Bug 775803] Re: do you like this?

2017-06-09 Thread John Butterworth

Hello friend,

Here  is some stuff that I  really like, so I just  I wanted to  ask
you if you're interested in something like that?  Take  a look here
https://clck.ru/BGaHE

Speak to you later, john.butterworth


From: Bug 775803 [mailto:775...@bugs.launchpad.net]
Sent: Friday, June 09, 2017 10:52 AM
To: john.butterwo...@talktalk.net
Subject: "I got 'em!"

I need  a man-purse, but I have  too much pride.  :-(


The main problem  is  that I work about 1.5 hours away from  where  I live, and 
I work long hours, so if I'm leaving  for work, I have to make damned sure I 
have everything I  need with  me, because  there's no  running  home for  
something or conning the wife into bringing me something  I forgot.


Sent from Mail for Windows 10

** Attachment added: "1CD7628C9C640B23415BB235FD4C1BA1.jpg"
   
https://bugs.launchpad.net/bugs/775803/+attachment/4893114/+files/1CD7628C9C640B23415BB235FD4C1BA1.jpg

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

Title:
  /usr/bin/python: error while loading shared libraries: /lib/i386
  -linux-gnu/libz.so.1: invalid ELF header

Status in zlib package in Ubuntu:
  New

Bug description:
  Binary package hint: nvidia-common

  Upgrade failed to install correctly

  ProblemType: Package
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-9-generic 2.6.38-9.43
  ProcVersionSignature: Ubuntu 2.6.35-29.51-generic 2.6.35.12
  Uname: Linux 2.6.35-29-generic i686
  Architecture: i386
  Date: Mon May  2 19:42:26 2011
  ErrorMessage: run-parts: /etc/kernel/postinst.d/nvidia-common exited with 
return code 127
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  SourcePackage: nvidia-common
  Title: package linux-image-2.6.38-9-generic 2.6.38-9.43 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/nvidia-common exited with 
return code 127
  UpgradeStatus: Upgraded to natty on 2011-05-02 (0 days ago)

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

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

[Touch-packages] [Bug 1696623] Re: macvtap creation issue using net namespaces

I upgraded my Xenial test system to linux-virtual-hwe-16.04-edge and with that 
it is working fine.
So we have a good testcase (thanks Rolando) a crash dmesg on the issue and 
confirmed that it is solved in a newer kernel.

Comes down to bisecting maybe, but there is a chance the kernel team
just knows.

That said I'm rerouting the bug to the kernel Team.

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

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

Title:
  macvtap creation issue using net namespaces

Status in linux package in Ubuntu:
  New

Bug description:
  Hi there,

  There seems to be a bug when trying to create two macvtap links that
  are contained within different net namespaces. This is what I'm facing
  and, at the same time, the steps to reproduce the issue:

  1 - Create two net namespaces:
  #
  root@rjz-nuc:~# ip netns add bng1
  root@rjz-nuc:~# ip netns add bng2

  2 - Create two veth links, one in one net NS and another one in the other net 
NS:
  #
  root@rjz-nuc:~# ip link add netns bng1 bng1-111_veth type veth peer name 
subs-lg111_veth
  root@rjz-nuc:~# ip link add netns bng2 bng2-111_veth type veth peer name 
subs-lg211_veth

  3a - Add a macvtap link on top of the 1st veth in the 1st net NS:
  #
  root@rjz-nuc:~# ip netns exec bng1 ip link add link bng1-111_veth name 
bng1-111_mcvtp type macvtap mode passthru

  3b - This executes correctly and creates a tap device:
  #
  root@rjz-nuc:~# ip netns exec bng1 ip link show bng1-111_mcvtp
  3: bng1-111_mcvtp@bng1-111_veth:  mtu 1500 qdisc noop 
state DOWN mode DEFAULT group default qlen 500
  link/ether ae:c6:bc:d8:d2:e7 brd ff:ff:ff:ff:ff:ff

  3c - Note the "3:" at the beginning of above output pointing to "tap3" that 
the command created:
  #
  root@rjz-nuc:~# ls -tral /dev/tap*
  crw--- 1 root root 241, 1 Jun  7 20:16 /dev/tap3

  4a - Try to add another macvtap link but now on top of the 1st veth in the 
2nd net NS:
  #
  root@rjz-nuc:~# ip netns exec bng2 ip link add link bng2-111_veth name 
bng2-111_mcvtp type macvtap mode passthru
  RTNETLINK answers: File exists

  4b - As it can be seen, it fails stating "file exists". Checking the output 
of "dmesg", it can be seen the reason behind this is that instead of choosing 
as the tap device the next system-wide free one (for instance, say, tap4) it 
chooses the "tap3" that was already created by the command in step 3a above:
  #
  [Jun 7 20:17] [ cut here ]
  [  +0.32] WARNING: CPU: 3 PID: 1216 at 
/build/linux-As38az/linux-4.4.0/fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80()
  [  +0.07] sysfs: cannot create duplicate filename '/class/macvtap/tap3'
  [  +0.05] Modules linked in: macvtap macvlan veth drbg ansi_cprng ctr ccm 
xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp espaf_key xfrm_algo arc4 
snd_hda_codec_hdmi 8250_dw snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core 
snd_soc_sst_ipc snd_soc_sst_dsp snd_hec_realtek snd_hda_codec_generic 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine dw_dmac_core snd_hda_intel 
snd_hda_codec inte iwlmvm snd_hda_core x86_pkg_temp_thermal intel_powerclamp 
coretemp snd_hwdep crct10dif_pclmul mac80211 snd_pcm crc32_pclmul ghash_i_intel 
snd_seq_midi aesni_intel snd_seq_midi_event aes_x86_64 lrw gf128mul snd_rawmidi 
glue_helper ablk_helper iwlwifi cryptd snd_put_leds snd_seq_device serio_raw 
cfg80211 snd_timer snd ir_lirc_codec soundcore lirc_dev ir_xmp_decoder 
ir_mce_kbd_decoder
  [  +0.000149]  ir_sharp_decoder ir_sanyo_decoder ir_sony_decoder 
ir_jvc_decoder ir_rc6_decoder btusb hci_uart btrtl btbcm ir_rc5_debtqca 
ir_nec_decoder idma64 virt_dma mei_me shpchp mei btintel intel_lpss_pci 
bluetooth rc_rc6_mce ite_cir rc_core intel_lpss_acpi ad mac_hid acpi_als 
intel_lpss kfifo_buf industrialio kvm_intel kvm irqbypass autofs4 i915_bpo 
intel_ips i2c_algo_bit drm_kms_helpe0e syscopyarea sysfillrect sysimgblt ptp 
sdhci_pci fb_sys_fops pps_core drm sdhci ahci libahci video 
pinctrl_sunrisepoint i2c_hid p_intel hid fjes
  [  +0.000124] CPU: 3 PID: 1216 Comm: ip Not tainted 4.4.0-79-generic 
#100-Ubuntu
  [  +0.07] Hardware name:  /NUC6i3SYB, BIOS 
SYSKLi35.86A.0024.2015.1027.2142 10/27/2015
  [  +0.06]  0286 ffea66e1 88083a5ef5b8 
813f94d3
  [  +0.13]  88083a5ef600 81ce3010 88083a5ef5f0 
81081322
  [  +0.11]  88083a56c000 88083c212900 88083a5fbca8 
88083a5fbca8
  [  +0.11] Call Trace:
  [  +0.17]  [] dump_stack+0x63/0x90
  [  +0.15]  [] warn_slowpath_common+0x82/0xc0
  [  +0.11]  [] warn_slowpath_fmt+0x5c/0x80
  [  +0.15]  [] sysfs_warn_dup+0x62/0x80
  [  +0.14]  [] sysfs_do_create_link_sd.isra.2+0x9e/0xb0
  [  +0.14]  [] sysfs_create_link+0x25/0x40
  [  +0.13]  [] device_add+0x22e/0x650
  [  +0.12]  []

[Touch-packages] [Bug 1697016] Re: package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

** Tags removed: need-duplicate-check

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

Title:
  package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  New

Bug description:
  no sound in player

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl-doc 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   gstreamer1.0-libav: Install
   libssl-doc: Configure
   gstreamer1.0-libav: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jun  9 20:58:12 2017
  Dependencies:
   
  DuplicateSignature:
   package:libssl-doc:1.0.2g-1ubuntu4.6
   Unpacking gstreamer1.0-libav:amd64 (1.8.3-1ubuntu0.2) ...
   dpkg: error processing package libssl-doc (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-11-24 (197 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to xenial on 2017-05-02 (37 days ago)

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

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

[Touch-packages] [Bug 1696623] Re: macvtap creation issue using net namespaces