[Touch-packages] [Bug 1633698] Re: ufw before6.rules adds echo-request and echo-response rules to wrong chain

2017-01-11 Thread Launchpad Bug Tracker
This bug was fixed in the package ufw - 0.35-3

---
ufw (0.35-3) unstable; urgency=medium

  * 0002-bug849628.patch: adjust testsuite for recent changes to netbase
(Closes: 849628)
  * 0003-use-default-tcp-syncookies.patch: don't override distribution default
for TCP syncookies
  * 0004-lp1633698.patch: adjust ufw6-before-output rules for echo-reply and
echo-request (LP: #1633698)
  * update debian/before6.rules.md5sum
  * fix lintian errors:
- debian/control: Build-Depends on dh-python and debhelper >= 9
- debian/compat: use compatibility level 9

 -- Jamie Strandboge   Sun, 08 Jan 2017 16:33:45 +

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

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

Title:
  ufw before6.rules adds echo-request and echo-response rules to wrong
  chain

Status in ufw:
  Fix Committed
Status in ufw package in Ubuntu:
  Fix Released

Bug description:
  The default before6.rules file that is installed with the ufw package
  contains a copy/paste error. It is apparent that the intention is to
  add rules for echo-request and echo-response to the following chains:

  ufw6-before-input
  ufw6-before-output
  ufw6-before-forward

  However there is a copy/paste error and instead of adding the rules to
  ufw6-before-output, it adds it to ufw6-before-input a second time. The
  result is that the rules are absent from ufw6-before-output.

  The file that needs to be fixed in the package is:
  /usr/share/ufw/iptables/before6.rules

  Here is what diff -u shows if I compare the original file to the
  corrected version:

  --- /usr/share/ufw/iptables/before6.rules 2016-04-15 17:16:29.0 
+1200
  +++ ufw_fixed_before6.rules   2016-10-15 23:00:57.763041239 +1300
  @@ -77,8 +77,8 @@
   -A ufw6-before-output -p icmpv6 --icmpv6-type time-exceeded -j ACCEPT
   # codes 0-2
   -A ufw6-before-output -p icmpv6 --icmpv6-type parameter-problem -j ACCEPT
  --A ufw6-before-input -p icmpv6 --icmpv6-type echo-request -j ACCEPT
  --A ufw6-before-input -p icmpv6 --icmpv6-type echo-reply -j ACCEPT
  +-A ufw6-before-output -p icmpv6 --icmpv6-type echo-request -j ACCEPT
  +-A ufw6-before-output -p icmpv6 --icmpv6-type echo-reply -j ACCEPT
   -A ufw6-before-output -p icmpv6 --icmpv6-type router-solicitation -m hl 
--hl-eq 255 -j ACCEPT
   -A ufw6-before-output -p icmpv6 --icmpv6-type neighbor-advertisement -m hl 
--hl-eq 255 -j ACCEPT
   -A ufw6-before-output -p icmpv6 --icmpv6-type neighbor-solicitation -m hl 
--hl-eq 255 -j ACCEPT

  The impact of this error is minor because the ufw.conf file sets the default 
outbound policy to accept:
  DEFAULT_OUTPUT_POLICY="ACCEPT"

  Of course if anyone changed the default outbound policy then the error
  would mean that pings made from the server to other machines would be
  blocked.

  I will attach the original and my fixed version of before6.rules to
  this bug report.

  Thanks for taking the time to look at this issue.

  Nick.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ufw 0.35-2
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic i686
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  Date: Sat Oct 15 23:09:04 2016
  InstallationDate: Installed on 2016-10-14 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release i386 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

2017-01-11 Thread Aron Xu
Mark as Fix Released in Zesty.

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Triaged
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

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

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

  For xenial, we'll also backporting a patch from 1.2.6 that should fix
  a no-networking-after-resuming-from-sleep issue. This patch was
  applied to Debian testing and zesty in 1.4.2-3ubuntu1.

  For yakkety, this is an update to 1.2.6. Once 1.2.6 has been in use
  for a while without new problems, we'll look into doing a separate SRU
  for Xenial.

  [Test Case]

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

  [Regression Potential]

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

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

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


[Touch-packages] [Bug 1654192] Re: resizing windows not working properly

2017-01-11 Thread Michael Zanetti
checking unity8's code again, I am very confident this happens in lower
layers, likely miral.

** 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/1654192

Title:
  resizing windows not working properly

Status in Canonical System Image:
  New
Status in miral package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Run this qml app:

  http://paste.ubuntu.com/23738946/

  try resizing it, after releasing the mouse it will always resize
  itself back to be tiny...

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

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


[Touch-packages] [Bug 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

2017-01-11 Thread Albert Astals Cid
Unfortunately I don't run a xenial machine anymore (i'm on zesty now) so
I'd appreciate if someone else could do the testing.

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

Title:
  keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

Status in Canonical System Image:
  Confirmed
Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in libertine package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  New
Status in libertine source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Fix Released
Status in xorg-server package in Ubuntu RTM:
  New

Bug description:
  [Impact]

  Auto key repeating does not work in Libertine X apps which is very
  frustrating to users.

  [Test Case]

  1. Install xterm in libertine
  2. Start xterm from the "Xapps" scope
  3. Wait for xterm to appear
  4. Press and hold a key

  See how it only appears once and not multiple times as it should.

  [Regression Potential]

  Non observed.

  
  Original Description:

  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

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

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


[Touch-packages] [Bug 1392699] Re: Can't change locale settings (e.g. language, 12/24-hour time, date format) independently

2017-01-11 Thread Jean-Baptiste Lallement
** Changed in: canonical-devices-system-image
 Assignee: Jean-Baptiste Lallement (jibel) => (unassigned)

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

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

Title:
  Can't change locale settings (e.g. language, 12/24-hour time, date
  format) independently

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  A. Try to use US English, but with all apps using 24-hour instead of 12-hour 
time. Or:
  B. Try to use UK English, but with all apps using -MM-DD date format.

  What happens: You can't.
  What should happen: You can.

  Since Ubuntu has existed, it has used the GNU locale system. This
  system assumes that every single person using a particular locale
  wants exactly the same settings for time display, date display,
  currency display, alphabetizing, and number formatting.
  

  Windows, Mac OS, and (to a lesser extent) iOS have always been more
  flexible: setting a locale sets appropriate defaults for these
  settings, but you can also change them individually. Ubuntu should do
  the same.

  This might involve changing the locale system itself, or it might
  involve changing all relevant toolkits so that they ignore the locale
  system when appropriate.

  It would also involve adding settings in System Settings to customize
  the individual locale details.

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

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


[Touch-packages] [Bug 1591547] Re: Merge pcsc-lite 1.8.17-1 (main) from Debian testing (main)

2017-01-11 Thread Amr Ibrahim
Ping!

** Summary changed:

- Merge pcsc-lite 1.8.17-1 (main) from Debian testing (main)
+ Merge pcsc-lite 1.8.20-1 (main) from Debian testing (main)

** Description changed:

- Please merge pcsc-lite 1.8.17-1 (main) from Debian testing (main)
+ Please merge pcsc-lite 1.8.20-1 (main) from Debian testing (main) for bugs 
and security fixes.
+ ---
+ 
+ 1.8.20: Ludovic Rousseau
+ 30 December 2016
+ - Fix a crash and potential security issue in pcscd
+ 
+ 
+ 1.8.19: Ludovic Rousseau
+ 9 December 2016
+ - SCardGetStatusChange(): Fix a (rare) race condition
+ - Doxygen:
+   . SCardGetStatusChange() may return SCARD_E_UNKNOWN_READER
+   . SCardConnect() and SCardReconnect() will never return SCARD_E_NOT_READY
+ - pcsc-spy:
+   . fix display of execution time
+   . log the thread number in the results
+ - Some other minor improvements
+ 
+ 
+ 1.8.18: Ludovic Rousseau
+ 10 August 2016
+ - SCardDisconnect(): much faster with SCARD_UNPOWER_CARD
+ - SCardConnect(): Fix a possible duplicated hCard context
+ - Fix compilation on FreeBSD
+ - Fix compilation on Solaris
+ - Some other minor improvements
+ 
  
  1.8.17: Ludovic Rousseau
  29 May 2016
  - Fix SCardEndTransaction() issue with a SCARD_SHARE_EXCLUSIVE connection
  - Fix an issue when used with systemd (problem in signal handler)
  - SCardGetAttrib(): set pcbAttrLen when buffer is too small
  - Doxygen: SCardGetAttrib() pbAttr can be NULL
  - Doxygen: SCardGetAttrib() *pcbAttrLen contains the buffer size
  - fix compilation warnings and link errors on SunOS
  - Some other minor improvements
  
  
  1.8.16: Ludovic Rousseau
  20 March 2016
  - SCardCancel() was not correctly handled
-   When a SCardGetStatusChange() was cancelled then a next PC/SC call
-   after the SCardGetStatusChange() may fail with a strange error code if
-   the event waited in SCardGetStatusChange() occurs.
+   When a SCardGetStatusChange() was cancelled then a next PC/SC call
+   after the SCardGetStatusChange() may fail with a strange error code if
+   the event waited in SCardGetStatusChange() occurs.
  - Doxygen: fix different documentation issues
  - SCARD_SCOPE_GLOBAL is now defined in a public header (even if never used)
  - Enable Trace and Profile features using compiler flags and without
-   modifying the source code
+   modifying the source code
  - Some other minor improvements and bug corrections
  
  
  1.8.15: Ludovic Rousseau
  25 December 2015
  - Add support of remove and/or customize PC/SC reader names using
-   PCSCLITE_FILTER_IGNORE_READER_NAMES and PCSCLITE_FILTER_EXTEND_READER_NAMES
-   See 
http://ludovicrousseau.blogspot.fr/2015/12/remove-andor-customize-pcsc-reader-names.html
+   PCSCLITE_FILTER_IGNORE_READER_NAMES and PCSCLITE_FILTER_EXTEND_READER_NAMES
+   See 
http://ludovicrousseau.blogspot.fr/2015/12/remove-andor-customize-pcsc-reader-names.html
  - Some other minor improvements and bug corrections
  -
  
  Explanation of the Ubuntu delta:
