date:20161128

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

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

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

Title:
  no IDN in nslookup and host

Status in BIND:
  New
Status in bind9 package in Ubuntu:
  Confirmed
Status in iputils package in Ubuntu:
  Confirmed
Status in bind9 package in Debian:
  New

Bug description:
  Binary package hint: bind9

  Neither nslookup or host supports IDN. If you try , for example, to
  get the IP for "registrera-domän.se" it fails every time. As the use
  of IDN is increasing I think it would be a good thing if these tools
  supported this.

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

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

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-28 Thread Lorn Potter

where is the latest bzr repo?

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

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions

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

[Touch-packages] [Bug 1616422] Re: [trusty SRU/FFE] Add systemd binary package for snapd

2016-11-28 Thread Po-Hsu Lin

Forgot to mention that the apparmor, libapparmor-perl, libapparmor1
packages are from Thomas' ppa as well.

Verification step 7,8,9 are all good for the 4.4 hwe kernel on Trusty.

And I check with 3.13 kernel again, it works with apparmor package
installed from Thomas' paa too.

As a result, I will set the tag to verification-done.
Thanks

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

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

Title:
  [trusty SRU/FFE] Add systemd binary package for snapd

Status in init-system-helpers package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in init-system-helpers source package in Trusty:
  Fix Committed
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.

  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the
  other binary packages do not change and there are no code changes that
  affect processes other than the "deputy pid 1" service manager). So
  for plain upgrades the regression potential is very low. However,
  there is a medium potential for breakage when actually installing the
  new systemd package, as it might interfere with upstart jobs or other
  running processes, cause boot/shutdown hangs, etc.

  For init-system-helpers, the regression potential is near-zero: We
  never had (and never will) systemd as pid 1 in trusty, so deb-systemd-
  invoke was previously never called. It does get called now if you
  install Ubuntu packages that ship a systemd unit, so we need to make
  that a no-op to retain the current behaviour.

  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.

   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.

   3. Ensure that "sudo journalctl" works and that "sudo systemctl
  status systemd-journald" is running and has a few lines of log at the
  end (unlike what you get when you run systemctl as user).

   4. Install a package that ships a systemd .service file, such as
  "haveged". Ensure that the service file is ignored, "pgrep -af
  haveged" should only have *one* process and "systemctl status haveged"
  should not be running (it should not exist, or not be enabled and be
  inactive). [This part also needs the updated init-system-helpers].

     The only services that are running are expected to be systemd-
  journald.service and systemd-journald.socket.

   5. Ensure that the standard targets are active, as that is where
  third-party/snap services hook into:

  systemctl status sysinit.target multi-user.target default.target

   6. Install snapd (not in trusty yet, e. g. from Thomas' PPA) and
  ensure you can install a snap, and its services start after installing
  the snap and after rebooting.

   7. Run "sudo apt-get install --reinstall systemd" to ensure that
  upgrades to newer systemd trusty versions work. The running systemd
  should *not* be restarted as that would disrupt snapd and its services
  (verify that the pid in "initctl status systemd" is the same before
  and after the upgrade).

   8. Run "sudo apt install -y colord && sudo apt purge -y colord". This
  should succeed.

   9. Dist-upgrade to 16.04 to ensure that there are no file conflicts,
  dependency issues, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1616422/+subscriptions

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

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-28 Thread Olivier Tilloy

@Lorn: no need for webbrowser-app, the issue can be reliably reproduced
with the standalone QML example in comment #1. I just tested on arale
with the latest rc-proposed image, saved the example as /tmp/test.qml
and ran it like so:

  phablet@ubuntu-phablet:/tmp$ qmlscene --desktop_file_hint=unity8
test.qml

When plugging in a bluetooth keyboard/mouse combo, I’m seeing the
following output:

QObject: Cannot create children for a parent that is in a different thread.
(Parent is QInputInfoManagerMir(0xae10e6ac), parent's thread is 
QThread(0x1612170), current thread is QThread(0x176c3f8)
qml: keyboard count: 0

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

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions

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

[Touch-packages] [Bug 1244869] Re: Unity home lens restricts results to only files after a search returning only files

2016-11-28 Thread Paweł Stołowski

I think the cause of this problem are filters, they are apparently not
reset correctly in this scenario. If you expand the filters on the 2nd
search and select Applications, it works as a workaround too.

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

Title:
  Unity home lens restricts results to only files after a search
  returning only files

Status in unity-scope-home package in Ubuntu:
  Confirmed

Bug description:
  After doing a search in the home lens (the one that returns both files
  and applications for a search), if your search returned files, then
  the next search will return files too, even if it should be returning
  applications.

  Steps to reproduce:

  1. Press the super key to bring up the dash
  2. Type a search query that will return only files
  3. Go away, perhaps by opening the file you searched for, or pressing the 
super key again
  4. Press the super key to bring up the dash
  5. Replace the previous search term with a search query that should return 
applications
  6. Notice that it actually returns only files

  I expected the 2nd search to return applications (and maybe files) --
  but certainly not just files.

  The workaround is to delete the search query before beginning to type
  to replace the search term.

  I have a video showing the error. Let's see if I can attach it...

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-scope-home 6.8.2+13.10.20131003-0ubuntu1
  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.1
  Architecture: amd64
  Date: Sat Oct 26 01:31:47 2013
  InstallationDate: Installed on 2013-01-12 (286 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: unity-scope-home
  UpgradeStatus: Upgraded to saucy on 2013-10-23 (2 days ago)

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

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

[Touch-packages] [Bug 1645257] [NEW] bluetoothd does not notice udev-induced device name change

2016-11-28 Thread Tobias Wolter

Public bug reported:

Cheers,

using Ubuntu 16.10 and bluez 5.41-0ubuntu3 from yakkety, using Bluetooth
NAP functionality to connect a device via the system's network connect
fails because udev renames the device when it is registered and
bluetoothd fails to realize that:

Nov 28 10:26:21 fenrir kernel: bluetooth hci0:256 enx340286443693: renamed from 
bnep0
Nov 28 10:26:21 fenrir bluetoothd[2224]: bnep: Can't add bnep0 to the bridge 
pan1: No such device(19)
Nov 28 10:26:21 fenrir bluetoothd[2224]: BNEP server cannot be added

Expected results would, of course, be "added enx340286443693 to the
bridge pan1".

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

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

Title:
  bluetoothd does not notice udev-induced device name change

Status in bluez package in Ubuntu:
  New

Bug description:
  Cheers,

  using Ubuntu 16.10 and bluez 5.41-0ubuntu3 from yakkety, using
  Bluetooth NAP functionality to connect a device via the system's
  network connect fails because udev renames the device when it is
  registered and bluetoothd fails to realize that:

  Nov 28 10:26:21 fenrir kernel: bluetooth hci0:256 enx340286443693: renamed 
from bnep0
  Nov 28 10:26:21 fenrir bluetoothd[2224]: bnep: Can't add bnep0 to the bridge 
pan1: No such device(19)
  Nov 28 10:26:21 fenrir bluetoothd[2224]: BNEP server cannot be added

  Expected results would, of course, be "added enx340286443693 to the
  bridge pan1".

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

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

[Touch-packages] [Bug 1639568] Re: dnsmasq not updated by NetworkManager on system resume

2016-11-28 Thread Rene Mayrhofer

I have the same issue when e.g.:
- switching from Ethernet (via a USB-to-Ethernet adapter) and WiFi
- turning on or off a VPN managed by NetworkManager (openvpn configured 
manually does not have the issue)

My current workaround is to killall dnsmasq as root. It will re-start
automatically with the updated settings.

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

Title:
  dnsmasq not updated by NetworkManager on system resume

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When the system resumes after sleep dnsmasq is either not updated with
  new dns information of never resumes operation.  Restarting the
  network-manager service will manually resolve the problem.  Everything
  else seems correct, the DHCP information is correct and shows the
  correct nameservers, resolv.conf is updated correctly.  I am unable to
  determine if the issue is with dnsmasq not resuming or if the dbus
  message with the name servers is getting lost.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov  6 07:24:44 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev wlp58s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.218  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
The_Magical_Mystery_Tour  4e4fe235-20a0-414a-8ec3-97f65060250e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --  
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1639568] Re: dnsmasq not updated by NetworkManager on system resume

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  dnsmasq not updated by NetworkManager on system resume

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When the system resumes after sleep dnsmasq is either not updated with
  new dns information of never resumes operation.  Restarting the
  network-manager service will manually resolve the problem.  Everything
  else seems correct, the DHCP information is correct and shows the
  correct nameservers, resolv.conf is updated correctly.  I am unable to
  determine if the issue is with dnsmasq not resuming or if the dbus
  message with the name servers is getting lost.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov  6 07:24:44 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev wlp58s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.218  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
The_Magical_Mystery_Tour  4e4fe235-20a0-414a-8ec3-97f65060250e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --  
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices

I successfully ran the test case against ubuntu20.9 in -proposed. I also
verified that using losetup and mount on loop devices still works:

$ sudo losetup -f --show debian-stretch-DI-alpha7-amd64-netinst.iso 
/dev/loop0
$ sudo mount /dev/loop0 /mnt
mount: block device /dev/loop0 is write-protected, mounting read-only
$ ls /mnt
autorun.inf  debian [...]

With the -proposed version, losetup -f also succeeds to use /dev/loop-
control, so you can do the above a few times and it works with
/dev/loop12 too. When moving /dev/loop-control out of the way, the above
also works up to loop7, and then errors out with "losetup: could not
find any free loop device" as expected. "losetup -a" correctly shows the
bound devices/files.


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

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

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

Title:
  [trusty] mount -o loop is limited to 8 loop devices

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Trusty:
  Fix Committed

Bug description:
  trusty has a very old util-linux which does not yet know about /dev
  /loop-control to create arbitrarily many loop devices. This feature
  was introduced in Linux 3.1 already (i. e. before precise even). This
  is a showstopper for backporting snappy as that needs a lot of loop
  mounts.

  Support for loop-control got introduced later util-linux versions, but
  backporting full support for it (for losetup) is too intrusive. We
  only need a partial backport for "mount -o loop".

  SRU TEST CASE:
  First, use up all default 8 loop devices:
  $ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done

  Now try to use a 9th:
  $ dd if=/dev/zero of=/tmp/img bs=1M count=50
  $ mkfs.ext2 -F /tmp/img
  $ sudo mount -o loop /tmp/img /mnt

  With current trusty's "mount" package this will fail with "could not
  find any free loop device". With the proposed version, this should
  succeed, and "sudo losetup -a" should show "/dev/loop8: ...
  (/tmp/img)".

  Now, reboot, disable loop-control with

    sudo mv /dev/loop-control{,.disabled}

  and run the test case again. Now "mount -o loop" should fail with
  "could not find any free loop device" (as before). Ensure that there
  are no hangs, infinite loops, etc.

  ADDITIONAL REGRESSION CHECKING TEST CASES

  1. Check that every type of losetup call documented in the losetup
  manpage still works correctly.

  2. Check that mount and umount commands that use loop devices still
  work correctly.

  REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-
  linux support has exited for a long time without known/major issues,
  so this should be fairly safe. Also, the patch falls back to the
  previous "iterate over loop0 to loop7" behaviour if loop-control is
  not available.

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

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

[Touch-packages] [Bug 1644595] Re: krb5-1.13.2+dfsg-5 source contains source subject to the aladdin license

Hi,
thank you for your report on this - I must admit I'm not an expert on this.
I checked the actually delivered binaries do not contain any reference - as you 
outlined this is due to the respective file only being for win support.

In what extend the file being (unused) in the source is a violation I have no 
idea.
We likely want to drop or mention it in Debian and Ubuntu the same way.
I'll ask more developers how to proceed here.

Thank you!

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

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

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

Title:
  krb5-1.13.2+dfsg-5 source contains source subject to the aladdin
  license

Status in krb5 package in Ubuntu:
  Confirmed

Bug description:
  The krb5-1.13.2+dfsg-5 package source contains a file autolock.hxx  in
  the directory
  
krb5-1.13.2+dfsg-5\krb5_1.13.2+dfsg.orig\krb5-1.13.2+dfsg\src\ccapi\common\win\OldCC.
  Although not declared in any other licensing file for this package the
  file contains comments indicating its subject to the Aladdin license
  which has implications for any commercial distribution of the
  software, specifically:

  “2(a) Distribution of the Program or any work based on the Program by
  a commercial organization to any third party is prohibited if any
  payment is made in connection with such distribution, whether directly
  (as in payment for a copy fo the Program) or indirectly (as in payment
  for some service related to the Program, or payment for some product
  or service that includes a copy of the Program ‘without charge’ . . .”

  This file clearly is not needed or used for any Linux build as it
  appears specific to windows.

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

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

[Touch-packages] [Bug 1644572] Re: package init 1.29ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

Hi,

Usually people are recommending to uninstall and reinstall the package.
That is harder to do on init.

But you could try to do:
$ sudo apt-get --reinstall install init

I wonder as it is just an almost empty package where not that much should be 
able to break, but to be sure If the former doesn't help could you report back 
with the output of these commands:
$ dpkg -s init
$ dpkg --verify init
$ debconf-show init
$ dpkg -L init


Note - that might be related from the log:
Nov 24 19:57:37 hostname org.debian.apt[662]: 
/usr/lib/python3/dist-packages/aptdaemon/progress.py:491: Warning: Source ID 95 
was not found when attempting to remove it
Nov 24 19:57:37 hostname org.debian.apt[662]:   GLib.source_remove(id)
Nov 24 19:57:37 hostname org.debian.apt[662]: 
/usr/lib/python3/dist-packages/aptdaemon/progress.py:491: Warning: Source ID 96 
was not found when attempting to remove it
Nov 24 19:57:37 hostname org.debian.apt[662]:   GLib.source_remove(id)
Nov 24 19:57:37 hostname org.debian.apt[662]: 
/usr/lib/python3/dist-packages/aptdaemon/progress.py:491: Warning: Source ID 99 
was not found when attempting to remove it
Nov 24 19:57:37 hostname org.debian.apt[662]:   GLib.source_remove(id)
Nov 24 19:57:37 hostname org.debian.apt[662]: 
/usr/lib/python3/dist-packages/aptdaemon/progress.py:491: Warning: Source ID 
100 was not found when attempting to remove it
Nov 24 19:57:37 hostname org.debian.apt[662]:   GLib.source_remove(id)


** Changed in: init-system-helpers (Ubuntu)
   Status: New => Incomplete

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

Title:
  package init 1.29ubuntu3 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in init-system-helpers package in Ubuntu:
  Incomplete

Bug description:
  Cannot install any new packages, broke init

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: init 1.29ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Nov 24 19:57:35 2016
  DpkgTerminalLog:
   dpkg: error processing package init (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-11-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: init-system-helpers
  Title: package init 1.29ubuntu3 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1644572/+subscriptions

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

[Touch-packages] [Bug 1615044] Re: "unmanaged-devices=" lists misbehaves with "except:"

** Changed in: network-manager (Ubuntu)
 Assignee: Martin Pitt (pitti) => (unassigned)

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

Title:
  "unmanaged-devices=" lists misbehaves with "except:"

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  In yakkety we now ship /usr/lib/NetworkManager/conf.d/10-globally-
  managed-devices.conf with

 unmanaged-devices=*,except:type:wifi,except:type:wwan

  but this now breaks conf.d snippets which want to blacklist an
  additional interface, such as /run/NetworkManager/conf.d/test-
  blacklist.conf that does

unmanaged-devices+=wlan0

  resulting in

  # NetworkManager --print-config
  [...]
  unmanaged-devices=*,except:type:wifi,except:type:wwan,wlan0

  Intuitively this should ignore wlan0 and all other non-wifi/wwan
  devices, but with that it *does* manage wlan0.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.2-0ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: i3
  Date: Fri Aug 19 18:23:02 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   
   source-directory interfaces.d
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile,ofono
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

** Changed in: init-system-helpers (Ubuntu Xenial)
 Assignee: Martin Pitt (pitti) => (unassigned)

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

Title:
  output of invoke-rc.d for systemd units un-debuggable on failure

Status in init-system-helpers package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  Triaged

Bug description:
  When invoke-rc.d is called on a systemd system, if the unit fails to
  start, you get output like:

  Created symlink 
/etc/systemd/system/multi-user.target.wants/openafs-fileserver.service → 
/lib/systemd/system/openafs-fileserver.service.
  Job for openafs-fileserver.service failed because the control process exited 
with error code.
  See "systemctl status openafs-fileserver.service" and "journalctl -xe" for 
details.
  invoke-rc.d: initscript openafs-fileserver, action "start" failed.
  dpkg: error processing package openafs-fileserver (--configure):
   subprocess installed post-installation script returned error exit status 1

  The output shown here comes from systemctl itself, and is usually
  fine.  The admin who ran systemctl can run those other commands to
  debug.

  However, when called by invoke-rc.d, this output is usually seen only
  in a log file; maybe submitted in a bug report, maybe attached to
  something like an autopkgtest:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/armhf/o/openafs/20160624_174535@/log.gz

  By the time someone looks at this log output, it is often too late to
  run those commands in order to debug the failure.

  invoke-rc.d should call these commands for us on systemd unit failure,
  so that the relevant debugging information is included in the log
  where it can help.

  We don't want to call 'journalctl -xe', which might leak information
  into the log from other jobs, but 'journalctl -x -u ' may
  be appropriate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1596056/+subscriptions

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

[Touch-packages] [Bug 1579130] Re: need to support renaming of devices in container and on first boot

** Changed in: systemd (Ubuntu)
 Assignee: Martin Pitt (pitti) => (unassigned)

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

Title:
  need to support renaming of devices in container and on first boot

Status in cloud-init package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
  We're interested in supporting network configuration of cloud
  instances including lxc containers via maas/cloud-init yaml format.

  For Containers, the end goal is to do:
  $ lxc init xenial x1
  $ ncpath=/var/lib/cloud/seed/nocloud-net/network-config
  $ sudo tee /var/lib/lxd/containers/x1/rootfs/$ncpath < 
into 'eth0').
   That is implemented by check of 
/sys/devices/virtual/net/eth0/name_assign_type . Value of 4 means renamed.

   c.) systemd.link will not attempt to rename a device that does not have a 
driver.
     To see that run: udevadm test-builtin net_setup_link /sys/class/net/eth0
     http://paste.ubuntu.com/16261974/

   d.) on first boot of a cloud instance, the systemd.link files in the
  initramfs are either pristine or from the previous instance.  The
  devices will leave the initramfs either named incorrectly or named
  with standard persistent naming and will have already been renamed.

  To force these systemd.link files to run in spite of 'b' on kvm guests
  or bare metal, we have found that unbind and rebind of the device will
  clear the state and rename would occur.  that can be done as shown in
  https://bugs.launchpad.net/ubuntu/+source/cloud-
  init/+bug/1577844/comments/3 but since there is no 'driver' we cannot
  unbind and rebind veth devices.

  To do this right, we need to support:
   1.) renaming on first boot with initramfs and with 'stale' initramfs
   2.) renaming in lxc containers
   3.) user updating whatever files or mechanism is used post first boot.  For 
