date:20161215

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

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

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

Title:
  No login prompt when waking up the computer from suspend

Status in lightdm package in Ubuntu:
  Expired

Bug description:
  Ubuntu 16.10 x64.

* I let my computer go to sleep.
* Several hours later I wake it up.

  Expected result: the lock screen is displayed, waiting for me to input my 
password.
  Actual result: I am directly back to my desktop.

  I verified that the option to ask for my password at wake up is
  correctly checked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 15 18:34:14 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-14 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1645698] Re: [SRU] network-manager 1.2.4

2016-12-15 Thread Aron Xu

@jbicha, I would make updates to all 3 series quickly to introduce that
fix, but it would be really nice to have an 1.2.4 update because it's
been long waited (without postponing to wait for other series). What do
you think?

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

Title:
  [SRU] network-manager 1.2.4

Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager source package in Xenial:
  Triaged

Bug description:
  [Impact]

  This SRU would try to have the latest upstream point release of 1.2.x
  land in Xenial, which is the successor of the current 1.2.2 version,
  fixing quite some bugs that's suitable to land in the sable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  [Regression Potential]

  This version has been in yakkety for sometime, and there's no report
  of regressions until now.

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

All the listed test cases appear to have been covered and successfully
verified for both xenial and yakkety. We're just waiting for Jason to do
his testing (he said "tomorrow" Friday December 16...). If that gets
done then, the updates should be good to release on Monday (there aren't
usually SRU promotions to -updates on Fridays).

** Description changed:

  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
  
  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)
  
  Bugs related to uploads for this specific SRU:
  
  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU
  
  ifupdown:
  bug 1629972: networking.service takes down lo on stop
  
  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)
  
  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD
  
  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot
  
  [Impact]
  
  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in an
  ipv6-only environment is affected.
  
  [Stable Fix]
  
  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.
  
  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.
  
  [Test Case]
  
  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to, and
  see it fail to configure the network.
  
  [Regression Potential]
  
  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.
  
  [Tests for verification]
  
  Whoever checks the last one off, please mark verification done.
  
  MAAS test cases:
   X / Y
  [+]/[+] MAAS on IPv6-only network
  [+]/[+] MAAS on IPv4-only network
  [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
  [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)
  
  Non-MAAS test cases:
   X / Y
  [+]/[+] ip="" and ip6 not present
  [+]/[+] ip=:eth0:dhcp and ip6 not present
  [+]/[+] d-i install with iSCSI remote root should complete normally
- [+]/[ ] Validate normal boot without remote root
+ [+]/[+] Validate normal boot without remote root
  [+]/[+] Booting an iSCSI remote root via IPv4 (using ip=)
  [+]/[+] Booting an iSCSI remote root via IPv6 (using ip6=)
  [+]/[+] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
  [+]/[+] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)52-54-00-53-5d-24
  [+]/[+] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking

[Touch-packages] [Bug 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names

Milestoning, since we should try to not drop the ball on this bug; I
will need to revisit the mailing list thread and how exactly we do the
naming for these devices.

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

** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-17.03

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

Title:
  USB NICs get too long name for ifupdown aliases or bridge names

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  I have a USB NIC that is connected to my denial system. I tried to
  create an alias, and after reboot, it wasn't created. When I manually
  try to bring it up I have the error.

  /e/n/i:

  auto enx000ec688b79f
  iface enx000ec688b79f inet static
  address 10.90.90.1
  netmask 255.255.255.0

  auto enx000ec688b79f:1
  iface enx000ec688b79f:1 inet static
  address 192.168.100.1
  netmask 255.255.255.0

  ubuntu@maas00:~$ sudo ifup enx000ec688b79f
  ubuntu@maas00:~$ sudo ifup enx000ec688b79f:1
  RTNETLINK answers: Numerical result out of range
  Failed to bring up enx000ec688b79f:1.

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

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

[Touch-packages] [Bug 1649313] Re: Mediascanner is not working

2016-12-15 Thread Michi Henning

I downloaded the latest image from ubuntu-touch/staging/ubuntu

"OS Build Details" in system settings reports r85, 20161215

Unfortunately, I can't provide the output from system-image-cli because,
since flashing this image, USB is broken. I can no longer get my desktop
to recognize the USB port. It's as if the USB port is dead (lsusb
doesn't find the device). Developer mode is on, and when I plug my
Aquaris E5 into the same port using the same cable, it's recognized just
fine.

Anyway, after installing this image, the SD card is no longer recognized
at all, no matter how many times I insert it. (The same card works fine
in the E5.)

I guess the problem is with the image from ubuntu-touch/staging/ubuntu

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

Title:
  Mediascanner is not working

Status in mediascanner2 package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New

Bug description:
  Story: looks like this is a well known bug but there wasn't a bug
  report yet so I'm opening it. Sdcards detection doesn't work in
  frieza_arm64.

  Environment:

  current build number: 99
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-12-12 12:21:18
  version version: 99
  version ubuntu: 20161210
  version device: 20161014.0
  version custom: 20161210

  Steps:

  1º Put some media files(songs,videos) on a sdcard
  2º Install the sdcard in frieza
  3º Open music app or music/video scopes

  Current result: music app reports no songs were found and music/video
  scopes don't show the media files either

  Expected result: all files from sdcard or other external devices
  should be detected

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

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

[Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

The resolvconf portion of this issue has been moved to bug #1649931.
I'm removing resolvconf 1.78ubuntu3 from xenial-proposed and will
replace it with a resolvconf 1.78ubuntu4 with the correct bug ref.

** Changed in: resolvconf (Ubuntu Xenial)
   Status: Fix Committed => Invalid

** Changed in: resolvconf (Ubuntu Yakkety)
   Status: In Progress => Invalid

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  Fix Released
Status in cloud-init package in Ubuntu:
  Triaged
Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in resolvconf source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  New
Status in resolvconf source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Fix Released
Status in resolvconf package in Debian:
  Fix Committed

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms

  cloud-init would need networkd to run at or before
  'networking.service' so it can raise networking to then find and use
  network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links

  # grep cloud-init /usr/share/snappy/dpkg.list
  ii  cloud-init

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

Hello Ryan, or anyone else affected,

Accepted resolvconf into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.78ubuntu4 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: resolvconf (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 resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1649931

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

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

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  
  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  
  Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash

# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd

# enable networkd and netplan
apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
version: 2
ethernets:
  eth0:
dhcp4: true
  EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

netplan generate

# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a 
After=systemd-network-wait-online.service' 
/lib/systemd/system/cloud-init.service

reboot

# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

# the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.

  
  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.

  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

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

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

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

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

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  
  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  
  Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash

# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd

# enable networkd and netplan
apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
version: 2
ethernets:
  eth0:
dhcp4: true
  EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

netplan generate

# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a 
After=systemd-network-wait-online.service' 
/lib/systemd/system/cloud-init.service

reboot

# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

# the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.

  
  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.

  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online.

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

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

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

>> For systemd portion, we carry the
>>  systemd-networkd-resolvconf-update.service as a delta from Debian

> I'm not sure what you mean here; the systemd package in zesty is currently
> in sync with Debian.

Ok, it appears that post-16.04, systemd-networkd-resolvconf-
update.service is dropped from the package in favor of
debian/extra/units/systemd-resolved.service.d/resolvconf.conf, so this
patch does not apply.

I have verified that there is no ordering bug post-16.04, provided that
the changes to resolvconf are applied. /lib/systemd/system/systemd-
resolved.service.d/resolvconf.conf causes systemd-resolved to notify
resolvconf of its nameserver, if /run/resolvconf/enable-updates exists.
/run/resolvconf/enable-updates exists if resolvconf.service is started.
resolvconf.service is started Before=network-pre.target; network.target
is After=network-pre.target; systemd-resolved.service is
After=network.target.  So only the change to resolvconf is needed for
yakkety and beyond.

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in resolvconf source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  
  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  
  Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash

# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd

# enable networkd and netplan
apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
version: 2
ethernets:
  eth0:
dhcp4: true
  EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

netplan generate

# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a 
After=systemd-network-wait-online.service' 
/lib/systemd/system/cloud-init.service

reboot

# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

# the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.

  
  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.

  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  Dec 15 19:28:56.124555

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

2016-12-15 Thread David Barnett

So vim.gtk3 crashes consistently for all Ubuntu users on Unity desktop?
Is anyone still working on a 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/1611363

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

Status in vim:
  Unknown
Status in vim package in Ubuntu:
  Confirmed
Status in vim source package in Xenial:
  Confirmed

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

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

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

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

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

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

[Touch-packages] [Bug 1649662] Re: [regression] resizing a gtk+3/mir app makes it unusable - pixels get stretched and input stops working

Invalid for GTK. I have now reproduced the same bug using a pure Mir
demo (which is software rendered in case that's relevant):

$ mir_demo_client_progressbar 20 --desktop_file_hint=unity8

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

** Summary changed:

- [regression] resizing a gtk+3/mir app makes it unusable - pixels get 
stretched and input stops working
+ [regression] resizing a some apps in Unity8 makes them distorted and freeze 
(usually software clients)

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

Title:
  [regression] resizing a some apps in Unity8 makes them distorted and
  freeze (usually software clients)

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8 + proposed and 16.04 + overlay PPA
  mir 0.25
  miral 0.25
  unity8/zesty-proposed,now 8.15+17.04.20161207.1-0ubuntu1 amd64 
[installed,automatic]

  steps:
  1)run gedit, nautilus, sol or whatever gtk+3 app ("ubuntu-app-launch sol" for 
ex). if you are not sure how to launch a gtk3 app run 
"ubuntu-app-launch-appids" first to see the appids and then "ubuntu-app-launch 
"

  2) resize the window (the context gets stretched in a weird way and
  input doesn't work anymore)

  see attached screenshot

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

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

[Touch-packages] [Bug 1649662] Re: [regression] resizing a some apps in Unity8 makes them distorted and freeze (usually software clients)

Also the bug does not exist in Mir demo servers.

This is just a QtMir/Unity8 bug.

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

Title:
  [regression] resizing a some apps in Unity8 makes them distorted and
  freeze (usually software clients)

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8 + proposed and 16.04 + overlay PPA
  mir 0.25
  miral 0.25
  unity8/zesty-proposed,now 8.15+17.04.20161207.1-0ubuntu1 amd64 
[installed,automatic]

  steps:
  1)run gedit, nautilus, sol or whatever gtk+3 app ("ubuntu-app-launch sol" for 
ex). if you are not sure how to launch a gtk3 app run 
"ubuntu-app-launch-appids" first to see the appids and then "ubuntu-app-launch 
"

  2) resize the window (the context gets stretched in a weird way and
  input doesn't work anymore)

  see attached screenshot

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

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

[Touch-packages] [Bug 1649662] Re: [regression] resizing a gtk+3/mir app makes it unusable - pixels get stretched and input stops working

Confirmed. The bug has now escaped proposed and is in zesty.

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

Title:
  [regression] resizing a some apps in Unity8 makes them distorted and
  freeze (usually software clients)

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8 + proposed and 16.04 + overlay PPA
  mir 0.25
  miral 0.25
  unity8/zesty-proposed,now 8.15+17.04.20161207.1-0ubuntu1 amd64 
[installed,automatic]

  steps:
  1)run gedit, nautilus, sol or whatever gtk+3 app ("ubuntu-app-launch sol" for 
ex). if you are not sure how to launch a gtk3 app run 
"ubuntu-app-launch-appids" first to see the appids and then "ubuntu-app-launch 
"

  2) resize the window (the context gets stretched in a weird way and
  input doesn't work anymore)

  see attached screenshot

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

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

[Touch-packages] [Bug 1649662] Re: [regression] resizing a gtk+3/mir app makes it unusable - pixels get stretched and input stops working

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

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

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

Title:
  [regression] resizing a some apps in Unity8 makes them distorted and
  freeze (usually software clients)

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8 + proposed and 16.04 + overlay PPA
  mir 0.25
  miral 0.25
  unity8/zesty-proposed,now 8.15+17.04.20161207.1-0ubuntu1 amd64 
[installed,automatic]

  steps:
  1)run gedit, nautilus, sol or whatever gtk+3 app ("ubuntu-app-launch sol" for 
ex). if you are not sure how to launch a gtk3 app run 
"ubuntu-app-launch-appids" first to see the appids and then "ubuntu-app-launch 
"

  2) resize the window (the context gets stretched in a weird way and
  input doesn't work anymore)

  see attached screenshot

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

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

[Touch-packages] [Bug 1649662] Re: [regression] resizing a gtk+3/mir app makes it unusable - pixels get stretched and input stops working

** Summary changed:

- resizing a gtk+3/mir app makes it unusable - pixels get stretched and input 
stops working
+ [regression] resizing a gtk+3/mir app makes it unusable - pixels get 
stretched and input stops working

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

Title:
  [regression] resizing a some apps in Unity8 makes them distorted and
  freeze (usually software clients)

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8 + proposed and 16.04 + overlay PPA
  mir 0.25
  miral 0.25
  unity8/zesty-proposed,now 8.15+17.04.20161207.1-0ubuntu1 amd64 
[installed,automatic]

  steps:
  1)run gedit, nautilus, sol or whatever gtk+3 app ("ubuntu-app-launch sol" for 
ex). if you are not sure how to launch a gtk3 app run 
"ubuntu-app-launch-appids" first to see the appids and then "ubuntu-app-launch 
"

  2) resize the window (the context gets stretched in a weird way and
  input doesn't work anymore)

  see attached screenshot

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

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

[Touch-packages] [Bug 1650022] Re: We need a "close" action for killing an app in a trust prompt

** Tags removed: unity-desktop
** Tags added: unity8-desktop

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

Title:
  We need a "close" action for killing an app in a trust prompt

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  The original designs for trust prompts included a close action in the
  header to close apps that were opened in a trust session.  This is
  particularly important when apps might not behave well or hang, there
  is no way out.  The close action is like a back button to take you
  back out of the app.

  We're close to landing trust session support in content-hub, where
  we'll open source apps for content picking in a trust prompt.  We've
  found apps that have a tendency to hang, leaving the user no way out
  besides killing both the source and destination apps.  Clearly those
  apps need some fixing, but we need to give the user an easy way out.

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

** Changed in: isc-dhcp (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: initramfs-tools (Ubuntu Xenial)
Milestone: None => xenial-updates

** Changed in: initramfs-tools (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)

  Bugs related to uploads for this specific SRU:

  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU

  ifupdown:
  bug 1629972: networking.service takes down lo on stop

  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)

  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD

  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  [Stable Fix]

  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.

  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

  [Tests for verification]

  Whoever checks the last one off, please mark verification done.

  MAAS test cases:
   X / Y
  [+]/[+] MAAS on IPv6-only network
  [+]/[+] MAAS on IPv4-only network
  [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
  [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)

  Non-MAAS test cases:
   X / Y
  [+]/[+] ip="" and ip6 not present
  [+]/[+] ip=:eth0:dhcp and ip6 not present
  [+]/[+] d-i install with iSCSI remote root should complete normally
  [+]/[ ] Validate normal boot without remote root
  [+]/[+] Booting an iSCSI remote root via IPv4 (using ip=)
  [+]/[+] Booting an iSCSI remote root via IPv6 (using ip6=)
  [+]/[+] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
  [+]/[+] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)52-54-00-53-5d-24
  [+]/[+] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)

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

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