-   * Merge new upstream release from Debian Unstable (LP: #1483750).
- - debian/rules: Move runtime libraries to /lib, for the benefit of
-   wpasupplicant. (See Debian #531592)
+   * Merge new upstream release from Debian Unstable (LP: #1483750).
+ - debian/rules: Move runtime libraries to /lib, for the benefit of
+   wpasupplicant. (See Debian #531592)
  
  Sorry, my packaging skills are zero, so that I can't work on this merge.
  -
  
  Changelog entries since current yakkety version 1.8.14-1ubuntu1:
  
+ pcsc-lite (1.8.20-1) unstable; urgency=medium
+ 
+   * New upstream release
+ 
+  -- Ludovic Rousseau   Fri, 30 Dec 2016 18:17:58
+ +0100
+ 
+ pcsc-lite (1.8.19-1) unstable; urgency=medium
+ 
+   * New upstream release
+ 
+  -- Ludovic Rousseau   Fri, 09 Dec 2016 10:11:15
+ +0100
+ 
+ pcsc-lite (1.8.18-1) unstable; urgency=medium
+ 
+   * New upstream release
+ 
+  -- Ludovic Rousseau   Wed, 10 Aug 2016 20:56:54
+ +0200
+ 
  pcsc-lite (1.8.17-1) unstable; urgency=medium
  
-   * New upstream release
-   * debian/control: Standards-Version: 3.9.7 -> 3.9.8. No change needed.
+   * New upstream release
+   * debian/control: Standards-Version: 3.9.7 -> 3.9.8. No change needed.
  
-  -- Ludovic Rousseau   Sun, 29 May 2016 17:30:12
+  -- Ludovic Rousseau   Sun, 29 May 2016 17:30:12
  +0200
  
  pcsc-lite (1.8.16-1) unstable; urgency=medium
  
-   * New upstream release
-   * debian/control: fix lintian warning vcs-field-uses-insecure-uri 
vcs-browser
- Use https:// instead of http://
-   * debian/control: Standards-Version: 3.9.6 -> 3.9.7. No change needed.
-   * debian/rules: use "hardening=+all" to harden even more the binaries
+   * New upstream release
+   * debian/control: fix lintian warning vcs-field-uses-insecure-uri 
vcs-browser
+ Use https:// instead of http://
+   * debian/control: Standards-Version

[Touch-packages] [Bug 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

2017-01-11 Thread Daniel van Vugt
The fix is already in xenial (see above). Chris is asking for trusty
testing. Similarly I don't run trusty :)

Surely whoever requested this for trusty should be able to test it? Is
there such a person?

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

Title:
  keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

Status in Canonical System Image:
  Confirmed
Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in libertine package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  New
Status in libertine source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Fix Released
Status in xorg-server package in Ubuntu RTM:
  New

Bug description:
  [Impact]

  Auto key repeating does not work in Libertine X apps which is very
  frustrating to users.

  [Test Case]

  1. Install xterm in libertine
  2. Start xterm from the "Xapps" scope
  3. Wait for xterm to appear
  4. Press and hold a key

  See how it only appears once and not multiple times as it should.

  [Regression Potential]

  Non observed.

  
  Original Description:

  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

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

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


[Touch-packages] [Bug 1591547] Re: Merge pcsc-lite 1.8.20-1 (main) from Debian testing (main)

2017-01-11 Thread Amr Ibrahim
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-10109

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

Title:
  Merge pcsc-lite 1.8.20-1 (main) from Debian testing (main)

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  Please merge pcsc-lite 1.8.20-1 (main) from Debian testing (main) for bugs 
and security fixes.
  ---

  1.8.20: Ludovic Rousseau
  30 December 2016
  - Fix a crash and potential security issue in pcscd

  
  1.8.19: Ludovic Rousseau
  9 December 2016
  - SCardGetStatusChange(): Fix a (rare) race condition
  - Doxygen:
. SCardGetStatusChange() may return SCARD_E_UNKNOWN_READER
. SCardConnect() and SCardReconnect() will never return SCARD_E_NOT_READY
  - pcsc-spy:
. fix display of execution time
. log the thread number in the results
  - Some other minor improvements

  
  1.8.18: Ludovic Rousseau
  10 August 2016
  - SCardDisconnect(): much faster with SCARD_UNPOWER_CARD
  - SCardConnect(): Fix a possible duplicated hCard context
  - Fix compilation on FreeBSD
  - Fix compilation on Solaris
  - Some other minor improvements

  
  1.8.17: Ludovic Rousseau
  29 May 2016
  - Fix SCardEndTransaction() issue with a SCARD_SHARE_EXCLUSIVE connection
  - Fix an issue when used with systemd (problem in signal handler)
  - SCardGetAttrib(): set pcbAttrLen when buffer is too small
  - Doxygen: SCardGetAttrib() pbAttr can be NULL
  - Doxygen: SCardGetAttrib() *pcbAttrLen contains the buffer size
  - fix compilation warnings and link errors on SunOS
  - Some other minor improvements

  
  1.8.16: Ludovic Rousseau
  20 March 2016
  - SCardCancel() was not correctly handled
    When a SCardGetStatusChange() was cancelled then a next PC/SC call
    after the SCardGetStatusChange() may fail with a strange error code if
    the event waited in SCardGetStatusChange() occurs.
  - Doxygen: fix different documentation issues
  - SCARD_SCOPE_GLOBAL is now defined in a public header (even if never used)
  - Enable Trace and Profile features using compiler flags and without
    modifying the source code
  - Some other minor improvements and bug corrections

  
  1.8.15: Ludovic Rousseau
  25 December 2015
  - Add support of remove and/or customize PC/SC reader names using
    PCSCLITE_FILTER_IGNORE_READER_NAMES and PCSCLITE_FILTER_EXTEND_READER_NAMES
    See 
http://ludovicrousseau.blogspot.fr/2015/12/remove-andor-customize-pcsc-reader-names.html
  - Some other minor improvements and bug corrections
  -

  Explanation of the Ubuntu delta:
    * Merge new upstream release from Debian Unstable (LP: #1483750).
  - debian/rules: Move runtime libraries to /lib, for the benefit of
    wpasupplicant. (See Debian #531592)

  Sorry, my packaging skills are zero, so that I can't work on this merge.
  -

  Changelog entries since current yakkety version 1.8.14-1ubuntu1:

  pcsc-lite (1.8.20-1) unstable; urgency=medium

* New upstream release

   -- Ludovic Rousseau   Fri, 30 Dec 2016 18:17:58
  +0100

  pcsc-lite (1.8.19-1) unstable; urgency=medium

* New upstream release

   -- Ludovic Rousseau   Fri, 09 Dec 2016 10:11:15
  +0100

  pcsc-lite (1.8.18-1) unstable; urgency=medium

* New upstream release

   -- Ludovic Rousseau   Wed, 10 Aug 2016 20:56:54
  +0200

  pcsc-lite (1.8.17-1) unstable; urgency=medium

    * New upstream release
    * debian/control: Standards-Version: 3.9.7 -> 3.9.8. No change needed.

   -- Ludovic Rousseau   Sun, 29 May 2016 17:30:12
  +0200

  pcsc-lite (1.8.16-1) unstable; urgency=medium

    * New upstream release
    * debian/control: fix lintian warning vcs-field-uses-insecure-uri 
vcs-browser
  Use https:// instead of http://
    * debian/control: Standards-Version: 3.9.6 -> 3.9.7. No change needed.
    * debian/rules: use "hardening=+all" to harden even more the binaries

   -- Ludovic Rousseau   Sun, 20 Mar 2016 17:28:29
  +0100

  pcsc-lite (1.8.15-1) unstable; urgency=medium

    * New upstream release

   -- Ludovic Rousseau   Fri, 25 Dec 2015 21:28:30
  +0100

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

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


[Touch-packages] [Bug 1638301] Re: systemctl start auto-completion shows error

2017-01-11 Thread Rigo
Where I can I find a workaround for current systems (16.04,16.10)?

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

Title:
  systemctl start  auto-completion shows error

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  When i try to auto-complete the "systemctl start " the
  following error message is shown in bash:

  Unit org.freedesktop.network1.busname could not be found.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:42:37 2016
  InstallationDate: Installed on 2015-06-20 (499 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Dell System Vostro 3450
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=7468e7be-a2e1-48dd-ba72-244c33698364 ro cgroup_enable=memory 
swapaccount=1 quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (12 days ago)
  dmi.bios.date: 07/22/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0GG0VM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/22/2011:svnDellInc.:pnDellSystemVostro3450:pvr:rvnDellInc.:rn0GG0VM:rvrA01:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System Vostro 3450
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour

2017-01-11 Thread Sebastien Bacher
Thanks FanJun for looking at this one

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

** Changed in: avahi (Ubuntu)
 Assignee: Canonical Desktop Team (canonical-desktop-team) => FanJun Kong - 
( BH1SCW ) (fjkong)

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

Title:
  avahi-daemon crashes multiple times an hour

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Ever since upgrading to 16.10, avahi-daemon crashes multiple times an
  hour, leading to the prompt to report the issue to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:48:35 2016
  InstallationDate: Installed on 2016-07-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago)

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

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


[Touch-packages] [Bug 1655584] [NEW] systemd-udevd busyloops when nvidia kernel module fails to load

2017-01-11 Thread Lauri Tirkkonen
Public bug reported:

On a machine where nvidia-367 is installed, but the driver won't attach (due to
the nvidia card being older and requiring legacy drivers), systemd-udevd
repeatedly attempts to load it anyway, causing high CPU and memory usage. I
observed the systemd-udevd process at 98% CPU usage and 2.5G RSS reported by
top(1); restarting the service reduces resource usage momentarily, but it
appears to be climbing back up (I suspect the number of events is growing).

Workaround is of course installing the correct driver package, but udevd really
ought not behave like this if something fails to load.

Some journal entries for systemd-udevd.service:

Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' 
failed with exit code 1.
Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' 
failed with exit code 1.
Jan 11 11:22:11 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' failed 
with exit code 9.
Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe 
nvidia-modeset' failed with exit code 1.
Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' 
failed with exit code 1.
Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' 
failed with exit code 1.
Jan 11 11:22:12 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' failed 
with exit code 9.
Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe 
nvidia-modeset' failed with exit code 1.
Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' 
failed with exit code 1.
Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' 
failed with exit code 1.

dmesg shows repeated failures for loading the nvidia module:

[1675406.587926] NVRM: The NVIDIA GeForce 9300 GE GPU installed in this 
system is
 NVRM:  supported through the NVIDIA 340.xx Legacy drivers. 
Please
 NVRM:  visit http://www.nvidia.com/object/unix.html for 
more
 NVRM:  information.  The 367.57 NVIDIA driver will ignore
 NVRM:  this GPU.  Continuing probe...
[1675406.587936] NVRM: No NVIDIA graphics adapter found!
[1675406.588078] NVRM: NVIDIA init module failed!

Release information:

# lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
# apt policy systemd udev
systemd:
  Installed: 229-4ubuntu13
  Candidate: 229-4ubuntu13
  Version table:
 *** 229-4ubuntu13 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 229-4ubuntu10 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 229-4ubuntu4 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial/main amd64 Packages
udev:
  Installed: 229-4ubuntu13
  Candidate: 229-4ubuntu13
  Version table:
 *** 229-4ubuntu13 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 229-4ubuntu10 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 229-4ubuntu4 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial/main amd64 Packages

** 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/1655584

Title:
  systemd-udevd busyloops when nvidia kernel module fails to load

Status in systemd package in Ubuntu:
  New

Bug description:
  On a machine where nvidia-367 is installed, but the driver won't attach (due 
to
  the nvidia card being older and requiring legacy drivers), systemd-udevd
  repeatedly attempts to load it anyway, causing high CPU and memory usage. I
  observed the systemd-udevd process at 98% CPU usage and 2.5G RSS reported by
  top(1); restarting the service reduces resource usage momentarily, but it
  appears to be climbing back up (I suspect the number of events is growing).

  Workaround is of course installing the correct driver package, but udevd 
really
  ought not behave like this if something fails to load.

  Some journal entries for systemd-udevd.service:

  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' 
failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' 
failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' 
failed with exit code 9.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe 
nvidia-modeset' failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' 
failed with exit code 1.

[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour

2017-01-11 Thread Sebastien Bacher
similar report on Debian but without much useful content,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841926 , seems it
started with 0.6.32

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

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

Title:
  avahi-daemon crashes multiple times an hour

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Ever since upgrading to 16.10, avahi-daemon crashes multiple times an
  hour, leading to the prompt to report the issue to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:48:35 2016
  InstallationDate: Installed on 2016-07-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago)

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

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


[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour

2017-01-11 Thread Sebastien Bacher
upstream mailing list message about a similar issue,
https://lists.freedesktop.org/archives/avahi/2016-October/002439.html

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

Title:
  avahi-daemon crashes multiple times an hour

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Ever since upgrading to 16.10, avahi-daemon crashes multiple times an
  hour, leading to the prompt to report the issue to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:48:35 2016
  InstallationDate: Installed on 2016-07-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago)

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

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


[Touch-packages] [Bug 1527166] Re: cron.daily/apt reports MarkUpgrade() called on a non-upgrable pkg: 'linux-headers..."

2017-01-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  cron.daily/apt reports MarkUpgrade() called on a non-upgrable pkg:
  'linux-headers..."

Status in python-apt package in Ubuntu:
  Triaged
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  Today I received the following messages from /etc/cron.daily/apt on my
  14.04 LTS server

  MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-3.13.0-73'
  MarkUpgrade() called on a non-upgrable pkg: 
'linux-image-extra-3.13.0-73-generic'
  MarkUpgrade() called on a non-upgrable pkg: 'linux-image-3.13.0-73-generic'
  MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-3.13.0-73-generic'

  
  First of all I suppose  the message should read  non-upgradable
  non-upgrable is possibly incorrect and should be corrected.

  Secondly I have no clue, what this message means so the error message
  should be revised to give more details.

  I think this as a minor bug but messages should always be correct,
  precise and possibly helpful.

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

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


[Touch-packages] [Bug 1527166] Re: cron.daily/apt reports MarkUpgrade() called on a non-upgrable pkg: 'linux-headers..."

2017-01-11 Thread Thomas A. F. Thorne
Seen in an email this morning from a 16.04 system:
/etc/cron.daily/apt:
MarkUpgrade() called on a non-upgrable pkg: 'linux-image-4.4.0-59-generic'
MarkUpgrade() called on a non-upgrable pkg: 'linux-tools-3.13.0-107-generic'
MarkUpgrade() called on a non-upgrable pkg: 'linux-tools-3.13.0-107'
MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-4.4.0-59-generic'
MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-4.4.0-59'
MarkUpgrade() called on a non-upgrable pkg: 'linux-cloud-tools-3.13.0-107'
MarkUpgrade() called on a non-upgrable pkg: 
'linux-cloud-tools-3.13.0-107-generic'

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

Title:
  cron.daily/apt reports MarkUpgrade() called on a non-upgrable pkg:
  'linux-headers..."

Status in python-apt package in Ubuntu:
  Triaged
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  Today I received the following messages from /etc/cron.daily/apt on my
  14.04 LTS server

  MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-3.13.0-73'
  MarkUpgrade() called on a non-upgrable pkg: 
'linux-image-extra-3.13.0-73-generic'
  MarkUpgrade() called on a non-upgrable pkg: 'linux-image-3.13.0-73-generic'
  MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-3.13.0-73-generic'

  
  First of all I suppose  the message should read  non-upgradable
  non-upgrable is possibly incorrect and should be corrected.

  Secondly I have no clue, what this message means so the error message
  should be revised to give more details.

  I think this as a minor bug but messages should always be correct,
  precise and possibly helpful.

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

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


[Touch-packages] [Bug 788167] Re: CUPS cannot print to Kerberos-authenticated SMB print queue

2017-01-11 Thread Keith Ward
** Bug watch added: Debian Bug tracker #711341
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711341

** Changed in: debian
   Importance: Undecided => Unknown

** Changed in: debian
   Status: New => Unknown

** Changed in: debian
 Remote watch: None => Debian Bug tracker #711341

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

Title:
  CUPS cannot print to Kerberos-authenticated SMB print queue

Status in cups package in Ubuntu:
  Confirmed
Status in Debian:
  Unknown

Bug description:
  Binary package hint: cups

  That was investigated on maverick (cups 1.4.4) and natty (cups 1.4.6).

  CUPS in Ubuntu cannot authenticate using Kerberos to an SMB print
  queue, such as one in an Active Directory.  This is because the smb
  backend is being invoked as user lp, and this user cannot access the
  Kerberos credential cache of the user who submitted the job.  When
  trying to print, the job is held for authentication, and a dialog
  prompting for username/password is being shown.  On Windows (and
  possibly other OS), the user would not be prompted if he has a ticket
  in the Kerberos realm (ie, "logged on to the domain") he is trying to
  print to.

  The CUPS smb backend on Ubuntu is the smbspool binary provided by
  Samba.  When run as a user, it will pick the Kerberos credential cache
  by itself and authenticate seamlessly.  Otherwise, it will read the
  KRB5CCNAME environment variable and try to use that when possible.

  There is two possible solutions to that:

  - Invoke the smb backend as root and pass it the KRB5CCNAME
  environment variable pointing to the user's Kerberos credential cache.
  CUPS execute the backend as user lp if it is world-executable, which
  is currently the case on Ubuntu.  User lp do not have the permission
  to read  the user's credential cache, hence why the smb backend would
  need to be executed as root (by removing the world-executable bit).
  Also, CUPS does not currently set KRB5CCNAME before invoking the smb
  backend (see http://www.cups.org/str.php?L3847).

  - Execute smbspool as the user submitting the job.

  
  I presume we would have the same problem with other backend that would do 
Kerberos authentication, although I do not know of a specific one.  I have only 
tested and investigated with the smb backend.

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

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


[Touch-packages] [Bug 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied

2017-01-11 Thread Jason Penney
This also affects isc-dhcp-server6 in the same way. It's service file
would also need to be updated similarly.

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

Title:
  isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid:
  Permission denied

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 14-10 to 15-04, and now see the following in
  syslog:

  Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 
audit(1430045408.725:8): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1  capname="dac_ove
  rride"
  Apr 26 10:50:08 server sh[8619]: Can't create PID file 
/run/dhcp-server/dhcpd.pid: Permission denied.

  Description:Ubuntu 15.04
  Release:15.04

  isc-dhcp-server:
Installed: 4.3.1-5ubuntu2

  --- 8x -

  # cat /etc/default/isc-dhcp-server

  # Defaults for isc-dhcp-server initscript
  # sourced by /etc/init.d/isc-dhcp-server
  # installed at /etc/default/isc-dhcp-server by the maintainer scripts

  #
  # This is a POSIX shell fragment
  #

  # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
  #DHCPD_CONF=/etc/dhcp/dhcpd.conf

  # Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
  #DHCPD_PID=/var/run/dhcpd.pid

  # Additional options to start dhcpd with.
  #   Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
  #OPTIONS=""

  # On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
  #   Separate multiple interfaces with spaces, e.g. "eth0 eth1".
  INTERFACES=""

  --- 8x -

  # ls -la /var/run
  lrwxrwxrwx 1 root root 4 Oct 24  2013 /var/run -> /run

  # ls -la /run/dhcp-server/
  total 0
  drwxr-xr-x  2 dhcpd dhcpd   40 Apr 26 10:59 .
  drwxr-xr-x 34 root  root  1060 Apr 26 11:33 ..

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

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


[Touch-packages] [Bug 1653373] Re: [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32mMultiView color format.

2017-01-11 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~alfonsosanchezbeato/ubuntu/+source/gst-plugins-bad1.0/+git/gst-plugins-bad1.0/+merge/314513

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

Title:
  [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32mMultiView
  color format.

Status in gst-plugins-bad1.0 package in Ubuntu:
  New

Bug description:
  From gstamc-constants.h:
/* NV12 but with stride and plane heights aligned to 32, Stores two images,
 * one after the other in top-bottom layout */
COLOR_QCOM_FormatYVU420SemiPlanar32mMultiView = 0x7fa30c05,

  Support is added by adding android-gst color format mapping, using the
  same code as COLOR_QCOM_FormatYUV420SemiPlanar to handle software
  conversion (as in gstamc.c) and adding special handling for multi-view
  nature of the format (as in gstamcvideodec.c).

  Adding support for this format fixes video playback on Fairphone 2.

  gst-plugins-bad1.0 version 1.8.2-1ubuntu0.1~overlay1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1653373/+subscriptions

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


[Touch-packages] [Bug 1654192] Re: resizing windows not working properly

2017-01-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  resizing windows not working properly

Status in Canonical System Image:
  New
Status in miral package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Run this qml app:

  http://paste.ubuntu.com/23738946/

  try resizing it, after releasing the mouse it will always resize
  itself back to be tiny...

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

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


[Touch-packages] [Bug 1653373] Re: [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32mMultiView color format.

2017-01-11 Thread Alfonso Sanchez-Beato
PR proposed with the patch:
https://code.launchpad.net/~alfonsosanchezbeato/ubuntu/+source/gst-
plugins-bad1.0/+git/gst-plugins-bad1.0/+merge/314513

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

Title:
  [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32mMultiView
  color format.

Status in gst-plugins-bad1.0 package in Ubuntu:
  New

Bug description:
  From gstamc-constants.h:
/* NV12 but with stride and plane heights aligned to 32, Stores two images,
 * one after the other in top-bottom layout */
COLOR_QCOM_FormatYVU420SemiPlanar32mMultiView = 0x7fa30c05,

  Support is added by adding android-gst color format mapping, using the
  same code as COLOR_QCOM_FormatYUV420SemiPlanar to handle software
  conversion (as in gstamc.c) and adding special handling for multi-view
  nature of the format (as in gstamcvideodec.c).

  Adding support for this format fixes video playback on Fairphone 2.

  gst-plugins-bad1.0 version 1.8.2-1ubuntu0.1~overlay1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1653373/+subscriptions

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


[Touch-packages] [Bug 1654192] Re: resizing windows not working properly

2017-01-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  resizing windows not working properly

Status in Canonical System Image:
  New
Status in miral package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Run this qml app:

  http://paste.ubuntu.com/23738946/

  try resizing it, after releasing the mouse it will always resize
  itself back to be tiny...

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

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


[Touch-packages] [Bug 1440360] Re: Incomplete long-left swipe resets dash

2017-01-11 Thread Michael Zanetti
** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Incomplete long-left swipe resets dash

Status in Ubuntu UX:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce the issue:
  1 - open e.g. Ubuntu Store scope (from the app scope) or Youtube scope (from 
the video scope)
  2 - (shortly) swipe from the left to invoke launcher

  Expected outcome:
  The launcher can be used to open a pinned app (while the current scope is 
still kept in the background) or dismissed to return to the current scope.

  Actual outcome:
  The current scope will immediately be closed and the first (main) scope 
(typically the app scope on devel-images and the Today scope on RTM) will be 
shown.
  If I understand the current design guidelines correctly this is the expected 
behaviour for a full left-to-right swipe, but not for a short swipe from the 
left to invoke the launcher.

  This behaviour can be observed on both the current devel-proposed and
  RTM images.

  -
  Desired UX

  - Don't trigger the "go to home" action yet when the long swipe is
  started but when user releases the finger and all the long swipe
  parameters are fulfilled (distance threshold and direction)

  - Also trigger "go to home" action when any other scope is focused.
  Currently action is triggered only when app is focused and when a
  child scope is focused but not when one of the dash scopes is focused.

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

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


[Touch-packages] [Bug 1633012] Re: indicator-network show no wi-fi ap's (amd64)

2017-01-11 Thread CSRedRat
When this will be fixed?

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

Title:
  indicator-network show no wi-fi ap's (amd64)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Enviroment:

  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  HW: intel+intel graphics+ intel wireless 3160 Laptop &&
  amd+nvidia+ralink PC

  1º I did an OEM installation on my laptop and a manual partitioning in PC
  2º On first boot check indicator-network status

  Current result: if you connected to Wi-Fi during installation, on
  first boot it does not connect to it. Indicator-network shows no wi-fi
  ap's but ethernet works fine when you plug the rj45

  Expected result: indicator-network should remember the Wi-Fi you
  connected during installation and automatically connect to it(not in
  OEM)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 13 11:37:27 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  IpRoute:
   default via 192.168.1.1 dev enp0s25  proto static  metric 100 
   169.254.0.0/16 dev enp0s25  scope link  metric 1000 
   192.168.1.0/24 dev enp0s25  proto kernel  scope link  src 192.168.1.55  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH
   Conexión cableada 1  4774df2a-6439-34e9-bbe9-9089c987c290  802-3-ethernet   
1476351437  jue 13 oct 2016 11:37:17 CEST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  yes enp0s25  
activated  /org/freedesktop/NetworkManager/ActiveConnection/2 
   Hedmonhater  4f551ad5-dbcb-4894-ac36-d031439936fe  802-11-wireless  
1476349793  jue 13 oct 2016 11:09:53 CEST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s25  ethernet  connected/org/freedesktop/NetworkManager/Devices/0  
Conexión cableada 1  4774df2a-6439-34e9-bbe9-9089c987c290  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   wlp2s0   wifi  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----   
  
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1575319] Re: [Ubuntu Touch] Manage Scopes doesn't scroll up/down when modifying position

2017-01-11 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu)
   Status: Triaged => In Progress

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

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

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

Title:
  [Ubuntu Touch] Manage Scopes doesn't scroll up/down when modifying
  position

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

Bug description:
  When managing the order of available scopes, if the list of scopes is
  longer than what can be shown on the screen, dragging scope to top or
  bottom of screen doesn't automatically begin to scroll screen.  Scope
  would have to be dropped near then top, then scroll screen, then move
  scope into final position.

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

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


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

2017-01-11 Thread Luis Henriques
** Changed in: linux (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 bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1616107

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

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

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

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

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

[Touch-packages] [Bug 1655621] [NEW] It tells programs crashed, but they were normally closed

2017-01-11 Thread florin
Public bug reported:

Since I installed Ubuntu 16.10 I get crash reports (Sorry, Ubuntu 16.10
has experienced an internal error message) when I close some programs.
It happens with quite a lot, I can remember qBittorrent. There is no
crash, I just closed them, there should have been no error report.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apport-gtk 2.20.3-0ubuntu8.2
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jan 11 13:44:25 2017
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apport (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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1655621

Title:
  It tells programs crashed, but they were normally closed

Status in apport package in Ubuntu:
  New

Bug description:
  Since I installed Ubuntu 16.10 I get crash reports (Sorry, Ubuntu
  16.10 has experienced an internal error message) when I close some
  programs. It happens with quite a lot, I can remember qBittorrent.
  There is no crash, I just closed them, there should have been no error
  report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apport-gtk 2.20.3-0ubuntu8.2
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:44:25 2017
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-01-11 Thread Harald
I submitted a patch. See https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=819361

Patch inline:
-
--- sshconnect2.c.orig  2017-01-04 19:47:10.0 +0100
+++ sshconnect2.c   2017-01-05 04:13:08.977425272 +0100
@@ -222,7 +222,6 @@
orig = myproposal[PROPOSAL_SERVER_HOST_KEY_ALGS];
xasprintf(&myproposal[PROPOSAL_SERVER_HOST_KEY_ALGS],
"%s,null", orig);
-   free(gss);
}
}
 #endif
@@ -273,6 +272,16 @@
/* remove ext-info from the KEX proposals for rekeying */
myproposal[PROPOSAL_KEX_ALGS] =
compat_kex_proposal(options.kex_algorithms);
+#ifdef GSSAPI
+   /* repair myproposal after it was crumpled by the */
+   /* ext-info removal above */
+   if (gss) {
+   orig = myproposal[PROPOSAL_KEX_ALGS];
+   xasprintf(&myproposal[PROPOSAL_KEX_ALGS],
+ "%s,%s", gss, orig);
+   free(gss);
+   }
+#endif
if ((r = kex_prop2buf(kex->my, myproposal)) != 0)
fatal("kex_prop2buf: %s", ssh_err(r));

-
This patch should be merged with gssapi.patch (for obvious reasons).

Harald.

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

Title:
  ssh GSSAPI rekey failure

Status in openssh package in Ubuntu:
  Triaged

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

  Steps to reproduce:

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

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

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

  It looks like the list of KEX algor

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

2017-01-11 Thread Harald
> It does not seem to honor "ReKeyLimit 0G 1H" in my case.

Have you tried "RekeyLimit 0" on _both_ ends?

Harald.

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

Title:
  ssh GSSAPI rekey failure

Status in openssh package in Ubuntu:
  Triaged

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

  Steps to reproduce:

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

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

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

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

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

  ssh_config is as follows:

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

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

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


[Touch-packages] [Bug 1655631] [NEW] Internal Microphone works on 16.04, but not on ZZ

2017-01-11 Thread Marco Parillo
Public bug reported:

My microphone (built in, or using the plug-in jack) works just fine in
16.04 with the Kubuntu backports PPA, but not in ZZ. This is in two
partitions on the same laptop. I think System Settings multimedia looks
the same in both 16.04 and ZZ.

Since it is the same piece of HW, and with the backports, I assume the
app layer is almost identical between 16.04 and ZZ, I wonder if it is
lower down in the stack.

On 16.04, uname -a: Linux mparillo-HP-EliteBook-8440p 4.4.0-57-generic
#78-Ubuntu SMP

On ZZ, uname -a: Linux mparillo-HP-EliteBook-8440p 4.9.0-11-generic
#12-Ubuntu SMP

lspci: 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series
Chipset High Definition Audio (rev 05)

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


** Tags: kubuntu zesty

** Tags added: zesty

** Tags added: kubuntu

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

Title:
  Internal Microphone works on 16.04, but not on ZZ

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My microphone (built in, or using the plug-in jack) works just fine in
  16.04 with the Kubuntu backports PPA, but not in ZZ. This is in two
  partitions on the same laptop. I think System Settings multimedia
  looks the same in both 16.04 and ZZ.

  Since it is the same piece of HW, and with the backports, I assume the
  app layer is almost identical between 16.04 and ZZ, I wonder if it is
  lower down in the stack.

  On 16.04, uname -a: Linux mparillo-HP-EliteBook-8440p 4.4.0-57-generic
  #78-Ubuntu SMP

  On ZZ, uname -a: Linux mparillo-HP-EliteBook-8440p 4.9.0-11-generic
  #12-Ubuntu SMP

  lspci: 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series
  Chipset High Definition Audio (rev 05)

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

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


[Touch-packages] [Bug 1655345] Re: OSK doesn't appear on lock screen

2017-01-11 Thread Víctor R . Ruiz
*** This bug is a duplicate of bug 1654568 ***
https://bugs.launchpad.net/bugs/1654568

I'm not sure this is a duplication of that bug, because nothing happens
if the OSK area is pressed.

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

Title:
  OSK doesn't appear on lock screen

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

Bug description:
  Test case.
  - Reboot device.
  - Press on password text box.

  Expected result.
  - OSK appears.

  Actual result.
  - OSK doesn't appear, although the password box is located up, as if the OSK 
is opened.

  Opening and closing the indicators, and tapping again in the password
  text box makes it appear.

  
  current build number: 119
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

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

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


[Touch-packages] [Bug 1655431] Re: apt-helper / update-notifier / ttf-mscorefonts-installer download failure (regression)

2017-01-11 Thread Julian Andres Klode
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923

That is a problem on sourceforge:

E: Failed to fetch
https://netix.dl.sourceforge.net/project/corefonts/the%20fonts/final/andale32.exe
Redirection from https to
'http://downloads.sourceforge.net/mirrorproblem?failedmirror=netix.dl.sourceforge.net'
is forbidden

We send it a valid https request, indicating that we already have 198384
bytes (the complete file)

> GET /project/corefonts/the%20fonts/final/andale32.exe HTTP/1.1
Host: netix.dl.sourceforge.net
User-Agent: Debian APT-CURL/1.0 (1.4~beta2)
Accept: */*
Cache-Control: max-age=0
Range: bytes=198384-
If-Range: Thu, 15 Aug 2002 14:33:49 GMT


It answers it has found the file at another location, but redirects to an 
unencrypted mirror problem URL:

< HTTP/1.1 302 Found
< Date: Wed, 11 Jan 2017 12:30:56 GMT
< Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips
< Location: 
http://downloads.sourceforge.net/mirrorproblem?failedmirror=netix.dl.sourceforge.net
< Connection: close
< Transfer-Encoding: chunked
< Content-Type: text/html; charset=iso-8859-1
<

There was another issue with "invalid content-range" - I'm working on
that. But that one can easily be resolved on the redirector as well. It
makes no sense for the server to respond with "Content-Range: */" (basically meaning: Oh, I can't satisfy that range) on a
redirect.

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

Title:
  apt-helper / update-notifier / ttf-mscorefonts-installer download
  failure (regression)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  * OS release: Ubuntu 16.04.1 LTS
  * Package version: 3.168.3

  For the past few days (maybe even weeks for other users), update-
  notifier has been very repeatedly failing to handle the downloads for
  ttf-mscorefonts-installer. Previously it was working fine on the same
  system.

  This seems to affect a lot of desktop users, but the issue is usually
  misdiagnosed on forums because it is attributed to ttf-mscorefonts-
  installer and not to update-notifier-common.

  The issue is made particularly irritating because the update-notifier
  cron job tries and fails and notifies users daily of this failure.

  The issue can be reproduced by having ttf-mscorefonts-installer
  installed, and running:

  sudo dpkg-reconfigure update-notifier-common

  The error messages seem to be random but actually appear to be
  consistent for a given download source:

  * freefr.dl.sourceforge.net: 404  Not Found
  * kent.dl.sourceforge.net: Protocol "http" not supported or disabled in 
libcurl
  * netassist.dl.sourceforge.net: The HTTP server sent an invalid Content-Range 
header Bad header data [IP: 62.205.134.42 80]
  * netcologne.dl.sourceforge.net: The HTTP server sent an invalid 
Content-Range header
  * netix.dl.sourceforge.net: 404  Not Found
  * vorboss.dl.sourceforge.net: 404  Not Found

  In all above cases, the reported failing URL can be downloaded just
  fine using wget.

  Some other mirrors appear to work (unfortunately, mirror names are
  only printed in case of errors). However, since ttf-mscorefonts-
  installer triggers 11 downloads in a row, chances of randomly getting
  11 working mirrors are very low.

  I am tagging this as regression-update because the issue started
  happening when upgrading from 3.168.2 to 3.168.3 last Friday. It is of
  course entirely possible the root cause is in another package, but
  this would also likely be a regression-update, since I am very careful
  about system-wide changes on this machine.

  The previous update from 3.168.1 to 3.168.2 on November 4th went just
  fine. ttf-mscorefonts-installer has been installed (just fine) on
  September 26th, and not upgraded since then.

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

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


[Touch-packages] [Bug 1655644] [NEW] unity8 crash after create a new account

2017-01-11 Thread Renato Araujo Oliveira Filho
Public bug reported:

Unity8 crashes after create a new account

How to reproduce:

1- start system settings
2- Go to online accounts
3- Click to create a new account
4- Choose any account on the list (Eg. google)
5- Follow the steps to create the new account

Expected

Account created and back to system settings

Current

Unity8 crash.

** Affects: unity8 (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/1655644

Title:
  unity8 crash after create a new account

Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 crashes after create a new account

  How to reproduce:

  1- start system settings
  2- Go to online accounts
  3- Click to create a new account
  4- Choose any account on the list (Eg. google)
  5- Follow the steps to create the new account

  Expected

  Account created and back to system settings

  Current

  Unity8 crash.

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

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


[Touch-packages] [Bug 1655644] Re: unity8 crash after create a new account

2017-01-11 Thread Renato Araujo Oliveira Filho
Back trace:

#0  0x7f2373dca4d0 in Protocol::features() const () from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Telephony/libtelephonyservice-qml.so
#1  0x7f2373db3410 in AccountList::filterAccounts() () from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Telephony/libtelephonyservice-qml.so
#2  0x7f23b1c51c34 in QMetaObject::activate(QObject*, int, int, void**) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f2373da2d0a in 
TelepathyHelper::onNewAccount(Tp::SharedPtr const&) () from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Telephony/libtelephonyservice-qml.so
#4  0x7f2373dacbc1 in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Telephony/libtelephonyservice-qml.so
#5  0x7f23b1c51b81 in QMetaObject::activate(QObject*, int, int, void**) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f23737517d2 in 
Tp::AccountManager::newAccount(Tp::SharedPtr const&) () from 
/usr/lib/x86_64-linux-gnu/libtelepathy-qt5.so.0
#7  0x7f2373754bb7 in ?? () from 
/usr/lib/x86_64-linux-gnu/libtelepathy-qt5.so.0
#8  0x7f23b1c51b81 in QMetaObject::activate(QObject*, int, int, void**) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f237393ea6f in Tp::PendingOperation::finished(Tp::PendingOperation*) 
() from /usr/lib/x86_64-linux-gnu/libtelepathy-qt5.so.0
#10 0x7f237393fed0 in ?? () from 
/usr/lib/x86_64-linux-gnu/libtelepathy-qt5.so.0
#11 0x7f23b1c52729 in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f23b1c2515a in QCoreApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f23b1c252b8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f23b1c2717a in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f23b1c79f63 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f23ae8351a7 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x7f23ae835400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x7f23ae8354ac in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7f23b1c7a36f in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f23b1c2300a in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7f23b1c2b6cc in QCoreApplication::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x004079fa in ?? ()
#23 0x7f23b1062830 in __libc_start_main (main=0x4077e0, argc=2, 
argv=0x7fff0b10e9a8, init=, fini=, 
rtld_fini=, stack_end=0x7fff0b10e998)
at ../csu/libc-start.c:291
#24 0x00407bd9 in _start ()

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

Title:
  unity8 crash after create a new account

Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 crashes after create a new account

  How to reproduce:

  1- start system settings
  2- Go to online accounts
  3- Click to create a new account
  4- Choose any account on the list (Eg. google)
  5- Follow the steps to create the new account

  Expected

  Account created and back to system settings

  Current

  Unity8 crash.

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

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


[Touch-packages] [Bug 1655644] Re: unity8 crash after create a new account

2017-01-11 Thread Renato Araujo Oliveira Filho
this was caused by a developer branch. And was fixed before the release.

** 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/1655644

Title:
  unity8 crash after create a new account

Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Unity8 crashes after create a new account

  How to reproduce:

  1- start system settings
  2- Go to online accounts
  3- Click to create a new account
  4- Choose any account on the list (Eg. google)
  5- Follow the steps to create the new account

  Expected

  Account created and back to system settings

  Current

  Unity8 crash.

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

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


[Touch-packages] [Bug 788167] Re: CUPS cannot print to Kerberos-authenticated SMB print queue

2017-01-11 Thread Bug Watch Updater
** Changed in: debian
   Status: Unknown => New

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

Title:
  CUPS cannot print to Kerberos-authenticated SMB print queue

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

Bug description:
  Binary package hint: cups

  That was investigated on maverick (cups 1.4.4) and natty (cups 1.4.6).

  CUPS in Ubuntu cannot authenticate using Kerberos to an SMB print
  queue, such as one in an Active Directory.  This is because the smb
  backend is being invoked as user lp, and this user cannot access the
  Kerberos credential cache of the user who submitted the job.  When
  trying to print, the job is held for authentication, and a dialog
  prompting for username/password is being shown.  On Windows (and
  possibly other OS), the user would not be prompted if he has a ticket
  in the Kerberos realm (ie, "logged on to the domain") he is trying to
  print to.

  The CUPS smb backend on Ubuntu is the smbspool binary provided by
  Samba.  When run as a user, it will pick the Kerberos credential cache
  by itself and authenticate seamlessly.  Otherwise, it will read the
  KRB5CCNAME environment variable and try to use that when possible.

  There is two possible solutions to that:

  - Invoke the smb backend as root and pass it the KRB5CCNAME
  environment variable pointing to the user's Kerberos credential cache.
  CUPS execute the backend as user lp if it is world-executable, which
  is currently the case on Ubuntu.  User lp do not have the permission
  to read  the user's credential cache, hence why the smb backend would
  need to be executed as root (by removing the world-executable bit).
  Also, CUPS does not currently set KRB5CCNAME before invoking the smb
  backend (see http://www.cups.org/str.php?L3847).

  - Execute smbspool as the user submitting the job.

  
  I presume we would have the same problem with other backend that would do 
Kerberos authentication, although I do not know of a specific one.  I have only 
tested and investigated with the smb backend.

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

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


[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar

2017-01-11 Thread Chris Coulson
** Changed in: oxide
   Status: In Progress => Fix Released

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

Title:
  Webview appears to think it's in focus when typing in the addressbar

Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

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

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


[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-11 Thread Rik Mills
The issue with the buildd hang is now reported against launchpad-builds
as:

Bug #1655298 - Indefinite build hangs during python tests of gpgme1.0
v1.8

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

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

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


[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

2017-01-11 Thread Laurent Bonnaud
I tested with a 4.9.2 mainline kernel.
I will try to test with an Ubuntu kernel when I have a chance to reboot my 
system...

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1465766] Re: low sound volume

2017-01-11 Thread Lasha Abulashvili
Same problem here, lenovo X1C3.

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

Title:
  low sound volume

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  this is a thinkpad x1 carbon 3rd gen running xubuntu 15.04

  sound volume is very low compared to windows (dual boot), even with
  alsa and pulseaudio controls set to 100% (or greater).

  this applies to all apps.

  i can get really loud sound with:
  pactl set-sink-volume 1 30
  but then it is very distorted.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  smwilson   1577 F pulseaudio
   /dev/snd/controlC0:  smwilson   1577 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jun 16 06:44:39 2015
  InstallationDate: Installed on 2015-06-04 (11 days ago)
  InstallationMedia: Xubuntu Core 15.04 - amd64 - 20150425
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Volume slider, or mixer problems
  Title: [20BSCTO1WW, Realtek ALC3232, Speaker, Internal] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET25W (1.03 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET25W(1.03):bd12/01/2014:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1465766] Re: low sound volume

2017-01-11 Thread Lasha Abulashvili
With latest kernel too, 4.8.X

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

Title:
  low sound volume

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  this is a thinkpad x1 carbon 3rd gen running xubuntu 15.04

  sound volume is very low compared to windows (dual boot), even with
  alsa and pulseaudio controls set to 100% (or greater).

  this applies to all apps.

  i can get really loud sound with:
  pactl set-sink-volume 1 30
  but then it is very distorted.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  smwilson   1577 F pulseaudio
   /dev/snd/controlC0:  smwilson   1577 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jun 16 06:44:39 2015
  InstallationDate: Installed on 2015-06-04 (11 days ago)
  InstallationMedia: Xubuntu Core 15.04 - amd64 - 20150425
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Volume slider, or mixer problems
  Title: [20BSCTO1WW, Realtek ALC3232, Speaker, Internal] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET25W (1.03 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET25W(1.03):bd12/01/2014:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1574776] Re: Only one subtitle displayed at any given time

2017-01-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Only one subtitle displayed at any given time

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  Many of the videos I watch are subtitled foreign works; they generally
  have multiple subtitles onscreen at once, with one translating the
  speech and others translating onscreen text. Gstreamer invariably only
  displays one and more often than not it's the less helpful one,
  leaving me unable to tell what's  been said because "episode 2" is
  deemed more important information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.0-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Apr 25 18:25:16 2016
  InstallationDate: Installed on 2015-06-28 (302 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to xenial on 2016-04-19 (6 days ago)

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

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


[Touch-packages] [Bug 1655687] [NEW] webbrowser-app graphics garbled in unity8 session

2017-01-11 Thread Alex T Newman
Public bug reported:

Web pages appear garbled and graphically corrupt when displayed on the
webbrowser-app under unity8 on a Kabylake Dell Inspiron 5378 using the
default unity8 session currently included with Ubuntu 16.10:


This behavior occurs 100% of the time on this hardware under unity8 and
does not occur when webbrowser-app is started under unity7.

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

** Attachment added: "screenshot of graphical corruption"
   
https://bugs.launchpad.net/bugs/1655687/+attachment/4802907/+files/screenshot20170111_095635696.png

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

Title:
  webbrowser-app graphics garbled in unity8 session

Status in unity8 package in Ubuntu:
  New

Bug description:
  Web pages appear garbled and graphically corrupt when displayed on the
  webbrowser-app under unity8 on a Kabylake Dell Inspiron 5378 using the
  default unity8 session currently included with Ubuntu 16.10:


  This behavior occurs 100% of the time on this hardware under unity8
  and does not occur when webbrowser-app is started under unity7.

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

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


[Touch-packages] [Bug 1655687] Re: webbrowser-app graphics garbled in unity8 session

2017-01-11 Thread Alex T Newman
Attaching output of apport-bug for unity8 and webbrowser-app as well as
application-legacy-webbrowser-app-.log from ~/.cache/upstart. Let me
know if there's any other useful information I can gather.

** Attachment added: "apport output and log files"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1655687/+attachment/4802908/+files/webbrowser-app-unity8-apport.tar.gz

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

Title:
  webbrowser-app graphics garbled in unity8 session

Status in unity8 package in Ubuntu:
  New

Bug description:
  Web pages appear garbled and graphically corrupt when displayed on the
  webbrowser-app under unity8 on a Kabylake Dell Inspiron 5378 using the
  default unity8 session currently included with Ubuntu 16.10:


  This behavior occurs 100% of the time on this hardware under unity8
  and does not occur when webbrowser-app is started under unity7.

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

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


[Touch-packages] [Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-11 Thread Gerry Boland
I'm failing to reproduce this unfortunately. I'm also failing to create
a libertine container. It was failing due to bug 1653973, so I installed
silo 2341, but now it fails with:

Failed to download http://images.linuxcontainers.org//meta/1.0/index-user
LxcContainer.py:254: ERROR: create_libertine_container(): Failed to create 
container
libertine-container-manager:94: ERROR: create():Failed to create container

This is odd, as networking is fine, and I can wget that URL
successfully.


I've left my AMD laptop running with unity8 for hours yesterday, and no crash.

Can you paste more of that unity8.log please? From the output, it
indicates that the physical display state changed somehow, or at least
Mir thinks it did. Disabling screen blanking was a good idea, but are
you sure it worked? How did you try it?

Also, what GPU have you got?

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

Title:
  Unity8 crashes with SIGSEGV in Screen::makeCurrent
  (./src/platforms/mirserver/screen.cpp:406)

Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+15.04.20151130.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6cee045a96ab5c9a03847aeb290f4860eea1034d
  contains more details.

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

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


[Touch-packages] [Bug 1457540] Re: cannot convert lv to type thin-pool on trusty

2017-01-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  cannot convert lv to type thin-pool on trusty

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  2. $ apt-cache policy lvm2
  lvm2:
Installed: 2.02.98-6ubuntu2
Candidate: 2.02.98-6ubuntu2
Version table:
   *** 2.02.98-6ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3.  lvconvert to type thin-pool warns about destrying data on the target LV's 
and thin type, this is the output on vivid:
  ubuntu@lvm02:~$ sudo lvconvert --type thin-pool --poolmetadata vg/pool0meta 
vg/pool0
WARNING: Converting logical volume vg/pool0 and vg/pool0meta to pool's data 
and metadata volumes.
THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.)
  Do you really want to convert vg/pool0 and vg/pool0meta? [y/n]: y
Logical volume "lvol0" created
Converted vg/pool0 to thin pool.
  ubuntu@lvm02:~$ sudo lvs -a
LV  VG   Attr   LSize  Pool Origin Data%  Meta%  Move Log 
Cpy%Sync Convert
[lvol0_pmspare] vg   ewi---  1.00g  
  
pool0   vg   twi-a-tz-- 10.00g 0.00   0.01  
  
[pool0_tdata]   vg   Twi-ao 10.00g  
  
[pool0_tmeta]   vg   ewi-ao  1.00g  

  4. lvconvert returns 0, but does not convert the lv to type thin-pool

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lvm2 2.02.98-6ubuntu2
  ProcVersionSignature: User Name 3.13.0-52.85-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-52-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  Date: Thu May 21 15:35:20 2015
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-01-11 Thread Timo Aaltonen
fixed in zesty which has 13.0.3

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

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

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

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

Title:
  mesa gpu lockup

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

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

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

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

  Symptoms occur when playing Team Fortress 2.

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

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

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


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

2017-01-11 Thread Timo Aaltonen
there is another sru pending review for xenial and yakkety, but this
could be added to them

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

Title:
  mesa gpu lockup

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

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

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

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

  Symptoms occur when playing Team Fortress 2.

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

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

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


[Touch-packages] [Bug 1655687] Re: webbrowser-app graphics garbled in unity8 session

2017-01-11 Thread Gerry Boland
I'm adding Oxide to the bug, as the browser chrome is being rendered ok.
I also see these strings in the browser log:

[0111/095625:ERROR:layer_tree_host_impl.cc(2189)] Forcing zero-copy tile 
initialization as worker context is missing
[0111/095625:ERROR:oxide_compositor_gpu_shims.cc(258)] Error creating EGLImage: 
EGL_BAD_PARAMETER
Cannot find EGLConfig, returning null config

Which make sense as those kinds of visual artefacts are typically GPU
tiling problems.

** Also affects: oxide-qt (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/1655687

Title:
  webbrowser-app graphics garbled in unity8 session

Status in oxide-qt package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Web pages appear garbled and graphically corrupt when displayed on the
  webbrowser-app under unity8 on a Kabylake Dell Inspiron 5378 using the
  default unity8 session currently included with Ubuntu 16.10:


  This behavior occurs 100% of the time on this hardware under unity8
  and does not occur when webbrowser-app is started under unity7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1655687/+subscriptions

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


[Touch-packages] [Bug 1655699] [NEW] no sound-card detected after linux-image upgrade

2017-01-11 Thread Bernhard Maechtel
Public bug reported:

aplay: device_list:268: no soundcards found...

00:1f.3 Audio device: Intel Corporation Device 9d70 (rev 21)
Subsystem: Dell Device 06f2
Flags: fast devsel, IRQ 255
Memory at d122 (64-bit, non-prefetchable) [disabled] [size=16K]
Memory at d120 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: 

00:1f.4 SMBus: Intel Corporation Device 9d23 (rev 21)

:~$ sudo apt-get install linux-restricted-modules-`uname -r` linux-generic
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Unable to locate package linux-restricted-modules-4.4.0-59-generic
E: Couldn't find any package by regex 'linux-restricted-modules-4.4.0-59-generic

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

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

Title:
  no sound-card detected after linux-image upgrade

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  aplay: device_list:268: no soundcards found...

  00:1f.3 Audio device: Intel Corporation Device 9d70 (rev 21)
Subsystem: Dell Device 06f2
Flags: fast devsel, IRQ 255
Memory at d122 (64-bit, non-prefetchable) [disabled] [size=16K]
Memory at d120 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: 

  00:1f.4 SMBus: Intel Corporation Device 9d23 (rev 21)

  :~$ sudo apt-get install linux-restricted-modules-`uname -r` linux-generic
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package linux-restricted-modules-4.4.0-59-generic
  E: Couldn't find any package by regex 
'linux-restricted-modules-4.4.0-59-generic

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

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

2017-01-11 Thread ThorstenK
** Changed in: cups (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 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:
  Fix Released

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

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

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


[Touch-packages] [Bug 1654974] Re: webbrowser-app locks up my session (zesty)

2017-01-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  webbrowser-app locks up my session (zesty)

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  My setup:
   * up-to-date zesty
   * unity8-greeter as greeter
   * unity7 as desktop

  How to reproduce:
   * open xterm
   * start webbrowser-app from xterm

  Everything locks up and have to hard reboot the computer.

  I tried catching the output to a file with &> but got nothing, so i
  took a picture.

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

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


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

2017-01-11 Thread Timo Aaltonen
xenial will probably get 12.0.5 that fixes this

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

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

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

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1173915] Re: initctl continuously takes 100% of CPU

2017-01-11 Thread Dattée David
bump 
Having the same problem too with /sbin/initctl emit indicator-services-start

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

Title:
  initctl continuously takes 100% of CPU

Status in upstart :
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Many programs are fairly slow to start on my computer, despite it
  being relatively new (core i5). Suspecting a heavy CPU usage, I
  started gnome-system-monitor: all processes were displayed at 0% CPU,
  but the overall load was 1.33; 1.33; 1.34.

  Using the "top" command, however, revealed the real CPU use, with the
  "initctl" process taking 100%CPU, even 1 hour after startup.

  I upgraded to roaring ringtail before checking this but the symptoms
  were the same with quantal quetzal, so there is a fair chance the
  causes were identical.

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: upstart 1.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CheckboxSubmission: 2deefc5fd2f1f0ae2fdd4bd781248a2a
  CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
  Date: Sun Apr 28 13:04:05 2013
  ExecutablePath: /sbin/initctl
  InstallationDate: Installed on 2012-12-15 (133 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=fa624f8f-d9d0-4b09-af8b-88b106aaaf5b ro quiet splash vt.handoff=7
  SourcePackage: upstart
  UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
  UpstartBugCategory: System

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

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


[Touch-packages] [Bug 1556071] Re: cl device not found

2017-01-11 Thread Timo Aaltonen
do you have mesa-opencl-icd installed?

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

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

Title:
  cl device not found

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  I get this on python:

  Traceback (most recent call last):
File "./prueba.py", line 7, in 
  ctx = cl.create_some_context()
File "/usr/lib/python2.7/dist-packages/pyopencl/__init__.py", line 804, in 
create_some_context
  devices = platform.get_devices()
  pyopencl.RuntimeError: clGetDeviceIDs failed: device not found

  
  but my device is compatible with openCL 1.2. I don't know if mesa has not 
support for openCL yet (I don't know how to check it)

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

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


[Touch-packages] [Bug 1425525] Re: Mir EGL platform exposes extensions that it doesn't actually support

2017-01-11 Thread Timo Aaltonen
this is fixed long ago

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

Title:
  Mir EGL platform exposes extensions that it doesn't actually support

Status in Mir:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  The mir eglDisplay exposes EGL extensions that it doesn't actually
  implement.

  Including:
   - EGL_EXT_buffer_age
   - EGL_EXT_swap_buffers_with_damage

  Mir claims to support these, but when using them noting is actually painted.
  According to Chris, these implementations aren't there yet. In mesa, at least.

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

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


[Touch-packages] [Bug 1654722] Re: Ubuntu Touch: No sound on speakers but OK on headset

2017-01-11 Thread Simone allegri
Hi, bad news

I did a fresh installation from stable channel with --bootstrap command and now 
the speakers works fine... but only without the cover!!!
Later i take a video...

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

Title:
  Ubuntu Touch: No sound on speakers but OK on headset

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Since a couple of days ago I have lost all sound on the speakers of the phone 
(no application plays any sound, no ringtones, notifications), but sounds can 
be heard normally with a headset. Sound
  configuration looks OK, and restarting does not help.

  I tried to remove .config/pulse completely and restart, but no progress. I 
attach the file 
  ubuntu-phablet-stream-volumes.tdb
  which was there before removing the folder and restarting.

  BQ E5, OTA 14.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:6.0-0ubuntu9.25
  Uname: Linux 3.4.67 armv7l
  AlsaInfo: This script requires lspci. Please install it, and re-run this 
script.
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sat Jan  7 09:30:00 2017
  InstallationDate: Installed on 2016-11-18 (49 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1647467] Update Released

2017-01-11 Thread Brian Murray
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/1647467

Title:
  InRelease file splitter treats getline() errors as EOF

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Yakkety:
  Fix Released
Status in apt source package in Zesty:
  Fix Released

Bug description:
  We have just been made aware of a security bug upstream that affects
  the validation of signatures on InRelease file. This bug is to track
  progress for it.

  It allows for attacking a repository via MITM attacks, circumventing
  the signature of the InRelease file.

  It works by making a call to getline() fail with ENOMEM, which is not
  documented as an error for that but follows from the fact that
  getline() can allocate memory. In such a case, apt would treat the
  first part of the file as a valid release file.

  
  = Original bug report =
  From: Jann Horn 
  To: secur...@debian.org
  Cc: 
  Date: Mon, 5 Dec 2016 18:33:09 +0100
  Subject: apt: repository signing bypass via memory allocation failure

  == Vulnerability ==
  When apt-get updates a repository that uses an InRelease file (clearsigned
  Release files), this file is processed as follows:
  First, the InRelease file is downloaded to disk.
  In a subprocess running the gpgv helper, "apt-key verify" (with some more
  arguments) is executed through the following callchain:

  gpgv.cc:main -> pkgAcqMethod::Run -> GPGVMethod::URIAcquire
    -> GPGVMethod::VerifyGetSigners -> ExecGPGV

  ExecGPGV() splits the clearsigned file into payload and signature using
  SplitClearSignedFile(), calls apt-key on these two files to perform the
  cryptographic signature verification, then discards the split files and only
  retains the clearsigned original. SplitClearSignedFile() ignores leading and
  trailing garbage.

  Afterwards, in the parent process, the InRelease file has to be loaded again
  so that its payload can be processed. At this point, the code
  isn't aware anymore whether the Release file was clearsigned or
  split-signed, so the file is opened using OpenMaybeClearSignedFile(), which
  first attempts to parse the file as a clearsigned (InRelease) file and extract
  the payload, then falls back to treating the file as the file as a 
split-signed
  (Release) file if the file format couldn't be recognized.

  The weakness here is: If an attacker can create an InRelease file that
  is parsed as a proper split-signed file during signature validation, but then
  isn't recognized by OpenMaybeClearSignedFile(), the "leading garbage" that was
  ignored by the signature validation is interpreted as repository metadata,
  bypassing the signing scheme.

  It first looks as if it would be impossible to create a file that is 
recognized
  as split-signed by ExecGPGV(), but isn't recognized by
  OpenMaybeClearSignedFile(), because both use the same function,
  SplitClearSignedFile(), for parsing the file. However, multiple executions of
  SplitClearSignedFile() on the same data can actually have different non-error
  results because of a bug.
  SplitClearSignedFile() uses getline() to parse the input file. A return code
  of -1, which signals that either EOF or an error occured, is always treated
  as EOF. The Linux manpage only lists EINVAL (caused by bad arguments) as
  possible error code, but because the function allocates (nearly) unbounded
  amounts of memory, it can actually also fail with ENOMEM if it runs out of
  memory.
  Therefore, if an attacker can cause the address space in the main apt-get
  process to be sufficiently constrained to prevent allocation of a large line
  buffer while the address space of the gpgv helper process is less constrained
  and permits the allocation of a buffer with the same size, the attacker can 
use
  this to fake an end-of-file condition in SplitClearSignedFile() that causes 
the
  file to be parsed as a normal Release file.

  A very crude way to cause such a constraint on a 32-bit machine is based on
  abusing ASLR. Because ASLR randomizes the address space after each execve(),
  thereby altering how much contiguous virtual memory is available, an 
allocation
  that attempts to use the average available virtual memory should ideally 
succeed
  50% of the time, resulting in an upper limit of 25% for the success rate of 
the
  whole atta

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

2017-01-11 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.2.18

---
apt (1.2.18) xenial; urgency=high

  * SECURITY UPDATE: gpgv: Check for errors when splitting files (CVE-2016-1252)
Thanks to Jann Horn, Google Project Zero for reporting the issue
(LP: #1647467)
  * gpgv: Flush the files before checking for errors

apt (1.2.17) xenial; urgency=medium

  [ David Kalnischkies ]
  * apt-key: warn instead of fail on unreadable keyrings (LP: #1642386)
  * show apt-key warnings in apt update (Closes: 834973)

  [ Julian Andres Klode ]
  * test-releasefile-verification: installaptold: Clean up before run

apt (1.2.16) xenial; urgency=medium

  [ David Kalnischkies ]
  * avoid changing the global LC_TIME for Release writing
  * use de-localed std::put_time instead rolling our own
  * accept only the expected UTC timezones in date parsing (Closes: 819697)
  * avoid std::get_time usage to sidestep libstdc++6 bug (LP: #1593583)
  * imbue datetime parsing with C.UTF-8 locale (Closes: 828011)
  * prevent C++ locale number formatting in text APIs (try 2) (Closes: 832044)
  * prevent C++ locale number formatting in text APIs (try 3) (LP: #1611010)
(LP: #1592817)
  * imbue .diff/Index parsing with C.UTF-8 as well

  [ Julian Andres Klode ]
  * Use C locale instead of C.UTF-8 for protocol strings
  * Add shippable.yml for CI on Shippable
  * Revert "if the FileFd failed already following calls should fail, too"
(LP: #1641905)

 -- Julian Andres Klode   Thu, 08 Dec 2016 15:28:08
+0100

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-1252

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

Title:
  At least one invalid signature was encountered.

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

Bug description:
  [Summary]

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

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

  [Workaround]

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

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

  [Impact]
  Breaks update on systems with unreadable GPG keys

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

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

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

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

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

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

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

2017-01-11 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.2.18

---
apt (1.2.18) xenial; urgency=high

  * SECURITY UPDATE: gpgv: Check for errors when splitting files (CVE-2016-1252)
Thanks to Jann Horn, Google Project Zero for reporting the issue
(LP: #1647467)
  * gpgv: Flush the files before checking for errors

apt (1.2.17) xenial; urgency=medium

  [ David Kalnischkies ]
  * apt-key: warn instead of fail on unreadable keyrings (LP: #1642386)
  * show apt-key warnings in apt update (Closes: 834973)

  [ Julian Andres Klode ]
  * test-releasefile-verification: installaptold: Clean up before run

apt (1.2.16) xenial; urgency=medium

  [ David Kalnischkies ]
  * avoid changing the global LC_TIME for Release writing
  * use de-localed std::put_time instead rolling our own
  * accept only the expected UTC timezones in date parsing (Closes: 819697)
  * avoid std::get_time usage to sidestep libstdc++6 bug (LP: #1593583)
  * imbue datetime parsing with C.UTF-8 locale (Closes: 828011)
  * prevent C++ locale number formatting in text APIs (try 2) (Closes: 832044)
  * prevent C++ locale number formatting in text APIs (try 3) (LP: #1611010)
(LP: #1592817)
  * imbue .diff/Index parsing with C.UTF-8 as well

  [ Julian Andres Klode ]
  * Use C locale instead of C.UTF-8 for protocol strings
  * Add shippable.yml for CI on Shippable
  * Revert "if the FileFd failed already following calls should fail, too"
(LP: #1641905)

 -- Julian Andres Klode   Thu, 08 Dec 2016 15:28:08
+0100

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-1252

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

Title:
  Minor unit Test regression in 1.2.15

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1642386] Update Released

2017-01-11 Thread Brian Murray
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/1642386

Title:
  At least one invalid signature was encountered.

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

Bug description:
  [Summary]

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

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

  [Workaround]

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

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

  [Impact]
  Breaks update on systems with unreadable GPG keys

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

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

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

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

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

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease
  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease
  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease
  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]
  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]
  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]
  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease
  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB]
  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease
  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]
  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]
  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease
    At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease
  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease
    At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]
  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease
    At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease
  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]
  Hit:17 http://security.debian.org wheezy/updates InRelease
  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]
  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease
  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease
  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease
  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease
    At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease
  Hit:23 http://mirrors.kernel.org/ubuntu precise Release
  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release
  Ign:25 http://archive.canonical.com/ubuntu precise InRelease
  Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Hit:27 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease
  Hit:28 http://ftp.debian.org/debian unstable InRelease
  Err:6 http://mirrors.kernel.org/ubuntu precise-security InRelease
    At least one invalid signature was encountered.
  Err:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease
    At least one invalid signature was encountered

[Touch-packages] [Bug 1654722] Re: Ubuntu Touch: No sound on speakers but OK on headset

2017-01-11 Thread Pat McGowan
Everything seems normal to me, that is the same as a working device. 
I noticed you had played a game, last suggestion is to run the game again and 
set the volume there. In the past there had been issues where the volume 
remained muted playing media if sound effects were muted during a game, 
although that should no longer be the case. and the fact that the headphones 
work probably rules that out.
Otherwise perhaps backup the user data and reflash to rule out hardware. Sorry 
out of ideas.
@jim any thoughts? 

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Jim Hodapp (jhodapp)

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

Title:
  Ubuntu Touch: No sound on speakers but OK on headset

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Since a couple of days ago I have lost all sound on the speakers of the phone 
(no application plays any sound, no ringtones, notifications), but sounds can 
be heard normally with a headset. Sound
  configuration looks OK, and restarting does not help.

  I tried to remove .config/pulse completely and restart, but no progress. I 
attach the file 
  ubuntu-phablet-stream-volumes.tdb
  which was there before removing the folder and restarting.

  BQ E5, OTA 14.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:6.0-0ubuntu9.25
  Uname: Linux 3.4.67 armv7l
  AlsaInfo: This script requires lspci. Please install it, and re-run this 
script.
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sat Jan  7 09:30:00 2017
  InstallationDate: Installed on 2016-11-18 (49 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1641905] Update Released

2017-01-11 Thread Brian Murray
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/1641905

Title:
  Minor unit Test regression in 1.2.15

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

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

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

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

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

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

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

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

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


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

2017-01-11 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.2.18

---
apt (1.2.18) xenial; urgency=high

  * SECURITY UPDATE: gpgv: Check for errors when splitting files (CVE-2016-1252)
Thanks to Jann Horn, Google Project Zero for reporting the issue
(LP: #1647467)
  * gpgv: Flush the files before checking for errors

apt (1.2.17) xenial; urgency=medium

  [ David Kalnischkies ]
  * apt-key: warn instead of fail on unreadable keyrings (LP: #1642386)
  * show apt-key warnings in apt update (Closes: 834973)

  [ Julian Andres Klode ]
  * test-releasefile-verification: installaptold: Clean up before run

apt (1.2.16) xenial; urgency=medium

  [ David Kalnischkies ]
  * avoid changing the global LC_TIME for Release writing
  * use de-localed std::put_time instead rolling our own
  * accept only the expected UTC timezones in date parsing (Closes: 819697)
  * avoid std::get_time usage to sidestep libstdc++6 bug (LP: #1593583)
  * imbue datetime parsing with C.UTF-8 locale (Closes: 828011)
  * prevent C++ locale number formatting in text APIs (try 2) (Closes: 832044)
  * prevent C++ locale number formatting in text APIs (try 3) (LP: #1611010)
(LP: #1592817)
  * imbue .diff/Index parsing with C.UTF-8 as well

  [ Julian Andres Klode ]
  * Use C locale instead of C.UTF-8 for protocol strings
  * Add shippable.yml for CI on Shippable
  * Revert "if the FileFd failed already following calls should fail, too"
(LP: #1641905)

 -- Julian Andres Klode   Thu, 08 Dec 2016 15:28:08
+0100

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-1252

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

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

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

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

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

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

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

  [Test case]
  Steps to reproduce:

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

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

  Expected result: No crashes during installation

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

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

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

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


[Touch-packages] [Bug 1611010] Update Released

2017-01-11 Thread Brian Murray
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/1611010

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

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

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

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

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

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

  [Test case]
  Steps to reproduce:

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

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

  Expected result: No crashes during installation

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

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

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

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


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

2017-01-11 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.2.18

---
apt (1.2.18) xenial; urgency=high

  * SECURITY UPDATE: gpgv: Check for errors when splitting files (CVE-2016-1252)
Thanks to Jann Horn, Google Project Zero for reporting the issue
(LP: #1647467)
  * gpgv: Flush the files before checking for errors

apt (1.2.17) xenial; urgency=medium

  [ David Kalnischkies ]
  * apt-key: warn instead of fail on unreadable keyrings (LP: #1642386)
  * show apt-key warnings in apt update (Closes: 834973)

  [ Julian Andres Klode ]
  * test-releasefile-verification: installaptold: Clean up before run

apt (1.2.16) xenial; urgency=medium

  [ David Kalnischkies ]
  * avoid changing the global LC_TIME for Release writing
  * use de-localed std::put_time instead rolling our own
  * accept only the expected UTC timezones in date parsing (Closes: 819697)
  * avoid std::get_time usage to sidestep libstdc++6 bug (LP: #1593583)
  * imbue datetime parsing with C.UTF-8 locale (Closes: 828011)
  * prevent C++ locale number formatting in text APIs (try 2) (Closes: 832044)
  * prevent C++ locale number formatting in text APIs (try 3) (LP: #1611010)
(LP: #1592817)
  * imbue .diff/Index parsing with C.UTF-8 as well

  [ Julian Andres Klode ]
  * Use C locale instead of C.UTF-8 for protocol strings
  * Add shippable.yml for CI on Shippable
  * Revert "if the FileFd failed already following calls should fail, too"
(LP: #1641905)

 -- Julian Andres Klode   Thu, 08 Dec 2016 15:28:08
+0100

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-1252

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

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

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

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

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

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

  For the SRU:

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

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

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


[Touch-packages] [Bug 1593583] Update Released

2017-01-11 Thread Brian Murray
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/1593583

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

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

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

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

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

  For the SRU:

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

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

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


[Touch-packages] [Bug 1592817] Update Released

2017-01-11 Thread Brian Murray
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/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 apt source package in Xenial:
  Fix Released

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

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

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

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

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

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

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

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


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

2017-01-11 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.2.18

---
apt (1.2.18) xenial; urgency=high

  * SECURITY UPDATE: gpgv: Check for errors when splitting files (CVE-2016-1252)
Thanks to Jann Horn, Google Project Zero for reporting the issue
(LP: #1647467)
  * gpgv: Flush the files before checking for errors

apt (1.2.17) xenial; urgency=medium

  [ David Kalnischkies ]
  * apt-key: warn instead of fail on unreadable keyrings (LP: #1642386)
  * show apt-key warnings in apt update (Closes: 834973)

  [ Julian Andres Klode ]
  * test-releasefile-verification: installaptold: Clean up before run

apt (1.2.16) xenial; urgency=medium

  [ David Kalnischkies ]
  * avoid changing the global LC_TIME for Release writing
  * use de-localed std::put_time instead rolling our own
  * accept only the expected UTC timezones in date parsing (Closes: 819697)
  * avoid std::get_time usage to sidestep libstdc++6 bug (LP: #1593583)
  * imbue datetime parsing with C.UTF-8 locale (Closes: 828011)
  * prevent C++ locale number formatting in text APIs (try 2) (Closes: 832044)
  * prevent C++ locale number formatting in text APIs (try 3) (LP: #1611010)
(LP: #1592817)
  * imbue .diff/Index parsing with C.UTF-8 as well

  [ Julian Andres Klode ]
  * Use C locale instead of C.UTF-8 for protocol strings
  * Add shippable.yml for CI on Shippable
  * Revert "if the FileFd failed already following calls should fail, too"
(LP: #1641905)

 -- Julian Andres Klode   Thu, 08 Dec 2016 15:28:08
+0100

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-1252

-- 
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 apt source package in Xenial:
  Fix Released

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1655709] [NEW] Spurious crash report dialog on every login

2017-01-11 Thread Dan Kegel
Public bug reported:

For the last few years, on nearly all my computers, ubuntu has
rewarded my logging in with a crash dialog.  Nothing's actually
wrong; xorg probably trips over its shoelaces every time it
shuts down, but so late in the process that it doesn't matter.

Today I went through the crash upload procedure, but no
web browser window opened, so either I did something wrong,
or the bug is marked 'ignore uploads' somehow... hence
this manual report.

This bug has to have been reported before, but has probably
been marked WONTFIX or something because it is benign.

But it does matter, and it's not benign, because I, my wife, 
and my son get those darn crash dialogs.

It doesn't seem to matter what graphics card or driver is in use.

Want the crash file left behind after the last upload?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
Uname: Linux 4.4.0-43-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Jan 11 08:56:26 2017
DistUpgraded: 2016-04-26 16:26:11,919 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
InstallationDate: Installed on 2014-07-18 (908 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam 
/ CNF7129
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK Computer Inc. G60JX
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-43-generic 
root=UUID=28258489-6453-456a-9ecc-c41a02ad0631 ro rootflags=subvol=@ nomodeset 
quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-26 (259 days ago)
dmi.bios.date: 08/16/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G60JX
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: PEGATRON Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr208:bd08/16/2010:svnASUSTeKComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
dmi.product.name: G60JX
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Jan 11 08:41:53 2017
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

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

Title:
  Spurious crash report dialog on every login

Status in xorg package in Ubuntu:
  New

Bug description:
  For the last few years, on nearly all my computers, ubuntu has
  rewarded my logging

[Touch-packages] [Bug 1605796] Re: mesa FTBFS on ppc64el with -O3 due to ICE

2017-01-11 Thread Timo Aaltonen
** Changed in: mesa (Ubuntu)
   Status: New => Fix Committed

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

Title:
  mesa FTBFS on ppc64el with -O3 due to ICE

Status in gcc-6 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed

Bug description:
  Dropping optimization to -O2 allows this build to succeed:

  https://launchpad.net/ubuntu/+source/mesa/12.0.1-3ubuntu1/+build/10484583

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/1605796/+subscriptions

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


[Touch-packages] [Bug 1568829] Re: nm-applet icon not showing when /proc is mounted with hidepid!=0

2017-01-11 Thread Aron Xu
** Changed in: network-manager (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1568829

Title:
  nm-applet icon not showing when /proc is mounted with hidepid!=0

Status in Network Manager Applet:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  Steps to reproduce:

  1. (Re-)mount /proc with hidepid=1 (or =2)
  2. Restart nm-applet

  nm-applet's icon does not reappear after the restart. This used to
  work with version 1.0.

  
  Original bug description:

  Since I upgraded to -proposed network-manager and network-manager-gnome 
versions, nm-applet no longer works.
  Manually starting it on a console give:

  $ nm-applet

  (nm-applet:6250): nm-applet-WARNING **: 
GDBus.Error:org.freedesktop.NetworkManager.AgentManager.PermissionDenied: 
Unable to determine request sender and UID.
  (nm-applet:6250): libnm-CRITICAL **: nm_client_get_nm_running: assertion 
'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_get_state: assertion 
'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_networking_get_enabled: 
assertion 'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_get_enabled: 
assertion 'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_hardware_get_enabled: 
assertion 'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_get_enabled: assertion 
'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_hardware_get_enabled: 
assertion 'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_get_devices: assertion 
'NM_IS_CLIENT (client)' failed

  What's odd is the NM and NM-gnome base versions are not identical:

  $ apt-cache policy network-manager network-manager-gnome
  network-manager:
    Installed: 1.1.93-0ubuntu1
    Candidate: 1.1.93-0ubuntu1
    Version table:
   *** 1.1.93-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.4-0ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  network-manager-gnome:
    Installed: 1.1.93-1ubuntu1
    Candidate: 1.1.93-1ubuntu1
    Version table:
   *** 1.1.93-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.10-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-gnome 1.1.93-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 11 08:16:59 2016
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 1:
   (process:7301): nmcli-CRITICAL **: Error: Could not create NMClient object: 
Unable to authenticate request..
  nmcli-dev:
   Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 1:
   (process:7297): nmcli-CRITICAL **: Error: Could not create NMClient object: 
Unable to authenticate request..
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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


[Touch-packages] [Bug 1565080] Re: ubuntuBSD support

2017-01-11 Thread Timo Aaltonen
** Changed in: mesa (Ubuntu)
   Status: New => Fix Committed

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

Title:
  ubuntuBSD support

Status in mesa package in Ubuntu:
  Fix Committed

Bug description:
  Hi

  Please could you apply attached patch to make mesa buildable on
  ubuntuBSD? It just needs to adjust a few dependencies.

  Thanks!

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

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


[Touch-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

2017-01-11 Thread Aron Xu
Hi chih, the patch can't apply cleanly in nm-1.2, needs some porting.

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  New
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION 
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged-- 

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+subscriptions

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

2017-01-11 Thread Robie Basak
> ** Changed in: cups (Ubuntu Xenial)   
>
>Status: Fix Committed => Fix Released

No, it's not.

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

-- 
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:
  Fix Committed

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

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

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


[Touch-packages] [Bug 1625409] Re: /usr/lib/accountsservice/accounts-daemon:6:g_assertion_message:g_assertion_message_expr:do_exec:fork_exec_with_pipes:g_spawn_sync

2017-01-11 Thread Sebastien Bacher
** Changed in: accountsservice (Ubuntu)
   Importance: Undecided => Low

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

Title:
  /usr/lib/accountsservice/accounts-
  
daemon:6:g_assertion_message:g_assertion_message_expr:do_exec:fork_exec_with_pipes:g_spawn_sync

Status in accountsservice package in Ubuntu:
  New

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

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

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


[Touch-packages] [Bug 1542743] Re: Bluetooth: Patch file not found ar3k/AthrBT_0x00000200.dfu

2017-01-11 Thread chevrier
Thank you so much!! This works for Kernel 4.9.2
Your deb files allowed me to get bluetooth to work on all possible kernels...
you are the man!

i just need to figure out now how to get the sound to come out from the 
earphones when plugged in - that driver I downloaded for the old kernels does 
not seem to work for the newer one - a bit of a nuisance - i am using recon 3d 
i soundblaster, i think...  it's the standard on dell alienware i believe (m17 
r 2 for me)
many thanks

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

Title:
  Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Since some Versions of Linux Kernel and Ubuntu Releases this problem
  exists.

  I am now running ubuntu 16.04 prerelease and still have the same
  problem.

  Bluetooth does not work with the atheros device on  msi gt 72 2qd
  notebook.

  WORKAROUND FOR [0CF3:3004] DEVICE ONLY with kernel 4.4:

  sudo apt install dkms
  wget 
https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542743-dkms_0.1_all.deb
  sudo dpkg -i btusb-lp1542743-dkms_0.1_all.deb

  FOR KERNEL 4.8 A WORKAROUND DKMS DEB IS

  https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files
  /btusb-lp1542743-dkms_0.2~4.8_all.deb

  dmesg | grep Bluetooth:
  [2.655360] Bluetooth: Core ver 2.21
  [2.655373] Bluetooth: HCI device and connection manager initialized
  [2.655377] Bluetooth: HCI socket layer initialized
  [2.655379] Bluetooth: L2CAP socket layer initialized
  [2.655385] Bluetooth: SCO socket layer initialized
  [6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.612794] Bluetooth: BNEP filters: protocol multicast
  [6.612798] Bluetooth: BNEP socket layer initialized
  [9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
  [9.016882] Bluetooth: Loading patch file failed

  hwinfo | grep Bluetooth:
  <6>[6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    <6>[6.612794] Bluetooth: BNEP filters: protocol multicast
    <6>[6.612798] Bluetooth: BNEP socket layer initialized
    <3>[9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
    <3>[9.016882] Bluetooth: Loading patch file failed
  60: USB 00.0: 11500 Bluetooth Device
    Model: "Atheros AR3012 Bluetooth 4.0"
    Device: usb 0x3004 "AR3012 Bluetooth 4.0"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.36-0ubuntu1
  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.19.4-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  7 00:38:04 2016
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2015-10-24 (105 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. GT72 2QD
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=f7880b23-39b5-423a-bdbf-62b111783450 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-02-02 (4 days ago)
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10I
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10I:bd12/19/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QD:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QD
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:

  rfkill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no

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

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


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

2017-01-11 Thread Eric Desrochers
Installing isc-dhcp-client-noddns on Trusty and then upgrade to Xenial
with a local archive of a modified Xenial's isc-dhcp-client to replace
isc-dhcp-client-noddns package to isc-dhcp-client during release upgrade
from Trusty to Xenial work as expected with a completed successful
release upgrade.

+Replaces:
+ isc-dhcp-client-noddns (<< 4.2.4-7ubuntu12.8+noddnsbuild1),

Capture after upgrade :

# cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

# dpkg -l | grep -i dhcp
ii  isc-dhcp-client4.3.3-5ubuntu12.7   amd64
DHCP client for automatically obtaining an IP address
rc  isc-dhcp-client-noddns 4.2.4-7ubuntu12.8+noddnsbuild1  amd64
Dynamic DNS (DDNS) enabled DHCP client
ii  isc-dhcp-common4.3.3-5ubuntu12.6   amd64
common files used by all of the isc-dhcp packages

# lsof -i udp
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
dhclient 707 root6u  IPv4  16437  0t0  UDP *:bootpc 

# ls -altr /sbin/dhclient*
-rwxr-xr-x 1 root root  15219 Jan 11 09:12 /sbin/dhclient-script
-rwxr-xr-x 1 root root 487248 Jan 11 09:12 /sbin/dhclient

The only thing that could be improve that I can't think of right now, is
to not make isc-dhcp-client-noddns not turn into "rc" state by making
sure its configuration files doesn't remain.

- Eric

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

Title:
  isc-dhcp dhclient listens on extra random ports

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

Bug description:
  [Impact]

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

  Impact reported by users :

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

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

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

  Xenial has separated dhclient in two packages :

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

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

  [Test Case]

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

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

  
  [Regression Potential] 

  * none expected

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

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

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

  Note that this is how Xenial does it.

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

  [Original Description]

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

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bu

[Touch-packages] [Bug 976410] Re: mga_dri.so missing in mesa

2017-01-11 Thread Timo Aaltonen
there is no DRI driver for mga anymore, the old one got dropped from 8.0
because it didn't support DRI2

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  mga_dri.so missing in mesa

Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  ubuntu 12.04 beta2, libgl1-mesa-dri

  Mesa falls back to sw rendering on my Matrox G500 graphics board. Poor
  grafic performance. The driver was present in 11.10.

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

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


[Touch-packages] [Bug 1654722] Re: Ubuntu Touch: No sound on speakers but OK on headset

2017-01-11 Thread Walter Garcia-Fontes
pat-mcgowan: I installed a couple of games exactly for what you way,
trying to turn the volume on and off to see if I got back the sound, but
it didn't work out.

I wait a couple of days more and reflash.

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

Title:
  Ubuntu Touch: No sound on speakers but OK on headset

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Since a couple of days ago I have lost all sound on the speakers of the phone 
(no application plays any sound, no ringtones, notifications), but sounds can 
be heard normally with a headset. Sound
  configuration looks OK, and restarting does not help.

  I tried to remove .config/pulse completely and restart, but no progress. I 
attach the file 
  ubuntu-phablet-stream-volumes.tdb
  which was there before removing the folder and restarting.

  BQ E5, OTA 14.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:6.0-0ubuntu9.25
  Uname: Linux 3.4.67 armv7l
  AlsaInfo: This script requires lspci. Please install it, and re-run this 
script.
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sat Jan  7 09:30:00 2017
  InstallationDate: Installed on 2016-11-18 (49 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

2017-01-11 Thread Aron Xu
@ubuntu-sponsor, please help sponsor the following branch xenial, which has 
been updated to 1.2.6 as well:
https://code.launchpad.net/~network-manager/network-manager/+git/ubuntu/+ref/xenial

** Description changed:

  [Impact]
  
  This SRU would try to have the latest well-tested upstream point release
- (1.2.4) of 1.2.x land in Xenial, which is the successor of the current
+ (1.2.6) of 1.2.x land in Xenial, which is the successor of the current
  1.2.2 version, fixing quite some bugs that's suitable to land in the
  stable branch.
  
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2
- 
- For xenial, we'll also backporting a patch from 1.2.6 that should fix a
- no-networking-after-resuming-from-sleep issue. This patch was applied to
- Debian testing and zesty in 1.4.2-3ubuntu1.
- 
- For yakkety, this is an update to 1.2.6. Once 1.2.6 has been in use for
- a while without new problems, we'll look into doing a separate SRU for
- Xenial.
  
  [Test Case]
  
  After installing the updated version, users should be able to avoid some
  mem leaks in some cases and have generally improved DNS related
  experiences.
  
  [Regression Potential]
  
- This version has been in yakkety for sometime, and there's no report of
- regressions until now.
+ This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
+ complete.

** Tags removed: verification-failed

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Triaged
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

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

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

  [Test Case]

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

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

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

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


[Touch-packages] [Bug 1567650] Re: Wifi hotspot removed after ota-7 and no usb tethering gui

2017-01-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Wifi hotspot removed after ota-7 and no usb tethering gui

Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  On my nexus 4 on bq aquaris RC channel the non working wifi hotspot
  option in settings is gone. There is also no guide for usb tethering.

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

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


[Touch-packages] [Bug 1465766] Re: low sound volume

2017-01-11 Thread Stephen Wilson
OP here. This bug still exists. A very partial workaround is to use
PulseAudio Equalizer. Zero out the first three channels (50, 100, 156
Hz) and the highest one (20 KHz) because the speakers cannot make them
anyway. Bump up some of the others until it sounds best to you. It
doesn't solve the problem, but it improves the sound somewhat.

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

Title:
  low sound volume

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  this is a thinkpad x1 carbon 3rd gen running xubuntu 15.04

  sound volume is very low compared to windows (dual boot), even with
  alsa and pulseaudio controls set to 100% (or greater).

  this applies to all apps.

  i can get really loud sound with:
  pactl set-sink-volume 1 30
  but then it is very distorted.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  smwilson   1577 F pulseaudio
   /dev/snd/controlC0:  smwilson   1577 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jun 16 06:44:39 2015
  InstallationDate: Installed on 2015-06-04 (11 days ago)
  InstallationMedia: Xubuntu Core 15.04 - amd64 - 20150425
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Volume slider, or mixer problems
  Title: [20BSCTO1WW, Realtek ALC3232, Speaker, Internal] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET25W (1.03 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET25W(1.03):bd12/01/2014:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1655723] [NEW] kernel linux-image-extra-4.8.0-34-generic 4.8.0-34.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 143

2017-01-11 Thread kihosap
Public bug reported:

this kernel version fails to apply, "sync" seems hanged while compiling

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: linux-image-extra-4.8.0-34-generic 4.8.0-34.36
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.2
AptOrdering:
 linux-generic:amd64: Remove
 linux-image-generic:amd64: Remove
 linux-image-extra-4.8.0-34-generic:amd64: Remove
 linux-image-4.8.0-34-generic:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  ostia  3412 F pulseaudio
 /dev/snd/controlC0:  ostia  3412 F pulseaudio
 /dev/snd/controlC1:  ostia  3412 F pulseaudio
Date: Wed Jan 11 11:07:28 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 143
HibernationDevice: RESUME=UUID=c75246c5-69ac-4f5b-9360-f554aeb55482
InstallationDate: Installed on 2016-12-14 (28 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IwConfig:
 as0t0 no wireless extensions.
 
 enp3s0no wireless extensions.
 
 lono wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. H81M-S2H
ProcFB:
 0 VESA VGA
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=3cf0a264-0929-4ada-86b4-f91cd955c038 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
RfKill:
 0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.8.0-34-generic 4.8.0-34.36 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 143
UpgradeStatus: Upgraded to yakkety on 2016-12-15 (27 days ago)
dmi.bios.date: 08/11/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-S2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S2H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: H81M-S2H
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package yakkety

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

Title:
  kernel  linux-image-extra-4.8.0-34-generic 4.8.0-34.36 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 143

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  this kernel version fails to apply, "sync" seems hanged while
  compiling

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-extra-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   linux-generic:amd64: Remove
   linux-image-generic:amd64: Remove
   linux-image-extra-4.8.0-34-generic:amd64: Remove
   linux-image-4.8.0-34-generic:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ostia  3412 F pulseaudio
   /dev/snd/controlC0:  ostia  3412 F pulseaudio
   /dev/snd/controlC1:  ostia  3412 F pulseaudio
  Date: Wed Jan 11 11:07:28 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 143
  HibernationDevice: RESUME=UUID=c75246c5-69ac-4f5b-9360-f554aeb55482
  InstallationDate: Installed on 2016-12-14 (28 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   as0t0 no wireless extensions.
   
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H81M-S2H
  ProcFB:
   0 VESA VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=3cf0a264-0929-4ada-86b4-f91cd955c038 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daem

[Touch-packages] [Bug 1391243] Re: [utopic] libg1-mesa-dev doesn't create any libGL.so link

2017-01-11 Thread Timo Aaltonen
fglrx is removed from the archive

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

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

Title:
  [utopic] libg1-mesa-dev doesn't create  any libGL.so link

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Package version installed: 10.3.0-0ubuntu3
  Ubuntu release: Utopic (normal upgrade from Trusty)

  Trying to build OpenGL-depending program I run ./configure script
  which tries to invoke «glBegin» with gcc and -lGL, and it fails.

  I have both libgl1-mesa-{dev,dri,glx} and fglrx-updates{,-dev} installed, and 
only manual symlinking helps.
  Alhough I wanted fglrx libGL.so.1.2 symlinked, none is being symlinked, so 
it's bad in its current state.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libgl1-mesa-dev 10.3.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic i686
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  BootLog: * Starting Deluge BitTorrent Daemon deluged
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Nov 10 19:40:31 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates-core, 14.201, 3.16.0-23-generic, i686: installed
   fglrx-updates-core, 14.201, 3.16.0-25-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] 
(prog-if 00 [VGA controller])
     Subsystem: Toshiba America Info Systems Device [1179:fa34]
     Subsystem: Toshiba America Info Systems Device [1179:fa34]
  InstallationDate: Installed on 2013-10-30 (376 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  LightdmGreeterLog: ** (lightdm-gtk-greeter:6257): WARNING **: Failed to load 
user image: Failed to open file '/home/reslayer/.face': No such file or 
directory
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:5685): WARNING **: Failed to 
load user image: Failed to open file '/home/reslayer/.face': No such file or 
directory
  MachineType: TOSHIBA Satellite C50D-A-K8K
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: PT10AN
  dmi.board.vendor: AMD
  dmi.board.version: Base 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.10:bd05/22/2013:svnTOSHIBA:pnSatelliteC50D-A-K8K:pvrPSCH2R-00700JRU:rvnAMD:rnPT10AN:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C50D-A-K8K
  dmi.product.version: PSCH2R-00700JRU
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Oct 28 04:22:34 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1
  xserver.video_driver: fglrx

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

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


[Touch-packages] [Bug 1298517] Re: Rendering issues in unity with xserver-modeset

2017-01-11 Thread Timo Aaltonen
I believe this is fixed since, if not feel free to reopen

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

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

Title:
  Rendering issues in unity with xserver-modeset

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Starting to report this against unity, feel free to re-assign against
  the correct package (the xserver or llvm-pipe?). With the current
  Trusty image (64bit) installed into a VM (KVM or Xen) that uses the
  default Cirrus graphics (using virt-managers VNC viewer), I see at
  least two issues:

  1. Occasionally (not sure how to force it to happen) the mouse pointer
  will not be rendered while input grab is active. This leaves no
  indication about where the mouse pointer is. In some cases it seemed
  to help when I switched to a text console and back.

  2. Near to unreadable gnome terminal sessions. Background seems half
  transparent, half unset. Text barely readable.

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

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


[Touch-packages] [Bug 949606] Re: 64 bit dev packages should include 32 bit .so library file

2017-01-11 Thread Timo Aaltonen
nope, libraries should just be migrated to support multiarch, like
libglu 9.0.0-2.1

** Changed in: mesa (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  64 bit dev packages should include 32 bit .so library file

Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  64 bit dev packages contain a 64 bit version of the library file(s)
  that they provide for linking but not a 32 bit version of the library
  file(s). In previous versions of Ubuntu, however, it was possible to
  compile 32 bit applications using the 64 bit dev packages in by
  installing ia32-libs, which contained the required 32 bit library
  files.

  In the move to multiarch, 32 bit library files are being removed from
  ia32-libs. Multiarch (I assume) aims to keep the architectures
  separate, so the generally intended solution is to install the i386
  version of the dev package when compiling 32 bit applications, ie
  side-by-side with the 64 bit dev package.

  However, some 64 bit development packages conflict with their 32 bit
  equivalent. This creates a regressive situation where it is impossible
  to install them side-by-side - you are forced to either install the 32
  bit package, which breaks 64 bit compilations, or the 64 bit package,
  which breaks 32 bit compilations.

  An example is libglu1-mesa-dev, which conflicts with libglu1-mesa-
  dev:i386. The libglu1-mesa-dev file contains all the necessary
  development files for 32 bit *except* for the 32 bit library file. It
  does contain the 64 bit library file. Since the library file is part
  of the development files, libglu1-mesa-dev does not contain all the
  necessary development files for 32 bit, ie it does not contain all the
  necessary development files for multiarch. I think that it *should*
  contain all the necessary files for building multarch applications.

  The two workarounds are:

  1. Manually re-install the required i386 dev packages before compiling
  32 bit apps, and then manually re-install the required amd64 dev
  packages before compiling 64 bit apps. This is a real pain.

  2. Install the i386 binary package (eg libglu1-mesa:i386) and the
  amd64 dev package (eg libglu1-mesa-dev), and manually create symlinks
  for the i386 libXYZ.so package (eg sudo ln -s /usr/lib/i386-linux-
  gnu/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so). This is a more
  permanent solution but is a real pain to set up, as you have to find
  each missing library manually, and some library files, like
  mesa/libGL.so.1, are in subfolders.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libglu1-mesa-dev 8.0.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.94.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,grid,resize,compiztoolbox,vpswitch,place,gnomecompat,move,regex,animation,imgpng,snap,mousepoll,session,expo,workarounds,wall,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  Date: Thu Mar  8 10:20:54 2012
  DistUpgraded: Log time: 2012-02-26 08:25:08.500725
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox-guest, 4.1.8, 3.2.0-12-generic, x86_64: installed
   virtualbox-guest, 4.1.8, 3.2.0-14-generic, x86_64: installed
   virtualbox-guest, 4.1.8, 3.2.0-17-generic, x86_64: installed
   virtualbox-guest, 4.1.8, 3.2.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120201.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic 
root=UUID=630a9f76-6f8f-43be-bb99-6be721c9deaf ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: mesa
  UpgradeStatus: Upgraded to precise on 2012-02-26 (11 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.30-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A

[Touch-packages] [Bug 1649149] Re: Takes a long time to load

2017-01-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Takes a long time to load

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  On Meizu Pro 5, both with OTA-13 and OTA-14, gallery-app takes about
  1.5 minutes to load. Meanwhile it uses 100% of one cpu. I have a lot
  of photos on my SD card (25GB). I would expect the app to load
  instantaneously or in a few seconds.

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

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


[Touch-packages] [Bug 1649149] Re: Takes a long time to load

2017-01-11 Thread dinamic
same here with a lot of images, it takes very long to load :*(

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

Title:
  Takes a long time to load

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  On Meizu Pro 5, both with OTA-13 and OTA-14, gallery-app takes about
  1.5 minutes to load. Meanwhile it uses 100% of one cpu. I have a lot
  of photos on my SD card (25GB). I would expect the app to load
  instantaneously or in a few seconds.

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

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


[Touch-packages] [Bug 1649149] Re: Takes a long time to load

2017-01-11 Thread dinamic
on Meizu Mx4

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

Title:
  Takes a long time to load

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  On Meizu Pro 5, both with OTA-13 and OTA-14, gallery-app takes about
  1.5 minutes to load. Meanwhile it uses 100% of one cpu. I have a lot
  of photos on my SD card (25GB). I would expect the app to load
  instantaneously or in a few seconds.

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

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


[Touch-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

2017-01-11 Thread Barry Warsaw
Removed unhelpful attachments and retagged to armhf.

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

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

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Incomplete
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1655735] Missing required logs.

2017-01-11 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1655735

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Incomplete
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1655302] Re: [Trusty] systemd startup fails in the presence of cgmanager

2017-01-11 Thread Dave Morley
** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Trusty] systemd startup fails in the presence of cgmanager

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In trusty, systemd 204 clashes with cgmanager, with systemd failing to
  start up properly. As a consequence, snapd fails to operate properly.

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

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


[Touch-packages] [Bug 1646517] Re: In unity8-session snap on Core 16, no battery icon is shown

2017-01-11 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

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

** Changed in: canonical-devices-system-image
Milestone: p1 => p2

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

Title:
  In unity8-session snap on Core 16, no battery icon is shown

Status in Canonical System Image:
  Confirmed
Status in indicator-power package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I was testing the unity8-session in a Core 16 VM, and I noticed that
  indicator-power wasn't showing an icon in the top panel.

  When I opened the indicator menu, indicator-power seemed to be filling
  out its menu correctly, so it is running.  It just didn't give an icon
  that u8 knew about (or we aren't bundling the right icons into the
  snap?).  But I bet that the indicator is giving back an absolute path
  that points outside the snap.

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

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


[Touch-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

2017-01-11 Thread Barry Warsaw
On Jan 11, 2017, at 06:30 PM, Brad Figg wrote:

>If, due to the nature of the issue you have encountered, you are unable
>to run this command, please add a comment stating that fact and change
>the bug status to 'Confirmed'.

This is probably a regression only on armhf, so the logs generated on amd64
won't be helpful.


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

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1589637] Re: Unable to open multiple instances of the same app

2017-01-11 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: p1 => p2

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

Title:
  Unable to open multiple instances of the same app

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  You're unable to open two instances of the same app. Such as gedit or
  firefox.

  qtmir needs instance-based signals: app instance started, app instance 
stopped, etc
  As in 
http://bazaar.launchpad.net/~indicator-applet-developers/ubuntu-app-launch/trunk.16.10/view/head:/libubuntu-app-launch/registry.h#L77

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

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


[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment

2017-01-11 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: p1 => p2

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

Title:
  mission-control should use different paths when in a snap environment

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  New
Status in telepathy-mission-control-5 package in Ubuntu:
  Confirmed

Bug description:
  When running confined into a snap environment, mission-control needs
  to use different paths for its files:

  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.CC7LOY':
 No such file or directory
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.7I1LOY':
 No such file or

  Instead of using $SNAP, it probably should use $SNAP_DATA

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

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


[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

2017-01-11 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

** Changed in: canonical-devices-system-image
Milestone: p1 => p2

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

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

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

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


[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

2017-01-11 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: p1 => p2

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Canonical System Image:
  In Progress
Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Released
Status in address-book-service package in Ubuntu:
  Fix Released
Status in camera-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu:
  Fix Released
Status in gallery-app package in Ubuntu:
  Fix Released
Status in history-service package in Ubuntu:
  Fix Released
Status in indicator-bluetooth package in Ubuntu:
  Fix Released
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  Fix Released
Status in indicator-location package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in indicator-network package in Ubuntu:
  Fix Released
Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-session package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in maliit-framework package in Ubuntu:
  In Progress
Status in mediaplayer-app package in Ubuntu:
  Fix Released
Status in mediascanner2 package in Ubuntu:
  Fix Released
Status in messaging-app package in Ubuntu:
  Fix Released
Status in policykit-unity8 package in Ubuntu:
  Fix Released
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in unity-scope-scopes package in Ubuntu:
  Won't Fix
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

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

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


[Touch-packages] [Bug 1171929] Re: removing package for account support leaves null entry

2017-01-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-control-center-signon (Ubuntu)
   Status: New => Confirmed

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

Title:
  removing package for account support leaves null entry

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

Bug description:
  1. Add Twitter account
  2. Remove package account-plugin-twitter
  3. Open GCC online account panel
  4. Entry is there, but it is null

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Tue Apr 23 17:31:37 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-12-07 (137 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121207)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sk_SK.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center-signon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1652695] Re: GCE default NTP configuration uses both leap-smeared and true UTC sources

2017-01-11 Thread Philip Roche
This seems to be somewhat related to https://bugs.launchpad.net/cpc-
gce/+bug/1639089 (only affects Xenial).

In summary the "pool" entries in ntp.conf should be commented out by
gce-cloud-config but when ntp.conf transitioned from using "server" to
"pool" gce-cloud-config was not updated.

I will be fixing lp:1639089 in the GCE Xenial image build process
initially followed by a fix for gce-cloud-config.

Note that gce-cloud-config is being deprecated in favour of gce-compute-
image-packages which does not have this bug.

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

Title:
  GCE default NTP configuration uses both leap-smeared and true UTC
  sources

Status in cloud-images:
  New
Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  A default install of cloud images on GCE results in a configuration of
  NTP which will likely be problematic during leap seconds, because it
  uses both Google's leap-smeared time source, and the public pool,
  which uses true UTC.  These should not be combined in the default
  configuration.

  The principle of least astonishment would suggest that a non-standard
  feature like leap smearing should be disabled by default.

  This behaviour has been consistent in the 3 different GCE regions in
  which I've recently created instances.

  
  root@instance-4:~# cat /etc/cloud/build.info 
  build_name: server
  serial: 20161221

  
  root@instance-4:~# cat /etc/ntp.conf
  # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help

  driftfile /var/lib/ntp/ntp.drift

  # Enable this if you want statistics to be logged.
  #statsdir /var/log/ntpstats/

  statistics loopstats peerstats clockstats
  filegen loopstats file loopstats type day enable
  filegen peerstats file peerstats type day enable
  filegen clockstats file clockstats type day enable

  # Specify one or more NTP #servers.

  # Use servers from the NTP Pool Project. Approved by Ubuntu Technical Board
  # on 2011-02-08 (LP: #104525). See http://www.pool.ntp.org/join.html for
  # more information.
  pool 0.ubuntu.pool.ntp.org iburst
  pool 1.ubuntu.pool.ntp.org iburst
  pool 2.ubuntu.pool.ntp.org iburst
  pool 3.ubuntu.pool.ntp.org iburst

  # Use Ubuntu's ntp #server as a fallback.
  pool ntp.ubuntu.com

  # ... comments snipped ...

  # By default, exchange time with everybody, but don't allow configuration.
  restrict -4 default kod notrap nomodify nopeer noquery limited
  restrict -6 default kod notrap nomodify nopeer noquery limited

  # Local users may interrogate the ntp #server more closely.
  restrict 127.0.0.1
  restrict ::1

  # Needed for adding pool entries
  restrict source notrap nomodify noquery

  # ... comments snipped ...

  # Google NTP source. This was added as part of the gce-cloud-config package.
  server metadata.google.internal

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1652695/+subscriptions

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


  1   2   >