[Touch-packages] [Bug 1641175] Re: unity8 fails to build in arm64 because of tests segfault

[Albert Astals Cid]

Isn't this the "Qt doesn't like the new arm64 kernel" bug we already had
that made us revert the kernel?

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

Title:
  unity8 fails to build in arm64 because of tests segfault

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

Bug description:
  Recent builds of unity8 fails in arm64 because of this error

  See for example: https://launchpadlibrarian.net/293000651
  /buildlog_ubuntu-zesty-
  arm64.unity8_8.15+17.04.2016.1-0ubuntu1_BUILDING.txt.gz

  21/23 Test #18: testUtilsStyle ...***Exception:
  SegFault  0.43 sec

  https://launchpadlibrarian.net/292999853/buildlog_ubuntu-xenial-arm64
  .ubuntu-system-settings_0.4+16.04.2016-0ubuntu1_BUILDING.txt.gz

  29/29 Test #29: tst_notifications ...***Failed0.62 sec
  Segmentation fault (core dumped)

  (gdb) = End of stack trace ==
  QFATAL : TrustStoreModelTest::testEmpty() Received signal 11
   Function time: 6ms Total time: 7ms
  FAIL!  : TrustStoreModelTest::testEmpty() Received a fatal error.
 Loc: [Unknown file(0)]
  Totals: 1 passed, 1 failed, 0 skipped, 0 blacklisted
  * Finished testing of TrustStoreModelTest *
  Aborted (core dumped)

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

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

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Dave Hartley]

HP Elitebook 850 G3 with a fresh install of 16.04.1 had the suspend bug
(laptop would not suspend when the lid was closed).

Adding the line in login.confd worked for suspending, but I now have to
press the power button to resume from suspend. Opening the lid does not
resume.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  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
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

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

[Touch-packages] [Bug 765152] Re: spacenavd xserver permissions problem

[jf353]

This bug is still in 16.10 present and a systemd problem.
Because of this bug Freecad is not able to use 3d mouse.
Workaround (in terminal):
sudo service spacenavd stop
sudo /usr/bin/spacenavd -v -d
start freecad

The error message:
failed to open X11 display ":0.0"
results in the lack of the magellan protocol and
freecad needs it.

Testet on x86_64(16.10) and Aarm64(Odroid C2, 16.04).


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

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

Title:
  spacenavd xserver permissions problem

Status in spacenavd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Binary package hint: spacenavd

  spacenavd is not working log file is:

  Spacenav daemon 0.5
  using device: /dev/ttyS0
  trying to open X11 display ":0.0"
 XAUTHORITY=/root/.Xauthority
  No protocol specified
  failed to open X11 display ":0.0"
  waiting for X socket file to appear

  can be worked around with:
  sudo xhost +
  sudo /etc/init.d/spacenavd restart

  log file should look like:

  Spacenav daemon 0.5
  using device: /dev/ttyS0
  trying to open X11 display ":0"
 XAUTHORITY=/root/.Xauthority

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: spacenavd 0.5-1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Mon Apr 18 16:31:28 2011
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: spacenavd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1641505] Re: support adbd emergency shell under systemd

[Ubuntu Foundations Team Bug Bot]

The attachment "0001-Add-adbd-emergency-shell-systemd-support.patch"
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 lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1641505

Title:
  support adbd emergency shell under systemd

Status in Canonical System Image:
  New
Status in android-tools package in Ubuntu:
  In Progress
Status in lxc-android-config package in Ubuntu:
  In Progress

Bug description:
  Currently adbd emergency shell is only available under upstart, so
  some work is needed to bring it up under systemd as well.

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

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

[Touch-packages] [Bug 1608246] Re: Does not work button on the headphones to answer call's [Meizu PRO 5]

[leonidy-85]

Same issue with r221

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

Title:
  Does not work button on the headphones to answer call's  [Meizu PRO 5]

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  Call answer with headset button does not work.
  Checked on Meizu PRO 5 with OTA-12 and with several wired headset.
  PS: Works fine on BQ Aquaris e4.5 Ubuntu edition.

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

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

[Touch-packages] [Bug 1608246] Re: Does not work button on the headphones to answer call's [Meizu PRO 5]

[Launchpad Bug Tracker]

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

** Changed in: dialer-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Does not work button on the headphones to answer call's  [Meizu PRO 5]

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  Call answer with headset button does not work.
  Checked on Meizu PRO 5 with OTA-12 and with several wired headset.
  PS: Works fine on BQ Aquaris e4.5 Ubuntu edition.

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

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

[Touch-packages] [Bug 1641547] [NEW] ubuntu-bug: Segmentation fault (core dumped)

[Uqbar]

Public bug reported:

The command is: ubuntu-bug apport
The browser starts and after a while I get this on the console:

Segmentation fault (core dumped)

I have given a look to the core, but I have no clue on the error:

[enzo@Feynman ~] file core 
core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from 
'/usr/bin/python3 /usr/share/apport/apport-kde libpam-runtime'
[enzo@Feynman ~] gdb /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 9053]
[New LWP 9054]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/python3 /usr/share/apport/apport-kde 
libpam-runtime'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fa6b3d370f5 in ?? () from 
/usr/lib/python3/dist-packages/PyQt5/QtCore.cpython-35m-x86_64-linux-gnu.so
[Current thread is 1 (Thread 0x7fa6b7fd8700 (LWP 9053))]
(gdb) bt
#0  0x7fa6b3d370f5 in ?? () from 
/usr/lib/python3/dist-packages/PyQt5/QtCore.cpython-35m-x86_64-linux-gnu.so
#1  0x7fa6b392da27 in QObject::~QObject() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fa6afd8fe28 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#3  0x7fa6b782bff8 in __run_exit_handlers (status=1, listp=0x7fa6b7bb55f8 
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#4  0x7fa6b782c045 in __GI_exit (status=) at exit.c:104
#5  0x005fef1f in Py_Exit ()
#6  0x005ff00a in ?? ()
#7  0x005ff076 in PyErr_PrintEx ()
#8  0x005ffd39 in PyRun_SimpleFileExFlags ()
#9  0x0063f886 in Py_Main ()
#10 0x004d00e1 in main ()


I attach the xz-ipped core.
It happens every time.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.1
Uname: Linux 4.8.7-040807-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashReports:
 640:1000:114:1497199:2016-11-13 17:05:21.636583884 +0100:2016-11-13 
17:05:20.352581887 +0100:/var/crash/_usr_bin_kactivitymanagerd.1000.crash
 640:1000:114:12194639:2016-11-14 10:02:23.067422551 +0100:2016-11-14 
10:02:23.068422553 +0100:/var/crash/_usr_share_apport_apport-kde.1000.crash
CurrentDesktop: KDE
Date: Mon Nov 14 10:07:19 2016
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "The dumped core"
   https://bugs.launchpad.net/bugs/1641547/+attachment/4777136/+files/core.xz

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

Title:
  ubuntu-bug: Segmentation fault (core dumped)

Status in apport package in Ubuntu:
  New

Bug description:
  The command is: ubuntu-bug apport
  The browser starts and after a while I get this on the console:

  Segmentation fault (core dumped)

  I have given a look to the core, but I have no clue on the error:

  [enzo@Feynman ~] file core 
  core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from 
'/usr/bin/python3 /usr/share/apport/apport-kde libpam-runtime'
  [enzo@Feynman ~] gdb /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 f

[Touch-packages] [Bug 1639745] Re: Mir GL clients never appear at all on VirtualBox

[Daniel van Vugt]

** Branch linked: lp:~vanvugt/mir/handle-buffer-allocation-failure

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

Title:
  Mir GL clients never appear at all on VirtualBox

Status in Mir:
  In Progress
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Mir GL clients never appear at all on VirtualBox.

  After digging for a while, it appears the issue is that vboxvideo does
  not support DRM_CAP_PRIME and so only supports GEM flink names. Sadly
  Mir is the opposite now: Mir only supports PRIME but not flink names.

  Internally some exceptions are being thrown in Mir at present, but we
  seem to catch and silence them all. So you never see any error
  messages at all. Just Mir GL clients never appear on screen in
  VirtualBox.

  For the record, Wayland supports falling back to flink names in the
  absence of PRIME. We should too.

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

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

[Touch-packages] [Bug 765152] Re: spacenavd xserver permissions problem

[Martin Pitt]

** No longer affects: systemd (Ubuntu)

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

Title:
  spacenavd xserver permissions problem

Status in spacenavd package in Ubuntu:
  New

Bug description:
  Binary package hint: spacenavd

  spacenavd is not working log file is:

  Spacenav daemon 0.5
  using device: /dev/ttyS0
  trying to open X11 display ":0.0"
 XAUTHORITY=/root/.Xauthority
  No protocol specified
  failed to open X11 display ":0.0"
  waiting for X socket file to appear

  can be worked around with:
  sudo xhost +
  sudo /etc/init.d/spacenavd restart

  log file should look like:

  Spacenav daemon 0.5
  using device: /dev/ttyS0
  trying to open X11 display ":0"
 XAUTHORITY=/root/.Xauthority

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: spacenavd 0.5-1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Mon Apr 18 16:31:28 2011
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: spacenavd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1641549] [NEW] migrate lxc android container to lxd

[Vicamo Yang]

Public bug reported:

Several things to do here:
* include lxd, lxd-client in default installation,
* writable path for lxd: lxd resides at /var/lib/lxd and it takes write 
permission to fully function,
* migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, 
etc.,
* migrate systemd service definitions, etc.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: lxc-android-config (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: lxd systemd

** Description changed:

  Several things to do here:
- * writable path for lxd: lxd resides at /var/lib/lxd and it takes write 
permission to fully function.
- * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, 
etc.
+ * include lxd, lxd-client in default installation,
+ * writable path for lxd: lxd resides at /var/lib/lxd and it takes write 
permission to fully function,
+ * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, 
etc.,
  * migrate systemd service definitions, etc.

** Also affects: lxc-android-config (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: lxd systemd

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

Title:
  migrate lxc android container to lxd

Status in Canonical System Image:
  New
Status in lxc-android-config package in Ubuntu:
  New

Bug description:
  Several things to do here:
  * include lxd, lxd-client in default installation,
  * writable path for lxd: lxd resides at /var/lib/lxd and it takes write 
permission to fully function,
  * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, 
etc.,
  * migrate systemd service definitions, etc.

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

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

[Touch-packages] [Bug 1641561] [NEW] make android lxc as a snap

[Vicamo Yang]

Public bug reported:

With snapd running in current Ubuntu Touch Xenial port, we'd like to
package whole android container as a snap for the final all-snap target.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: lxc-android-config (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: lxc-android-config (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  make android lxc as a snap

Status in Canonical System Image:
  New
Status in lxc-android-config package in Ubuntu:
  New

Bug description:
  With snapd running in current Ubuntu Touch Xenial port, we'd like to
  package whole android container as a snap for the final all-snap
  target.

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

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

[Touch-packages] [Bug 1641561] Re: make android lxc as a snap

[Vicamo Yang]

http://bazaar.launchpad.net/~timo-jyrinki/+junk/uitk-
gallery/view/head:/snapcraft.yaml reference for snappy content
interface.

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

Title:
  make android lxc as a snap

Status in Canonical System Image:
  New
Status in lxc-android-config package in Ubuntu:
  New

Bug description:
  With snapd running in current Ubuntu Touch Xenial port, we'd like to
  package whole android container as a snap for the final all-snap
  target.

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

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

[Touch-packages] [Bug 1641561] Re: make android lxc as a snap

[Vicamo Yang]

With bug 1641549, we're also trying to migrate current lxc-based android
container to lxd image. Snap interface to access lxd is in bug 1634880.

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

Title:
  make android lxc as a snap

Status in Canonical System Image:
  New
Status in lxc-android-config package in Ubuntu:
  New

Bug description:
  With snapd running in current Ubuntu Touch Xenial port, we'd like to
  package whole android container as a snap for the final all-snap
  target.

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

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

[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

[goran]

it seems that dnsmasq is creating this problem. Is it possible to setup
dnsmasq resolving multiple DNS for IP?

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Incomplete
Status in openvpn package in Ubuntu:
  Incomplete

Bug description:
  [Triage Notes]

  This bug can no longer make progress. Please see comment 50 for
  details and further instructions.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

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

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

[Touch-packages] [Bug 1631519] Re: No X on boot with external monitor connected

[Chris Taylor]

I have tried isotope's fix of adding to /usr/share/X11/xorg.conf.d/ a
file named 20-intel.conf with the following:

Section "Device"
   Identifier "Intel Graphics"
   Driver "intel"
EndSection

The fix works for me: X now starts on boot with my two external monitors
plugged in.

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

Title:
  No X on boot with external monitor connected

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When booting from today's (201610907) daily yakkety livecd with an
  external display attached X does not start.

  If the external monitor is attached after X has started I can boot to
  the desktop using only using the laptop's LCD (ThinkPad x230, intel
  graphics).  The attaching a 1920x1080 LCD via miniDP extends the
  desktop but windows moved around produce a trail of windows that
  persist even after the window is closed.

  This is a regression from Xenial.

  $ lsb_release -rd
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10

  $ apt-cache policy xorg
  xorg:
    Installed: 1:7.7+13ubuntu4
    Candidate: 1:7.7+13ubuntu4
    Version table:
   *** 1:7.7+13ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.379
  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: Fri Oct  7 20:23:46 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007)
  MachineType: LENOVO 2306CTO
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  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:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  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-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  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: Fri Oct  7 20:18:12 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1622893] Re: NetworkManager takes very long to start, or times out, blocked on RNG

[Bug Watch Updater]

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

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

Title:
  NetworkManager takes very long to start, or times out, blocked on RNG

Status in Auto Package Testing:
  Fix Released
Status in gnutls28 package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New
Status in network-manager package in Debian:
  Fix Released

Bug description:
  Since a few days ago, NetworkManager.service takes awfully long to
  start, or even times out on failure and then gets restarted. This
  happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the
  systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes
  due to the NM timeout.

  In the journal there is no actual logging from
  /usr/sbin/NetworkManager yet, just the start timeout.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.2-0ubuntu8
  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
  CurrentDesktop: i3
  Date: Tue Sep 13 10:05:05 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/auto-package-testing/+bug/1622893/+subscriptions

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

[Touch-packages] [Bug 1639745] Re: Mir GL clients never appear at all on VirtualBox

[Daniel van Vugt]

** Branch linked: lp:~vanvugt/mir/reply-buffer-allocation-failures

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

Title:
  Mir GL clients never appear at all on VirtualBox

Status in Mir:
  In Progress
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Mir GL clients never appear at all on VirtualBox.

  After digging for a while, it appears the issue is that vboxvideo does
  not support DRM_CAP_PRIME and so only supports GEM flink names. Sadly
  Mir is the opposite now: Mir only supports PRIME but not flink names.

  Internally some exceptions are being thrown in Mir at present, but we
  seem to catch and silence them all. So you never see any error
  messages at all. Just Mir GL clients never appear on screen in
  VirtualBox.

  For the record, Wayland supports falling back to flink names in the
  absence of PRIME. We should too.

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

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

[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd

[Vicamo Yang]

Again, avila's kernel is pretty outdated, and its user namespace support
is so poor that it's actually mis-behave on a certain security related
operations.

In security/commoncap.c, function cap_prctl_drop, it should check
`ns_capable(...)`, not just `capable(...)`. See
https://github.com/lxc/lxd/issues/2039 . At lease commit 160da84
"userns: Allow PR_CAPBSET_DROP in a user namespace" has to be cherry-
picked, but besides that, I also found a lot similar places to be fixed.

** Bug watch added: LXD bug tracker #2039
   https://github.com/lxc/lxd/issues/2039

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

Title:
  migrate lxc android container to lxd

Status in Canonical System Image:
  New
Status in lxc-android-config package in Ubuntu:
  New

Bug description:
  Several things to do here:
  * include lxd, lxd-client in default installation,
  * writable path for lxd: lxd resides at /var/lib/lxd and it takes write 
permission to fully function,
  * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, 
etc.,
  * migrate systemd service definitions, etc.

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

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

[Touch-packages] [Bug 1637758] Re: lightdm greeter session not properly shut down at login

[Launchpad Bug Tracker]

** Branch linked: lp:~pitti/lightdm/cleanup-session

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

Title:
  lightdm greeter session not properly shut down at login

Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  I am using lightdm with 2 seats. After 2409 revision randomly one of
  two seats does not work correctly.

  xsettings plugin from unity-settings-daemon or gnome-settings-deamon
  fails to start because there is already _XSESSION_S* manager running.

  After revision 2409 in system monitor I see that there is still
  running unity-settings-daemon started by lightdm. Reverting this
  revision fixes my problem.

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

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

[Touch-packages] [Bug 1637758] Re: lightdm greeter session not properly shut down at login

[Martin Pitt]

** No longer affects: systemd (Ubuntu)

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

Title:
  lightdm greeter session not properly shut down at login

Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  I am using lightdm with 2 seats. After 2409 revision randomly one of
  two seats does not work correctly.

  xsettings plugin from unity-settings-daemon or gnome-settings-deamon
  fails to start because there is already _XSESSION_S* manager running.

  After revision 2409 in system monitor I see that there is still
  running unity-settings-daemon started by lightdm. Reverting this
  revision fixes my problem.

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

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

[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

[GeyerA]

I flashed on Mako already months ago and experienced issues with my
Alpine car stereo. Now flashed again latest release and connected to my
BMW F31 multimedia system. All seemed fine after pairing but then the
multimedia launched a call showing "**" as the destination number.
Radio obviously stopped playing but no message on the phone. I removed
the device and paired again but also then, again launched the call in
the car with the *** as a destination. If somebody can instruct me
how to run a log file, just let me know.

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

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

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

[Touch-packages] [Bug 1641578] [NEW] can enter spread while in emergency dialer in greeter

[Michael Zanetti]

Public bug reported:

Steps to reproduce:

* lock the device
* from the lockscreen, open the emergency dialoer
* do a right edge swipe

=> spread is shown

during a lockdown, nothing but the dialer app should be shown

** Affects: canonical-devices-system-image
 Importance: Critical
 Assignee: Michał Sawicz (saviq)
 Status: In Progress

** Affects: unity8 (Ubuntu)
 Importance: Critical
 Assignee: Michael Zanetti (mzanetti)
 Status: In Progress

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

Title:
  can enter spread while in emergency dialer in greeter

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

Bug description:
  Steps to reproduce:

  * lock the device
  * from the lockscreen, open the emergency dialoer
  * do a right edge swipe

  => spread is shown

  during a lockdown, nothing but the dialer app should be shown

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

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

[Touch-packages] [Bug 1641578] Re: can enter spread while in emergency dialer in greeter

[Michał Sawicz]

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

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Zanetti (mzanetti)

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

** Changed in: canonical-devices-system-image
Milestone: None => 14

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

Title:
  can enter spread while in emergency dialer in greeter

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

Bug description:
  Steps to reproduce:

  * lock the device
  * from the lockscreen, open the emergency dialoer
  * do a right edge swipe

  => spread is shown

  during a lockdown, nothing but the dialer app should be shown

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

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

[Martin Pitt]

For the record: Commit 0b14bf7a is not sufficient. That neither fixes
"losetup" nor "mount -o loop", and systemd's .mount units also just get
translated into a /bin/mount -o loop" call.

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

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 in
  http://git.kernel.org/cgit/utils/util-linux/util-
  linux.git/commit/?id=0b14bf7a

  SRU TEST CASE: (FIXME: this does not actually get fixed with the above commit)
  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:
  $ sudo mount -o loop /etc/issue /mnt

  With current trusty's util-linux this will fail with "could not find
  any free loop device". With the proposed version, this should "only"
  fail with "you must specify the filesystem type" (or try it on an
  actual file system image).

  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 1622893] Re: NetworkManager takes very long to start, or times out, blocked on RNG

[Martin Pitt]

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

** Changed in: gnutls28 (Ubuntu)
   Status: Triaged => In Progress

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

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

Title:
  NetworkManager takes very long to start, or times out, blocked on RNG

Status in Auto Package Testing:
  Fix Released
Status in gnutls28 package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager package in Debian:
  Fix Released

Bug description:
  Since a few days ago, NetworkManager.service takes awfully long to
  start, or even times out on failure and then gets restarted. This
  happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the
  systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes
  due to the NM timeout.

  In the journal there is no actual logging from
  /usr/sbin/NetworkManager yet, just the start timeout.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.2-0ubuntu8
  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
  CurrentDesktop: i3
  Date: Tue Sep 13 10:05:05 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/auto-package-testing/+bug/1622893/+subscriptions

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

[Touch-packages] [Bug 1641578] Re: can enter spread while in emergency dialer in greeter

[Launchpad Bug Tracker]

** Branch linked: lp:~mzanetti/unity8/disable-spread-while-locked

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

Title:
  can enter spread while in emergency dialer in greeter

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

Bug description:
  Steps to reproduce:

  * lock the device
  * from the lockscreen, open the emergency dialoer
  * do a right edge swipe

  => spread is shown

  during a lockdown, nothing but the dialer app should be shown

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

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

[Touch-packages] [Bug 1641072] Re: Side stage not restored after rotation

[Michał Sawicz]

I agree, side stage should only be dismissed by explicit user action
(i.e. swiping it away).

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

Title:
  Side stage not restored after rotation

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  bq M10 silo #2177

  Steps to reproduce:
  1. In landscape add an app to the side stage
  2. Make sure the side stage is not focused
  3. Rotate to portrait and back to landscape

  Expected result:
  Both the side stage and main app are visible, like before rotation

  What happens instead:
  Only the main app is visible, the side stage is hidden

  I understand this behaviour could be intentional but imo it'd be
  better if the side stage was restored even if the app there was not
  focused. My reasons: rotation could be made by accident (for example
  when carrying the device), even if I intentionally made the rotation,
  I don't expect to lose my windows arrangement.

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

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

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Łukasz Zemczak]

@Shay: yes, we will prepare an SRU to the currently supported series
soon - but please note that the current 'fix' is, in fact, just a
workaround. But it works.

@Simon: I can try finding some people that could reproduce this easily,
prepare patched-up version of dbus with both the proposed fixes and ask
them to run tests on them. Would be really cool if a real fix could be
found this way. I'll take care of this this week and send feedback here
and the upstream bug.

Thanks again for looking into this further Simon!

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Unknown
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Confirmed
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1533251] Re: Ubuntu phone / Aquaris E5: no ringtones when receiving calls, no sound when receiving messages; no sound on speakers

[Andrea Simonetti]

I can not replicate it . It seems like some times the phone come to a loop and 
until it is not finished , it wont turn on the big speaker.
Can this be helpful?

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

Title:
  Ubuntu phone / Aquaris E5: no ringtones when receiving calls, no sound
  when receiving messages; no sound on speakers

Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Aquaris E5 HD, Ubuntu Edition; Ubuntu 15.04, OTA-8.5

  My phone does not ring / play sound on speakers. No problems to answer
  calls, when having notice by vibrating / display notification; Have
  phone for some weeks now - at very beginning it worked; short after it
  stopped playing sounds; swithched sound on in pathwind & uninstalled
  pathwind - no difference; sometimes it plays ringtones - but have no
  idea under which circumstances; even when it rang for one time it does
  not anymore one call later, although I did not make any changes in
  settings between the calls; does not play sounds / ringtones when
  selecting them in settings (no difference which ringtone).

  Today I made full reset on phone (by Settings) - still no sounds.

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

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

[Touch-packages] [Bug 1543467] Re: Unity8 can't correctly display multi-surface apps (i.e. menus and tooltips)

[Daniel d'Andrada]

** Branch linked: lp:~gerboland/qtubuntu/windows-hidden-on-creation

** Branch linked: lp:~gerboland/qtubuntu/rasterGLSurface-fixes

** Branch linked: lp:~gerboland/qtubuntu/add--more-surface-type-support

** Branch linked: lp:~gerboland/qtubuntu/active-decision-refactor

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

** Changed in: qtubuntu
   Status: New => In Progress

** Changed in: qtubuntu
 Assignee: (unassigned) => Gerry Boland (gerboland)

** Branch linked: lp:~dandrader/unity8/childWindows

** Branch linked: lp:~dandrader/qtmir/miral-childWindows

** Changed in: unity8 (Ubuntu)
 Assignee: Nick Dedekind (nick-dedekind) => Daniel d'Andrada (dandrader)

** Changed in: qtmir (Ubuntu)
 Assignee: Nick Dedekind (nick-dedekind) => Daniel d'Andrada (dandrader)

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

Title:
  Unity8 can't correctly display multi-surface apps (i.e. menus and
  tooltips)

Status in Canonical System Image:
  Triaged
Status in QtMir:
  Triaged
Status in qtubuntu:
  In Progress
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Unity8 can't display multi-surface apps (including menus and
  tooltips).

  Fixing bug 1497085 was a great start. However instead of crashing
  Unity8 now just shows the most recently created window by the app in
  the apps /single window/, and stretches it too. When such a secondary
  window like a menu or tooltip closes, you never get back to the
  original app window. So existing apps still aren't quite usable yet.

  Test case:
  sudo apt-get install mir-demos
  mir_demo_client_multiwin -- --desktop_file_hint=unity8

  Expected: Three windows (red, green, blue)
  Observed: Only the blue window

  You can also experience the same bug with lots of apps via:  Xmir
  -rootless under Unity8.

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

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