Re: [Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

On Thu, Dec 15, 2016 at 09:43:48PM -, Ryan Harper wrote:
> I don't disagree (that saying few folks impacted means low).

> This portion was split out from the previous systemd SRU

> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636912

> in which the changes were classified in the same way, so I was coping over
> the assessment done by pitti and Foundations with which I agree.

> I'd be happy if someone else could comment on whether they disagree with
> the assessment.

> IMO the risk is low:

The point here is that 'regression potential' is not meant to be a scalar,
it's meant to be a description of where regressions are possible so that we
can assess whether additional testing is needed to guard against those
regressions.

And also to ensure that the SRU submitter has carefully thought about this
question, since going through that exercise usually results in a better SRU.

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in resolvconf source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash

# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd

# enable networkd and netplan
apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
version: 2
ethernets:
  eth0:
dhcp4: true
  EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

netplan generate

# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a 
After=systemd-network-wait-online.service' 
/lib/systemd/system/cloud-init.service

reboot

# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

# the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.

  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.

  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online.

To manage notifications about this bug

[Touch-packages] [Bug 1650419] Re: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned

2016-12-15 Thread Seth Arnold

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

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

Title:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in bamf package in Ubuntu:
  New
Status in ca-certificates package in Ubuntu:
  New

Bug description:
  while upgrading from ubuntu 16.04 LTS to 60.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Dec 16 02:48:58 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-02-12 (307 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to yakkety on 2016-12-16 (0 days ago)

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

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

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

resolvconf (1.79ubuntu4) zesty; urgency=medium

  * debian/resolvconf.service: Add missing Wants=network-pre.target.

 -- Martin Pitt   Thu, 08 Dec 2016 10:21:12
+0100

resolvconf (1.79ubuntu3) zesty; urgency=medium

  * debian/resolvconf.service: resolvconf service must run before any of the
  possible network configuration services (ifupdown, networkd, NetworkManager)
  so use network-pre.target instead of service names. (LP: #1636912)

 -- Ryan Harper   Wed, 07 Dec 2016 03:30:55
-0600


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

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

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

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in resolvconf source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  
  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  
  Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash

# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd

# enable networkd and netplan
apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
version: 2
ethernets:
  eth0:
dhcp4: true
  EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

netplan generate

# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a 
After=systemd-network-wait-online.service' 
/lib/systemd/system/cloud-init.service

reboot

# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

# the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.

  
  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.

  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online.

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

-- 
Mailing

[Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

Hello Ryan, or anyone else affected,

Accepted resolvconf into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.78ubuntu3 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: resolvconf (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  Fix Released
Status in cloud-init package in Ubuntu:
  Triaged
Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in resolvconf source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  New
Status in resolvconf source package in Yakkety:
  In Progress
Status in systemd source package in Yakkety:
  Fix Released
Status in resolvconf package in Debian:
  Fix Committed

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms

  cloud-init would need networkd to run at or before
  'networking.service' so it can raise networking to then find and use
  network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list
  ii

Re: [Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

On Thu, Dec 15, 2016 at 09:44:32PM -, Ryan Harper wrote:
> On Thu, Dec 15, 2016 at 10:27 PM, Brian Murray  wrote:

> > How is this fixed in the development release?

> For systemd portion, we carry the
> systemd-networkd-resolvconf-update.service as a delta from Debian

I'm not sure what you mean here; the systemd package in zesty is currently
in sync with Debian.

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in resolvconf source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  
  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  
  Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash

# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd

# enable networkd and netplan
apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
version: 2
ethernets:
  eth0:
dhcp4: true
  EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

netplan generate

# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a 
After=systemd-network-wait-online.service' 
/lib/systemd/system/cloud-init.service

reboot

# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

# the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.

  
  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.

  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online.

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

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

[Touch-packages] [Bug 1649960] Re: Apport fails to upload some crash reports

2016-12-15 Thread Jeremy Bicha

** No longer affects: ubuntu-gnome

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

Title:
  Apport fails to upload some crash reports

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  For some reason I often find that if I try to report a .crash (which
  the GUI for some reason didn't alert me about) file this will happen
  (this happens with all the Apport tools to report a crash, this just
  so happens to be the apport-cli example):

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (6.7 MB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C): S

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.

[Touch-packages] [Bug 1650419] Re: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned

2016-12-15 Thread Pushpa Raj Paudel

sorry while upgrading from ubuntu 16.04 LTS to 16.10

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

Title:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  while upgrading from ubuntu 16.04 LTS to 60.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Dec 16 02:48:58 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-02-12 (307 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to yakkety on 2016-12-16 (0 days ago)

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

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

[Touch-packages] [Bug 1650419] [NEW] package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned

2016-12-15 Thread Pushpa Raj Paudel

Public bug reported:

while upgrading from ubuntu 16.04 LTS to 60.10

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: ca-certificates 20160104ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Fri Dec 16 02:48:58 2016
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2016-02-12 (307 days ago)
InstallationMedia: It
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: ca-certificates
Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to yakkety on 2016-12-16 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  while upgrading from ubuntu 16.04 LTS to 60.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Dec 16 02:48:58 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-02-12 (307 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to yakkety on 2016-12-16 (0 days ago)

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

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

Re: [Touch-packages] [Bug 1650389] Re: Installing snapd on 14.04.5 desktop downgrades xorg et al.

2016-12-15 Thread Mark Shuttleworth

On 15/12/16 17:25, Steve Langasek wrote:
> This was a known limitation when the SRU went through, and it was
> allowed because the understood target for snapd on 14.04 was
> server/cloud environments, not desktops.  Has that changed?

It's unexpected for me, and will be substantially difficult to message
("install this but not on a desktop"). So I think we need to press on
this to understand it better. We do want snaps on 14.04, its a key part
of the value we're offering, but we can't make that a choice that
negatively impacts a desktop.

Mark

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

Title:
  Installing snapd on 14.04.5 desktop downgrades xorg et al.

Status in Snappy:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When trying to install the latest snapd on a 14.04.5 desktop image,
  the installation of systemd (as a dependency of snapd) triggers a
  whole bunch of downgrades as systemd-shim is removed and replaced with
  systemd.

  We have to adjust the packaging such that installation of systemd does
  not trigger such behavior for packages depending on systemd-shim in
  trusty.

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

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

[Touch-packages] [Bug 1595607] Re: /bin/nano:* Error in `nano': free(): invalid next size (normal): ADDR *

This fix made it into Yakkety and Zesty, but not Xenial.  I've uploaded
a fix to the Xenial SRU queue for review by the Ubuntu SRU team.

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

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

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

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

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

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

Title:
  /bin/nano:*** Error in `nano': free(): invalid next size (normal):
  ADDR ***

Status in nano package in Ubuntu:
  Fix Released
Status in nano source package in Xenial:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding nano.  This problem was most recently seen with version
  2.5.3-2, the problem page at
  https://errors.ubuntu.com/problem/d609e39daa79867af99f7c1c75f3db7b998971d9
  contains more details.

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

All non-MAAS remote rootfs -based test cases have been verified for
Yakkety now. Everything checks out. I will now do the last test case
remaining which is to do a standard (non-remote root) install and
upgrade to proposed packages to make sure standard installs aren't
broken.

** Description changed:

  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
  
  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)
  
  Bugs related to uploads for this specific SRU:
  
  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU
  
  ifupdown:
  bug 1629972: networking.service takes down lo on stop
  
  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)
  
  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD
  
  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot
  
  [Impact]
  
  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in an
  ipv6-only environment is affected.
  
  [Stable Fix]
  
  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.
  
  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.
  
  [Test Case]
  
  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to, and
  see it fail to configure the network.
  
  [Regression Potential]
  
  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.
  
  [Tests for verification]
  
  Whoever checks the last one off, please mark verification done.
  
  MAAS test cases:
-  X / Y
+  X / Y
  [+]/[+] MAAS on IPv6-only network
  [+]/[+] MAAS on IPv4-only network
  [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
  [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)
  
  Non-MAAS test cases:
-  X / Y
- [+]/[ ] ip="" and ip6 not present
- [+]/[ ] ip=:eth0:dhcp and ip6 not present
- [+]/[ ] d-i install with iSCSI remote root should complete normally
+  X / Y
+ [+]/[+] ip="" and ip6 not present
+ [+]/[+] ip=:eth0:dhcp and ip6 not present
+ [+]/[+] d-i install with iSCSI remote root should complete normally
  [+]/[ ] Validate normal boot without remote root
- [+]/[ ] Booting an iSCSI remote root via IPv4 (using ip=)
- [+]/[ ] Booting an iSCSI remote root via IPv6 (using ip6=)
- [+]/[ ] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
- [+]/[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)
- [+]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)
+ [+]/[+] Booting an iSCSI remote root via IPv4 (using ip=)
+ [+]/[+] Booting an iSCSI remote root via IPv6 (using ip6=)
+ [+]/[+] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
+ [+]/[+] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)52-54-00-53-5d-24
+ [+]/[+] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

2016-12-15 Thread LaMont Jones

Final review feedback has been incorporated into initramfs-tools, isc-
dhcp, and open-iscsi, and uploaded to zesty.

** Description changed:

  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
  
  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)
  
  Bugs related to uploads for this specific SRU:
  
  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU
  
  ifupdown:
  bug 1629972: networking.service takes down lo on stop
  
  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)
  
  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD
  
  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot
  
  [Impact]
  
  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in an
  ipv6-only environment is affected.
  
  [Stable Fix]
  
  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.
  
  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.
  
  [Test Case]
  
  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to, and
  see it fail to configure the network.
  
  [Regression Potential]
  
  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.
  
  [Tests for verification]
  
  Whoever checks the last one off, please mark verification done.
  
  MAAS test cases:
- [+] MAAS on IPv6-only network
- [+] MAAS on IPv4-only network
- [+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
- [+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)
+  X / Y
+ [+]/[+] MAAS on IPv6-only network
+ [+]/[+] MAAS on IPv4-only network
+ [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
+ [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)
  
  Non-MAAS test cases:
- X/Y
+  X / Y
  [+]/[ ] ip="" and ip6 not present
  [+]/[ ] ip=:eth0:dhcp and ip6 not present
  [+]/[ ] d-i install with iSCSI remote root should complete normally
  [+]/[ ] Validate normal boot without remote root
  [+]/[ ] Booting an iSCSI remote root via IPv4 (using ip=)
  [+]/[ ] Booting an iSCSI remote root via IPv6 (using ip6=)
  [+]/[ ] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
  [+]/[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)
  [+]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not

[Touch-packages] [Bug 1627504] Re: [MS-7968, Realtek ALC1150, Black SPDIF Out, Rear] Underruns, dropouts or crackling sound. Test tones work but sound immediatly returns to poor quality after completi

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [MS-7968, Realtek ALC1150, Black SPDIF Out, Rear] Underruns, dropouts
  or crackling sound. Test tones work but sound immediatly returns to
  poor quality after completion.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Using digital audio output on Intel driver.
  Sound from games is barely decipherable over the distortion/crackle. Playing 
test tones (left/right test and on bug report) work fine but the noise returns 
when the clips are completed.

  Tried tsched=0, hda fix 1 and hda fix 2. no luck yet
  When first added tsched command, it blurs the screen and no audio devices are 
available. remove, restart, re-add and screen and audio back but problem still 
present (maybe just spelt wrong first time?).

  Help appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nytonial   1759 F pulseaudio
   /dev/snd/controlC0:  nytonial   1759 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Sep 25 15:28:53 2016
  InstallationDate: Installed on 2016-09-07 (17 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black SPDIF Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [MS-7968, Realtek ALC1150, Black SPDIF Out, Rear] Underruns, dropouts 
or crackling sound
  UpgradeStatus: Upgraded to xenial on 2016-09-08 (16 days ago)
  dmi.bios.date: 02/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A XPOWER GAMING TITANIUM EDITION(MS-7968)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.60:bd02/23/2016:svnMSI:pnMS-7968:pvr3.0:rvnMSI:rnZ170AXPOWERGAMINGTITANIUMEDITION(MS-7968):rvr3.0:cvnMSI:ct3:cvr3.0:
  dmi.product.name: MS-7968
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-09-25T14:21:58.691691

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

-- 
Mailing list: https://launchpad.net/~touch-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

2016-12-15 Thread Timo Aaltonen

zesty has 12.0.4, and 13.0.2 in proposed, closing

** Summary changed:

- Mesa 12.0.4 - multiple important fixes, stable branch
+ Mesa 12.0.5 - multiple important fixes, stable branch

** Description changed:

  [Impact]
- Mesa 12.0.4 is now available as a point release in the stable branch. Mesa 
has MRE for these.
+ 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]
  There's only a modest number of changes to the drivers, the performance boost 
for Radeon is result of one fix for the shaders.
  
+ This release will be tested by the certification team on a set of
+ machines, they will post the results here when done.
+ 
  [Regression potential]
  The release consists of cherry-picks from master, specifically selected as 
bugfixes. Regression potential should be low.

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/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 Yakkety:
  Confirmed

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]
  There's only a modest number of changes to the drivers, the performance boost 
for Radeon is result of one fix for the shaders.

  This release will be tested by the certification team on a set of
  machines, they will post the results here when done.

  [Regression potential]
  The release consists of cherry-picks from master, specifically selected as 
bugfixes. Regression potential 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 1645798] Re: No snaps appear in scope on Core 16

2016-12-15 Thread Rodney Dawes

You can run the scope with U1_DEBUG=1 set, and it will spew more debug
info.

I doubt it's threads. We're not using QtDBus here really. The ubuntu-
download-manager code does use it, but we're no longer really using it
in the scope, only the client object gets created on startup, and then
never used. There is an MP to remove the dependency on ubuntu-download-
manager and libclick in https://bileto.ubuntu.com/#/ticket/2306, and I
asked Michael to build a snap with it and try, but it was still failing
for him with that.

I guess you'd need to run the scope manually under gdb to be able to get
a trace, but I can't tell you how to do that on an all snaps system,
unfortunately.

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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

[Touch-packages] [Bug 1649960] Re: Apport fails to upload some crash reports

2016-12-15 Thread Nikita Yerenkov-Scott

** Description changed:

  For some reason I often find that if I try to report a .crash (which the
  GUI for some reason didn't alert me about) file this will happen (this
  happens with all the Apport tools to report a crash, this just so
  happens to be the apport-cli example):
- 
  
  *** Send problem report to the developers?
  
  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.
  
- What would you like to do? Your options are:
-   S: Send report (6.7 MB)
-   V: View report
-   K: Keep report file for sending later or copying to somewhere else
-   I: Cancel and ignore future crashes of this program version
-   C: Cancel
- Please choose (S/V/K/I/C): S
- 
- *** Collecting problem information
- 
- The collected information can be sent to the developers to improve the
- application. This might take a few minutes.
-

[Touch-packages] [Bug 1542597] Re: dnsmasq breaks Steam downloads on Comcast

2016-12-15 Thread Joshua Powers

Thank you for taking the time to report this bug and helping to make
Ubuntu better. In an effort to keep an up-to-date list of bugs to work I
have reviewed this report to verify it still requires a fix and it
occurs on a supported version of Ubuntu.

Can you please let us know if this is still issue and if so give us a
reproducible address to query? On 16.04 I do not see this behavior when
using dnsmasq. We'd be grateful if you would then provide an update and
then change the bug status back to New.

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

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

Title:
  dnsmasq breaks Steam downloads on Comcast

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  TL;DR: With dnsmasq configured, "nslookup
  cdn.cs.comcast.steampowered.com" (rather, the query, not nslookup
  itself) hangs.  As a result of the DNS query hanging, Steam is unable
  to download any game content.

  Longer explanation, which I posted on the Steam forum at
  http://steamcommunity.com/discussions/forum/1/412446292762583371/ to
  help other users:

  I had a persistent problem with Steam not downloading games on Ubuntu,
  even on the same machine and same network where it worked fine under
  Windows (both 7 and 10). Here's an explanation of why and how to fix
  it, since most people will not be able to diagnose it.

  Background:

  Like most big data providers, Steam has a lot of servers hosted at
  various ISPs. When you download a game, you're directed to servers
  that are topologically closer to you--usually ones hosted by the ISP
  you use. In my case, this is Comcast, and Steam uses the host name
  cdn.comcast.cs.steampowered.com.

  Ubuntu Desktop uses a caching DNS server called dnsmasq. Besides
  providing caching services, it captures advertised hostnames on the
  network, allowing you to refer to other machines by name without
  having to set up DNS.

  Symptom:

  You'll get dialog windows and messages in the Steam log file saying
  that connections timed out. No downloads will actually work.

  Interestingly, nowhere does it explicitly tell you that it's actually
  the DNS query that's timing out, as opposed to the connection to the
  actual content server. This confused me quite a bit.

  The problem:

  Steam's DNS and dnsmasq don't get along. The list of DNS records for
  cdn.comcast.cs.steampowered.com is long enough that the response
  doesn't fit in a UDP packet. Normally this is retried transparently
  over TCP and works fine. However, dnsmasq stalls and times out on this
  request. (Don't ask me why. I haven't debugged it--yet.) As a result,
  all attempts to connect to the Steam content servers fail, and no
  downloads occur.

  Note: I've only run the Steam client on Ubuntu 14.10 and 15.04. I do
  not know whether this problem affects other versions.

  Workaround:

  The obvious workaround is to stop using dnsmasq. However, it's
  somewhat hardwired into Ubuntu. Here's what I did:

  # apt-get install unbound # do this first or you'll be sad
  # cd /etc/NetworkManager
  # service NetworkManager stop
  # vi NetworkManager.conf # or whatever editor you want; I don't care
  [change "dns=dnsmasq" to "dns=unbound"]
  # rm /etc/resolv.conf # don't forget this
  # service NetworkManager start

  Now all your DNS queries should go through your local unbound server
  (at 127.0.0.1 a.k.a. localhost), retries over TCP should work as
  expected, and Steam should be able to download just fine. You can test
  it with:

  # nslookup cdn.comcast.cs.steampowered.com

  If that hangs or returns SERVFAIL or REFUSED, you still have a
  problem.

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

d-i install with proposed enable also passed. As far as I am concerned,
this is verification-done for *Xenial*.

We may still want to wait for Jason DeRose's input on the SRU.

** Description changed:

  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
  
  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)
  
  Bugs related to uploads for this specific SRU:
  
  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU
  
  ifupdown:
  bug 1629972: networking.service takes down lo on stop
  
  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)
  
  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD
  
  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot
  
  [Impact]
  
  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in an
  ipv6-only environment is affected.
  
  [Stable Fix]
  
  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.
  
  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.
  
  [Test Case]
  
  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to, and
  see it fail to configure the network.
  
  [Regression Potential]
  
  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.
  
  [Tests for verification]
  
  Whoever checks the last one off, please mark verification done.
  
  MAAS test cases:
  [+] MAAS on IPv6-only network
  [+] MAAS on IPv4-only network
  [+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
  [+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)
  
  Non-MAAS test cases:
  X/Y
  [+]/[ ] ip="" and ip6 not present
  [+]/[ ] ip=:eth0:dhcp and ip6 not present
- [ ]/[ ] d-i install with iSCSI remote root should complete normally
+ [+]/[ ] d-i install with iSCSI remote root should complete normally
  [+]/[ ] Validate normal boot without remote root
  [+]/[ ] Booting an iSCSI remote root via IPv4 (using ip=)
  [+]/[ ] Booting an iSCSI remote root via IPv6 (using ip6=)
  [+]/[ ] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
  [+]/[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)
  [+]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458:

[Touch-packages] [Bug 1650389] Re: Installing snapd on 14.04.5 desktop downgrades xorg et al.

I do not believe there is any path to successfully install snapd on a
14.04 desktop system.  Only one of systemd and systemd-shim can own the
systemd dbus services; systemd doesn't implement them in a way that will
work with upstart as pid1, which means we need systemd-shim to own them
so that the desktop consumers of the services will function; and it's
intrusive surgery to make systemd work without registering them.

This was a known limitation when the SRU went through, and it was
allowed because the understood target for snapd on 14.04 was
server/cloud environments, not desktops.  Has that changed?

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

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

Title:
  Installing snapd on 14.04.5 desktop downgrades xorg et al.

Status in Snappy:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When trying to install the latest snapd on a 14.04.5 desktop image,
  the installation of systemd (as a dependency of snapd) triggers a
  whole bunch of downgrades as systemd-shim is removed and replaced with
  systemd.

  We have to adjust the packaging such that installation of systemd does
  not trigger such behavior for packages depending on systemd-shim in
  trusty.

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

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

[Touch-packages] [Bug 1496163] Re: i915 firmware is not copied to initrd

2016-12-15 Thread Philipp Kern

Attached is a debdiff for a SRU for trusty.

** Patch added: "initramfs-tools_0.103ubuntu4.5_0.103ubuntu4.6.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1496163/+attachment/4792198/+files/initramfs-tools_0.103ubuntu4.5_0.103ubuntu4.6.debdiff

** Description changed:

- On Skylake, the skl_dmc firmware is failing to load. From dmesg:
+ [ Impact ]
+ 
+ On Skylake, skl_dmc firmware is not incorporated into the initramfs.
+ This is because it is a symlink to a versioned blob and the initramfs-
+ tools hook does not dereference symlinks. As the driver is actually
+ loaded from the initramfs, the firmware is missing for the lifetime of
+ the boot, which means that the GPU cannot enter its lowest available
+ power states plus some hotplugging scenarios are broken. This all
+ manifests itself as such in dmesg:
  
  [0.728803] i915 :00:02.0: Direct firmware load for 
i915/skl_dmc_ver1.bin failed with error -2
  [0.728817] [drm:i915_firmware_load_error_print [i915]] *ERROR* failed to 
load firmware i915/skl_dmc_ver1.bin (0)
  
- This means the GPU can't enter its lowest available power states, plus
- many display hotplugging scenarios (that only the skl_dmc firmware can
- handle) are broken.
+ [ Test Case ]
  
- On a whim I tried some other firmware versions:
+ After the fix has been applied and the initrd regenerates, the firmware
+ should load successfully after a reboot.
  
- 1) pointed the skl_dmc_ver1.bin symlink to skl_dmc_ver1_18.bin (instead
- of skl_dmc_ver1_19.bin)
+ [ Regression Potential ]
  
- 2) downloaded the latest (skl_dmc_ver1_21.bin) and pointed the
- skl_dmc_ver1.bin symlink to it
- 
- But neither corrected the situation.
- 
- Thanks!
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 15.10
- Package: linux-image-4.2.0-10-generic 4.2.0-10.11
- ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
- Uname: Linux 4.2.0-10-generic x86_64
- ApportVersion: 2.18.1-0ubuntu1
- Architecture: amd64
- AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  oem1251 F pulseaudio
- CurrentDesktop: Unity
- Date: Tue Sep 15 16:21:24 2015
- HibernationDevice: RESUME=UUID=637df075-0afa-420f-a3ca-342be8bf297f
- IwConfig:
-  enp4s0no wireless extensions.
-  
-  lono wireless extensions.
- Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 04f2:0833 Chicony Electronics Co., Ltd 
-  Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
-  Bus 001 Device 004: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader 
Controller
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- MachineType: System manufacturer System Product Name
- ProcFB: 0 inteldrmfb
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-10-generic 
root=UUID=f967534a-9cc3-4d1a-a7f3-72d28959e3c6 ro i915.verbose_state_checks=1 
quiet splash vt.handoff=7
- RelatedPackageVersions:
-  linux-restricted-modules-4.2.0-10-generic N/A
-  linux-backports-modules-4.2.0-10-generic  N/A
-  linux-firmware1.147
- RfKill:
-  
- SourcePackage: linux
- UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
- UpgradeStatus: No upgrade log present (probably fresh install)
- dmi.bios.date: 08/19/2015
- dmi.bios.vendor: American Megatrends Inc.
- dmi.bios.version: 0403
- dmi.board.asset.tag: Default string
- dmi.board.name: Z170-P D3
- dmi.board.vendor: ASUSTeK COMPUTER INC.
- dmi.board.version: Rev X.0x
- dmi.chassis.asset.tag: Default string
- dmi.chassis.type: 3
- dmi.chassis.vendor: Default string
- dmi.chassis.version: Default string
- dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0403:bd08/19/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-PD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
- dmi.product.name: System Product Name
- dmi.product.version: System Version
- dmi.sys.vendor: System manufacturer
+ Unlikely, as the fix is part of Ubuntu since Wily.