example, if the user wrote a 25-my-rules.link after first boot, a reboot should 
prefer their provided names to whatever were originally there.
   4.) if cloud-init networking is disabled, the renaming should not occur.

  Related Bugs:
   * bug 1594546: no need to write systemd.link files 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri May  6 15:42:52 2016
  MachineType: LENOVO 33672B7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=19ac97d5-6973-4193-9a09-2e6bbfa38262 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G8ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 33672B7
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG8ET96WW(2.56):bd12/18/2013:svnLENOVO:pn33672B7:pvrThinkPadX131e:rvnLENOVO:rn33672B7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 33672B7
  dmi.product.version: ThinkPad X131e
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1446537] Re: apport hook fails in add_info with TypeError: 'str' does not support the buffer interface

** Changed in: apport (Ubuntu)
 Assignee: Martin Pitt (pitti) => (unassigned)

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

Title:
  apport hook fails in add_info with TypeError: 'str' does not support
  the buffer interface

Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Xenial:
  In Progress

Bug description:
  on vivid

  ⟫ ubuntu-bug ubiquity
  dpkg-query: aucun paquet ne correspond à ubiquity
  ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 61, in 
add_info
  if 'Buffer I/O error on device' in syslog:
  TypeError: 'str' does not support the buffer interface

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 21 10:15:56 2015
  InstallationDate: Installed on 2013-09-03 (594 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1545707] Re: Error message "Operation failed: No such file or directory" on installing/reconfiguring systemd

** Changed in: systemd (Ubuntu)
 Assignee: Martin Pitt (pitti) => (unassigned)

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

Title:
  Error message "Operation failed: No such file or directory" on
  installing/reconfiguring systemd

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 16.04 dev with systemd 229-1ubuntu2 and on
  installing/reconfiguring it I'm getting this output (the first error
  has already its own bug report here:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1475094 ):

  root@ubuntu:~# dpkg-reconfigure systemd
  addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
  Operation failed: No such file or directory

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

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

[Touch-packages] [Bug 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction

** Changed in: systemd (Ubuntu)
 Assignee: Martin Pitt (pitti) => (unassigned)

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

Title:
  IdleAction=suspend specified in logind.conf must systematically be
  inhibited during user interaction

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I want my computer to suspend when there is NO opened user session.

  So, I have activated following lines inside '/etc/systemd/logind.conf' :
  IdleAction=suspend
  IdleActionSec=15min

  -  Systematically , under Ubuntu Vivid (15.04), this works correctly :
 During user interaction, the computer does NOT automatically suspend, but 
stays continuously alive.
 Once all users have closed their session, the computer automatically 
suspends after 15 min.

  -  But systematically , under Ubuntu Wily (15.10 beta2), the computer 
automatically suspends after 15 min EVEN during user interaction.
 Hitting the keyboard makes the computer resume without data loss, but this 
is still annoying.
 In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must 
systematically be inhibited during user interaction.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z_admin1665 F pulseaudio
   /dev/snd/controlC1:  z_admin1665 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Oct  8 19:26:59 2015
  HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140
  InstallationDate: Installed on 2015-09-27 (10 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.149
  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: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 1620780] Re: dev-sda2.device job running and times out

There is some chance that this got fixed with
https://github.com/systemd/systemd/commit/c5a97ed1

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

Title:
  dev-sda2.device job running and times out

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ lxc launch ubuntu-daily:yakkety y4
  $ lxc exec y3 -- systemctl list-jobs
  JOB UNITTYPE  STATE  
5 dev-sda2.device start running

  1 jobs listed.

  $ lxc exec y3 -- cat /etc/cloud/build.info 
  build_name: server
  serial: 20160902

  $ lxc exec y3 -- systemd-analyze
  Startup finished in 1min 30.373s (userspace) = 6d 2h 27min 41.963s

  
  $ lxc exec y3 -- journalctl > yakkety-lxd-journalctl.txt

  $ lxc exec y3 -- systemctl status dev-sda2.device
  ● dev-sda2.device
 Loaded: loaded
 Active: activating (tentative) since Tue 2016-09-06 18:38:31 UTC; 4min 39s 
ago

  Sep 06 18:40:01 y3 systemd[1]: dev-sda2.device: Job dev-sda2.device/start 
timed out.
  Sep 06 18:40:01 y3 systemd[1]: Timed out waiting for device dev-sda2.device.
  Sep 06 18:40:01 y3 systemd[1]: dev-sda2.device: Job dev-sda2.device/start 
failed with result 'timeout'.
  Warning: Journal has been rotated since unit was started. Log output is 
incomplete or unavailable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep  6 18:38:48 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic.efi.signed 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1274115] Re: snd_pcm_avail() returned a value that is exceptionally large

2016-11-28 Thread jonnieo

I have the same bug. Lenovo X1 yoga. Laptop becomes completely
unresponsive. Anyone found a way out?

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

Title:
  snd_pcm_avail() returned a value that is exceptionally large

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sometimese sound begins stutter while listen to music or watching youtube. In 
syslog I see:
  Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] 
alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 
866944 bytes (4914 ms).
  Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. 
Please report this issue to the ALSA developers.

  I'm using Kubuntu 13.10
  $ uname -a
  Linux bazilio-laptop 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux
  $ kde4-config --version
  Qt: 4.8.4
  KDE Development Platform: 4.12.0
  kde4-config: 1.0
  $ pulseaudio --version
  pulseaudio 4.0
  $ alsactl --version
  alsactl version 1.0.27.1

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

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

[Touch-packages] [Bug 1274115] Re: snd_pcm_avail() returned a value that is exceptionally large

2016-11-28 Thread jonnieo

More info: I have the same bug. Lenovo X1 yoga. Laptop becomes
completely unresponsive. ubuntu 16.04, kernel 4.4.0-47-generic, pulsaudo

 Anyone found a way out?

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

Title:
  snd_pcm_avail() returned a value that is exceptionally large

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sometimese sound begins stutter while listen to music or watching youtube. In 
syslog I see:
  Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] 
alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 
866944 bytes (4914 ms).
  Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. 
Please report this issue to the ALSA developers.

  I'm using Kubuntu 13.10
  $ uname -a
  Linux bazilio-laptop 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux
  $ kde4-config --version
  Qt: 4.8.4
  KDE Development Platform: 4.12.0
  kde4-config: 1.0
  $ pulseaudio --version
  pulseaudio 4.0
  $ alsactl --version
  alsactl version 1.0.27.1

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

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

[Touch-packages] [Bug 1644595] Re: krb5-1.13.2+dfsg-5 source contains source subject to the aladdin license

I cannot find the license claim mentioned. In the source for krb5
1.13.2+dfsg-5, I see src/ccapi/common/win/OldCC/autolock.hxx but it
appears to have a regular MIT-style license boilerplate. It has
sha256sum
02d63ce54f142101910143464f9eea3935f7d478e4e32998f5ba02cf8ffddc61. I also
grepped for Aladdin (case insenstive) and nothing came up. Are you sure
you don't have some local filesystem corruption or something like that?
Can you confirm with "pull-lp-source" on a different system that you can
pull the source file with the license you found, and provide the top
line of the debian/changelog file in that source tree?

Marking Incomplete as I cannot find any evidence of a license problem in
the source itself.

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

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

Title:
  krb5-1.13.2+dfsg-5 source contains source subject to the aladdin
  license

Status in krb5 package in Ubuntu:
  Confirmed

Bug description:
  The krb5-1.13.2+dfsg-5 package source contains a file autolock.hxx  in
  the directory
  