[Touch-packages] [Bug 1281700] Re: policykit-1 is not aware of groups assigned by pam_group

[Tobias Volfing]

I am affected by this as well. I want my LDAP users to be able to manage
printers. I've tried removing authentication in cupsd.conf, this works
for the CUPS interface. But not from 'Printers' in system settings. So
instead I've added them to the lpadmin group with the pam mount module,
but it is still not possible.

As noted in another comment, id shows the user being a member of
lpadmin, but id username doesn't.

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

Title:
  policykit-1 is not aware of groups assigned by pam_group

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  I'm using pam_group for my ldap users so that they get assigned default 
ubuntu groups:
  $ tail -n2 /etc/security/group.conf

  # add LDAP users to these default groups, but don't give them admin rights.
  "*;*;*;Al-2400;audio,video,cdrom,plugdev,fuse"

  These additional group IDs are assigned correctly:

  $ id
  uid=6007(myusername) gid=6000(ldapgroup) 
groups=6000(ldapgroup),24(cdrom),29(audio),44(video),46(plugdev),104(fuse)

  Based on these additional groups, I'm trying to give certain user
  groups the necessary permissions to execute program, using
  policykit-1. Unfortunately, policykit does seem to only 'see' / 'be
  aware' of the primary group that the user belongs to (and not those
  additional groups that are assigend via /etc/security/group.conf).

  This works (users can start the program):
  [AllowUsertoDoSomething]
  Identity=unix-group:ldapgroup

  This doesn't work (users are asked to provide the administrator password):
  [AllowUsertoDoSomething]
  Identity=unix-group:plugdev

  I suspect that this has something to do with the fact that 'id' does
  return conflicting information about groups:

  # call id without username, returns all groups, including the ones defined in 
/etc/security/group.conf
  $ id
  uid=6007(myusername) gid=6000(ldapgroup) 
groups=6000(ldapgroup),24(cdrom),29(audio),44(video),46(plugdev),104(fuse)

  # call id with username, only ldap groups are returned, the ones defined in 
/etc/security/group.conf are missing.
  $ id myusername
  uid=6007(myusername) gid=6000(ldapgroup) groups=6000(ldapgroup)

  My suspicion is that policykit-1 is calling "id user" (or a similar command) 
and "sees" only the main ldap groups.
  I did not expect this behavior, because /etc/pam.d/polkit-1 does include 
/etc/pam.d/common-auth (which includes the "auth optional pam_group.so" line)

  This is Ubuntu 12.04.3 with all latest updates. Any help and
  suggestions are appreciated.

  $ lsb_release -rd
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04

  $ apt-cache policy policykit-1
  policykit-1:
    Installed: 0.104-1ubuntu1.1
    Candidate: 0.104-1ubuntu1.1
  ---
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  MarkForUpload: True
  NonfreeKernelModules: nvidia
  Package: policykit-1 0.104-1ubuntu1.1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-41.64~precise1-generic 3.5.7.21
  Tags:  precise
  Uname: Linux 3.5.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1641578] Re: can enter spread while in emergency dialer in greeter

[Michał Sawicz]

** Branch linked: lp:~mzanetti/unity8/disable-spread-while-locked-stable

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

Title:
  can enter spread while in emergency dialer in greeter

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

Bug description:
  Steps to reproduce:

  * lock the device
  * from the lockscreen, open the emergency dialoer
  * do a right edge swipe

  => spread is shown

  during a lockdown, nothing but the dialer app should be shown

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

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

[Touch-packages] [Bug 1622893] Re: NetworkManager takes very long to start, or times out, blocked on RNG

[Martin Pitt]

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

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

Title:
  NetworkManager takes very long to start, or times out, blocked on RNG

Status in Auto Package Testing:
  Fix Released
Status in gnutls28 package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager package in Debian:
  Fix Released

Bug description:
  Since a few days ago, NetworkManager.service takes awfully long to
  start, or even times out on failure and then gets restarted. This
  happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the
  systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes
  due to the NM timeout.

  In the journal there is no actual logging from
  /usr/sbin/NetworkManager yet, just the start timeout.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.2-0ubuntu8
  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
  CurrentDesktop: i3
  Date: Tue Sep 13 10:05:05 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/auto-package-testing/+bug/1622893/+subscriptions

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

[Touch-packages] [Bug 1641592] [NEW] nano 2.5.3-2 on Xenial crashes with long paths on lockfiles

[Antti Tönkyrä]

Public bug reported:

# lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
# apt-cache policy nano
nano:
  Installed: 2.5.3-2
  Candidate: 2.5.3-2

Reproducer:
1. # nano -G 
999
2. 
3. # nano -G 
999
4. 
5. 

Quick dissection:
Looking at function do_lockfile in files.c, it seems that promptstr is 
statically allocated to 128 characters. Now with a sufficiently long filename, 
the following sprintf() call will overflow the allocated promptstr buffer and 
corrupt memory.

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

** Summary changed:

- nano 2.5.3-2 on Xenial crashes when trying to access a lockfile
+ nano 2.5.3-2 on Xenial crashes with long paths on lockfiles

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

Title:
  nano 2.5.3-2 on Xenial crashes with long paths on lockfiles

Status in nano package in Ubuntu:
  New

Bug description:
  # lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  # apt-cache policy nano
  nano:
Installed: 2.5.3-2
Candidate: 2.5.3-2

  Reproducer:
  1. # nano -G 
999
  2. 
  3. # nano -G 
999
  4. 
  5. 

  Quick dissection:
  Looking at function do_lockfile in files.c, it seems that promptstr is 
statically allocated to 128 characters. Now with a sufficiently long filename, 
the following sprintf() call will overflow the allocated promptstr buffer and 
corrupt memory.

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

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

[Touch-packages] [Bug 1398560] Re: Music playback randomly stops working

[Andrea Simonetti]

Hello.. Is this last one a permanent solution?

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

Title:
  Music playback randomly stops working

Status in Canonical System Image:
  Fix Released
Status in Media Hub:
  Invalid
Status in qtubuntu-camera:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu RTM:
  Fix Released

Bug description:
  While listening to music media-hub stops randomly. Restart of the job
  and reboots don't fix it. Video works fine. Also, 320 kbps music
  pauses randomly, might be related. I have also talked about this on
  the mailing list.

  This is probably a side effect of bug 1438486 (or similar), as pulse
  is working but without sound just for the multimedia related roles.

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

-- 
Mailing list: https://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 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Pablo Carranza]

We can try the proposed patched version in one worker at gitlab. It will
get stressed quite fast

On Nov 14, 2016 13:25, "Łukasz Zemczak" <1591...@bugs.launchpad.net>
wrote:

> @Shay: yes, we will prepare an SRU to the currently supported series
> soon - but please note that the current 'fix' is, in fact, just a
> workaround. But it works.
>
> @Simon: I can try finding some people that could reproduce this easily,
> prepare patched-up version of dbus with both the proposed fixes and ask
> them to run tests on them. Would be really cool if a real fix could be
> found this way. I'll take care of this this week and send feedback here
> and the upstream bug.
>
> Thanks again for looking into this further Simon!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1591411
>
> Title:
>   systemd-logind must be restarted every ~1000 SSH logins to prevent a
>   ~25 second delay
>
> Status in D-Bus:
>   Unknown
> Status in systemd:
>   Unknown
> Status in dbus package in Ubuntu:
>   Fix Released
> Status in systemd package in Ubuntu:
>   Fix Released
> Status in dbus source package in Xenial:
>   Confirmed
> Status in systemd source package in Xenial:
>   Invalid
> Status in dbus source package in Yakkety:
>   Confirmed
> Status in systemd source package in Yakkety:
>   Invalid
>
> Bug description:
>   I noticed on a system that accepts large numbers of SSH connections
>   that after awhile, SSH sessions were taking ~25 seconds to complete.
>
>   Looking in /var/log/auth.log, systemd-logind starts failing with the
>   following:
>
>   Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened
> for user ubuntu by (uid=0)
>   Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user
> ubuntu.
>   Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session
> scope: Transport endpoint is not connected
>   Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to
> create session: Message recipient disconnected from message bus without
> replying
>
>   I reproduced this in an LXD container by doing something like:
>
>   lxc launch ubuntu:x test
>   lxc exec test -- login -f ubuntu
>   ssh-import-id 
>
>   Then ran a script as follows (passing in ubuntu@):
>
>   while [ 1 ]; do
>   (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
>   done
>
>   In my case, after 1052 logins, the 1053rd and thereafter were taking
>   25+ seconds to complete. Here are some snippets from the log file:
>
>   $ cat log | grep 0m0 | wc -l
>   1052
>
>   $ cat log | grep 0m25 | wc -l
>   4
>
>   $ tail -5 log
>   real  0m0.222s
>   real  0m25.232s
>   real  0m25.235s
>   real  0m25.236s
>   real  0m25.239s
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: systemd 229-4ubuntu5
>   ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
>   Uname: Linux 4.4.0-22-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2
>   Architecture: amd64
>   Date: Sat Jun 11 00:09:34 2016
>   MachineType: Notebook W230SS
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic
> root=/dev/mapper/ubuntu--vg-root ro quiet splash
>   SourcePackage: systemd
>   SystemdDelta:
>[EXTENDED]   /lib/systemd/system/rc-local.service →
> /lib/systemd/system/rc-local.service.d/debian.conf
>[EXTENDED]   /lib/systemd/system/systemd-timesyncd.service →
> /lib/systemd/system/systemd-timesyncd.service.d/disable-
> with-time-daemon.conf
>
>2 overridden configuration files found.
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/15/2014
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 4.6.5
>   dmi.board.asset.tag: Tag 12345
>   dmi.board.name: W230SS
>   dmi.board.vendor: Notebook
>   dmi.board.version: Not Applicable
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Notebook
>   dmi.chassis.version: N/A
>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:
> svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:
> rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
>   dmi.product.name: W230SS
>   dmi.product.version: Not Applicable
>   dmi.sys.vendor: Notebook
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dbus/+bug/1591411/+subscriptions
>

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Unknown
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Con

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

[ChristianEhrhardt]

Thanks Colin for making the allocation and outlining the details of
base-passswd handling.

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  <...>

  Please see comments for the problem description, and summary of
  originally bridged comments in the description.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1623666] Re: iOS10 will not connect to Ubuntu

[J. McDonald]

Sam Gleske, with all due respect, that is not an really an answer.  I am
an end user, not a code developer, but I understood the basics of the
problem with the package being built with GnuTLS instead of the correct
version of OpenSSL. You are also incorrect with respect to
libimobiledevice being fixed within the Ubuntu 16.04 repositories.  The
most recent version still has this bug and I confirmed that it still
does not work either in Ubuntu 16.04 or the related Mint 18.

A patch was suggested as a solution, but the linked patch provided no clear, 
understandable (at least to me, an end user) description of how to install it.  
I did find a very helpful solution here:
https://answers.launchpad.net/ubuntu/+source/libimobiledevice/+question/402748