** Tags removed: wily

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

Title:
  i915 firmware is not copied to initrd

Status in Skylinux:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  In Progress
Status in initramfs-tools source package in Vivid:
  In Progress
Status in initramfs-tools source package in Wily:
  Fix Released

Bug description:
  [ Impact ]

  On Skylake, skl_dmc firmware is not incorporated into the initramfs.
  This is because it is a symlink to a versioned blob and the initramfs-
  tools hook does not dereference symlinks. As the driver is actually
  loaded from the initramfs, the firmware is missing for the lifetime of
  the boot, which means that the GPU cannot enter its lowest available
  power states plus some hotplugging scenarios

[Touch-packages] [Bug 1648806] Re: Arbitrary code execution through crafted CrashDB or Package/Source fields in .crash files

This bug was fixed in the package apport - 2.20.4-0ubuntu1

---
apport (2.20.4-0ubuntu1) zesty; urgency=medium

  * New upstream release:
- SECURITY FIX: Restrict a report's CrashDB field to literals.
  Use ast.literal_eval() instead of the generic eval(), to prevent
  arbitrary code execution from malicious .crash files. A user could be
  tricked into opening a crash file whose CrashDB field contains an
  exec(), open(), or similar commands; this is fairly easy as we install a
  MIME handler for these. Thanks to Donncha O'Cearbhaill for discovering
  this!  (CVE-2016-9949, LP: #1648806)
- SECURITY FIX: Fix path traversal vulnerability with hooks execution.
  Ensure that Package: and SourcePackage: fields loaded from reports do
  not contain directories. Until now, an attacker could trick a user into
  opening a malicious .crash file containing "Package:
  ../../../../some/dir/foo" which would execute /some/dir/foo.py with
  arbitrary code. Thanks to Donncha O'Cearbhaill for discovering this!
  (CVE-2016-9950, LP: #1648806)
- SECURITY FIX: apport-{gtk,kde}: Only offer "Relaunch" for recent
  /var/crash crashes.
  It only makes sense to offer relaunching for crashes that just happened
  and the apport UI got triggered on those. When opening a .crash file
  copied from somewhere else or after the crash happened, this is even
  actively dangerous as a malicious crash file can specify any arbitrary
  command to run. Thanks to Donncha O'Cearbhaill for discovering this!
  (CVE-2016-9951, LP: #1648806)
- backends/packaging-apt-dpkg.py: provide a fallback method if using zgrep
  to search for a file in Contents.gz fails due to a lack of memory.
  Thanks Brian Murray.
- bin/apport-retrace: When --core-file is used instead of loading the core
  file and adding it to the apport report just pass the file reference to
  gdb.
  * debian/control: Adjust Vcs-Bzr: for zesty branch.

 -- Martin Pitt   Wed, 14 Dec 2016 21:28:57
+0100

** Changed in: apport (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
  Arbitrary code execution through crafted CrashDB or Package/Source
  fields in .crash files

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Yakkety:
  Fix Released
Status in apport source package in Zesty:
  Fix Released

Bug description:
  Forwarding private (encrypted) mail from Donncha O'Cearbhaill
  :

  = 8< ==
  Hi Martin,

  I have been auditing the Apport software in my free time and
  unfortunately I have found some serious security issues.

  Untrusted files can be passed to apport-gtk as it is registered as the
  default file handler for "text/x-apport" files. The mime-type includes
  .crash files but also any unknown file type which begins with
  "ProblemType: ". An attacker could social engineer a victim into opening
  a malicious Apport crash file simply by clicking on it.

  In apport/ui.py, Apport is reading the CrashDB field and then it then
  evaluates the field as Python code if it begins with a "{". This is very
  dangerous as it can allow remote attackers to execute arbitrary Python code.

  The vulnerable code was introduce on 2012-08-22 in Apport revision
  2464
  (http://bazaar.launchpad.net/~apport-hackers/apport/trunk/files/2464).
  This code was first included in release 2.6.1. All Ubuntu Desktop
  versions after 12.05 (Precise) include this vulnerable code by default.

  An easy fix would be to parse the value as JSON instead of eval()'ing
  it.

  There is also a path traversal issue where the Package or SourcePackage
  fields are not sanitized before being used to build a path to the
  package specific hook files in the /usr/share/apport/package-hooks/
  directory.

  By setting "Package: ../../../../proc/self/cwd/Downloads/rce-hook.py" a
  remote attacker could exploit this bug to execute Python scripts that
  have be placed in the user's Downloads directory.

  Would you like to apply for a CVE for this issues or should I? I'd like
  to see these issue fixed soon so that Ubuntu users can be kept safe. I'm
  planning to publish a blog post about these issues but I'll wait until
  patched version of Apport are available in the repositories.

  Please let me know if you have any questions.

  Kind Regards,
  Donncha
  = 8< ==

  I just talked to Donna on Jabber, and he plans to disclose that in
  around a

[Touch-packages] [Bug 1649582] Re: lxc-start fails to start a unprivileged container - cgroup permissions

2016-12-15 Thread Sneetsher

Yeah, please see lxc_cgroup_debug_outputs.txt file for all outputs and
lxc config.

** Attachment added: "lxc_cgroup_debug_outputs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1649582/+attachment/4792203/+files/lxc_cgroup_debug_outputs.txt

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

Title:
  lxc-start fails to start a unprivileged container  - cgroup
  permissions

Status in lxc package in Ubuntu:
  New

Bug description:
  I was following this simple getting start tutorial:

  https://linuxcontainers.org/lxc/getting-started/

  Created using:

  lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64

  But it always fails at:

  lxc-start -n ci -d

  I even tried another Ubuntu 14.04 but didn't work too for same
  problem.

  Below the debug log got from running `lxc-start`

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 13 14:05:44 2016
  InstallationDate: Installed on 2016-07-09 (156 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1649605] Re: webbrowser crashes are not reported

2016-12-15 Thread dinamic

2GB :o)

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

Title:
  webbrowser crashes are not reported

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 17.04 unity7

  webbrowser crashes are not reported, i keep seeing this message
  whenever the webbrowser crashes "your computer does not have enough
  free memory to automatically analyze the problem and send a report to
  the developers". i'm not sure how much free memory it needs but it's
  the only app that does that, for others the report works fine

  see attached screenshot

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

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

[Touch-packages] [Bug 1649605] Re: webbrowser crashes are not reported

2016-12-15 Thread dinamic

but i get crash reports for chrome, and chromes om nom noms the RAM

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

Title:
  webbrowser crashes are not reported

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 17.04 unity7

  webbrowser crashes are not reported, i keep seeing this message
  whenever the webbrowser crashes "your computer does not have enough
  free memory to automatically analyze the problem and send a report to
  the developers". i'm not sure how much free memory it needs but it's
  the only app that does that, for others the report works fine

  see attached screenshot

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

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

[Touch-packages] [Bug 1650389] Re: Installing snapd on 14.04.5 desktop downgrades xorg et al.

2016-12-15 Thread Michael Vogt

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

** Changed in: snappy
   Importance: Undecided => Critical

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

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

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

Title:
  Installing snapd on 14.04.5 desktop downgrades xorg et al.

Status in Snappy:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When trying to install the latest snapd on a 14.04.5 desktop image,
  the installation of systemd (as a dependency of snapd) triggers a
  whole bunch of downgrades as systemd-shim is removed and replaced with
  systemd.

  We have to adjust the packaging such that installation of systemd does
  not trigger such behavior for packages depending on systemd-shim in
  trusty.

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

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

[Touch-packages] [Bug 1650389] [NEW] Installing snapd on 14.04.5 desktop downgrades xorg et al.

2016-12-15 Thread Thomas Voß

Public bug reported:

When trying to install the latest snapd on a 14.04.5 desktop image, the
installation of systemd (as a dependency of snapd) triggers a whole
bunch of downgrades as systemd-shim is removed and replaced with
systemd.

We have to adjust the packaging such that installation of systemd does
not trigger such behavior for packages depending on systemd-shim in
trusty.

** Affects: snappy
 Importance: Critical
 Status: Confirmed

** Affects: systemd (Ubuntu)
 Importance: Critical
 Status: Confirmed


** Tags: 14.04

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

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

Title:
  Installing snapd on 14.04.5 desktop downgrades xorg et al.

Status in Snappy:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When trying to install the latest snapd on a 14.04.5 desktop image,
  the installation of systemd (as a dependency of snapd) triggers a
  whole bunch of downgrades as systemd-shim is removed and replaced with
  systemd.

  We have to adjust the packaging such that installation of systemd does
  not trigger such behavior for packages depending on systemd-shim in
  trusty.

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

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

[Touch-packages] [Bug 1649605] Re: webbrowser crashes are not reported

2016-12-15 Thread Olivier Tilloy

I’m occasionally seeing that when I run webbrowser-app in a VirtualBox VM. 
Never seen it on my work laptop, but that one has 16GB, which is plenty.
How much memory overall does your system have?

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Incomplete

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

Title:
  webbrowser crashes are not reported

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 17.04 unity7

  webbrowser crashes are not reported, i keep seeing this message
  whenever the webbrowser crashes "your computer does not have enough
  free memory to automatically analyze the problem and send a report to
  the developers". i'm not sure how much free memory it needs but it's
  the only app that does that, for others the report works fine

  see attached screenshot

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

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

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

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

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  
  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  
  Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash

# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd

# enable networkd and netplan
apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
version: 2
ethernets:
  eth0:
dhcp4: true
  EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

netplan generate

# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a 
After=systemd-network-wait-online.service' 
/lib/systemd/system/cloud-init.service

reboot

# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

# the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.

  
  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.

  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online.

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

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

Re: [Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

On Thu, Dec 15, 2016 at 10:27 PM, Brian Murray  wrote:

> How is this fixed in the development release?
>

For systemd portion, we carry the
systemd-networkd-resolvconf-update.service as a delta from Debian

Ryan

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  
  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  
  Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash

# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd

# enable networkd and netplan
apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
version: 2
ethernets:
  eth0:
dhcp4: true
  EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

netplan generate

# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a 
After=systemd-network-wait-online.service' 
/lib/systemd/system/cloud-init.service

reboot

# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

# the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.

  
  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.

  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online.

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

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

Re: [Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

On Thu, Dec 15, 2016 at 10:27 PM, Brian Murray  wrote:

> How is this fixed in the development release?
>

There is an upstream resolvconf bug that addresses that package portion:

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

> Also the having a "Regression Potential" of low just because not a lot
> of people use the service is wrong.  A bad change could still horribly
> impact the users of the software, regardless of how many users there
> are.
>

I don't disagree (that saying few folks impacted means low).

This portion was split out from the previous systemd SRU

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636912

in which the changes were classified in the same way, so I was coping over
the assessment done by pitti and Foundations with which I agree.

I'd be happy if someone else could comment on whether they disagree with
the assessment.

IMO the risk is low:

The changes involve running resolvconf.service earlier (which sets an
inotify watch) and
does not regress anyone AFAICT.

Asking that DNS services (systemd-networkd-resolvconf-update.service) to
run before
network-online.target vs.  (how it is today) running after
network-online.target is reach
 also has low regression potential since _nothing_ requiring networking
should
run before systemd reaches network-online.target anyhow.

These potential users would already be broken since the units don't
currently
ensure that resolvconf (when  using networkd instead of
networking.service/ifupdown)
runs to completion before reaching network-online.target.

>
> ** Changed in: resolvconf (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1649931
>
> Title:
>   systemd-networkd needs to ensure DNS is up before network-
>   online.target
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/resolvconf/+
> bug/1649931/+subscriptions
>

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash

# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd

# enable networkd and netplan
apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
version: 2
ethernets:
  eth0:
dhcp4: true
  EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

netplan generate

# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a 
After=systemd-network-wait-online.service' 
/lib/systemd/system/cloud-init.service

reboot

# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

# the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]:

[Touch-packages] [Bug 1649875] Re: OSK does not pop up in new window

2016-12-15 Thread Olivier Tilloy

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

** This bug has been marked a duplicate of bug 1648842
   [Regression] Switching between two windows of the same app using quick swipe 
from right edge breaks focus

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

Title:
  OSK does not pop up in new window

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Story: looks like new window and private window opens correctly but
  OSK doesn't pop up when tapping over address bar, I can make it work
  by swiping to the main webbrowser page where OSK works fine.

  Environment:

  current build number: 101
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-12-14 09:38:52
  version version: 101
  version ubuntu: 20161214
  version device: 20161014.0
  version custom: 20161214

  Steps:

  1º Open webbrowser-app
  2º On the right side menu button select "New window"
  3º Tap over the address field in the new window(notice OSK does not pop up)
  4º On right side menu select "New private mode"
  5º Tap over the address field in new private window (notice OSK does not pop 
up)
  6º Swipe to the main window and tab, check that OSK pops up

  Current result: when tapping over the address bar in a new window or
  private window, OSK does not appear

  Expected result: OSK should always appear when tapping on address bar
  or search fields like in the main page of webbrowser

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

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

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

How is this fixed in the development release?

Also the having a "Regression Potential" of low just because not a lot
of people use the service is wrong.  A bad change could still horribly
impact the users of the software, regardless of how many users there
are.

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

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  
  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  
  Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash

# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd

# enable networkd and netplan
apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
version: 2
ethernets:
  eth0:
dhcp4: true
  EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

netplan generate

# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a 
After=systemd-network-wait-online.service' 
/lib/systemd/system/cloud-init.service

reboot

# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

# the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.

  
  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.

  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online.

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

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

[Touch-packages] [Bug 622431] Re: iptables rules are not saved across reboots

2016-12-15 Thread Joshua Powers

** Changed in: server-papercuts
   Status: New => Won't Fix

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

Title:
  iptables rules are not saved across reboots

Status in Ubuntu Server papercuts:
  Won't Fix
Status in iptables package in Ubuntu:
  Won't Fix
Status in iptables package in Debian:
  Fix Released

Bug description:
  Running Ubuntu 10.04 server over linode.com, the "minimal" distro
  shipped by default does not save iptables rules by default across
  reboots. The ufw package is a convenience iptables wrapper, however,
  most experienced admins will not want to discard their iptables
  knowledge and flexibility for ufw.

  The wiki page: https://help.ubuntu.com/community/IptablesHowTo#Saving iptables
  mentions various scripts and hacks to achieve that, although it should be a 
distro's job to do something that common. I suggest shipping a system service 
that will save/restore services like centos/redhat, and that can be easily 
enabled/disabled as per the admin's needs

To manage notifications about this bug go to:
https://bugs.launchpad.net/server-papercuts/+bug/622431/+subscriptions

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

[Touch-packages] [Bug 1240336] Re: After release upgrade, the user looses permissions for several basic actions in the system

2016-12-15 Thread Владимир

I run into this problem after upgrade from Ubuntu 14.04 to Ubuntu 16.04
All suggested solutions didn't work well for me. But I found another very 
simple one.
I found the obsolete file in my home directory:
/home/current_user/.config/autostart/polkit-gnome-authentication-agent-1.desktop
After removing it everything runs well.

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

Title:
  After release upgrade, the user looses permissions for several basic
  actions in the system

Status in gdm package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged
Status in lxdm package in Ubuntu:
  Triaged
Status in policykit-desktop-privileges package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:
  - Upgrade Ubuntu to the next release.

  RESULT:
  - The user looses permissions for several basic actions in the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1650201] Re: Lightdm doesn't honour EXIF orientation tag on background images

2016-12-15 Thread Robert Ancell

Assuming you are using Unity Greeter, please shout out if not correct.

** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)

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

Title:
  Lightdm doesn't honour EXIF orientation tag on background images

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  The display manager (lightdm I assume) displays background images that
  have EXIF orientation tag with the original orientation of the image
  not of the EXIF orientation tag, which is completely incorrect.

  I'm running xenial and lightdm is version 1.18.3-0ubuntu1.

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

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

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

Hello Jeremy, or anyone else affected,

Accepted evolution-data-server into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/evolution-data-server/3.22.3-0ubuntu0.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 evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1639926

Title:
  Update evolution-data-server to 3.22.3

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Yakkety:
  Fix Committed

Bug description:
  Impact
  ==
  This is the second evolution SRU for yakkety. This update includes the new 
bugfix releases 3.22.2 and 3.22.3. Updating e-d-s is required to update 
evolution to 3.22.3 (LP: #1639942)

  https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22
  https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22

  Test Case
  =
  After installing the update, restart your computer. (Is there a flag 
evolution-data-server should set to prompt the user to do this?)

  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.

  Regression Potential
  
  Low. There are a fair amount of changes in this update, but they are all 
targeted towards fixing bugs. This is the same release that other GNOME 3.22 
distros ship. This may be the last official 3.22 release for the Evolution 
stack.

  Other Info
  ==
  Note that there is an issue with Google authentication affecting at least 
3.20 and 3.22.0. The underlying issue should be fixed with this update (it was 
partially fixed with 3.22.1 already in yakkety-updates). Unfortunately, anyone 
anywhere using older still-broken versions of e-d-s still break authentication 
for everyone else using the same API key!

  Because of this, GNOME is updating the key used by GNOME Online
  Accounts (LP: #1649995). The key used by e-d-s might need to be
  updated too. And maybe the key used by Ubuntu Online Accounts (LP:
  #1650007). This is because there are 2 or 3 different ways to use a
  Google account with Evolution. You only need to update the key for the
  Google authentication method you use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1639926/+subscriptions

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

[Touch-packages] [Bug 1639926] Re: Update evolution-data-server to 3.22.3

"After installing the update, restart your computer. (Is there a flag
evolution-data-server should set to prompt the user to do this?)"

There is documentation in update-notifier's HOOKS file about this:

Another example is the reboot notification. Packages like the kernel,
glibc, dbus and hal require a reboot. To simplify things
update-notifier installs a helper script in

/usr/share/update-notifier/notify-reboot-required

that can be called in the packages postinst script (make sure to check
for it first). It is i18n-able via langpacks and it will only be shown
once.

** Changed in: evolution-data-server (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 evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1639926

Title:
Update evolution-data-server to 3.22.3

Status in evolution-data-server package in Ubuntu:
Fix Released
Status in evolution-data-server source package in Yakkety:
Fix Committed

Bug description:
Impact
==
This is the second evolution SRU for yakkety. This update includes the new
bugfix releases 3.22.2 and 3.22.3. Updating e-d-s is required to update
evolution to 3.22.3 (LP: #1639942)

https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22
https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22

Test Case
=
After installing the update, restart your computer. (Is there a flag
evolution-data-server should set to prompt the user to do this?)

Run several eds-using apps like Evolution, GNOME Calendar and verify
that they continue to run at least as well as before this update.

Regression Potential

Low. There are a fair amount of changes in this update, but they are all
targeted towards fixing bugs. This is the same release that other GNOME 3.22
distros ship. This may be the last official 3.22 release for the Evolution
stack.

Other Info
==
Note that there is an issue with Google authentication affecting at least
3.20 and 3.22.0. The underlying issue should be fixed with this update (it was
partially fixed with 3.22.1 already in yakkety-updates). Unfortunately, anyone
anywhere using older still-broken versions of e-d-s still break authentication
for everyone else using the same API key!

Because of this, GNOME is updating the key used by GNOME Online
Accounts (LP: #1649995). The key used by e-d-s might need to be
updated too. And maybe the key used by Ubuntu Online Accounts (LP:
#1650007). This is because there are 2 or 3 different ways to use a
Google account with Evolution. You only need to update the key for the
Google authentication method you use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1639926/+subscriptions

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

[Touch-packages] [Bug 1650375] [NEW] Video fails

2016-12-15 Thread alain

Public bug reported:

Video failure during mp4 (.avi) reading. Recurrent concern.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
BootLog:
 [[0;32m  OK  [0m] Started LSB: Speech Dispatcher.
 [[0;32m  OK  [0m] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Dec 15 21:51:31 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] C61 [GeForce 6150SE nForce 430] 
[1025:0394]
InstallationDate: Installed on 2016-12-01 (14 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 001 Device 004: ID 059f:102a LaCie, Ltd Rikiki Hard Drive
 Bus 001 Device 002: ID 04a9:176d Canon, Inc. PIXMA MG2550
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser Printer
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: eMachines EL1358
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=b5bf3784-f5af-4627-8503-a82a628a8998 ro plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/20/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P01-B1
dmi.board.name: EL1358
dmi.board.vendor: eMachines
dmi.chassis.type: 3
dmi.chassis.vendor: eMachines
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/20/2011:svneMachines:pnEL1358:pvr:rvneMachines:rnEL1358:rvr:cvneMachines:ct3:cvr:
dmi.product.name: EL1358
dmi.sys.vendor: eMachines
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Dec 15 21:17:11 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImPS/2 Generic Wheel Mouse MOUSE, id 9
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: nouveau

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


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

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

Title:
  Video fails

Status in xorg package in Ubuntu:
  New

Bug description:
  Video failure during mp4 (.avi) reading. Recurrent concern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  BootLog:
   [[0;32m  OK  [0m] Started LSB: Speech Dispatcher.
   [[0;32m  OK  [0m] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Dec 15 21:51:31 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] C61 [GeForce 6150SE nForce 430] 
[1025:0394]
  InstallationDate: Installed on 2016-12-01 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64

[Touch-packages] [Bug 1561158] Re: Sierra Wireless EM7305 SIM state detected falsely

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

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

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

Title:
  Sierra Wireless EM7305 SIM state detected falsely

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  Im on Ubuntu 15.10 with kernel 4.2.0-34-generic on 64bit. My Laptop
  has a Sierra Wireless EM7305 WWAN modem built in, which used to work,
  when I first received the laptop (on Ubuntu 14.10).

  ModemManager 1.4.12-1ubuntu1
  NetworkManager 1.0.4-0ubuntu5.3

  The modem does not show up in NetworkManager anymore. ModemManager
  reports the SIM to be missing, but it isn't. I booted up a Windows VM
  and attached the USB device to confirm the modem correctly detects the
  SIM.

  mmcli -m 0 | grep -Ev equipment\|imei

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'70f86bd11e9d52c0a616806d8577df83343c0cd3')
    -
    Hardware |   manufacturer: 'Sierra'
     |  model: 'MBIM [1199:9063]'
     |   revision: 'SWI9X15C_05.05.47.00'
     |  supported: 'gsm-umts, lte'
     |current: 'gsm-umts, lte'
    -
    System   | device: '/sys/devices/pci:00/:00:14.0/usb1/1-4'
     |drivers: 'cdc_mbim'
     | plugin: 'Sierra'
     |   primary port: 'cdc-wdm0'
     |  ports: 'cdc-wdm0 (mbim), wwan0 (net)'
    -
    Numbers  |   own : 'unknown'
    -
    Status   |   lock: 'unknown'
     | unlock retries: 'unknown'
     |  state: 'failed'
     |  failed reason: 'sim-missing'
     |power state: 'low'
     |access tech: 'unknown'
     | signal quality: '0' (cached)
    -
    Modes|  supported: 'allowed: 2g, 3g, 4g; preferred: none'
     |current: 'allowed: any; preferred: none'
    -
    Bands|  supported: 'unknown'
     |current: 'unknown'
    -
    IP   |  supported: 'ipv4, ipv6, ipv4v6'
    -
    SIM  |   path: 'none'

    -
    Bearers  |  paths: 'none'

  Output of ModemManager --debug in attached mm.log

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

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

[Touch-packages] [Bug 1616548] Re: Cups causes LibreOffice unittests to loop in a sbuild

2016-12-15 Thread Paul Gevers

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

Title:
  Cups causes LibreOffice unittests to loop in a sbuild

Status in cups package in Ubuntu:
  Fix Released
Status in sbuild package in Ubuntu:
  Incomplete
Status in winff package in Ubuntu:
  Fix Released

Bug description:
  When building LibreOffice 1:5.2.0-0ubuntu1 on a xenial host with a
  yakkety sbuild, e.g. by:

  sbuild -A -d yakkety-amd64 (...).dsc

  this loops/busy hangs with unittests. This was working ok up to
  5.2.0~rc4 (=final), it is a regression by a LibreOffice dependency,
  most likely CUPS, which was updated.

  I tried to inject debug symbols by running with a: --chroot-setup-
  command and then run something along the lines of:

   apt install cups
   wget http://launchpadlibrarian.net/278966811/cups-dbgsym_2.2~rc1-4_amd64.ddeb
   wget 
http://launchpadlibrarian.net/278966816/libcups2-dbgsym_2.2~rc1-4_amd64.ddeb
   dpkg -i cups-dbgsym_2.2~rc1-4_amd64.ddeb
   dpkg -i libcups2-dbgsym_2.2~rc1-4_amd64.ddeb

  before starting the build proper, but I got only marginally better
  debug info. The hanging LibreOffice test processes usually have 2-4
  child processes. The parent and one of the childs are busy, while the
  rest idle.

  Here is a stacktrace of the busy child:

  Program received signal SIGPIPE, Broken pipe.
  0x2b0a80dd615f in fgetspent (stream=0x11) at fgetspent.c:43
  43in fgetspent.c
  (gdb) bt
  #0  0x2b0a80dd615f in fgetspent (stream=0x11) at fgetspent.c:43
  #1  0x001e in ?? ()
  #2  0x55c4976981e0 in ?? ()
  #3  0x2b0a8aff8d20 in ipp_options () from 
/usr/lib/x86_64-linux-gnu/libcups.so.2
  #4  0x4002 in ?? ()
  #5  0x2b0a8ada9feb in ppdCollect2 (ppd=0x2b0a8ada9bdf 
, section=29, min_order=0, choices=0x2b0a8adad6f3 
) at emit.c:145
  #6  0x in ?? ()

  Here is a stacktrace of the busy parent:

  Thread 3 "CUPSManager cup" received signal SIGPIPE, Broken pipe.
  0x2b0a80dd615f in fgetspent (stream=0x11) at fgetspent.c:43
  43in fgetspent.c
  (gdb) bt
  #0  0x2b0a80dd615f in fgetspent (stream=0x11) at fgetspent.c:43
  #1  0x001e in ?? ()
  #2  0x55c4976981e0 in ?? ()
  #3  0x2b0a8aff8d20 in ipp_options () from 
/usr/lib/x86_64-linux-gnu/libcups.so.2
  #4  0x4002 in ?? ()
  #5  0x2b0a8ada9feb in ppdCollect2 (ppd=0x2b0a8ada9bdf 
, section=29, min_order=0, choices=0x2b0a8adad6f3 
) at emit.c:145
  #6  0x in ?? ()

  
  When pressing "c" in gdb to continue, both processes stop very quickly again 
with the SIGPIPE.
  Venturing a guess: Is the signal handling of CUPS b0rked? As fgetspent reads 
the shadow file[1], maybe there are missing permissions or other sandbox issues 
that CUPS doesnt handle error cases for properly?

  [1] http://linux.die.net/man/3/fgetspent

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

I've done all the non-MAAS test cases on xenial so far except for
completing an installation with proposed enabled (it's a little more
complicated); things are working as expected. I removed the "Booting an
iSCSI remote root via IPv6 (no ip6=, d-i use case)" as it makes no sense
-- d-i will not set up iscsi for IPv6 at this point.

** Description changed:

  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
  
  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)
  
  Bugs related to uploads for this specific SRU:
  
  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU
  
  ifupdown:
  bug 1629972: networking.service takes down lo on stop
  
  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)
  
  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD
  
  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot
  
  [Impact]
  
  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in an
  ipv6-only environment is affected.
  
  [Stable Fix]
  
  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.
  
  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.
  
  [Test Case]
  
  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to, and
  see it fail to configure the network.
  
  [Regression Potential]
  
  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.
  
  [Tests for verification]
  
  Whoever checks the last one off, please mark verification done.
  
  MAAS test cases:
  [+] MAAS on IPv6-only network
  [+] MAAS on IPv4-only network
  [+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
  [+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)
  
  Non-MAAS test cases:
  X/Y
  [+]/[ ] ip="" and ip6 not present
- [ ]/[ ] ip=:eth0:dhcp and ip6 not present
+ [+]/[ ] ip=:eth0:dhcp and ip6 not present
  [ ]/[ ] d-i install with iSCSI remote root should complete normally
  [+]/[ ] Validate normal boot without remote root
  [+]/[ ] Booting an iSCSI remote root via IPv4 (using ip=)
  [+]/[ ] Booting an iSCSI remote root via IPv6 (using ip6=)
  [+]/[ ] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
- [ ]/[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)
- [ ]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)
+ [+]/[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)
+ [+]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source package in Yakkety:
  Won't Fix
Status in

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

** Description changed:

  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
  
  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)
  
  Bugs related to uploads for this specific SRU:
  
  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU
  
  ifupdown:
  bug 1629972: networking.service takes down lo on stop
  
  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)
  
  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD
  
  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot
  
  [Impact]
  
  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in an
  ipv6-only environment is affected.
  
  [Stable Fix]
  
  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.
  
  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.
  
  [Test Case]
  
  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to, and
  see it fail to configure the network.
  
  [Regression Potential]
  
  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.
  
  [Tests for verification]
  
  Whoever checks the last one off, please mark verification done.
  
  MAAS test cases:
  [+] MAAS on IPv6-only network
  [+] MAAS on IPv4-only network
  [+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
  [+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)
  
  Non-MAAS test cases:
- [ ] ip="" and ip6 not present
- [ ] ip=:eth0:dhcp and ip6 not present
- [ ] d-i install with iSCSI remote root should complete normally
- [+] Validate normal boot without remote root
- [ ] Booting an iSCSI remote root via IPv4 (using ip=)
- [ ] Booting an iSCSI remote root via IPv6 (using ip6=)
- [ ] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
- [ ] Booting an iSCSI remote root via IPv6 (no ip6=, d-i use case)
- [ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting 
device)
- [ ] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)
+ X/Y
+ [+]/[ ] ip="" and ip6 not present
+ [ ]/[ ] ip=:eth0:dhcp and ip6 not present
+ [ ]/[ ] d-i install with iSCSI remote root should complete normally
+ [+]/[ ] Validate normal boot without remote root
+ [+]/[ ] Booting an iSCSI remote root via IPv4 (using ip=)
+ [+]/[ ] Booting an iSCSI remote root via IPv6 (using ip6=)
+ [+]/[ ] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
+ [ ]/[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)
+ [ ]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

I've accepted a new version of open-iscsi in yakkety, but the SRU tools
barfed on modifying the bug.

** Changed in: open-iscsi (Ubuntu Yakkety)
   Status: Fix Released => Fix Committed

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)

  Bugs related to uploads for this specific SRU:

  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU

  ifupdown:
  bug 1629972: networking.service takes down lo on stop

  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)

  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD

  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  [Stable Fix]

  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.

  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

  [Tests for verification]

  Whoever checks the last one off, please mark verification done.

  MAAS test cases:
  [+] MAAS on IPv6-only network
  [+] MAAS on IPv4-only network
  [+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
  [+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)

  Non-MAAS test cases:
  X/Y
  [+]/[ ] ip="" and ip6 not present
  [+]/[ ] ip=:eth0:dhcp and ip6 not present
  [ ]/[ ] d-i install with iSCSI remote root should complete normally
  [+]/[ ] Validate normal boot without remote root
  [+]/[ ] Booting an iSCSI remote root via IPv4 (using ip=)
  [+]/[ ] Booting an iSCSI remote root via IPv6 (using ip6=)
  [+]/[ ] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
  [+]/[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)
  [+]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)

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

-- 
Mailing list: https://launchpad.net/~touch-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.4 - multiple important fixes, stable branch

The Test Case is rather incomplete for an SRU.  Could you add some
information about how the changes will be tested and we will ensure
there are no regressions?

Thanks!

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

-- 
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.4 - multiple important fixes, stable branch

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Yakkety:
  Incomplete

Bug description:
  [Impact]
  Mesa 12.0.4 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]
  There's only a modest number of changes to the drivers, the performance boost 
for Radeon is result of one fix for the shaders.

  [Regression potential]
  The release consists of cherry-picks from master, specifically selected as 
bugfixes. Regression potential 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 1649964] Re: POWER9 128-bit iEEE float point support in GDB

** Changed in: gdb (Ubuntu)
Milestone: ubuntu-17.02 => None

** Changed in: gdb (Ubuntu)
 Assignee: Matthias Klose (doko) => Taco Screen team (taco-screen-team)

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

Title:
  POWER9 128-bit iEEE float point support in GDB

Status in gdb package in Ubuntu:
  Triaged

Bug description:
  It is missing the 128-bit IEEE floating-point types support in GDB

  These are the commit ids from the patchset already included on
  upstream GDB, they should be available on next gdb release:

  5f3bceb68dd211be977eb61d5f1ea68e7de51b7aFix typo in ada_language_arch_info
  ae438bc5c06b770c00f37e4ed244707ce3ab9ff4Fix TYPE_SPECIFIC_FIELD for types 
created via arch_type
  88dfca6c43c11dea69db24cfb87e6821e63e29b2Add some missing arch_..._type 
helpers
  19f392bc2a93d9e64d063b884cd6eca547c8dad0Unify init_type and arch_type 
interface and helpers
  a9ff5f12cff6cd06f74ecf387ac5468984c94c6fRemove obsolete TYPE_FLAG_... 
values
  c413c44801e449f1f0b9828b81770e752b8219afRemove TYPE_NOSIGN "char" hack
  49f190bcb7f074ea2e27d4e967e4fae9ed7dafb6Add missing format for built-in 
floating-point types
  9b790ce7227fa346d08a41462119e9a3e93f5e80Add gdbarch callback to provide 
formats for debug info float types
  00d5215ecec4fa0a78dcc37fec9425593753eb66Support 128-bit IEEE 
floating-point types on Intel and Power

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

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

[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2016-12-15 Thread Nicholaus Shupe

Completely broke my 16.04 to 16.10 upgrade. Really bad. Thankfully I
backed the VM up.

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome. 
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

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

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

** Patch added: "xenial-dns-before-online-target-lp1649931.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+attachment/4792126/+files/xenial-dns-before-online-target-lp1649931.debdiff

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  
  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  
  Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash

# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd

# enable networkd and netplan
apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
version: 2
ethernets:
  eth0:
dhcp4: true
  EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

netplan generate

# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a 
After=systemd-network-wait-online.service' 
/lib/systemd/system/cloud-init.service

reboot

# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

# the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.

  
  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.

  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online.

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

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

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

** Description changed:

  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.
  
  This was discussed in https://launchpad.net/bugs/1636912 however it was
  not a regression since there aren't any users of networkd + DNS early in
  boot at this time, it was requested that we move this DNS issue to a
  separate bug.
+ 
+ 
+ [SRU]
+ Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.
+ 
+ Regression potential: Low. networkd is not widely being used outside of
+ netplan/snappy in xenial.
+ 
+ 
+ Test Case:
+   lxc launch ubuntu-daily:xenial x1
+   lxc exec x1 /bin/bash
+ 
+   # make sure you're on systemd-229-4ubuntu13
+   apt update && apt install -y systemd
+ 
+   # enable networkd and netplan
+   apt install -y nplan
+ cat < /etc/netplan/nplan.yaml
+ network:
+   version: 2
+   ethernets:
+ eth0:
+   dhcp4: true
+ EOF
+   sed -i.orig -e 's/^source/# source/' /etc/network/interfaces
+   
+   netplan generate
+   
+   # make sure cloud-init.service uses networkd
+   sed -i.orig -e '/After=networking.service/a 
After=systemd-network-wait-online.service' 
/lib/systemd/system/cloud-init.service
+ 
+   reboot
+ 
+   # check that the order of execution with:
+   journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service
+ 
+   # the order should be:
+ 1. resolvconf:  systemd[1]: Started Nameserver information manager.
+ 2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
+ 3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
+ 4. network-online.target: systemd[1]: Reached target Network is Online.
+ 
+ === BAD OUTPUT ===
+ On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:
+ 
+ Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
+ Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
+ Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
+ Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
+ Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
+ Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
+ Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
+ Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
+ Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
+ 
+ 
+ === GOOD OUTPUT ===
+ On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.
+ 
+ Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
+ Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
+ Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
+ Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
+ Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
+ Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
+ Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online.

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  
  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  
  Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash

# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd

# enable networkd and netplan
apt install -y nplan
  cat

[Touch-packages] [Bug 1645308] Re: [SRU] Backport zeromq3 4.2.0 to yakkety

This is blocked by the fact that 4.2.0 is stuck in zesty-proposed.

** Changed in: zeromq3 (Ubuntu Yakkety)
   Status: In Progress => Incomplete

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

Title:
  [SRU] Backport zeromq3 4.2.0 to yakkety

Status in zeromq3 package in Ubuntu:
  Fix Released
Status in zeromq3 source package in Yakkety:
  Incomplete

Bug description:
  [Impact]

  As per product requirement, we have released a git-snapshot based pre-
  release version of zeromq3 4.2.0 to yakkety
  (4.1.5+git20160811+2fc86bc) as the upstream version was not yet
  available. The agreement was that we will release the snapshot-based
  version only if, once the official update is available we will update
  and switch.

  The rationale for this would be that the snapshot-based version is
  anyway more-or-less feature compatible with the official version. It's
  also not wise to keep shipping a snapshot for long as some bugfixes
  might be missing from the cherry-pick. The generated binaries are
  binary-compatible, with only a few new symbols exported in the main
  4.2.0 version.

  [Test Case]

  No particular test-case - installing the new version and making sure
  that existing reverse-dependencies still work as intended.

  [Regression Potential]

  There is, of course, some regression potential, but as already
  mentioned: there weren't too many commits since the git snapshot that
  our previous version was based off.

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

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

[Touch-packages] [Bug 1650354] Re: system error on login after a power button reboot becuase of disabled reboot/shutown options in the power menu

2016-12-15 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  system error on login after a power button reboot becuase of disabled
  reboot/shutown options in the power menu

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  i started the update my Lubuntu version to the latest version i waited
  for the update to finish while i was doing a few other things.. i  had
  to get done to not disturb the computer... after the auto-restart .. i
  went to the power menu to shut down .. both that and the reboot option
  were giving me errors and it wasn't letting me perform either
  operation.. i had to manually shut the computer down from the power
  button.. i turned it on from there and it gave a me "system error soon
  after i logged in...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic i686
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  Date: Thu Dec 15 13:24:49 2016
  DuplicateSignature:
   package:unattended-upgrades:0.90ubuntu0.2
   Installing new version of config file /etc/logrotate.d/unattended-upgrades 
...
   dpkg: error processing package unattended-upgrades (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-07-25 (143 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-12-15 (0 days ago)
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2016-12-15T13:27:11.616348

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

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

[Touch-packages] [Bug 1650354] [NEW] system error on login after a power button reboot becuase of disabled reboot/shutown options in the power menu

2016-12-15 Thread Christopher

Public bug reported:

i started the update my Lubuntu version to the latest version i waited
for the update to finish while i was doing a few other things.. i  had
to get done to not disturb the computer... after the auto-restart .. i
went to the power menu to shut down .. both that and the reboot option
were giving me errors and it wasn't letting me perform either
operation.. i had to manually shut the computer down from the power
button.. i turned it on from there and it gave a me "system error soon
after i logged in...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90ubuntu0.2
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic i686
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: i386
Date: Thu Dec 15 13:24:49 2016
DuplicateSignature:
 package:unattended-upgrades:0.90ubuntu0.2
 Installing new version of config file /etc/logrotate.d/unattended-upgrades ...
 dpkg: error processing package unattended-upgrades (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-07-25 (143 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 0.90ubuntu0.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-12-15 (0 days ago)
mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2016-12-15T13:27:11.616348

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  system error on login after a power button reboot becuase of disabled
  reboot/shutown options in the power menu

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  i started the update my Lubuntu version to the latest version i waited
  for the update to finish while i was doing a few other things.. i  had
  to get done to not disturb the computer... after the auto-restart .. i
  went to the power menu to shut down .. both that and the reboot option
  were giving me errors and it wasn't letting me perform either
  operation.. i had to manually shut the computer down from the power
  button.. i turned it on from there and it gave a me "system error soon
  after i logged in...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic i686
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  Date: Thu Dec 15 13:24:49 2016
  DuplicateSignature:
   package:unattended-upgrades:0.90ubuntu0.2
   Installing new version of config file /etc/logrotate.d/unattended-upgrades 
...
   dpkg: error processing package unattended-upgrades (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-07-25 (143 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-12-15 (0 days ago)
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2016-12-15T13:27:11.616348

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

-- 
Mailing list: https://launchpad.net/~touch-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)

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-0ubuntu1 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: lxc (Ubuntu Trusty)
   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 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

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

Hello Stéphane, or anyone else affected,

Accepted lxc into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/2.0.6-0ubuntu1~ubuntu16.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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1647010

Title:
  SRU of LXC 2.0.6 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  In Progress
Status in lxc source package in Xenial:
  Fix Committed
Status in lxc source package in Yakkety:
  Fix Committed

Bug description:
  LXC upstream released LXC 2.0.5 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,

[Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

2016-12-15 Thread Bug Watch Updater

** Changed in: resolvconf (Debian)
   Status: New => Fix Committed

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  Fix Released
Status in cloud-init package in Ubuntu:
  Triaged
Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in resolvconf source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  New
Status in resolvconf source package in Yakkety:
  In Progress
Status in systemd source package in Yakkety:
  Fix Released
Status in resolvconf package in Debian:
  Fix Committed

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms

  cloud-init would need networkd to run at or before
  'networking.service' so it can raise networking to then find and use
  network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links

  # grep cloud-init /usr/share/snappy/dpkg.list
  ii  cloud-init
0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all  Init 
scripts for cloud instances

  SRU INFORMATION FOR systemd
  ===
  Fix: For xenial it is sufficient to drop systemd-networkd's 
After=dbus.service (https://github.com/systemd/systemd/commit/5f004d1e32) and

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

Hello Stéphane, or anyone else affected,

Accepted lxc into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/2.0.6-0ubuntu1~ubuntu16.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: lxc (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

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

Title:
  SRU of LXC 2.0.6 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  In Progress
Status in lxc source package in Xenial:
  Fix Committed
Status in lxc source package in Yakkety:
  Fix Committed

Bug description:
  LXC upstream released LXC 2.0.5 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

[Touch-packages] [Bug 1647105] Re: Merge vim 2:8.0.0095-1 from Debian testing/unstable

This bug was fixed in the package vim - 2:8.0.0095-1ubuntu2

---
vim (2:8.0.0095-1ubuntu2) zesty; urgency=medium

  * ubuntu-series-support.patch: Drop vivid and wily from supported
list.

 -- Adam Conrad   Tue, 06 Dec 2016 03:03:48 -0700

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

Title:
  Merge vim 2:8.0.0095-1 from Debian testing/unstable

Status in vim package in Ubuntu:
  Fix Released

Bug description:
  Since Debian has now migrated vim from Python 2 to Python 3, this
  drops the Python 2 variants.

  Test build: https://launchpad.net/~andersk/+archive/ubuntu/ppa

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

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

Re: [Touch-packages] [Bug 1649582] Re: lxc-start fails to start a unprivileged container - cgroup permissions

2016-12-15 Thread Christian Brauner

Please attach the container config file and show or attache the output
of the following commands:

- grep cgroup /proc/1/mountinfo
- cat /proc/self/cgroup
- ls -al /sys/fs/cgroup
- lxcfs --version

Thanks!

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

Title:
  lxc-start fails to start a unprivileged container  - cgroup
  permissions

Status in lxc package in Ubuntu:
  New

Bug description:
  I was following this simple getting start tutorial:

  https://linuxcontainers.org/lxc/getting-started/

  Created using:

  lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64

  But it always fails at:

  lxc-start -n ci -d

  I even tried another Ubuntu 14.04 but didn't work too for same
  problem.

  Below the debug log got from running `lxc-start`

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 13 14:05:44 2016
  InstallationDate: Installed on 2016-07-09 (156 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar

2016-12-15 Thread Santosh

The real cause here is we rely on focusOut(In)Event to check for
activeFocus item. but the any check of ActiveFocus (hasActiveFocus or
window->activeFocusItem) inside focusout/in event give incorrect result.

when another item is focused(location bar), window->activeFocusItem()
return null not the new activeFocus Item.

While check for activeFocus item is consistent Once we get ItemChanged event.
http://doc.qt.io/qt-5/qquickitem.html#itemChange

So When quickItem activeFocus changes we get ItemChange event and after
any check window->activeFocusItem() correctly return the newly focus
QuickItem.

In short, we should do webview focus update based on ItemChange event.

see previous comments also for more on activeFocus behaviour inside
focusout/in event.

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

Title:
  Webview appears to think it's in focus when typing in the addressbar

Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

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

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

[Touch-packages] [Bug 1606600] Re: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported

2016-12-15 Thread Musbach

Hello,
I am fighting exactly with the same problem. Is there any workaround?
Thanks
BR

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

Title:
  dpkg-reconfigure unattended-upgrades results in update-rc.d warning
  that start and stop actions are no longer supported

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to script a change to the automatic updating of servers,
  and tried the following:

  echo "debconf unattended-upgrades/enable_auto_updates boolean false" | 
debconf-set-selections -
  dpkg-reconfigure -fnoninteractive unattended-upgrades

  The result, however, is a warning message:

  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

  At this point, the change I tried to make seems to be lost. To show
  this in an expanded sequence:

  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: true
  root@brennan:/home/ubuntu# echo "debconf 
unattended-upgrades/enable_auto_updates boolean false" | debconf-set-selections 
-
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: false
  root@brennan:/home/ubuntu# dpkg-reconfigure -fnoninteractive 
unattended-upgrades
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/enable_auto_updates: true
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";

  If I omit the "-fnoninteractive" option to dpkg-reconfigure, I still
  get the warning message, but the change IS accepted and takes effect.
  Of course, this isn't useful in a script that should be run non-
  interactively. I've tried the equivalent commands to reconfigure other
  packages, and they work without error message, so I believe the
  problem is with unattended-upgrades, not with debconf/dpkg-
  reconfigure.

  This problem affects Ubuntu 16.04.1 (and probably 16.04 GA, but I've
  not tested it). It works as expected with Ubuntu 14.04. (That version,
  of course, defeaults to "false" for the unattended-
  upgrades/enable_auto_updates value. I've tested both with the default
  "false" value and after changing it to "true," with successful runs
  both times.)

  Version information, as requested:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90
Version table:
   *** 0.90 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy debconf
  debconf:
Installed: 1.5.58ubuntu1
Candidate: 1.5.58ubuntu1
Version table:
   *** 1.5.58ubuntu1 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1649582] Re: lxc-start fails to start a unprivileged container - cgroup permissions

2016-12-15 Thread Sneetsher

Yes.

$ apt-cache policy libpam-cgfs
libpam-cgfs:
  Installed: 2.0.4-0ubuntu1~ubuntu16.04.1
  Candidate: 2.0.4-0ubuntu1~ubuntu16.04.1
  Version table:
 *** 2.0.4-0ubuntu1~ubuntu16.04.1 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 2.0.0-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

I also reinstall it, just in case, but still fails to start

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

Title:
  lxc-start fails to start a unprivileged container  - cgroup
  permissions

Status in lxc package in Ubuntu:
  New

Bug description:
  I was following this simple getting start tutorial:

  https://linuxcontainers.org/lxc/getting-started/

  Created using:

  lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64

  But it always fails at:

  lxc-start -n ci -d

  I even tried another Ubuntu 14.04 but didn't work too for same
  problem.

  Below the debug log got from running `lxc-start`

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 13 14:05:44 2016
  InstallationDate: Installed on 2016-07-09 (156 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

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

2016-12-15 Thread Eric Desrochers

@caribou
@rbasak

Let me share the work (since rbasak seems to like the approach) I've
done so far on my above recent proposal :

isc-dhcp-client: dhclient with DDNS functionality enabled
isc-dhcp-client-noddns : dhclient with DDNS functionality disabled

This is a working debdiff, I think the only things that need to be
covered is the release upgrade portion.

Let me know what you think so far.

** Patch added: "debdiff_noddns_proposal_still_in_progress"
   
https://bugs.launchpad.net/ubuntu/trusty/+source/isc-dhcp/+bug/1176046/+attachment/4792032/+files/noddns_binary_pkg.debdiff

-- 
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 these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient
  udp0  0 0.0.0.0:68

[Touch-packages] [Bug 1650022] Re: We need a "close" action for killing an app in a trust prompt

2016-12-15 Thread Michał Sawicz

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

Title:
  We need a "close" action for killing an app in a trust prompt

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  The original designs for trust prompts included a close action in the
  header to close apps that were opened in a trust session.  This is
  particularly important when apps might not behave well or hang, there
  is no way out.  The close action is like a back button to take you
  back out of the app.

  We're close to landing trust session support in content-hub, where
  we'll open source apps for content picking in a trust prompt.  We've
  found apps that have a tendency to hang, leaving the user no way out
  besides killing both the source and destination apps.  Clearly those
  apps need some fixing, but we need to give the user an easy way out.

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

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

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

2016-12-15 Thread Ubuntu Foundations Team Bug Bot

The attachment "xenial_resolvconf-lp1649931.diff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

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

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

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

** Patch added: "xenial_resolvconf-lp1649931.diff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1649931/+attachment/4792030/+files/xenial_resolvconf-lp1649931.diff

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

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

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

[Touch-packages] [Bug 1649995] Re: Replace Google API key used by GNOME services

2016-12-15 Thread Jeremy Bicha

** Description changed:

  Impact
  ==
  Some bugs in evolution-data-server (e-d-s) were causing daily limit errors 
for those using Google services with evolution-data-server and apps that use it 
(Evolution is a prominent example). Unfortunately, it looks like users using 
older versions of e-d-s are causing those errors to affect everyone using e-d-s 
since they are using the same API key. It's very difficult for GNOME to push 
everyone to use an updated version of their software.
  
  Therefore, this update changes the API key used by those using the GNOME
  Online Accounts feature for Google services.
  
  Test Case
  =
  Restart your computer after applying the updates.
  
  Then use Evolution with a Google account configured by gnome-control-
  center's Online Accounts. The easiest way to configure that correctly is
  to use Ubuntu GNOME.
  
  Make sure that Evolution works without getting authentication errors
  with your Google services.
  
  Regression Potential
  
  I think the only possibility for regression is if GNOME did not configure the 
key correctly with Google's developer platform.
  
  Other Info
  ==
  This update depends on the pending evolution-data-server 3.22.3 SRU (LP: 
#1639926) since we need to make sure the user has a fixed version of 
evolution-data-server so we don't taint the new keys too!
  
- Also, Evolution has two ways to use Google services: 1) GNOME Online
- Accounts 2) evolution-data-server has its own Google authentication
- method. The evolution-data-server key probably will similarly need to be
- updated.
+ Also, I believe Evolution has three ways to use Google services: 1)
+ GNOME Online Accounts 2) evolution-data-server (e-d-s) has its own
+ Google authentication method 3) Ubuntu Online Accounts.
+ 
+ The errors are much less common for the e-d-s API key so upstream does
+ not intend to change that key. The e-d-s key is new, only existing in
+ Ubuntu 16.10 and above. (It's not even used in the Ubuntu 16.04 GNOME3
+ Staging PPA since --disable-google-auth is used there to not add a new
+ universe dependency.)
+ 
+ See LP: #1650007 for whether this affects the Ubuntu Online Accounts
+ key.

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

Title:
  Replace Google API key used by GNOME services

Status in gnome-online-accounts:
  Fix Released
Status in gnome-online-accounts package in Ubuntu:
  New
Status in gnome-online-accounts source package in Yakkety:
  New

Bug description:
  Impact
  ==
  Some bugs in evolution-data-server (e-d-s) were causing daily limit errors 
for those using Google services with evolution-data-server and apps that use it 
(Evolution is a prominent example). Unfortunately, it looks like users using 
older versions of e-d-s are causing those errors to affect everyone using e-d-s 
since they are using the same API key. It's very difficult for GNOME to push 
everyone to use an updated version of their software.

  Therefore, this update changes the API key used by those using the
  GNOME Online Accounts feature for Google services.

  Test Case
  =
  Restart your computer after applying the updates.

  Then use Evolution with a Google account configured by gnome-control-
  center's Online Accounts. The easiest way to configure that correctly
  is to use Ubuntu GNOME.

  Make sure that Evolution works without getting authentication errors
  with your Google services.

  Regression Potential
  
  I think the only possibility for regression is if GNOME did not configure the 
key correctly with Google's developer platform.

  Other Info
  ==
  This update depends on the pending evolution-data-server 3.22.3 SRU (LP: 
#1639926) since we need to make sure the user has a fixed version of 
evolution-data-server so we don't taint the new keys too!

  Also, I believe Evolution has three ways to use Google services: 1)
  GNOME Online Accounts 2) evolution-data-server (e-d-s) has its own
  Google authentication method 3) Ubuntu Online Accounts.

  The errors are much less common for the e-d-s API key so upstream does
  not intend to change that key. The e-d-s key is new, only existing in
  Ubuntu 16.10 and above. (It's not even used in the Ubuntu 16.04 GNOME3
  Staging PPA since --disable-google-auth is used there to not add a new
  universe dependency.)

  See LP: #1650007 for whether this affects the Ubuntu Online Accounts
  key.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1649995/+subscriptions

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

[Touch-packages] [Bug 1248072] Re: VMware virtual connector recognized by Mir as "Unknown"

This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1

---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium

  * New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 42
  . mircommon ABI bumped to 7
  . mirplatform ABI bumped to 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI bumped to 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI bumped to 6
  . mircore ABI added, at version 1
- Enhancements:
  . Added pointer confinement support
  . Identify Raspberry Pi output types correctly
  . Added dead key and compose key support
  . Added gamma support for KMS hardware
  . Added yakkety and zesty gcc-6 support
  . Added surface passthrough support for fullscreen clients of nested
servers
  . Introduced a new library `libmircore'
  . Began migrating from Protobuf to Cap'n Proto starting with events
  . Began support for VirtualBox (servers now start instead of crashing
but full support for GL clients is still missing)
  . Began support for high precision frame timing, implemented for the
KMS, Android and X11 backends so far
  . Added --display-report support for the X11 backend
  . Improved reliability of `mirvanity' latency test tool
  . Moved to using the CSS cursor naming scheme internally, although
the old symbolic indentifiers remain unchanged and still work
  . Added refresh rate to MirSurfaceOutputEvent
  . Many improvements to automated test quality and coverage
  . Smoother desktop zoom using mir_proving_server (Super + two fingers)
- Bugs fixed:
  . FTBFS On Zesty: invalid use of
'struct native_handle' (LP: #1638774)
  . libmirclient-debug-extension-dev install debug/surface.h
twice (LP: #1639153)
  . Mir crashes on virtual box drmModeCrtcSetGamma
Function not implemented (LP: #1638220)
  . Flickering in mir_demo_client_multistream (LP: #1635273)
  . Camera apps (camera & vanity) never exit (LP: #1635010)
  . Clients cannot connect when MIR_SOCKET="" (LP: #1634508)
  . mirtest-dev packaging fails to sepcify boost depends (LP: #1633537)
  . cursor.h is unclear about mir_diagonal_resize_* (LP: #1626924)
  . Inconsistent underscores in cursor names (LP: #1632617)
  . [regression] Accidental libmircommon.so.6 break (LP: #1617865)
  . [regression] mir demo server fails to start with mx4 (LP: #1615703)
  . [regression] Trust prompt now shown when starting camera (LP: #1612256)
  . [regression] make abi-check fails to build (LP: #1626866)
  . Nested servers prevent overlays or fullscreen bypass (LP: #1262116)
  . Failed to get PRIME fd from gbm bo (LP: #1607812)
  . Mir-on-X is difficult to use on 1366x768 laptop (LP: #1590959)
  . Remove useless message 'Surface 0 DPI' in demos (LP: #1559831)
  . Mir fails to cross-build with newer sbuild (LP: #1628507)
  . Infinite loop in AbstractShell::focus_next_session (LP: #1625401)
  . Destroying a presentation chain doesn't trigger ownership
notification to client (LP: #1626503)
  . Keyboard layout not applied on the shell (LP: #1626435)
  . Warning, No syntax specified for the proto file (LP: #1624971)
  . display-report=log reports vsync on non-existent output number
(LP: #1621352)
  . libmirserver-dev missing uuid-dev depends (LP: #1617435)
  . debian/control missing epoxy (LP: #1617256)
  . Downstreams need to disable clang diagnostic "-Wreturn-type-clinkage"
to build against public headers (LP: #1615587)
  . mirtest-dev: mock_display_configuration.h uses mg namespace without
using it (LP: #1614983)
  . FTBFS using clang (LP: #1609612)
  . mesa-kms doesn't fall back to using software cursor if hardware
cursor is unavailable (LP: #1610054)
  . StubGraphicsPlatform::create_display() leaves a dubious state
(LP: #1611337)
  . Mir build/tests fail with gcc-6 and LTO (LP: #1610215)
  . Cross compiling on xenial fails (LP: #1609329)
  . Building with -DMIR_PLATFORM=anroid fails (LP: #1609916)
  . unity-system-compositor crashes on start-up with "Mir fatal error:
Failed to schedule page flip" (LP: #1584894)
  . mir_connection_create_spec_for_tooltip doesn't meet requirements
(LP: #1603922)
  . Updating surface size/location needs to update the pointer confinement
(LP: #1604673)
  . ServerConfigurationOption is not ptest safe (LP: #1607351)
  . HWC's vsync_signal_on is never called when using HWC 1.0 (LP: #1613373)
  . mir_connection_create_spec_for_tooltip does not set aux_rect
(LP: #1632335)
  . VMware virtual connector recognized by Mir as "unknown" (LP: #1248072)
  . Fix code to match the

[Touch-packages] [Bug 1559831] Re: Some mir_demo_client(s) report useless message 'Surface 0 DPI'

This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1

---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium

  * New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 42
  . mircommon ABI bumped to 7
  . mirplatform ABI bumped to 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI bumped to 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI bumped to 6
  . mircore ABI added, at version 1
- Enhancements:
  . Added pointer confinement support
  . Identify Raspberry Pi output types correctly
  . Added dead key and compose key support
  . Added gamma support for KMS hardware
  . Added yakkety and zesty gcc-6 support
  . Added surface passthrough support for fullscreen clients of nested
servers
  . Introduced a new library `libmircore'
  . Began migrating from Protobuf to Cap'n Proto starting with events
  . Began support for VirtualBox (servers now start instead of crashing
but full support for GL clients is still missing)
  . Began support for high precision frame timing, implemented for the
KMS, Android and X11 backends so far
  . Added --display-report support for the X11 backend
  . Improved reliability of `mirvanity' latency test tool
  . Moved to using the CSS cursor naming scheme internally, although
the old symbolic indentifiers remain unchanged and still work
  . Added refresh rate to MirSurfaceOutputEvent
  . Many improvements to automated test quality and coverage
  . Smoother desktop zoom using mir_proving_server (Super + two fingers)
- Bugs fixed:
  . FTBFS On Zesty: invalid use of
'struct native_handle' (LP: #1638774)
  . libmirclient-debug-extension-dev install debug/surface.h
twice (LP: #1639153)
  . Mir crashes on virtual box drmModeCrtcSetGamma
Function not implemented (LP: #1638220)
  . Flickering in mir_demo_client_multistream (LP: #1635273)
  . Camera apps (camera & vanity) never exit (LP: #1635010)
  . Clients cannot connect when MIR_SOCKET="" (LP: #1634508)
  . mirtest-dev packaging fails to sepcify boost depends (LP: #1633537)
  . cursor.h is unclear about mir_diagonal_resize_* (LP: #1626924)
  . Inconsistent underscores in cursor names (LP: #1632617)
  . [regression] Accidental libmircommon.so.6 break (LP: #1617865)
  . [regression] mir demo server fails to start with mx4 (LP: #1615703)
  . [regression] Trust prompt now shown when starting camera (LP: #1612256)
  . [regression] make abi-check fails to build (LP: #1626866)
  . Nested servers prevent overlays or fullscreen bypass (LP: #1262116)
  . Failed to get PRIME fd from gbm bo (LP: #1607812)
  . Mir-on-X is difficult to use on 1366x768 laptop (LP: #1590959)
  . Remove useless message 'Surface 0 DPI' in demos (LP: #1559831)
  . Mir fails to cross-build with newer sbuild (LP: #1628507)
  . Infinite loop in AbstractShell::focus_next_session (LP: #1625401)
  . Destroying a presentation chain doesn't trigger ownership
notification to client (LP: #1626503)
  . Keyboard layout not applied on the shell (LP: #1626435)
  . Warning, No syntax specified for the proto file (LP: #1624971)
  . display-report=log reports vsync on non-existent output number
(LP: #1621352)
  . libmirserver-dev missing uuid-dev depends (LP: #1617435)
  . debian/control missing epoxy (LP: #1617256)
  . Downstreams need to disable clang diagnostic "-Wreturn-type-clinkage"
to build against public headers (LP: #1615587)
  . mirtest-dev: mock_display_configuration.h uses mg namespace without
using it (LP: #1614983)
  . FTBFS using clang (LP: #1609612)
  . mesa-kms doesn't fall back to using software cursor if hardware
cursor is unavailable (LP: #1610054)
  . StubGraphicsPlatform::create_display() leaves a dubious state
(LP: #1611337)
  . Mir build/tests fail with gcc-6 and LTO (LP: #1610215)
  . Cross compiling on xenial fails (LP: #1609329)
  . Building with -DMIR_PLATFORM=anroid fails (LP: #1609916)
  . unity-system-compositor crashes on start-up with "Mir fatal error:
Failed to schedule page flip" (LP: #1584894)
  . mir_connection_create_spec_for_tooltip doesn't meet requirements
(LP: #1603922)
  . Updating surface size/location needs to update the pointer confinement
(LP: #1604673)
  . ServerConfigurationOption is not ptest safe (LP: #1607351)
  . HWC's vsync_signal_on is never called when using HWC 1.0 (LP: #1613373)
  . mir_connection_create_spec_for_tooltip does not set aux_rect
(LP: #1632335)
  . VMware virtual connector recognized by Mir as "unknown" (LP: #1248072)
  . Fix code to match the

[Touch-packages] [Bug 1262116] Re: Nested servers prevent overlays or fullscreen bypass from working

This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1

---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium

  * New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 42
  . mircommon ABI bumped to 7
  . mirplatform ABI bumped to 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI bumped to 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI bumped to 6
  . mircore ABI added, at version 1
- Enhancements:
  . Added pointer confinement support
  . Identify Raspberry Pi output types correctly
  . Added dead key and compose key support
  . Added gamma support for KMS hardware
  . Added yakkety and zesty gcc-6 support
  . Added surface passthrough support for fullscreen clients of nested
servers
  . Introduced a new library `libmircore'
  . Began migrating from Protobuf to Cap'n Proto starting with events
  . Began support for VirtualBox (servers now start instead of crashing
but full support for GL clients is still missing)
  . Began support for high precision frame timing, implemented for the
KMS, Android and X11 backends so far
  . Added --display-report support for the X11 backend
  . Improved reliability of `mirvanity' latency test tool
  . Moved to using the CSS cursor naming scheme internally, although
the old symbolic indentifiers remain unchanged and still work
  . Added refresh rate to MirSurfaceOutputEvent
  . Many improvements to automated test quality and coverage
  . Smoother desktop zoom using mir_proving_server (Super + two fingers)
- Bugs fixed:
  . FTBFS On Zesty: invalid use of
'struct native_handle' (LP: #1638774)
  . libmirclient-debug-extension-dev install debug/surface.h
twice (LP: #1639153)
  . Mir crashes on virtual box drmModeCrtcSetGamma
Function not implemented (LP: #1638220)
  . Flickering in mir_demo_client_multistream (LP: #1635273)
  . Camera apps (camera & vanity) never exit (LP: #1635010)
  . Clients cannot connect when MIR_SOCKET="" (LP: #1634508)
  . mirtest-dev packaging fails to sepcify boost depends (LP: #1633537)
  . cursor.h is unclear about mir_diagonal_resize_* (LP: #1626924)
  . Inconsistent underscores in cursor names (LP: #1632617)
  . [regression] Accidental libmircommon.so.6 break (LP: #1617865)
  . [regression] mir demo server fails to start with mx4 (LP: #1615703)
  . [regression] Trust prompt now shown when starting camera (LP: #1612256)
  . [regression] make abi-check fails to build (LP: #1626866)
  . Nested servers prevent overlays or fullscreen bypass (LP: #1262116)
  . Failed to get PRIME fd from gbm bo (LP: #1607812)
  . Mir-on-X is difficult to use on 1366x768 laptop (LP: #1590959)
  . Remove useless message 'Surface 0 DPI' in demos (LP: #1559831)
  . Mir fails to cross-build with newer sbuild (LP: #1628507)
  . Infinite loop in AbstractShell::focus_next_session (LP: #1625401)
  . Destroying a presentation chain doesn't trigger ownership
notification to client (LP: #1626503)
  . Keyboard layout not applied on the shell (LP: #1626435)
  . Warning, No syntax specified for the proto file (LP: #1624971)
  . display-report=log reports vsync on non-existent output number
(LP: #1621352)
  . libmirserver-dev missing uuid-dev depends (LP: #1617435)
  . debian/control missing epoxy (LP: #1617256)
  . Downstreams need to disable clang diagnostic "-Wreturn-type-clinkage"
to build against public headers (LP: #1615587)
  . mirtest-dev: mock_display_configuration.h uses mg namespace without
using it (LP: #1614983)
  . FTBFS using clang (LP: #1609612)
  . mesa-kms doesn't fall back to using software cursor if hardware
cursor is unavailable (LP: #1610054)
  . StubGraphicsPlatform::create_display() leaves a dubious state
(LP: #1611337)
  . Mir build/tests fail with gcc-6 and LTO (LP: #1610215)
  . Cross compiling on xenial fails (LP: #1609329)
  . Building with -DMIR_PLATFORM=anroid fails (LP: #1609916)
  . unity-system-compositor crashes on start-up with "Mir fatal error:
Failed to schedule page flip" (LP: #1584894)
  . mir_connection_create_spec_for_tooltip doesn't meet requirements
(LP: #1603922)
  . Updating surface size/location needs to update the pointer confinement
(LP: #1604673)
  . ServerConfigurationOption is not ptest safe (LP: #1607351)
  . HWC's vsync_signal_on is never called when using HWC 1.0 (LP: #1613373)
  . mir_connection_create_spec_for_tooltip does not set aux_rect
(LP: #1632335)
  . VMware virtual connector recognized by Mir as "unknown" (LP: #1248072)
  . Fix code to match the

[Touch-packages] [Bug 1584894] Re: unity-system-compositor (or any Mir server) crashes on start-up with "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics Adapter and QEMU

This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1

---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium

  * New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 42
  . mircommon ABI bumped to 7
  . mirplatform ABI bumped to 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI bumped to 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI bumped to 6
  . mircore ABI added, at version 1
- Enhancements:
  . Added pointer confinement support
  . Identify Raspberry Pi output types correctly
  . Added dead key and compose key support
  . Added gamma support for KMS hardware
  . Added yakkety and zesty gcc-6 support
  . Added surface passthrough support for fullscreen clients of nested
servers
  . Introduced a new library `libmircore'
  . Began migrating from Protobuf to Cap'n Proto starting with events
  . Began support for VirtualBox (servers now start instead of crashing
but full support for GL clients is still missing)
  . Began support for high precision frame timing, implemented for the
KMS, Android and X11 backends so far
  . Added --display-report support for the X11 backend
  . Improved reliability of `mirvanity' latency test tool
  . Moved to using the CSS cursor naming scheme internally, although
the old symbolic indentifiers remain unchanged and still work
  . Added refresh rate to MirSurfaceOutputEvent
  . Many improvements to automated test quality and coverage
  . Smoother desktop zoom using mir_proving_server (Super + two fingers)
- Bugs fixed:
  . FTBFS On Zesty: invalid use of
'struct native_handle' (LP: #1638774)
  . libmirclient-debug-extension-dev install debug/surface.h
twice (LP: #1639153)
  . Mir crashes on virtual box drmModeCrtcSetGamma
Function not implemented (LP: #1638220)
  . Flickering in mir_demo_client_multistream (LP: #1635273)
  . Camera apps (camera & vanity) never exit (LP: #1635010)
  . Clients cannot connect when MIR_SOCKET="" (LP: #1634508)
  . mirtest-dev packaging fails to sepcify boost depends (LP: #1633537)
  . cursor.h is unclear about mir_diagonal_resize_* (LP: #1626924)
  . Inconsistent underscores in cursor names (LP: #1632617)
  . [regression] Accidental libmircommon.so.6 break (LP: #1617865)
  . [regression] mir demo server fails to start with mx4 (LP: #1615703)
  . [regression] Trust prompt now shown when starting camera (LP: #1612256)
  . [regression] make abi-check fails to build (LP: #1626866)
  . Nested servers prevent overlays or fullscreen bypass (LP: #1262116)
  . Failed to get PRIME fd from gbm bo (LP: #1607812)
  . Mir-on-X is difficult to use on 1366x768 laptop (LP: #1590959)
  . Remove useless message 'Surface 0 DPI' in demos (LP: #1559831)
  . Mir fails to cross-build with newer sbuild (LP: #1628507)
  . Infinite loop in AbstractShell::focus_next_session (LP: #1625401)
  . Destroying a presentation chain doesn't trigger ownership
notification to client (LP: #1626503)
  . Keyboard layout not applied on the shell (LP: #1626435)
  . Warning, No syntax specified for the proto file (LP: #1624971)
  . display-report=log reports vsync on non-existent output number
(LP: #1621352)
  . libmirserver-dev missing uuid-dev depends (LP: #1617435)
  . debian/control missing epoxy (LP: #1617256)
  . Downstreams need to disable clang diagnostic "-Wreturn-type-clinkage"
to build against public headers (LP: #1615587)
  . mirtest-dev: mock_display_configuration.h uses mg namespace without
using it (LP: #1614983)
  . FTBFS using clang (LP: #1609612)
  . mesa-kms doesn't fall back to using software cursor if hardware
cursor is unavailable (LP: #1610054)
  . StubGraphicsPlatform::create_display() leaves a dubious state
(LP: #1611337)
  . Mir build/tests fail with gcc-6 and LTO (LP: #1610215)
  . Cross compiling on xenial fails (LP: #1609329)
  . Building with -DMIR_PLATFORM=anroid fails (LP: #1609916)
  . unity-system-compositor crashes on start-up with "Mir fatal error:
Failed to schedule page flip" (LP: #1584894)
  . mir_connection_create_spec_for_tooltip doesn't meet requirements
(LP: #1603922)
  . Updating surface size/location needs to update the pointer confinement
(LP: #1604673)
  . ServerConfigurationOption is not ptest safe (LP: #1607351)
  . HWC's vsync_signal_on is never called when using HWC 1.0 (LP: #1613373)
  . mir_connection_create_spec_for_tooltip does not set aux_rect
(LP: #1632335)
  . VMware virtual connector recognized by Mir as "unknown" (LP: #1248072)
  . Fix code to match the

[Touch-packages] [Bug 1595940] Re: MultiThreadedCompositor test failure in CI

This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1

---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium

  * New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 42
  . mircommon ABI bumped to 7
  . mirplatform ABI bumped to 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI bumped to 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI bumped to 6
  . mircore ABI added, at version 1
- Enhancements:
  . Added pointer confinement support
  . Identify Raspberry Pi output types correctly
  . Added dead key and compose key support
  . Added gamma support for KMS hardware
  . Added yakkety and zesty gcc-6 support
  . Added surface passthrough support for fullscreen clients of nested
servers
  . Introduced a new library `libmircore'
  . Began migrating from Protobuf to Cap'n Proto starting with events
  . Began support for VirtualBox (servers now start instead of crashing
but full support for GL clients is still missing)
  . Began support for high precision frame timing, implemented for the
KMS, Android and X11 backends so far
  . Added --display-report support for the X11 backend
  . Improved reliability of `mirvanity' latency test tool
  . Moved to using the CSS cursor naming scheme internally, although
the old symbolic indentifiers remain unchanged and still work
  . Added refresh rate to MirSurfaceOutputEvent
  . Many improvements to automated test quality and coverage
  . Smoother desktop zoom using mir_proving_server (Super + two fingers)
- Bugs fixed:
  . FTBFS On Zesty: invalid use of
'struct native_handle' (LP: #1638774)
  . libmirclient-debug-extension-dev install debug/surface.h
twice (LP: #1639153)
  . Mir crashes on virtual box drmModeCrtcSetGamma
Function not implemented (LP: #1638220)
  . Flickering in mir_demo_client_multistream (LP: #1635273)
  . Camera apps (camera & vanity) never exit (LP: #1635010)
  . Clients cannot connect when MIR_SOCKET="" (LP: #1634508)
  . mirtest-dev packaging fails to sepcify boost depends (LP: #1633537)
  . cursor.h is unclear about mir_diagonal_resize_* (LP: #1626924)
  . Inconsistent underscores in cursor names (LP: #1632617)
  . [regression] Accidental libmircommon.so.6 break (LP: #1617865)
  . [regression] mir demo server fails to start with mx4 (LP: #1615703)
  . [regression] Trust prompt now shown when starting camera (LP: #1612256)
  . [regression] make abi-check fails to build (LP: #1626866)
  . Nested servers prevent overlays or fullscreen bypass (LP: #1262116)
  . Failed to get PRIME fd from gbm bo (LP: #1607812)
  . Mir-on-X is difficult to use on 1366x768 laptop (LP: #1590959)
  . Remove useless message 'Surface 0 DPI' in demos (LP: #1559831)
  . Mir fails to cross-build with newer sbuild (LP: #1628507)
  . Infinite loop in AbstractShell::focus_next_session (LP: #1625401)
  . Destroying a presentation chain doesn't trigger ownership
notification to client (LP: #1626503)
  . Keyboard layout not applied on the shell (LP: #1626435)
  . Warning, No syntax specified for the proto file (LP: #1624971)
  . display-report=log reports vsync on non-existent output number
(LP: #1621352)
  . libmirserver-dev missing uuid-dev depends (LP: #1617435)
  . debian/control missing epoxy (LP: #1617256)
  . Downstreams need to disable clang diagnostic "-Wreturn-type-clinkage"
to build against public headers (LP: #1615587)
  . mirtest-dev: mock_display_configuration.h uses mg namespace without
using it (LP: #1614983)
  . FTBFS using clang (LP: #1609612)
  . mesa-kms doesn't fall back to using software cursor if hardware
cursor is unavailable (LP: #1610054)
  . StubGraphicsPlatform::create_display() leaves a dubious state
(LP: #1611337)
  . Mir build/tests fail with gcc-6 and LTO (LP: #1610215)
  . Cross compiling on xenial fails (LP: #1609329)
  . Building with -DMIR_PLATFORM=anroid fails (LP: #1609916)
  . unity-system-compositor crashes on start-up with "Mir fatal error:
Failed to schedule page flip" (LP: #1584894)
  . mir_connection_create_spec_for_tooltip doesn't meet requirements
(LP: #1603922)
  . Updating surface size/location needs to update the pointer confinement
(LP: #1604673)
  . ServerConfigurationOption is not ptest safe (LP: #1607351)
  . HWC's vsync_signal_on is never called when using HWC 1.0 (LP: #1613373)
  . mir_connection_create_spec_for_tooltip does not set aux_rect
(LP: #1632335)
  . VMware virtual connector recognized by Mir as "unknown" (LP: #1248072)
  . Fix code to match the

[Touch-packages] [Bug 1650007] Re: Consider changing Google API key

2016-12-15 Thread Jeremy Bicha

Ok, a bit more info, copying from
https://bugzilla.gnome.org/show_bug.cgi?id=771547#c62

--
The internal Google OAuth2 authentication had been introduced in eds 3.20.0 
(thus it's pretty new), for which I released eds 3.20.6 with all the yet-known 
fixes recently, in a hope that distros which still use 3.20.x will update and 
thus will help all users. I'm not going to change the Google API keys in eds, 
because the statistics which the Google server provides indicate that the usage 
is pretty fine with the internal eds Google API keys. Just compare, the numbers 
from the Tuesday this week:

- for the GOA, the past 24 hours:
  CalDAV API  - 104 millions of requests, 99 millions errors (95.34%)
  Tasks API   - 65 millions of requests, 65 millions errors (99.93%)

- for the eds, the past 24 hours:
  CalDAV API   - 399 thousands of requests, 5 thousands errors (1.37%)
  CardDAV API  - 59 thousands of requests, 12 errors (0.02%)
  Contacts API - 30 thousands of requests, 31 errors (0.1%)
  Tasks API- 9 thousands of requests, 0 errors (0%)

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

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

Title:
  Consider changing Google API key

Status in account-plugins package in Ubuntu:
  New

Bug description:
  evolution-data-server (e-d-s) 3.20 before 3.20.6 and 3.22 before
  3.22.2 had bugs that caused users using Google services to experience
  daily limit timeouts and authentication errors. Unfortunately, users
  using older versions are causing those problems for everyone that
  still uses the affected API key. Therefore GNOME is updating the API
  key used by GNOME Online Accounts. For more info, see LP: #1649995 and
  https://bugzilla.gnome.org/774202

  - I don't know yet if e-d-s before 3.20 is also affected. I asked but
  you're welcome to ask the Evolution devs yourself.
  https://bugzilla.gnome.org/show_bug.cgi?id=771547#c61

  - Upstream evolution has two ways to configure a Google account: GNOME
  Online Accounts and e-d-s. I assume Ubuntu Online Accounts is a 3rd
  way. (I think e-d-s will need to switch to a new Google API key too
  but that hasn't happened yet.)

  - For Ubuntu 16.10, we need the latest evolution-data-server SRU (LP:
  #1639926) to be pushed to yakkety-updates and fully 100% phased before
  publishing the new key.

  - Therefore, assuming Ubuntu Online Accounts is affected, I suggest
  you consider changing the Google API key used in Ubuntu 16.10 and
  above. Once we figure out if e-d-s needs to be updated for 16.04 (and
  possibly earlier releases), I believe we'll need to update the key
  there too.

  - On the other hand, since we control Ubuntu updates (unlike GNOME
  which has not control over who uses what version of their stuff) maybe
  we don't need to change the key after all. Maybe we just need to push
  the e-d-s SRUs as security updates to ensure people use the fixed
  versions?

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

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

[Touch-packages] [Bug 1590959] Re: Mir-on-X is difficult to use (window too big) on a 1366x768 laptop

This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1

---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium

  * New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 42
  . mircommon ABI bumped to 7
  . mirplatform ABI bumped to 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI bumped to 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI bumped to 6
  . mircore ABI added, at version 1
- Enhancements:
  . Added pointer confinement support
  . Identify Raspberry Pi output types correctly
  . Added dead key and compose key support
  . Added gamma support for KMS hardware
  . Added yakkety and zesty gcc-6 support
  . Added surface passthrough support for fullscreen clients of nested
servers
  . Introduced a new library `libmircore'
  . Began migrating from Protobuf to Cap'n Proto starting with events
  . Began support for VirtualBox (servers now start instead of crashing
but full support for GL clients is still missing)
  . Began support for high precision frame timing, implemented for the
KMS, Android and X11 backends so far
  . Added --display-report support for the X11 backend
  . Improved reliability of `mirvanity' latency test tool
  . Moved to using the CSS cursor naming scheme internally, although
the old symbolic indentifiers remain unchanged and still work
  . Added refresh rate to MirSurfaceOutputEvent
  . Many improvements to automated test quality and coverage
  . Smoother desktop zoom using mir_proving_server (Super + two fingers)
- Bugs fixed:
  . FTBFS On Zesty: invalid use of
'struct native_handle' (LP: #1638774)
  . libmirclient-debug-extension-dev install debug/surface.h
twice (LP: #1639153)
  . Mir crashes on virtual box drmModeCrtcSetGamma
Function not implemented (LP: #1638220)
  . Flickering in mir_demo_client_multistream (LP: #1635273)
  . Camera apps (camera & vanity) never exit (LP: #1635010)
  . Clients cannot connect when MIR_SOCKET="" (LP: #1634508)
  . mirtest-dev packaging fails to sepcify boost depends (LP: #1633537)
  . cursor.h is unclear about mir_diagonal_resize_* (LP: #1626924)
  . Inconsistent underscores in cursor names (LP: #1632617)
  . [regression] Accidental libmircommon.so.6 break (LP: #1617865)
  . [regression] mir demo server fails to start with mx4 (LP: #1615703)
  . [regression] Trust prompt now shown when starting camera (LP: #1612256)
  . [regression] make abi-check fails to build (LP: #1626866)
  . Nested servers prevent overlays or fullscreen bypass (LP: #1262116)
  . Failed to get PRIME fd from gbm bo (LP: #1607812)
  . Mir-on-X is difficult to use on 1366x768 laptop (LP: #1590959)
  . Remove useless message 'Surface 0 DPI' in demos (LP: #1559831)
  . Mir fails to cross-build with newer sbuild (LP: #1628507)
  . Infinite loop in AbstractShell::focus_next_session (LP: #1625401)
  . Destroying a presentation chain doesn't trigger ownership
notification to client (LP: #1626503)
  . Keyboard layout not applied on the shell (LP: #1626435)
  . Warning, No syntax specified for the proto file (LP: #1624971)
  . display-report=log reports vsync on non-existent output number
(LP: #1621352)
  . libmirserver-dev missing uuid-dev depends (LP: #1617435)
  . debian/control missing epoxy (LP: #1617256)
  . Downstreams need to disable clang diagnostic "-Wreturn-type-clinkage"
to build against public headers (LP: #1615587)
  . mirtest-dev: mock_display_configuration.h uses mg namespace without
using it (LP: #1614983)
  . FTBFS using clang (LP: #1609612)
  . mesa-kms doesn't fall back to using software cursor if hardware
cursor is unavailable (LP: #1610054)
  . StubGraphicsPlatform::create_display() leaves a dubious state
(LP: #1611337)
  . Mir build/tests fail with gcc-6 and LTO (LP: #1610215)
  . Cross compiling on xenial fails (LP: #1609329)
  . Building with -DMIR_PLATFORM=anroid fails (LP: #1609916)
  . unity-system-compositor crashes on start-up with "Mir fatal error:
Failed to schedule page flip" (LP: #1584894)
  . mir_connection_create_spec_for_tooltip doesn't meet requirements
(LP: #1603922)
  . Updating surface size/location needs to update the pointer confinement
(LP: #1604673)
  . ServerConfigurationOption is not ptest safe (LP: #1607351)
  . HWC's vsync_signal_on is never called when using HWC 1.0 (LP: #1613373)
  . mir_connection_create_spec_for_tooltip does not set aux_rect
(LP: #1632335)
  . VMware virtual connector recognized by Mir as "unknown" (LP: #1248072)
  . Fix code to match the

[Touch-packages] [Bug 1563210] Re: CI Failure in DisplayConfiguration/DisplayFormatSetting.can_get_all_output_format/{6, 2}

This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1

---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium

  * New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 42
  . mircommon ABI bumped to 7
  . mirplatform ABI bumped to 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI bumped to 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI bumped to 6
  . mircore ABI added, at version 1
- Enhancements:
  . Added pointer confinement support
  . Identify Raspberry Pi output types correctly
  . Added dead key and compose key support
  . Added gamma support for KMS hardware
  . Added yakkety and zesty gcc-6 support
  . Added surface passthrough support for fullscreen clients of nested
servers
  . Introduced a new library `libmircore'
  . Began migrating from Protobuf to Cap'n Proto starting with events
  . Began support for VirtualBox (servers now start instead of crashing
but full support for GL clients is still missing)
  . Began support for high precision frame timing, implemented for the
KMS, Android and X11 backends so far
  . Added --display-report support for the X11 backend
  . Improved reliability of `mirvanity' latency test tool
  . Moved to using the CSS cursor naming scheme internally, although
the old symbolic indentifiers remain unchanged and still work
  . Added refresh rate to MirSurfaceOutputEvent
  . Many improvements to automated test quality and coverage
  . Smoother desktop zoom using mir_proving_server (Super + two fingers)
- Bugs fixed:
  . FTBFS On Zesty: invalid use of
'struct native_handle' (LP: #1638774)
  . libmirclient-debug-extension-dev install debug/surface.h
twice (LP: #1639153)
  . Mir crashes on virtual box drmModeCrtcSetGamma
Function not implemented (LP: #1638220)
  . Flickering in mir_demo_client_multistream (LP: #1635273)
  . Camera apps (camera & vanity) never exit (LP: #1635010)
  . Clients cannot connect when MIR_SOCKET="" (LP: #1634508)
  . mirtest-dev packaging fails to sepcify boost depends (LP: #1633537)
  . cursor.h is unclear about mir_diagonal_resize_* (LP: #1626924)
  . Inconsistent underscores in cursor names (LP: #1632617)
  . [regression] Accidental libmircommon.so.6 break (LP: #1617865)
  . [regression] mir demo server fails to start with mx4 (LP: #1615703)
  . [regression] Trust prompt now shown when starting camera (LP: #1612256)
  . [regression] make abi-check fails to build (LP: #1626866)
  . Nested servers prevent overlays or fullscreen bypass (LP: #1262116)
  . Failed to get PRIME fd from gbm bo (LP: #1607812)
  . Mir-on-X is difficult to use on 1366x768 laptop (LP: #1590959)
  . Remove useless message 'Surface 0 DPI' in demos (LP: #1559831)
  . Mir fails to cross-build with newer sbuild (LP: #1628507)
  . Infinite loop in AbstractShell::focus_next_session (LP: #1625401)
  . Destroying a presentation chain doesn't trigger ownership
notification to client (LP: #1626503)
  . Keyboard layout not applied on the shell (LP: #1626435)
  . Warning, No syntax specified for the proto file (LP: #1624971)
  . display-report=log reports vsync on non-existent output number
(LP: #1621352)
  . libmirserver-dev missing uuid-dev depends (LP: #1617435)
  . debian/control missing epoxy (LP: #1617256)
  . Downstreams need to disable clang diagnostic "-Wreturn-type-clinkage"
to build against public headers (LP: #1615587)
  . mirtest-dev: mock_display_configuration.h uses mg namespace without
using it (LP: #1614983)
  . FTBFS using clang (LP: #1609612)
  . mesa-kms doesn't fall back to using software cursor if hardware
cursor is unavailable (LP: #1610054)
  . StubGraphicsPlatform::create_display() leaves a dubious state
(LP: #1611337)
  . Mir build/tests fail with gcc-6 and LTO (LP: #1610215)
  . Cross compiling on xenial fails (LP: #1609329)
  . Building with -DMIR_PLATFORM=anroid fails (LP: #1609916)
  . unity-system-compositor crashes on start-up with "Mir fatal error:
Failed to schedule page flip" (LP: #1584894)
  . mir_connection_create_spec_for_tooltip doesn't meet requirements
(LP: #1603922)
  . Updating surface size/location needs to update the pointer confinement
(LP: #1604673)
  . ServerConfigurationOption is not ptest safe (LP: #1607351)
  . HWC's vsync_signal_on is never called when using HWC 1.0 (LP: #1613373)
  . mir_connection_create_spec_for_tooltip does not set aux_rect
(LP: #1632335)
  . VMware virtual connector recognized by Mir as "unknown" (LP: #1248072)
  . Fix code to match the

[Touch-packages] [Bug 1615703] Re: [regression] mir demo server fails to start with mx4

This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1

---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium

  * New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 42
  . mircommon ABI bumped to 7
  . mirplatform ABI bumped to 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI bumped to 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI bumped to 6
  . mircore ABI added, at version 1
- Enhancements:
  . Added pointer confinement support
  . Identify Raspberry Pi output types correctly
  . Added dead key and compose key support
  . Added gamma support for KMS hardware
  . Added yakkety and zesty gcc-6 support
  . Added surface passthrough support for fullscreen clients of nested
servers
  . Introduced a new library `libmircore'
  . Began migrating from Protobuf to Cap'n Proto starting with events
  . Began support for VirtualBox (servers now start instead of crashing
but full support for GL clients is still missing)
  . Began support for high precision frame timing, implemented for the
KMS, Android and X11 backends so far
  . Added --display-report support for the X11 backend
  . Improved reliability of `mirvanity' latency test tool
  . Moved to using the CSS cursor naming scheme internally, although
the old symbolic indentifiers remain unchanged and still work
  . Added refresh rate to MirSurfaceOutputEvent
  . Many improvements to automated test quality and coverage
  . Smoother desktop zoom using mir_proving_server (Super + two fingers)
- Bugs fixed:
  . FTBFS On Zesty: invalid use of
'struct native_handle' (LP: #1638774)
  . libmirclient-debug-extension-dev install debug/surface.h
twice (LP: #1639153)
  . Mir crashes on virtual box drmModeCrtcSetGamma
Function not implemented (LP: #1638220)
  . Flickering in mir_demo_client_multistream (LP: #1635273)
  . Camera apps (camera & vanity) never exit (LP: #1635010)
  . Clients cannot connect when MIR_SOCKET="" (LP: #1634508)
  . mirtest-dev packaging fails to sepcify boost depends (LP: #1633537)
  . cursor.h is unclear about mir_diagonal_resize_* (LP: #1626924)
  . Inconsistent underscores in cursor names (LP: #1632617)
  . [regression] Accidental libmircommon.so.6 break (LP: #1617865)
  . [regression] mir demo server fails to start with mx4 (LP: #1615703)
  . [regression] Trust prompt now shown when starting camera (LP: #1612256)
  . [regression] make abi-check fails to build (LP: #1626866)
  . Nested servers prevent overlays or fullscreen bypass (LP: #1262116)
  . Failed to get PRIME fd from gbm bo (LP: #1607812)
  . Mir-on-X is difficult to use on 1366x768 laptop (LP: #1590959)
  . Remove useless message 'Surface 0 DPI' in demos (LP: #1559831)
  . Mir fails to cross-build with newer sbuild (LP: #1628507)
  . Infinite loop in AbstractShell::focus_next_session (LP: #1625401)
  . Destroying a presentation chain doesn't trigger ownership
notification to client (LP: #1626503)
  . Keyboard layout not applied on the shell (LP: #1626435)
  . Warning, No syntax specified for the proto file (LP: #1624971)
  . display-report=log reports vsync on non-existent output number
(LP: #1621352)
  . libmirserver-dev missing uuid-dev depends (LP: #1617435)
  . debian/control missing epoxy (LP: #1617256)
  . Downstreams need to disable clang diagnostic "-Wreturn-type-clinkage"
to build against public headers (LP: #1615587)
  . mirtest-dev: mock_display_configuration.h uses mg namespace without
using it (LP: #1614983)
  . FTBFS using clang (LP: #1609612)
  . mesa-kms doesn't fall back to using software cursor if hardware
cursor is unavailable (LP: #1610054)
  . StubGraphicsPlatform::create_display() leaves a dubious state
(LP: #1611337)
  . Mir build/tests fail with gcc-6 and LTO (LP: #1610215)
  . Cross compiling on xenial fails (LP: #1609329)
  . Building with -DMIR_PLATFORM=anroid fails (LP: #1609916)
  . unity-system-compositor crashes on start-up with "Mir fatal error:
Failed to schedule page flip" (LP: #1584894)
  . mir_connection_create_spec_for_tooltip doesn't meet requirements
(LP: #1603922)
  . Updating surface size/location needs to update the pointer confinement
(LP: #1604673)
  . ServerConfigurationOption is not ptest safe (LP: #1607351)
  . HWC's vsync_signal_on is never called when using HWC 1.0 (LP: #1613373)
  . mir_connection_create_spec_for_tooltip does not set aux_rect
(LP: #1632335)
  . VMware virtual connector recognized by Mir as "unknown" (LP: #1248072)
  . Fix code to match the

[Touch-packages] [Bug 1610054] Re: mesa-kms doesn't fall back to using a software cursor if a hardware cursor is unavailable

This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1

---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium

  * New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 42
  . mircommon ABI bumped to 7
  . mirplatform ABI bumped to 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI bumped to 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI bumped to 6
  . mircore ABI added, at version 1
- Enhancements:
  . Added pointer confinement support
  . Identify Raspberry Pi output types correctly
  . Added dead key and compose key support
  . Added gamma support for KMS hardware
  . Added yakkety and zesty gcc-6 support
  . Added surface passthrough support for fullscreen clients of nested
servers
  . Introduced a new library `libmircore'
  . Began migrating from Protobuf to Cap'n Proto starting with events
  . Began support for VirtualBox (servers now start instead of crashing
but full support for GL clients is still missing)
  . Began support for high precision frame timing, implemented for the
KMS, Android and X11 backends so far
  . Added --display-report support for the X11 backend
  . Improved reliability of `mirvanity' latency test tool
  . Moved to using the CSS cursor naming scheme internally, although
the old symbolic indentifiers remain unchanged and still work
  . Added refresh rate to MirSurfaceOutputEvent
  . Many improvements to automated test quality and coverage
  . Smoother desktop zoom using mir_proving_server (Super + two fingers)
- Bugs fixed:
  . FTBFS On Zesty: invalid use of
'struct native_handle' (LP: #1638774)
  . libmirclient-debug-extension-dev install debug/surface.h
twice (LP: #1639153)
  . Mir crashes on virtual box drmModeCrtcSetGamma
Function not implemented (LP: #1638220)
  . Flickering in mir_demo_client_multistream (LP: #1635273)
  . Camera apps (camera & vanity) never exit (LP: #1635010)
  . Clients cannot connect when MIR_SOCKET="" (LP: #1634508)
  . mirtest-dev packaging fails to sepcify boost depends (LP: #1633537)
  . cursor.h is unclear about mir_diagonal_resize_* (LP: #1626924)
  . Inconsistent underscores in cursor names (LP: #1632617)
  . [regression] Accidental libmircommon.so.6 break (LP: #1617865)
  . [regression] mir demo server fails to start with mx4 (LP: #1615703)
  . [regression] Trust prompt now shown when starting camera (LP: #1612256)
  . [regression] make abi-check fails to build (LP: #1626866)
  . Nested servers prevent overlays or fullscreen bypass (LP: #1262116)
  . Failed to get PRIME fd from gbm bo (LP: #1607812)
  . Mir-on-X is difficult to use on 1366x768 laptop (LP: #1590959)
  . Remove useless message 'Surface 0 DPI' in demos (LP: #1559831)
  . Mir fails to cross-build with newer sbuild (LP: #1628507)
  . Infinite loop in AbstractShell::focus_next_session (LP: #1625401)
  . Destroying a presentation chain doesn't trigger ownership
notification to client (LP: #1626503)
  . Keyboard layout not applied on the shell (LP: #1626435)
  . Warning, No syntax specified for the proto file (LP: #1624971)
  . display-report=log reports vsync on non-existent output number
(LP: #1621352)
  . libmirserver-dev missing uuid-dev depends (LP: #1617435)
  . debian/control missing epoxy (LP: #1617256)
  . Downstreams need to disable clang diagnostic "-Wreturn-type-clinkage"
to build against public headers (LP: #1615587)
  . mirtest-dev: mock_display_configuration.h uses mg namespace without
using it (LP: #1614983)
  . FTBFS using clang (LP: #1609612)
  . mesa-kms doesn't fall back to using software cursor if hardware
cursor is unavailable (LP: #1610054)
  . StubGraphicsPlatform::create_display() leaves a dubious state
(LP: #1611337)
  . Mir build/tests fail with gcc-6 and LTO (LP: #1610215)
  . Cross compiling on xenial fails (LP: #1609329)
  . Building with -DMIR_PLATFORM=anroid fails (LP: #1609916)
  . unity-system-compositor crashes on start-up with "Mir fatal error:
Failed to schedule page flip" (LP: #1584894)
  . mir_connection_create_spec_for_tooltip doesn't meet requirements
(LP: #1603922)
  . Updating surface size/location needs to update the pointer confinement
(LP: #1604673)
  . ServerConfigurationOption is not ptest safe (LP: #1607351)
  . HWC's vsync_signal_on is never called when using HWC 1.0 (LP: #1613373)
  . mir_connection_create_spec_for_tooltip does not set aux_rect
(LP: #1632335)
  . VMware virtual connector recognized by Mir as "unknown" (LP: #1248072)
  . Fix code to match the

[Touch-packages] [Bug 1613352] Re: Test timeout: MesaDisplayConfigurationTest.reads_updated_subpixel_information

This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1

---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium

  * New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 42
  . mircommon ABI bumped to 7
  . mirplatform ABI bumped to 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI bumped to 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI bumped to 6
  . mircore ABI added, at version 1
- Enhancements:
  . Added pointer confinement support
  . Identify Raspberry Pi output types correctly
  . Added dead key and compose key support
  . Added gamma support for KMS hardware
  . Added yakkety and zesty gcc-6 support
  . Added surface passthrough support for fullscreen clients of nested
servers
  . Introduced a new library `libmircore'
  . Began migrating from Protobuf to Cap'n Proto starting with events
  . Began support for VirtualBox (servers now start instead of crashing
but full support for GL clients is still missing)
  . Began support for high precision frame timing, implemented for the
KMS, Android and X11 backends so far
  . Added --display-report support for the X11 backend
  . Improved reliability of `mirvanity' latency test tool
  . Moved to using the CSS cursor naming scheme internally, although
the old symbolic indentifiers remain unchanged and still work
  . Added refresh rate to MirSurfaceOutputEvent
  . Many improvements to automated test quality and coverage
  . Smoother desktop zoom using mir_proving_server (Super + two fingers)
- Bugs fixed:
  . FTBFS On Zesty: invalid use of
'struct native_handle' (LP: #1638774)
  . libmirclient-debug-extension-dev install debug/surface.h
twice (LP: #1639153)
  . Mir crashes on virtual box drmModeCrtcSetGamma
Function not implemented (LP: #1638220)
  . Flickering in mir_demo_client_multistream (LP: #1635273)
  . Camera apps (camera & vanity) never exit (LP: #1635010)
  . Clients cannot connect when MIR_SOCKET="" (LP: #1634508)
  . mirtest-dev packaging fails to sepcify boost depends (LP: #1633537)
  . cursor.h is unclear about mir_diagonal_resize_* (LP: #1626924)
  . Inconsistent underscores in cursor names (LP: #1632617)
  . [regression] Accidental libmircommon.so.6 break (LP: #1617865)
  . [regression] mir demo server fails to start with mx4 (LP: #1615703)
  . [regression] Trust prompt now shown when starting camera (LP: #1612256)
  . [regression] make abi-check fails to build (LP: #1626866)
  . Nested servers prevent overlays or fullscreen bypass (LP: #1262116)
  . Failed to get PRIME fd from gbm bo (LP: #1607812)
  . Mir-on-X is difficult to use on 1366x768 laptop (LP: #1590959)
  . Remove useless message 'Surface 0 DPI' in demos (LP: #1559831)
  . Mir fails to cross-build with newer sbuild (LP: #1628507)
  . Infinite loop in AbstractShell::focus_next_session (LP: #1625401)
  . Destroying a presentation chain doesn't trigger ownership
notification to client (LP: #1626503)
  . Keyboard layout not applied on the shell (LP: #1626435)
  . Warning, No syntax specified for the proto file (LP: #1624971)
  . display-report=log reports vsync on non-existent output number
(LP: #1621352)
  . libmirserver-dev missing uuid-dev depends (LP: #1617435)
  . debian/control missing epoxy (LP: #1617256)
  . Downstreams need to disable clang diagnostic "-Wreturn-type-clinkage"
to build against public headers (LP: #1615587)
  . mirtest-dev: mock_display_configuration.h uses mg namespace without
using it (LP: #1614983)
  . FTBFS using clang (LP: #1609612)
  . mesa-kms doesn't fall back to using software cursor if hardware
cursor is unavailable (LP: #1610054)
  . StubGraphicsPlatform::create_display() leaves a dubious state
(LP: #1611337)
  . Mir build/tests fail with gcc-6 and LTO (LP: #1610215)
  . Cross compiling on xenial fails (LP: #1609329)
  . Building with -DMIR_PLATFORM=anroid fails (LP: #1609916)
  . unity-system-compositor crashes on start-up with "Mir fatal error:
Failed to schedule page flip" (LP: #1584894)
  . mir_connection_create_spec_for_tooltip doesn't meet requirements
(LP: #1603922)
  . Updating surface size/location needs to update the pointer confinement
(LP: #1604673)
  . ServerConfigurationOption is not ptest safe (LP: #1607351)
  . HWC's vsync_signal_on is never called when using HWC 1.0 (LP: #1613373)
  . mir_connection_create_spec_for_tooltip does not set aux_rect
(LP: #1632335)
  . VMware virtual connector recognized by Mir as "unknown" (LP: #1248072)
  . Fix code to match the

[Touch-packages] [Bug 1604673] Re: If a surface updates its size the pointer confinement region isnt updated

This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1

---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium

  * New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 42
  . mircommon ABI bumped to 7
  . mirplatform ABI bumped to 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI bumped to 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI bumped to 6
  . mircore ABI added, at version 1
- Enhancements:
  . Added pointer confinement support
  . Identify Raspberry Pi output types correctly
  . Added dead key and compose key support
  . Added gamma support for KMS hardware
  . Added yakkety and zesty gcc-6 support
  . Added surface passthrough support for fullscreen clients of nested
servers
  . Introduced a new library `libmircore'
  . Began migrating from Protobuf to Cap'n Proto starting with events
  . Began support for VirtualBox (servers now start instead of crashing
but full support for GL clients is still missing)
  . Began support for high precision frame timing, implemented for the
KMS, Android and X11 backends so far
  . Added --display-report support for the X11 backend
  . Improved reliability of `mirvanity' latency test tool
  . Moved to using the CSS cursor naming scheme internally, although
the old symbolic indentifiers remain unchanged and still work
  . Added refresh rate to MirSurfaceOutputEvent
  . Many improvements to automated test quality and coverage
  . Smoother desktop zoom using mir_proving_server (Super + two fingers)
- Bugs fixed:
  . FTBFS On Zesty: invalid use of
'struct native_handle' (LP: #1638774)
  . libmirclient-debug-extension-dev install debug/surface.h
twice (LP: #1639153)
  . Mir crashes on virtual box drmModeCrtcSetGamma
Function not implemented (LP: #1638220)
  . Flickering in mir_demo_client_multistream (LP: #1635273)
  . Camera apps (camera & vanity) never exit (LP: #1635010)
  . Clients cannot connect when MIR_SOCKET="" (LP: #1634508)
  . mirtest-dev packaging fails to sepcify boost depends (LP: #1633537)
  . cursor.h is unclear about mir_diagonal_resize_* (LP: #1626924)
  . Inconsistent underscores in cursor names (LP: #1632617)
  . [regression] Accidental libmircommon.so.6 break (LP: #1617865)
  . [regression] mir demo server fails to start with mx4 (LP: #1615703)
  . [regression] Trust prompt now shown when starting camera (LP: #1612256)
  . [regression] make abi-check fails to build (LP: #1626866)
  . Nested servers prevent overlays or fullscreen bypass (LP: #1262116)
  . Failed to get PRIME fd from gbm bo (LP: #1607812)
  . Mir-on-X is difficult to use on 1366x768 laptop (LP: #1590959)
  . Remove useless message 'Surface 0 DPI' in demos (LP: #1559831)
  . Mir fails to cross-build with newer sbuild (LP: #1628507)
  . Infinite loop in AbstractShell::focus_next_session (LP: #1625401)
  . Destroying a presentation chain doesn't trigger ownership
notification to client (LP: #1626503)
  . Keyboard layout not applied on the shell (LP: #1626435)
  . Warning, No syntax specified for the proto file (LP: #1624971)
  . display-report=log reports vsync on non-existent output number
(LP: #1621352)
  . libmirserver-dev missing uuid-dev depends (LP: #1617435)
  . debian/control missing epoxy (LP: #1617256)
  . Downstreams need to disable clang diagnostic "-Wreturn-type-clinkage"
to build against public headers (LP: #1615587)
  . mirtest-dev: mock_display_configuration.h uses mg namespace without
using it (LP: #1614983)
  . FTBFS using clang (LP: #1609612)
  . mesa-kms doesn't fall back to using software cursor if hardware
cursor is unavailable (LP: #1610054)
  . StubGraphicsPlatform::create_display() leaves a dubious state
(LP: #1611337)
  . Mir build/tests fail with gcc-6 and LTO (LP: #1610215)
  . Cross compiling on xenial fails (LP: #1609329)
  . Building with -DMIR_PLATFORM=anroid fails (LP: #1609916)
  . unity-system-compositor crashes on start-up with "Mir fatal error:
Failed to schedule page flip" (LP: #1584894)
  . mir_connection_create_spec_for_tooltip doesn't meet requirements
(LP: #1603922)
  . Updating surface size/location needs to update the pointer confinement
(LP: #1604673)
  . ServerConfigurationOption is not ptest safe (LP: #1607351)
  . HWC's vsync_signal_on is never called when using HWC 1.0 (LP: #1613373)
  . mir_connection_create_spec_for_tooltip does not set aux_rect
(LP: #1632335)
  . VMware virtual connector recognized by Mir as "unknown" (LP: #1248072)
  . Fix code to match the

[Touch-packages] [Bug 1621352] Re: --display-report=log reports vsync on non-existent output number

This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1

---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium

  * New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 42
  . mircommon ABI bumped to 7
  . mirplatform ABI bumped to 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI bumped to 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI bumped to 6
  . mircore ABI added, at version 1
- Enhancements:
  . Added pointer confinement support
  . Identify Raspberry Pi output types correctly
  . Added dead key and compose key support
  . Added gamma support for KMS hardware
  . Added yakkety and zesty gcc-6 support
  . Added surface passthrough support for fullscreen clients of nested
servers
  . Introduced a new library `libmircore'
  . Began migrating from Protobuf to Cap'n Proto starting with events
  . Began support for VirtualBox (servers now start instead of crashing
but full support for GL clients is still missing)
  . Began support for high precision frame timing, implemented for the
KMS, Android and X11 backends so far
  . Added --display-report support for the X11 backend
  . Improved reliability of `mirvanity' latency test tool
  . Moved to using the CSS cursor naming scheme internally, although
the old symbolic indentifiers remain unchanged and still work
  . Added refresh rate to MirSurfaceOutputEvent
  . Many improvements to automated test quality and coverage
  . Smoother desktop zoom using mir_proving_server (Super + two fingers)
- Bugs fixed:
  . FTBFS On Zesty: invalid use of
'struct native_handle' (LP: #1638774)
  . libmirclient-debug-extension-dev install debug/surface.h
twice (LP: #1639153)
  . Mir crashes on virtual box drmModeCrtcSetGamma
Function not implemented (LP: #1638220)
  . Flickering in mir_demo_client_multistream (LP: #1635273)
  . Camera apps (camera & vanity) never exit (LP: #1635010)
  . Clients cannot connect when MIR_SOCKET="" (LP: #1634508)
  . mirtest-dev packaging fails to sepcify boost depends (LP: #1633537)
  . cursor.h is unclear about mir_diagonal_resize_* (LP: #1626924)
  . Inconsistent underscores in cursor names (LP: #1632617)
  . [regression] Accidental libmircommon.so.6 break (LP: #1617865)
  . [regression] mir demo server fails to start with mx4 (LP: #1615703)
  . [regression] Trust prompt now shown when starting camera (LP: #1612256)
  . [regression] make abi-check fails to build (LP: #1626866)
  . Nested servers prevent overlays or fullscreen bypass (LP: #1262116)
  . Failed to get PRIME fd from gbm bo (LP: #1607812)
  . Mir-on-X is difficult to use on 1366x768 laptop (LP: #1590959)
  . Remove useless message 'Surface 0 DPI' in demos (LP: #1559831)
  . Mir fails to cross-build with newer sbuild (LP: #1628507)
  . Infinite loop in AbstractShell::focus_next_session (LP: #1625401)
  . Destroying a presentation chain doesn't trigger ownership
notification to client (LP: #1626503)
  . Keyboard layout not applied on the shell (LP: #1626435)
  . Warning, No syntax specified for the proto file (LP: #1624971)
  . display-report=log reports vsync on non-existent output number
(LP: #1621352)
  . libmirserver-dev missing uuid-dev depends (LP: #1617435)
  . debian/control missing epoxy (LP: #1617256)
  . Downstreams need to disable clang diagnostic "-Wreturn-type-clinkage"
to build against public headers (LP: #1615587)
  . mirtest-dev: mock_display_configuration.h uses mg namespace without
using it (LP: #1614983)
  . FTBFS using clang (LP: #1609612)
  . mesa-kms doesn't fall back to using software cursor if hardware
cursor is unavailable (LP: #1610054)
  . StubGraphicsPlatform::create_display() leaves a dubious state
(LP: #1611337)
  . Mir build/tests fail with gcc-6 and LTO (LP: #1610215)
  . Cross compiling on xenial fails (LP: #1609329)
  . Building with -DMIR_PLATFORM=anroid fails (LP: #1609916)
  . unity-system-compositor crashes on start-up with "Mir fatal error:
Failed to schedule page flip" (LP: #1584894)
  . mir_connection_create_spec_for_tooltip doesn't meet requirements
(LP: #1603922)
  . Updating surface size/location needs to update the pointer confinement
(LP: #1604673)
  . ServerConfigurationOption is not ptest safe (LP: #1607351)
  . HWC's vsync_signal_on is never called when using HWC 1.0 (LP: #1613373)
  . mir_connection_create_spec_for_tooltip does not set aux_rect
(LP: #1632335)
  . VMware virtual connector recognized by Mir as "unknown" (LP: #1248072)
  . Fix code to match the

[Touch-packages] [Bug 1607351] Re: ServerConfigurationOption is not ptest (parallel test running) safe