[Touch-packages] [Bug 1674532] Re: glibc update caused NSS ABI break

[Adam Conrad]

** Summary changed:

- Ubuntu 14.04 broken during PXE boot
+ glibc update caused NSS ABI break

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

Title:
  glibc update caused NSS ABI break

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Fix Released
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Fix Released
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  Fix Released
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  Invalid

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

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

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

[Touch-packages] [Bug 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Adam Conrad]

Yes, it's known that updating from the version with the regression to
the version that backed it out will cause the same (well, inverse) bug
to appear until services or the machine are restarted.  That's
unfortunate, but there's not a whole bunch we can do to mitigate that,
and reverting the regression was the important bit.

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

Title:
  glibc update caused NSS ABI break

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Fix Released
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Fix Released
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  Fix Released
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  Invalid

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

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

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

[Touch-packages] [Bug 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Adam Conrad]

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

** Changed in: glibc (Ubuntu Xenial)
   Importance: Undecided => Critical

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

** Changed in: eglibc (Ubuntu Precise)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

** Changed in: eglibc (Ubuntu Trusty)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

** Changed in: glibc (Ubuntu Xenial)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Confirmed
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Confirmed
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  Confirmed
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  Invalid

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

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

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

[Touch-packages] [Bug 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Adam Conrad]

** Changed in: glibc (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Confirmed
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Confirmed
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  New
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  New

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

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

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

[Touch-packages] [Bug 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Adam Conrad]

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

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

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

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

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

** Also affects: glibc (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: eglibc (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: glibc (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: eglibc (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Changed in: eglibc (Ubuntu Precise)
   Importance: Undecided => Critical

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

** Changed in: eglibc (Ubuntu Trusty)
   Importance: Undecided => Critical

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

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

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

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

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

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

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Confirmed
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Confirmed
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  New
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  New

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

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

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

[Touch-packages] [Bug 1609888] Re: package vim-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/xxd', which is also in package vim 20160703-1

[Adam Conrad]

We can't possibly be expected to deal with conflicts with locally-
packaged software we didn't provide.  We support upgrades from Ubuntu to
Ubuntu.

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

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

Title:
  package vim-common (not installed) failed to install/upgrade: trying
  to overwrite '/usr/bin/xxd', which is also in package vim 20160703-1

Status in vim package in Ubuntu:
  Invalid

Bug description:
  The vim updates from debian seems to conflict with the one I compiled
  from source.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: vim-common (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Aug  4 12:35:28 2016
  DpkgHistoryLog:
   Start-Date: 2016-08-04  12:35:20
   Commandline: aptdaemon role='role-commit-packages' sender=':1.357'
   Install: vim-common:amd64 (2:7.4.1689-3ubuntu1.1, automatic), 
vim-runtime:amd64 (2:7.4.1689-3ubuntu1.1, automatic)
   Upgrade: google-chrome-stable:amd64 (52.0.2743.82-1, 52.0.2743.116-1), 
vim:amd64 (20160703-1, 2:7.4.1689-3ubuntu1.1), neovim:amd64 
(0.1.4ubuntu1+git201607061313+2636+20~ubuntu16.04.1, 
0.1.4ubuntu1+git201608031207+2682+20~ubuntu16.04.1)
  DuplicateSignature:
   package:vim-common:(not installed)
   Unpacking vim-common (2:7.4.1689-3ubuntu1.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/vim-common_2%3a7.4.1689-3ubuntu1.1_amd64.deb (--unpack):
trying to overwrite '/usr/bin/xxd', which is also in package vim 20160703-1
  ErrorMessage: trying to overwrite '/usr/bin/xxd', which is also in package 
vim 20160703-1
  InstallationDate: Installed on 2016-06-04 (61 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: vim
  Title: package vim-common (not installed) failed to install/upgrade: trying 
to overwrite '/usr/bin/xxd', which is also in package vim 20160703-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1673817] Re: update-secure-boot-policy behaving badly with unattended-upgrades

[Adam Conrad]

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

** Changed in: shim-signed (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: shim-signed (Ubuntu)
   Importance: Undecided => High

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

Title:
  update-secure-boot-policy behaving badly with unattended-upgrades

Status in shim-signed package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  Currently, unattended-upgrades will automatically install all updates
  for those running development releases of Ubuntu (LP: #1649709)

  Today, my computer was acting very sluggish. Looking at my process
  list, I saw/ usr/sbin/update-secureboot-policy was using a log of CPU.

  I killed the process. I have a /var/crash/shim-signed.0.crash but
  since it's 750 MB, I didn't bother submitting it or looking at it
  more. Maybe it crashed because I killed the process. Also, I see that
  unattended-upgrades-dpkg.log is 722 MB.

  Today's update included both VirtualBox and the linux kernel.

  I am attaching an excerpt of /var/log/unattended-upgrades/unattended-
  upgrades-dpkg.log

  This message was repeated a very large number of times (but I only
  included it once in the attachment:

  "Invalid password

  The Secure Boot key you've entered is not valid. The password used must be 
  between 8 and 16 characters."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: shim-signed 1.23+0.9+1474479173.6c180c6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 17 11:15:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-23 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  SourcePackage: shim-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1661691] Re: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

[Adam Conrad]

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

** Changed in: vim (Ubuntu Zesty)
   Status: Confirmed => 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/1661691

Title:
  TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

Status in vim package in Ubuntu:
  In Progress
Status in vim source package in Zesty:
  In Progress

Bug description:
  I quite often have the following work flow:

  a.) lxc launch ubuntu-daily:zesty z1
  b.) lxc exec z1 /bin/bash
  c.) % vi foo.txt
  d.) paste some thing from my X buffer (hit middle mouse button).

  Somewhere between yakkety (2:7.4.1829-1ubuntu2.1) and zesty
  (2:8.0.0095-1ubuntu2) this behavior changed.

  Previously this all worked fine.

  Now, in zesty, however an attempt to paste results in a vi error message:
   E353: Nothing in register "

  to fix this, you can first disable the mouse 'a' [1]

   : set mouse-=a

  
  I'm not sure what is enabling this, because /usr/share/vim/vimrc has the line
  set mouse=a commented out.

  --
  [1] 
http://www.varesano.net/blog/fabio/disable%20vim%20automatic%20visual%20mode%20using%20mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: vim-nox 2:8.0.0095-1ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  3 12:14:20 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (561 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1638122] Re: vim-gtk-py2 pkg doesn't support python2

[Adam Conrad]

Testing on yakkety here, '/usr/bin/vim.gtk-py2 --version' reports
python2 support and not python3.  /usr/bin/vim, however, is pointing to
vim-gnome, which is (correctly) the inverse.  Perhaps that's the
confusion?

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

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

Title:
  vim-gtk-py2  pkg doesn't support python2

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Found on:
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety
  $ uname -a
  Linux p55a-ud3 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 14:39:52 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  Description:
  vim-gtk-py2 pkg from official repository doesn't support python2. But it has 
built with flag -lpython3.5m instead.

  Expected:
  vim-gtk-py2 and vim-gtk3-py2 is support python2.

  Actually:
  vim-gtk-py2 and vim-gtk3-py2 isn't support python2.

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

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

[Touch-packages] [Bug 1608935] Re: 2:7.4.1689-3ubuntu1.1 added unneeded dependency

[Adam Conrad]

It wasn't an "unneeded dependency", vim in Ubuntu has always had python
support built in (though we switched from python2 to python3).  This was
fixing a regression, not introducing something new to annoy you.

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

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

Title:
  2:7.4.1689-3ubuntu1.1 added unneeded dependency

Status in vim package in Ubuntu:
  Won't Fix

Bug description:
  To fix a Powerline issue, an unneeded dependy on libpython3.5 has been
  added to vim package.

  cf. 
http://changelogs.ubuntu.com/changelogs/pool/main/v/vim/vim_7.4.1689-3ubuntu1.1/changelog
  and https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1574897

  Adding libpython3.5 to vim will refrain any user to upgrade without
  forcing him to dist-upgrade

  vim users should not been forced to install libpython3.5

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

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

[Touch-packages] [Bug 1613949] Re: vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu 16.04.1 Xenial

[Adam Conrad]

This came about because you installed from -updates (possibly a point
release ISO), and then disabled non-security updates, causing the local
and remote packages to be mismatched until a security update trumped
them both.

Definitely not a vim packaging bug.

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

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

Title:
  vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu
  16.04.1 Xenial

Status in vim package in Ubuntu:
  Invalid

Bug description:
  I have a fresh install of Ubuntu v16.04.1, then I did an `apt-get
  upgrade` and it only had a few seemingly-minor packages to upgrade
  (don't remember the list, sorry).

  Apparently all the core vim packages have been upgraded to
  2:7.4.1689-3ubuntu1.1 but vim-gtk3 (and all the other gvim-providing
  packages I tested) are still held back to 2:7.4.1689-3ubuntu1 so there
  is a version mis-match.

  Now I get the following error:

  [[[ BEGIN PASTE ]]]

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

  The following packages have unmet dependencies:
   vim-gtk3 : Depends: vim-common (= 2:7.4.1689-3ubuntu1) but 
2:7.4.1689-3ubuntu1.1 is to be installed
  Depends: vim-runtime (= 2:7.4.1689-3ubuntu1) but 
2:7.4.1689-3ubuntu1.1 is to be installed
  E: Unable to correct problems, you have held broken packages.

  [[[ END PASTE ]]]

  
  However I can still get gvim working if I force the installation of the 
vim-gtk3 package using dpkg.  Of course this is not a good solution, because it 
leaves my system in a state of seemingly-broken packages!

  
  [[[ BEGIN PASTE ]]]

  root@machine:/# dpkg -i --force-depends ./vim-gtk3_7.4.1689-3ubuntu1_amd64.deb
  Selecting previously unselected package vim-gtk3.
  (Reading database ... 251539 files and directories currently installed.)
  Preparing to unpack .../vim-gtk3_7.4.1689-3ubuntu1_amd64.deb ...
  Unpacking vim-gtk3 (2:7.4.1689-3ubuntu1) ...
  dpkg: vim-gtk3: dependency problems, but configuring anyway as you requested:
   vim-gtk3 depends on vim-common (= 2:7.4.1689-3ubuntu1); however:
Version of vim-common on system is 2:7.4.1689-3ubuntu1.1.
   vim-gtk3 depends on vim-runtime (= 2:7.4.1689-3ubuntu1); however:
Version of vim-runtime on system is 2:7.4.1689-3ubuntu1.1.

  Setting up vim-gtk3 (2:7.4.1689-3ubuntu1) ...
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vim (vim) in 
auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vimdiff 
(vimdiff) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rvim (rvim) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rview 
(rview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vi (vi) in 
auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/view (view) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/ex (ex) in 
auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/editor 
(editor) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvim (gvim) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gview 
(gview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgview 
(rgview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgvim 
(rgvim) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/evim (evim) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/eview 
(eview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvimdiff 
(gvimdiff) in auto mode

  [[[ END PASTE ]]]

  
  And yes, I can confirm that gvim actually works using this method.  We just 
need to upgrade the package versioning so that we don't have a problem with the 
apt-get packaging dependency system.

  Thanks for all your hard work.  Ubuntu is #1!!!  :-)

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

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

[Touch-packages] [Bug 1654882] Re: vim python 2.x support missing

[Adam Conrad]

vim can't reliably/sanely run with python2 and python3 both linked in
(despite the build system letting you try), so we chose python3.  I'd
encourage you to upgrade your addons to py3 and give that a whirl.

If, however, you're stuck with python2 for now, you might want to try
installing "vim-nox-py2", which exists in xenial and yakkety for this
very reason.  We've dropped it in zesty and beyond, however.

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

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

Title:
  vim python 2.x support missing

Status in vim package in Ubuntu:
  Won't Fix

Bug description:
  While using vim with vim-youcompleteme is completely broken in Ubuntu
  16.04.

  While running the command:

  vim --version | grep python

  I observed the python support is missing in this vim build: -python

  +cryptv  +linebreak   -python  +vreplace
  +cscope  +lispindent  +python3 +wildignore
  Linking: gcc   -L. -Wl,-Bsymbolic-functions -Wl,-z,relro -fstack-protector 
-rdynamic -Wl,-export-dynamic -Wl,-E  -Wl,-Bsymbolic-functions -fPIE -pie 
-Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim   -lgtk-x11-2.0 -lgdk-x11-2.0 
-lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 
-lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype  -lgnomeui-2 -lSM 
-lICE -lbonoboui-2 -lgnome-2 -lpopt -lbonobo-2 -lbonobo-activation -lORBit-2 
-lgnomecanvas-2 -lart_lgpl_2 -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 
-latk-1.0 -lcairo -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lfontconfig -lfreetype 
-lgdk_pixbuf-2.0 -lgnomevfs-2 -lgconf-2 -lgthread-2.0 -lgmodule-2.0 
-lgobject-2.0 -lglib-2.0 -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE  -lm 
-ltinfo -lnsl  -lselinux  -lacl -lattr -lgpm -ldl  -L/usr/lib -llua5.2 -Wl,-E  
-fstack-protector-strong -L/usr/local/lib  
-L/usr/lib/x86_64-linux-gnu/perl/5.22/CORE -lperl -ldl -lm -lpthread -lcrypt  
-L/usr/lib/python3.5/config-3.5m-x86_64
 -linux-gnu -lpython3.5m -lpthread -ldl -lutil -lm -L/usr/lib/x86_64-linux-gnu 
-ltcl8.6 -ldl -lz -lpthread -lieee -lm -lruby-2.3 -lpthread -lgmp -ldl -lcrypt 
-lm

  Currently the vim-youcompleteme is completely unusable from vim-addon-
  manager.

  Also many vim plugin which I am currently using which requires this
  python support have stopped working altogether such as clang-format.py

  Kindly release an updated version with support for python-2.x.

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

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

[Touch-packages] [Bug 1669646] Re: Vim on Xenial not build with python2/3 and lua

[Adam Conrad]

You're using vim-tiny.  Install the "vim" package if you need python3
support, and vim-nox, vim-athena, vim-gtk2, or vim-gtk3 (as appropriate
for your environment) if you need *all* interpreters.  See the
descriptions for each package.

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

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

Title:
  Vim on Xenial not build with python2/3 and lua

Status in vim package in Ubuntu:
  Invalid

Bug description:
  The Feature included as follow on Xenial, but no python2/3 and lua:

  ➜  ~ vim --version  
  VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Mar 02 2017 10:44:27)
  Included patches: 1-313, 315-398
  Modified by pkg-vim-maintain...@lists.alioth.debian.org
  Compiled by pkg-vim-maintain...@lists.alioth.debian.org
  Huge version without GUI.  Features included (+) or not (-):
  +acl +file_in_path+mouse_sgr   +tag_old_static
  +arabic  +find_in_path-mouse_sysmouse  -tag_any_white
  +autocmd +float   +mouse_urxvt -tcl
  -balloon_eval+folding +mouse_xterm +termguicolors
  -browse  -footer  +multi_byte  +terminfo
  ++builtin_terms  +fork()  +multi_lang  +termresponse
  +byte_offset +gettext -mzscheme+textobjects
  +channel -hangul_input+netbeans_intg   +timers
  +cindent +iconv   +num64   +title
  -clientserver+insert_expand   +packages-toolbar
  -clipboard   +job +path_extra  +user_commands
  +cmdline_compl   +jumplist-perl+vertsplit
  +cmdline_hist+keymap  +persistent_undo +virtualedit
  +cmdline_info+lambda  +postscript  +visual
  +comments+langmap +printer +visualextra
  +conceal +libcall +profile +viminfo
  +cryptv  +linebreak   -python  +vreplace
  +cscope  +lispindent  -python3 +wildignore
  +cursorbind  +listcmds+quickfix+wildmenu
  +cursorshape +localmap+reltime +windows
  +dialog_con  -lua +rightleft   +writebackup
  +diff+menu-ruby-X11
  +digraphs+mksession   +scrollbind  -xfontset
  -dnd +modify_fname+signs   -xim
  -ebcdic  +mouse   +smartindent -xpm
  +emacs_tags  -mouseshape  +startuptime -xsmp
  +eval+mouse_dec   +statusline  -xterm_clipboard
  +ex_extra+mouse_gpm   -sun_workshop-xterm_save
  +extra_search-mouse_jsbterm   +syntax  
  +farsi   +mouse_netterm   +tag_binary

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

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

[Touch-packages] [Bug 1661691] Re: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

[Adam Conrad]

Ahh, thanks for digging, Christian.  Given this appears to break
horribly in all chroot scenarios (not just containers), I'm inclined to
just remove that bit from the defaults file.  Also of note, the shiny
new defaults thing has syntax:on, so I can remove that from our Debian
delta.  Yay.  Will prepare an upload fixing this and some other bits
shortly.

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

Title:
  TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

Status in vim package in Ubuntu:
  Confirmed
Status in vim source package in Zesty:
  Confirmed

Bug description:
  I quite often have the following work flow:

  a.) lxc launch ubuntu-daily:zesty z1
  b.) lxc exec z1 /bin/bash
  c.) % vi foo.txt
  d.) paste some thing from my X buffer (hit middle mouse button).

  Somewhere between yakkety (2:7.4.1829-1ubuntu2.1) and zesty
  (2:8.0.0095-1ubuntu2) this behavior changed.

  Previously this all worked fine.

  Now, in zesty, however an attempt to paste results in a vi error message:
   E353: Nothing in register "

  to fix this, you can first disable the mouse 'a' [1]

   : set mouse-=a

  
  I'm not sure what is enabling this, because /usr/share/vim/vimrc has the line
  set mouse=a commented out.

  --
  [1] 
http://www.varesano.net/blog/fabio/disable%20vim%20automatic%20visual%20mode%20using%20mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: vim-nox 2:8.0.0095-1ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  3 12:14:20 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (561 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1661691] Re: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

[Adam Conrad]

I can middle-paste fine under TERM=xterm with vim.  Are you using gvim
or some other variant?

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

Title:
  TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

Status in vim package in Ubuntu:
  Confirmed
Status in vim source package in Zesty:
  Confirmed

Bug description:
  I quite often have the following work flow:

  a.) lxc launch ubuntu-daily:zesty z1
  b.) lxc exec z1 /bin/bash
  c.) % vi foo.txt
  d.) paste some thing from my X buffer (hit middle mouse button).

  Somewhere between yakkety (2:7.4.1829-1ubuntu2.1) and zesty
  (2:8.0.0095-1ubuntu2) this behavior changed.

  Previously this all worked fine.

  Now, in zesty, however an attempt to paste results in a vi error message:
   E353: Nothing in register "

  to fix this, you can first disable the mouse 'a' [1]

   : set mouse-=a

  
  I'm not sure what is enabling this, because /usr/share/vim/vimrc has the line
  set mouse=a commented out.

  --
  [1] 
http://www.varesano.net/blog/fabio/disable%20vim%20automatic%20visual%20mode%20using%20mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: vim-nox 2:8.0.0095-1ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  3 12:14:20 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (561 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1673557] Re: /proc/cpuinfo should be collected

[Adam Conrad]

Ugly collapsing code:

sed -n '/^processor/,/^$/{/^$/q; p}' /proc/cpuinfo ; foo=$(sed
'/^processor/,/^$/d' /proc/cpuinfo); if [ -n "$foo" ]; then echo -e
"\n$foo"; fi

Prettying that into one line of sed or awk shouldn't technically be
hard, but not my top priority today. :P

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

Title:
  /proc/cpuinfo should be collected

Status in apport package in Ubuntu:
  Triaged
Status in whoopsie package in Ubuntu:
  Triaged

Bug description:
  apport does not currently collect data from /proc/cpuinfo and this
  would be useful to determine how many users can only run the i386
  version of Ubuntu.

  The general Ubuntu hook, possibly add_kernel_info() could be used,
  should be modified such that the contents of /proc/cpuinfo are
  gathered.

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

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

[Touch-packages] [Bug 1555904] Re: opal-prd not installed by default on ppc64el systems

[Adam Conrad]

** Package changed: ubuntu-meta (Ubuntu) => skiboot (Ubuntu)

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

Title:
  opal-prd not installed by default on ppc64el systems

Status in skiboot package in Ubuntu:
  New

Bug description:
  Just tried an install with current 16.04 network media, using standard
  server package selections, and it looks like opal-prd isn't installed
  by default:

   [jk@fstn ~]$ dpkg -l opal-prd
   dpkg-query: no packages found matching opal-prd

  This is required for RAS-type functions on OpenPOWER machines; and has
  a similar role to something like acpid, on x86.

  I'm not sure whether filing this against the skiboot package is best,
  or whether this should be moved to something installer-related. Happy
  to shift if necessary.

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

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

[Touch-packages] [Bug 1612835] Re: Please remove jasper from Zesty

[Adam Conrad]

Removing packages from zesty:
jasper 1.900.1-debian1-2.4+deb8u1 in zesty
libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty amd64
libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty arm64
libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty armhf
libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty i386
libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty powerpc
libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty ppc64el
libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty s390x
libjasper-runtime 1.900.1-debian1-2.4+deb8u1 in zesty amd64
libjasper-runtime 1.900.1-debian1-2.4+deb8u1 in zesty arm64
libjasper-runtime 1.900.1-debian1-2.4+deb8u1 in zesty armhf
libjasper-runtime 1.900.1-debian1-2.4+deb8u1 in zesty i386
libjasper-runtime 1.900.1-debian1-2.4+deb8u1 in zesty powerpc
libjasper-runtime 1.900.1-debian1-2.4+deb8u1 in zesty ppc64el
libjasper-runtime 1.900.1-debian1-2.4+deb8u1 in zesty s390x
libjasper1 1.900.1-debian1-2.4+deb8u1 in zesty amd64
libjasper1 1.900.1-debian1-2.4+deb8u1 in zesty arm64
libjasper1 1.900.1-debian1-2.4+deb8u1 in zesty armhf
libjasper1 1.900.1-debian1-2.4+deb8u1 in zesty i386
libjasper1 1.900.1-debian1-2.4+deb8u1 in zesty powerpc
libjasper1 1.900.1-debian1-2.4+deb8u1 in zesty ppc64el
libjasper1 1.900.1-debian1-2.4+deb8u1 in zesty s390x
Comment: Removed from Debian; https://bugs.debian.org/812630
Remove [y|N]? y
1 package successfully removed.


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

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

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

Title:
  Please remove jasper from Zesty

Status in digikam package in Ubuntu:
  Fix Released
Status in jasper package in Ubuntu:
  Fix Released
Status in kde4libs package in Ubuntu:
  Fix Released
Status in kimageformats package in Ubuntu:
  Fix Released
Status in kopete package in Ubuntu:
  Fix Released

Bug description:
  Jasper has been removed from Debian. It would be great if jasper's
  source and all binary packages could be removed in Ubuntu before 17.04
  is released. Jasper has a long security history and shouldn't remain,
  unmaintained, in universe.

  
https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html
  /jasper-rm.html

  As of 2017-02-10, all reverse depends in Zesty have been updated to
  drop dependencies on jasper:

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

  
  == Original Report ==

  # reverse-depends -b src:jasper
  Reverse-Build-Depends
  =
  * digikam   (for libjasper-dev)
  * kde4libs  (for libjasper-dev)
  * kimageformats (for libjasper-dev)
  * kopete(for libjasper-dev)

  The last 4 are KDE stuff. Since these packages have already removed
  their jasper dependency in Debian, you should be able to just copy
  what's already been done.

  February 2017 Update
  
  Here are the remaining commits from Debian that need to be applied in Ubuntu:

  
https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=5c373d77d
  
https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=efe65d118b

  
https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=efad42f0186
  
https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=b12bc0753c7

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

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

[Touch-packages] [Bug 1662562] Re: Ubuntu 16.04.2 should have Mesa 13.0.4 out-of-the-box

[Adam Conrad]

** Changed in: ubuntu
   Status: Confirmed => Invalid

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

Title:
  Ubuntu 16.04.2 should have Mesa 13.0.4 out-of-the-box

Status in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  Mesa 13.0.4 has been released recently, and it is a good idea to include Mesa 
13.0.4 to ubuntu 16.04.2 before its release. Please see this article:
  
http://news.softpedia.com/news/mesa-13-0-4-released-with-radeonsi-and-intel-anv-vulkan-driver-improvements-512493.shtml
  "Users are urged to update to Mesa 13.0.4 as soon as possible"
  It makes no sense to release 16.04.2 with outdated mesa, while there is a new 
stable mesa available

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

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

[Touch-packages] [Bug 1637601] Update Released

[Adam Conrad]

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

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in base-passwd source package in Xenial:
  Won't Fix
Status in libvirt source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Users performing live migration of guests with image files
     shared over NFS between the source and target host systems
     may experience I/O errors in the guests if user id of the
     libvirt-qemu user differs between the host systems, due to
     permission errors when accessing the image files.

   * The 16.04 LTS is an important stream for KVM (at least on
     Power), and guest live migration over NFS is an important
     feature on it.

   * The proposed fix (a minimal backport from what is applied
     on Zesty/Debian, so to be very conservative for the LTS)
     simply tries to use the reserved uid for the libvirt-qemu
     user on new installations (when the user is created) if
     the reserved uid is not taken by another user (no failures
     occur if the libvirt-qemu user already exists or the uid
     is taken.)

  [Test Case]

   * Setup 2x systems with Ubuntu 16.04 LTS as KVM hosts (e.g., micro and tiny)
     (check whether the libvirt-qemu uid differs between them;
  e.g. # id libvirt-qemu )

   * Create a guest in the source KVM host system (e.g, microg5)

   * Live migrate the guest to the destination KVM host system (e.g.,
  tiny)

     root@micro:~# virsh migrate --live --domain microg5 qemu+ssh://tiny/system
   --verbose --undefinesource --persistent --timeout 60
     Migration: [100 %]

   * Check whether the guest is now listed in the destination KVM host
  system:

  root@tiny:~# virsh list --all
  Id Name State

  12 microg5 running

   * Check whether I/O errors are seen in that guest:

  root@microg5:~# dmesg
  ...
  [ 60.818955] blk_update_request: I/O error, dev vdc, sector 96749232
  [ 60.819113] Aborting journal on device vdc2-8.
  [ 60.820121] blk_update_request: I/O error, dev vdc, sector 9084320
  [ 60.820643] EXT4-fs warning (device vdc2): ext4_end_bio:329: I/O error
   -5 writing to inode 393279 (offset 0 size 0 ...

  * Simplified test of the wanted effect:
- install libvirt on a system that didn't have it before and check the  
  id of libvirt-qemu
$ id libvirt-qemu

  [Regression Potential]

   * On installations in which the libvirt-qemu user does not exist
     (e.g., first time installation of libvirt-bin) its assigned uid
     might be different from what the user previously expected, since
     now it's assigned a number from the reserved range.

   * Overall, the fix is very conservative (the uid assignment only
     happens in case: 1) the libvirt-qemu user is being created, and
     2) if the desired uid is not taken by another user, e.g. LDAP).

  [Other Info]

   * None at this time.

  <...>

  Please see comment #8 for the problem description, and summary of
  originally bridged comments in the description in later comments.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1622686] Update Released

[Adam Conrad]

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

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

Title:
  double header in 16.10

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  New
Status in humanity-icon-theme source package in Yakkety:
  Fix Released
Status in ubiquity source package in Yakkety:
  New

Bug description:
  [Impact]

  During install and oem-firstboot, the header bar at the top of the
  screen in Ubiquity is twice as tall as it should be on hidpi screens
  (looking like two normal sized header bars stacked on top of each
  other), and the blue a11y icon is double sized.

  This looks obviously incorrect and ugly and makes a bad first
  impression on users installing Ubuntu on a hidpi laptop or customers
  of Ubuntu OEMs booting new machines for the first time.  Arstechnica
  commented negatively on this in their review of Dell's XPS 13:
  http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still-
  delivers-linux-now-embraces-svelte-hardware/

  Users of the Dell XPS 13 are affected as well as users of other brands
  of laptops with hidpi screens.  System76 is temporarily carrying a
  patched version of Humanity to work around this bug.

  The a11y icon is double-sized because the version of Humanity shipping
  in Ubuntu doesn't support @2 hidpi scaling, which results in the
  header bar doubling its height.  Because the header bar is drawn with
  CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars
  stacked one on top of the other.  The fix to the Humanity icon theme
  adds @2 hidpi support, which shrinks the icon and restores the header
  bar to its normal height.

  
  [Test Case]
  ISO install:
  1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer 
with a hidpi screen.
  2. Note the double-sized header and icon during install.
  - Using an iso with a fixed version of Humanity, the header and icon 
should look normal.

  OEM-Firstboot:
  1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi 
screen.
  2. After installing, click the launcher icon to "Prepare for shipping to the 
end user" and reboot.
  3. During oem-firstboot, note the double-sized header and icon during install.
  - To test the fix, install a fixed version of humanity before preparing 
the system for the end user.
  

  [Regression Potential]

  This patch affects the look of anything using the Humanity icon set.
  The look of Nautilus, and many other GTK apps will be affected.  This
  is not a regression but fixes another bug and resolves a discrepancy
  between rendering of icons on hidpi screens vs lowdpi screens.

  The biggest risk for regression comes from the off chance that there
  is an error or omission in the index.theme files.  Comparing icons on
  a broad range of applications and systems should catch this class of
  issues.  If any issues with icons are found, check there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1622686/+subscriptions

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

[Touch-packages] [Bug 1657863] Update Released

[Adam Conrad]

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

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

Title:
  Icons are too big or the wrong icon is shown on hidpi screens

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Released
Status in humanity-icon-theme source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Humanity icons are sometimes displayed too big on hidpi screens in
  16.04.  On both 16.04 and 16.10, different icons are used on hidpi
  screens than non-hidpi screens.  Sometimes the icons look similar but
  with much thinner strokes, while other times an icon with a different
  metaphor is used.  Users on hidpi screens will notice that icons in
  applications like Nautilus, Transmission, etc. look different (not
  just clearer) on hidpi screens.

  The fix here is to add support for @2 icons to the Humanity theme by
  adding symbolic links for @2 icons and updating the index.theme files
  accordingly.

  We should backport the fix to 16.04 and 16.10, so Humanity icons look
  the same on hidpi screens as non-hidpi screens.

  
  [Test Case]

  Here are a few test cases: 
  1) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.04: Open Nautilus and see that the icons on the hidpi 