which provided a link to a ppa with updated versions of libimobiledevice
for Ubuntu 14.04 and 16.04 using OpenSSL at the following URL:
https://launchpad.net/~martin-
salbaba/+archive/ubuntu/ppa+libimobiledevice

I installed the version from the PPA, unpaired and paired the phone, and
confirmed that it works at least in my case (Mint 18 & Ubuntu 16.04,
iPhone 5c, and iOS10.1).

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

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

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

[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional

[Paweł Stołowski]

Please ignore my last comment about this affecting scopes... It was a
different root cause afterwards (missing mime database and gdk-pixbuf
loaders/cache - https://code.launchpad.net/~stolowski/unity8-session-
snap/thumbnailer-fixes/+merge/310756 should fix it).

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

Title:
  libapparmor's aa_query_label() always returns allowed = 0 for file
  rules containing the "owner" conditional

Status in AppArmor:
  Triaged
Status in Snappy:
  Won't Fix
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Download and compile the following sample C app that calls aa_query_label

  wget https://launchpadlibrarian.net/207629699/query_file.c
  gcc -o query_file query_file.c -l apparmor

  2. Install a snap that uses the home interface, for example demo-wget:

  snap install demo-wget

  3. Create a file in your home:

  touch /home/USERNAME/testfile

  4. Ask apparmor if demo-wget can read that file with query_file:

  ./query_file snap.demo-wget.wget /home/USERNAME/testfile

  
  Expected result:

  output of ./query_file command is 
  read '/home/kaleo/toto' allowed

  
  Current result:

  output of ./query_file command is 
  read '/home/kaleo/toto' denied

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

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

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

[ChristianEhrhardt]

@Mauricio Faria de Oliveira - with the passwd change in I looked deeper
into the proposed libvirt debdiff - Sorry to realize that only now, but
please help me to clarify/avoid these issues?

While overall I think it is a great fix to define a known uid/gid I'm
not so happy with the fact that it changes the group used for
libvirt/qemu on build. I think it needs some more fine tuning to be more
usable and less interuptive. Therefore I wanted to discuss the following
issues:

#1 On a given Xenial install as of today the files are owned by libvirt-
qemu:kvm (e.g. pools and images it creates). Those files will still be
owned by group "kvm", but after the upgrade libvirt/qemu will fail to
access properly right?

#2 I see on the xenial diff you remove the groups in postrm. That will
leave the files unowned, just with ther numeric gid. Is there any reason
to do this delgroup/deluser? And if so why not in Zesty?

#3 despite the other changes you left the --ingroup kvm - I think it is
right to leave it, but if you go the route of changing it to libvirt-
qemu this would need to change as well.

Once sorted out Colin might reassign (or a new one :-/) the gid to "kvm"
and you could implement it as libvirt-qemu:kvm staying compatible with
all setups out there already.


My suggestion would be:
- stick to libvirt-qemu:kvm
- do not drop the user/group on postrm
Do you think that would work for you then?

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  <...>

  Please see comments for the problem description, and summary of
  originally bridged comments in the description.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1638021] Update Released

[Martin Pitt]

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

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

Title:
  [SRU] Update apt/xenial to 1.2.15

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

Bug description:
  [Impact]
  1.2.15 is a somewhat larger bugfix release because I screwed up a bit with 