krb5-1.13.2+dfsg-5\krb5_1.13.2+dfsg.orig\krb5-1.13.2+dfsg\src\ccapi\common\win\OldCC.
  Although not declared in any other licensing file for this package the
  file contains comments indicating its subject to the Aladdin license
  which has implications for any commercial distribution of the
  software, specifically:

  “2(a) Distribution of the Program or any work based on the Program by
  a commercial organization to any third party is prohibited if any
  payment is made in connection with such distribution, whether directly
  (as in payment for a copy fo the Program) or indirectly (as in payment
  for some service related to the Program, or payment for some product
  or service that includes a copy of the Program ‘without charge’ . . .”

  This file clearly is not needed or used for any Linux build as it
  appears specific to windows.

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

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

** Changed in: systemd (Ubuntu Xenial)
 Assignee: Martin Pitt (pitti) => (unassigned)

-- 
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 systemd package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in cloud-init source package in Yakkety:
  New
Status in systemd source package in Yakkety:
  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 
(for xenial only) drop the useless org.freedesktop.network1.busname unit (which 
is always "condition failed" as there is no kdbus, but it moves 
systemd-network.service after sockets.target which is too late for c

[Touch-packages] [Bug 1644595] Re: krb5-1.13.2+dfsg-5 source contains source subject to the aladdin license

I'm sorry, my mistake. I see what you mean now. It's "Alladin Free
Public License", is mentioned in the boilerplate, but the associated
copy of the license doesn't appear to be included.

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

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

Title:
  krb5-1.13.2+dfsg-5 source contains source subject to the aladdin
  license

Status in krb5 package in Ubuntu:
  Confirmed

Bug description:
  The krb5-1.13.2+dfsg-5 package source contains a file autolock.hxx  in
  the directory
  
krb5-1.13.2+dfsg-5\krb5_1.13.2+dfsg.orig\krb5-1.13.2+dfsg\src\ccapi\common\win\OldCC.
  Although not declared in any other licensing file for this package the
  file contains comments indicating its subject to the Aladdin license
  which has implications for any commercial distribution of the
  software, specifically:

  “2(a) Distribution of the Program or any work based on the Program by
  a commercial organization to any third party is prohibited if any
  payment is made in connection with such distribution, whether directly
  (as in payment for a copy fo the Program) or indirectly (as in payment
  for some service related to the Program, or payment for some product
  or service that includes a copy of the Program ‘without charge’ . . .”

  This file clearly is not needed or used for any Linux build as it
  appears specific to windows.

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

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

[Touch-packages] [Bug 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers

** Changed in: resolvconf (Ubuntu)
 Assignee: Martin Pitt (pitti) => Canonical Foundations Team 
(canonical-foundations)

** Changed in: resolvconf (Ubuntu)
Milestone: ubuntu-16.11 => ubuntu-16.12

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

Title:
  resolv.conf for resolved stub server should have a comment how to see
  the actual servers

Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  resolv.conf currently just has

nameserver 127.0.0.53

  with resolved (its local stub resolver). We should have an extra
  comment on top of that that says

# systemd-resolved stub resolver; run "systemd-resolve --status" to
  see the actual name servers

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

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

[Touch-packages] [Bug 1620780] Re: dev-sda2.device job running and times out

Indeed this does not happen any more with the upstream master build from
https://launchpad.net/~pitti/+archive/ubuntu/systemd/+packages, so 233
will fix this.

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

Title:
  dev-sda2.device job running and times out

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  $ lxc launch ubuntu-daily:yakkety y4
  $ lxc exec y3 -- systemctl list-jobs
  JOB UNITTYPE  STATE  
5 dev-sda2.device start running

  1 jobs listed.

  $ lxc exec y3 -- cat /etc/cloud/build.info 
  build_name: server
  serial: 20160902

  $ lxc exec y3 -- systemd-analyze
  Startup finished in 1min 30.373s (userspace) = 6d 2h 27min 41.963s

  
  $ lxc exec y3 -- journalctl > yakkety-lxd-journalctl.txt

  $ lxc exec y3 -- systemctl status dev-sda2.device
  ● dev-sda2.device
 Loaded: loaded
 Active: activating (tentative) since Tue 2016-09-06 18:38:31 UTC; 4min 39s 
ago

  Sep 06 18:40:01 y3 systemd[1]: dev-sda2.device: Job dev-sda2.device/start 
timed out.
  Sep 06 18:40:01 y3 systemd[1]: Timed out waiting for device dev-sda2.device.
  Sep 06 18:40:01 y3 systemd[1]: dev-sda2.device: Job dev-sda2.device/start 
failed with result 'timeout'.
  Warning: Journal has been rotated since unit was started. Log output is 
incomplete or unavailable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep  6 18:38:48 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic.efi.signed 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1641272] Re: Debug symbols package doesnt exist

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Setting Importance to Low as this only impacts developers.

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

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

Title:
  Debug symbols package doesnt exist

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  On Yakkery with ddebs repos enabled there is no debug packages for
  dnsmasq

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

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

[Touch-packages] [Bug 1641272] Re: Debug symbols package doesnt exist

(patches welcome!)

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

Title:
  Debug symbols package doesnt exist

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  On Yakkery with ddebs repos enabled there is no debug packages for
  dnsmasq

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

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

[Touch-packages] [Bug 1641372] Re: Upgrade to 16.04 failed.

Thank you for your report.

You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community

If it turns out that your issue is a bug in Ubuntu, then we need a full
bug report please. Until then, we can't make any progress on this
report, and you won't find many people who can help you here - we have
better venues where there is a community willing to help - see the link
above.

If you believe that this is really a bug, then you may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

** Changed in: init-system-helpers (Ubuntu)
   Status: New => Incomplete

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

Title:
  Upgrade to 16.04 failed.

Status in init-system-helpers package in Ubuntu:
  Incomplete

Bug description:
  I ran an upgrade package from terminal mode in 14.04.2.  i am now at
  14.04.5 but GUI does not work. my system is 7 years old and started
  with ubuntu 9.1. system works in 14.04.5 in terminal mode. ctrl-alt-f7
  makes the screen go black.  i think i have no drivers for the NVidea.
  What is the best supported video card? I want to try another video
  card with the best driver support.  i ordered a 16.04 boot usb.  this
  will not arrive for a month.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1641372/+subscriptions

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

[Touch-packages] [Bug 1645308] [NEW] [SRU] Backport zeromq3 4.2.0 to yakkety

2016-11-28 Thread Łukasz Zemczak

Public bug reported:

[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.

** Affects: zeromq3 (Ubuntu)
 Importance: Medium
 Status: Fix Released

** Affects: zeromq3 (Ubuntu Yakkety)
 Importance: Medium
 Assignee: Łukasz Zemczak (sil2100)
 Status: In Progress

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

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

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

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

** Changed in: zeromq3 (Ubuntu Yakkety)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

-- 
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:
  In Progress

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 1644595] Re: krb5-1.13.2+dfsg-5 source contains source subject to the aladdin license

Reported to Debian as that is an issue we share, linked the deb-bug
here.

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

** Also affects: kerberos via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846088
   Importance: Unknown
   Status: Unknown

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

Title:
  krb5-1.13.2+dfsg-5 source contains source subject to the aladdin
  license

Status in Kerberos:
  Unknown
Status in krb5 package in Ubuntu:
  Confirmed

Bug description:
  The krb5-1.13.2+dfsg-5 package source contains a file autolock.hxx  in
  the directory
  
krb5-1.13.2+dfsg-5\krb5_1.13.2+dfsg.orig\krb5-1.13.2+dfsg\src\ccapi\common\win\OldCC.
  Although not declared in any other licensing file for this package the
  file contains comments indicating its subject to the Aladdin license
  which has implications for any commercial distribution of the
  software, specifically:

  “2(a) Distribution of the Program or any work based on the Program by
  a commercial organization to any third party is prohibited if any
  payment is made in connection with such distribution, whether directly
  (as in payment for a copy fo the Program) or indirectly (as in payment
  for some service related to the Program, or payment for some product
  or service that includes a copy of the Program ‘without charge’ . . .”

  This file clearly is not needed or used for any Linux build as it
  appears specific to windows.

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

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

[Touch-packages] [Bug 1612224] Re: [17.04 FEAT] Extend cpu topology to support drawers

2016-11-28 Thread Heinz-Werner Seeck

** Summary changed:

- [16.10 FEAT] Extend cpu topology to support drawers
+ [17.04 FEAT] Extend cpu topology to support drawers

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

Title:
  [17.04 FEAT] Extend cpu topology to support drawers

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New

Bug description:
  kernel 4.8: Add support for the additional scheduling layer within the
  kernel and util-linux.

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

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

[Touch-packages] [Bug 1612224] Re: [17.04 FEAT] Extend cpu topology to support drawers

2016-11-28 Thread bugproxy

--- Comment From heinz-werner_se...@de.ibm.com 2016-11-28 07:53 EDT---
Change target to 17.04 where util-linux 2.29 is already included. Which 
completes the funtionallity

** Tags removed: targetmilestone-inin1610
** Tags added: targetmilestone-inin1704

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

Title:
  [17.04 FEAT] Extend cpu topology to support drawers

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New

Bug description:
  kernel 4.8: Add support for the additional scheduling layer within the
  kernel and util-linux.

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

-- 
Mailing list: https://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 1641372] Re: Upgrade to 16.04 failed.

2016-11-28 Thread George Marlatt

Thankyou.
I upgraded successfully by downloading a 16.04 boot disk.  Burned a CD on
my microsoft system and upgraded painlessly.
Ubuntu has been running flawlessly on my AMD - ASUS since 2009.
George Marlatt

On Nov 28, 2016 7:21 AM, "Robie Basak" <1641...@bugs.launchpad.net>
wrote:

> Thank you for your report.
>
> You can find pointers to get help for this sort of problem here:
> http://www.ubuntu.com/support/community
>
> If it turns out that your issue is a bug in Ubuntu, then we need a full
> bug report please. Until then, we can't make any progress on this
> report, and you won't find many people who can help you here - we have
> better venues where there is a community willing to help - see the link
> above.
>
> If you believe that this is really a bug, then you may find it helpful
> to read "How to report bugs effectively"
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
> if you would then provide a more complete description of the problem,
> explain why you believe this is a bug in Ubuntu rather than a problem
> specific to your system, and then change the bug status back to New.
>
> ** Changed in: init-system-helpers (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1641372
>
> Title:
>   Upgrade to 16.04 failed.
>
> Status in init-system-helpers package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I ran an upgrade package from terminal mode in 14.04.2.  i am now at
>   14.04.5 but GUI does not work. my system is 7 years old and started
>   with ubuntu 9.1. system works in 14.04.5 in terminal mode. ctrl-alt-f7
>   makes the screen go black.  i think i have no drivers for the NVidea.
>   What is the best supported video card? I want to try another video
>   card with the best driver support.  i ordered a 16.04 boot usb.  this
>   will not arrive for a month.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/init-system-
> helpers/+bug/1641372/+subscriptions
>

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

Title:
  Upgrade to 16.04 failed.

Status in init-system-helpers package in Ubuntu:
  Incomplete

Bug description:
  I ran an upgrade package from terminal mode in 14.04.2.  i am now at
  14.04.5 but GUI does not work. my system is 7 years old and started
  with ubuntu 9.1. system works in 14.04.5 in terminal mode. ctrl-alt-f7
  makes the screen go black.  i think i have no drivers for the NVidea.
  What is the best supported video card? I want to try another video
  card with the best driver support.  i ordered a 16.04 boot usb.  this
  will not arrive for a month.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1641372/+subscriptions

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

[Touch-packages] [Bug 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

2016-11-28 Thread Adam Boyhan

I can confirm that I have this issue in a ubuntu based OS (proxmox).  I
have the hardware, is there anything I can do to help resolve this
issue?

Setting up /etc/network/interfaces with the "no-auto-down" option
doesn't help, it prevents the interface from coming up all together.

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

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058889]  [] 
br_dev_delete+0x42/0xb0 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058895]  [] 
br_del_bridge+0x4a/0x70 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058911]  [] 
br_ioctl_deviceless_stub+0x153/0x230 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058984]  [] ? 
secur

[Touch-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Hi Richard,

Thanks for updating the bug with Dave's latest suggestion in order to
isolate this particular situation.

We will come back to you soon with the next steps.

Regards,
Eric

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

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions 
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

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

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

[Touch-packages] [Bug 1608965] Re: ssh GSSAPI rekey failure

> Any news on handling this bug?

Sorry, this is deep in the backlog and I don't expect Ubuntu developers
to look into this any time soon on a volunteer basis.

I suggest that you try the latest upstream openssh release, and if it is
still an issue there, then raise the bug upstream if it hasn't been
reported already.

If it is fixed in the latest upstream release, then if you could
identify the fix then we can do something about it in Ubuntu.

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

Title:
  ssh GSSAPI rekey failure

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  If I have ssh set up using GSSAPI with rekeying enabled, then the
  connection fails on rekey, and tries to do host-based verification
  'mid-session'.

  Steps to reproduce:

  $ ssh -vvv server.example.com
  
  debug1: Authenticating to ssh.example.com:22 as 'user'
  
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-A/vxljAEU54gt9a48EiANQ==,gss-group1-sha1-A/vxljAEU54gt9a48EiANQ==,gss-group14-sha1-A/vxljAEU54gt9a48EiANQ==,gss-gex-sha1-bontcUwnM6aGfWCP21alxQ==,gss-group1-sha1-bontcUwnM6aGfWCP21alxQ==,gss-group14-sha1-bontcUwnM6aGfWCP21alxQ==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group1-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q==,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
  
  debug2: peer server KEXINIT proposal
  debug2: KEX algorithms: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
  
  Last login: Tue Aug 02 10:47:20 2016 from foo

  # Then do 'kinit' on the client to get a new ticket...

  debug1: need rekeying
  debug1: SSH2_MSG_KEXINIT sent
  debug1: rekeying in progress
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1
  debug2: host key algorithms: 
ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa,null
  [...]
  debug2: peer server KEXINIT proposal
  debug2: KEX algorithms: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
  [...]
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: rekeying in progress
  debug1: rekeying in progress
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:w7yxbCZNBX4d5EAgmCrFYa3XUpDjvWiDOw4/YOY9q8E
  The authenticity of host 'server.example.com (10.0.0.1)' can't be established.
  ECDSA key fingerprint is SHA256:w7yxbCZNBX4d5EAgmCrFYa3XUpDjvWiDOw4/YOY9q8E.
  Are you sure you want to continue connecting (yes/no)? 
  Host key verification failed.

  It looks like the list of KEX algorithms differs between the initial
  connection, and the rekeying.

  This behaviour seems to occur with a client running 16.04 (openssh-
  client 1:7.2p2-4ubuntu1) but not on 15.10 (openssh-client
  1:6.9p1-2ubuntu0.2).

  ssh_config is as follows:

  HashKnownHosts no
  GSSAPIAuthentication yes
  GSSAPIDelegateCredentials yes
  GSSAPIRenewalForcesRekey yes
  GSSAPITrustDNS yes
  GSSAPIKeyExchange yes
  ForwardX11 yes
  ForwardX11Trusted yes

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

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

[Touch-packages] [Bug 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

Based on the investigation so far, it seems to me that this is entirely
a kernel bug, and there is nothing required in the bridge-utils package
in order to fix this issue. So I'm marking this bug as Invalid for
bridge-utils. The kernel tasks remain open. If this is incorrect, please
explain why you expect to need a fix in bridge-utils and reopen that
task.

** Changed in: bridge-utils (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: bridge-utils (Ubuntu Xenial)
   Status: Confirmed => Invalid

** Changed in: bridge-utils (Ubuntu Yakkety)
   Status: Confirmed => Invalid

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

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Invalid

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 b

[Touch-packages] [Bug 1645332] [NEW] package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-11-28 Thread kobfa

Public bug reported:

not sure what I'm looking at. Please advise. Thanks.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
Uname: Linux 4.4.0-49-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CupsErrorLog:
 
Date: Mon Nov 21 08:41:19 2016
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2015-12-07 (357 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
KernLog:
 
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: LENOVO 2325BC7
Papersize: letter
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-49-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-49-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: cups
Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-08-04 (116 days ago)
dmi.bios.date: 09/11/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET82WW (2.02 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2325BC7
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: AG978241
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2325BC7:pvrThinkPadX230:rvnLENOVO:rn2325BC7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2325BC7
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
modified.conffile..etc.default.cups:
 # Cups configure options
 
 # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
 # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
 # LOAD_LP_MODULE=yes
mtime.conffile..etc.default.cups: 2015-08-05T00:18:48

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


** Tags: apport-package i386 need-duplicate-check package-from-proposed xenial

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  not sure what I'm looking at. Please advise. Thanks.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CupsErrorLog:
   
  Date: Mon Nov 21 08:41:19 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-12-07 (357 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  KernLog:
   
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 2325BC7
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-49-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-49-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (116 days ago)
  dmi.bios.date: 09/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET82WW (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325BC7
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: AG978241
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2325BC7:pvrThinkPadX230:rvnLENOVO:rn2325BC7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325BC7
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2015-08-05T00:18:48

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

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

[Touch-packages] [Bug 1645332] Re: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-11-28 Thread Till Kamppeter

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

** This bug has been marked a duplicate of bug 1642966
   package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  not sure what I'm looking at. Please advise. Thanks.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CupsErrorLog:
   
  Date: Mon Nov 21 08:41:19 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-12-07 (357 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  KernLog:
   
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 2325BC7
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-49-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-49-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (116 days ago)
  dmi.bios.date: 09/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET82WW (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325BC7
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: AG978241
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2325BC7:pvrThinkPadX230:rvnLENOVO:rn2325BC7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325BC7
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2015-08-05T00:18:48

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

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

[Touch-packages] [Bug 1612224] Re: [17.04 FEAT] Extend cpu topology to support drawers

2016-11-28 Thread Dimitri John Ledkov

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

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

Title:
  [17.04 FEAT] Extend cpu topology to support drawers

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  kernel 4.8: Add support for the additional scheduling layer within the
  kernel and util-linux.

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

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

[Touch-packages] [Bug 1645338] [NEW] package rsyslog 8.16.0-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-11-28 Thread Harald Engels

Public bug reported:

Rsyslog got removed for testing syslog-ng (in a quite fresh Ubuntu Mate
16.04 installation). This removes also the meta-package ubuntu-minimal
(why this nonsense?). But then syslog-ng got removed and rsyslog re-
installed. It seems that the installation of rsyslog fails then
repeatedly. The installation of ubuntu-minimal works (no rsyslog
installation errors) but after a reboot the starting of rsyslog fails
with the message that the installation failed.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: rsyslog 8.16.0-1ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Nov 28 11:20:45 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-11-27 (1 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: rsyslog
Title: package rsyslog 8.16.0-1ubuntu3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package rsyslog 8.16.0-1ubuntu3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Rsyslog got removed for testing syslog-ng (in a quite fresh Ubuntu
  Mate 16.04 installation). This removes also the meta-package ubuntu-
  minimal (why this nonsense?). But then syslog-ng got removed and
  rsyslog re-installed. It seems that the installation of rsyslog fails
  then repeatedly. The installation of ubuntu-minimal works (no rsyslog
  installation errors) but after a reboot the starting of rsyslog fails
  with the message that the installation failed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: rsyslog 8.16.0-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Nov 28 11:20:45 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-27 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: rsyslog
  Title: package rsyslog 8.16.0-1ubuntu3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1643467] Re: Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec

2016-11-28 Thread Amr Ibrahim

** Tags added: precise

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

Title:
  Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec

Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Confirmed

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22&redirect_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

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

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

[Touch-packages] [Bug 1610519] Re: apport-gtk crashes with segmentation fault

2016-11-28 Thread Niklas Edmundsson

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

** This bug has been marked a duplicate of bug 1574886
   All gtk applications Segfault if no GLX context is active

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

Title:
  apport-gtk crashes with segmentation fault

Status in apport package in Ubuntu:
  New

Bug description:
  apport-bug calling apport-gtk crashes with a segmentation fault.

  ~ $ lsb_release -rd
  Description: Ubuntu 16.04.1 LTS
  Release: 16.04
  ~ $ dpkg -l apport-gtk
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ NameVersion  Architecture 
Description
  
+++-===---
  ii  apport-gtk  2.20.1-0ubuntu2.1all  
GTK+ frontend for the apport crash report system

  
  This look related to #1610518.

  
  The backtrace from the core:

  ~ $ apport-bug 
  Segmentation fault (core dumped)
  ~ $ gdb64 /usr/bin/python3 core 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /usr/bin/python3...(no debugging symbols found)...done.

  warning: core file may not match specified executable file.
  [New LWP 4932]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

  warning: the debug information found in "/lib64/ld-2.23.so" does not
  match "/lib64/ld-linux-x86-64.so.2" (CRC mismatch).

  Core was generated by `/usr/bin/python3 /usr/share/apport/apport-gtk'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37

  warning: Source file is more recent than executable.
  37movdqu  (%rdi), %xmm0
  (gdb) backtrace full
  #0  rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37
  No locals.
  #1  0x7f89cc55bf22 in _IO_str_init_static_internal 
(sf=sf@entry=0x7ffc1fa72690, ptr=ptr@entry=0x0, size=size@entry=0, 
pstart=pstart@entry=0x0)
  at strops.c:41
  fp = 0x7ffc1fa72690
  end = 
  #2  0x7f89cc54ab67 in __GI___isoc99_vsscanf (string=0x0, 
format=0x7f89c5e972f2 "%d.%d", args=args@entry=0x7ffc1fa727b8) at 
isoc99_vsscanf.c:41
  ret = -863365216
  sf = {_sbf = {_f = {_flags = -72515584, _IO_read_ptr = 0x0, 
_IO_read_end = 0x0, _IO_read_base = 0x0, _IO_write_base = 0x0, 
_IO_write_ptr = 0x0, _IO_write_end = 0x0, _IO_buf_base = 0x0, 
_IO_buf_end = 0x0, _IO_save_base = 0x0, _IO_backup_base = 0x0, 
_IO_save_end = 0x0, _markers = 0x0, _chain = 0x0, _fileno = 0, 
_flags2 = 0, _old_offset = 71776119061217280, _cur_column = 0, 
_vtable_offset = 0 '\000', _shortbuf = "", _lock = 0x0, _offset 
= 0, _codecvt = 0x0, _wide_data = 0x, 
_freeres_list = 0x0, _freeres_buf = 0xff00ff00, __pad5 
= 18446462598732840960, _mode = -1, 
_unused2 = '\000' }, vtable = 0x7f89cc8a17a0 
<_IO_str_jumps>}, _s = {_allocate_buffer = 0x0, _free_buffer = 0x0}}
  #3  0x7f89cc54ab07 in __isoc99_sscanf (s=, 
format=) at isoc99_sscanf.c:31
  arg = 
  done = -863365216
  #4  0x7f89c5e79d22 in epoxy_glx_version () from 
/usr/lib/x86_64-linux-gnu/libepoxy.so.0
  No symbol table info available.
  #5  0x7f89c8b18509 in gdk_x11_screen_init_gl 
(screen=screen@entry=0xdf6160)
  at /build/gtk+3.0-6ZPWga/gtk+3.0-3.18.9/./gdk/x11/gdkglcontext-x11.c:774
  display = 0xdf1020
  display_x11 = 0xdf1020
  dpy = 0xde3800
  error_base = 172
  event_base = 104
  screen_num = 0
  #6  0x7f89c8b1882a in _gdk_x11_screen_update_visuals_for_gl 
(screen=screen@entry=0xdf6160)
  at /build/gtk+3.0-6ZPWga/gtk+3.0-3.18.9/./gdk/x11/gdkglcontext-x11.c:1114
  x11_screen = 0xdf6160
  display = 0xdf1020
  display_x11 = 0xdf1020

[Touch-packages] [Bug 1644757] Re: [MIR] liburcu

2016-11-28 Thread Scott Moser

I subscribed ubuntu-server to bug mail.

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

Title:
  [MIR] liburcu

Status in liburcu package in Ubuntu:
  New

Bug description:
  The coming merge of latest multipath-tools will add a dependency to
  liburcu.

  This was added upstream by:
 commit cb98c8837693a4a4f76895ff3e8c59bc3ba844ca
 Author: Hannes Reinecke 
 Date:   Tue Jun 14 16:36:30 2016 +0200
 multipathd: use userspace RCU to access configuration

  That is a non optional change (no configure selection or runtime detection).
  Patching out the locking of the project sounds like the most error prone 
thing I can think of, therefore I request a MIR for liburcu.

  
  Processing Main Inclusion Requirements:
  1. Availability: The package must already be in the Ubuntu universe, and must 
build for the architectures it is designed to work on.

  Last version fine since Xenial,former verisions go back til precise (not all 
archs) 
   liburcu1 | 0.6.7-2 | precise/universe | amd64, armhf, i386, powerpc
   liburcu1 | 0.7.12-0ubuntu2 | trusty   | amd64, arm64, armhf, i386, 
powerpc, ppc64el
   liburcu2 | 0.8.5-1ubuntu1  | vivid| amd64, arm64, armhf, i386, 
powerpc, ppc64el
   liburcu4 | 0.9.1-3 | xenial/universe | amd64, arm64, armhf, i386, powerpc, 
ppc64el, s390x
   liburcu4 | 0.9.2-3 | yakkety | amd64, arm64, armhf, i386, powerpc, 
ppc64el, s390x
   liburcu4 | 0.9.2-3 | zesty   | amd64, arm64, armhf, i386, powerpc, 
ppc64el, s390x

  
  2. The package is useful for a large part of our user base.
  => The package is a new build dependency or dependency of a package that we 
already support and in wide use by enterprise Ubuntu setups (multipath-tools).
  => The package helps meet a specific Blueprint goal (The merge of a more 
recent multipath-version in blueprint servercloud-z-server-core).

  
  3. Security.
  => So far the package never showed up in any of the links referred to by 
"Security Checks"
  => No Executables which have the suid or sgid bit set (no executables at all 
btw, so no /sbin, ...)
  => No services / daemons
  => No ports
  => no addon/plugin so far used directly by
  * gdnsd
  * glusterfs-common
  * knot
  * liblttng-ctl0
  * liblttng-ust-ctl2
  * liblttng-ust0
  * liburcu-dev
  * lttng-tools
  * netsniff-ng
  * python3-lttng
  None of these is especially security-sensitive software (filters, scanners, 
UI skins, etc) 

  
  4. Quality assurance
  => no config needed
  => no debconf
  => no long term outstanding bugs that matter (only one for precise which 
nobody seemed to care so far, but that is not crit at all)
  https://bugs.launchpad.net/ubuntu/+source/liburcu
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=liburcu
  => No special HW needs to be used
  => Comes with a unit test that is ran on build via dh_auto_test
  => it has a watch file

  
  5. UI standards
  => No user-facing application, so no UI/Translation needs

  
  6. Dependencies:
  => has only one Dependency to libc6, no suggests, recommends

  7. Standards compliance
  => No known FHS/Policy issues

  8. Maintenance
  => Well maintained in Debian, only a sync so far.
  Since needed for the process we might set Server-Dev, given what it does 
Foundations might be more correct but I can't directly volunteer others :-/

  9. Background information:
  => The package descriptions is comprehensive and correct IMHO:
   "This data synchronization library provides read-side access which scales
   linearly with the number of cores. It does so by allowing multiples copies of
   a given data structure to live at the same time, and by monitoring the data
   structure accesses to detect grace periods after which memory reclamation is
   possible."

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

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

[Touch-packages] [Bug 1644757] Re: [MIR] liburcu

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

We found that this already had a MIR in bug 1203591 but a short universe
hickup without a reason.

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

Title:
  [MIR] liburcu

Status in liburcu package in Ubuntu:
  New

Bug description:
  The coming merge of latest multipath-tools will add a dependency to
  liburcu.

  This was added upstream by:
 commit cb98c8837693a4a4f76895ff3e8c59bc3ba844ca
 Author: Hannes Reinecke 
 Date:   Tue Jun 14 16:36:30 2016 +0200
 multipathd: use userspace RCU to access configuration

  That is a non optional change (no configure selection or runtime detection).
  Patching out the locking of the project sounds like the most error prone 
thing I can think of, therefore I request a MIR for liburcu.

  
  Processing Main Inclusion Requirements:
  1. Availability: The package must already be in the Ubuntu universe, and must 
build for the architectures it is designed to work on.

  Last version fine since Xenial,former verisions go back til precise (not all 
archs) 
   liburcu1 | 0.6.7-2 | precise/universe | amd64, armhf, i386, powerpc
   liburcu1 | 0.7.12-0ubuntu2 | trusty   | amd64, arm64, armhf, i386, 
powerpc, ppc64el
   liburcu2 | 0.8.5-1ubuntu1  | vivid| amd64, arm64, armhf, i386, 
powerpc, ppc64el
   liburcu4 | 0.9.1-3 | xenial/universe | amd64, arm64, armhf, i386, powerpc, 
ppc64el, s390x
   liburcu4 | 0.9.2-3 | yakkety | amd64, arm64, armhf, i386, powerpc, 
ppc64el, s390x
   liburcu4 | 0.9.2-3 | zesty   | amd64, arm64, armhf, i386, powerpc, 
ppc64el, s390x

  
  2. The package is useful for a large part of our user base.
  => The package is a new build dependency or dependency of a package that we 
already support and in wide use by enterprise Ubuntu setups (multipath-tools).
  => The package helps meet a specific Blueprint goal (The merge of a more 
recent multipath-version in blueprint servercloud-z-server-core).

  
  3. Security.
  => So far the package never showed up in any of the links referred to by 
"Security Checks"
  => No Executables which have the suid or sgid bit set (no executables at all 
btw, so no /sbin, ...)
  => No services / daemons
  => No ports
  => no addon/plugin so far used directly by
  * gdnsd
  * glusterfs-common
  * knot
  * liblttng-ctl0
  * liblttng-ust-ctl2
  * liblttng-ust0
  * liburcu-dev
  * lttng-tools
  * netsniff-ng
  * python3-lttng
  None of these is especially security-sensitive software (filters, scanners, 
UI skins, etc) 

  
  4. Quality assurance
  => no config needed
  => no debconf
  => no long term outstanding bugs that matter (only one for precise which 
nobody seemed to care so far, but that is not crit at all)
  https://bugs.launchpad.net/ubuntu/+source/liburcu
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=liburcu
  => No special HW needs to be used
  => Comes with a unit test that is ran on build via dh_auto_test
  => it has a watch file

  
  5. UI standards
  => No user-facing application, so no UI/Translation needs

  
  6. Dependencies:
  => has only one Dependency to libc6, no suggests, recommends

  7. Standards compliance
  => No known FHS/Policy issues

  8. Maintenance
  => Well maintained in Debian, only a sync so far.
  Since needed for the process we might set Server-Dev, given what it does 
Foundations might be more correct but I can't directly volunteer others :-/

  9. Background information:
  => The package descriptions is comprehensive and correct IMHO:
   "This data synchronization library provides read-side access which scales
   linearly with the number of cores. It does so by allowing multiples copies of
   a given data structure to live at the same time, and by monitoring the data
   structure accesses to detect grace periods after which memory reclamation is
   possible."

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

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

[Touch-packages] [Bug 1644757] Re: [MIR] liburcu

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

See https://launchpad.net/ubuntu/+source/liburcu/+publishinghistory

** This bug has been marked a duplicate of bug 1203591
   [MIR] liburcu

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

Title:
  [MIR] liburcu

Status in liburcu package in Ubuntu:
  New

Bug description:
  The coming merge of latest multipath-tools will add a dependency to
  liburcu.

  This was added upstream by:
 commit cb98c8837693a4a4f76895ff3e8c59bc3ba844ca
 Author: Hannes Reinecke 
 Date:   Tue Jun 14 16:36:30 2016 +0200
 multipathd: use userspace RCU to access configuration

  That is a non optional change (no configure selection or runtime detection).
  Patching out the locking of the project sounds like the most error prone 
thing I can think of, therefore I request a MIR for liburcu.

  
  Processing Main Inclusion Requirements:
  1. Availability: The package must already be in the Ubuntu universe, and must 
build for the architectures it is designed to work on.

  Last version fine since Xenial,former verisions go back til precise (not all 
archs) 
   liburcu1 | 0.6.7-2 | precise/universe | amd64, armhf, i386, powerpc
   liburcu1 | 0.7.12-0ubuntu2 | trusty   | amd64, arm64, armhf, i386, 
powerpc, ppc64el
   liburcu2 | 0.8.5-1ubuntu1  | vivid| amd64, arm64, armhf, i386, 
powerpc, ppc64el
   liburcu4 | 0.9.1-3 | xenial/universe | amd64, arm64, armhf, i386, powerpc, 
ppc64el, s390x
   liburcu4 | 0.9.2-3 | yakkety | amd64, arm64, armhf, i386, powerpc, 
ppc64el, s390x
   liburcu4 | 0.9.2-3 | zesty   | amd64, arm64, armhf, i386, powerpc, 
ppc64el, s390x

  
  2. The package is useful for a large part of our user base.
  => The package is a new build dependency or dependency of a package that we 
already support and in wide use by enterprise Ubuntu setups (multipath-tools).
  => The package helps meet a specific Blueprint goal (The merge of a more 
recent multipath-version in blueprint servercloud-z-server-core).

  
  3. Security.
  => So far the package never showed up in any of the links referred to by 
"Security Checks"
  => No Executables which have the suid or sgid bit set (no executables at all 
btw, so no /sbin, ...)
  => No services / daemons
  => No ports
  => no addon/plugin so far used directly by
  * gdnsd
  * glusterfs-common
  * knot
  * liblttng-ctl0
  * liblttng-ust-ctl2
  * liblttng-ust0
  * liburcu-dev
  * lttng-tools
  * netsniff-ng
  * python3-lttng
  None of these is especially security-sensitive software (filters, scanners, 
UI skins, etc) 

  
  4. Quality assurance
  => no config needed
  => no debconf
  => no long term outstanding bugs that matter (only one for precise which 
nobody seemed to care so far, but that is not crit at all)
  https://bugs.launchpad.net/ubuntu/+source/liburcu
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=liburcu
  => No special HW needs to be used
  => Comes with a unit test that is ran on build via dh_auto_test
  => it has a watch file

  
  5. UI standards
  => No user-facing application, so no UI/Translation needs

  
  6. Dependencies:
  => has only one Dependency to libc6, no suggests, recommends

  7. Standards compliance
  => No known FHS/Policy issues

  8. Maintenance
  => Well maintained in Debian, only a sync so far.
  Since needed for the process we might set Server-Dev, given what it does 
Foundations might be more correct but I can't directly volunteer others :-/

  9. Background information:
  => The package descriptions is comprehensive and correct IMHO:
   "This data synchronization library provides read-side access which scales
   linearly with the number of cores. It does so by allowing multiples copies of
   a given data structure to live at the same time, and by monitoring the data
   structure accesses to detect grace periods after which memory reclamation is
   possible."

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

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

[Touch-packages] [Bug 1620780] Re: dev-sda2.device job running and times out

2016-11-28 Thread Scott Moser

I can verify that in a lxc container of zesty i installed ppa above (yakkety) 
and dist-upgraded.
rebooted and no dev-sda2 job.

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

Title:
  dev-sda2.device job running and times out

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  $ lxc launch ubuntu-daily:yakkety y4
  $ lxc exec y3 -- systemctl list-jobs
  JOB UNITTYPE  STATE  
5 dev-sda2.device start running

  1 jobs listed.

  $ lxc exec y3 -- cat /etc/cloud/build.info 
  build_name: server
  serial: 20160902

  $ lxc exec y3 -- systemd-analyze
  Startup finished in 1min 30.373s (userspace) = 6d 2h 27min 41.963s

  
  $ lxc exec y3 -- journalctl > yakkety-lxd-journalctl.txt

  $ lxc exec y3 -- systemctl status dev-sda2.device
  ● dev-sda2.device
 Loaded: loaded
 Active: activating (tentative) since Tue 2016-09-06 18:38:31 UTC; 4min 39s 
ago

  Sep 06 18:40:01 y3 systemd[1]: dev-sda2.device: Job dev-sda2.device/start 
timed out.
  Sep 06 18:40:01 y3 systemd[1]: Timed out waiting for device dev-sda2.device.
  Sep 06 18:40:01 y3 systemd[1]: dev-sda2.device: Job dev-sda2.device/start 
failed with result 'timeout'.
  Warning: Journal has been rotated since unit was started. Log output is 
incomplete or unavailable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep  6 18:38:48 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic.efi.signed 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1645366] [NEW] upgrading pulseaudio 8.3.0 to 8.3.1 on 16.04 broke bluetooth audio for me

2016-11-28 Thread deuscovri...@gmail.com

Public bug reported:

Description:Ubuntu 16.04.1 LTS
Release:16.04
Package name:
1:8.0-0ubuntu3.1

After using the software updater to upgrade libpulseaudio I am unable to
connect/pair my Bose QC 35 to my computer.


When using blueman to connect, I receive the following error:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 607, in 
msg_reply_handler
*message.get_args_list()))
  File "/usr/lib/python3/dist-packages/blueman/bluez/Device.py", line 33, in err
raise exception
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken. 
This used to work before the update.

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

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

Title:
  upgrading pulseaudio 8.3.0 to 8.3.1 on 16.04 broke bluetooth audio for
  me

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  Package name:
  1:8.0-0ubuntu3.1

  After using the software updater to upgrade libpulseaudio I am unable
  to connect/pair my Bose QC 35 to my computer.

  
  When using blueman to connect, I receive the following error:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 607, in 
msg_reply_handler
  *message.get_args_list()))
File "/usr/lib/python3/dist-packages/blueman/bluez/Device.py", line 33, in 
err
  raise exception
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken. 
  This used to work before the update.

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

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

[Touch-packages] [Bug 1645362] [NEW] Calculator example is broken

Public bug reported:

When I start the calculator example, I only see a header with
'Calculator' as the title, and a '0' as a result for calculations, but
there is no input field where I can enter new calculations.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: examples snap

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

Title:
  Calculator example is broken

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  When I start the calculator example, I only see a header with
  'Calculator' as the title, and a '0' as a result for calculations, but
  there is no input field where I can enter new calculations.

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

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

[Touch-packages] [Bug 1645363] [NEW] slow sbuild Debian package builds (schroot calls are slow)

2016-11-28 Thread Benjamin Drung

Public bug reported:

Since the upgrade to Ubuntu 16.10, building packages with sbuild takes
much more time than previously. sbuild creates a schroot session for
building Debian packages and calls sbuild --run-session several times.
Entering the sessions takes norally 10 ms, but entering the session from
sbuild takes several seconds now:

time schroot -d / -c $session --run-session -q -u root -p -- true
real0m2.098s
user0m0.008s
sys 0m0.000s

This causes a drastic build time increase for small packages. Example
package build time on my affected Ubuntu workstation:

Build-Time: 9 s
Install-Time: 115 s
Package-Time: 195 s (= 00:03:15)

compared to the build bot running Debian stable (having a slower
processor):

Build-Time: 9 s
Install-Time: 24 s
Package-Time: 41 s

/var/log/syslog shows many entries about starting and stopping D-Bus
services:

Nov 28 16:27:34 konstrukt systemd[1]: Created slice User Slice of root.
Nov 28 16:27:34 konstrukt systemd[1]: Starting User Manager for UID 0...
Nov 28 16:27:34 konstrukt systemd[1]: Started Session 2 of user root.
Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Timers.
Nov 28 16:27:34 konstrukt systemd[21965]: Starting D-Bus User Message Bus 
Socket.
Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Paths.
Nov 28 16:27:34 konstrukt systemd[21965]: Listening on D-Bus User Message Bus 
Socket.
Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Sockets.
Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Basic System.
Nov 28 16:27:34 konstrukt systemd[21965]: Starting Run Click user-level hooks...
Nov 28 16:27:34 konstrukt systemd[21965]: Started D-Bus User Message Bus.
Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 40.327µs 404
Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Activating service 
name='ca.desrt.dconf'
Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 23.455µs 404
Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Successfully activated service 
'ca.desrt.dconf'
Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Activating via systemd: service 
name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
Nov 28 16:27:35 konstrukt systemd[21965]: Starting Virtual filesystem service...
Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Successfully activated service 
'org.gtk.vfs.Daemon'
Nov 28 16:27:35 konstrukt systemd[21965]: Started Virtual filesystem service.
Nov 28 16:27:35 konstrukt click[21997]: 
/usr/lib/ubuntu-push-client/click-hook:15: PyGIWarning: Click was imported 
without specifying a version first. Use gi.require_version('Click', '0.4') 
before import to ensure that the right version gets loaded.
Nov 28 16:27:35 konstrukt click[21997]:   from gi.repository import Click
Nov 28 16:27:35 konstrukt click[21997]: hooks.vala:1216: User-level hook 
push-helper failed: Hook command 
'/usr/lib/ubuntu-push-client/click-hook-wrapper' failed: Child process exited 
with code 1
Nov 28 16:27:35 konstrukt click[21997]: Some user-level hooks failed: 
push-helper
Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Main 
process exited, code=exited, status=1/FAILURE
Nov 28 16:27:35 konstrukt systemd[21965]: Failed to start Run Click user-level 
hooks.
Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Unit 
entered failed state.
Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Failed with 
result 'exit-code'.
Nov 28 16:27:35 konstrukt systemd[21965]: Reached target Default. 
Nov 28 16:27:35 konstrukt systemd[21965]: Startup finished in 497ms.
Nov 28 16:27:35 konstrukt systemd[1]: Started User Manager for UID 0.
Nov 28 16:27:35 konstrukt schroot[22084]: 
[pb-jessie-93c04c41-79af-4e32-addb-09a186998122 chroot] (bdrung->root) Running 
command: "getent group sbuild"
Nov 28 16:27:35 konstrukt systemd[1]: Stopping User Manager for UID 0...
Nov 28 16:27:35 konstrukt systemd[21965]: Stopping D-Bus User Message Bus...
Nov 28 16:27:35 konstrukt systemd[21965]: Stopped target Default.
Nov 28 16:27:35 konstrukt systemd[21965]: Stopping Virtual filesystem service...
Nov 28 16:27:35 konstrukt systemd[21965]: Stopped D-Bus User Message Bus.
Nov 28 16:27:35 konstrukt systemd[1]: Started Session 2 of user root.
Nov 28 16:27:36 konstrukt systemd[21965]: Stopped Virtual filesystem servic

[Touch-packages] [Bug 1645365] [NEW] customtheme example broken in the deb package

Public bug reported:

The theme/ directory that contains the custom theme is missing.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: examples snap

** Tags added: examples snap

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

Title:
  customtheme example broken in the deb package

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  The theme/ directory that contains the custom theme is missing.

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

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

[Touch-packages] [Bug 1645362] Re: Calculator example is broken

** Tags added: examples snap

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

Title:
  Calculator example is broken

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  When I start the calculator example, I only see a header with
  'Calculator' as the title, and a '0' as a result for calculations, but
  there is no input field where I can enter new calculations.

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

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

[Touch-packages] [Bug 1645363] Re: slow sbuild Debian package builds (schroot calls are slow)

At least for me the reason was bug 1626436. Can you try the test kernel
there and see if that helps?

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

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

Title:
  slow sbuild Debian package builds (schroot calls are slow)

Status in sbuild package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade to Ubuntu 16.10, building packages with sbuild takes
  much more time than previously. sbuild creates a schroot session for
  building Debian packages and calls sbuild --run-session several times.
  Entering the sessions takes norally 10 ms, but entering the session
  from sbuild takes several seconds now:

  time schroot -d / -c $session --run-session -q -u root -p -- true
  real0m2.098s
  user0m0.008s
  sys 0m0.000s

  This causes a drastic build time increase for small packages. Example
  package build time on my affected Ubuntu workstation:

  Build-Time: 9 s
  Install-Time: 115 s
  Package-Time: 195 s (= 00:03:15)

  compared to the build bot running Debian stable (having a slower
  processor):

  Build-Time: 9 s
  Install-Time: 24 s
  Package-Time: 41 s

  /var/log/syslog shows many entries about starting and stopping D-Bus
  services:

  Nov 28 16:27:34 konstrukt systemd[1]: Created slice User Slice of root.
  Nov 28 16:27:34 konstrukt systemd[1]: Starting User Manager for UID 0...
  Nov 28 16:27:34 konstrukt systemd[1]: Started Session 2 of user root.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Timers.
  Nov 28 16:27:34 konstrukt systemd[21965]: Starting D-Bus User Message Bus 
Socket.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Paths.
  Nov 28 16:27:34 konstrukt systemd[21965]: Listening on D-Bus User Message Bus 
Socket.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Sockets.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Basic System.
  Nov 28 16:27:34 konstrukt systemd[21965]: Starting Run Click user-level 
hooks...
  Nov 28 16:27:34 konstrukt systemd[21965]: Started D-Bus User Message Bus.
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
  Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 40.327µs 404
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
  Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Activating service 
name='ca.desrt.dconf'
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
  Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 23.455µs 404
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
  Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Successfully activated service 
'ca.desrt.dconf'
  Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Activating via systemd: service 
name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
  Nov 28 16:27:35 konstrukt systemd[21965]: Starting Virtual filesystem 
service...
  Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Successfully activated service 
'org.gtk.vfs.Daemon'
  Nov 28 16:27:35 konstrukt systemd[21965]: Started Virtual filesystem service.
  Nov 28 16:27:35 konstrukt click[21997]: 
/usr/lib/ubuntu-push-client/click-hook:15: PyGIWarning: Click was imported 
without specifying a version first. Use gi.require_version('Click', '0.4') 
before import to ensure that the right version gets loaded.
  Nov 28 16:27:35 konstrukt click[21997]:   from gi.repository import Click
  Nov 28 16:27:35 konstrukt click[21997]: hooks.vala:1216: User-level hook 
push-helper failed: Hook command 
'/usr/lib/ubuntu-push-client/click-hook-wrapper' failed: Child process exited 
with code 1
  Nov 28 16:27:35 konstrukt click[21997]: Some user-level hooks failed: 
push-helper
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Main 
process exited, code=exited, status=1/FAILURE
  Nov 28 16:27:35 konstrukt systemd[21965]: Failed to start Run Click 
user-level hooks.
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Unit 
entered failed state.
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Failed 
with result 'exit-code'.
  Nov 28 16:27:35 konstrukt systemd[21965]: Reached target Default. 
  Nov 28 16:27:35 konstrukt systemd[21965]: Startup finished in 497ms.
  Nov 28 16:27:35 konstrukt systemd[1]: Started User

[Touch-packages] [Bug 1645372] [NEW] support display scaling slider in unity8

2016-11-28 Thread Bill Filler

Public bug reported:

We need to be able to scale the display in unity8, via ubuntu-system-
settings Display->Scaling slider. This will need backend support in Mir
and unity8, filing this bug to track.

Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

** Affects: mir (Ubuntu)
 Importance: High
 Status: New

** Affects: qtmir (Ubuntu)
 Importance: High
 Status: New

** Affects: ubuntu-system-settings (Ubuntu)
 Importance: High
 Assignee: Jonas G. Drange (jonas-drange)
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: High
 Status: New

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

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

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

** Changed in: ubuntu-system-settings (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: (unassigned) => Jonas G. Drange (jonas-drange)

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

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

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

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

Title:
  support display scaling slider in unity8

Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

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

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

[Touch-packages] [Bug 1645375] [NEW] Xorg freeze when starting chromium-browser

2016-11-28 Thread Richard

Public bug reported:

I get messages like the following in the journal:

kernel: nouveau :0a:00.0: fifo: CACHE_ERROR - ch 7 [chromium-
browse[6657]] subc 3 mthd 15ec data 


I can still SSH in.

Chromium Version 53.0.2785.143 Built on Ubuntu , running on Ubuntu 16.10
(64-bit)

lsb_release -rd:

  Description:  Ubuntu 16.10
  Release:  16.10

apt-cache policy xserver-xorg-video-nouveau:

xserver-xorg-video-nouveau:
  Installed: 1:1.0.12-2
  Candidate: 1:1.0.12-2
  Version table:
 *** 1:1.0.12-2 500
500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
100 /var/lib/dpkg/status

What you expected to happen:

  Chrome Browser window to open.

What happened instead:

  Outline of Chrome Browser window appeared and then Xorg froze. Mouse
point could be moved on one display but between displays. Nothing was
responsive on the UI.

Running Chromium with:

chromium-browser -gpu

works and does not freeze.

Regards

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Nov 28 15:49:47 2016
DistUpgraded: 2016-10-19 16:07:29,098 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.6, 4.8.0-26-generic, x86_64: installed
 virtualbox, 5.1.6, 4.8.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
 NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company GT218 [NVS 300] [103c:0862]
InstallationDate: Installed on 2016-01-05 (327 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
MachineType: Dell Inc. PowerEdge T320
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-27-generic 
root=UUID=0f94436a-b93a-4750-b0f1-08be2c4b2188 ro rootflags=subvol=@
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to yakkety on 2016-10-19 (40 days ago)
dmi.bios.date: 01/29/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.2
dmi.board.name: 0FDT3J
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 17
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd01/29/2015:svnDellInc.:pnPowerEdgeT320:pvr:rvnDellInc.:rn0FDT3J:rvrA02:cvnDellInc.:ct17:cvr:
dmi.product.name: PowerEdge T320
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Mon Nov 28 15:43:48 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu yakkety

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

Title:
  Xorg freeze when starting chromium-browser

Status in xorg package in Ubuntu:
  New

Bug description:
  I get messages like the following in the journal:

  kernel: nouveau :0a:00.0: fifo: CACHE_ERROR - ch 7 [chromium-
  browse[6657]] subc 3 mthd 15ec data 

  
  I can still SSH in.

  Chromium Version 53.0.2785.143 Built on Ubuntu , running on Ubuntu
  16.10 (64-bit)

  lsb_release -rd:

Description:Ubuntu 16.10
Release:16.10

  apt-cache policy xserver-xorg-video-nouveau:

  xserver-xorg-video-nouveau:
Installed: 1:1.0.12-2
Candidate: 1:1.0.12-2
Version table:
   *** 1:1.0.12-2 500
  500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  What you expected to happ

[Touch-packages] [Bug 1645372] Re: support display scaling slider in unity8

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

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

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

Title:
  support display scaling slider in unity8

Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

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

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

[Touch-packages] [Bug 1645372] Re: support display scaling slider in unity8

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

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

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

Title:
  support display scaling slider in unity8

Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

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

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

[Touch-packages] [Bug 1645372] Re: support display scaling slider in unity8

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

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  support display scaling slider in unity8

Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

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

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

[Touch-packages] [Bug 1645372] Re: support display scaling slider in unity8

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

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

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

Title:
  support display scaling slider in unity8

Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

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

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

[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

2016-11-28 Thread Jim Hodapp

@Robin: Yeah I've been able to get mine working as well. Were you trying
with Ubuntu desktop or on Ubuntu Touch? The choppiness seems to be bluez
doing other device scans. So on Touch, if you make sure that system
settings is in the background, it should remain nearly chop-free. On the
desktop, it stopped scanning if I closed system settings and then got a
lot better quality.

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

Title:
  Fails to pair with Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

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

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

[Touch-packages] [Bug 1645363] Re: slow sbuild Debian package builds (schroot calls are slow)

2016-11-28 Thread Benjamin Drung

Yes! With linux 4.8.0-29-generic #31~lp1626436ProposedWithTwoPatches the
build is fast again:

Build-Time: 5
Install-Time: 18
Package-Time: 36

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

Title:
  slow sbuild Debian package builds (schroot calls are slow)

Status in sbuild package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade to Ubuntu 16.10, building packages with sbuild takes
  much more time than previously. sbuild creates a schroot session for
  building Debian packages and calls sbuild --run-session several times.
  Entering the sessions takes norally 10 ms, but entering the session
  from sbuild takes several seconds now:

  time schroot -d / -c $session --run-session -q -u root -p -- true
  real0m2.098s
  user0m0.008s
  sys 0m0.000s

  This causes a drastic build time increase for small packages. Example
  package build time on my affected Ubuntu workstation:

  Build-Time: 9 s
  Install-Time: 115 s
  Package-Time: 195 s (= 00:03:15)

  compared to the build bot running Debian stable (having a slower
  processor):

  Build-Time: 9 s
  Install-Time: 24 s
  Package-Time: 41 s

  /var/log/syslog shows many entries about starting and stopping D-Bus
  services:

  Nov 28 16:27:34 konstrukt systemd[1]: Created slice User Slice of root.
  Nov 28 16:27:34 konstrukt systemd[1]: Starting User Manager for UID 0...
  Nov 28 16:27:34 konstrukt systemd[1]: Started Session 2 of user root.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Timers.
  Nov 28 16:27:34 konstrukt systemd[21965]: Starting D-Bus User Message Bus 
Socket.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Paths.
  Nov 28 16:27:34 konstrukt systemd[21965]: Listening on D-Bus User Message Bus 
Socket.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Sockets.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Basic System.
  Nov 28 16:27:34 konstrukt systemd[21965]: Starting Run Click user-level 
hooks...
  Nov 28 16:27:34 konstrukt systemd[21965]: Started D-Bus User Message Bus.
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
  Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 40.327µs 404
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
  Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Activating service 
name='ca.desrt.dconf'
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
  Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 23.455µs 404
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
  Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Successfully activated service 
'ca.desrt.dconf'
  Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Activating via systemd: service 
name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
  Nov 28 16:27:35 konstrukt systemd[21965]: Starting Virtual filesystem 
service...
  Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Successfully activated service 
'org.gtk.vfs.Daemon'
  Nov 28 16:27:35 konstrukt systemd[21965]: Started Virtual filesystem service.
  Nov 28 16:27:35 konstrukt click[21997]: 
/usr/lib/ubuntu-push-client/click-hook:15: PyGIWarning: Click was imported 
without specifying a version first. Use gi.require_version('Click', '0.4') 
before import to ensure that the right version gets loaded.
  Nov 28 16:27:35 konstrukt click[21997]:   from gi.repository import Click
  Nov 28 16:27:35 konstrukt click[21997]: hooks.vala:1216: User-level hook 
push-helper failed: Hook command 
'/usr/lib/ubuntu-push-client/click-hook-wrapper' failed: Child process exited 
with code 1
  Nov 28 16:27:35 konstrukt click[21997]: Some user-level hooks failed: 
push-helper
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Main 
process exited, code=exited, status=1/FAILURE
  Nov 28 16:27:35 konstrukt systemd[21965]: Failed to start Run Click 
user-level hooks.
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Unit 
entered failed state.
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Failed 
with result 'exit-code'.
  Nov 28 16:27:35 konstrukt systemd[21965]: Reached target Default. 
  Nov 28 16:27:35 konstrukt systemd[21965]: Startup finished in 497ms.
  Nov 28 16:27:35 konstrukt systemd[1]: Started User Manager for UID 0.
  Nov 28 16:27:35 konstrukt schroot[22084]: 
[pb-jessie-93c04c41-79af-

[Touch-packages] [Bug 1645365] Re: customtheme example broken in the deb package

** Also affects: ubuntu-ui-toolkit-examples
   Importance: Undecided
   Status: New

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

Title:
  customtheme example broken in the deb package

Status in ubuntu-ui-toolkit-examples:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  The theme/ directory that contains the custom theme is missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit-examples/+bug/1645365/+subscriptions

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

[Touch-packages] [Bug 1645362] Re: Calculator example is broken

** Also affects: ubuntu-ui-toolkit-examples
   Importance: Undecided
   Status: New

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

Title:
  Calculator example is broken

Status in ubuntu-ui-toolkit-examples:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  When I start the calculator example, I only see a header with
  'Calculator' as the title, and a '0' as a result for calculations, but
  there is no input field where I can enter new calculations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit-examples/+bug/1645362/+subscriptions

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

[Touch-packages] [Bug 1644541] Re: Update stuck at “configuring unattended-upgrades”

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

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

Title:
  Update stuck at “configuring unattended-upgrades”

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  On basically fresh install from ubuntu-16.04.1-desktop-amd64.iso; no
  updates or installs had been applied since installing the OS from the
  media.

  During execution of "Software Updater", it freezes indefinitely while
  "Installing updates..." at the step marked "Configuring unattended-
  upgrades."

  It appears that this happens if System Settings->Software &
  Updates->Updates, "Automatically check for updates" has been set to
  "Never."

  If that is instead set to "Daily" and the following are then set in
  /etc/apt/apt.conf.d/10periodic then the update succeeds:

  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Download-Upgradeable-Packages "1";
  APT::Periodic::AutocleanInterval "7";
  APT::Periodic::Unattended-Upgrade "1";

  Someone else had asked about this issue at AskUbuntu.  Their question
  along with my answer (from Kevin) provide some further details:

  http://askubuntu.com/questions/851371/update-stuck-at-configuring-
  unattended-upgrades-software-updater-turned-black/852110#852110

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

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

[Touch-packages] [Bug 1642863] Re: Upgrading unattended-upgrades gives errors and a warning

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

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

Title:
  Upgrading unattended-upgrades gives errors and a warning

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Ubuntu release
  ==

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Package version
  ===

  unattended-upgrades:
Installed: 0.90ubuntu0.2
Candidate: 0.90ubuntu0.2
Version table:
   *** 0.90ubuntu0.2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

  What I expected to happen
  =

  No error or warning messages during a software upgrade.

  What happened instead
  =

  When an updated version of unattended-upgrades is installed, the
  following error messages appear because /tmp is mounted noexec for
  security reasons (see the Securing Debian Manual, section 4.10 at
  https://www.debian.org/doc/manuals/securing-debian-
  howto/ch4.en.html#s4.10):

  Preconfiguring packages ...
  Can't exec "/tmp/unattended-upgrades.config.5svL0F": Permission denied at 
/usr/share/perl/5.22/IPC/Open3.pm line 178.
  open2: exec of /tmp/unattended-upgrades.config.5svL0F configure 
0.90ubuntu0.1 failed at /usr/share/perl5/Debconf/ConfModule.pm line 59.

  Also, the following warning occurs later on:

  Setting up unattended-upgrades (0.90ubuntu0.2) ...
  update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 18 02:36:54 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-01 (17 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "0";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-11-07T13:58:08.805628

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

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

[Touch-packages] [Bug 1645363] Re: slow sbuild Debian package builds (schroot calls are slow)

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

Thanks for confirming!

** This bug has been marked a duplicate of bug 1626436
   [4.8 regression] boot has become very slow

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

Title:
  slow sbuild Debian package builds (schroot calls are slow)

Status in sbuild package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade to Ubuntu 16.10, building packages with sbuild takes
  much more time than previously. sbuild creates a schroot session for
  building Debian packages and calls sbuild --run-session several times.
  Entering the sessions takes norally 10 ms, but entering the session
  from sbuild takes several seconds now:

  time schroot -d / -c $session --run-session -q -u root -p -- true
  real0m2.098s
  user0m0.008s
  sys 0m0.000s

  This causes a drastic build time increase for small packages. Example
  package build time on my affected Ubuntu workstation:

  Build-Time: 9 s
  Install-Time: 115 s
  Package-Time: 195 s (= 00:03:15)

  compared to the build bot running Debian stable (having a slower
  processor):

  Build-Time: 9 s
  Install-Time: 24 s
  Package-Time: 41 s

  /var/log/syslog shows many entries about starting and stopping D-Bus
  services:

  Nov 28 16:27:34 konstrukt systemd[1]: Created slice User Slice of root.
  Nov 28 16:27:34 konstrukt systemd[1]: Starting User Manager for UID 0...
  Nov 28 16:27:34 konstrukt systemd[1]: Started Session 2 of user root.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Timers.
  Nov 28 16:27:34 konstrukt systemd[21965]: Starting D-Bus User Message Bus 
Socket.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Paths.
  Nov 28 16:27:34 konstrukt systemd[21965]: Listening on D-Bus User Message Bus 
Socket.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Sockets.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Basic System.
  Nov 28 16:27:34 konstrukt systemd[21965]: Starting Run Click user-level 
hooks...
  Nov 28 16:27:34 konstrukt systemd[21965]: Started D-Bus User Message Bus.
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
  Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 40.327µs 404
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
  Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Activating service 
name='ca.desrt.dconf'
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
  Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 23.455µs 404
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
  Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Successfully activated service 
'ca.desrt.dconf'
  Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Activating via systemd: service 
name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
  Nov 28 16:27:35 konstrukt systemd[21965]: Starting Virtual filesystem 
service...
  Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Successfully activated service 
'org.gtk.vfs.Daemon'
  Nov 28 16:27:35 konstrukt systemd[21965]: Started Virtual filesystem service.
  Nov 28 16:27:35 konstrukt click[21997]: 
/usr/lib/ubuntu-push-client/click-hook:15: PyGIWarning: Click was imported 
without specifying a version first. Use gi.require_version('Click', '0.4') 
before import to ensure that the right version gets loaded.
  Nov 28 16:27:35 konstrukt click[21997]:   from gi.repository import Click
  Nov 28 16:27:35 konstrukt click[21997]: hooks.vala:1216: User-level hook 
push-helper failed: Hook command 
'/usr/lib/ubuntu-push-client/click-hook-wrapper' failed: Child process exited 
with code 1
  Nov 28 16:27:35 konstrukt click[21997]: Some user-level hooks failed: 
push-helper
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Main 
process exited, code=exited, status=1/FAILURE
  Nov 28 16:27:35 konstrukt systemd[21965]: Failed to start Run Click 
user-level hooks.
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Unit 
entered failed state.
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Failed 
with result 'exit-code'.
  Nov 28 16:27:35 konstrukt systemd[21965]: Reached target Default. 
  Nov 28 16:27:35 konstrukt systemd[21965]: Startup finished in 497ms.
  Nov 28 16:27:35 konstrukt systemd[1]: Started User Manager for UID

[Touch-packages] [Bug 1645384] [NEW] package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida d

2016-11-28 Thread José Andrade Méndez Julián

Public bug reported:

el problema se genero cuando intentaba descargar unos programas, no se
completo la descarga  y la tuve que reiniciar y posterior al reinicio
aparecio el  mensaje de error.

ProblemType: Package
DistroRelease: elementary 0.4
Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Nov 28 09:10:05 2016
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 128
InstallationDate: Installed on 2016-11-26 (1 days ago)
InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to 
install/upgrade: el subproceso instalado el script post-installation devolvió 
el código de salida de error 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to
  install/upgrade: el subproceso instalado el script post-installation
  devolvió el código de salida de error 128

Status in gconf package in Ubuntu:
  New

Bug description:
  el problema se genero cuando intentaba descargar unos programas, no se
  completo la descarga  y la tuve que reiniciar y posterior al reinicio
  aparecio el  mensaje de error.

  ProblemType: Package
  DistroRelease: elementary 0.4
  Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Nov 28 09:10:05 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 128
  InstallationDate: Installed on 2016-11-26 (1 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to 
install/upgrade: el subproceso instalado el script post-installation devolvió 
el código de salida de error 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1577596] Re: ntpd not started when using ntpdate

2016-11-28 Thread Heinrich Hartl

attached version of ntpdate solves the problem for me and hopefully for 
everybody.
I do not mind if comments are removed.
The attached version avoids the conflict between ntpd and ntpdate and also 
makes the skript simpler.


** Attachment added: "ntpdate_HH is a revised version of  
/etc/network/if-up.d/ntpdate"
   
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596/+attachment/4784298/+files/ntpdate_HH

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Won't Fix

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions

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

[Touch-packages] [Bug 1323837] Re: [phone] Sim toolkit is not available on UT

2016-11-28 Thread Alien911

is there any way to get this to work, som workaround? this is the one
ting that makes Ubuntu phone usless as my main phone.

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

Title:
  [phone] Sim toolkit is not available on UT

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  E.g. of SIm toolkit is http://support.vodafone.com.au/articles/FAQ
  /SIM-Toolkit

  While a lot of those addons are completely crap and useless, the SIm
  toolkit is sometimes used by some phone provider to set your sim card
  to roaming mode when you are abroad which makes it a must have.

  For the moment i need to borrow a second phone put my sim card in it,
  go to the Sim-toolkit, enable my sim card for roaming and put the sim
  card back in my UT to get my phone working while i am abroad. I need
  to do the same when i go back home.

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

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

[Touch-packages] [Bug 1577596] Re: ntpd not started when using ntpdate

2016-11-28 Thread Heinrich Hartl

Please do not blame me too hard if I provided a "patch" not in the
correct format - but the script does the job for me. ntpd is started and
continues to run, ntpdate seems to be invoked twice. The first
invocation is too early and failes. The next one does its job but
doesn't do a very impressive correction of the system time.

And here is an excerpt from my reboot log:
$ grep -i ntp syslog_1743
Nov 28 17:33:49 localhost kernel: [0.076562] Mountpoint-cache hash table 
entries: 2048 (order: 1, 8192 bytes)
Nov 28 17:33:49 localhost ntpdate[781]: no servers can be used, exiting
Nov 28 17:34:01 localhost systemd[1]: Starting LSB: Start NTP daemon...
Nov 28 17:34:02 localhost ntp[1285]:  * Starting NTP server ntpd
Nov 28 17:34:02 localhost ntpd[1306]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:48 
UTC 2016 (1): Starting
Nov 28 17:34:02 localhost ntpd[1306]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 116:125
Nov 28 17:34:02 localhost ntp[1285]:...done.
Nov 28 17:34:02 localhost systemd[1]: Started LSB: Start NTP daemon.
Nov 28 17:34:02 localhost ntpd[1309]: proto: precision = 0.129 usec (-23)
Nov 28 17:34:02 localhost ntpd[1309]: restrict 0.0.0.0: KOD does nothing 
without LIMITED.
Nov 28 17:34:02 localhost ntpd[1309]: restrict ::: KOD does nothing without 
LIMITED.
Nov 28 17:34:02 localhost ntpd[1309]: Listen and drop on 0 v6wildcard [::]:123
Nov 28 17:34:02 localhost ntpd[1309]: Listen and drop on 1 v4wildcard 
0.0.0.0:123
Nov 28 17:34:02 localhost ntpd[1309]: Listen normally on 2 lo 127.0.0.1:123
Nov 28 17:34:02 localhost ntpd[1309]: Listen normally on 3 eth0 192.168.0.12:123
Nov 28 17:34:02 localhost ntpd[1309]: Listen normally on 4 lo [::1]:123
Nov 28 17:34:02 localhost ntpd[1309]: Listen normally on 5 eth0 
[fe80::221:9bff:fe4c:d684%2]:123
Nov 28 17:34:02 localhost ntpd[1309]: Listening on routing socket on fd #22 for 
interface updates
Nov 28 17:34:05 localhost ntpdate[1154]: adjust time server 172.26.195.1 offset 
-0.28 sec

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Won't Fix

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions

-- 
Mailing list:

[Touch-packages] [Bug 1644541] Re: Update stuck at “configuring unattended-upgrades”

It'd be helpful to see /var/log/apt/term.log from a system that
encounters this issue.

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

Title:
  Update stuck at “configuring unattended-upgrades”

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  On basically fresh install from ubuntu-16.04.1-desktop-amd64.iso; no
  updates or installs had been applied since installing the OS from the
  media.

  During execution of "Software Updater", it freezes indefinitely while
  "Installing updates..." at the step marked "Configuring unattended-
  upgrades."

  It appears that this happens if System Settings->Software &
  Updates->Updates, "Automatically check for updates" has been set to
  "Never."

  If that is instead set to "Daily" and the following are then set in
  /etc/apt/apt.conf.d/10periodic then the update succeeds:

  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Download-Upgradeable-Packages "1";
  APT::Periodic::AutocleanInterval "7";
  APT::Periodic::Unattended-Upgrade "1";

  Someone else had asked about this issue at AskUbuntu.  Their question
  along with my answer (from Kevin) provide some further details:

  http://askubuntu.com/questions/851371/update-stuck-at-configuring-
  unattended-upgrades-software-updater-turned-black/852110#852110

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

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

After more investigation, it seems like the 2 extra port-bindings port
assignation decision is made by "libdns" itself.

https://github.com/wklaebe/bind9/blob/ac1dcdd124a5abdec4969e2c33836d863bf73aa7/lib/dns/dispatch.c#L1921

--
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:
In Progress

Bug 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&t=95273&p=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 0.0.0.0:*
2659/dhclient
udp6 0 0 :::45664:::*
2659/dhclient

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

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

[Touch-packages] [Bug 1645352] [NEW] No HDMI output after upgrade to 16.04!

You have been subscribed to a public bug:

Running Ubuntu 16.04 64bit, 4.4.8 Kernel on an ASUS Trio with Intel® Haswell 
graphics card and using i915 driver. After upgrade there is no HDMI output to 
the external screen that I use daily. 
I did the following:
- Upgraded to  4.4.8 Kernel hoping that the issue would be resolved.
- Checked for other reports of this issue and followed advise to use NVIDIA 364 
drivers. 
- Checked Intel for the most recent driver which is already packaged with 
16.04;  it is the i915 driver which is in use.
- Used Intel driver update tool to ensure that update is correct.
- Purchased a HDMI adapter to use mini-display port; works and reports HDMI1 is 
in use, but HDMI2 is not recognized (when monitor is plugged in to HDMI2)
- Someone has assisted and has confirmed that there seems to be no hardware 
issues.

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


** Tags: bot-comment
-- 
No HDMI output after upgrade to 16.04!
https://bugs.launchpad.net/bugs/1645352
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

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

I suspect you don't have -updates enabled for universe in your
/etc/apt/sources.list file.  If you did you'd see the following:

 $ apt-cache policy vim-gtk3
vim-gtk3:
  Installed: (none)
  Candidate: 2:7.4.1689-3ubuntu1.1
  Version table:
 2:7.4.1689-3ubuntu1.1 500
500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages
 2:7.4.1689-3ubuntu1 500
500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages

vim-common and vim-runtime are in main and you seem to have -updates
enabled for that pocket.

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

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

Status in vim package in Ubuntu:
  Confirmed

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

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

  Now I get the following error:

  [[[ BEGIN PASTE ]]]

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

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

  [[[ END PASTE ]]]

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

  
  [[[ BEGIN PASTE ]]]

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

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

  [[[ END PASTE ]]]

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

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

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

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

[Touch-packages] [Bug 1645415] [NEW] Earphones not working on Ubuntu 16.04.1 after resume from suspend

2016-11-28 Thread Tapo

Public bug reported:

I am a new Ubuntu user and installed 16.04.1 LTS dual boot with Windows 10.
Recently I discovered that my earphones have a pulsating white noise after the 
machine is resumed from suspend. The laptop speakers are fine though. On reboot 
everything works fine.

I have tried restarting pulseaudio using following commands:
pulseaudio -k
pulseaudio --start

Also tried this:
/usr/bin/pasuspender /bin/true

But the pulsating sound persists.

My laptop model is ASUS ROG G501VW F1034T.

I have updated my system using commands:
sudo apt update
sudo apt upgrade

Please let me know if I need to provide outputs of commands or any
system logs.

Here is the "lsb_release -rd" command output: 
Description:Ubuntu 16.04.1 LTS
Release:16.04

** Affects: ubuntu
 Importance: Undecided
 Status: New

** Package changed: alsa-driver (Ubuntu) => ubuntu

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

Title:
  Earphones not working on Ubuntu 16.04.1 after resume from suspend

Status in Ubuntu:
  New

Bug description:
  I am a new Ubuntu user and installed 16.04.1 LTS dual boot with Windows 10.
  Recently I discovered that my earphones have a pulsating white noise after 
the machine is resumed from suspend. The laptop speakers are fine though. On 
reboot everything works fine.

  I have tried restarting pulseaudio using following commands:
  pulseaudio -k
  pulseaudio --start

  Also tried this:
  /usr/bin/pasuspender /bin/true

  But the pulsating sound persists.

  My laptop model is ASUS ROG G501VW F1034T.

  I have updated my system using commands:
  sudo apt update
  sudo apt upgrade

  Please let me know if I need to provide outputs of commands or any
  system logs.

  Here is the "lsb_release -rd" command output: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

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

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

[Touch-packages] [Bug 1645352] Re: No HDMI output after upgrade to 16.04!

** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  No HDMI output after upgrade to 16.04!

Status in xorg package in Ubuntu:
  New

Bug description:
  Running Ubuntu 16.04 64bit, 4.4.8 Kernel on an ASUS Trio with Intel® Haswell 
graphics card and using i915 driver. After upgrade there is no HDMI output to 
the external screen that I use daily. 
  I did the following:
  - Upgraded to  4.4.8 Kernel hoping that the issue would be resolved.
  - Checked for other reports of this issue and followed advise to use NVIDIA 
364 drivers. 
  - Checked Intel for the most recent driver which is already packaged with 
16.04;  it is the i915 driver which is in use.
  - Used Intel driver update tool to ensure that update is correct.
  - Purchased a HDMI adapter to use mini-display port; works and reports HDMI1 
is in use, but HDMI2 is not recognized (when monitor is plugged in to HDMI2)
  - Someone has assisted and has confirmed that there seems to be no hardware 
issues.

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

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

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-28 Thread Lorn Potter

I meant latest repo for qtsystems-opensource-src.

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

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions

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

[Touch-packages] [Bug 1645437] [NEW] Problem appear like Xorg

2016-11-28 Thread Cyrilux

Public bug reported:

In first, i working ubuntu16.04 on VirtualBox machine.Host is linux Mint
Cinnamon 17.3. I trying custom Ubuntu for Yosemite style whith help of
Noob's Lab. Lot of commands line don't work ! Maybe problem with Gtk3 ?

For examples: Gnome-Screenshot'captures are all black or back of screen
not the windows... During splash you can see a destroy picture like lot
of rays! and little others...

Sorry for my english (i'm french!!!) et thank you very much for you
work.

Cyril

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Nov 28 19:28:04 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2016-11-19 (9 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=17e79935-2f42-4abb-8d15-2246144b6d53 ro drm.debug=0xe quiet 
vesafb.invalid=1 nopat splash plymouth:debug
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Nov 28 19:26:22 2016
xserver.configfile: default
xserver.errors:
 AIGLX error: vboxvideo does not export required DRI extension
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 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/1645437

Title:
  Problem appear like Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  In first, i working ubuntu16.04 on VirtualBox machine.Host is linux
  Mint Cinnamon 17.3. I trying custom Ubuntu for Yosemite style whith
  help of Noob's Lab. Lot of commands line don't work ! Maybe problem
  with Gtk3 ?

  For examples: Gnome-Screenshot'captures are all black or back of
  screen not the windows... During splash you can see a destroy picture
  like lot of rays! and little others...

  Sorry for my english (i'm french!!!) et thank you very much for you
  work.

  Cyril

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Nov 28 19:28:04 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef]

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

I was able to identify from where the port range list is initialize, and the 
decision is taken by binary package "libdns162" (source package "bind9")[1] 
which dhclient relies on.
Basically, it randomly takes any port available between 1024 and 65535[2]

So there is a port randomization mechanism made by the library that take
the decision instead of, for instance in some other cases, where the
decision is leave it to the kernel[3].

In this particular case both sysctl options :
net.ipv4.ip_local_port_range
net.ipv4.ip_local_reserved_ports

have no effect on port assignation decision.

[1] - 
https://github.com/wklaebe/bind9/blob/ac1dcdd124a5abdec4969e2c33836d863bf73aa7/lib/dns/dispatch.c#L1921
[2] - https://tools.ietf.org/html/rfc6335
[3] - Example : net.ipv4.ip_local_port_range = 32768 60999

Regards,

-- 
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:
  In Progress

Bug 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&t=95273&p=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  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

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

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

So long story short, starting with Xenial you have the possibility to
install "isc-dhcp-client" which doesn't include the 2 extra port
bindings, but if you need it for Dynamic DNS (DDNS) you can optionally
install "isc-dhcp-client-ddns".

On Trusty, "isc-dhcp-client" combine both, and AFAIK, I don't think the
SRU process will allow the source package to be re-designed just like
Xenial to add this new binary package "isc-dhcp-client-ddns" in Trusty
archive, since this according to me falls under a feature request more
than fixing a bug.

-- 
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:
  In Progress

Bug 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&t=95273&p=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  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

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

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

So long story short, starting with Xenial you have the possibility to
install "isc-dhcp-client" which doesn't include the 2 extra port
bindings, but if you need it for Dynamic DNS (DDNS) you can optionally
install "isc-dhcp-client-ddns".

On Trusty, "isc-dhcp-client" combine both.

Will ask the SRU team if it would be acceptable to split up the binary
package in two to include changes (already applied in Xenial) to trusty.

-- 
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:
  In Progress

Bug 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&t=95273&p=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  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

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

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

[Touch-packages] [Bug 1643901] Re: flxdec security update tracking bug

2016-11-28 Thread Mathew Hodson

** No longer affects: gst-plugins-good0.10 (Ubuntu Yakkety)

** No longer affects: gst-plugins-good0.10 (Ubuntu Zesty)

** Changed in: gst-plugins-good0.10 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gst-plugins-good0.10 (Ubuntu)
   Status: Invalid => Fix Released

** No longer affects: gst-plugins-good1.0 (Ubuntu Precise)

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

Title:
  flxdec security update tracking bug

Status in gst-plugins-good0.10 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Confirmed
Status in gst-plugins-good0.10 source package in Precise:
  Fix Released
Status in gst-plugins-good0.10 source package in Trusty:
  Fix Released
Status in gst-plugins-good1.0 source package in Trusty:
  Fix Released
Status in gst-plugins-good0.10 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Yakkety:
  Fix Released
Status in gst-plugins-good1.0 source package in Zesty:
  Confirmed

Bug description:
  This bug is to track the security update to fix the flxdec out-of-
  bounds write.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1643901/+subscriptions

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

[Touch-packages] [Bug 1577596] Re: ntpd not started when using ntpdate

2016-11-28 Thread Ubuntu Foundations Team Bug Bot

The attachment "ntpdate_HH is a revised version of  /etc/network/if-
up.d/ntpdate" seems to be a patch.  If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Won't Fix

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions

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

[Touch-packages] [Bug 1610517] Re: package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade triggers looping

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

** Changed in: hicolor-icon-theme (Ubuntu)
   Status: New => Confirmed

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

Title:
  package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade
  triggers looping

Status in hicolor-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  While running a `do-release-upgrade` from Xubuntu 15.10 to 16.04
  something like a post-install hook apparently triggered looping.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-38-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Aug  6 11:48:42 2016
  Dependencies:
   
  DuplicateSignature: package:hicolor-icon-theme:0.15-0ubuntu1:triggers 
looping, abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-02-24 (893 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-06 (0 days ago)

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

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

[Touch-packages] [Bug 1610517] Re: package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade triggers looping

2016-11-28 Thread EdwardDyer

A number of errors of this type occurred during upgrade to 16.4.1 LTS

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

Title:
  package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade
  triggers looping

Status in hicolor-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  While running a `do-release-upgrade` from Xubuntu 15.10 to 16.04
  something like a post-install hook apparently triggered looping.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-38-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Aug  6 11:48:42 2016
  Dependencies:
   
  DuplicateSignature: package:hicolor-icon-theme:0.15-0ubuntu1:triggers 
looping, abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-02-24 (893 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-06 (0 days ago)

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

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

[Touch-packages] [Bug 1323837] Re: [phone] Sim toolkit is not available on UT

2016-11-28 Thread taiebot65

By reporting it to bq or meizu. I have not purchased a supported phone
but if I had I would have highlighted this.

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

Title:
  [phone] Sim toolkit is not available on UT

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  E.g. of SIm toolkit is http://support.vodafone.com.au/articles/FAQ
  /SIM-Toolkit

  While a lot of those addons are completely crap and useless, the SIm
  toolkit is sometimes used by some phone provider to set your sim card
  to roaming mode when you are abroad which makes it a must have.

  For the moment i need to borrow a second phone put my sim card in it,
  go to the Sim-toolkit, enable my sim card for roaming and put the sim
  card back in my UT to get my phone working while i am abroad. I need
  to do the same when i go back home.

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

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

[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

2016-11-28 Thread Michael Terry

** Also affects: maliit-framework (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  In Progress
Status in address-book-service package in Ubuntu:
  In Progress
Status in dialer-app package in Ubuntu:
  In Progress
Status in history-service package in Ubuntu:
  New
Status in indicator-bluetooth package in Ubuntu:
  In Progress
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  In Progress
Status in indicator-location package in Ubuntu:
  In Progress
Status in indicator-messages package in Ubuntu:
  In Progress
Status in indicator-network package in Ubuntu:
  In Progress
Status in indicator-power package in Ubuntu:
  In Progress
Status in indicator-session package in Ubuntu:
  In Progress
Status in indicator-sound package in Ubuntu:
  In Progress
Status in indicator-transfer package in Ubuntu:
  In Progress
Status in maliit-framework package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in pay-service package in Ubuntu:
  New
Status in policykit-unity8 package in Ubuntu:
  Fix Released
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  In Progress
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  In Progress
Status in unity-scope-scopes package in Ubuntu:
  Won't Fix
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

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

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

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-28 Thread Olivier Tilloy

I don’t know where that code lives.
https://code.launchpad.net/ubuntu/+source/qtsystems-opensource-src/ doesn’t 
have the latest changes it seems. Timo would know.

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

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions

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

> Will ask the SRU team if it would be acceptable to split up the binary
package in two to include changes (already applied in Xenial) to trusty.

I think that it's important that existing Trusty users can continue to
use this DDNS functionality after the SRU without any necessary
intervention. They may be depending on this functionality. If they have
to do something (such as install the additional package manually), then
that would be a regression and not acceptable in an SRU.

If there's a way to do the split such that users will automatically get
isc-dhcp-client-ddns installed but users bothered by this bug then have
the option to switch to the one without it, then that might work. But
perhaps it would be simpler to provide users a way to disable this
functionality manually? Is there any kind of runtime configuration
available?

-- 
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:
  In Progress

Bug 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&t=95273&p=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  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

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

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

[Touch-packages] [Bug 1644468] Re: pull to refresh text to bright on scopes with new theme

2016-11-28 Thread Michał Sawicz

** Branch linked: lp:~cimi/unity8/fix-pull-to-refresh-text-color

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

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

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Andrea Cimitan (cimi)

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

Title:
  pull to refresh text to bright on scopes with new theme

Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  the rc-proposed images recently got new scopes and a brighter theme.
  with this theme the "pull to refresh" text in the scopes became
  unreadable bright (see attached screenshot). the grey tone of the font
  is only very minimally brighter than the background. if we want to
  keep the text there it should be changed to have more contrast so it
  is readable.

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

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

[Touch-packages] [Bug 1645485] [NEW] very old display driver bug?

2016-11-28 Thread gregrwm

Public bug reported:

the most bothersome, most notable, and most curious symptom of this bug
is the absolute degree to which the display locks up.  xclock's seconds
are no longer changing, the mouse cursor won't move, and even ctl-alt-F1
does nothing.

meanwhile mplayer, playing in a hidden tmux window, is still playing
merrily along.

i logged in via sshd and copied this from htop:
0  [|100.0%] Tasks: 68; 3 running
1  [|| 1.3%] Load average: 1.00 0.91 
0.53
Mem[|973M/1.91G] Time: 14:26:17
Swp[   0K/1.86G]
  PID START USER   VIRT   RES  NI CPU%   TIME+  S Command
 1714 12:50 g 1713M  789M   0  0.0  6:37.92 S /usr/lib/firefox/firefox
 2368 14:07 g  661M 57252   0  0.0  0:03.33 S /usr/bin/python3 
/usr/bin/blueman-manager
  794 12:49 root   269M 54988   0 99.3 10:12.88 R /usr/lib/xorg/Xorg -core 
:0 -seat seat0 -auth /var/
 2385 14:07 g  583M 53524   0  0.0  0:00.39 S /usr/bin/python3 
/usr/bin/blueman-applet
 2397 14:07 g  555M 42968   0  0.0  0:10.68 S pavucontrol
 1926 12:57 g  282M 37752   0  0.7  0:02.46 S 
/usr/lib/firefox/plugin-container /opt/google/talkp
 1933 12:57 g  512M 36404   0  0.0  0:02.96 S 
/opt/google/talkplugin/GoogleTalkPlugin
 2403 14:07 g  823M 30352   0  0.0  0:03.52 S mplayer -ao pulse -af 
channels=2 -framedrop -msgcol
F1Help  F2Setup F3SearchF4FilterF5Tree  F6SortByF7Nice -F8Nice +F9Kill  F10Quit

ps also attached, taken before killing xorg.

i've filed this under xorg merely because xorg is the one stuck eating
all the CPU.  i really suspect the display driver, and don't know how to
find or identify that.

i much more commonly saw these very same symptoms when i used to run
xscreensaver.  i stopped running xscreensaver just to stop beating my
head against that wall.  but many years and many releases later, it
looks like this display driver bug is still lurking around.

there was hardly anything running when this froze.  i already mentioned
mplayer (sound only) and tmux, twm's the window manager, firefox was
running but iconized and idle tho running gmail and the googletalk
plugin, not that i suspect any of them in any way.  xterm was occupying
most of the screen, showing tmux, and idle.  the ones i'd more suspect
would be xclock & pavucontrol.  pavucontrol was hidden but busily
showing it's audio level bar, xclock was visible and displaying the time
of day including seconds, so the most likely one to have tripped a
display driver bug.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Nov 28 14:36:38 2016
InstallationDate: Installed on 2016-10-15 (43 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "ps taken before xorg killed"
   https://bugs.launchpad.net/bugs/1645485/+attachment/4784403/+files/ps

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

Title:
  very old display driver bug?

Status in xorg package in Ubuntu:
  New

Bug description:
  the most bothersome, most notable, and most curious symptom of this
  bug is the absolute degree to which the display locks up.  xclock's
  seconds are no longer changing, the mouse cursor won't move, and even
  ctl-alt-F1 does nothing.

  meanwhile mplayer, playing in a hidden tmux window, is still playing
  merrily along.

  i logged in via sshd and copied this from htop:
  0  [|100.0%] Tasks: 68; 3 running
  1  [|| 1.3%] Load average: 1.00 0.91 
0.53
  Mem[|973M/1.91G] Time: 14:26:17
  Swp[   0K/1.86G]
PID START USER   VIRT   RES  NI CPU%   TIME+  S Command
   1714 12:50 g 1713M  789M   0  0.0  6:37.92 S /usr/lib/firefox/firefox
   2368 14:07 g  661M 57252   0  0.0  0:03.33 S /usr/bin/python3 
/usr/bin/blueman-manager
794 12:49 root   269M 54988   0 99.3 10:12.88 R /usr/lib/xorg/Xorg 
-core :0 -seat seat0 -auth /var/
   2385 14:07 g  583M 53524   0  0.0  0:00.39 S /usr/bin/python3 
/usr/bin/blueman-applet
   2397 14:07 g  555M 42968   0  0.0  0:10.68 S pavucontrol
   1926 12:57 g  282M 37752   0  0.7  0:02.46 S 
/usr/lib/firefox/plugin-container /opt/google/talkp
   1933 12:57 g  512M 36404   0  0.0  0:02.96 S 
/opt/google/talkplugin/GoogleTalkPlugin
   24

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

> But perhaps it would be simpler to provide users a way to disable this
functionality manually? Is there any kind of runtime configuration
available?

At runtime, it doesn't seem to have a way, for instance, I already tried
the following without success: do-forward-updates false;

# man dhclient.conf
   If  you  want  to  do  DNS  updates  in the DHCP client script (see 
dhclient-script(8)) rather than having the DHCP client do the update directly 
(for example, if you want to use SIG(0) authentication, which is not supported 
directly by the DHCP client, you can
   instruct the client not to do the update using the do-forward-updates 
statement.  Flag should be true if you want the DHCP client to do the update, 
and false if you don't want the DHCP client to do the update.  By default,  the 
 DHCP  client  will  do  the  DNS
   update.

To disable the functionality at the moment for Trusty, manipulation in
the source package is required.

Undefine NSUPDATE in includes/site.h :

-#define NSUPDATE
+/* #define NSUPDATE */

and disabled failover and tracing in debian/rules :

./configure \
--prefix=/usr \
--sysconfdir=/etc/dhcp \
+   --disable-tracing \
+   --disable-failover \


Eric

-- 
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:
  In Progress

Bug 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&t=95273&p=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  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

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

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

[Touch-packages] [Bug 1576424] Re: Gimp crashes with text tool & caps lock

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

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

Title:
  Gimp crashes with text tool & caps lock

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Xenial:
  Fix Committed
Status in gtk+2.0 source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Gimp crashes with a segfault when I use caps lock while renaming a
  layer. It is possible Caps lock causes crashes in other events also.

  [Test Case]

  Steps to reproduce:

  1. Open a new blank gimp document
  2. select the text tool
  3. type a couple of words of text (gimp will create a text layer above the 
background layer)
  4. with the text tool still selected, click on the background layer (just to 
move away from the text layer)
  5. now double click on the text layer to rename the layer (layer name gets 
highlighted)
  6. press the caps lock key
  7. click on the background layer again (without renaming or doing anything to 
the text layer)
  Now repeat steps 5 and 6.
  Gimp crashes.

  [Regression Potential]

  None expected. The patch used has been taken from upstream
  development.

  
https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad

  Packages for Xenial and Yakkety have been built in a PPA and
  regression tested.

  [ Other Info ]

  I can force this to happen every time I launch Gimp. Rebooting makes
  no difference. It seems to be the second time I press caps lock that
  forces the crash. I tried launching Gimp with caps lock on vs caps
  lock off, but I don't believe it made any difference. I can force a
  crash every time following the above sequence.

  I deleted my gimp preferences folder then rebooted for good measure.
  Gimp created a fresh preferences folder, but it hasn't solved the
  problem. I was originally in single window mode, but the new
  preferences folder put me back to multi window, but it crashes either
  way.

  I ran dmesg | tail after the crash and got the following line:

  gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0
  error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000]

  I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver
  (available from the Additional Drivers tab). In that same tab, I also
  have enabled Processor microcode firmware for Intel CPUs. Terminal
  tells me Gimp version is 2.8.16-1ubuntu1

  I'm not very experienced with bug reporting and not sure what other
  information I need to supply. Gimp was absolutely rock solid on this
  machine with 15.10, so it may be a Xubuntu issue.

  Hope someone can take a look at this. Thanks.

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

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

[Touch-packages] [Bug 1576424] Re: Gimp crashes with text tool & caps lock

This bug was fixed in the package gtk+2.0 - 2.24.30-4ubuntu3

---
gtk+2.0 (2.24.30-4ubuntu3) yakkety; urgency=medium

  * debian/patches/lp1576424-explicitly-disconnect-keymap-signals.patch
- GtkEntry: Explicitly disconnect keymap signals. (LP: #1576424)

 -- Martin Wimpress   Tue, 04 Oct 2016
17:07:26 +0100

** Changed in: gtk+2.0 (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  Gimp crashes with text tool & caps lock

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Xenial:
  Fix Committed
Status in gtk+2.0 source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Gimp crashes with a segfault when I use caps lock while renaming a
  layer. It is possible Caps lock causes crashes in other events also.

  [Test Case]

  Steps to reproduce:

  1. Open a new blank gimp document
  2. select the text tool
  3. type a couple of words of text (gimp will create a text layer above the 
background layer)
  4. with the text tool still selected, click on the background layer (just to 
move away from the text layer)
  5. now double click on the text layer to rename the layer (layer name gets 
highlighted)
  6. press the caps lock key
  7. click on the background layer again (without renaming or doing anything to 
the text layer)
  Now repeat steps 5 and 6.
  Gimp crashes.

  [Regression Potential]

  None expected. The patch used has been taken from upstream
  development.

  
https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad

  Packages for Xenial and Yakkety have been built in a PPA and
  regression tested.

  [ Other Info ]

  I can force this to happen every time I launch Gimp. Rebooting makes
  no difference. It seems to be the second time I press caps lock that
  forces the crash. I tried launching Gimp with caps lock on vs caps
  lock off, but I don't believe it made any difference. I can force a
  crash every time following the above sequence.

  I deleted my gimp preferences folder then rebooted for good measure.
  Gimp created a fresh preferences folder, but it hasn't solved the
  problem. I was originally in single window mode, but the new
  preferences folder put me back to multi window, but it crashes either
  way.

  I ran dmesg | tail after the crash and got the following line:

  gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0
  error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000]

  I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver
  (available from the Additional Drivers tab). In that same tab, I also
  have enabled Processor microcode firmware for Intel CPUs. Terminal
  tells me Gimp version is 2.8.16-1ubuntu1

  I'm not very experienced with bug reporting and not sure what other
  information I need to supply. Gimp was absolutely rock solid on this
  machine with 15.10, so it may be a Xubuntu issue.

  Hope someone can take a look at this. Thanks.

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

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

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-28 Thread Lorn Potter

I can reproduce this on turbo.
Does not happen when running the inputinfo console app in qtsystem examples.

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

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions

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

[Touch-packages] [Bug 1645501] [NEW] corefiles not created in armhf chroot on arm64 porter