screen are much larger.  (This applies to icons on the desktop as well.)
  -The fix should result in icons being the same size on both hidpi and 
lowdpi.
  
  2) Using a computer with a hidpi screen and one with a lowdpi screen running 
Ubuntu 16.04 or 16.10: Open Transmission and see that the "Open" button in the 
toolbar uses an icon with a different metaphor on hidpi screens (an up arrow 
emerging from a folder) than on lowdpi screens (a sheet of paper emerging from 
a folder).
  - The fix should result in the "sheet of paper emerging from a folder" 
icon being used here on both hidpi and lowdpi screens.

  3) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.10: Compare icons in Nautilus and see that the icons 
look sutbly different.  The strokes in icons on the hidpi screen will be 
visibly thinner on the hidpi screen because icons for bigger scale are used 
(say 48 on hidpi instead of 24) rather than rendering the original size icon at 
a larger resolution.
  - The fix should result in icons that have the same stroke width on hidpi 
and lowdpi screens.  The icons will still be sharper on the hidpi screen, but 
the lines won't be thinner.
  

  [Regression Potential]

  The patch is designed for compatibility where @2 support is not
  available by listing the @2 directories under "ScaledDirectories="
  rather than "Directories=".  However it's possible there could be
  other kinds of issues not found in testing.  If there are any
  omissions or errors in the index.theme, this could cause rendering
  issues for some categories of icons.  Comparing icons on a broad range
  of applications and systems should catch this class of issues.

  Hidpi users may find that their machine looks different after the
  update than it did before.  This is not a regression, but a fix to a
  bug that's been present all along.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions

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

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

[Adam Conrad]

Hello undefined, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/12.0.6-0ubuntu0.16.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

Title:
  mesa gpu lockup

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Yakkety:
  Fix Committed

Bug description:
  package: mesa
  version: 11.2.0-1ubuntu2.2
  release: 16.04.1 / "Xenial"

  references:
  * https://bugs.freedesktop.org/show_bug.cgi?id=93649
  * https://cgit.freedesktop.org/mesa/mesa/commit/?id=6dc96de3

  symptoms:
  1. kernel reports "GPU lockup"
  2. kernel reports "GPU softreset"
  3. immediately frozen display
  4. eventual "INFO: task (kworker|Xorg)[/:0-9]+ blocked for more than 120 
seconds."
  5. computer hanging on system reboot requiring a forced power off

  Symptoms occur when playing Team Fortress 2.

  Attachments:
  1. mesa source package patch
  2. lspci output for video card (ie Radeon HD 7750)
  3. kernel log

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

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

[Touch-packages] [Bug 1641017] Re: Mesa 12.0.5 - multiple important fixes, stable branch

[Adam Conrad]

Hello Boaz, or anyone else affected,

Accepted mesa into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/12.0.6-0ubuntu0.16.10.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

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

Title:
  Mesa 12.0.5 - multiple important fixes, stable branch

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Mesa 12.0.5 is now available as a point release in the stable branch. Mesa 
has MRE for these.

  The release contains multiple fixes amongst which:
  The nouveau vdpau driver performance has been restored. The wayland-egl
  module no longer crashes if the user calls eglDestroySurface and
  wl_egl_window_destroy in the "wrong" order. libEGL correctly advertises
  the EGL platforms available. Multiple fd leaks were addressed, which
  could prevent rmmod of devices such as the DisplayLink drivers. Radeonsi
  has gained noticeable performance by disabling ReZ. Interop between third
  party OpenCL implementations and mesa's libGL/libEGL is back online...
  and many more.

  Full changelog:
  https://lists.freedesktop.org/archives/mesa-dev/2016-November/135027.html

  I am particularly interested in the RadeonSI performance boost:
  https://lists.freedesktop.org/archives/mesa-dev/2016-October/131759.html
  In real-world tests the boost is about 20% (Yay!) :
  
http://www.phoronix.com/scan.php?page=news_item=Mesa-Post-ReZ-Change-Benchmarks

  [Test case]
  Run the default desktop and maybe a game or two.

  This release has been tested on xenial by the certification team on a set of 
machines, covering:
  Intel Haswell
  Intel Broadwell
  Intel Skylake
  AMD Mobility Radeon HD 5430/5450/5470

  and they all passed the tests.

  Once this is in -proposed, the community will be asked to test it on a
  wider range of devices.

  [Regression potential]
  yakkety: the release consists of cherry-picks from master, specifically 
selected as bugfixes. Regression potential should be low.

  xenial: it's a bigger bump for xenial, but since yakkety already ships
  with this series the risk should be low

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

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

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

[Adam Conrad]

Hello Boaz, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/12.0.6-0ubuntu0.16.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

Title:
  Mesa 12.0.5 - multiple important fixes, stable branch

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Mesa 12.0.5 is now available as a point release in the stable branch. Mesa 
has MRE for these.

  The release contains multiple fixes amongst which:
  The nouveau vdpau driver performance has been restored. The wayland-egl
  module no longer crashes if the user calls eglDestroySurface and
  wl_egl_window_destroy in the "wrong" order. libEGL correctly advertises
  the EGL platforms available. Multiple fd leaks were addressed, which
  could prevent rmmod of devices such as the DisplayLink drivers. Radeonsi
  has gained noticeable performance by disabling ReZ. Interop between third
  party OpenCL implementations and mesa's libGL/libEGL is back online...
  and many more.

  Full changelog:
  https://lists.freedesktop.org/archives/mesa-dev/2016-November/135027.html

  I am particularly interested in the RadeonSI performance boost:
  https://lists.freedesktop.org/archives/mesa-dev/2016-October/131759.html
  In real-world tests the boost is about 20% (Yay!) :
  
http://www.phoronix.com/scan.php?page=news_item=Mesa-Post-ReZ-Change-Benchmarks

  [Test case]
  Run the default desktop and maybe a game or two.

  This release has been tested on xenial by the certification team on a set of 
machines, covering:
  Intel Haswell
  Intel Broadwell
  Intel Skylake
  AMD Mobility Radeon HD 5430/5450/5470

  and they all passed the tests.

  Once this is in -proposed, the community will be asked to test it on a
  wider range of devices.

  [Regression potential]
  yakkety: the release consists of cherry-picks from master, specifically 
selected as bugfixes. Regression potential should be low.

  xenial: it's a bigger bump for xenial, but since yakkety already ships
  with this series the risk should be low

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

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

[Touch-packages] [Bug 1643789] Re: Backport packages for 16.04.2 lts-hwe stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/12.0.6-0ubuntu0.16.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  Backport packages for 16.04.2 lts-hwe stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Won't Fix
Status in libdrm source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New

Bug description:
  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.

  Since the xserver is already at 1.18.4, the full stack from 16.10 will
  not be backported as a renamed set of packages. Instead, only the
  drivers with bugfix releases will be backported, plus the libraries
  and mesa that complement the set.

  [Test case]

  Run a desktop session, see that things still work

  [Regression potential]

  libdrm:
  slim to none, changes from 2.4.67..2.4.70:
  - amdgpu: spelling fixes
  - ati: typo-/make check fixes
  - intel: pci-id changes, already SRU'd
  - nouveau: only some android makefile diff
  - core: drmGetDevice fixes for multi-gpu

  mesa:
  included here just to keep the necessary backport bits in the same bug, the 
actual update testing will be handled on bug #1641017. That said:
  - Intel validates new upstream releases on all their hw
  - AMD probably does the same, though it's unverified
  - this release was already tested by cert team on a handful of intel/amd 
machines

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

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

[Touch-packages] [Bug 1652486] Re: mesa gpu lockup

[Adam Conrad]

Hello undefined, or anyone else affected,

Accepted mesa into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/12.0.6-0ubuntu0.16.10.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

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

Title:
  mesa gpu lockup

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Yakkety:
  Fix Committed

Bug description:
  package: mesa
  version: 11.2.0-1ubuntu2.2
  release: 16.04.1 / "Xenial"

  references:
  * https://bugs.freedesktop.org/show_bug.cgi?id=93649
  * https://cgit.freedesktop.org/mesa/mesa/commit/?id=6dc96de3

  symptoms:
  1. kernel reports "GPU lockup"
  2. kernel reports "GPU softreset"
  3. immediately frozen display
  4. eventual "INFO: task (kworker|Xorg)[/:0-9]+ blocked for more than 120 
seconds."
  5. computer hanging on system reboot requiring a forced power off

  Symptoms occur when playing Team Fortress 2.

  Attachments:
  1. mesa source package patch
  2. lspci output for video card (ie Radeon HD 7750)
  3. kernel log

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

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

[Touch-packages] [Bug 1652564] Re: [i965 gen7][regression][patch]Intel mesa driver raises SIGFPE.

[Adam Conrad]

Hello dnord, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/12.0.6-0ubuntu0.16.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  [i965 gen7][regression][patch]Intel mesa driver raises SIGFPE.

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Yakkety:
  Fix Released

Bug description:
  There was a regression in intel mesa driver that caused raise of
  SIGFPE signal which resulted in startup error messages (about division
  by zero or invalid floating point operation) in some applications and
  games sensitive to this behavior.

  Currently it resolved in upstream:
  https://bugs.freedesktop.org/show_bug.cgi?id=95419
  By following commit:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=01c89ccc5d1529aa1efbae80c8ef641a59abbd93
  Is it possible to include foregoing patch to avoid bug in current 
distributions?

  Distribution: Ubuntu 16.04
  Video card: Intel HD 4600
  Mesa version: 11.2.0-1ubuntu2.2

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

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

[Touch-packages] [Bug 1647016] Re: SRU of LXC 1.0.9 (upstream bugfix release)

[Adam Conrad]

Hello Stéphane, or anyone else affected,

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

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

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

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

** Tags removed: verification-failed

** Tags added: verification-needed

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

Title:
  SRU of LXC 1.0.9 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Invalid
Status in lxc source package in Precise:
  In Progress
Status in lxc source package in Trusty:
  Fix Committed

Bug description:
  LXC upstream released LXC 1.0.9 as a bugfix release with following
  changelog:

   - Security fix for CVE-2016-8649
   - utils: make detect_ramfs_rootfs() return bool
   - tests: add test for detect_ramfs_rootfs()
   - add Documentation entries to lxc and lxc@ units
   - mark the python examples as having utf-8 encoding
   - log: sanity check the returned value from snprintf()
   - lxc-alpine: mount /dev/shm as tmpfs
   - archlinux: Do DHCP on eth0
   - archlinux: Fix resolving
   - Drop leftover references to lxc_strerror()
   - tests: fix image download for s390x
   - tools: fix coding style in lxc_attach
   - tools: make overlay valid backend
   - tools: better error reporting for lxc-start
   - alpine: Fix installing extra packages
   - lxc-alpine: do not drop setfcap
   - s390x: Fix seccomp handling of personalities
   - tools: correct the argument typo in lxc_copy
   - Use libtool for liblxc.so
   - c/r: use --external instead of --veth-pair
   - c/r: remember to increment netnr
   - c/r: add checkpoint/restore support for macvlan interfaces
   - ubuntu: Fix package upgrades requiring proc
   - c/r: drop duplicate hunk from macvlan case
   - c/r: use snprintf to compute device name
   - Tweak libtool handling to work with Android
   - tests: add lxc_error() and lxc_debug()
   - container start: clone newcgroup immediately
   - use python3_sitearch for including the python code
   - fix rpm build, include all built files, but only once
   - cgfs: fix invalid free()
   - find OpenSUSE's build also as obs-build
   - improve help text for --fancy and --fancy-format
   - improve wording of the help page for lxc-ls
   - cgfs: add print_cgfs_init_debuginfo()
   - cgfs: skip empty entries under /proc/self/cgroup
   - cgfs: explicitly check for NULL
   - tools: use correct exit code for lxc-stop
   - c/r: explicitly emit bind mounts as criu arguments
   - log: bump LXC_LOG_BUFFER_SIZE to 4096
   - conf: merge network namespace move & rename on shutdown
   - c/r: save criu's stdout during dump too
   - c/r: remove extra \ns from logs
   - c/r: fix off-by-one error
   - c/r: check state before doing a checkpoint/restore
   - start: CLONE_NEWCGROUP after we have setup cgroups
   - create symlink for /var/run
   - utils: add lxc_append_string()
   - cgroups: remove isolated cpus from cpuset.cpus
   - Update Ubuntu release name: add zesty and remove wily
   - templates: add squashfs support to lxc-ubuntu-cloud.in
   - cgroups: skip v2 hierarchy entry
   - also stop lxc-net in runlevels 0 and 6
   - add lxc.egg-info to gitignore
   - install bash completion where pkg-config tells us to
   - conf: do not use %m format specifier
   - debian: Don't depend on libui-dialog-perl
   - cgroups: use %zu format specifier to print size_t
   - lxc-checkpoint: automatically detect if --external or --veth-pair
   - cgroups: prevent segfault in cgfsng
   - utils: add lxc_preserve_ns()
   - start: add netnsfd to lxc_handler
   - conf: use lxc_preserve_ns()
   - attach: use lxc_preserve_ns()
   - lxc_user_nic: use lxc_preserve_ns()
   - conf, start: improve log output
   - conf: explicitly remove veth device from host
   - conf, start: be smarter when deleting networks
   - start, utils: improve preserve_ns()
   - start, error: improve log + non-functional changes
   - start, namespace: move ns_info to namespace.{c,h}
   - attach, utils: bugfixes
   - attach: use ns_info[LXC_NS_MAX] struct
   - namespace: always attach to user namespace first
   - cgroup: improve isolcpus handling
   - 

[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports

[Adam Conrad]

Third option: Tell users who are bothered by this misfeature to upgrade
to Xenial.   "I don't like these ports being in use" isn't a bug, per
se, and our goal should not be to backport exact feature parity from
Xenial to Trusty.  We release new releases for a variety of reasons, and
this is one of them.

I understand the compulsion to always make every LTS "look and behave
the same", but there are points of diminishing returns, and this is one
of them.  To quote pitti (on another backporting topic), "if this is
really what we want, why don't we just symlink trusty to xenial?"

If there was a bug to be fixed here, sure, let's fix it, but I don't see
one worth fixing.  Long-time trusty users have been at this for over 2.5
years, and I don't see a flood of people complaining about these random
ports, while Xenial has been out for over half a year now, and the few
people genuinely irritated can, well, use Xenial.

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to take 
the sysctl values into account (net.ipv4.ip_local_port_range & 
net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion 
isc-dhcp upstream doesn't want to rely on kernel for randomization.
   
  There is no realtime configuration to disable the feature or workaround this. 
The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  
  [Regression Potential] 

  * none expected

  I did the split such that users will automatically get isc-dhcp-client-ddns 
installed but users bothered by this bug then will have the option to switch to 
the one without it by uninstalling (isc-dhcp-client-ddns), 
  so existing Trusty users can continue to use this DDNS functionality after 
the SRU without any necessary intervention.

  With  isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  Without isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc

  Note that this is how Xenial does it.

  [Other Info]
   
   * See : 
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/comments/19 to 
look at my discussion with rbasak on if that approach would be acceptable for 
SRU.

  [Original Description]

  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of 

[Touch-packages] [Bug 1649959] Re: unattended upgrade of apt kills running apt-daily job

[Adam Conrad]

Hello Chaskiel, or anyone else affected,

Accepted apt into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.3.3 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: apt (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  unattended upgrade of apt kills running apt-daily job

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Causes automatic upgrades by unattended-upgrades to be interrupted if apt is 
configured, leaving the system in a partially configured state.

  [Test case]
  Install apt - make sure the apt-daily.service is not restarted (this systemd 
service runs unattended-upgrades)

  [Regression Potential] 
  It's only overriding dh_systemd_start to not be called for the service, so I 
don't see any possibility for regressions.

  [Original Bug report]
  This morning, I discovered that my new xenial system had attempted an 
unattended upgrade overnight but the upgrade was incomplete. It attempted to 
upgrade
  apt apt-transport-https apt-utils firefox firefox-locale-en 
flashplugin-installer libapt-inst2.0 libapt-pkg5.0 libgme0

  but the unattended-upgrades-dpkg.log log terminates after apt is
  configured.

  I had to dpkg --configure --pending and apt-get -f install to get apt back 
into working order.
  There were no errors, crashes or cores logged.

  The journal indicates that apt-daily.service stopped and restarted around the 
time of the upgrade, so I am assuming that is the problem (that systemd killed 
the update session as the result of an update to the unit files)
  ---
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-12-06 (7 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NonfreeKernelModules: openafs
  Package: apt 1.3.2ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Tags:  yakkety
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1592817] Re: gdebi-gtk crashed with ValueError in update_interface(): could not convert string to float: '0, 0000'

[Adam Conrad]

Hello Jimmy, or anyone else affected,

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

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

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

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

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

** Tags added: verification-needed

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

Title:
  gdebi-gtk crashed with ValueError in update_interface(): could not
  convert string to float: '0,'

Status in apt package in Ubuntu:
  Fix Released
Status in gdebi package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Fix Committed
Status in gdebi source package in Xenial:
  Confirmed

Bug description:
  Errors Bucket
  -
  https://errors.ubuntu.com/problem/31a80b4c477107c659b93a4277ed46c14a3c8c53
  and
  https://errors.ubuntu.com/problem/c349b36522b1d43e2604357f75f0215fdafe1c7a

  [Impact]
  Crashes of gdebi (and possibly other tools) in non-English locales which use 
1,0 or similar instead of 1.0

  [Test case]
  Install a deb package with gdebi, like Google Chrome, in such a locale.

  Original: Gdebi crashed while installing Google Chrome .deb-fil bur
  the error didn't appear until I logged out and back in again

  [Regression potential]
  Same as bug 1611010 - very low.

  
  ProblemType: CrashDistroRelease: Ubuntu 16.10
  Package: gdebi 0.9.5.7ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
  Uname: Linux 4.4.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 15 15:01:11 2016
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationDate: Installed on 2016-06-15 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160511)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive 
/media/jimmy/Seagate\ Backup\ Plus\ 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb
  ProcEnviron:
   PATH=(custom, no user)
   LANG=da_DK.UTF-8
   LANGUAGE=da
   SHELL=/bin/bash
   TERM=unknown
  PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/media/jimmy/Seagate 
Backup Plus 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb']SourcePackage: 
gdebi
  Title: gdebi-gtk crashed with ValueError in update_interface(): could not 
convert string to float: '0,'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''

[Adam Conrad]

Hello Victor, or anyone else affected,

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

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

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

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

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

** Tags added: verification-needed

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

Title:
  yakkety desktop - non-english installation crashes with
  /plugininstall.py: ValueError: invalid literal for int() with base 10:
  ''

Status in apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Fix Committed
Status in ubiquity source package in Xenial:
  Triaged

Bug description:
  Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com
  /daily-live/current/

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Preconditions: W10+Xenial xerus installed, internet connection, 3rd
  party sw and updates selected

  [Impact]
  Breaks installation in some non-English locales.

  [Test case]
  Steps to reproduce:

  1º Click something else on Installation type screen>select /dev/sdaX where 
Xenial is installed, use it to mount / and leave some space to create the /home 
partition(ext4)
  2º Then click back and select erase ubuntu 16.04.1 and install Yakkety
  3º Installation starts

  Current result: After a little time installing it crashes and a window
  shows up to let the user know that some info is being gathered to send
  it to developers, and finally firefox opens on the bug report web on
  ubiquity package

  Expected result: No crashes during installation

  [Regression potential]
  Very low, we're running this in 1.3 since a long time. The fix depends on 
another one that restricts the Date parser to accept only UTC time zones in 
Release files, though (we do not understand the other ones anyway), and thus 
might reject some repositories it silently accepted in a wrong way previously 
(we have not seen anyone report a regression yet since uploading that in June).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubiquity 16.10.5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Aug  8 15:50:56 2016
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808)
  ProcEnviron:
   LANGUAGE=es_ES.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1593583] Re: Invalid 'Date' entry in Release file /var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_yakkety-proposed_InRelease

[Adam Conrad]

Hello dino99, or anyone else affected,

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

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

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

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

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

** Tags added: verification-needed

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

Title:
  Invalid 'Date' entry in Release file
  /var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_yakkety-
  proposed_InRelease

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  New

Bug description:
  Continuously get that warning when using synaptic to reload the
  sources. This happen with apt 1.3-exp2 only.

  This seems a regression as per that old report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809329

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3~exp2
  ProcVersionSignature: Ubuntu 4.6.0-7.8-generic 4.6.0
  Uname: Linux 4.6.0-7-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jun 17 08:19:22 2016
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

  For the SRU:

  [Impact]
  Prevent adding this regression to 1.2.16
  [Test case]
  Parse (Release file with) date where hour is single digit
  [Regression potential]
  Should be very low, we are running this in yakkety too, and in Debian since 
quite some time.

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

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

[Touch-packages] [Bug 1641905] Re: Minor unit Test regression in 1.2.15

[Adam Conrad]

Hello Julian, or anyone else affected,

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

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

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

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

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

** Tags added: verification-needed

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

Title:
  Minor unit Test regression in 1.2.15

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  Fix Committed

Bug description:
  In 1.2.15 the unit tests (which run at build time) fail with an error
  message in the atomic files test, because I picked a commit that
  improved the error handling a bit (a previous error now propagates
  into further calls):

  /<>/test/libapt/fileutl_test.cc:376: Failure
  Value of: f.Close()
Actual: false
  Expected: true

  I'll revert that for 1.2.16, as it depends on another fix, and I'm not
  sure I really want those two in there.

  [Impact]
  * Causes unit test failure, but might not have real effects

  [Test Case]
  * Check that build output (which runs unit tests) contains no failure

  [Regression Potential]
  * None, we are just reverting a commit from 1.2.15, so we have the same as in 
1.2.14

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

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

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

[Adam Conrad]

Hello Seth, or anyone else affected,

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

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

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

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

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

** Tags added: verification-needed

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed

Bug description:
  [Summary]

  A regression in apt in Xenial 1.2.15 causes "apt-get update" to fail
  with "At least one invalid signature was encountered." if there are
  files in /etc/apt/trusted.gpg.d/ that are not readable by the _apt
  user.

  This has the consequence of getting apt "stuck"; it will not be able
  to download its own update that fixes the issue. This means that all
  affected users must apply the workaround; otherwise they will be stuck
  forever.

  [Workaround]

  Make sure all files in /etc/apt/trusted.gpg.d/ are world-readable. For
  example: "sudo chmod 644 /etc/apt/trusted.gpg.d/*". Then try "apt-get
  update" again.

  Alternatively, you can manually install the fixed version of apt using
  dpkg.

  [Impact]
  Breaks update on systems with unreadable GPG keys

  [Test case]
  Run apt update with an unreadable GPG key file in trusted.gpg.d. This should 
work and (stretch goal) print a warning about the key being unreadable.

  [Regression potential]
  Low risk. We check that very situation in the automated test suite now like 
we did a lot of other situations before. The fix has been available in apt 
since 1.3_rc3 on Aug 30, and there have been no regressions reported since then.

  [Original bug report]
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease
  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease
  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease
  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]
  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]
  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]
  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease
  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB]
  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease
  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]
  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]
  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease
    At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease
  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease
    At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]
  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease
    At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease
  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]
  Hit:17 http://security.debian.org wheezy/updates InRelease
  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]
  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease
  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease
  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease
  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease
    At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease
  

[Touch-packages] [Bug 1647832] Re: schroot sudo main: unable to allocate memory

[Adam Conrad]

Closing as invalid, sudo was having a sad due to a lack of virtual
filesystems being mounted in the chroot.

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

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

Title:
  schroot sudo main: unable to allocate memory

Status in sudo package in Ubuntu:
  Invalid

Bug description:
  Unable to use sudo within zesty armhf chroot on trusty arch64.
  Getting error unable to to allocate memory.

  
  $ sudo ls
  sudo: main: unable to allocate memory

  
  kernel - 4.4.0-38-generic
  release - Ubuntu 14.04.5 LTS
  system architecture - arm64
  chroot architecture - armhf

  
  sudo:
Installed: 1.8.9p5-1ubuntu1.3
Candidate: 1.8.9p5-1ubuntu1.3
Version table:
   *** 1.8.9p5-1ubuntu1.3 0
  500 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   1.8.9p5-1ubuntu1.1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ trusty-security/main arm64 
Packages
   1.8.9p5-1ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main arm64 Packages

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

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

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

[Adam Conrad]

"- fail quietly, gracefully, and quickly"

I'm not sure how a 2-second delay on login for people who firewall off
outside access can be qualified as "quickly".

I'm also skeptical in general here about this being a thing that should
be happening by default.

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

Title:
  add a motd script for news

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

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

  == SRU ==

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

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

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

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

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

[Touch-packages] [Bug 1644363] Re: [trusty/arm64] binutils segfaults on bash gettext configure test

[Adam Conrad]

Note that only the static build sees this segv, the non-static build
works fine.

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

Title:
  [trusty/arm64] binutils segfaults on bash gettext configure test

Status in binutils package in Ubuntu:
  Invalid
Status in binutils source package in Trusty:
  Confirmed

Bug description:
  On arm64, the bash gettext configure test causes binutils to segv:

  configure:8453: gcc -o conftest -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=
  format-security -Wall -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -static conftest.c  
  >&5
  conftest.c: In function 'main':
  conftest.c:116:8: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
  ^
  conftest.c:116:29: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
   ^
  collect2: error: ld terminated with signal 11 [Segmentation fault], core 
dumped
  configure:8453: $? = 1
  configure: failed program was:
  | /* confdefs.h */
  | #define PACKAGE_NAME "bash"
  | #define PACKAGE_TARNAME "bash"
  | #define PACKAGE_VERSION "4.3-release"
  | #define PACKAGE_STRING "bash 4.3-release"
  | #define PACKAGE_BUGREPORT "bug-b...@gnu.org"
  | #define PACKAGE_URL ""
  | #define ALIAS 1
  | #define PUSHD_AND_POPD 1
  | #define RESTRICTED_SHELL 1
  | #define PROCESS_SUBSTITUTION 1
  | #define PROMPT_STRING_DECODE 1
  | #define SELECT_COMMAND 1
  | #define HELP_BUILTIN 1
  | #define ARRAY_VARS 1
  | #define DPAREN_ARITHMETIC 1
  | #define BRACE_EXPANSION 1
  | #define COMMAND_TIMING 1
  | #define EXTENDED_GLOB 1
  | #define EXTGLOB_DEFAULT 0
  | #define COND_COMMAND 1
  | #define COND_REGEXP 1
  | #define COPROCESS_SUPPORT 1
  | #define ARITH_FOR_COMMAND 1
  | #define NETWORK_REDIRECTIONS 1
  | #define PROGRAMMABLE_COMPLETION 1
  | #define DEBUGGER 1
  | #define CASEMOD_ATTRS 1
  | #define CASEMOD_EXPANSIONS 1
  | #define GLOBASCII_DEFAULT 0
  | #define MEMSCRAMBLE 1
  | #define STDC_HEADERS 1
  | #define HAVE_SYS_TYPES_H 1
  | #define HAVE_SYS_STAT_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_MEMORY_H 1
  | #define HAVE_STRINGS_H 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_STDINT_H 1
  | #define HAVE_UNISTD_H 1
  | #define __EXTENSIONS__ 1
  | #define _ALL_SOURCE 1
  | #define _GNU_SOURCE 1
  | #define _POSIX_PTHREAD_SEMANTICS 1
  | #define _TANDEM_SOURCE 1
  | #define READLINE 1
  | #define HISTORY 1
  | #define BANG_HISTORY 1
  | #define _GNU_SOURCE 1
  | #define HAVE_STRINGIZE 1
  | #define HAVE_LONG_DOUBLE_WIDER 1
  | #define HAVE_LONG_DOUBLE 1
  | #define PROTOTYPES 1
  | #define __PROTOTYPES 1
  | #define restrict __restrict
  | #define HAVE_ALLOCA_H 1
  | #define HAVE_ALLOCA 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_SYS_PARAM_H 1
  | #define HAVE_SYS_TIME_H 1
  | #define HAVE_GETPAGESIZE 1
  | #define HAVE_MMAP 1
  | #define INTDIV0_RAISES_SIGFPE 0
  | #define HAVE_INTTYPES_H_WITH_UINTMAX 1
  | #define HAVE_STDINT_H_WITH_UINTMAX 1
  | #define HAVE_UNSIGNED_LONG_LONG 1
  | #define HAVE_UINTMAX_T 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_ARGZ_H 1
  | #define HAVE_LIMITS_H 1
  | #define HAVE_LOCALE_H 1
  | #define HAVE_NL_TYPES_H 1
  | #define HAVE_MALLOC_H 1
  | #define HAVE_STDDEF_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_SYS_PARAM_H 1
  | #define HAVE_FEOF_UNLOCKED 1
  | #define HAVE_FGETS_UNLOCKED 1
  | #define HAVE_GETC_UNLOCKED 1
  | #define HAVE_GETCWD 1
  | #define HAVE_GETEGID 1
  | #define HAVE_GETEUID 1
  | #define HAVE_GETGID 1
  | #define HAVE_GETUID 1
  | #define HAVE_MEMPCPY 1
  | #define HAVE_MUNMAP 1
  | #define HAVE_PUTENV 1
  | #define HAVE_SETENV 1
  | #define HAVE_SETLOCALE 1
  | #define HAVE_LOCALECONV 1
  | #define HAVE_STPCPY 1
  | #define HAVE_STRCASECMP 1
  | #define HAVE_STRDUP 1
  | #define HAVE_STRTOUL 1
  | #define HAVE_TSEARCH 1
  | #define HAVE___ARGZ_COUNT 1
  | #define HAVE___ARGZ_STRINGIFY 1
  | #define HAVE___ARGZ_NEXT 1
  | #define HAVE___FSETLOCKING 1
  | #define HAVE_ICONV 1
  | #define ICONV_CONST 
  | #define HAVE_LANGINFO_CODESET 1
  | #define HAVE_LC_MESSAGES 1
  | /* end confdefs.h.  */
  | #include 
  | extern int _nl_msg_cat_cntr;
  | extern int *_nl_domain_bindings;
  | int
  | main ()
  | {
  | bindtextdomain ("", "");
  | return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
  |   ;
  |   return 0;
  | }
  configure:8461: result: no

To manage notifications about this bug go to:

[Touch-packages] [Bug 1644363] Re: [trusty/arm64] binutils segfaults on bash gettext configure test

[Adam Conrad]

A failed build tree with config.log (successful in build-bash, failed in
build-static) can be found by people with rugby access at
rugby:~adconrad/bash-4.3

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

Title:
  [trusty/arm64] binutils segfaults on bash gettext configure test

Status in binutils package in Ubuntu:
  Invalid
Status in binutils source package in Trusty:
  Confirmed

Bug description:
  On arm64, the bash gettext configure test causes binutils to segv:

  configure:8453: gcc -o conftest -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=
  format-security -Wall -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -static conftest.c  
  >&5
  conftest.c: In function 'main':
  conftest.c:116:8: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
  ^
  conftest.c:116:29: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
   ^
  collect2: error: ld terminated with signal 11 [Segmentation fault], core 
dumped
  configure:8453: $? = 1
  configure: failed program was:
  | /* confdefs.h */
  | #define PACKAGE_NAME "bash"
  | #define PACKAGE_TARNAME "bash"
  | #define PACKAGE_VERSION "4.3-release"
  | #define PACKAGE_STRING "bash 4.3-release"
  | #define PACKAGE_BUGREPORT "bug-b...@gnu.org"
  | #define PACKAGE_URL ""
  | #define ALIAS 1
  | #define PUSHD_AND_POPD 1
  | #define RESTRICTED_SHELL 1
  | #define PROCESS_SUBSTITUTION 1
  | #define PROMPT_STRING_DECODE 1
  | #define SELECT_COMMAND 1
  | #define HELP_BUILTIN 1
  | #define ARRAY_VARS 1
  | #define DPAREN_ARITHMETIC 1
  | #define BRACE_EXPANSION 1
  | #define COMMAND_TIMING 1
  | #define EXTENDED_GLOB 1
  | #define EXTGLOB_DEFAULT 0
  | #define COND_COMMAND 1
  | #define COND_REGEXP 1
  | #define COPROCESS_SUPPORT 1
  | #define ARITH_FOR_COMMAND 1
  | #define NETWORK_REDIRECTIONS 1
  | #define PROGRAMMABLE_COMPLETION 1
  | #define DEBUGGER 1
  | #define CASEMOD_ATTRS 1
  | #define CASEMOD_EXPANSIONS 1
  | #define GLOBASCII_DEFAULT 0
  | #define MEMSCRAMBLE 1
  | #define STDC_HEADERS 1
  | #define HAVE_SYS_TYPES_H 1
  | #define HAVE_SYS_STAT_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_MEMORY_H 1
  | #define HAVE_STRINGS_H 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_STDINT_H 1
  | #define HAVE_UNISTD_H 1
  | #define __EXTENSIONS__ 1
  | #define _ALL_SOURCE 1
  | #define _GNU_SOURCE 1
  | #define _POSIX_PTHREAD_SEMANTICS 1
  | #define _TANDEM_SOURCE 1
  | #define READLINE 1
  | #define HISTORY 1
  | #define BANG_HISTORY 1
  | #define _GNU_SOURCE 1
  | #define HAVE_STRINGIZE 1
  | #define HAVE_LONG_DOUBLE_WIDER 1
  | #define HAVE_LONG_DOUBLE 1
  | #define PROTOTYPES 1
  | #define __PROTOTYPES 1
  | #define restrict __restrict
  | #define HAVE_ALLOCA_H 1
  | #define HAVE_ALLOCA 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_SYS_PARAM_H 1
  | #define HAVE_SYS_TIME_H 1
  | #define HAVE_GETPAGESIZE 1
  | #define HAVE_MMAP 1
  | #define INTDIV0_RAISES_SIGFPE 0
  | #define HAVE_INTTYPES_H_WITH_UINTMAX 1
  | #define HAVE_STDINT_H_WITH_UINTMAX 1
  | #define HAVE_UNSIGNED_LONG_LONG 1
  | #define HAVE_UINTMAX_T 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_ARGZ_H 1
  | #define HAVE_LIMITS_H 1
  | #define HAVE_LOCALE_H 1
  | #define HAVE_NL_TYPES_H 1
  | #define HAVE_MALLOC_H 1
  | #define HAVE_STDDEF_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_SYS_PARAM_H 1
  | #define HAVE_FEOF_UNLOCKED 1
  | #define HAVE_FGETS_UNLOCKED 1
  | #define HAVE_GETC_UNLOCKED 1
  | #define HAVE_GETCWD 1
  | #define HAVE_GETEGID 1
  | #define HAVE_GETEUID 1
  | #define HAVE_GETGID 1
  | #define HAVE_GETUID 1
  | #define HAVE_MEMPCPY 1
  | #define HAVE_MUNMAP 1
  | #define HAVE_PUTENV 1
  | #define HAVE_SETENV 1
  | #define HAVE_SETLOCALE 1
  | #define HAVE_LOCALECONV 1
  | #define HAVE_STPCPY 1
  | #define HAVE_STRCASECMP 1
  | #define HAVE_STRDUP 1
  | #define HAVE_STRTOUL 1
  | #define HAVE_TSEARCH 1
  | #define HAVE___ARGZ_COUNT 1
  | #define HAVE___ARGZ_STRINGIFY 1
  | #define HAVE___ARGZ_NEXT 1
  | #define HAVE___FSETLOCKING 1
  | #define HAVE_ICONV 1
  | #define ICONV_CONST 
  | #define HAVE_LANGINFO_CODESET 1
  | #define HAVE_LC_MESSAGES 1
  | /* end confdefs.h.  */
  | #include 
  | extern int _nl_msg_cat_cntr;
  | extern int *_nl_domain_bindings;
  | int
  | main ()
  | {
  | bindtextdomain ("", "");
  | return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
  |   ;
  |   return 0;
  | }
  configure:8461: result: no

To manage notifications about this bug 

[Touch-packages] [Bug 1644363] Re: [trusty/arm64] binutils segfaults on bash gettext configure test

[Adam Conrad]

Also, this didn't happen in the release pocket, so it's a regression in
an SRU of binutils (or gcc feeding it garbage, possibly).

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

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

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

Title:
  [trusty/arm64] binutils segfaults on bash gettext configure test

Status in binutils package in Ubuntu:
  Invalid
Status in binutils source package in Trusty:
  Confirmed

Bug description:
  On arm64, the bash gettext configure test causes binutils to segv:

  configure:8453: gcc -o conftest -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=
  format-security -Wall -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -static conftest.c  
  >&5
  conftest.c: In function 'main':
  conftest.c:116:8: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
  ^
  conftest.c:116:29: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
   ^
  collect2: error: ld terminated with signal 11 [Segmentation fault], core 
dumped
  configure:8453: $? = 1
  configure: failed program was:
  | /* confdefs.h */
  | #define PACKAGE_NAME "bash"
  | #define PACKAGE_TARNAME "bash"
  | #define PACKAGE_VERSION "4.3-release"
  | #define PACKAGE_STRING "bash 4.3-release"
  | #define PACKAGE_BUGREPORT "bug-b...@gnu.org"
  | #define PACKAGE_URL ""
  | #define ALIAS 1
  | #define PUSHD_AND_POPD 1
  | #define RESTRICTED_SHELL 1
  | #define PROCESS_SUBSTITUTION 1
  | #define PROMPT_STRING_DECODE 1
  | #define SELECT_COMMAND 1
  | #define HELP_BUILTIN 1
  | #define ARRAY_VARS 1
  | #define DPAREN_ARITHMETIC 1
  | #define BRACE_EXPANSION 1
  | #define COMMAND_TIMING 1
  | #define EXTENDED_GLOB 1
  | #define EXTGLOB_DEFAULT 0
  | #define COND_COMMAND 1
  | #define COND_REGEXP 1
  | #define COPROCESS_SUPPORT 1
  | #define ARITH_FOR_COMMAND 1
  | #define NETWORK_REDIRECTIONS 1
  | #define PROGRAMMABLE_COMPLETION 1
  | #define DEBUGGER 1
  | #define CASEMOD_ATTRS 1
  | #define CASEMOD_EXPANSIONS 1
  | #define GLOBASCII_DEFAULT 0
  | #define MEMSCRAMBLE 1
  | #define STDC_HEADERS 1
  | #define HAVE_SYS_TYPES_H 1
  | #define HAVE_SYS_STAT_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_MEMORY_H 1
  | #define HAVE_STRINGS_H 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_STDINT_H 1
  | #define HAVE_UNISTD_H 1
  | #define __EXTENSIONS__ 1
  | #define _ALL_SOURCE 1
  | #define _GNU_SOURCE 1
  | #define _POSIX_PTHREAD_SEMANTICS 1
  | #define _TANDEM_SOURCE 1
  | #define READLINE 1
  | #define HISTORY 1
  | #define BANG_HISTORY 1
  | #define _GNU_SOURCE 1
  | #define HAVE_STRINGIZE 1
  | #define HAVE_LONG_DOUBLE_WIDER 1
  | #define HAVE_LONG_DOUBLE 1
  | #define PROTOTYPES 1
  | #define __PROTOTYPES 1
  | #define restrict __restrict
  | #define HAVE_ALLOCA_H 1
  | #define HAVE_ALLOCA 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_SYS_PARAM_H 1
  | #define HAVE_SYS_TIME_H 1
  | #define HAVE_GETPAGESIZE 1
  | #define HAVE_MMAP 1
  | #define INTDIV0_RAISES_SIGFPE 0
  | #define HAVE_INTTYPES_H_WITH_UINTMAX 1
  | #define HAVE_STDINT_H_WITH_UINTMAX 1
  | #define HAVE_UNSIGNED_LONG_LONG 1
  | #define HAVE_UINTMAX_T 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_ARGZ_H 1
  | #define HAVE_LIMITS_H 1
  | #define HAVE_LOCALE_H 1
  | #define HAVE_NL_TYPES_H 1
  | #define HAVE_MALLOC_H 1
  | #define HAVE_STDDEF_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_SYS_PARAM_H 1
  | #define HAVE_FEOF_UNLOCKED 1
  | #define HAVE_FGETS_UNLOCKED 1
  | #define HAVE_GETC_UNLOCKED 1
  | #define HAVE_GETCWD 1
  | #define HAVE_GETEGID 1
  | #define HAVE_GETEUID 1
  | #define HAVE_GETGID 1
  | #define HAVE_GETUID 1
  | #define HAVE_MEMPCPY 1
  | #define HAVE_MUNMAP 1
  | #define HAVE_PUTENV 1
  | #define HAVE_SETENV 1
  | #define HAVE_SETLOCALE 1
  | #define HAVE_LOCALECONV 1
  | #define HAVE_STPCPY 1
  | #define HAVE_STRCASECMP 1
  | #define HAVE_STRDUP 1
  | #define HAVE_STRTOUL 1
  | #define HAVE_TSEARCH 1
  | #define HAVE___ARGZ_COUNT 1
  | #define HAVE___ARGZ_STRINGIFY 1
  | #define HAVE___ARGZ_NEXT 1
  | #define HAVE___FSETLOCKING 1
  | #define HAVE_ICONV 1
  | #define ICONV_CONST 
  | #define HAVE_LANGINFO_CODESET 1
  | #define HAVE_LC_MESSAGES 1
  | /* end confdefs.h.  */
  | #include 
  | extern int _nl_msg_cat_cntr;
  | extern int *_nl_domain_bindings;
  | int
  | main ()
  | {
  | bindtextdomain ("", "");
  | return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 

[Touch-packages] [Bug 1644363] Re: [trusty/arm64] binutils segfaults on bash gettext configure test

[Adam Conrad]

ii  binutils 2.24-5ubuntu14.1   
 arm64GNU assembler, linker and binary utilities
ii  gcc-4.8  4.8.4-2ubuntu1~14.04.3 
 arm64GNU C compiler
ii  libc6:arm64  2.19-0ubuntu6.9
 arm64Embedded GNU C Library: Shared libraries
ii  libc6-dev:arm64  2.19-0ubuntu6.9
 arm64Embedded GNU C Library: Development Libraries and Header Files


** Also affects: binutils (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  [trusty/arm64] binutils segfaults on bash gettext configure test

Status in binutils package in Ubuntu:
  Invalid
Status in binutils source package in Trusty:
  Confirmed

Bug description:
  On arm64, the bash gettext configure test causes binutils to segv:

  configure:8453: gcc -o conftest -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=
  format-security -Wall -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -static conftest.c  
  >&5
  conftest.c: In function 'main':
  conftest.c:116:8: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
  ^
  conftest.c:116:29: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
   ^
  collect2: error: ld terminated with signal 11 [Segmentation fault], core 
dumped
  configure:8453: $? = 1
  configure: failed program was:
  | /* confdefs.h */
  | #define PACKAGE_NAME "bash"
  | #define PACKAGE_TARNAME "bash"
  | #define PACKAGE_VERSION "4.3-release"
  | #define PACKAGE_STRING "bash 4.3-release"
  | #define PACKAGE_BUGREPORT "bug-b...@gnu.org"
  | #define PACKAGE_URL ""
  | #define ALIAS 1
  | #define PUSHD_AND_POPD 1
  | #define RESTRICTED_SHELL 1
  | #define PROCESS_SUBSTITUTION 1
  | #define PROMPT_STRING_DECODE 1
  | #define SELECT_COMMAND 1
  | #define HELP_BUILTIN 1
  | #define ARRAY_VARS 1
  | #define DPAREN_ARITHMETIC 1
  | #define BRACE_EXPANSION 1
  | #define COMMAND_TIMING 1
  | #define EXTENDED_GLOB 1
  | #define EXTGLOB_DEFAULT 0
  | #define COND_COMMAND 1
  | #define COND_REGEXP 1
  | #define COPROCESS_SUPPORT 1
  | #define ARITH_FOR_COMMAND 1
  | #define NETWORK_REDIRECTIONS 1
  | #define PROGRAMMABLE_COMPLETION 1
  | #define DEBUGGER 1
  | #define CASEMOD_ATTRS 1
  | #define CASEMOD_EXPANSIONS 1
  | #define GLOBASCII_DEFAULT 0
  | #define MEMSCRAMBLE 1
  | #define STDC_HEADERS 1
  | #define HAVE_SYS_TYPES_H 1
  | #define HAVE_SYS_STAT_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_MEMORY_H 1
  | #define HAVE_STRINGS_H 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_STDINT_H 1
  | #define HAVE_UNISTD_H 1
  | #define __EXTENSIONS__ 1
  | #define _ALL_SOURCE 1
  | #define _GNU_SOURCE 1
  | #define _POSIX_PTHREAD_SEMANTICS 1
  | #define _TANDEM_SOURCE 1
  | #define READLINE 1
  | #define HISTORY 1
  | #define BANG_HISTORY 1
  | #define _GNU_SOURCE 1
  | #define HAVE_STRINGIZE 1
  | #define HAVE_LONG_DOUBLE_WIDER 1
  | #define HAVE_LONG_DOUBLE 1
  | #define PROTOTYPES 1
  | #define __PROTOTYPES 1
  | #define restrict __restrict
  | #define HAVE_ALLOCA_H 1
  | #define HAVE_ALLOCA 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_SYS_PARAM_H 1
  | #define HAVE_SYS_TIME_H 1
  | #define HAVE_GETPAGESIZE 1
  | #define HAVE_MMAP 1
  | #define INTDIV0_RAISES_SIGFPE 0
  | #define HAVE_INTTYPES_H_WITH_UINTMAX 1
  | #define HAVE_STDINT_H_WITH_UINTMAX 1
  | #define HAVE_UNSIGNED_LONG_LONG 1
  | #define HAVE_UINTMAX_T 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_ARGZ_H 1
  | #define HAVE_LIMITS_H 1
  | #define HAVE_LOCALE_H 1
  | #define HAVE_NL_TYPES_H 1
  | #define HAVE_MALLOC_H 1
  | #define HAVE_STDDEF_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_SYS_PARAM_H 1
  | #define HAVE_FEOF_UNLOCKED 1
  | #define HAVE_FGETS_UNLOCKED 1
  | #define HAVE_GETC_UNLOCKED 1
  | #define HAVE_GETCWD 1
  | #define HAVE_GETEGID 1
  | #define HAVE_GETEUID 1
  | #define HAVE_GETGID 1
  | #define HAVE_GETUID 1
  | #define HAVE_MEMPCPY 1
  | #define HAVE_MUNMAP 1
  | #define HAVE_PUTENV 1
  | #define HAVE_SETENV 1
  | #define HAVE_SETLOCALE 1
  | #define HAVE_LOCALECONV 1
  | #define HAVE_STPCPY 1
  | #define HAVE_STRCASECMP 1
  | #define HAVE_STRDUP 1
  | #define HAVE_STRTOUL 1
  | #define HAVE_TSEARCH 1
  | #define HAVE___ARGZ_COUNT 1
  | #define HAVE___ARGZ_STRINGIFY 1
  | #define HAVE___ARGZ_NEXT 1
  | #define 

[Touch-packages] [Bug 1644363] [NEW] [trusty/arm64] binutils segfaults on bash gettext configure test

[Adam Conrad]

Public bug reported:

On arm64, the bash gettext configure test causes binutils to segv:

configure:8453: gcc -o conftest -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=
format-security -Wall -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro 
-static conftest.c  
>&5
conftest.c: In function 'main':
conftest.c:116:8: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
 return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
^
conftest.c:116:29: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
 return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
 ^
collect2: error: ld terminated with signal 11 [Segmentation fault], core dumped
configure:8453: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "bash"
| #define PACKAGE_TARNAME "bash"
| #define PACKAGE_VERSION "4.3-release"
| #define PACKAGE_STRING "bash 4.3-release"
| #define PACKAGE_BUGREPORT "bug-b...@gnu.org"
| #define PACKAGE_URL ""
| #define ALIAS 1
| #define PUSHD_AND_POPD 1
| #define RESTRICTED_SHELL 1
| #define PROCESS_SUBSTITUTION 1
| #define PROMPT_STRING_DECODE 1
| #define SELECT_COMMAND 1
| #define HELP_BUILTIN 1
| #define ARRAY_VARS 1
| #define DPAREN_ARITHMETIC 1
| #define BRACE_EXPANSION 1
| #define COMMAND_TIMING 1
| #define EXTENDED_GLOB 1
| #define EXTGLOB_DEFAULT 0
| #define COND_COMMAND 1
| #define COND_REGEXP 1
| #define COPROCESS_SUPPORT 1
| #define ARITH_FOR_COMMAND 1
| #define NETWORK_REDIRECTIONS 1
| #define PROGRAMMABLE_COMPLETION 1
| #define DEBUGGER 1
| #define CASEMOD_ATTRS 1
| #define CASEMOD_EXPANSIONS 1
| #define GLOBASCII_DEFAULT 0
| #define MEMSCRAMBLE 1
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define __EXTENSIONS__ 1
| #define _ALL_SOURCE 1
| #define _GNU_SOURCE 1
| #define _POSIX_PTHREAD_SEMANTICS 1
| #define _TANDEM_SOURCE 1
| #define READLINE 1
| #define HISTORY 1
| #define BANG_HISTORY 1
| #define _GNU_SOURCE 1
| #define HAVE_STRINGIZE 1
| #define HAVE_LONG_DOUBLE_WIDER 1
| #define HAVE_LONG_DOUBLE 1
| #define PROTOTYPES 1
| #define __PROTOTYPES 1
| #define restrict __restrict
| #define HAVE_ALLOCA_H 1
| #define HAVE_ALLOCA 1
| #define HAVE_STDLIB_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_SYS_PARAM_H 1
| #define HAVE_SYS_TIME_H 1
| #define HAVE_GETPAGESIZE 1
| #define HAVE_MMAP 1
| #define INTDIV0_RAISES_SIGFPE 0
| #define HAVE_INTTYPES_H_WITH_UINTMAX 1
| #define HAVE_STDINT_H_WITH_UINTMAX 1
| #define HAVE_UNSIGNED_LONG_LONG 1
| #define HAVE_UINTMAX_T 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_ARGZ_H 1
| #define HAVE_LIMITS_H 1
| #define HAVE_LOCALE_H 1
| #define HAVE_NL_TYPES_H 1
| #define HAVE_MALLOC_H 1
| #define HAVE_STDDEF_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_SYS_PARAM_H 1
| #define HAVE_FEOF_UNLOCKED 1
| #define HAVE_FGETS_UNLOCKED 1
| #define HAVE_GETC_UNLOCKED 1
| #define HAVE_GETCWD 1
| #define HAVE_GETEGID 1
| #define HAVE_GETEUID 1
| #define HAVE_GETGID 1
| #define HAVE_GETUID 1
| #define HAVE_MEMPCPY 1
| #define HAVE_MUNMAP 1
| #define HAVE_PUTENV 1
| #define HAVE_SETENV 1
| #define HAVE_SETLOCALE 1
| #define HAVE_LOCALECONV 1
| #define HAVE_STPCPY 1
| #define HAVE_STRCASECMP 1
| #define HAVE_STRDUP 1
| #define HAVE_STRTOUL 1
| #define HAVE_TSEARCH 1
| #define HAVE___ARGZ_COUNT 1
| #define HAVE___ARGZ_STRINGIFY 1
| #define HAVE___ARGZ_NEXT 1
| #define HAVE___FSETLOCKING 1
| #define HAVE_ICONV 1
| #define ICONV_CONST 
| #define HAVE_LANGINFO_CODESET 1
| #define HAVE_LC_MESSAGES 1
| /* end confdefs.h.  */
| #include 
| extern int _nl_msg_cat_cntr;
| extern int *_nl_domain_bindings;
| int
| main ()
| {
| bindtextdomain ("", "");
| return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
|   ;
|   return 0;
| }
configure:8461: result: no

** Affects: binutils (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: binutils (Ubuntu Trusty)
 Importance: Undecided
 Status: Confirmed

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

Title:
  [trusty/arm64] binutils segfaults on bash gettext configure test

Status in binutils package in Ubuntu:
  Invalid
Status in binutils source package in Trusty:
  Confirmed

Bug description:
  On arm64, the bash gettext configure test causes binutils to segv:

  configure:8453: gcc -o conftest -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=
  format-security -Wall -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -static 

[Touch-packages] [Bug 1577460] Update Released

[Adam Conrad]

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

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

Title:
  mkinitramfs --help > Core dumped

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in glibc package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in glibc source package in Xenial:
  Fix Released
Status in util-linux source package in Xenial:
  New

Bug description:
  Problem Description
  ==
  root@zlin060:~# mkinitramfs --help
  Segmentation fault (core dumped)
  W: non-GNU getopt
  root@zlin060:~#

  == Comment: #9 - Heinz-Werner Seeck  - 
2016-05-02 10:09:34 ==
  With Ubuntu 14.40 login via ssh:

  Following cmd :
  'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help'

  Following call-stack occured (creates coredump):

  #0  __strncmp_c (s1=0x2e6575634a500a6d , 
  s1@entry=0x2e6575634a500a6a , 
  s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
  #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, 
argv=0x40, 
  optstring=0x20030 , longopts=, 
  longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
  #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=, 
  optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
  at getopt.c:1175
  #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=, 
  long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
  #4  0x02aa236821d8 in ?? ()
  #5  0x02aa23681c22 in main ()

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

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

[Touch-packages] [Bug 1621373] Update Released

[Adam Conrad]

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

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

Title:
  Turkey terminated DST

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Precise:
  Fix Released
Status in tzdata source package in Trusty:
  Fix Released
Status in tzdata source package in Xenial:
  Fix Released

Bug description:
  Hi,

  Turkey switched to permanent GMT+3 and terminated DST. Winter time
  changes will not applied at 2016-10-30.

  Turkish:
  Government publication: 
http://www.resmigazete.gov.tr/eskiler/2016/09/20160908-2.pdf
  http://aa.com.tr/tr/gunun-basliklari/kis-saati-uygulamasi-sona-erdi/642856

  English:
  
http://aa.com.tr/en/todays-headlines/turkey-to-implement-daylight-saving-time-year-round/642894

  The changes has been committed to tz project.
  https://github.com/eggert/tz/commit/3e31dbe52b8730ed762880e88bf4c68ac00b8cc3

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

[Adam Conrad]

** Also affects: initramfs-tools (Ubuntu Yakkety)
   Importance: High
 Assignee: Dave Chiluk (chiluk)
   Status: In Progress

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Yakkety:
  In Progress

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.

   * Discover that the device never comes up because, networking is not
  configured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.  This is common on
  machines that use nfsroot or otherwise pxe boot.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix.
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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

[Touch-packages] [Bug 1626245] Re: [MIR] fonts-android

[Adam Conrad]

** Changed in: fonts-android (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] fonts-android

Status in fonts-android package in Ubuntu:
  Fix Released

Bug description:
  Please include the fonts-android package in Ubuntu's component main.

  fonts-android includes the fonts-droid-fallback binary, and as a
  result of the discussion at bug 1625734, the server team wants that
  libgs9-common, which currently recommends fonts-noto-cjk, is changed
  to instead recommend fonts-droid-fallback.

  fonts-android is a Debian package and included in Debian's component
  main. It was included in Ubuntu's component main between trusty and
  wily.

  Bugs:

  http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=fonts-android

  https://bugs.launchpad.net/ubuntu/+source/fonts-android

  I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements,
  and haven't found any issues that would prevent the proposed main
  inclusion.

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

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

[Touch-packages] [Bug 1621373] Re: Turkey terminated DST

[Adam Conrad]

** Also affects: tzdata (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

** Also affects: tzdata (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

Title:
  Turkey terminated DST

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Precise:
  New
Status in tzdata source package in Trusty:
  New
Status in tzdata source package in Xenial:
  New

Bug description:
  Hi,

  Turkey switched to permanent GMT+3 and terminated DST. Winter time
  changes will not applied at 2016-10-30.

  Turkish:
  Government publication: 
http://www.resmigazete.gov.tr/eskiler/2016/09/20160908-2.pdf
  http://aa.com.tr/tr/gunun-basliklari/kis-saati-uygulamasi-sona-erdi/642856

  English:
  
http://aa.com.tr/en/todays-headlines/turkey-to-implement-daylight-saving-time-year-round/642894

  The changes has been committed to tz project.
  https://github.com/eggert/tz/commit/3e31dbe52b8730ed762880e88bf4c68ac00b8cc3

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

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

[Touch-packages] [Bug 1600000] Re: libnss-resolve treats two trailing dots on a domain name incorrectly

[Adam Conrad]

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/3978
   Importance: Unknown
   Status: Unknown

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

Title:
  libnss-resolve treats two trailing dots on a domain name incorrectly

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  208.118.235.148 STREAM wildebeest.gnu.org
  208.118.235.148 DGRAM  
  208.118.235.148 RAW
  (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ resolve dns/ dns/' 
/etc/nsswitch.conf 
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ dns/ resolve dns/' 
/etc/nsswitch.conf 
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  208.118.235.148 STREAM wildebeest.gnu.org
  208.118.235.148 DGRAM  
  208.118.235.148 RAW
  (base)adconrad@nosferatu:~$ 

  This is responsible for the new regression in glibc:

  --
  FAIL: posix/tst-getaddrinfo5
  original exit status 1
  resolving "localhost." worked, proceeding to test
  resolving "localhost.." failed, test passed
  resolving "www.gnu.org." worked, proceeding to test
  resolving "www.gnu.org.." worked, test failed
  --

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

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

[Touch-packages] [Bug 1613638] Re: [MIR] unity8

[Adam Conrad]

Demoting again, as unity8's dependencies are still winding through the
process.

** Changed in: unity8 (Ubuntu)
   Status: Fix Released => In Progress

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

Title:
  [MIR] unity8

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is planned for inclusion in main for 16.10

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has both unit tests and autopkgtests

  [Dependencies]
   The whole list of dependencies being MIR'ed is being tracked by 
https://trello.com/b/mab4G8UQ/unity-8-in-16-10
   * indicator-network [bug #1612619]
   * libusermetrics [bug #1612259]
   * pay-service [bug #1614202]
   * qmenumodel [bug #1612363]
   * qtmir [bug #1612358]
   * qtsystems-opensource-src [bug #1552860]
   * thumbnailer [bug #1613561]
   * ubuntu-settings-components [bug #1613640]
   * ubuntu-system-settings [bug #1612280]
   * unity-notifications [bug #1613678]
   * unity-scopes-api [bug #1612461]
   * unity-scopes-shell [bug #1612460]
   * unity-system-compositor [bug #1613601]
   Recommends:
   * unity-scope-click [bug #1614203]
   * unity-scope-mediascanner [bug #1218409]
   Potential to skip:
   * biometryd [https://trello.com/c/oP4UmB9t]
   * telephony-service [bug #1613490]

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images

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

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

[Touch-packages] [Bug 1600124] Re: Adjust KBL PCI-ID's

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted xserver-xorg-video-intel into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/xserver-xorg-video-intel/2:2.99.917+git20160325-1ubuntu1.1 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: xserver-xorg-video-intel (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Adjust KBL PCI-ID's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in libdrm source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Committed

Bug description:
  Current list of KBL PCI-ID's is incomplete, there are a few that are
  should not be listed and few that are missing. To fix this, adjust the
  list in kernel/libdrm/mesa/ddx to match upstream.

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

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

[Touch-packages] [Bug 1598212] Re: /etc/os-release: Please specify VERSION_CODENAME

[Adam Conrad]

** Changed in: base-files (Ubuntu)
   Status: New => Fix Committed

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

Title:
  /etc/os-release: Please specify VERSION_CODENAME

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

Bug description:
  [ SRU Justification ]
  UBUNTU_CODENAME was added by the snapd team, then proposed upstream in a more 
generic way.  Upstream settled on VERSION_CODENAME, and we should include that 
as well, in case third party (or, indeed, future versions of our own) software 
decide to start looking for it.

  [ SRU Test Case ]
  Check diffs of both source package and installed os-release, make sure 
nothing's changed except VERSION_CODENAME, and that the value is correct.

  [ Regression Potential ]
  Nein.

  [ Original Report ]
  The os-release specification was updated in systemd > 230 to also include a 
VERSION_CODENAME parameter: 
https://github.com/systemd/systemd/commit/646b997c118e261c5ececc434dd40d0dbdbac4d8

  Please replace the custom UBUNTU_CODENAME parameter by
  VERSION_CODENAME in yakkety and add VERSION_CODENAME to /etc/os-
  release to all stable releases.

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

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

[Touch-packages] [Bug 1598212] Re: /etc/os-release: Please specify VERSION_CODENAME

[Adam Conrad]

Likely need to keep both UBUNTU_CODENAME and VERSION_CODENAME in xenial
forever, to avoid having to add a (very) icky "Breaks: snapd (<< fixed-
version)" to base-files when we remove it.

Though, in the interest of correctness, I suppose that Breaks would also
be necessary in yakkety, but maybe we can get away with handwaving past
it, if it doesn't critically break snapd on upgrade.

** Changed in: base-files (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: base-files (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Description changed:

- The os-release specification was updated in systemd > 230 to also
- include a VERSION_CODENAME parameter:
- 
https://github.com/systemd/systemd/commit/646b997c118e261c5ececc434dd40d0dbdbac4d8
+ [ SRU Justification ]
+ UBUNTU_CODENAME was added by the snapd team, then proposed upstream in a more 
generic way.  Upstream settled on VERSION_CODENAME, and we should include that 
as well, in case third party (or, indeed, future versions of our own) software 
decide to start looking for it.
+ 
+ [ SRU Test Case ]
+ Check diffs of both source package and installed os-release, make sure 
nothing's changed except VERSION_CODENAME, and that the value is correct.
+ 
+ [ Regression Potential ]
+ Nein.
+ 
+ [ Original Report ]
+ The os-release specification was updated in systemd > 230 to also include a 
VERSION_CODENAME parameter: 
https://github.com/systemd/systemd/commit/646b997c118e261c5ececc434dd40d0dbdbac4d8
  
  Please replace the custom UBUNTU_CODENAME parameter by VERSION_CODENAME
  in yakkety and add VERSION_CODENAME to /etc/os-release to all stable
  releases.

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

Title:
  /etc/os-release: Please specify VERSION_CODENAME

Status in base-files package in Ubuntu:
  New
Status in base-files source package in Xenial:
  New
Status in base-files package in Debian:
  New

Bug description:
  [ SRU Justification ]
  UBUNTU_CODENAME was added by the snapd team, then proposed upstream in a more 
generic way.  Upstream settled on VERSION_CODENAME, and we should include that 
as well, in case third party (or, indeed, future versions of our own) software 
decide to start looking for it.

  [ SRU Test Case ]
  Check diffs of both source package and installed os-release, make sure 
nothing's changed except VERSION_CODENAME, and that the value is correct.

  [ Regression Potential ]
  Nein.

  [ Original Report ]
  The os-release specification was updated in systemd > 230 to also include a 
VERSION_CODENAME parameter: 
https://github.com/systemd/systemd/commit/646b997c118e261c5ececc434dd40d0dbdbac4d8

  Please replace the custom UBUNTU_CODENAME parameter by
  VERSION_CODENAME in yakkety and add VERSION_CODENAME to /etc/os-
  release to all stable releases.

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

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

[Touch-packages] [Bug 1598212] Re: /etc/os-release: Please specify VERSION_CODENAME

[Adam Conrad]

** Also affects: base-files (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  /etc/os-release: Please specify VERSION_CODENAME

Status in base-files package in Ubuntu:
  New
Status in base-files source package in Xenial:
  New
Status in base-files package in Debian:
  New

Bug description:
  The os-release specification was updated in systemd > 230 to also
  include a VERSION_CODENAME parameter:
  
https://github.com/systemd/systemd/commit/646b997c118e261c5ececc434dd40d0dbdbac4d8

  Please replace the custom UBUNTU_CODENAME parameter by
  VERSION_CODENAME in yakkety and add VERSION_CODENAME to /etc/os-
  release to all stable releases.

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

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

[Touch-packages] [Bug 1611203] Re: Failed to share folder via Samba

[Adam Conrad]

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

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

Title:
  Failed to share folder via Samba

Status in apt package in Ubuntu:
  New

Bug description:
  Right click folder
  Select to share
  was asked to install additional packages
  installation failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: grub2-common 2.02~beta2-36ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  CrashReports:
   640:999:116:2469178:2016-08-08 19:56:52.363672483 +0200:2016-08-08 
19:56:47.068153600 +0200:/var/crash/_usr_bin_compiz.999.crash
   600:0:116:388676:2016-08-09 06:40:32.688627958 +0200:2016-08-09 
06:40:33.688627958 +0200:/var/crash/grub2-common.0.crash
   600:0:116:387630:2016-08-09 06:40:33.600633678 +0200:2016-08-09 
06:40:33.572635511 +0200:/var/crash/libfuse2:amd64.0.crash
   600:0:116:388674:2016-08-09 06:40:33.628631845 +0200:2016-08-09 
06:40:33.600633678 +0200:/var/crash/grub-common.0.crash
  Date: Tue Aug  9 06:40:33 2016
  DuplicateSignature:
   package:grub2-common:2.02~beta2-36ubuntu3.2
   Processing triggers for ufw (0.35-0ubuntu2) ...
   dpkg: error processing package libfuse2:amd64 (--configure):
package libfuse2:amd64 is already installed and configured
  ErrorMessage: package grub2-common is already installed and configured
  InstallationDate: Installed on 2016-08-08 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: dpkg
  Title: package grub2-common 2.02~beta2-36ubuntu3.2 failed to install/upgrade: 
package grub2-common is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1544627] Re: systemd-udevd crashed with SIGABRT in __open_nocancel()

[Adam Conrad]

FWIW, this trips every time I write an ISO to a USB stick.

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

Title:
  systemd-udevd crashed with SIGABRT in __open_nocancel()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The computer was one... I was not even using it...

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: udev 228-5ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Thu Feb 11 14:59:05 2016
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2016-02-03 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: HP HP ZBook Studio G3
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic 
root=UUID=a9634764-1439-45e7-a0ca-8c2d030238e6 ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __open_nocancel () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/25/2015
  dmi.bios.vendor: HP
  dmi.bios.version: N82 Ver. 01.03
  dmi.board.name: 80D4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN82Ver.01.03:bd12/25/2015:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.38:cvnHP:ct10:cvr:
  dmi.product.name: HP ZBook Studio G3
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1608622] Re: 14.04.5 drops to initramfs prompt during boot with nvme drive

[Adam Conrad]

Hello David, or anyone else affected,

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

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

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

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

** Also affects: initramfs-tools (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Changed in: initramfs-tools (Ubuntu Trusty)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Changed in: initramfs-tools (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  14.04.5 drops to initramfs prompt during boot with nvme drive

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Trusty:
  Fix Committed

Bug description:
  So, installing 14.04.4 works fine, but systems with nvme drives don't
  boot after installing 14.04.5.

  Steps to reproduce:
  1) Install Ubuntu 14.04.5 on a system with an nvme drive
  2) reboot
  3) instead of booting to a graphical environment, there is an initramfs 
prompt.

  Notes: This also prevents reaching any of the recovery mode tools.

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

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

[Touch-packages] [Bug 1605117] Re: Unity greeter indicators don't show on second launch

[Adam Conrad]

Hello Roman, or anyone else affected,

Accepted lightdm into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.18.2-0ubuntu2 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: lightdm (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  Unity greeter indicators don't show on second launch

Status in Light Display Manager:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Unity Greeter indicators don't show second time greeter started.

  [Test Case]
  1. Log in with greeter
  2. Log out

  Expected result:
  Unity greeter is shown with all UI elements as in step 1.

  Observed result:
  Unity greeter is shown but only one indicator shows (accessibility)

  [Regression potential]
  Low. The fix was already present in the Bzr branch (removed some unneeded 
code that would accidentally close stdin). The fix was not released since it 
hadn't been shown to be a problem before this report.

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

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

[Touch-packages] [Bug 1577734] Re: Backport packages for 14.04.5 lts-xenial stack

[Adam Conrad]

Marking v-done, based on IRC feedback.

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

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Invalid
Status in x11proto-randr source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

[Touch-packages] [Bug 1577734] Update Released

[Adam Conrad]

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

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Invalid
Status in x11proto-randr source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

[Touch-packages] [Bug 1589204] Re: apt-get dist-upgrade and apt full-upgrade not reporting held back package

[Adam Conrad]

Tested precise, trusty, xenial, and yakkety.  Looks like this bug was
introduced between precise and trusty (that is, it works correctly in
precise's 0.8.16~exp12ubuntu10, but not trusty's 1.0.1ubuntu2 or later).

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

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

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

Title:
  apt-get dist-upgrade and apt full-upgrade not reporting held back
  package

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Trusty:
  New
Status in apt source package in Xenial:
  New

Bug description:
  I have the situation where a package cannot be upgraded because of missing 
dependencies.  However
  sudo apt-get dist-upgrade
  and
  sudo apt full-upgrade
  and
  sudo apt upgrade
  all show
  0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

  Only
  sudo apt-get upgrade
  shows
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

  I believe all of the above commands should show that 1 cannot be
  upgraded.

  This bug is not about the particular package I am trying to install, but 
about the way apt reports the problem.
  The details, for reference, are that I am trying to upgrade mosquitto from 
the mosquitto ppa.  After apt-get update I see
  $ apt-cache policy mosquitto
  mosquitto:
    Installed: 1.4.8-1build1
    Candidate: 1.4.9-0mosquitto1
    Version table:
   1.4.9-0mosquitto1 500
  500 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu 
xenial/main amd64 Packages
   *** 1.4.8-1build1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  but if I try to manually install mosquitto I get

  The following packages have unmet dependencies.
   mosquitto : Depends: libwebsockets3 (>= 1.2) but it is not installable

  and

  $ apt-cache policy libwebsockets3
  libwebsockets3:
    Installed: (none)
    Candidate: (none)
  Due to the fact that libwebsockets3 is not available for Xenial.
  As I said this bug is not about the problem with this particular package but 
about the fact that apt does not report that there is a package to be upgraded, 
but it cannot be done.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun  5 08:45:33 2016
  InstallationDate: Installed on 2014-10-21 (592 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-03-06 (90 days ago)

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

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

[Touch-packages] [Bug 1589204] Re: apt-get dist-upgrade and apt full-upgrade not reporting held back package

[Adam Conrad]

(To test in older versions, change the copy:// to a file:/ because derp)

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

Title:
  apt-get dist-upgrade and apt full-upgrade not reporting held back
  package

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Trusty:
  New
Status in apt source package in Xenial:
  New

Bug description:
  I have the situation where a package cannot be upgraded because of missing 
dependencies.  However
  sudo apt-get dist-upgrade
  and
  sudo apt full-upgrade
  and
  sudo apt upgrade
  all show
  0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

  Only
  sudo apt-get upgrade
  shows
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

  I believe all of the above commands should show that 1 cannot be
  upgraded.

  This bug is not about the particular package I am trying to install, but 
about the way apt reports the problem.
  The details, for reference, are that I am trying to upgrade mosquitto from 
the mosquitto ppa.  After apt-get update I see
  $ apt-cache policy mosquitto
  mosquitto:
    Installed: 1.4.8-1build1
    Candidate: 1.4.9-0mosquitto1
    Version table:
   1.4.9-0mosquitto1 500
  500 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu 
xenial/main amd64 Packages
   *** 1.4.8-1build1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  but if I try to manually install mosquitto I get

  The following packages have unmet dependencies.
   mosquitto : Depends: libwebsockets3 (>= 1.2) but it is not installable

  and

  $ apt-cache policy libwebsockets3
  libwebsockets3:
    Installed: (none)
    Candidate: (none)
  Due to the fact that libwebsockets3 is not available for Xenial.
  As I said this bug is not about the problem with this particular package but 
about the fact that apt does not report that there is a package to be upgraded, 
but it cannot be done.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun  5 08:45:33 2016
  InstallationDate: Installed on 2014-10-21 (592 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-03-06 (90 days ago)

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

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

[Touch-packages] [Bug 1589204] Re: apt-get dist-upgrade and apt full-upgrade not reporting held back package

[Adam Conrad]

Simple reproducer:

# cat /etc/apt/sources.list.d/test.list 
deb [trusted=yes] copy://home/adconrad/apt-test ./
# cat /home/adconrad/apt-test/Packages 
Package: apt
Priority: important
Section: admin
Architecture: amd64
Version: 99:1
Depends: test (>= 99:1)
# apt-get update
# apt-get dist-upgrade | grep upgraded
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# apt-get autoremove | grep upgraded
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
# apt-get upgrade | grep upgraded
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
# apt-get install hello | grep upgraded
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.

Note that only "dist-upgrade" appears to fail to report the package
being held because it's uninstallable.

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

Title:
  apt-get dist-upgrade and apt full-upgrade not reporting held back
  package

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Trusty:
  New
Status in apt source package in Xenial:
  New

Bug description:
  I have the situation where a package cannot be upgraded because of missing 
dependencies.  However
  sudo apt-get dist-upgrade
  and
  sudo apt full-upgrade
  and
  sudo apt upgrade
  all show
  0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

  Only
  sudo apt-get upgrade
  shows
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

  I believe all of the above commands should show that 1 cannot be
  upgraded.

  This bug is not about the particular package I am trying to install, but 
about the way apt reports the problem.
  The details, for reference, are that I am trying to upgrade mosquitto from 
the mosquitto ppa.  After apt-get update I see
  $ apt-cache policy mosquitto
  mosquitto:
    Installed: 1.4.8-1build1
    Candidate: 1.4.9-0mosquitto1
    Version table:
   1.4.9-0mosquitto1 500
  500 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu 
xenial/main amd64 Packages
   *** 1.4.8-1build1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  but if I try to manually install mosquitto I get

  The following packages have unmet dependencies.
   mosquitto : Depends: libwebsockets3 (>= 1.2) but it is not installable

  and

  $ apt-cache policy libwebsockets3
  libwebsockets3:
    Installed: (none)
    Candidate: (none)
  Due to the fact that libwebsockets3 is not available for Xenial.
  As I said this bug is not about the problem with this particular package but 
about the fact that apt does not report that there is a package to be upgraded, 
but it cannot be done.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun  5 08:45:33 2016
  InstallationDate: Installed on 2014-10-21 (592 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-03-06 (90 days ago)

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

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

[Touch-packages] [Bug 1606640] Re: a typo in 481-1 broke lesspipe ddeb support

[Adam Conrad]

Verified that the version in xenial-updates behaves correctly and calls
dpkg for ddebs.

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

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

Title:
  a typo in 481-1 broke lesspipe ddeb support

Status in less package in Ubuntu:
  Fix Committed
Status in less source package in Xenial:
  Fix Committed
Status in less package in Debian:
  Unknown

Bug description:
  [ SRU Justification ]
  Due to the bug, "less foo.ddeb" now gives you binary goop, instead of 
executing dpkg.

  [ Test Case ]
  Make sure the output of "less foo.ddeb" is similar to "less foo.deb", rather 
than a binary dump.

  [ Regression Potential ]
  nil, it's a 1-char fix.

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

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

[Touch-packages] [Bug 1606640] [NEW] a typo in 481-1 broke lesspipe ddeb support

[Adam Conrad]

Public bug reported:

[ SRU Justification ]
Due to the bug, "less foo.ddeb" now gives you binary goop, instead of executing 
dpkg.

[ Test Case ]
Make sure the output of "less foo.ddeb" is similar to "less foo.deb", rather 
than a binary dump.

[ Regression Potential ]
nil, it's a 1-char fix.

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

** Affects: less (Ubuntu Xenial)
 Importance: Undecided
 Status: New

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

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

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

** Also affects: less (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832121
   Importance: Unknown
   Status: Unknown

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

Title:
  a typo in 481-1 broke lesspipe ddeb support

Status in less package in Ubuntu:
  New
Status in less source package in Xenial:
  New
Status in less package in Debian:
  Unknown

Bug description:
  [ SRU Justification ]
  Due to the bug, "less foo.ddeb" now gives you binary goop, instead of 
executing dpkg.

  [ Test Case ]
  Make sure the output of "less foo.ddeb" is similar to "less foo.deb", rather 
than a binary dump.

  [ Regression Potential ]
  nil, it's a 1-char fix.

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

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

[Touch-packages] [Bug 1596091] Re: command "less" not installed by default in Xenial

[Adam Conrad]

** Also affects: cloud-images
   Importance: Undecided
   Status: New

** No longer affects: less (Ubuntu)

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

Title:
  command "less" not installed by default in Xenial

Status in cloud-images:
  New

Bug description:
  In previous version of Ubuntu "less" came by default, now it seems we
  have to install it manually using apt-get. This is bad for programs
  like "man" or "diff" that use less' scrolling capability.

  Note: I'm using the Docker version of 16.04 which is built on ubuntu-
  xenial-core-cloudimg-amd64-root.tar.gz as shown here:

  https://github.com/tianon/docker-brew-ubuntu-
  core/blob/f2682b59c32241b97e904af6691e997fa9c79c91/xenial/Dockerfile

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

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

[Touch-packages] [Bug 1585942] Re: Mesa causes a segmentation fault on arm64 (wrong count of uniform locations)

[Adam Conrad]

Hello Alberto, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/11.2.0-1ubuntu2.1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  Mesa causes a segmentation fault on arm64 (wrong count of uniform
  locations)

Status in Canonical System Image:
  Fix Committed
Status in mesa package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in ubuntu-system-settings-online-accounts source package in Xenial:
  New
Status in webbrowser-app source package in Xenial:
  New

Bug description:
  This error appeared when running unit tests for a QML app in our
  Jenkins/silo infrastructure, on arm64 only:
  https://launchpadlibrarian.net/261581280/buildlog_ubuntu-yakkety-arm64
  .ubuntu-system-settings-online-
  accounts_0.7+16.10.20160525.1-0ubuntu1_BUILDING.txt.gz

  Pasting the relevant lines here in case the link above goes away:

  ===
  QT_PLUGIN_PATH=/usr/lib/aarch64-linux-gnu/qt5/plugins 
LD_LIBRARY_PATH=/usr/lib/aarch64-linux-gnu${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH} 
xvfb-run -s '-screen 0 640x480x24' -a dbus-test-runner -t   
./tst_online_accounts_qml
  DBus daemon: 
unix:abstract=/tmp/dbus-2tbhBHxLZq,guid=03f9df417d619b79067a68045745ad95
  task-0: Started with PID: 16930
  task-0: * Start testing of online_accounts_qml *
  task-0: Config: Using QtTest library 5.5.1, Qt 5.5.1 
(arm64-little_endian-lp64 shared (dynamic) release build; by GCC 5.3.1 20160519)
  task-0: PASS   : online_accounts_qml::AccountCreationPage::initTestCase()
  task-0: QWARN  : online_accounts_qml::AccountCreationPage::test_fallback() 
file:///dummy/path/testPlugin/Main.qml: File not found
  task-0: PASS   : online_accounts_qml::AccountCreationPage::test_fallback()
  task-0: QWARN  : online_accounts_qml::AccountCreationPage::test_flickable() 
file:///dummy/path/testPlugin/Main.qml: File not found
  task-0: PASS   : online_accounts_qml::AccountCreationPage::test_flickable()
  task-0: PASS   : online_accounts_qml::AccountCreationPage::cleanupTestCase()
  task-0: QWARN  : online_accounts_qml::UnknownTestFunc() QEGLPlatformContext: 
Failed to make temporary surface current, format not updated
  task-0: PASS   : online_accounts_qml::AuthorizationPage::initTestCase()
  task-0: QWARN  : online_accounts_qml::AuthorizationPage::test_1_one_account() 
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:54:
 TypeError: Cannot call method 'indexOf' of undefined
  task-0: PASS   : online_accounts_qml::AuthorizationPage::test_1_one_account()
  task-0: QWARN  : 
online_accounts_qml::AuthorizationPage::test_2_add_another(with button) 
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:54:
 TypeError: Cannot call method 'indexOf' of undefined
  task-0: QWARN  : 
online_accounts_qml::AuthorizationPage::test_2_add_another(with button) 
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:79:23:
 Unable to assign [undefined] to QString
  task-0: PASS   : 
online_accounts_qml::AuthorizationPage::test_2_add_another(with button)
  task-0: QWARN  : 
online_accounts_qml::AuthorizationPage::test_2_add_another(with button) 
[PERFORMANCE]: Last frame took 254 ms to render.
  task-0: QWARN  : 
online_accounts_qml::AuthorizationPage::test_2_add_another(without button) 
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:54:
 TypeError: Cannot call method 'indexOf' of undefined
  task-0: QWARN  : 

[Touch-packages] [Bug 1585771] Update Released

[Adam Conrad]

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

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

Title:
  Automatic security upgrades are always enabled

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

Bug description:
  After installing 16.04 server and selecting the option "no automatic
  upgrades" the system will still be configured to automatically perform
  security upgrades.

  $ cat /etc/apt/apt.conf.d/20auto-upgrades 
  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Unattended-Upgrade "1";

  $ head -n 8 /etc/apt/apt.conf.d/50unattended-upgrades 
  // Automatically upgrade packages from these (origin:archive) pairs
  Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}-security";
  //"${distro_id}:${distro_codename}-updates";
  //"${distro_id}:${distro_codename}-proposed";
  //"${distro_id}:${distro_codename}-backports";
  };

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

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

[Touch-packages] [Bug 1585771] Re: Automatic security upgrades are always enabled

[Adam Conrad]

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

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

Title:
  Automatic security upgrades are always enabled

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

Bug description:
  After installing 16.04 server and selecting the option "no automatic
  upgrades" the system will still be configured to automatically perform
  security upgrades.

  $ cat /etc/apt/apt.conf.d/20auto-upgrades 
  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Unattended-Upgrade "1";

  $ head -n 8 /etc/apt/apt.conf.d/50unattended-upgrades 
  // Automatically upgrade packages from these (origin:archive) pairs
  Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}-security";
  //"${distro_id}:${distro_codename}-updates";
  //"${distro_id}:${distro_codename}-proposed";
  //"${distro_id}:${distro_codename}-backports";
  };

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

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

[Touch-packages] [Bug 1556330] Update Released

[Adam Conrad]

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

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

Title:
  upstream curl bug #1371: p12 client certificates code is broken

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  The bug makes it impossible to use PKCS#12 secure storage of client
  certificates and private keys with any affected Ubuntu releases. The
  fix is one line fixing a broken switch statement and was already
  tested against Ubuntu 14.04 LTS with a rebuilt curl package.

  This was fixed in upstream libcurl in the following bug:

  https://sourceforge.net/p/curl/bugs/1371/

  The bug fix consists of one missing break statement at the end of a
  case in a switch statement.

  I personally patched the bug using source code release
  curl_7.35.0-1ubuntu2.6.dsc, used in Ubuntu 14.04 LTS, and verified it
  does indeed fix the bug and all of the package's tests still pass
  afterwards.

  [Test Case]

  The bug can be reproduced using the following libcurl parameters (even
  via CLI, pycurl, etc.).

  CURLOPT_SSLCERTTYPE == "P12"
  CURLOPT_SSLCERT = path to PKCS#12
  CURLOPT_SSLKEY = path to PKCS#12
  CURLOPT_SSLKEYPASSWD = key for PKCS#12 if needed

  Basically, just use a PKCS#12 format client certificate and private
  key against some certificate protected web server.

  [Regression Potential]

  If it could possibly break anything, which is extraordinarily
  unlikely, it would break one of the three client certificate formats
  (most likely PKCS#12 but also PEM or DER). Note 1/3 formats is already
  broken due to the bug. Client certificates of all three types could be
  checked to prevent this.

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

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

[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

[Adam Conrad]

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

** Tags added: verification-needed-trusty verification-needed-wily

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

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Wily:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Infiniband users relying on DHCP can't use DHCP relay.

  [Test Case]

   * Comment #13
   * Mellanox has tested themselves.
   * Clear way of knowing if fix worked (tcpdump).

  [Regression Potential]

   * Only related to Infiniband.
   * Infiniband support could stop working (unlikely, already tested).

  [Other Info]

  DHCP client is sending discover with Unicast type request for the
  offer, in this configuration of IB to ETH through a relay we need the
  type to be broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  DHCP CLIENT (IPoIB)
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

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

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

[Touch-packages] [Bug 1529815] Update Released

[Adam Conrad]

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

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

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Wily:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Infiniband users relying on DHCP can't use DHCP relay.

  [Test Case]

   * Comment #13
   * Mellanox has tested themselves.
   * Clear way of knowing if fix worked (tcpdump).

  [Regression Potential]

   * Only related to Infiniband.
   * Infiniband support could stop working (unlikely, already tested).

  [Other Info]

  DHCP client is sending discover with Unicast type request for the
  offer, in this configuration of IB to ETH through a relay we need the
  type to be broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  DHCP CLIENT (IPoIB)
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

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

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

[Touch-packages] [Bug 1579267] Update Released

[Adam Conrad]

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

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

Title:
  plymouth-start.service: After: reference to non-existent keyboard-
  setup.service

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Keymaps are not correctly set on virtual console (in gettys)

  [Test case]
  Set keymap, using us, intl variant. Test that dead keys behave correctly (ie. 
hitting an apostrophe and then e yields "é" rather than "'e".

  [Regression potential]
  System that carry a keyboard configuration but the system administrators rely 
on the fact that the local console keymap remains in US will find that it no 
longer behaves as expected.

  ---

  16.04 amd64.

  plymouth-start.service refers to a non-existent keyboard-
  setup.service:

  $ grep keyboard -r /lib/systemd/system/*
  /lib/systemd/system/plymouth-start.service:After=systemd-udev-trigger.service 
systemd-udevd.service keyboard-setup.service
  tj@T300CHI:~$ apt-file search keyboard-setup.service
  tj@T300CHI:~$

  The file only exists in 16.10 in console-setup-linux

  This caught me out whilst I was debugging some console-setup issues.

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

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

[Touch-packages] [Bug 1576893] Update Released

[Adam Conrad]

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

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

Title:
  console colors are not correctly applied

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Debconf prompts are incredibly ugly on virtual console; colors are off from 
the "official" aubergine background. This applies to Ubuntu specifically since 
other flavors may specify a different color scheme that may not be affected.

  [Test case]
  1) sudo dpkg-reconfigure debconf

  [Regression potential]
  None. This only applies to the display colors for a console, and only on a 
linux virtual console (ie. not a terminal).

  ---

  At least on Xenial and onwards, our color scheme for the VTs is not
  being applied, since setvtrgb is not getting run on boot (it's still
  only an upstart job).

  Porting setvtrgb to a systemd unit makes the pretty colors appear, and
  I can get my debconf/newt prompts back with an aubergine background.

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

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

[Touch-packages] [Bug 1572697] Update Released

[Adam Conrad]

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

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

Title:
  broken symlink console-setup.service [systemd]

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Console font and other configs from kbd/console-setup may not be applied on 
boot.

  [Test case]
  1) Configure a keymap / key translation table.
  2) Boot the system
  3) Console should have the key translation table applied.

  [Regression potential]
  Minimal; this applies configuration that should always be applied on boot and 
only applies as a fix to a regression from previous releases, and only on a 
virtual console.

  ---

  keyboard-configuration 1.108ubuntu15 contains console-setup.service in
  /lib/systemd/system/multi-user.target.wants, but as a broken symlink:

  $ dpkg -L keyboard-configuration | grep multi-user.target.wants
  /lib/systemd/system/multi-user.target.wants
  /lib/systemd/system/multi-user.target.wants/console-setup.service

  $ sudo find -L /lib/systemd/system -type l -ls
    1315455  0 lrwxrwxrwx   1 root root   22 Apr 20 03:11 
/lib/systemd/system/multi-user.target.wants/console-setup.service -> 
/console-setup.service

  Symlink should point to ../console-setup.service instead.

  I originally reported this in
  https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1534121
  against console-setup, which was the wrong package to refer to. My
  apologies for messing that up.

  Additional info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy keyboard-configuration
  keyboard-configuration:
    Installed: 1.108ubuntu15
    Candidate: 1.108ubuntu15
    Version table:
   *** 1.108ubuntu15 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1591622] Update Released

[Adam Conrad]

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

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

Title:
  Can't login to system, system is booting up error

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  Fix Released
Status in console-setup source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Regression in console-setup 1.108ubuntu15.1 in xenial-proposed which 
introduced a dependency loop caused logins to fail in around 10% of boots.

  [Test case]
  1) reboot
  2) attempt to login

  In the failure case, the system will display an error message:
  "System is booting up. See pam_nologin(8)."

  [Regression Potential]
  This is intended to fix a regression already found in xenial-proposed due to 
dependencies in the systemd units. Other ordering issues may arise, such that 
it is possible for another process to otherwise fail to load because of the 
invalid dependencies between systemd jobs. Care is to be taken in testing the 
proposed fix, and involves many reboot tests.

  ---

  On login screen (LightDM) I cant login to system because system error is 
displayed: System is booting up. See pam_nologin(8). This message is appearing 
randomly, sometimes when I boot system I can login and sometimes not. It starts 
to show after last console-setup-linux, console-setup and 
keyboard-configuration to version 1.108ubuntu15.1.
  Photo with error in attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-lowlatency 4.4.10
  Uname: Linux 4.4.0-23-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun 12 08:50:29 2016
  InstallationDate: Installed on 2015-02-13 (484 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmConfig:
   [Seat:*]
   allow-guest = false
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (47 days ago)
  mtime.conffile..etc.init.lightdm.conf: 2015-06-08T20:05:20

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

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

[Touch-packages] [Bug 1593379] Update Released

[Adam Conrad]

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

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

Title:
  systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or
  /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd package in Debian:
  Fix Released

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB
  devices.

  It appears the regression is here:
  * Set MAC based name for USB network interfaces only for universally
  administered (i. e. stable) MACs, not for locally administered (i. e.
  randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link
  (as link files don't currently support globs for MACAddress=) and replace
  with an udev rule in /lib/udev/rules.d/73-special-net-names.rules.
  (Closes: #812575, LP: #1574483)

  As Raspberry Pi's use eth0 via USB, this breaks running systems.

  Before:
  ii  systemd229-4ubuntu4 armhfsystem and service manager
  ii  udev   229-4ubuntu4 armhf/dev/ and hotplug management daem

  3: eth0:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  After:

  ii  systemd  229-4ubuntu6armhf   
system and service manager
  ii  udev 229-4ubuntu6armhf   
/dev/ and hotplug management daemon

  3: enxb827eb1639e9:  mtu 1500 qdisc 
pfifo_fast state UP mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  cat /proc/cmdline
  dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 
bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 
smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 
vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 
rootfstype=ext4 elevator=deadline rootwait

  With the default interfaces configuration, all networking is lost on
  reboot after upgrade.

  
  SRU TEST CASE
  =
   * Boot with "net.ifnames=0" on the kernel command line, and connect an USB 
ethernet device. It will still be called enxDEADBEEF with current xenial. With 
the -proposed version it will instead keep the kernel name, like "usb0" as 
intended.

   * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules"
  (the other documented way to disable ifnames) and do the above
  connect/name check test again.

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

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

[Touch-packages] [Bug 1602256] Update Released

[Adam Conrad]

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

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

Title:
  sometimes "systemd-coredump[]: Coredump file descriptor missing."
  is seen, upstream #2984

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

Bug description:
  Please include this upstream fix/pull request:

  coredump: use next_datagram_size_fd instead of ioctl(FIONREAD) #3237
  https://github.com/systemd/systemd/pull/3237

  Reported as
  sometimes "systemd-coredump[]: Coredump file descriptor missing." is 
seen, upstream #2984
  https://github.com/systemd/systemd/issues/2984

  Or make a release using systemd tag=v230

   :~$ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04

  :~$ apt-cache policy systemd
  systemd:
    Installed: 229-4ubuntu6
    Candidate: 229-4ubuntu6
    Version table:
   *** 229-4ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  SRU INFORMATION
  ---
  This only affects systemd-coredump which we don't use in Ubuntu by default 
(we use Apport), so the regression potential is very low. There is no 
straightforward reproducer for this (see upstream bug report: 
https://github.com/systemd/systemd/issues/2984). But our systemd package has 
integration tests for coredump: 
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/tests/boot-and-services?h=ubuntu-xenial#n436
 

  Thus if the updated package still succeeds its autopkgtests, this
  should provide sufficient regression testing for this bug.

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

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

[Touch-packages] [Bug 1583861] Update Released

[Adam Conrad]

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

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

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Fix Released
Status in upower source package in Xenial:
  Fix Committed

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

  
  To reset the idle-delay, just call
gsettings reset org.gnome.desktop.session idle-delay

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+subscriptions

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

[Touch-packages] [Bug 1582803] Update Released

[Adam Conrad]

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

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

Title:
  [SRU]bug report script uses invalid nm options

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Xenial reports have those warnings "Error: Object 'nm' is unknown, try 'nmcli 
help'." the "nm-cli" syntax changed and the hook needs to be updated

  [Test Case]
  Future apport report to errors.ubuntu.com should have proper information 
output from nmcli command, rather than throwing an error message.

  [Regression Potential]
  This is a simple change of the command line option on information collection, 
which should be safe.

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

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

[Touch-packages] [Bug 1557026] Update Released

[Adam Conrad]

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

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

Title:
  [SRU]Network Manager sets powersave off by default in xenial

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  NetworkManager consumes more power than previous releases because powersave 
support is not updated.

  [Test Case]
  With the patch applied, network device power management should be on when 
supported, for example:

  $ sudo iwconfig wlan0 | grep "Power Management"
Power Management:on

  [Regression Potential]
  Regression may happen when the power management feature of certain device 
isn't implemented properly in kernel, but since we are quite conservative on 
enabling power management in kernel development such case should be rare.

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

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

[Touch-packages] [Bug 1595707] Update Released

[Adam Conrad]

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

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

Title:
  [SRU]crash in nmc_find_connection

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Ubuntu error tracker receives some reports agains 1.2.0 for a crash in 
nmc_find_connection() when connecting to a password protected wlan connection, 
by running command: nmcli device connect wlan0
  T he problem page at 
https://errors.ubuntu.com/problem/16ece0c3816c93d9c763402902edf04448cbe6c8 
contains more details.

  [Test Case]
  After applying the patch, errors.ubuntu.com should stop receiving new crash 
reports for this problem.

  [Regression Potential]
  The fix is making the connection list available for certain 
nmc_secrets_requested() call, which should be harmless.

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

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

[Touch-packages] [Bug 1603137] Update Released

[Adam Conrad]

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

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

Title:
  libbfd changed name without transition

Status in binutils package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in binutils source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid

Bug description:
  [SRU Justification]
  the latest binutils update in xenial to 2.26.1-1ubuntu1~16.04 changed the 
name of the libbfd library from: libbfd-2.26-system.so to 
libbfd-2.26.1-system.so
  This apparently happened without transitioning all dependencies.
  For example it broke the perf tool from the linux-tools-common package as it 
is still linked against the old libbfd name.

  To reproduce run "perf" with linux >= 4.4.0-24.43 and binutils
  2.26.1-1ubuntu1~16.04 and you get an cannot open libbfd-2.26-system.so
  error.

  [Test case]
  1. Install eztrace on 16.04.
  2. Install binutils from xenial-updates.
  3. Run 'eztrace'.  Confirm that this fails with a library error.
  4. Install binutils from xenial-proposed.
  5. Run 'eztrace'.  Confirm that this gives usage output instead of failing 
with a library error.

  [Regression potential]
  Packages which depend on libbfd-2.26-system.so are currently broken with the 
binutils in xenial-updates.  No packages appear to have been built yet against 
the libbfd-2.26.1-system.so soname.  Therefore the regression potential is 
minimal.  The solution is intended to be compatible with both upstream sonames, 
so that any future packages which do rebuild against the 2.26.1 soname will 
have a versioned dependency on binutils (>= 2.26.1), binutils (<= 2.27).

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

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

[Touch-packages] [Bug 1598770] Update Released

[Adam Conrad]

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

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

Title:
  Unity in low-graphics mode has animations and unneeded redraws

Status in compiz package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in compiz source package in Xenial:
  Fix Released
Status in nux source package in Xenial:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in unity-control-center source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  When unity is in Low graphics mode (because of software rendering)
  there are still window animations and fade effects which we should get
  rid of.

  
  [Test case]

  This should apply naturally to a (virtual-)machine with no hardware
  acceleration or There are multiple ways to force low-gfx mode:

  1) Add an upstart job such as:

  cat << EOF > ~/.config/upstart/lowgfx.conf
  start on starting unity7

  pre-start script
#initctl set-env --global UNITY_LOW_GFX_MODE=1
initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1
  end script
  EOF 

  
  2) Run unity with:
 COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx

  On login unity should use opaque views (dash, switcher, launcher,
  shortcut-dialogs) with no fading and reduced effects. Windows should
  also use smaller shadows.

  
  [Regression potential]

  Some settings from unity-control-center couldn't be applied to normal
  profile. Low graphics mode might be used as normal one.

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

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

[Touch-packages] [Bug 1603137] Re: libbfd changed name without transition

[Adam Conrad]

Hello Julian, or anyone else affected,

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

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

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

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

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

** Tags added: verification-needed

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

Title:
  libbfd changed name without transition

Status in binutils package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in binutils source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Invalid

Bug description:
  [SRU Justification]
  the latest binutils update in xenial to 2.26.1-1ubuntu1~16.04 changed the 
name of the libbfd library from: libbfd-2.26-system.so to 
libbfd-2.26.1-system.so
  This apparently happened without transitioning all dependencies.
  For example it broke the perf tool from the linux-tools-common package as it 
is still linked against the old libbfd name.

  To reproduce run "perf" with linux >= 4.4.0-24.43 and binutils
  2.26.1-1ubuntu1~16.04 and you get an cannot open libbfd-2.26-system.so
  error.

  [Test case]
  1. Install eztrace on 16.04.
  2. Install binutils from xenial-updates.
  3. Run 'eztrace'.  Confirm that this fails with a library error.
  4. Install binutils from xenial-proposed.
  5. Run 'eztrace'.  Confirm that this gives usage output instead of failing 
with a library error.

  [Regression potential]
  Packages which depend on libbfd-2.26-system.so are currently broken with the 
binutils in xenial-updates.  No packages appear to have been built yet against 
the libbfd-2.26.1-system.so soname.  Therefore the regression potential is 
minimal.  The solution is intended to be compatible with both upstream sonames, 
so that any future packages which do rebuild against the 2.26.1 soname will 
have a versioned dependency on binutils (>= 2.26.1), binutils (<= 2.27).

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

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

[Touch-packages] [Bug 1574693] Update Released

[Adam Conrad]

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

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

Title:
  No shadows under menus on Unity.

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  Fix Released

Bug description:
  Hi,

  After a fresh install of Ubuntu 16.04 in a new SSD, there aren't
  shadows under menus on application decoration borders and Unity panel.

  I've seen the same problem in Askubuntu:
  
http://askubuntu.com/questions/761842/no-shadows-under-menus-on-application-decoration-borders-and-unity-panel/762487#762487

  Thanks!!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 16:38:08 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company RS880M [Mobility Radeon HD 4225/4250] 
[103c:143c]
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 
5430/5450/5470] [1002:68e0] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2016-04-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP G62 Notebook PC
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=231aae18-0f30-4b65-943c-646a217d0d72 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 143C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 62.3D
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd03/15/2011:svnHewlett-Packard:pnHPG62NotebookPC:pvr059411252710001020100:rvnHewlett-Packard:rn143C:rvr62.3D:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP G62 Notebook PC
  dmi.product.version: 059411252710001020100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 16:23:48 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1506744] Update Released

[Adam Conrad]

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

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

Title:
  Newly installed applications do not show in the dash

Status in GLib:
  Confirmed
Status in bamf package in Ubuntu:
  In Progress
Status in gnome-menus package in Ubuntu:
  Fix Released
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid
Status in gnome-menus source package in Xenial:
  Fix Committed
Status in libunity source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  I am running 15.10 development version fully up to date, I installed it a few 
days ago and I have an issue with newly installed applications not appearing in 
the dash when I search for them, they can be started via console but the 
icons/launchers of newly installed applications will only appear in the dash 
after session is restarted.

  [Test case]
  1. Install a new applicaiton (using apt-get or the software center)
  2. Make sure the application is listed in the Unity Dash

  [Possible Regressions]
  Unity fails to list all the applications, not just the newly installed ones.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20151002.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 16 08:41:39 2015
  InstallationDate: Installed on 2015-10-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)Z

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

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

[Touch-packages] [Bug 1597523] Update Released

[Adam Conrad]

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

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

Title:
  SRU of LXC 2.0.3 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  LXC upstream released LXC 2.0.2 & 2.0.3 as bugfix releases with following 
changelog:
   - apparmor: Refresh generated file
   - apparmor: add make-rslave to usr.bin.lxc-start
   - apparmor: Allow bind-mounts and {r}shared/{r}private
   - apparmor: allow mount move
   - apparmor: Update mount states handling
   - core: Drop lxc-devsetup as unneeded by current autodev
   - core: Fix redefinition of struct in6_addr
   - core: Include all lxcmntent.h function declarations on Bionic
   - c/r: c/r: use criu's "full" mode for cgroups
   - systemd: start containers in foreground when using the lxc@.service
   - templates: debian: Make sure init is installed
   - templates: oracle: Fix console login
   - templates: plamo: Fix various issues
   - templates: ubuntu: Install apt-transport-https by default
   - travis: ensure 'make install' doesn't fail
   - travis: test VPATH builds
   - upstart: Force lxc-instance to behave like a good Upstart client

  Just like Ubuntu itself, upstream releases long term support releases,
  as is 2.0 and then periodic point releases including all the
  accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This bugfix release has already been uploaded to Yakkety and
  automatically backported in the upstream PPAs for all Ubuntu releases.
  So far without any reported regression.

  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  Once the SRU hits -updates, we will be backporting this to trusty-
  backports as well, making sure we have the same version everywhere.

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

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

[Touch-packages] [Bug 1600000] [NEW] libnss-resolve treats two trailing dots on a domain name incorrectly

[Adam Conrad]

Public bug reported:

(base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
208.118.235.148 STREAM wildebeest.gnu.org
208.118.235.148 DGRAM  
208.118.235.148 RAW
(base)adconrad@nosferatu:~$ sudo sed -i -e 's/ resolve dns/ dns/' 
/etc/nsswitch.conf 
(base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
(base)adconrad@nosferatu:~$ sudo sed -i -e 's/ dns/ resolve dns/' 
/etc/nsswitch.conf 
(base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
208.118.235.148 STREAM wildebeest.gnu.org
208.118.235.148 DGRAM  
208.118.235.148 RAW
(base)adconrad@nosferatu:~$ 

This is responsible for the new regression in glibc:

--
FAIL: posix/tst-getaddrinfo5
original exit status 1
resolving "localhost." worked, proceeding to test
resolving "localhost.." failed, test passed
resolving "www.gnu.org." worked, proceeding to test
resolving "www.gnu.org.." worked, test failed
--

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

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

Title:
  libnss-resolve treats two trailing dots on a domain name incorrectly

Status in systemd package in Ubuntu:
  New

Bug description:
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  208.118.235.148 STREAM wildebeest.gnu.org
  208.118.235.148 DGRAM  
  208.118.235.148 RAW
  (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ resolve dns/ dns/' 
/etc/nsswitch.conf 
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ dns/ resolve dns/' 
/etc/nsswitch.conf 
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  208.118.235.148 STREAM wildebeest.gnu.org
  208.118.235.148 DGRAM  
  208.118.235.148 RAW
  (base)adconrad@nosferatu:~$ 

  This is responsible for the new regression in glibc:

  --
  FAIL: posix/tst-getaddrinfo5
  original exit status 1
  resolving "localhost." worked, proceeding to test
  resolving "localhost.." failed, test passed
  resolving "www.gnu.org." worked, proceeding to test
  resolving "www.gnu.org.." worked, test failed
  --

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

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

[Touch-packages] [Bug 1527343] Re: the package libtbb2 can't be installed in 64 bit and 32 bit at the same time

[Adam Conrad]

tbb was multiarched in Xenial (16.04)

** Package changed: dpkg (Ubuntu) => tbb (Ubuntu)

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

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

Title:
  the package libtbb2 can't be installed in 64 bit and 32 bit at the
  same time

Status in tbb package in Ubuntu:
  Fix Released

Bug description:
  the package libtbb2 (64 bit) is installed on my system because some other 
packages depend on it (e.g. blender). I try to install the 32 bit version of 
libtbb2:
  apt-get install libtbb2:i386

  but this installation would uninstall libtbb2 (64 bit) and all
  packages that depend on it (e.g. blender). So 32-bit Software that
  requires libtbb2 (32-bit) can't be used or all packages that depend on
  libtbb2 (64 bit) have to be uninstalled. This behaviour isn't correct.

  This happens on ubuntu 15.10 and on 14.04 too.

  way to reproduce:
  apt-get install libtbb2 libtbb2:i386

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: dpkg 1.18.2ubuntu5.1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Dec 17 18:37:47 2015
  InstallationDate: Installed on 2015-12-13 (3 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: dpkg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-3.8 into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-3.8/1:3.8-2ubuntu3~trusty4 in a few hours, and then in the
-proposed repository.

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

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

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

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Committed
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Committed
Status in x11proto-core source package in Trusty:
  New
Status in x11proto-randr source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

[Touch-packages] [Bug 1577734] Re: Backport packages for 14.04.5 lts-xenial stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted libxrandr into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libxrandr/2:1.5.0-1~trusty1 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: libxrandr (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Committed
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Committed
Status in x11proto-core source package in Trusty:
  New
Status in x11proto-randr source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

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

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted x11proto-randr into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/x11proto-
randr/1.5.0-1~trusty1 in a few hours, and then in the -proposed
repository.

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

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

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

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  New
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Committed
Status in x11proto-core source package in Trusty:
  New
Status in x11proto-randr source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

[Touch-packages] [Bug 1577734] Re: Backport packages for 14.04.5 lts-xenial stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-3.8 into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-3.8/1:3.8-2ubuntu3~trusty3 in a few hours, and then in the
-proposed repository.

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

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

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

** Tags removed: verification-failed

** Tags added: verification-needed

** Changed in: x11proto-randr (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  New
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Committed
Status in x11proto-core source package in Trusty:
  New
Status in x11proto-randr source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

[Touch-packages] [Bug 1577734] Re: Backport packages for 14.04.5 lts-xenial stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-3.8 into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-3.8/1:3.8-2ubuntu3~trusty2 in a few hours, and then in the
-proposed repository.

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

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

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

** Changed in: x11proto-core (Ubuntu)
   Status: New => Invalid

** Changed in: llvm-toolchain-3.8 (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

** Changed in: libdrm (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  New
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Committed
Status in x11proto-core source package in Trusty:
  New
Status in x11proto-randr source package in Trusty:
  New

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

[Touch-packages] [Bug 1574897] Re: Upgrading to 16.04 disables Python3?

[Adam Conrad]

As expected, the new xenial vim binary package grew a dependency on
libpython3.5, and powerline now works correctly.

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

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

Title:
  Upgrading to 16.04 disables Python3?

Status in vim package in Ubuntu:
  Fix Released
Status in vim source package in Xenial:
  Fix Committed

Bug description:
  Since I ran a do-release-upgrade last week from 15.10 to 16.04,
  starting Vim now produces this warning I haven't seen before:

  ~/D/abc ❯❯❯ vim   
 develop ✭
  You need vim compiled with Python 2.6, 2.7 or 3.2 and later support
  for Powerline to work. Please consult the documentation for more
  details.
  Press ENTER or type command to continue

  Then had a look at the included features of Vim:

  /e/alternatives ❯❯❯ vim --version
  VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28)
  Included patches: 1-1689
  Modified by pkg-vim-maintain...@lists.alioth.debian.org
  Compiled by pkg-vim-maintain...@lists.alioth.debian.org
  Huge version without GUI.  Features included (+) or not (-):
  +acl +farsi   +mouse_netterm   +tag_binary
  +arabic  +file_in_path+mouse_sgr   +tag_old_static
  +autocmd +find_in_path-mouse_sysmouse  -tag_any_white
  -balloon_eval+float   +mouse_urxvt -tcl
  -browse  +folding +mouse_xterm +terminfo
  ++builtin_terms  -footer  +multi_byte  +termresponse
  +byte_offset +fork()  +multi_lang  +textobjects
  +channel +gettext -mzscheme+timers
  +cindent -hangul_input+netbeans_intg   +title
  -clientserver+iconv   +packages-toolbar
  -clipboard   +insert_expand   +path_extra  +user_commands
  +cmdline_compl   +job -perl+vertsplit
  +cmdline_hist+jumplist+persistent_undo +virtualedit
  +cmdline_info+keymap  +postscript  +visual
  +comments+langmap +printer +visualextra
  +conceal +libcall +profile +viminfo
  +cryptv  +linebreak   -python  +vreplace
  +cscope  +lispindent  -python3 +wildignore
  +cursorbind  +listcmds+quickfix+wildmenu
  +cursorshape +localmap+reltime +windows
  +dialog_con  -lua +rightleft   +writebackup
  +diff+menu-ruby-X11
  +digraphs+mksession   +scrollbind  -xfontset
  -dnd +modify_fname+signs   -xim
  -ebcdic  +mouse   +smartindent -xsmp
  +emacs_tags  -mouseshape  +startuptime -xterm_clipboard
  +eval+mouse_dec   +statusline  -xterm_save
  +ex_extra+mouse_gpm   -sun_workshop-xpm
  +extra_search-mouse_jsbterm   +syntax  
 system vimrc file: "$VIM/vimrc"
   user vimrc file: "$HOME/.vimrc"
   2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/share/vim"
  Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -Wdate-time  -g -O2 -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=1  
  Linking: gcc   -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed -o vim-lm -ltinfo -lnsl  -lselinux -lacl -lattr -lgpm 
-ldl

  I see, there is -python and -python3

  But all news and documentation say the Vim in Xenial 16.04 comes with
  Python3 enabled. I am confused? A bug?

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

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

[Touch-packages] [Bug 1574897] Re: Upgrading to 16.04 disables Python3?

[Adam Conrad]

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

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

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

Title:
  Upgrading to 16.04 disables Python3?

Status in vim package in Ubuntu:
  Confirmed
Status in vim source package in Xenial:
  New

Bug description:
  Since I ran a do-release-upgrade last week from 15.10 to 16.04,
  starting Vim now produces this warning I haven't seen before:

  ~/D/abc ❯❯❯ vim   
 develop ✭
  You need vim compiled with Python 2.6, 2.7 or 3.2 and later support
  for Powerline to work. Please consult the documentation for more
  details.
  Press ENTER or type command to continue

  Then had a look at the included features of Vim:

  /e/alternatives ❯❯❯ vim --version
  VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28)
  Included patches: 1-1689
  Modified by pkg-vim-maintain...@lists.alioth.debian.org
  Compiled by pkg-vim-maintain...@lists.alioth.debian.org
  Huge version without GUI.  Features included (+) or not (-):
  +acl +farsi   +mouse_netterm   +tag_binary
  +arabic  +file_in_path+mouse_sgr   +tag_old_static
  +autocmd +find_in_path-mouse_sysmouse  -tag_any_white
  -balloon_eval+float   +mouse_urxvt -tcl
  -browse  +folding +mouse_xterm +terminfo
  ++builtin_terms  -footer  +multi_byte  +termresponse
  +byte_offset +fork()  +multi_lang  +textobjects
  +channel +gettext -mzscheme+timers
  +cindent -hangul_input+netbeans_intg   +title
  -clientserver+iconv   +packages-toolbar
  -clipboard   +insert_expand   +path_extra  +user_commands
  +cmdline_compl   +job -perl+vertsplit
  +cmdline_hist+jumplist+persistent_undo +virtualedit
  +cmdline_info+keymap  +postscript  +visual
  +comments+langmap +printer +visualextra
  +conceal +libcall +profile +viminfo
  +cryptv  +linebreak   -python  +vreplace
  +cscope  +lispindent  -python3 +wildignore
  +cursorbind  +listcmds+quickfix+wildmenu
  +cursorshape +localmap+reltime +windows
  +dialog_con  -lua +rightleft   +writebackup
  +diff+menu-ruby-X11
  +digraphs+mksession   +scrollbind  -xfontset
  -dnd +modify_fname+signs   -xim
  -ebcdic  +mouse   +smartindent -xsmp
  +emacs_tags  -mouseshape  +startuptime -xterm_clipboard
  +eval+mouse_dec   +statusline  -xterm_save
  +ex_extra+mouse_gpm   -sun_workshop-xpm
  +extra_search-mouse_jsbterm   +syntax  
 system vimrc file: "$VIM/vimrc"
   user vimrc file: "$HOME/.vimrc"
   2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/share/vim"
  Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -Wdate-time  -g -O2 -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=1  
  Linking: gcc   -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed -o vim-lm -ltinfo -lnsl  -lselinux -lacl -lattr -lgpm 
-ldl

  I see, there is -python and -python3

  But all news and documentation say the Vim in Xenial 16.04 comes with
  Python3 enabled. I am confused? A bug?

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

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

[Touch-packages] [Bug 1574897] Re: Upgrading to 16.04 disables Python3?

[Adam Conrad]

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

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

Title:
  Upgrading to 16.04 disables Python3?

Status in vim package in Ubuntu:
  Confirmed
Status in vim source package in Xenial:
  New

Bug description:
  Since I ran a do-release-upgrade last week from 15.10 to 16.04,
  starting Vim now produces this warning I haven't seen before:

  ~/D/abc ❯❯❯ vim   
 develop ✭
  You need vim compiled with Python 2.6, 2.7 or 3.2 and later support
  for Powerline to work. Please consult the documentation for more
  details.
  Press ENTER or type command to continue

  Then had a look at the included features of Vim:

  /e/alternatives ❯❯❯ vim --version
  VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28)
  Included patches: 1-1689
  Modified by pkg-vim-maintain...@lists.alioth.debian.org
  Compiled by pkg-vim-maintain...@lists.alioth.debian.org
  Huge version without GUI.  Features included (+) or not (-):
  +acl +farsi   +mouse_netterm   +tag_binary
  +arabic  +file_in_path+mouse_sgr   +tag_old_static
  +autocmd +find_in_path-mouse_sysmouse  -tag_any_white
  -balloon_eval+float   +mouse_urxvt -tcl
  -browse  +folding +mouse_xterm +terminfo
  ++builtin_terms  -footer  +multi_byte  +termresponse
  +byte_offset +fork()  +multi_lang  +textobjects
  +channel +gettext -mzscheme+timers
  +cindent -hangul_input+netbeans_intg   +title
  -clientserver+iconv   +packages-toolbar
  -clipboard   +insert_expand   +path_extra  +user_commands
  +cmdline_compl   +job -perl+vertsplit
  +cmdline_hist+jumplist+persistent_undo +virtualedit
  +cmdline_info+keymap  +postscript  +visual
  +comments+langmap +printer +visualextra
  +conceal +libcall +profile +viminfo
  +cryptv  +linebreak   -python  +vreplace
  +cscope  +lispindent  -python3 +wildignore
  +cursorbind  +listcmds+quickfix+wildmenu
  +cursorshape +localmap+reltime +windows
  +dialog_con  -lua +rightleft   +writebackup
  +diff+menu-ruby-X11
  +digraphs+mksession   +scrollbind  -xfontset
  -dnd +modify_fname+signs   -xim
  -ebcdic  +mouse   +smartindent -xsmp
  +emacs_tags  -mouseshape  +startuptime -xterm_clipboard
  +eval+mouse_dec   +statusline  -xterm_save
  +ex_extra+mouse_gpm   -sun_workshop-xpm
  +extra_search-mouse_jsbterm   +syntax  
 system vimrc file: "$VIM/vimrc"
   user vimrc file: "$HOME/.vimrc"
   2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/share/vim"
  Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -Wdate-time  -g -O2 -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=1  
  Linking: gcc   -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed -o vim-lm -ltinfo -lnsl  -lselinux -lacl -lattr -lgpm 
-ldl

  I see, there is -python and -python3

  But all news and documentation say the Vim in Xenial 16.04 comes with
  Python3 enabled. I am confused? A bug?

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

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

[Touch-packages] [Bug 1548061] Re: vim

[Adam Conrad]

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

** This bug has been marked a duplicate of bug 1574897
   Upgrading to 16.04 disables Python3?

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

Title:
  vim

Status in vim package in Ubuntu:
  New

Bug description:
  vim 7.4.963 in ubuntu 16.04
  without python support
  need rebuild with python support

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

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

[Touch-packages] [Bug 1591382] Re: [SRU] Add support for newton cloud-archive

[Adam Conrad]

Hello Corey, or anyone else affected,

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

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

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

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

** Changed in: software-properties (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  [SRU] Add support for newton cloud-archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  Fix Committed
Status in software-properties source package in Yakkety:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:newton
 cloud-archive:newton-proposed

  This will also need to be SRU'ed back to xenial.

  [Impact]
  End users have to manually enable the newton cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:newton
  sudo add-apt-repository cloud-archive:newton-proposed

  [Regression potential]
  Limited - just a data item addition

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

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