backporting fixes: 1.2.14 was released in June, and quite a few bugs have been 
fixed since then in the 1.3 series, but I never managed to release a new 1.2.y 
release. See Bug #1595177 for the 1.2.14 details.

  This changes the cache format to fix buffer overflows (the cache
  format is in sync with the 1.3 series and thus has the same version
  number). It also fixes several invalid states in the updating code
  (where we got mismatches before). Then there are several smaller
  bugfixes and more checks for file sanity I cannot really all recall,
  and some translation updates.

  This release also changes the autoremoval algorithm to only protect
  the latest same-source provider of a given package. infinity wanted
  this in for handling virtual ZFS modules provided by the kernel
  causing the kernels not to be autoremoved or something. We have this
  code in Debian testing and unstable since 1.3~pre1 early July and its
  in yakkety, and are reasonably sure it's stable now. This change also
  needs the two refactoring commits for the removal methods and the new
  pretty printers mentioned in the changelog.

  apt (1.2.15) xenial; urgency=medium

    [ Julian Andres Klode ]
    * methods/ftp: Cope with weird PASV responses.
  Thanks to Lukasz Stelmach for the initial patch (Closes: #420940)
    * Fix buffer overflow in debListParser::VersionHash() (Closes: #828812)
    * cache: Bump minor version to 6
    * indextargets: Check that cache could be built before using it
  (Closes: #829651)
    * gpgv: Unlink the correct temp file in error case
    * fileutl: empty file support: Avoid fstat() on -1 fd and check result
    * Ignore SIGINT and SIGQUIT for Pre-Install hooks
    * install-progress: Call the real ::fork() in our fork() method
    * Accept --autoremove as alias for --auto-remove
    * apt-inst: debfile: Pass comp. Name to ExtractTar, not Binary
    * changelog: Respect Dir setting for local changelog getting
    * Fix segfault and out-of-bounds read in Binary fields
    * Merge translations from 1.3~rc3
    * TagFile: Fix off-by-one errors in comment stripping
    * Base256ToNum: Fix uninitialized value
    * VersionHash: Do not skip too long dependency lines
    * Do not read stderr from proxy autodetection scripts

    [ Nicolas Le Cam ]
    * Use the ConditionACPower feature of systemd in the apt-daily service
  (Closes: #827930)

    [ David Kalnischkies ]
    * close server if parsing of header field failed
    * don't do atomic overrides with failed files (Closes: 828908)
    * if reading of autobit state failed, let write fail
    * write auto-bits before calling dpkg & again after if needed
    * factor out Pkg/DepIterator prettyprinters into own header
    * protect only the latest same-source providers from autoremove
    * reinstalling local deb file is no downgrade
    * do not treat same-version local debs as downgrade
    * avoid 416 response teardown binding to null pointer
    * don't change owner/perms/times through file:// symlinks
    * report all instead of first error up the acquire chain
    * keep trying with next if connection to a SRV host failed
    * call flush on the wrapped writebuffered FileFd
    * verify hash of input file in rred
    * use proper warning for automatic pipeline disable
    * rred: truncate result file before writing to it (Closes: #831762)
    * if the FileFd failed already following calls should fail, too
    * pass --force-remove-essential to dpkg only if needed
    * allow user@host (aka: no password) in URI parsing
    * drop incorrect const attribute from DirectoryExists (LP: 1473674)
    * http(s): allow empty values for header fields (Closes: 834048)
    * don't try pipelining if server closes connections (Closes: #832113)
    * don't loop on pinning pkgs from absolute debs by regex (Closes: 835818)
    * try not to call memcpy with length 0 in hash calculations
    * abort connection on '.' target replies in SRV

    [ Andrew Patterson ]
    * Add kernels with "+" in the package name to APT::NeverAutoRemove
  (Closes: #830159)

    [ Mert Dirik ]
    *

[Touch-packages] [Bug 1638021] Re: [SRU] Update apt/xenial to 1.2.15

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.2.15

---
apt (1.2.15) xenial; urgency=medium

  New micro release with bug fixes up to (and including) 1.3.1 (LP:
#1638021)

  [ Julian Andres Klode ]
  * methods/ftp: Cope with weird PASV responses.
Thanks to Lukasz Stelmach for the initial patch (Closes: #420940)
  * Fix buffer overflow in debListParser::VersionHash() (Closes: #828812)
  * cache: Bump minor version to 6
  * indextargets: Check that cache could be built before using it
(Closes: #829651)
  * gpgv: Unlink the correct temp file in error case
  * fileutl: empty file support: Avoid fstat() on -1 fd and check result
  * Ignore SIGINT and SIGQUIT for Pre-Install hooks
  * install-progress: Call the real ::fork() in our fork() method
  * Accept --autoremove as alias for --auto-remove
  * apt-inst: debfile: Pass comp. Name to ExtractTar, not Binary
  * changelog: Respect Dir setting for local changelog getting
  * Fix segfault and out-of-bounds read in Binary fields
  * Merge translations from 1.3~rc3
  * TagFile: Fix off-by-one errors in comment stripping
  * Base256ToNum: Fix uninitialized value
  * VersionHash: Do not skip too long dependency lines
  * Do not read stderr from proxy autodetection scripts

  [ Nicolas Le Cam ]
  * Use the ConditionACPower feature of systemd in the apt-daily service
(Closes: #827930)

  [ David Kalnischkies ]
  * close server if parsing of header field failed
  * don't do atomic overrides with failed files (Closes: 828908)
  * if reading of autobit state failed, let write fail
  * write auto-bits before calling dpkg & again after if needed
  * factor out Pkg/DepIterator prettyprinters into own header
  * protect only the latest same-source providers from autoremove
  * reinstalling local deb file is no downgrade
  * do not treat same-version local debs as downgrade
  * avoid 416 response teardown binding to null pointer
  * don't change owner/perms/times through file:// symlinks
  * report all instead of first error up the acquire chain
  * keep trying with next if connection to a SRV host failed
  * call flush on the wrapped writebuffered FileFd
  * verify hash of input file in rred
  * use proper warning for automatic pipeline disable
  * rred: truncate result file before writing to it (Closes: #831762)
  * if the FileFd failed already following calls should fail, too
  * pass --force-remove-essential to dpkg only if needed
  * allow user@host (aka: no password) in URI parsing
  * drop incorrect const attribute from DirectoryExists (LP: 1473674)
  * http(s): allow empty values for header fields (Closes: 834048)
  * don't try pipelining if server closes connections (Closes: #832113)
  * don't loop on pinning pkgs from absolute debs by regex (Closes: 835818)
  * try not to call memcpy with length 0 in hash calculations
  * abort connection on '.' target replies in SRV

  [ Andrew Patterson ]
  * Add kernels with "+" in the package name to APT::NeverAutoRemove
(Closes: #830159)

  [ Mert Dirik ]
  * Turkish program translation update (Closes: 832039)

  [ Zhou Mo ]
  * zh_CN.po: update simplified chinese translation

 -- Julian Andres Klode   Mon, 31 Oct 2016 15:29:08
+0100

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

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

Title:
  [SRU] Update apt/xenial to 1.2.15

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

Bug description:
  [Impact]
  1.2.15 is a somewhat larger bugfix release because I screwed up a bit with 
backporting fixes: 1.2.14 was released in June, and quite a few bugs have been 
fixed since then in the 1.3 series, but I never managed to release a new 1.2.y 
release. See Bug #1595177 for the 1.2.14 details.

  This changes the cache format to fix buffer overflows (the cache
  format is in sync with the 1.3 series and thus has the same version
  number). It also fixes several invalid states in the updating code
  (where we got mismatches before). Then there are several smaller
  bugfixes and more checks for file sanity I cannot really all recall,
  and some translation updates.

  This release also changes the autoremoval algorithm to only protect
  the latest same-source provider of a given package. infinity wanted
  this in for handling virtual ZFS modules provided by the kernel
  causing the kernels not to be autoremoved or something. We have this
  code in Debian testing and unstable since 1.3~pre1 early July and its
  in yakkety, and are reasonably sure it's stable now. This change also
  needs the two refactoring commits for the removal methods and the new
  pretty printers mentioned in the changelog.

  apt (1.2.15) xenial; urgency=medium

    [ Julian Andres Klode ]
    * methods/ftp: Cope with weird PASV responses.
  Thanks to Lukasz Stelmach for the initial 

[Touch-packages] [Bug 1605511] Re: openssl engine error if trying to exploit hw crypto on z due to library issue

[Dimitri John Ledkov]

** Changed in: openssl-ibmca (Ubuntu Yakkety)
   Status: Fix Committed => In Progress

** Changed in: openssl-ibmca (Ubuntu Xenial)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Description changed:

- openssl-ibmca usually requires libica2 and libica-utils for proper
- functioning and all required tooling (like icainfo, icastats, etc.)
+ [Testcase]
+ * configure ibmca engine as per below instructions
+ * execute openssl engine -c -
+ * it should complete without any loading errors
+ 
+ 
+ openssl-ibmca usually requires libica2 and libica-utils for proper 
functioning and all required tooling (like icainfo, icastats, etc.)
  
  But after the installation of these packages and the configuration, with is 
like this:
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo vi /etc/ssl/openssl.cnf
  adding the following line as the first active one:
  openssl_conf = openssl_def
  and removing or commenting all other occurrences of that line in the config 
file
  and saving and closing the openssl.cnf file
  this output of the openssl engine command is expected:
  
  $ openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  
  or even more precise these chiphers should be listed in case of "-c":
  
  $ openssl engine -c
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
-  [RAND, DES-ECB, DES-CBC, DES-OFB, DES-CFB, DES-EDE3, DES-EDE3-CBC, 
DES-EDE3-OFB, DES-EDE3-CFB, AES-128-ECB, AES-192-ECB, AES-256-ECB, AES-128-CBC, 
AES-192-CBC, AES-256-CBC, AES-128-OFB, AES-192-OFB, AES-256-OFB, AES-128-CFB, 
AES-192-CFB, AES-256-CFB, SHA1, SHA256, SHA512]
+  [RAND, DES-ECB, DES-CBC, DES-OFB, DES-CFB, DES-EDE3, DES-EDE3-CBC, 
DES-EDE3-OFB, DES-EDE3-CFB, AES-128-ECB, AES-192-ECB, AES-256-ECB, AES-128-CBC, 
AES-192-CBC, AES-256-CBC, AES-128-OFB, AES-192-OFB, AES-256-OFB, AES-128-CFB, 
AES-192-CFB, AES-256-CFB, SHA1, SHA256, SHA512]
  
  But instead openssl is giving this error, due to a missing "libica.so":
  $ openssl engine
  Error configuring OpenSSL
  4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load 
the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open 
shared object file: No such file or directory
  4395950360208:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:dso_lib.c:233:
  4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286:
  4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load 
the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open 
shared object file: No such file or directory
  4395950360208:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:dso_lib.c:233:
  4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286:
  4395950360208:error:260BC066:engine routines:INT_ENGINE_CONFIGURE:engine 
configuration error:eng_cnf.c:191:section=ibmca_section, name=init, value=1
- 4395950360208:error:0E07606D:configuration file routines:MODULE_RUN:module 
initialization error:conf_mod.c:223:module=engines, value=engine_section, 
retcode=-1  
+ 4395950360208:error:0E07606D:configuration file routines:MODULE_RUN:module 
initialization error:conf_mod.c:223:module=engines, value=engine_section, 
retcode=-1
  $
  
  There is no libica.so that is shipped with any of the above packages 
(verified with dpkg -l) or otherwise available in the filesystem:
  $ sudo find / -name "libica.so" 2>/dev/null
- ubuntu@HWE0001:~$ 
+ ubuntu@HWE0001:~$
  
  But there is a different verison of that libica:
  $ sudo find / -name "*libica.so*" 2>/dev/null
  /usr/lib/s390x-linux-gnu/libica.so.2
  /usr/lib/s390x-linux-gnu/libica.so.2.6.1
- $ 
+ $
  
  So there are right now two workarounds:
  1)
  creating a (symbolic) link from libica.so.2 to libica.so, like
- $ sudo ln -s /usr/lib/s390x-linux-gnu/libica.so.2 
/usr/lib/s390x-linux-gnu/libica.so 
+ $ sudo ln -s /usr/lib/s390x-linux-gnu/libica.so.2 
/usr/lib/s390x-linux-gnu/libica.so
  that allows openssl to find a library named 'libica.so':
  18:15:00: frank.hei...@canonical.com: ubuntu@HWE0001:~$ openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  But this could lead to issues in case of any potential functions or interface 
changes there we introduced with libica.so.2
  2)
  installation of the "libica-dev" package that provides a (development) 
version of libica.so:
  $ dpkg -L libica-dev | grep libica.so
  /usr/lib/s390x-linux-gnu/libica.so
  $
  
  But the hardware crypto exploitation should work out of the box w/o the
  link or the libica-dev package.
  
  Either libica.so should be shipped (in addition to libica.so.2) with the
  proper dependency to openssl-ibmca - openssh-ibmca should make use of
  libica2 instead of libica.so.2...

-- 
You received this bug notification because you are a member of Ubunt

[Touch-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly

[Jim Hodapp]

@Andrea: media-hub manages the playback state of nearly all playback
sessions on Ubuntu Touch. It utilizes pulseaudio for the sound server.
Any sounds coming from the web browser or web apps do not use media-hub.
Ringtone and notification sounds all go through media-hub for playback.

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

  UPDATE: As mentioned in comment #7, it seems the phone rings for a
  fraction of a second and then the sound pauses abruptly.

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

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

[Touch-packages] [Bug 1573547] Re: Apt's bash completion is incomplete

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.2.15

---
apt (1.2.15) xenial; urgency=medium

  New micro release with bug fixes up to (and including) 1.3.1 (LP:
#1638021)

  [ Julian Andres Klode ]
  * methods/ftp: Cope with weird PASV responses.
Thanks to Lukasz Stelmach for the initial patch (Closes: #420940)
  * Fix buffer overflow in debListParser::VersionHash() (Closes: #828812)
  * cache: Bump minor version to 6
  * indextargets: Check that cache could be built before using it
(Closes: #829651)
  * gpgv: Unlink the correct temp file in error case
  * fileutl: empty file support: Avoid fstat() on -1 fd and check result
  * Ignore SIGINT and SIGQUIT for Pre-Install hooks
  * install-progress: Call the real ::fork() in our fork() method
  * Accept --autoremove as alias for --auto-remove
  * apt-inst: debfile: Pass comp. Name to ExtractTar, not Binary
  * changelog: Respect Dir setting for local changelog getting
  * Fix segfault and out-of-bounds read in Binary fields
  * Merge translations from 1.3~rc3
  * TagFile: Fix off-by-one errors in comment stripping
  * Base256ToNum: Fix uninitialized value
  * VersionHash: Do not skip too long dependency lines
  * Do not read stderr from proxy autodetection scripts

  [ Nicolas Le Cam ]
  * Use the ConditionACPower feature of systemd in the apt-daily service
(Closes: #827930)

  [ David Kalnischkies ]
  * close server if parsing of header field failed
  * don't do atomic overrides with failed files (Closes: 828908)
  * if reading of autobit state failed, let write fail
  * write auto-bits before calling dpkg & again after if needed
  * factor out Pkg/DepIterator prettyprinters into own header
  * protect only the latest same-source providers from autoremove
  * reinstalling local deb file is no downgrade
  * do not treat same-version local debs as downgrade
  * avoid 416 response teardown binding to null pointer
  * don't change owner/perms/times through file:// symlinks
  * report all instead of first error up the acquire chain
  * keep trying with next if connection to a SRV host failed
  * call flush on the wrapped writebuffered FileFd
  * verify hash of input file in rred
  * use proper warning for automatic pipeline disable
  * rred: truncate result file before writing to it (Closes: #831762)
  * if the FileFd failed already following calls should fail, too
  * pass --force-remove-essential to dpkg only if needed
  * allow user@host (aka: no password) in URI parsing
  * drop incorrect const attribute from DirectoryExists (LP: 1473674)
  * http(s): allow empty values for header fields (Closes: 834048)
  * don't try pipelining if server closes connections (Closes: #832113)
  * don't loop on pinning pkgs from absolute debs by regex (Closes: 835818)
  * try not to call memcpy with length 0 in hash calculations
  * abort connection on '.' target replies in SRV

  [ Andrew Patterson ]
  * Add kernels with "+" in the package name to APT::NeverAutoRemove
(Closes: #830159)

  [ Mert Dirik ]
  * Turkish program translation update (Closes: 832039)

  [ Zhou Mo ]
  * zh_CN.po: update simplified chinese translation

 -- Julian Andres Klode   Mon, 31 Oct 2016 15:29:08
+0100

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

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

Title:
  Apt's bash completion is incomplete

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

Bug description:
  *** Original bug report ***

  "build-dep" and "clean" apt options are missing in /usr/share/bash-
  completion/completions/apt file.  Patch attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.10ubuntu1
  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
  CurrentDesktop: Unity
  Date: Fri Apr 22 14:25:54 2016
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

  *** SRU part ***

  [Test case]
  Check that options like build-dep and clean work.

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

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

[Touch-packages] [Bug 1595177] Re: [SRU] Update apt/xenial to 1.2.14

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.2.15

---
apt (1.2.15) xenial; urgency=medium

  New micro release with bug fixes up to (and including) 1.3.1 (LP:
#1638021)

  [ Julian Andres Klode ]
  * methods/ftp: Cope with weird PASV responses.
Thanks to Lukasz Stelmach for the initial patch (Closes: #420940)
  * Fix buffer overflow in debListParser::VersionHash() (Closes: #828812)
  * cache: Bump minor version to 6
  * indextargets: Check that cache could be built before using it
(Closes: #829651)
  * gpgv: Unlink the correct temp file in error case
  * fileutl: empty file support: Avoid fstat() on -1 fd and check result
  * Ignore SIGINT and SIGQUIT for Pre-Install hooks
  * install-progress: Call the real ::fork() in our fork() method
  * Accept --autoremove as alias for --auto-remove
  * apt-inst: debfile: Pass comp. Name to ExtractTar, not Binary
  * changelog: Respect Dir setting for local changelog getting
  * Fix segfault and out-of-bounds read in Binary fields
  * Merge translations from 1.3~rc3
  * TagFile: Fix off-by-one errors in comment stripping
  * Base256ToNum: Fix uninitialized value
  * VersionHash: Do not skip too long dependency lines
  * Do not read stderr from proxy autodetection scripts

  [ Nicolas Le Cam ]
  * Use the ConditionACPower feature of systemd in the apt-daily service
(Closes: #827930)

  [ David Kalnischkies ]
  * close server if parsing of header field failed
  * don't do atomic overrides with failed files (Closes: 828908)
  * if reading of autobit state failed, let write fail
  * write auto-bits before calling dpkg & again after if needed
  * factor out Pkg/DepIterator prettyprinters into own header
  * protect only the latest same-source providers from autoremove
  * reinstalling local deb file is no downgrade
  * do not treat same-version local debs as downgrade
  * avoid 416 response teardown binding to null pointer
  * don't change owner/perms/times through file:// symlinks
  * report all instead of first error up the acquire chain
  * keep trying with next if connection to a SRV host failed
  * call flush on the wrapped writebuffered FileFd
  * verify hash of input file in rred
  * use proper warning for automatic pipeline disable
  * rred: truncate result file before writing to it (Closes: #831762)
  * if the FileFd failed already following calls should fail, too
  * pass --force-remove-essential to dpkg only if needed
  * allow user@host (aka: no password) in URI parsing
  * drop incorrect const attribute from DirectoryExists (LP: 1473674)
  * http(s): allow empty values for header fields (Closes: 834048)
  * don't try pipelining if server closes connections (Closes: #832113)
  * don't loop on pinning pkgs from absolute debs by regex (Closes: 835818)
  * try not to call memcpy with length 0 in hash calculations
  * abort connection on '.' target replies in SRV

  [ Andrew Patterson ]
  * Add kernels with "+" in the package name to APT::NeverAutoRemove
(Closes: #830159)

  [ Mert Dirik ]
  * Turkish program translation update (Closes: 832039)

  [ Zhou Mo ]
  * zh_CN.po: update simplified chinese translation

 -- Julian Andres Klode   Mon, 31 Oct 2016 15:29:08
+0100

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

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

Title:
  [SRU] Update apt/xenial to 1.2.14

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

Bug description:
  (This is a template for now, so I can close the bug in the 1.2.14
  upload)

  [Impact]
  We intend to upload APT 1.2.14 to xenial under the new "micro upstream 
release" policy.

  Apart from fixing bug 1573547, it also updates translations fixes the
  following other bugs:

  [[1.2.13]]

  Segmentation fault fixes:
  * fail instead of segfault on unreadable config files (Closes: 824503)

  Fixes for 3rd party programs using libapt and C++ locale API:
  * prevent C++ locale number formatting in text APIs (Closes: #825396)

  Fix for hurd (not really affecting us here, but upstream):
  * apt-key: change to / before find to satisfy its CWD needs.
    Thanks to Samuel Thibault for 'finding' the culprit! (Closes: 826043)

  Leak fixes:
  * do not hang on piped input in PipedFileFdPrivate
  * don't leak an FD in lz4 (de)compression
  * don't leak FD in AutoProxyDetect command return parsing

  [[1.2.14]]
  Regression fix from 1.2.13:
    * do not error if auto-detect-proxy cmd has no output (Closes: 827713)
  Huge apt-ftparchive performance regression fix from 1.1:
    * Reinstate caching of file hashes in apt-ftparchive (Closes: #806924)
  Tiny bug fixes, about 2 lines each:
    * source: if download is skipped, don't try to unpack
    * ensure filesize of deb is included in the hashes list

  [Test case]
  The releases follow new upstream micro release rule and

[Touch-packages] [Bug 1350425] Re: Ubuntu 14.04 ACR38 card reader. Says "card is not found" in java applet

[veeru]

Hi Ludovic ,
Thanks for your quick review and one more thing after installing 
the pcsclite1 by default my "libccid.so " driver is located in this path 
"/usr/lib/pcsc/ifd-ccid.bundle/Contents/Linux"after running pcsc_scan 
command on my ubuntu 10.04 LTS and Debian 7(wheezy) it is giving 3B 04 12 34 56 
78 are my ATR string whether these bytes are correct ? please could you 
send me the link of installing pcsclite1 on ubuntu and Debian Linux 
distros...kindly guide me on right direction as well as send me the 
links(URL) regarding the documentation of related pcsclite1 with sample testing 
of commands such as pcsc_scan and gscriptor.how to upgrade the lower 
version of  pcsclite to latest version of pcsclite?


Thanks in Advance 

Best regards
Veeru

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

Title:
  Ubuntu 14.04 ACR38 card reader. Says "card is not found" in java
  applet

Status in pcsc-lite package in Ubuntu:
  Invalid

Bug description:
  ACR38 card reader is not working. Assume that I have wrong driver
  installed.

  tm@Compaq-HP-6510b:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  tm@Compaq-HP-6510b:~$ java -version
  java version "1.8.0_11"
  Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
  Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)

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

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

[Touch-packages] [Bug 1641358] Re: libgtk-3 should avoid configuration --enable-debug=no

[Sebastien Bacher]

Thank you for your bug report, does it create any issue in Ubuntu, if so
could you describe which one?

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  libgtk-3 should avoid configuration --enable-debug=no

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  The packaging guidelines for libgtk say to avoid using "--enable-
  debug=no" when packaging stable releases of GTK+. [1]

  The "--enable-debug=no" option can cause subtle errors and should be
  avoided. "--disable-debug" is another alias for this configuration
  option.

  More info and discussion at the Gtk-rs project (Rust bindings for
  GTK). [2]

  [1]: 
https://developer.gnome.org/gtk3/stable/gtk-building.html#extra-configuration-options
  [2]: https://github.com/gtk-rs/gtk/issues/270

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

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

[Touch-packages] [Bug 1605511] Re: openssl engine error if trying to exploit hw crypto on z due to library issue

[Launchpad Bug Tracker]

This bug was fixed in the package openssl-ibmca - 1.3.0-0ubuntu3

---
openssl-ibmca (1.3.0-0ubuntu3) zesty; urgency=medium

  * Attempt to dlopen libica.so.2, if libica.so (or ctrl provided one)
fails. LP: #1605511
  * Add depends on libica2.

 -- Dimitri John Ledkov   Tue, 04 Oct 2016 15:25:59
+0100

** Changed in: openssl-ibmca (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  openssl engine error if trying to exploit hw crypto on z due to
  library issue

Status in libica package in Ubuntu:
  Invalid
Status in openssl package in Ubuntu:
  Invalid
Status in openssl-ibmca package in Ubuntu:
  Fix Released
Status in libica source package in Xenial:
  Invalid
Status in openssl source package in Xenial:
  Invalid
Status in openssl-ibmca source package in Xenial:
  In Progress
Status in libica source package in Yakkety:
  Invalid
Status in openssl source package in Yakkety:
  Invalid
Status in openssl-ibmca source package in Yakkety:
  In Progress

Bug description:
  [Testcase]
  * configure ibmca engine as per below instructions
  * execute openssl engine -c -
  * it should complete without any loading errors

  
  openssl-ibmca usually requires libica2 and libica-utils for proper 
functioning and all required tooling (like icainfo, icastats, etc.)

  But after the installation of these packages and the configuration, with is 
like this:
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo vi /etc/ssl/openssl.cnf
  adding the following line as the first active one:
  openssl_conf = openssl_def
  and removing or commenting all other occurrences of that line in the config 
file
  and saving and closing the openssl.cnf file
  this output of the openssl engine command is expected:

  $ openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support

  or even more precise these chiphers should be listed in case of "-c":

  $ openssl engine -c
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
   [RAND, DES-ECB, DES-CBC, DES-OFB, DES-CFB, DES-EDE3, DES-EDE3-CBC, 
DES-EDE3-OFB, DES-EDE3-CFB, AES-128-ECB, AES-192-ECB, AES-256-ECB, AES-128-CBC, 
AES-192-CBC, AES-256-CBC, AES-128-OFB, AES-192-OFB, AES-256-OFB, AES-128-CFB, 
AES-192-CFB, AES-256-CFB, SHA1, SHA256, SHA512]

  But instead openssl is giving this error, due to a missing "libica.so":
  $ openssl engine
  Error configuring OpenSSL
  4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load 
the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open 
shared object file: No such file or directory
  4395950360208:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:dso_lib.c:233:
  4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286:
  4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load 
the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open 
shared object file: No such file or directory
  4395950360208:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:dso_lib.c:233:
  4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286:
  4395950360208:error:260BC066:engine routines:INT_ENGINE_CONFIGURE:engine 
configuration error:eng_cnf.c:191:section=ibmca_section, name=init, value=1
  4395950360208:error:0E07606D:configuration file routines:MODULE_RUN:module 
initialization error:conf_mod.c:223:module=engines, value=engine_section, 
retcode=-1
  $

  There is no libica.so that is shipped with any of the above packages 
(verified with dpkg -l) or otherwise available in the filesystem:
  $ sudo find / -name "libica.so" 2>/dev/null
  ubuntu@HWE0001:~$

  But there is a different verison of that libica:
  $ sudo find / -name "*libica.so*" 2>/dev/null
  /usr/lib/s390x-linux-gnu/libica.so.2
  /usr/lib/s390x-linux-gnu/libica.so.2.6.1
  $

  So there are right now two workarounds:
  1)
  creating a (symbolic) link from libica.so.2 to libica.so, like
  $ sudo ln -s /usr/lib/s390x-linux-gnu/libica.so.2 
/usr/lib/s390x-linux-gnu/libica.so
  that allows openssl to find a library named 'libica.so':
  18:15:00: frank.hei...@canonical.com: ubuntu@HWE0001:~$ openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  But this could lead to issues in case of any potential functions or interface 
changes there we introduced with libica.so.2
  2)
  installation of the "libica-dev" package that provides a (development) 
version of libica.so:
  $ dpkg -L libica-dev | grep libica.so
  /usr/lib/s390x-linux-gnu/libica.so
  $

  But the hardware crypto exploitation should work out of the box w/o
  the link or the libica-dev package.

  Either libic

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

[Mauricio Faria de Oliveira]

Hi Christian Ehrhardt,

> Sorry to realize that only now, but please help me to clarify/avoid
these issues?

no problem; sure.

> #1 On a given Xenial install as of today the files are owned by 
> libvirt-qemu:kvm (e.g. pools and images it creates). 
> Those files will still be owned by group "kvm", but after the upgrade 
> libvirt/qemu will fail to access properly right?

You're correct. The user permissions can still allow it to work, but
it's not really correct.

For Xenial, I'll upload a patch v2 without the group change. That's more 
conservative, and correct.
For Zesty and later, I believe it's better to keep the change (aligns w/ 
Debian).

> #2 I see on the xenial diff you remove the groups in postrm. That will leave 
> the files unowned, just with ther numeric gid. 
> Is there any reason to do this delgroup/deluser? And if so why not in Zesty?

Yes, but that's only in the 'purge' case, not in 'remove'. 
I think that removing the user/group in 'purge' would be correct, but I admit 
not to know the right rule for this case.
Per your question, and not to change a established behavior in the LTS, it 
seems better not to make this change. (removed in v2)

The reason to do it is to align with Debian, but is not strictly
required.

In Zesty, that is already done, thus no change required.

> #3 despite the other changes you left the --ingroup kvm - I think it is right 
> to leave it, 
> but if you go the route of changing it to libvirt-qemu this would need to 
> change as well.

I don't know if the kvm group is important for something else in the 
virtualization stack, but that is still aligned w/ Debian, so I opted to keep 
it.
Keeping it in v2 per Debian, you think it's right, and not doing the 
libvirt-qemu group change.

> Once sorted out Colin might reassign (or a new one :-/) the gid to "kvm" and 
> you could 
> implement it as libvirt-qemu:kvm staying compatible with all setups out there 
> already.

Humbly, I believe I have to defer this discussion to the maintainers in
Debian/Ubuntu, people who are more experienced in libvirt/qemu, as the
changes (libvirt-qemu user/group and kvm group) were introduced in
Debian at some point, for some reason, and those might play a role in
other components of the libvirt/qemu/kvm stack.  Sorry about the
uncertainty, but I'm not really a virtualization guy nowadays. :)


> My suggestion would be:
> - stick to libvirt-qemu:kvm
> - do not drop the user/group on postrm
> Do you think that would work for you then?

Agreed. I'll submit those on patch v2.

Thanks for the careful review and suggestions!

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  <...>

  Please see comments for the problem description, and summary of
  originally bridged comments in the description.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

[Mauricio Faria de Oliveira]

Hi Christian Ehrhardt,

Attaching PATCH v2 for Xenial.
It only checks/sets the UID for libvirt-qemu user; no other actions/changes 
performed.

** Patch added: "xenial_libvirt_uidgid_v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1637601/+attachment/4777295/+files/xenial_libvirt_uidgid_v2.debdiff

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  <...>

  Please see comments for the problem description, and summary of
  originally bridged comments in the description.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1641358] Re: libgtk-3 should avoid configuration --enable-debug=no

[Andrew Shu]

Thanks for the response. The problem is that with libgtk, "--enable-
debug=no" alters the logic within the library, and actually allows
undefined behavior, by disabling code assertions and cast checks.

This makes it easy for library and application developers to make
mistakes leading to "undefined behavior," like invalid memory accesses.

I am not familiar enough with the libgtk code base, so I cannot say if
"undefined behavior" includes potentially exploitable security issues
(due to memory accesses).

The solution is to build libgtk with "--enable-debug=minimum", which is
recommended by the GTK packaging guidelines.

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

Title:
  libgtk-3 should avoid configuration --enable-debug=no

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  The packaging guidelines for libgtk say to avoid using "--enable-
  debug=no" when packaging stable releases of GTK+. [1]

  The "--enable-debug=no" option can cause subtle errors and should be
  avoided. "--disable-debug" is another alias for this configuration
  option.

  More info and discussion at the Gtk-rs project (Rust bindings for
  GTK). [2]

  [1]: 
https://developer.gnome.org/gtk3/stable/gtk-building.html#extra-configuration-options
  [2]: https://github.com/gtk-rs/gtk/issues/270

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

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

[Touch-packages] [Bug 1627697] Re: gnome-terminal crashes on resize

[Alan Griffiths]

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

** No longer affects: miral

** No longer affects: gtk+3.0 (Ubuntu)

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

** Changed in: miral
   Status: New => Fix Committed

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

Title:
  gnome-terminal crashes on resize

Status in GTK+:
  New
Status in MirAL:
  Fix Committed

Bug description:
  Yakkety, Mir-0.24, lp:miral

  Run gnome-terminal on a touchscreen laptop and resizing by three-
  finger pinch...

  $ miral-run gnome-terminal
  $ 
  (gnome-terminal-server:4817): Gtk-WARNING **: GtkSettings Cursor Theme: 
Unsupported GDK backend
  ...
  (gnome-terminal-server:4817): Gdk-WARNING **: unknown property 
gtk-fontconfig-timestamp

  (gnome-terminal-server:4817): Gdk-WARNING **: Ignoring unknown Mir
  event 11

  (gnome-terminal-server:4817): Gtk-WARNING **: Allocating size to GtkBox 
0x55eb906c6900 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  *** Error in `/usr/lib/gnome-terminal/gnome-terminal-server': double free or 
corruption (out): 0x7f2e70258010 ***

  (Can't reproduce with Mir-0.1, but that may be because resize was too
  broken.)

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

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

[Touch-packages] [Bug 1591313] Re: Launcher quicklist doesn't have hover highlight

[Michał Sawicz]

** Summary changed:

- Launcher quicklist doesn't have over hightlight
+ Launcher quicklist doesn't have hover highlight

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

** Summary changed:

- Launcher quicklist doesn't have hover highlight
+ List Items don't have mouseover highlight

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

Title:
  List Items don't have mouseover highlight

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  On unity7 the quicklist menu entries have higlighight when you move
  the  mouse over then, unity8 should have it too.

  --
  Design resolution:

  The quicklist entries should have mouse over state. The quicklist menu
  should look visually the same as the context menu. Context menu items
  are essentially Ubuntu SDK list items and SDK list item is designed to
  have mouse over state. So if SDK list items are used for the quicklist
  menu the mouse over state will be there automatically once implemented
  in the sdk.

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

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

[Touch-packages] [Bug 1641358] Re: libgtk-3 should avoid configuration --enable-debug=no

[Sebastien Bacher]

do you have a specific example of an issue/bug created by the current
behaviour that you could share? what you write makes sense, it would
still be good to have some code showing the sort of issues users are
hitting at the moment with that configuration though

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

Title:
  libgtk-3 should avoid configuration --enable-debug=no

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  The packaging guidelines for libgtk say to avoid using "--enable-
  debug=no" when packaging stable releases of GTK+. [1]

  The "--enable-debug=no" option can cause subtle errors and should be
  avoided. "--disable-debug" is another alias for this configuration
  option.

  More info and discussion at the Gtk-rs project (Rust bindings for
  GTK). [2]

  [1]: 
https://developer.gnome.org/gtk3/stable/gtk-building.html#extra-configuration-options
  [2]: https://github.com/gtk-rs/gtk/issues/270

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

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

[Touch-packages] [Bug 1633219] Re: Upgrade to yakkety fails due to non-us locale

[Julian Andres Klode]

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

Marking this as a duplicate of bug 1592817. This is an APT bug to be
fixed in the upcoming 1.2.16, which is hopefully passing CI soon.

** This bug has been marked a duplicate of bug 1592817
   gdebi-gtk crashed with ValueError in update_interface(): could not convert 
string to float: '0,'

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

Title:
  Upgrade to yakkety fails due to non-us locale

Status in python-apt package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  Upgrade to yakkety failed during updates installation. The do-release-
  upgrade window froze and there was a stacktrace in the terminal:

  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-tqyb12c_/yakkety", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeMain.py", line 
242, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1880, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1845, in fullUpgrade
  if not self.doDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1183, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeCache.py", line 
267, in commit
  apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeView.py", line 
234, in run
  res = os.WEXITSTATUS(self.wait_child())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 339, in wait_child
  self.update_interface()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 346, in update_interface
  InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 255, in 
update_interface
  if float(percent) != self.percent or status_str != self.status:
  ValueError: could not convert string to float: '0,'
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 497, in 
add_to_existing
  self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 450, in write
  block = f.read(1048576)
File "/usr/lib/python3.5/codecs.py", line 321, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: 
invalid start byte

  Original exception was:
  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-tqyb12c_/yakkety", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeMain.py", line 
242, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1880, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1845, in fullUpgrade
  if not self.doDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1183, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeCache.py", line 
267, in commit
  apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeView.py", line 
234, in run
  res = os.WEXITSTATUS(self.wait_child())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 339, in wait_child
  self.update_interface()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 346, in update_interface
  InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 255, in 
update_interface
  if float(percent) != self.percent or status_str != self.status:
  ValueError: could not convert

[Touch-packages] [Bug 1591313] Re: List Items don't have mouseover highlight

[Michał Sawicz]

Marking the unity8 task as Invalid, if there is work in unity8 involved,
please reopen.

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

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

Title:
  List Items don't have mouseover highlight

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  On unity7 the quicklist menu entries have higlighight when you move
  the  mouse over then, unity8 should have it too.

  --
  Design resolution:

  The quicklist entries should have mouse over state. The quicklist menu
  should look visually the same as the context menu. Context menu items
  are essentially Ubuntu SDK list items and SDK list item is designed to
  have mouse over state. So if SDK list items are used for the quicklist
  menu the mouse over state will be there automatically once implemented
  in the sdk.

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

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

[Touch-packages] [Bug 1599301] Re: GenericScopeView test getting stuck

[Albert Astals Cid]

I "can" (by letting it run for hours) get it stuck in
GenericScopeView::test_seeAllTwoCategoriesScenario1

Backtrace at http://paste.ubuntu.com/23475591/

debugging with gdb it seems it got stuck at
QQuickTimeLinePrivate::advance, seems advanceTime was always 0 in that
particular case.

** Also affects: qtdeclarative-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  GenericScopeView test getting stuck

Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Every once in a while britney comes back with a failed run that is, in
  fact, a timed out run. Every time it gets stuck on GenericScopeView -
  but on different tests.

  Here's an example log.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/amd64/u/unity8/20160705_203355@/log.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160705-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul  5 23:25:40 2016
  InstallationDate: Installed on 2016-05-06 (60 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

[Mauricio Faria de Oliveira]

For reference,
Debian bug for libvirt is #844339

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  <...>

  Please see comments for the problem description, and summary of
  originally bridged comments in the description.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1641358] Re: libgtk-3 should avoid configuration --enable-debug=no

[Andrew Shu]

I am not sure if this answer will satisfy you, but the Rust bindings to
libgtk, in the Gtk-rs library, are unusable on Ubuntu currently since it
requires a libgtk compiled with safety on. I am trying to write a
Nautilus (aka Files on Ubuntu) extension which crashes when using Gtk-
rs.

It is not a defect in Gtk-rs per se, but rather a problem with how
libgtk is configured. Gtk-rs crashes when hitting the undefined behavior
(which is technically allowed given the broad definition of
"undefined"). To run without crashing, it relies on properly functioning
assertions in the libgtk code, to ensure it does not touch invalid
memory.

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

Title:
  libgtk-3 should avoid configuration --enable-debug=no

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  The packaging guidelines for libgtk say to avoid using "--enable-
  debug=no" when packaging stable releases of GTK+. [1]

  The "--enable-debug=no" option can cause subtle errors and should be
  avoided. "--disable-debug" is another alias for this configuration
  option.

  More info and discussion at the Gtk-rs project (Rust bindings for
  GTK). [2]

  [1]: 
https://developer.gnome.org/gtk3/stable/gtk-building.html#extra-configuration-options
  [2]: https://github.com/gtk-rs/gtk/issues/270

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

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

[Touch-packages] [Bug 1641358] Re: libgtk-3 should avoid configuration --enable-debug=no

[Sebastien Bacher]

thanks, that is a good reason ... now looking at the debian/rules
options we don't use --enable/disable-debug in an explicit way,
https://bazaar.launchpad.net/~ubuntu-
desktop/gtk/ubuntugtk3/view/head:/debian/rules

looking at a build log on xenial [1] 
"Debugging:minimum"

what version of ubuntu/architecture do you use? do you use a ppa or the
archive gtk?

[1] https://launchpadlibrarian.net/249838443/buildlog_ubuntu-xenial-
amd64.gtk+3.0_3.18.9-1ubuntu3_BUILDING.txt.gz

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

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

Title:
  libgtk-3 should avoid configuration --enable-debug=no

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  The packaging guidelines for libgtk say to avoid using "--enable-
  debug=no" when packaging stable releases of GTK+. [1]

  The "--enable-debug=no" option can cause subtle errors and should be
  avoided. "--disable-debug" is another alias for this configuration
  option.

  More info and discussion at the Gtk-rs project (Rust bindings for
  GTK). [2]

  [1]: 
https://developer.gnome.org/gtk3/stable/gtk-building.html#extra-configuration-options
  [2]: https://github.com/gtk-rs/gtk/issues/270

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

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

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

[Ubuntu Foundations Team Bug Bot]

The attachment "xenial_libvirt_uidgid_v2.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  <...>

  Please see comments for the problem description, and summary of
  originally bridged comments in the description.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1606600] Re: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported

[Launchpad Bug Tracker]

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

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

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

Title:
  dpkg-reconfigure unattended-upgrades results in update-rc.d warning
  that start and stop actions are no longer supported

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to script a change to the automatic updating of servers,
  and tried the following:

  echo "debconf unattended-upgrades/enable_auto_updates boolean false" | 
debconf-set-selections -
  dpkg-reconfigure -fnoninteractive unattended-upgrades

  The result, however, is a warning message:

  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

  At this point, the change I tried to make seems to be lost. To show
  this in an expanded sequence:

  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: true
  root@brennan:/home/ubuntu# echo "debconf 
unattended-upgrades/enable_auto_updates boolean false" | debconf-set-selections 
-
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: false
  root@brennan:/home/ubuntu# dpkg-reconfigure -fnoninteractive 
unattended-upgrades
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/enable_auto_updates: true
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";

  If I omit the "-fnoninteractive" option to dpkg-reconfigure, I still
  get the warning message, but the change IS accepted and takes effect.
  Of course, this isn't useful in a script that should be run non-
  interactively. I've tried the equivalent commands to reconfigure other
  packages, and they work without error message, so I believe the
  problem is with unattended-upgrades, not with debconf/dpkg-
  reconfigure.

  This problem affects Ubuntu 16.04.1 (and probably 16.04 GA, but I've
  not tested it). It works as expected with Ubuntu 14.04. (That version,
  of course, defeaults to "false" for the unattended-
  upgrades/enable_auto_updates value. I've tested both with the default
  "false" value and after changing it to "true," with successful runs
  both times.)

  Version information, as requested:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90
Version table:
   *** 0.90 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy debconf
  debconf:
Installed: 1.5.58ubuntu1
Candidate: 1.5.58ubuntu1
Version table:
   *** 1.5.58ubuntu1 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1641672] [NEW] Missing youtube, soundcloud and songkick results in music scope

[Victor gonzalez]

Public bug reported:

Environment:

current build number: 81
device name: frieza_arm64
channel: ubuntu-touch/staging/ubuntu
last update: 2016-11-15 05:29:49
version version: 81
version ubuntu: 20161112
version device: 20161014.0
version custom: 20161112

Steps to reproduce:

1º Swipe until you get to music scope
2º Open settings from upper right icon(gear wheel)

Current result: soundcloud, youtube and songkick sources aren't
available

Expected result: soundcloud, youtube and songkick sources should be
available

** Affects: unity-scope-mediascanner (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Missing youtube,soundcloud and songkick results in music  scope

Status in unity-scope-mediascanner package in Ubuntu:
  New

Bug description:
  Environment:

  current build number: 81
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-11-15 05:29:49
  version version: 81
  version ubuntu: 20161112
  version device: 20161014.0
  version custom: 20161112

  Steps to reproduce:

  1º Swipe until you get to music scope
  2º Open settings from upper right icon(gear wheel)

  Current result: soundcloud, youtube and songkick sources aren't
  available

  Expected result: soundcloud, youtube and songkick sources should be
  available

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

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

[Touch-packages] [Bug 1584795] Re: Severe lag in LibreOffice Draw due to /etc/X11/Xsession.d/90atk-adaptor

[Launchpad Bug Tracker]

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

** Changed in: at-spi2-atk (Ubuntu)
   Status: New => Confirmed

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

Title:
  Severe lag in LibreOffice Draw due to /etc/X11/Xsession.d/90atk-
  adaptor

Status in at-spi2-atk package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 16.04, I found that LibreOffice Draw (4.2.x, 5.0.x, 5.1.x
  versions) was extremely slow when selecting and moving a bunch of
  shapes in some relatively simple drawings. This occurred on five
  Ubuntu boxes I have. However, there was no slow down on Windows with
  the same files and also on a fresh install of Xubuntu 16.04 in a
  virtual machine.

  After a long investigation, I finally found the culprit: for some
  reason, the package gnome-orca was installed on my machines and this
  package pulls down the libatk-adaptor package, which in turn installs
  the file /etc/X11/Xsession.d/90atk-adaptor.

  I found that removing that file solves the problem and now LibreOffice
  Draw is fully responsive. Perhaps other graphic applications could
  suffer from the same problem, but I was not able to see some huge lag
  as in LO Draw.

  To reproduce:
  1. install libatk-adaptor (version 2.18.1-2ubuntu1:amd64 of Ubuntu 16.04) or 
simply the gnome-orca package

  2. open the attached file test.odg with LibreOffice Draw, and select a
  bunch of shapes (for example, the two axes and shapes of the page
  bottom). Then, try to move the selected shapes with the keyboard
  (shift + arrow) and you should see a severe lag. If you maintain the
  key pressed during the move, then the UI is blocked during some time.
  Moving the shapes using the mouse is faster but still quite slow as
  compared to the expected performance.

  3. remove the file /etc/X11/Xsession.d/90atk-adaptor and restart X

  4. open again the test.odg file. Now, moving a bunch of shapes using
  the keyboard (or the mouse) is very smooth and fluid, as it should be.

  This is 100% reproducible on all the machines I have where the libatk-
  adaptor package is installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1584795/+subscriptions

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

[Touch-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while

[Till Kamppeter]

Fixed package uploaded to xenial-proposed. Please test the package as
soon as it gets available and appropriate test instructions will get
posted here. Your feedback is needed in order to make the fix an
official update for Xenial.

SRU team: debdiff attached.

** Description changed:

  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0
  
  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏
  
  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups
  
  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.
+ 
+ [Impact]
+ 
+ If you want to use the CUPS web interface in Xenial and therefore set
+ "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
+ when it is idle and then an attempt to access http://localhost:631/ via
+ a web browser fails. People get confused as other access to CUPS
+ 
+ [Testcase]
+ 
+ Take a CUPS setup on Xenial with no shared print queues and CUPS only
+ listening on the domain socket. Activate the web interface via
+ 
+ cupsctl WebInterface=Yes
+ 
+ Now you are able to access the web interface via http://localhost:631/.
+ Wait for some minutes without accessing CUPS until the CUPS daemon shuts
+ down automatically. Try to open the web interface again and it will not
+ work.
+ 
+ With the fixed CUPS package CUPS will not auto-shutdown when the web
+ interface is activated.
+ 
+ [Regression Potential]
+ 
+ Low, as we are removing a simple distro patch to get back to the
+ original, upstream behavior.

** Changed in: cups (Ubuntu Xenial)
   Status: Confirmed => In Progress

** Patch added: "cups_2.1.3-4_2.1.3-4ubuntu0.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+attachment/4777337/+files/cups_2.1.3-4_2.1.3-4ubuntu0.1.debdiff

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

Title:
  CUPS web interface stops responding after a while

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

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web

[Touch-packages] [Bug 1585723] Re: UbuntuShape on intel i915 (Atom) uses fallback CPU rendering

[Emanuele Antonio Faraone]

** Tags removed: performance
** Tags added: i915

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

Title:
  UbuntuShape on intel i915 (Atom) uses fallback CPU rendering

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

Bug description:
  I'm digging into unity8 performance problems on older generation Intel
  GPUs - specifically i915 Atom GPUs.

  I've tested a simple QML file with a single empty UbuntuShape in it:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Rectangle {
  width: 400
  height: 300
  color: "blue"

  UbuntuShape {}
  }

  Running it with INTEL_DEBUG=perf env var set, I get this output:

  i915_program_error: Exceeded max ALU instructions (76 out of 64)
  ENTER FALLBACK 1: Program
  Mapping a busy BO, causing a stall on the GPU.

  which implies that MESA was unable to compile one of the UbuntuShape
  shaders as it created more ALU instructions than the GPU could deal
  with. MESA falls back to CPU rendering as a result.

  The GPU stall message I guess is related to that.

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

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

[Touch-packages] [Bug 1641690] [NEW] [X7, Realtek ALC282, Speaker, Internal] No sound at all

[tweichart]

Public bug reported:

no sound from built-in speakers, headphones fine
ubuntu 16.10, frehs install
laptop is this http://www.aorus.com/Product/Spec/X7

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  tweichart   2752 F pulseaudio
 /dev/snd/controlC2:  tweichart   2752 F pulseaudio
 /dev/snd/pcmC0D0p:   tweichart   2752 F...m pulseaudio
 /dev/snd/controlC0:  tweichart   2752 F pulseaudio
CurrentDesktop: Unity
Date: Mon Nov 14 18:51:43 2016
InstallationDate: Installed on 2016-11-11 (2 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  tweichart   2752 F pulseaudio
 /dev/snd/controlC2:  tweichart   2752 F pulseaudio
 /dev/snd/controlC0:  tweichart   2752 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [X7, Realtek ALC282, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/10/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X7.309
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X7
dmi.board.vendor: GIGABYTE
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX7.309:bd02/10/2014:svnGIGABYTE:pnX7:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnX7:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: X7
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: GIGABYTE

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


** Tags: amd64 apport-bug yakkety

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

Title:
  [X7, Realtek ALC282, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  no sound from built-in speakers, headphones fine
  ubuntu 16.10, frehs install
  laptop is this http://www.aorus.com/Product/Spec/X7

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tweichart   2752 F pulseaudio
   /dev/snd/controlC2:  tweichart   2752 F pulseaudio
   /dev/snd/pcmC0D0p:   tweichart   2752 F...m pulseaudio
   /dev/snd/controlC0:  tweichart   2752 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 14 18:51:43 2016
  InstallationDate: Installed on 2016-11-11 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tweichart   2752 F pulseaudio
   /dev/snd/controlC2:  tweichart   2752 F pulseaudio
   /dev/snd/controlC0:  tweichart   2752 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [X7, Realtek ALC282, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X7.309
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X7
  dmi.board.vendor: GIGABYTE
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX7.309:bd02/10/2014:svnGIGABYTE:pnX7:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnX7:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: X7
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: GIGABYTE

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

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

[Touch-packages] [Bug 1637601] chig6_migration logs

[bugproxy]

--- Comment on attachment From lakun...@in.ibm.com 2016-11-14 12:42 
EDT---


Machine Details:
=
Note:- 

System is on a private network.  Access the private network via SSH to 
"banner.isst.aus.stglabs.ibm.com" using your GSA ID and password. 
(Banner itself is behind a BSO, so must authenticate through that first.)

Login details :  
ssh banner.isst.aus.stglabs.ibm.com [debug/don2rry]

Source Host login:-
chikvm.isst.aus.stglabs.ibm.com [10.33.7.207]
[root/don2rry]

Destination Host Login:-
guskvm.isst.aus.stglabs.ibm.com has address 10.33.32.222

start Guest Login :-
virsh console chig6 --force

IPMI Login :- 
-
>From banner machine run the following :
ssh banner.isst.aus.stglabs.ibm.com [debug/don2rry ]

ipmitool -I lanplus -H fsp-chi  -P don2rry sol deactivate
ipmitool -I lanplus -H fsp-chi  -P don2rry sol activate


-
 TESTING INFORMATION
-

SYSTEM INFORMATION
--
  HOST NAME or NETWORK ADDRESS:   chikvm.isst.aus.stglabs.ibm.com
 [10.33.7.207]
guskvm..isst.aus.stglabs.ibm.com 10.33.32.222
   
  Sapphire FIRMWARE LEVEL:  - FW860.00 (SV860_056)

-
DEBUGGING INFORMATION
-
   
DEBUG / LOGIN INFORMATION 
- 
  ERROR LOG: on local machine 
  FSP LOGIN: see name above  [dev/FipSdev]
RECENT SYSTEM CHANGES  : none
-
  none

** Attachment added: "chig6_migration logs"
   
https://bugs.launchpad.net/bugs/1637601/+attachment/4777367/+files/logs_mig.zip

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  <...>

  Please see comments for the problem description, and summary of
  originally bridged comments in the description.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1440294] Re: syncevolution - no export of tasks / memos Aquaris E4.5

[Dom134]

This is also an issue on the Meizu Pro 5.  I can sync to my Nextcloud
tasks; however they do not show up on my Ubuntu-touch task list

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

Title:
   syncevolution - no export of tasks / memos Aquaris E4.5

Status in syncevolution package in Ubuntu:
  Confirmed

Bug description:
  Phone: bq Aquaris E4.5 Ubuntu Edtion
  OS: Ubuntu 14.10(r20)
  SyncEvolution 1.5

  Can not export my Tasks and memos.
  Calendar and contacts export works!

  phablet@ubuntu-phablet:~$ syncevolution --print-databases
  CalDAV:
     select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery ()

  CalDAVTodo:
     select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery ()

  CalDAVJournal:
     select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery ()

  CardDAV:
     select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery ()

  Evolution Address Book = Evolution Contacts = evolution-contacts:
     Persönlich (system-address-book) 

  Evolution Calendar = evolution-calendar:
     Geburts- & Jahrestage (birthdays)
     Persönlich (system-calendar) 

  Evolution Task List = Evolution Tasks = evolution-tasks:
     Alarms (1427538744.24638.0@ubuntu-phablet)
     Persönlich (system-task-list) 
     Reminders (1427534898.18825.0@ubuntu-phablet)

  Evolution Memos = evolution-memos:
     Persönlich (system-memo-list) 

  phablet@ubuntu-phablet:~$ syncevolution --export tasks backend=evolution-tasks
  phablet@ubuntu-phablet:~$ file tasks
  tasks: empty

  phablet@ubuntu-phablet:~$ syncevolution --print-items backend
  =evolution-tasks

  

  phablet@ubuntu-phablet:~$ syncevolution --print-items backend
  =evolution-memos

  

  phablet@ubuntu-phablet:~$ click list
  com.canonical.payui   15.01.120
  com.canonical.scopes.bbc-sport1.03
  com.canonical.scopes.etsy 1.0.29
  com.canonical.scopes.euronews 0.5
  com.canonical.scopes.fitbit   1.0.40
  com.mikeasoft.podbird 0.5
  com.ubuntu.calendar   0.4.600
  com.ubuntu.camera 3.0.0.544
  com.ubuntu.developer.bobo1993324.qvbam0.1.3.1
  com.ubuntu.developer.liberavia.ardmediathek   0.1
  com.ubuntu.developer.majster-pl.utorch1.6
  com.ubuntu.developer.mzanetti.leo 0.2
  com.ubuntu.developer.ogra.rtv-de  0.3
  com.ubuntu.developer.tyrelparker0.metalhammer 0.2
  com.ubuntu.docviewer  0.3.109
  com.ubuntu.filemanager0.4.386
  com.ubuntu.gallery2.9.1.1183
  com.ubuntu.music  2.0.846
  com.ubuntu.reminders  0.5.380
  com.ubuntu.scopes.soundcloud  1.0.1-39
  com.ubuntu.scopes.vimeo   1.0.2-84
  com.ubuntu.telegram   1.1.2.95
  com.ubuntu.terminal   0.7.70
  dekko.dekkoproject0.5.1
  help.ubuntucoredev0.2
  noobslabscope.noobslab0.1.1
  omgubuntu-scope.mreese1.4
  com.canonical.scopes.bbc  1.7
  com.canonical.scopes.calls1.1
  com.canonical.scopes.cnet 0.6
  com.canonical.scopes.contacts 0.7
  com.canonical.scopes.dashboard1.6
  com.canonical.scopes.engadget 0.5
  com.canonical.scopes.events   1.0.11
  com.canonical.scopes.fbphotos 1.23
  com.canonical.scopes.flickr   1.0.24
  com.canonical.scopes.hints0.20
  com.canonical.scopes.holidays 1.1
  com.canonical.scopes.inrix1.0.28
  com.canonical.scopes.instagram1.0.15
  com.canonical.scopes.news 2.13
  com.canonical.scopes.photos   1.31
  com.canonical.scopes.photos-local 1.23
  com.canonical.scopes.poi  1.0.11
  com.canonical.scopes.shopping 1.9
  com.canonical.scopes.songkick 1.0.11
  com.canonical.scopes.tasks1.3
  com.canonical.scopes.texts1.0
  com.canonical.scopes.timeout  0.4.12
  com.canonical.scopes.transport-alerts 1.10
  com.canonical.scopes.twittertrending  1.0.9
  com.canonical.scopes.wikinear 1.0.9
  com.canonical.scopes.yelp 1.0.34
  com.canonical.unity-scope-nearby  0.8.8
  com.nokia.heremaps1.0.4
  com.ubuntu.developer.ken-vandine.pathwind 0.2.9
  com.ubuntu.developer.mzanetti.tagger  0.9.0.0
  com.ubuntu.developer.webapps.webapp-twitter   1.0.21
  com.zeptolab.cuttherope.free  0.5.1
  com.ubuntu.calculator 1.3.339
  com.ubuntu.clock  3.3.192
  com.ubuntu.scopes.youtube 1.0.18-134
  com.ubuntu.weather1.1.403

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

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

[Touch-packages] [Bug 1641592] Re: nano 2.5.3-2 on Xenial crashes with long paths on lockfiles

[Benno Schulenberg]

This is a duplicate of upstream bug https://savannah.gnu.org/bugs/?47511
.

The problem was fixed in git, commit fb9585e.  See attached patch.  The
fix is in version 2.6.0 and higher.

Thanks for reporting.

** Bug watch added: GNU Savannah Bug Tracker #47511
   http://savannah.gnu.org/bugs/?47511

** Patch added: "fixes the crash when finding lockfiles for long names"
   
https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1641592/+attachment/4777372/+files/allocate-enough-space.patch

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

Title:
  nano 2.5.3-2 on Xenial crashes with long paths on lockfiles

Status in nano package in Ubuntu:
  New

Bug description:
  # lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  # apt-cache policy nano
  nano:
Installed: 2.5.3-2
Candidate: 2.5.3-2

  Reproducer:
  1. # nano -G 
999
  2. 
  3. # nano -G 
999
  4. 
  5. 

  Quick dissection:
  Looking at function do_lockfile in files.c, it seems that promptstr is 
statically allocated to 128 characters. Now with a sufficiently long filename, 
the following sprintf() call will overflow the allocated promptstr buffer and 
corrupt memory.

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

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

[Touch-packages] [Bug 1638204] Re: install snapd in default ubuntu xenial image

[Łukasz Zemczak]

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

** Changed in: ubuntu-touch-meta (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

** Changed in: ubuntu-touch-meta (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-touch-meta (Ubuntu)
   Status: New => In Progress

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

Title:
  install snapd in default ubuntu xenial image

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Committed

Bug description:
  currently m10 have arm64 branch. we want to run snapd on it !

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

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

[Touch-packages] [Bug 1638204] Re: install snapd in default ubuntu xenial image

[Łukasz Zemczak]

** Changed in: ubuntu-touch-meta (Ubuntu)
   Status: In Progress => Fix Committed

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

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

Title:
  install snapd in default ubuntu xenial image

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Committed

Bug description:
  currently m10 have arm64 branch. we want to run snapd on it !

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

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

[Touch-packages] [Bug 1605511] Re: openssl engine error if trying to exploit hw crypto on z due to library issue

[Frank Heimes]

Being curious I tried "openssl-ibmca_1.3.0-0ubuntu3_s390x.deb" on yakkety and 
xenial, too.
It looks good - the error message is gone.
(Even if I do not yet know how to interpret 'built on: reproducible build, date 
unspecified'...)

Yakkety:


>>> openssl-ibmca prior to (1.3.0-0ubuntu3):

ubuntu@s1lp14:~$ openssl speed -evp des-ede3-cbc
Doing des-ede3-cbc for 3s on 16 size blocks: 23686887 des-ede3-cbc's in 2.99s
Doing des-ede3-cbc for 3s on 64 size blocks: 16020848 des-ede3-cbc's in 3.00s
Doing des-ede3-cbc for 3s on 256 size blocks: 6971169 des-ede3-cbc's in 3.00s
Doing des-ede3-cbc for 3s on 1024 size blocks: 2154635 des-ede3-cbc's in 3.00s
Doing des-ede3-cbc for 3s on 8192 size blocks: 287230 des-ede3-cbc's in 3.00s
OpenSSL 1.0.2g  1 Mar 2016
built on: reproducible build, date unspecified
options:bn(64,64) rc4(8x,char) des(idx,cisc,16,int) aes(partial) blowfish(idx) 
compiler: cc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS 
-D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DB_ENDIAN -g -O2 
-fdebug-prefix-map=/build/openssl-tmX0Mb/openssl-1.0.2g=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack 
-Wall -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM 
-DSHA512_ASM -DAES_ASM -DAES_CTR_ASM -DAES_XTS_ASM -DGHASH_ASM
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes   1024 bytes   8192 bytes
des-ede3-cbc126752.57k   341778.09k   594873.09k   735448.75k   784329.39k
4396106589840:error:25066067:DSO support routines:DLFCN_LOAD:could not load the 
shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open 
shared object file: No such file or directory
4396106589840:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:dso_lib.c:233:
4396106589840:error:25066067:DSO support routines:DLFCN_LOAD:could not load the 
shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open 
shared object file: No such file or directory
4396106589840:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:dso_lib.c:233:

>>> openssl-ibmca (1.3.0-0ubuntu3):

ubuntu@s1lp14:~$ sudo dpkg -i ./openssl-ibmca_1.3.0-0ubuntu3_s390x.deb
(Reading database ... 91267 files and directories currently installed.)
Preparing to unpack .../openssl-ibmca_1.3.0-0ubuntu3_s390x.deb ...
Unpacking openssl-ibmca (1.3.0-0ubuntu3) over (1.3.0-0ubuntu3) ...
Setting up openssl-ibmca (1.3.0-0ubuntu3) ...
Processing triggers for man-db (2.7.5-1) ...
ubuntu@s1lp14:~$ openssl speed -evp des-ede3-cbc
Doing des-ede3-cbc for 3s on 16 size blocks: 24062744 des-ede3-cbc's in 2.99s
Doing des-ede3-cbc for 3s on 64 size blocks: 16179261 des-ede3-cbc's in 3.00s
Doing des-ede3-cbc for 3s on 256 size blocks: 7044115 des-ede3-cbc's in 3.00s
Doing des-ede3-cbc for 3s on 1024 size blocks: 2157283 des-ede3-cbc's in 3.00s
Doing des-ede3-cbc for 3s on 8192 size blocks: 287455 des-ede3-cbc's in 3.00s
OpenSSL 1.0.2g  1 Mar 2016
built on: reproducible build, date unspecified
options:bn(64,64) rc4(8x,char) des(idx,cisc,16,int) aes(partial) blowfish(idx) 
compiler: cc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS 
-D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DB_ENDIAN -g -O2 
-fdebug-prefix-map=/build/openssl-tmX0Mb/openssl-1.0.2g=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack 
-Wall -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM 
-DSHA512_ASM -DAES_ASM -DAES_CTR_ASM -DAES_XTS_ASM -DGHASH_ASM
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes   1024 bytes   8192 bytes
des-ede3-cbc128763.85k   345157.57k   601097.81k   736352.60k   784943.79k
ubuntu@s1lp14:~$ openssl engine -c ibmca
(ibmca) Ibmca hardware engine support
 [RSA, DSA, DH, RAND, DES-ECB, DES-CBC, DES-OFB, DES-CFB, DES-EDE3, 
DES-EDE3-CBC, DES-EDE3-OFB, DES-EDE3-CFB, AES-128-ECB, AES-192-ECB, 
AES-256-ECB, AES-128-CBC, AES-192-CBC, AES-256-CBC, AES-128-OFB, AES-192-OFB, 
AES-256-OFB, AES-128-CFB, AES-192-CFB, AES-256-CFB, SHA1, SHA256, SHA512]
[just checking that 'libica-dev' is really not installed]
ubuntu@s1lp14:~$ dpkg -l | grep libica
ii  libica-utils   2.6.1-3  
s390xhardware cryptography support for Linux on z Systems (utils)
ii  libica2:s390x  2.6.1-3  
s390xhardware cryptography support for IBM System z hardware
ii  openssl-ibmca  1.3.0-0ubuntu3   
s390xlibica based hardware acceleration engine for OpenSSL
ubuntu@s1lp14:~$ dpkg -l libica-dev
dpkg-query: no packages found matching libica-dev
ubuntu@s1lp14:~$ openssl engine
(dynamic) Dynamic engine loading support
(ib

[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[swaprava]

I'm using Ubuntu 16.04 on Dell Inspiron -- for me the problem is same
but the pointer jumps to the top-right corner and clicks the power
button. Did you guys figure out any workaround till the bug is fixed?

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1639489] Re: package click-apparmor 0.3.13.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: click-apparmor (Ubuntu)
   Status: New => Confirmed

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

Title:
  package click-apparmor 0.3.13.1 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in click-apparmor package in Ubuntu:
  Confirmed

Bug description:
  Happened after upgrade from 16.04 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: click-apparmor 0.3.13.1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sat Nov  5 10:44:18 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-04 (184 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.3.13.1 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-11-05 (0 days ago)

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

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

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

[Julian Andres Klode]

apt 1.2.16~rc1 just hit the PPA (might take some time for processing,
though):

  https://launchpad.net/~deity/+archive/ubuntu/apt-1.2

and should fix this bug. It would be great to have some confirmation of
that before uploading that, otherwise I'll go ahead with an SRU tomorrow
probably if I don't notice any regression on my system.

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

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

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

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

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

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

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

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

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

[Julian Andres Klode]

apt 1.2.16~rc1 just hit the PPA (might take some time for processing,
though):

  https://launchpad.net/~deity/+archive/ubuntu/apt-1.2

and should fix this bug. It would be great to have some confirmation of
that before uploading that, otherwise I'll go ahead with an SRU tomorrow
probably if I don't notice any regression on my system.

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

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

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

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

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

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

  Steps to reproduce:

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

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

  Expected result: No crashes during installation

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

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

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

[Touch-packages] [Bug 1590321] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:get_dpkg_log_content

[Brian Murray]

This works in xenial:

bdmurray@clean-xenial-amd64:~$ sudo apt-get install unattended-upgrades
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  bsd-mailx mail-transport-agent
The following packages will be upgraded:
  unattended-upgrades
1 upgraded, 0 newly installed, 0 to remove and 141 not upgraded.
Need to get 31.7 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://192.168.10.7/ubuntu xenial-proposed/main amd64 unattended-upgrades 
all 0.90ubuntu0.2 [31.7 kB]
Fetched 31.7 kB in 0s (1,225 kB/s)
Preconfiguring packages ...
(Reading database ... 212849 files and directories currently installed.)
Preparing to unpack .../unattended-upgrades_0.90ubuntu0.2_all.deb ...
Unpacking unattended-upgrades (0.90ubuntu0.2) over (0.90) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu10) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up unattended-upgrades (0.90ubuntu0.2) ...
Replacing config file /etc/apt/apt.conf.d/50unattended-upgrades with new version
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
bdmurray@clean-xenial-amd64:~$ sudo rm 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
rm: cannot remove '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log': 
No such file or directory
bdmurray@clean-xenial-amd64:~$ sudo /usr/bin/unattended-upgrades


** Tags added: verification-done-xenial

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

Title:
  /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-
  upgrade@1468:main:get_dpkg_log_content

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Yakkety:
  Fix Committed
Status in unattended-upgrades source package in Zesty:
  Fix Released

Bug description:
  Test Case
  -
  1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 
and Unattended-Upgrade is 1
  2) sudo apt-get update
  3) sudo /usr/bin/unattended-upgrades (to update the system)
  4) sudo /usr/bin/unattended-upgrades (a second time for some reason)
  5) sudo rm /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  6) sudo /usr/bin/unattended-upgrades

  Observe the following crash:

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1468, in 
  main(options)
    File "/usr/bin/unattended-upgrade", line 1406, in main
  log_content = get_dpkg_log_content(logfile_dpkg, install_start_time)
    File "/usr/bin/unattended-upgrade", line 1075, in get_dpkg_log_content
  with io.open(logfile_dpkg, encoding='utf-8') as fp:
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'

  With the version of the package from -proposed you won't receive the
  crash in step 6 and /var/log/unattended-upgrades/unattended-upgrades-
  dpkg.log will exist.

  Regression Potential
  
  This patch just ends up creating a file if it does not exist. Potential 
regressions would be a result of the patch being typo'ed e.g. typo'ing 
os.path.exits instead of os.path.exists and the code failing when a logfile 
does exist. So read the patch carefully!

  
  Original Description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with version 0.90, 
the problem page at 
https://errors.ubuntu.com/problem/db5f0a803afdf5bb5e20a42ce68f4fda3ce0df8a 
contains more details.

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

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

[Touch-packages] [Bug 1639977] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:write_stamp_file

[Brian Murray]

Verification passed in Xenial:

After this operation, 0 B of additional disk space will be used.
Get:1 http://192.168.10.7/ubuntu xenial-proposed/main amd64 unattended-upgrades 
all 0.90ubuntu0.2 [31.7 kB]
Fetched 31.7 kB in 0s (0 B/s)  
Preconfiguring packages ...
(Reading database ... 245059 files and directories currently installed.)
Preparing to unpack .../unattended-upgrades_0.90ubuntu0.2_all.deb ...
Unpacking unattended-upgrades (0.90ubuntu0.2) over (0.90) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu10) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up unattended-upgrades (0.90ubuntu0.2) ...
Replacing config file /etc/apt/apt.conf.d/50unattended-upgrades with new version
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
bdmurray@clean-xenial-amd64:~$ sudo /usr/bin/unattended-upgrade


** Tags added: verification-done-xenial

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

Title:
  /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-
  upgrade@1468:main:write_stamp_file

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

Bug description:
  Test Case
  -
  1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 
and Unattended-Upgrade is 1
  2) sudo apt-get update
  3) sudo rm -fr /var/lib/apt/periodic
  4) sudo /usr/bin/unattended-upgrade
  5) observe the following Traceback

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1468, in 
  main(options)
    File "/usr/bin/unattended-upgrade", line 1419, in main
  write_stamp_file()
    File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file
  with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"):
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/lib/apt/periodic/unattended-upgrades-stamp'

  With the version of the package from -proposed you'll receive no such
  Traceback.

  Regression Potential
  
  This patch just ends up creating a directory if it does not exist.  Potential 
regressions would be a result of the patch being typo'ed e.g. typo'ing 
os.path.exits instead of os.path.exists and the code failing when a statedir 
does exist.  So read the patch carefully!

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

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

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

[Touch-packages] [Bug 1624641] Re: security updates with a new dependency don't get installed

[Brian Murray]

After this operation, 0 B of additional disk space will be used.
Get:1 http://192.168.10.7/ubuntu yakkety-proposed/main amd64 
unattended-upgrades all 0.92ubuntu1.1 [33.4 kB]
Fetched 33.4 kB in 0s (582 kB/s)   
The system does not support apt-btrfs-snapshot
Preconfiguring packages ...
(Reading database ... 297966 files and directories currently installed.)
Preparing to unpack .../unattended-upgrades_0.92ubuntu1.1_all.deb ...
Unpacking unattended-upgrades (0.92ubuntu1.1) over (0.92ubuntu1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (231-9ubuntu1) ...
Setting up unattended-upgrades (0.92ubuntu1.1) ...
Replacing config file /etc/apt/apt.conf.d/50unattended-upgrades with new version
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
Processing triggers for man-db (2.7.5-1) ...
[ 11:53AM 5736 ]  [ bdmurray@speedy:~/Pictures/Nexus 5x ]
 $ head -n7 /etc/apt/apt.conf.d/50unattended-upgrades
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
//  "${distro_id}:${distro_codename}-updates";
//  "${distro_id}:${distro_codename}-proposed";
//  "${distro_id}:${distro_codename}-backports";

verification done for xenial

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

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

Title:
  security updates with a new dependency don't get installed

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

Bug description:
  Test Case
  -
  1) Boot a xenial system w/o chromium browser and w/o libspeechd2 installed
  2) Install the release version of chromium browser e.g. "sudo apt-get install 
chromium-browser=49.0.2623.108-0ubuntu1.1233 
chromium-browser-l10n=49.0.2623.108-0ubuntu1.1233 
chromium-codecs-ffmpeg-extra=49.0.2623.108-0ubuntu1.1233"
  3) Run apt-get update if you didn't already
  4) Run "sudo /usr/bin/unattended-upgrades -v -d"
  5) Observe the following output "Checking: chromium-browser ([, ])
  pkg 'libspeechd2' not in allowed origin
  sanity check failed"

  With the version of unattended-upgrades from -proposed libspeechd2
  should be from an allowed origin and chromium-browser will get
  updated.

  Regression Potential
  
  This change modifies the behavior of unattended-upgrades such that new 
packages will be installed on a user's system and they may not except such 
behavior (e.g. why was libspeechd2 insalled?).  However, this seems better than 
not installing security updates and leaving people's systems vulnerable to 
attack.

  Original Description
  
  E.g. chromium-browser has an update, but U-U does not update it. I saw in 
update-manager that the security update is available before running U-U. 
Afterwards I can install the update by update-manager.

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

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

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

[Touch-packages] [Bug 1641284] Re: libatk-adaptor breaks down the LibreOffice TexMaths extension

[Launchpad Bug Tracker]

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

** Changed in: at-spi2-atk (Ubuntu)
   Status: New => Confirmed

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

Title:
  libatk-adaptor breaks down the LibreOffice TexMaths extension

Status in at-spi2-atk package in Ubuntu:
  Confirmed

Bug description:
  Package: libatk-adaptor 2.18.1-2ubuntu1
  System: Ubuntu 16.04.1 LTS (Xenial Xerus)

  If the package libatk-adaptor is installed on Ubuntu (as a depency of
  gnome-orca for example), it breaks down the LibreOffice TexMaths
  extension. TexMaths is a popular extension used to enter / edit LaTeX
  equations on LibreOffice (see http://roland65.free.fr/texmaths).

  Step to reproduce the bug:

  1. It is assumed that LibreOffice 5.1.4 (with at least the Writer and
  Draw components) is installed on Ubuntu. It is also assumed that
  libatk-adaptor is installed.

  2. Install texlive:
  sudo apt-get install texlive

  3. Download and install the TexMaths extension (version 0.42) from
  there: https://sourceforge.net/projects/texmaths/files/0.42/

  4. Create a new empty Writer document, then click on the Pi icon (this
  is the TexMaths icon) and in the window that opens, type: 'x(t)+y(t)'
  (without the quotes), then click on the LaTeX button. This generates
  an SVG image of the 'x(t)+y(t)' equation.

  5. Select the SVG image of the equation by left clicking on it. Then
  click on the Pi icon. Now, instead of editing the equation, an error
  message is displayed: "The selected object is not a TexMaths
  equation... Please unselect it and call the macro again...".

  6. Now, right click on the SVG image and select the 'Description' menu
  voice. In the window that opens, the description is empty and does not
  contain the equation text, as it should.

  7. Now purge (and not just remove) the libatk-adaptor package:

  sudo apt-get purge libatk-adaptor

  then logout and login and repeat the steps 4, 5, and 6: everything is
  OK and the equation can be edited as usual.

  Another way to remove the bug instead of purging libatk-adaptor is to
  rename the file: /etc/X11/Xsession.d/90atk-adaptor to
  /etc/X11/Xsession.d/90atk-adaptor.orig . Then logout and login.

  Note there is another bug #1584795 that relates libatk-adaptor and
  LibreOffice, see there https://bugs.launchpad.net/ubuntu/+source/at-
  spi2-atk/+bug/1584795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1641284/+subscriptions

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

[Touch-packages] [Bug 1623143] Re: Linux container does not take same cpu configuration as kernet's hosts

[Christian Brauner]

** Changed in: lxc (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Linux container does not take same cpu configuration as kernet's hosts

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  When I configured cpu affinity on a ubuntu 16.04 with kernel version 
"4.4.0-36-generic" on a host containing 3 cpus:
  on /etc/default/grub:
  GRUB_CMDLINE_LINUX_DEFAULT="isolcpus=0"

  update-grub

  reboot

  The output of "cat /proc/self/status" :
  ubuntu@ubuntu:~$ cat /proc/self/status
   .
   .
   .
  Cpus_allowed: 6
  Cpus_allowed_list:1-2
  Mems_allowed: ,0001
  Mems_allowed_list:0
  voluntary_ctxt_switches:  0
  nonvoluntary_ctxt_switches:   1

  When I create an lxd container in this host using these commands:

    lxc launch ubuntu:14.04 my-ubuntu

  And access to this container using:

    lxc exec my-ubuntu -- /bin/bash

  The output of "cat /proc/self/status" :
    .
    .
    .
  Cpus_allowed: 7
  Cpus_allowed_list:0-2
  Mems_allowed: ,0001
  Mems_allowed_list:0
  voluntary_ctxt_switches:  0
  nonvoluntary_ctxt_switches:   4

  Result: Container's process doesn't take same configuration as host's process.
  Host process use  2 cpus:  Cpus_allowed_list: 1-2
  Container process use 3 cpus: Cpus_allowed_list:  0-2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-36-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Tue Sep 13 18:36:29 2016
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-08-04 (40 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic 
root=/dev/mapper/username--vg-root ro isolcpus=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-wily
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-wily
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1641592] Re: nano 2.5.3-2 on Xenial crashes with long paths on lockfiles

[Ubuntu Foundations Team Bug Bot]

The attachment "fixes the crash when finding lockfiles for long names"
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 nano in Ubuntu.
https://bugs.launchpad.net/bugs/1641592

Title:
  nano 2.5.3-2 on Xenial crashes with long paths on lockfiles

Status in nano package in Ubuntu:
  New

Bug description:
  # lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  # apt-cache policy nano
  nano:
Installed: 2.5.3-2
Candidate: 2.5.3-2

  Reproducer:
  1. # nano -G 
999
  2. 
  3. # nano -G 
999
  4. 
  5. 

  Quick dissection:
  Looking at function do_lockfile in files.c, it seems that promptstr is 
statically allocated to 128 characters. Now with a sufficiently long filename, 
the following sprintf() call will overflow the allocated promptstr buffer and 
corrupt memory.

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

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

[Touch-packages] [Bug 1641719] [NEW] Opacity for weekend days same as for other days

[Michal Predotka]

Public bug reported:

bq M10 rc-proposed silo #2195

When I pull down the calendar indicator, I see the opacity (or maybe color) for 
weekend days is different than for other work days. But when I switch to next 
month, the opacity is the same for all days.
Please see short video with this and other bugs with this silo: 
https://youtu.be/3vg6AQZmsqE

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Opacity for weekend days same as for other days

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  bq M10 rc-proposed silo #2195

  When I pull down the calendar indicator, I see the opacity (or maybe color) 
for weekend days is different than for other work days. But when I switch to 
next month, the opacity is the same for all days.
  Please see short video with this and other bugs with this silo: 
https://youtu.be/3vg6AQZmsqE

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

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

[Touch-packages] [Bug 1641724] [NEW] Tapping the month name has no effect

[Michal Predotka]

Public bug reported:

bq M10 rc-proposed silo #2195

I would expect that tapping the month name would display events for that
month. Unfortunately the month name is not clickable.

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Tapping the month name has no effect

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  bq M10 rc-proposed silo #2195

  I would expect that tapping the month name would display events for
  that month. Unfortunately the month name is not clickable.

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

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

[Touch-packages] [Bug 1641722] [NEW] Tapping a day often results in selecting not the day I wanted to

[Michal Predotka]

Public bug reported:

bq M10 rc-proposed silo #2195

Many times when testing after tapping a day I ended up selecting a day
which was below or above the day I was aiming for.

Please see short video with this and other bugs with this silo:
https://youtu.be/3vg6AQZmsqE

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Tapping a day often results in selecting not the day I wanted to

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  bq M10 rc-proposed silo #2195

  Many times when testing after tapping a day I ended up selecting a day
  which was below or above the day I was aiming for.

  Please see short video with this and other bugs with this silo:
  https://youtu.be/3vg6AQZmsqE

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

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

[Touch-packages] [Bug 1641720] [NEW] Selecting a day does not display all day event for that day

[Michal Predotka]

Public bug reported:

bq M10 rc-proposed silo #2195

When I select a day from the calendar, I can see events for that day but
it does not work with all-day events.

Please see short video with this and other bugs with this silo:
https://youtu.be/3vg6AQZmsqE

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Selecting a day does not display all day event for that day

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  bq M10 rc-proposed silo #2195

  When I select a day from the calendar, I can see events for that day
  but it does not work with all-day events.

  Please see short video with this and other bugs with this silo:
  https://youtu.be/3vg6AQZmsqE

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

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

[Touch-packages] [Bug 1641721] [NEW] Tapping on a day near to the screen edge switches to the next month

[Michal Predotka]

Public bug reported:

bq M10 rc-proposed silo #2195

Many times when testing after clicking a day on the right hand side
(Sundays in my case), the view switched to the next month.

Please see short video with this and other bugs with this silo:
https://youtu.be/3vg6AQZmsqE

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Tapping on a day near to the screen edge switches to the next month

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  bq M10 rc-proposed silo #2195

  Many times when testing after clicking a day on the right hand side
  (Sundays in my case), the view switched to the next month.

  Please see short video with this and other bugs with this silo:
  https://youtu.be/3vg6AQZmsqE

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

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

[Touch-packages] [Bug 1641731] [NEW] Selecting a day displays more results than expected

[Michal Predotka]

Public bug reported:

bq M10 rc-proposed silo #2195

When I tap a day I expect to see events for that day only but I can see
results from the future too.

Please see short video with this and other bugs with this silo:
https://youtu.be/3vg6AQZmsqE

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Selecting a day displays more results than expected

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  bq M10 rc-proposed silo #2195

  When I tap a day I expect to see events for that day only but I can
  see results from the future too.

  Please see short video with this and other bugs with this silo:
  https://youtu.be/3vg6AQZmsqE

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

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

[Touch-packages] [Bug 1641726] [NEW] Tapping a day displays all day event from previous day

[Michal Predotka]

Public bug reported:

bq M10 rc-proposed silo #2195

When I tap on a day there are some events displayed, also from the day
before.

Please see short video with this and other bugs with this silo:
https://youtu.be/3vg6AQZmsqE

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Tapping a day displays all day event from previous day

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  bq M10 rc-proposed silo #2195

  When I tap on a day there are some events displayed, also from the day
  before.

  Please see short video with this and other bugs with this silo:
  https://youtu.be/3vg6AQZmsqE

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

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

[Touch-packages] [Bug 1641236] Re: Confined processes inside container cannot fully access host pty device passed in by lxc exec

[Stéphane Graber]

Getting openpty called in the container would solve a lot of problems
for us but it's not possible to do in a safe way as it'd effectively
rely on the container's filesystem which the container user can change
or fake at will, allowing for attacks on the host's C library and LXD
itself.

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

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

Title:
  Confined processes inside container cannot fully access host pty
  device passed in by lxc exec

Status in apparmor package in Ubuntu:
  New
Status in lxd package in Ubuntu:
  New

Bug description:
  Now that AppArmor policy namespaces and profile stacking is in place,
  I noticed odd stdout buffering behavior when running confined
  processes via lxc exec. Much more data stdout data is buffered before
  getting flushed when the program is confined by an AppArmor profile
  inside of the container.

  I see that lxd is calling openpty(3) in the host environment, using
  the returned fd as stdout, and then executing the command inside of
  the container. This results in an AppArmor denial because the file
  descriptor returned by openpty(3) originates outside of the namespace
  used by the container.

  The denial is likely from glibc calling fstat(), from inside the
  container, on the file descriptor associated with stdout to make a
  decision on how much buffering to use. The fstat() is denied by
  AppArmor and glibc ends up handling the buffering differently than it
  would if the fstat() would have been successful.

  Steps to reproduce (using an up-to-date 16.04 amd64 VM):

  Create a 16.04 container
  $ lxc launch ubuntu-daily:16.04 x

  Run tcpdump in one terminal and generate traffic in another terminal (wget 
google.com)
  $ lxc exec x -- tcpdump -i eth0
  tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
  listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
  
  47 packets captured
  48 packets received by filter
  1 packet dropped by kernel
  

  Note that everything above  was printed immediately
  because it was printed to stderr. , which is printed to
  stdout, was not printed until you pressed ctrl-c and the buffers were
  flushed thanks to the program terminating. Also, this AppArmor denial
  shows up in the logs:

  audit: type=1400 audit(1478902710.025:440): apparmor="DENIED"
  operation="getattr" info="Failed name lookup - disconnected path"
  error=-13 namespace="root//lxd-x_"
  profile="/usr/sbin/tcpdump" name="dev/pts/12" pid=15530 comm="tcpdump"
  requested_mask="r" denied_mask="r" fsuid=165536 ouid=165536

  Now run tcpdump unconfined and take note that  is printed 
immediately, before you terminate tcpdump. Also, there are no AppArmor denials.
  $ lxc exec x -- aa-exec -p unconfined -- tcpdump -i eth0
  ...

  Now run tcpdump confined but in lxc exec's non-interactive mode and note that 
 is printed immediately and no AppArmor denials are present. 
(Looking at the lxd code in lxd/container_exec.go, openpty(3) is only called in 
interactive mode)
  $ lxc exec x --mode=non-interactive -- tcpdump -i eth0
  ...

  Applications that manually call fflush(stdout) are not affected by
  this as manually flushing stdout works fine. The problem seems to be
  caused by glibc not being able to fstat() the /dev/pts/12 fd from the
  host's namespace.

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

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

[Touch-packages] [Bug 1641728] [NEW] Tapping a day to unselect it shows more events than was there before

[Michal Predotka]

Public bug reported:

bq M10 rc-proposed silo #2195

I tap a day to see events related to day day, the day is selected (color
changed to blue). Then I tap that day again to 'unselect' it. The list
of events is longer than was before tapping that day in the first place.

Please see short video with this and other bugs with this silo:
https://youtu.be/3vg6AQZmsqE

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Tapping a day to unselect it shows more events than was there before

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  bq M10 rc-proposed silo #2195

  I tap a day to see events related to day day, the day is selected
  (color changed to blue). Then I tap that day again to 'unselect' it.
  The list of events is longer than was before tapping that day in the
  first place.

  Please see short video with this and other bugs with this silo:
  https://youtu.be/3vg6AQZmsqE

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

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

[Touch-packages] [Bug 1590321] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:get_dpkg_log_content

[Brian Murray]

Verification for yakkety returned a yes.

Unpacking unattended-upgrades (0.92ubuntu1.1) over (0.92ubuntu1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (231-9git1) ...
Setting up unattended-upgrades (0.92ubuntu1.1) ...
Replacing config file /etc/apt/apt.conf.d/50unattended-upgrades with new version
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
Processing triggers for man-db (2.7.5-1) ...
bdmurray@clean-yakkety-amd64:~$ sudo /usr/bin/unattended-upgrades
bdmurray@clean-yakkety-amd64:~$ ls -lh 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
-rw-r--r-- 1 root adm 2.3K Nov 14 13:08 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log


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

** Tags removed: verification-done-yakkeyt
** Tags added: verification-done-yakkety

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

Title:
  /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-
  upgrade@1468:main:get_dpkg_log_content

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Yakkety:
  Fix Committed
Status in unattended-upgrades source package in Zesty:
  Fix Released

Bug description:
  Test Case
  -
  1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 
and Unattended-Upgrade is 1
  2) sudo apt-get update
  3) sudo /usr/bin/unattended-upgrades (to update the system)
  4) sudo /usr/bin/unattended-upgrades (a second time for some reason)
  5) sudo rm /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  6) sudo /usr/bin/unattended-upgrades

  Observe the following crash:

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1468, in 
  main(options)
    File "/usr/bin/unattended-upgrade", line 1406, in main
  log_content = get_dpkg_log_content(logfile_dpkg, install_start_time)
    File "/usr/bin/unattended-upgrade", line 1075, in get_dpkg_log_content
  with io.open(logfile_dpkg, encoding='utf-8') as fp:
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'

  With the version of the package from -proposed you won't receive the
  crash in step 6 and /var/log/unattended-upgrades/unattended-upgrades-
  dpkg.log will exist.

  Regression Potential
  
  This patch just ends up creating a file if it does not exist. Potential 
regressions would be a result of the patch being typo'ed e.g. typo'ing 
os.path.exits instead of os.path.exists and the code failing when a logfile 
does exist. So read the patch carefully!

  
  Original Description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with version 0.90, 
the problem page at 
https://errors.ubuntu.com/problem/db5f0a803afdf5bb5e20a42ce68f4fda3ce0df8a 
contains more details.

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

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

[Touch-packages] [Bug 1639977] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:write_stamp_file

[Brian Murray]

Verily verified for Yakkety.

Preparing to unpack .../unattended-upgrades_0.92ubuntu1.1_all.deb ...
Unpacking unattended-upgrades (0.92ubuntu1.1) over (0.92ubuntu1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (231-9git1) ...
Setting up unattended-upgrades (0.92ubuntu1.1) ...
Replacing config file /etc/apt/apt.conf.d/50unattended-upgrades with new version
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
Processing triggers for man-db (2.7.5-1) ...
bdmurray@clean-yakkety-amd64:~$ ls 
/var/lib/apt/periodic/unattended-upgrades-stamp
ls: cannot access '/var/lib/apt/periodic/unattended-upgrades-stamp': No such 
file or directory
bdmurray@clean-yakkety-amd64:~$ sudo /usr/bin/unattended-upgrade
bdmurray@clean-yakkety-amd64:~$ ls 
/var/lib/apt/periodic/unattended-upgrades-stamp
/var/lib/apt/periodic/unattended-upgrades-stamp


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

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

Title:
  /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-
  upgrade@1468:main:write_stamp_file

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

Bug description:
  Test Case
  -
  1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 
and Unattended-Upgrade is 1
  2) sudo apt-get update
  3) sudo rm -fr /var/lib/apt/periodic
  4) sudo /usr/bin/unattended-upgrade
  5) observe the following Traceback

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1468, in 
  main(options)
    File "/usr/bin/unattended-upgrade", line 1419, in main
  write_stamp_file()
    File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file
  with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"):
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/lib/apt/periodic/unattended-upgrades-stamp'

  With the version of the package from -proposed you'll receive no such
  Traceback.

  Regression Potential
  
  This patch just ends up creating a directory if it does not exist.  Potential 
regressions would be a result of the patch being typo'ed e.g. typo'ing 
os.path.exits instead of os.path.exists and the code failing when a statedir 
does exist.  So read the patch carefully!

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

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

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

[Touch-packages] [Bug 1641358] Re: libgtk-3 should avoid configuration --enable-debug=no

[Andrew Shu]

I'm sorry for wasting your time. The problem does not appear to be a
misconfigured libgtk. From your links, it looks like it is already using
a configuration equivalent to --enable-debug=minimum.

Thank you for linking the build configurations, I would never have been
able to find those. Launchpad is a bit hard for me to navigate.

I am using Xenial, libgtk-3-0, 3.18.9-1ubuntu3.1

I will do further investigation to see if the bug is in Gtk-rs, or
Nautilus configuration, or elsewhere.

This bug can be closed. Thank you.

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

Title:
  libgtk-3 should avoid configuration --enable-debug=no

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  The packaging guidelines for libgtk say to avoid using "--enable-
  debug=no" when packaging stable releases of GTK+. [1]

  The "--enable-debug=no" option can cause subtle errors and should be
  avoided. "--disable-debug" is another alias for this configuration
  option.

  More info and discussion at the Gtk-rs project (Rust bindings for
  GTK). [2]

  [1]: 
https://developer.gnome.org/gtk3/stable/gtk-building.html#extra-configuration-options
  [2]: https://github.com/gtk-rs/gtk/issues/270

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

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

[Touch-packages] [Bug 1640123] Re: When Ubuntu16.04.1 is in the virtualbox with NAT adapter, the network will have errors about "Connection reset by peer"

[Launchpad Bug Tracker]

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

Title:
  When Ubuntu16.04.1 is in the  virtualbox with NAT adapter, the network
  will have errors about "Connection reset by peer"

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  By means of vagrant for using the ubuntu/xenial64 box, or under the 
virtualbox 5.1.6/5.1.8, installing ubuntu-16.04.1-server-amd64.iso (default 
installation + openssh server), ubuntu-16.04.1-desktop-amd64.iso (default 
installation), designate the Adapter1 of Guest OS as NAT type.
  In this case, some commands are executed with a "Connection reset by peer" 
error, such as apt-key or docker pull.

   The current test results 
  If the network is not NAT but NAT Network or Host Only, it will not go wrong.
  If the virtual machine is not virtualbox, it will not go wrong.
  Keeping other unchanged and just replacing centos with Ubuntu, it will not go 
wrong.
  Under different wifi environment, the test results remain unchanged.
  Upgrade all ubuntu to the latest version by using sudo apt upgrade, the test 
results are unchanged.

  Maybe the combination of virtualbox + NAT + ubuntu1604 is the reason
  and this error is very convert. Other network functions are available,
  may have errors only in a specific command.

   Repeating Steps 
  1. Run "vagrant init ubuntu/xenial64" in an empty directory
  2. vagrant up
  3. vagrant ssh
  4. Run "sudo apt-key adv --keyserver hkp://ha.pool.sks-keyservers.net:11371 
--recv-keys 58118E89F3A912897C070ADBF76221572C52609D" in Guest OS.

  The output is as follows :
  Executing: /tmp/tmp.LO7eukZqdi/gpg.1.sh --keyserver
  hkp://ha.pool.sks-keyservers.net:11371
  --recv-keys
  58118E89F3A912897C070ADBF76221572C52609D
  gpg: requesting key 2C52609D from hkp server ha.pool.sks-keyservers.net
  ?: [fd 4]: read error: Connection reset by peer
  gpgkeys: key 58118E89F3A912897C070ADBF76221572C52609D partially retrieved 
(probably corrupt)
  gpg: no valid OpenPGP data found.
  gpg: key 2C52609D: no valid user IDs
  gpg: this may be caused by a missing self-signature
  gpg: Total number processed: 1
  gpg: w/o user IDs: 1

  There is an error message during this "? : [fd 4]: read error:
  Connection reset by peer"

   Another error scene 
  I created a docker registry (called S) on the virtual machine of IDC, and 
when I ran "docker pull xxx" from another ubuntu Guest OS (called C) 
(virtualbox + NAT), you can see something from /var/log/syslog in C as follows:
  Nov 3 12:59:00 ubuntu-xenial dockerd[2167]: 
time="2016-11-03T12:59:00.506141276Z" level=error msg="Error trying v2 
registry: read tcp 10.0.2.15:33580->10.99.169.227:5000: read: connection reset 
by peer"
  Nov 3 12:59:00 ubuntu-xenial dockerd[2167]: 
time="2016-11-03T12:59:00.506732903Z" level=error msg="Attempting next endpoint 
for pull after error: read tcp 10.0.2.15:33580->10.99.169.227:5000: read: 
connection reset by peer”
  The 10.99.169.227 is the ip of S.
  S is also Ubuntu 16.04.1 LTS, but which is not running under the virtualbox.  
Run the above repeating steps 4 in S will not appear "Connection reset by peer" 
error.

   Script which can be executed on other system 
  Attachment is a test script, which is copied from output /tmp/tmp.LO7eukZqdi 
directory of the above repeating step 4. You can perform a test on any system 
by following these steps:
  1. tar -xf gpgtest.tar
  2. cd gpgtest
  3. ./gpg.1.sh --keyserver hkp://ha.pool.sks-keyservers.net:11371 --recv-keys 
58118E89F3A912897C070ADBF76221572C52609D

  In the environment of virtualbox + NAT + ubuntu, output will be like this:
  gpg: WARNING: unsafe permissions on homedir `.'
  gpg: requesting key 2C52609D from hkp server ha.pool.sks-keyservers.net
  ?: [fd 4]: read error: Connection reset by peer
  gpgkeys: key 58118E89F3A912897C070ADBF76221572C52609D partially retrieved 
(probably corrupt)
  gpg: no valid OpenPGP data found.
  gpg: key 2C52609D: no valid user IDs
  gpg: this may be caused by a missing self-signature
  gpg: Total number processed: 1
  gpg: w/o user IDs: 1

  You can see the output of "?: [Fd 4]: read error: Connection reset by
  peer".

  Under the vagrant + virtualbox + centos/7 box + NAT, the script output is 
like this:
  gpg: 警告：用户目录‘.’权限不安全
  gpg: 下载密钥‘2C52609D’，从 hkp 服务器 ha.pool.sks-keyservers.net
  gpg: 密钥 2C52609D：“Docker Release Tool (releasedocker) ”未改变
  gpg: 合计被处理的数量：1
  gpg: 未改变：1

   My test environment 
  Macbook pro 15, macOS 10.12.1 (16B2555), XPS15 (win10), MiBook13 (win10)
  Vagrant 1.8.6
  VirtualBox 5.1.6, 5.1.8
  vagrant box ubuntu/xenial64 20161102.0.0, 20161104.0.0
  vagrant box centos/7 1609.01
  ubuntu-16.04.1-server-amd64.iso (default in

[Touch-packages] [Bug 1546455] Re: Many instances of 'apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec" sock_type="dgram" protocol=0' in syslog

[Christian Boltz]

While support for "unspec" was added some months ago, the nptd profile
in upstream bzr wasn't updated. I just did this - trunk r3583, 2.10
branch r3360, 2.9 branch r3090.

See also https://bugzilla.opensuse.org/show_bug.cgi?id=1009964

** Bug watch added: bugzilla.opensuse.org/ #1009964
   http://bugzilla.opensuse.org/show_bug.cgi?id=1009964

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

Title:
  Many instances of 'apparmor="DENIED" operation="create"
  profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec"
  sock_type="dgram" protocol=0' in syslog

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Fix Released

Bug description:
  I just dist-upgraded to this version of ntp which arrived in xenial
  very recently. Since then I'm being constantly spammed with libnotify
  notifications about the following

  Feb 17 09:59:55 raleigh.local kernel: audit: type=1400 
audit(1455703195.606:429): apparmor="DENIED" operation="create" 
profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec" 
sock_type="dgram" protocol=0
  Feb 17 09:59:55 raleigh.local kernel: audit: type=1400 
audit(1455703195.606:430): apparmor="DENIED" operation="create" 
profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec" 
sock_type="dgram" protocol=0
  Feb 17 09:59:55 raleigh.local kernel: audit: type=1400 
audit(1455703195.606:431): apparmor="DENIED" operation="create" 
profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec" 
sock_type="dgram" protocol=0
  Feb 17 09:59:55 raleigh.local kernel: audit: type=1400 
audit(1455703195.606:432): apparmor="DENIED" operation="create" 
profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec" 
sock_type="dgram" protocol=0
  Feb 17 09:59:55 raleigh.local kernel: audit: type=1400 
audit(1455703195.606:433): apparmor="DENIED" operation="create" 
profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec" 
sock_type="dgram" protocol=0
  […]
  Feb 17 09:59:59 raleigh.local kernel: audit: type=1400 
audit(1455703199.526:434): apparmor="DENIED" operation="create" 
profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec" 
sock_type="dgram" protocol=0
  Feb 17 09:59:59 raleigh.local kernel: audit: type=1400 
audit(1455703199.526:435): apparmor="DENIED" operation="create" 
profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec" 
sock_type="dgram" protocol=0
  Feb 17 09:59:59 raleigh.local kernel: audit: type=1400 
audit(1455703199.526:436): apparmor="DENIED" operation="create" 
profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec" 
sock_type="dgram" protocol=0
  Feb 17 09:59:59 raleigh.local kernel: audit: type=1400 
audit(1455703199.526:437): apparmor="DENIED" operation="create" 
profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec" 
sock_type="dgram" protocol=0
  Feb 17 09:59:59 raleigh.local kernel: audit: type=1400 
audit(1455703199.526:438): apparmor="DENIED" operation="create" 
profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec" 
sock_type="dgram" protocol=0

  argh!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb 17 09:57:02 2016
  InstallationDate: Installed on 2012-10-07 (1227 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: ntp
  UpgradeStatus: Upgraded to xenial on 2013-05-07 (1016 days ago)

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

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

[Touch-packages] [Bug 1627697] [NEW] gnome-terminal crashes on resize

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Yakkety, Mir-0.24, lp:miral

Run gnome-terminal on a touchscreen laptop and resizing by three-finger
pinch...

$ miral-run gnome-terminal
$ 
(gnome-terminal-server:4817): Gtk-WARNING **: GtkSettings Cursor Theme: 
Unsupported GDK backend
...
(gnome-terminal-server:4817): Gdk-WARNING **: unknown property 
gtk-fontconfig-timestamp

(gnome-terminal-server:4817): Gdk-WARNING **: Ignoring unknown Mir event
11

(gnome-terminal-server:4817): Gtk-WARNING **: Allocating size to GtkBox 
0x55eb906c6900 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
*** Error in `/usr/lib/gnome-terminal/gnome-terminal-server': double free or 
corruption (out): 0x7f2e70258010 ***

(Can't reproduce with Mir-0.1, but that may be because resize was too
broken.)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: miral
 Importance: Undecided
 Status: Fix Committed


** Tags: gtk-mir
-- 
gnome-terminal crashes on resize
https://bugs.launchpad.net/bugs/1627697
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 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 1641779] [NEW] printer cropping the top off on prints

[BronsonMathews]

Public bug reported:

using a hp photosmart 5520 over the wireless. Im fairly positive this worked 
fine on 15.10.
But on 16.04 when printing the top of the page is always cropped off.

Ive tried all the things on the following page:
http://askubuntu.com/questions/112684/why-does-ubuntu-add-a-5-margin-to-the-top-when-printing-to-my-hp-psc-750

however no luck at all with any of these.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4
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
CupsErrorLog:
 W [15/Nov/2016:11:28:01 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-Gray..\' already exists
 W [15/Nov/2016:11:28:01 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-RGB..\' already exists
 W [15/Nov/2016:11:30:34 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-Gray..\' already exists
 W [15/Nov/2016:11:30:34 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-RGB..\' already exists
CurrentDesktop: Unity
Date: Tue Nov 15 11:33:32 2016
InstallationDate: Installed on 2016-08-15 (92 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lpstat: device for HP-Photosmart-5520-series: 
dnssd://Photosmart%205520%20series%20%5BDF47AD%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-fc15b4df47ad
MachineType: TOSHIBA Satellite L850
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-Photosmart-5520-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-Photosmart-5520-series.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=4657cafb-40f4-447f-b155-5e2db880d622 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/24/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.40
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.40:bd04/24/2012:svnTOSHIBA:pnSatelliteL850:pvrPSKDLA-0CC00R:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L850
dmi.product.version: PSKDLA-0CC00R
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug xenial

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

Title:
  printer cropping the top off on prints

Status in cups package in Ubuntu:
  New

Bug description:
  using a hp photosmart 5520 over the wireless. Im fairly positive this worked 
fine on 15.10.
  But on 16.04 when printing the top of the page is always cropped off.

  Ive tried all the things on the following page:
  
http://askubuntu.com/questions/112684/why-does-ubuntu-add-a-5-margin-to-the-top-when-printing-to-my-hp-psc-750

  however no luck at all with any of these.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  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
  CupsErrorLog:
   W [15/Nov/2016:11:28:01 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-Gray..\' already exists
   W [15/Nov/2016:11:28:01 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-RGB..\' already exists
   W [15/Nov/2016:11:30:34 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-Gray..\' already exists
   W [15/Nov/2016:11:30:34 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-RGB..\' already exists
  CurrentDesktop: Unity
  Date: Tue Nov 15 11:33:32 2016
  InstallationDate: Installed on 2016-08-15 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: device for HP-Photosmart-5520-series: 
dnssd://Photosmart%205520%20series%20%5BDF47AD%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-fc15b4df47ad
  MachineType: TOSHIBA Satellite L850
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-Photosmart-5520-series.ppd'] failed with exit code 2: