[Touch-packages] [Bug 1602256] Re: sometimes "systemd-coredump[]: Coredump file descriptor missing." is seen, upstream #2984

[LeK]

Unfortunately the fix did not help.

Output in the journal now has an extra line about creating a slice.

:~$ sudo journalctl --file /run/log/journal//system.journal

Jul 13 02:29:08 COBPTTDev kernel: asterisk[1570]: segfault at 300028 ip 
7f4961158d16 sp 7f48d84e8a38 error 4 in 
libc-2.23.so[7f49610ce000+1c]
Jul 13 02:29:08 COBPTTDev systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
Jul 13 02:29:08 COBPTTDev systemd[1]: Started Process Core Dump (PID 1607/UID 
0).
Jul 13 02:29:08 COBPTTDev systemd-coredump[1608]: Coredump file descriptor 
missing.

Likewise the coredump list is empty
:~$ sudo coredumpctl list /usr/sbin/asterisk
No coredumps found.

(asterisk is the Ubuntu package in Xenial)

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

Title:
  sometimes "systemd-coredump[]: Coredump file descriptor missing."
  is seen, upstream #2984

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

Bug description:
  Please include this upstream fix/pull request:

  coredump: use next_datagram_size_fd instead of ioctl(FIONREAD) #3237
  https://github.com/systemd/systemd/pull/3237

  Reported as
  sometimes "systemd-coredump[]: Coredump file descriptor missing." is 
seen, upstream #2984
  https://github.com/systemd/systemd/issues/2984

  Or make a release using systemd tag=v230

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

  :~$ apt-cache policy systemd
  systemd:
    Installed: 229-4ubuntu6
    Candidate: 229-4ubuntu6
    Version table:
   *** 229-4ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  SRU INFORMATION
  ---
  This only affects systemd-coredump which we don't use in Ubuntu by default 
(we use Apport), so the regression potential is very low. There is no 
straightforward reproducer for this (see upstream bug report: 
https://github.com/systemd/systemd/issues/2984). But our systemd package has 
integration tests for coredump: 
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/tests/boot-and-services?h=ubuntu-xenial#n436
 

  Thus if the updated package still succeeds its autopkgtests, this
  should provide sufficient regression testing for this bug.

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

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

[Touch-packages] [Bug 1588126] Re: [OTA-11] Wifi never connects since installing OTA-11

[Daniel van Vugt]

Workaround:
Flash the OTA-10 image first and set up wifi in OTA-10 which works. Then when 
you upgrade to OTA-11 over the air for real, the wifi config will continue 
working in OTA-11.

So the problem is just that a raw phone shipped with OTA-11 can't
connect to wifi when configured in the wizard or network indicator.

** Summary changed:

- [OTA-11] Wifi never connects since installing OTA-11
+ [OTA-11] Wifi never connects since installing OTA-11 (unless you install 
OTA-10 first)

** Summary changed:

- [OTA-11] Wifi never connects since installing OTA-11 (unless you install 
OTA-10 first)
+ [OTA-11] Wifi never connects since flashing OTA-11 (unless you flash OTA-10 
first then upgrade)

** Tags added: regression

** Summary changed:

- [OTA-11] Wifi never connects since flashing OTA-11 (unless you flash OTA-10 
first then upgrade)
+ [regression] [OTA-11] Wifi never connects since flashing OTA-11 (unless you 
flash OTA-10 first then upgrade)

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

Title:
  [regression] [OTA-11] Wifi never connects since flashing OTA-11
  (unless you flash OTA-10 first then upgrade)

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  I've just flashed clean images of OTA-11 from the stable channel onto
  a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the
  phones can see the wifi networks but can't connect to any of them any
  more.

  The wifi networks continue to work for non-Ubuntu devices.

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

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

[Touch-packages] [Bug 1602522] Re: The new Calendar on indicator doesn't use the translation's date format

[Launchpad Bug Tracker]

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

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Confirmed

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

Title:
  The new Calendar on indicator doesn't use the translation's date
  format

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On the rc-proposed channel there is a calendar (again) on the datetime
  indicator, but it doesn't use the date format of the system's
  language. See the screenshot

  It shows „Július 2016”, but as you see above on the image, it should
  be „2016 július”.

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

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

[Touch-packages] [Bug 1602522] [NEW] The new Calendar on indicator doesn't use the translation's date format

[Robin Heroldich]

Public bug reported:

On the rc-proposed channel there is a calendar (again) on the datetime
indicator, but it doesn't use the date format of the system's language.
See the screenshot

It shows „Július 2016”, but as you see above on the image, it should be
„2016 július”.

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Attachment added: "screenshot20160713_082439609.png"
   
https://bugs.launchpad.net/bugs/1602522/+attachment/4699860/+files/screenshot20160713_082439609.png

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

Title:
  The new Calendar on indicator doesn't use the translation's date
  format

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On the rc-proposed channel there is a calendar (again) on the datetime
  indicator, but it doesn't use the date format of the system's
  language. See the screenshot

  It shows „Július 2016”, but as you see above on the image, it should
  be „2016 július”.

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

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

[Touch-packages] [Bug 1591895] Re: SRU: backport python 2.7.12 to 16.04 LTS

[Launchpad Bug Tracker]

This bug was fixed in the package python2.7 - 2.7.12-1~16.04

---
python2.7 (2.7.12-1~16.04) xenial-proposed; urgency=medium

  * SRU: LP: #1591895. Backport 2.7.12 to 16.04 LTS.

python2.7 (2.7.12-1) unstable; urgency=medium

  * Python 2.7.12 release.

python2.7 (2.7.12~rc1-2) unstable; urgency=medium

  * Extend debian/copyright to the files shipped in the wheel files.

python2.7 (2.7.12~rc1-1) unstable; urgency=medium

  * Python 2.7.12 release candidate 1.
- Issue #20041: Fixed TypeError when frame.f_trace is set to None.
- Issue #25702: A --with-lto configure option has been added that will
  enable link time optimizations at build time during a make profile-opt.
  Some compilers and toolchains are known to not produce stable code when
  using LTO, be sure to test things thoroughly before relying on it.
  It can provide a few % speed up over profile-opt alone.
- Issue #26556: Update expat to 2.1.1, fixes CVE-2015-1283.
- Fix TLS stripping vulnerability in smptlib, CVE-2016-0772.
- Issue #7356: ctypes.util: Make parsing of ldconfig output independent of
  the locale.
- Issue #25738: Stop BaseHTTPServer.BaseHTTPRequestHandler.send_error()
  from sending a message body for 205 Reset Content.  Also, don't send the
  Content-Type header field in responses that don't have a body.
- Issue #21313: Fix the "platform" module to tolerate when sys.version
  contains truncated build information.
- Issue #27211: Fix possible memory corruption in io.IOBase.readline().
- Issue #5124: Paste with text selected now replaces the selection on X11.
  This matches how paste works on Windows, Mac, most modern Linux apps,
  and ttk widgets.
- Issue #24759: Make clear in idlelib.idle_test.__init__ that the directory
  is a private implementation of test.test_idle and tool for maintainers.
- Issue #21916: Added tests for the turtle module.
- Issue #27229: Fix the cross-compiling pgen rule for in-tree builds.
- Issue #17500, and https://github.com/python/pythondotorg/issues/945: 
Remove
  unused and outdated icons.

python2.7 (2.7.11-11) unstable; urgency=medium

  * Update to 20160602 from the 2.7 branch.
- Issue #26168: Fixed possible refleaks in failing Py_BuildValue() with
  the "N" format unit.
- Issue #27114: Fix SSLContext._load_windows_store_certs fails with
  PermissionError.
- Issue #26673: When tk reports font size as 0, change to size 10.
  Such fonts on Linux prevented the configuration dialog from opening.
- Issue #27044: Add ConfigDialog.remove_var_callbacks to stop memory leaks.
- In the 'IDLE-console differences' section of the IDLE doc, clarify
  how running with IDLE affects sys.modules and the standard streams.
- Issue #25507: Fix incorrect change in IOBinding that prevented printing.
  Change also prevented saving shell window with non-ascii characters.
  Augment IOBinding htest to include all major IOBinding functions.
- Issue #25905: Revert unwanted conversion of ' to ’ RIGHT SINGLE QUOTATION
  MARK in README.txt and open this and NEWS.txt with 'ascii'.
  Re-encode CREDITS.txt to utf-8 and open it with 'utf-8'.
  * Rebuild to pick up the GNU triplet change on i386 archs. Closes: #826128.

python2.7 (2.7.11-10) unstable; urgency=medium

  * Update to 20160518 from the 2.7 branch.
- Issue #27039: Fixed bytearray.remove() for values greater than 127.
- Issue #14132: Fix urllib.request redirect handling when the target only
  has a query string.
- Removed the requirements for the ctypes and modulefinder modules to be
  compatible with earlier Python versions.
- Issue #22274: In the subprocess module, allow stderr to be redirected to
  stdout even when stdout is not redirected.
- Issue #12045: Avoid duplicate execution of command in
  ctypes.util._get_soname().
- Issue #26960: Backported #16270 from Python 3 to Python 2, to prevent
  urllib from hanging when retrieving certain FTP files.

python2.7 (2.7.11-9) unstable; urgency=medium

  * Update to 20160509 from the 2.7 branch.
- Issue #25745: Fixed leaking a userptr in curses panel destructor.
- Issue #17765: weakref.ref() no longer silently ignores keyword arguments.
- Issue #26873: xmlrpclib now raises ResponseError on unsupported type tags
  instead of silently return incorrect result.
- Issue #24114: Fix an uninitialized variable in `ctypes.util`.
- Issue #26864: In urllib, change the proxy bypass host checking against
  no_proxy to be case-insensitive, and to not match unrelated host names
  that happen to have a bypassed hostname as a suffix.
- Issue #26804: urllib will prefer lower_case proxy environment variables
  over UPPER_CASE or Mixed_Case ones.
- Issue #26837: assertSequenceEqual() now correctly outputs non-stringified
  differing items.  This affects assertListEqual() and assertTupleEq

[Touch-packages] [Bug 1571198] Re: Missing symlink in python2.7-dbg package

[Launchpad Bug Tracker]

This bug was fixed in the package python2.7 - 2.7.12-1~16.04

---
python2.7 (2.7.12-1~16.04) xenial-proposed; urgency=medium

  * SRU: LP: #1591895. Backport 2.7.12 to 16.04 LTS.

python2.7 (2.7.12-1) unstable; urgency=medium

  * Python 2.7.12 release.

python2.7 (2.7.12~rc1-2) unstable; urgency=medium

  * Extend debian/copyright to the files shipped in the wheel files.

python2.7 (2.7.12~rc1-1) unstable; urgency=medium

  * Python 2.7.12 release candidate 1.
- Issue #20041: Fixed TypeError when frame.f_trace is set to None.
- Issue #25702: A --with-lto configure option has been added that will
  enable link time optimizations at build time during a make profile-opt.
  Some compilers and toolchains are known to not produce stable code when
  using LTO, be sure to test things thoroughly before relying on it.
  It can provide a few % speed up over profile-opt alone.
- Issue #26556: Update expat to 2.1.1, fixes CVE-2015-1283.
- Fix TLS stripping vulnerability in smptlib, CVE-2016-0772.
- Issue #7356: ctypes.util: Make parsing of ldconfig output independent of
  the locale.
- Issue #25738: Stop BaseHTTPServer.BaseHTTPRequestHandler.send_error()
  from sending a message body for 205 Reset Content.  Also, don't send the
  Content-Type header field in responses that don't have a body.
- Issue #21313: Fix the "platform" module to tolerate when sys.version
  contains truncated build information.
- Issue #27211: Fix possible memory corruption in io.IOBase.readline().
- Issue #5124: Paste with text selected now replaces the selection on X11.
  This matches how paste works on Windows, Mac, most modern Linux apps,
  and ttk widgets.
- Issue #24759: Make clear in idlelib.idle_test.__init__ that the directory
  is a private implementation of test.test_idle and tool for maintainers.
- Issue #21916: Added tests for the turtle module.
- Issue #27229: Fix the cross-compiling pgen rule for in-tree builds.
- Issue #17500, and https://github.com/python/pythondotorg/issues/945: 
Remove
  unused and outdated icons.

python2.7 (2.7.11-11) unstable; urgency=medium

  * Update to 20160602 from the 2.7 branch.
- Issue #26168: Fixed possible refleaks in failing Py_BuildValue() with
  the "N" format unit.
- Issue #27114: Fix SSLContext._load_windows_store_certs fails with
  PermissionError.
- Issue #26673: When tk reports font size as 0, change to size 10.
  Such fonts on Linux prevented the configuration dialog from opening.
- Issue #27044: Add ConfigDialog.remove_var_callbacks to stop memory leaks.
- In the 'IDLE-console differences' section of the IDLE doc, clarify
  how running with IDLE affects sys.modules and the standard streams.
- Issue #25507: Fix incorrect change in IOBinding that prevented printing.
  Change also prevented saving shell window with non-ascii characters.
  Augment IOBinding htest to include all major IOBinding functions.
- Issue #25905: Revert unwanted conversion of ' to ’ RIGHT SINGLE QUOTATION
  MARK in README.txt and open this and NEWS.txt with 'ascii'.
  Re-encode CREDITS.txt to utf-8 and open it with 'utf-8'.
  * Rebuild to pick up the GNU triplet change on i386 archs. Closes: #826128.

python2.7 (2.7.11-10) unstable; urgency=medium

  * Update to 20160518 from the 2.7 branch.
- Issue #27039: Fixed bytearray.remove() for values greater than 127.
- Issue #14132: Fix urllib.request redirect handling when the target only
  has a query string.
- Removed the requirements for the ctypes and modulefinder modules to be
  compatible with earlier Python versions.
- Issue #22274: In the subprocess module, allow stderr to be redirected to
  stdout even when stdout is not redirected.
- Issue #12045: Avoid duplicate execution of command in
  ctypes.util._get_soname().
- Issue #26960: Backported #16270 from Python 3 to Python 2, to prevent
  urllib from hanging when retrieving certain FTP files.

python2.7 (2.7.11-9) unstable; urgency=medium

  * Update to 20160509 from the 2.7 branch.
- Issue #25745: Fixed leaking a userptr in curses panel destructor.
- Issue #17765: weakref.ref() no longer silently ignores keyword arguments.
- Issue #26873: xmlrpclib now raises ResponseError on unsupported type tags
  instead of silently return incorrect result.
- Issue #24114: Fix an uninitialized variable in `ctypes.util`.
- Issue #26864: In urllib, change the proxy bypass host checking against
  no_proxy to be case-insensitive, and to not match unrelated host names
  that happen to have a bypassed hostname as a suffix.
- Issue #26804: urllib will prefer lower_case proxy environment variables
  over UPPER_CASE or Mixed_Case ones.
- Issue #26837: assertSequenceEqual() now correctly outputs non-stringified
  differing items.  This affects assertListEqual() and assertTupleEq

[Touch-packages] [Bug 1578927] Re: idle crashes on configure through menu

[Launchpad Bug Tracker]

This bug was fixed in the package python2.7 - 2.7.12-1~16.04

---
python2.7 (2.7.12-1~16.04) xenial-proposed; urgency=medium

  * SRU: LP: #1591895. Backport 2.7.12 to 16.04 LTS.

python2.7 (2.7.12-1) unstable; urgency=medium

  * Python 2.7.12 release.

python2.7 (2.7.12~rc1-2) unstable; urgency=medium

  * Extend debian/copyright to the files shipped in the wheel files.

python2.7 (2.7.12~rc1-1) unstable; urgency=medium

  * Python 2.7.12 release candidate 1.
- Issue #20041: Fixed TypeError when frame.f_trace is set to None.
- Issue #25702: A --with-lto configure option has been added that will
  enable link time optimizations at build time during a make profile-opt.
  Some compilers and toolchains are known to not produce stable code when
  using LTO, be sure to test things thoroughly before relying on it.
  It can provide a few % speed up over profile-opt alone.
- Issue #26556: Update expat to 2.1.1, fixes CVE-2015-1283.
- Fix TLS stripping vulnerability in smptlib, CVE-2016-0772.
- Issue #7356: ctypes.util: Make parsing of ldconfig output independent of
  the locale.
- Issue #25738: Stop BaseHTTPServer.BaseHTTPRequestHandler.send_error()
  from sending a message body for 205 Reset Content.  Also, don't send the
  Content-Type header field in responses that don't have a body.
- Issue #21313: Fix the "platform" module to tolerate when sys.version
  contains truncated build information.
- Issue #27211: Fix possible memory corruption in io.IOBase.readline().
- Issue #5124: Paste with text selected now replaces the selection on X11.
  This matches how paste works on Windows, Mac, most modern Linux apps,
  and ttk widgets.
- Issue #24759: Make clear in idlelib.idle_test.__init__ that the directory
  is a private implementation of test.test_idle and tool for maintainers.
- Issue #21916: Added tests for the turtle module.
- Issue #27229: Fix the cross-compiling pgen rule for in-tree builds.
- Issue #17500, and https://github.com/python/pythondotorg/issues/945: 
Remove
  unused and outdated icons.

python2.7 (2.7.11-11) unstable; urgency=medium

  * Update to 20160602 from the 2.7 branch.
- Issue #26168: Fixed possible refleaks in failing Py_BuildValue() with
  the "N" format unit.
- Issue #27114: Fix SSLContext._load_windows_store_certs fails with
  PermissionError.
- Issue #26673: When tk reports font size as 0, change to size 10.
  Such fonts on Linux prevented the configuration dialog from opening.
- Issue #27044: Add ConfigDialog.remove_var_callbacks to stop memory leaks.
- In the 'IDLE-console differences' section of the IDLE doc, clarify
  how running with IDLE affects sys.modules and the standard streams.
- Issue #25507: Fix incorrect change in IOBinding that prevented printing.
  Change also prevented saving shell window with non-ascii characters.
  Augment IOBinding htest to include all major IOBinding functions.
- Issue #25905: Revert unwanted conversion of ' to ’ RIGHT SINGLE QUOTATION
  MARK in README.txt and open this and NEWS.txt with 'ascii'.
  Re-encode CREDITS.txt to utf-8 and open it with 'utf-8'.
  * Rebuild to pick up the GNU triplet change on i386 archs. Closes: #826128.

python2.7 (2.7.11-10) unstable; urgency=medium

  * Update to 20160518 from the 2.7 branch.
- Issue #27039: Fixed bytearray.remove() for values greater than 127.
- Issue #14132: Fix urllib.request redirect handling when the target only
  has a query string.
- Removed the requirements for the ctypes and modulefinder modules to be
  compatible with earlier Python versions.
- Issue #22274: In the subprocess module, allow stderr to be redirected to
  stdout even when stdout is not redirected.
- Issue #12045: Avoid duplicate execution of command in
  ctypes.util._get_soname().
- Issue #26960: Backported #16270 from Python 3 to Python 2, to prevent
  urllib from hanging when retrieving certain FTP files.

python2.7 (2.7.11-9) unstable; urgency=medium

  * Update to 20160509 from the 2.7 branch.
- Issue #25745: Fixed leaking a userptr in curses panel destructor.
- Issue #17765: weakref.ref() no longer silently ignores keyword arguments.
- Issue #26873: xmlrpclib now raises ResponseError on unsupported type tags
  instead of silently return incorrect result.
- Issue #24114: Fix an uninitialized variable in `ctypes.util`.
- Issue #26864: In urllib, change the proxy bypass host checking against
  no_proxy to be case-insensitive, and to not match unrelated host names
  that happen to have a bypassed hostname as a suffix.
- Issue #26804: urllib will prefer lower_case proxy environment variables
  over UPPER_CASE or Mixed_Case ones.
- Issue #26837: assertSequenceEqual() now correctly outputs non-stringified
  differing items.  This affects assertListEqual() and assertTupleEq

[Touch-packages] [Bug 1588123] Update Released

[Martin Pitt]

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

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

Title:
  binutils - Bugzilla ID 20159

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

Bug description:
  Moved to Ubuntu 16.04 from Ubuntu 14.04 and was doing some Test Driven
  Development where we began to override the "time" system call from
  glibc. Failed on Ubuntu 16.04 and I filed a report with the binutils
  Bugzilla.

  https://sourceware.org/bugzilla/show_bug.cgi?id=20159

  (Turns out it was not dynamic linking that was the problem but GNU ld
  itself at link-time.)

  They have since developed a patch and I want to get this into the
  binutils 1.26 line that is maintained for 16.04 so we can continue to
  properly develop software on this distribution.

  Thanks!

  - Paul Braman

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

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

[Touch-packages] [Bug 1586673] Update Released

[Martin Pitt]

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

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

Title:
  Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS

Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-5-cross package in Ubuntu:
  Fix Released
Status in gcc-5-cross-ports package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Released
Status in gcc-5 source package in Xenial:
  Fix Released
Status in gcc-5-cross source package in Xenial:
  Fix Committed
Status in gcc-5-cross-ports source package in Xenial:
  Fix Committed

Bug description:
  Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS.  16.04 LTS ships
  binutils and gcc-5 versions taken from the release branches, which saw
  more regression fixes and support for new hardware until the 5.4.0 and
  2.26.1 point releases. The idea is to include these final point
  releases into 16.04.1 LTS, with test rebuilds done for all packages,
  and regression checks for seeded packages.

  Acceptance criteria should be no regressions for the seeded packages,
  plus a best effort for unseeded packages.  During the analysis of the
  build failures, one gcc regression (libstdc++ header reorg) was found
  and reverted, and validated, that these build failures are fixed (plus
  affected seeded packages were uploaded to xenial-proposed anyway).

  reference test rebuild:
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-baseline-xenial.html

  test rebuild (xenial-release):
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-xenial.html

  test rebuild (xenial-updates):
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-updates-xenial.html

  The test rebuild was done using packages from the ubuntu-
  toolchain-r/ppa.

  Attached is an analysis of the build failures, and whether they are
  regressions, or already are present in the xenial release.

  main component
  ==

  bzr
LP: #1592731, fixed in -proposed
  ecj
LP: #1592801, fixed in -updates
  freerdp
not a regression
  gcc-5-cross
needs update after gcc-5 acceptance
  gnutls28
LP: #1592693, fixed in -updates
  kmod
unrelated, tracked in LP: #1592722
  libnih
not a regression
  llvm-toolchain-3.6
not a regression
  migrate
unrelated (mysql-5.7), tracked in LP: #1592663
  neon27 (s390x)
unrelated, traked in LP: #1592698
  openvswitch
not a regression, tracked in LP: #1592793
  python-pymysql
unrelated (mysql-5.7), tracked in LP: #1592664
  python-tooz
unrelated, tracked in LP: #1592660
  sbsigntool
not a regression
  shim
not a regression
  strongswan
racy test, unrelated, tracked in LP: #1592706
  ubuntu-defaults-builder
unrelated, LP: #1597370, waiting for approval
  upstart
not a regression
  whoopsie
LP: #1592649, fixed in -updates
  yaboot
not a regression

  bzr package set
  ===

  bzr-builder
  bzr-upload
no regressions

  cli-mono package set
  

  gbrainy
  ikvm
  monodevelop
  tangerine
no regressions

  desktop-extra package set
  =

  java-gnome
not a regressions

  edubuntu package set
  

  atomix
  gbrainy
no regressions

  input-methods package set
  =

  fcitx-table-other
  libkkc
no regressions

  kubuntu package set (minus packages from main)
  ==

  avogadro
not a regression
  eigen2
not a regression
  fam
not a regression
  farstream-0.2
not a regression
  gst-plugins-base0.10
not a regression
  gst-plugins-good0.10
not a regression
  gstreamer0.10
not a regression
  kqoauth
not a regression
  kubuntu-web-shortcuts
not a regression
  libmpc
not a regression
  libmygpo-qt
not a regression
  libspe2
not a regression
  networkmanager-qt
obsoleted by version in -updates
  plotutils
not a regression
  qtcurve
not a regression
  tbb
not a regression
  telepathy-haze
not a regression
  telepathy-qt
not a regression

  
  lubuntu package set
  

  hardinfo
 

[Touch-packages] [Bug 1588123] Re: binutils - Bugzilla ID 20159

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.26.1-1ubuntu1~16.04

---
binutils (2.26.1-1ubuntu1~16.04) xenial-proposed; urgency=medium

  * SRU: LP: #1586673, backport to 16.04 LTS.
- Supports new POWER9 instructions. LP: #1588475.
  * Disable N32 and MIPS r6 cross builds.

binutils (2.26.1-1ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26.1-1) unstable; urgency=medium

  * binutils 2.26.1 release.

binutils (2.26-12ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26-12) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160624.
- Fix PR ld/20254 (AVR), PR ld/20221 (AVR), PR ld/20244 (x86).
- Support for three more new POWER9 instructions.
  * Cherry pick backports for AArch64 vulcan support (Dann Frazier).
LP: #1594452.

binutils (2.26-11ubuntu2) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26-11) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160610.
- Fix PR ld/20159, reverting the change for PR ld/16467. LP: #1588123.
  * Use ldconfig triggers instead of calling ldconfig directly.

binutils (2.26-10ubuntu3) yakkety; urgency=medium

  * Fix PR ld/20159, reverting the change for PR ld/16467.

binutils (2.26-10ubuntu2) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26-10) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160601.
- Fix PR ld/20117, PR ld/20030, PR ld/20093.
- Support for a few more new POWER9 instructions.
  * Build for N32 and MIPS r6 (YunQiang Su). Closes: #807377.
  * Mark cross binutils as M-A: foreign (Helmut Grohne). Closes: #824424.
  * More reproducible build fixes (Chris Lamb). Closes: #824413.
  * Fix PR ld/19886, --as-needed regression, taken from the trunk.

binutils (2.26-9ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.
- Fix PR ld/19886, --as-needed regression, taken from the trunk.

binutils (2.26-9) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160512.
- Fix PR ld/19878, PR ld/19827, PR gas/19909, PR ld/20006, PR gold/19047,
  PR gas/20047,  PR 20060.

 -- Matthias Klose   Thu, 30 Jun 2016 11:14:03 +0200

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

Title:
  binutils - Bugzilla ID 20159

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

Bug description:
  Moved to Ubuntu 16.04 from Ubuntu 14.04 and was doing some Test Driven
  Development where we began to override the "time" system call from
  glibc. Failed on Ubuntu 16.04 and I filed a report with the binutils
  Bugzilla.

  https://sourceware.org/bugzilla/show_bug.cgi?id=20159

  (Turns out it was not dynamic linking that was the problem but GNU ld
  itself at link-time.)

  They have since developed a patch and I want to get this into the
  binutils 1.26 line that is maintained for 16.04 so we can continue to
  properly develop software on this distribution.

  Thanks!

  - Paul Braman

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

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

[Touch-packages] [Bug 1586673] Re: Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS

[Launchpad Bug Tracker]

This bug was fixed in the package gcc-5 - 5.4.0-6ubuntu1~16.04.1

---
gcc-5 (5.4.0-6ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * SRU: LP: #1586673. Backport GCC 5.4 to 16.04 LTS.
  * Revert a libstdc++ header reorg done after the 5.3.0 release.
  * Add AArch64 Vulcan cpu support, backport from trunk. LP: #1594452.
  * Revert a libstdc++ header reorg done after the 5.3.0 release (only for
OS releases including a GCC 5 at release time).
  * Fixes C++ ICE. LP: #1593608.

gcc-5 (5.4.0-6ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-5 (5.4.0-6) unstable; urgency=medium

  * Fix gdc cross build.
  * Disable the AArch64 Vulcan cpu support for FSF builds, needs a proper
back port.

gcc-5 (5.4.0-5ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-5 (5.4.0-5) unstable; urgency=medium

  [ Matthias Klose ]
  * Add AArch64 Vulcan cpu support, backport from trunk. LP: #1594452.
  * Revert a libstdc++ header reorg done after the 5.3.0 release (only for
OS releases including a GCC 5 at release time).
  * Enforce build using binutils 2.26.1 for unstable/development series.
  * Mark cross compilers as M-A: foreign. Addresses: #827136.
  * Remove the MIPS r6 support again, dak doesn't like unknown architectures.

  [ Aurelien Jarno ]
  * Drop support for loongson 2f (YunQiang Su). Closes: #827554.
  * Apply proposed patch from Matthew Fortune to fix libjava on mips64el.

gcc-5 (5.4.0-4ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-5 (5.4.0-4) unstable; urgency=medium

  * gdc: Fix linking the runtime library. Closes: #826645.
  * gdc: Fix updates from 5.3.x. Closes: #826583.
  * Update the Linaro support to the 5-2016.06 snapshot.
  * Add MIPS r6 support and bump mipsn32(el) ISA to r2 (YunQiang Su).
Closes: #824986.
  * Avoid storing -fdebug-prefix-map in DW_AT_producer (for better
reproducibility). Taken from the trunk (Daniel Kahn Gillmor).
Closes: #819176.

gcc-5 (5.4.0-3ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-5 (5.4.0-3) unstable; urgency=medium

  * Update Ada patch for KFreeBSD (Steven Chamberlain). Closes: #826332.

gcc-5 (5.4.0-2) unstable; urgency=medium

  * Fix gdc packaging for architectures without libphobos support.

gcc-5 (5.4.0-1) unstable; urgency=medium

  * GCC 5.4.0 release.
- Fix PR target/68696 (AArch64), PR fortran/70350.
  * Update embedded timestamp setting patch, backported from the trunk.
  * Update the Linaro support to the 5-2016.05 snapshot.
  * Update gdc to the gcc-5 branch 20160603.

gcc-5 (5.3.1-21ubuntu11) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-5 (5.3.1-21) unstable; urgency=medium

  * GCC 5.4.0 release candidate 1.
  * Update to SVN 20160528 (r236840, 5.3.1) from the gcc-5-branch.
- Fix PR libstdc++/69703, PR libstdc++/71038, PR libstdc++/71036,
  PR libstdc++/71037, PR libstdc++/71005, PR libstdc++/71004,
  PR libstdc++/70609, PR target/69634, PR middle-end/68142,
  PR middle-end/69845, PR rtl-optimization/68814, PR lto/69003,
  PR ipa/66487, PR target/69252, PR target/67973 (x86),
  PR middle-end/67278, PR target/67278 (x86), PR tree-optimization/69720,
  PR tree-optimization/67921, PR middle-end/70941, PR middle-end/70931,
  PR tree-optimization/70623, PR tree-optimization/70780, PR c++/70347,
  PR c++/70466, PR fortran/71204, PR fortran/69603, PR libffi/65567,
  PR libstdc++/70762.
  * Update the ibm branch to 20160526.

gcc-5 (5.3.1-20ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-5 (5.3.1-20) unstable; urgency=medium

  * Update to SVN 20160519 (r236482, 5.3.1) from the gcc-5-branch.
- Fix PR sanitizer/71160, PR other/61321, PR other/61233, PR c++/70498,
  PR c++/69687, PR c++/70492, PR c++/67394, PR c++/70481, PR target/71161,
  PR ipa/70646, PR tree-optimization/69400, PR target/71145 (alpha),
  PR c++/70353, PR target/70809 (AArch64), PR c++/70613,
  PR target/70963 (PPC), PR c++/70505, PR c++/70494, PR c++/70648,
  PR c++/70353, PR c++/70095, PR c++/70135, PR fortran/69603.

gcc-5 (5.3.1-19ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-5 (5.3.1-19) unstable; urgency=medium

  * Fix dependency resolution for libraries not built anymore from
this source package.

gcc-5 (5.3.1-18) unstable; urgency=medium

  * Update to SVN 20160509 (r236033, 5.3.1) from the gcc-5-branch.
- Fix PR tree-optimization/70526, PR c++/70635, PR ada/70969,
  PR libgfortran/70684, PR target/60290 (Solaris).
  * Call dh_makeshlibs with the --noscripts option when building a
cross compiler.
  * Fix buildi

[Touch-packages] [Bug 1586673] Re: Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.26.1-1ubuntu1~16.04

---
binutils (2.26.1-1ubuntu1~16.04) xenial-proposed; urgency=medium

  * SRU: LP: #1586673, backport to 16.04 LTS.
- Supports new POWER9 instructions. LP: #1588475.
  * Disable N32 and MIPS r6 cross builds.

binutils (2.26.1-1ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26.1-1) unstable; urgency=medium

  * binutils 2.26.1 release.

binutils (2.26-12ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26-12) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160624.
- Fix PR ld/20254 (AVR), PR ld/20221 (AVR), PR ld/20244 (x86).
- Support for three more new POWER9 instructions.
  * Cherry pick backports for AArch64 vulcan support (Dann Frazier).
LP: #1594452.

binutils (2.26-11ubuntu2) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26-11) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160610.
- Fix PR ld/20159, reverting the change for PR ld/16467. LP: #1588123.
  * Use ldconfig triggers instead of calling ldconfig directly.

binutils (2.26-10ubuntu3) yakkety; urgency=medium

  * Fix PR ld/20159, reverting the change for PR ld/16467.

binutils (2.26-10ubuntu2) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26-10) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160601.
- Fix PR ld/20117, PR ld/20030, PR ld/20093.
- Support for a few more new POWER9 instructions.
  * Build for N32 and MIPS r6 (YunQiang Su). Closes: #807377.
  * Mark cross binutils as M-A: foreign (Helmut Grohne). Closes: #824424.
  * More reproducible build fixes (Chris Lamb). Closes: #824413.
  * Fix PR ld/19886, --as-needed regression, taken from the trunk.

binutils (2.26-9ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.
- Fix PR ld/19886, --as-needed regression, taken from the trunk.

binutils (2.26-9) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160512.
- Fix PR ld/19878, PR ld/19827, PR gas/19909, PR ld/20006, PR gold/19047,
  PR gas/20047,  PR 20060.

 -- Matthias Klose   Thu, 30 Jun 2016 11:14:03 +0200

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

Title:
  Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS

Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-5-cross package in Ubuntu:
  Fix Released
Status in gcc-5-cross-ports package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Released
Status in gcc-5 source package in Xenial:
  Fix Released
Status in gcc-5-cross source package in Xenial:
  Fix Committed
Status in gcc-5-cross-ports source package in Xenial:
  Fix Committed

Bug description:
  Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS.  16.04 LTS ships
  binutils and gcc-5 versions taken from the release branches, which saw
  more regression fixes and support for new hardware until the 5.4.0 and
  2.26.1 point releases. The idea is to include these final point
  releases into 16.04.1 LTS, with test rebuilds done for all packages,
  and regression checks for seeded packages.

  Acceptance criteria should be no regressions for the seeded packages,
  plus a best effort for unseeded packages.  During the analysis of the
  build failures, one gcc regression (libstdc++ header reorg) was found
  and reverted, and validated, that these build failures are fixed (plus
  affected seeded packages were uploaded to xenial-proposed anyway).

  reference test rebuild:
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-baseline-xenial.html

  test rebuild (xenial-release):
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-xenial.html

  test rebuild (xenial-updates):
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-updates-xenial.html

  The test rebuild was done using packages from the ubuntu-
  toolchain-r/ppa.

  Attached is an analysis of the build failures, and whether they are
  regressions, or already are present in the xenial release.

  main c

[Touch-packages] [Bug 1588475] Update Released

[Martin Pitt]

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

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

Title:
  Pull latest binutils POWER9 support commit that adds support for 3 new
  instructions

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

Bug description:
  Two new ISA 3.0 RFCs have been created that add 3 new instructions
  that will be present in POWER9.  Binutils support for these new
  instructions have been committed to the binutils trunk and 2.26
  release branches with the commits below.  We would like this change to
  be picked up for the next release/update.

  
  binutils trunk:

  commit 19dfcc89e8d94526f011242041b700ede8834996
  Author: Peter Bergner 
  Date:   Thu May 26 19:06:51 2016 -0500

  Add support for new POWER ISA 3.0 instructions.
  
  opcodes/
  
  * ppc-opc.c (CY): New define.  Document it.
  (powerpc_opcodes) : New mnemonics.
  
  gas/
  * testsuite/gas/ppc/altivec3.d : Add test.
  * testsuite/gas/ppc/altivec3.s: Likewise.
  * testsuite/gas/ppc/power9.d : Add tests.
  * testsuite/gas/ppc/power9.s: Likewise.

  binutils 2.26:

  commit 8bfb4f2639cc2a4b5bc6862adbdd3e948e61ace2
  Author: Peter Bergner 
  Date:   Wed Jun 1 09:48:03 2016 -0500

  Add support for new POWER ISA 3.0 instructions.
  
  opcodes/
  
  Backport from master
  2016-05-26  Peter Bergner 
  
  * ppc-opc.c (CY): New define.  Document it.
  (powerpc_opcodes) : New mnemonics.
  
  gas/
  Backport from master
  2016-05-26  Peter Bergner 
  
  * testsuite/gas/ppc/altivec3.d : Add test.
  * testsuite/gas/ppc/altivec3.s: Likewise.
  * testsuite/gas/ppc/power9.d : Add tests.
  * testsuite/gas/ppc/power9.s: Likewise.

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

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

[Touch-packages] [Bug 1588475] Re: Pull latest binutils POWER9 support commit that adds support for 3 new instructions

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.26.1-1ubuntu1~16.04

---
binutils (2.26.1-1ubuntu1~16.04) xenial-proposed; urgency=medium

  * SRU: LP: #1586673, backport to 16.04 LTS.
- Supports new POWER9 instructions. LP: #1588475.
  * Disable N32 and MIPS r6 cross builds.

binutils (2.26.1-1ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26.1-1) unstable; urgency=medium

  * binutils 2.26.1 release.

binutils (2.26-12ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26-12) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160624.
- Fix PR ld/20254 (AVR), PR ld/20221 (AVR), PR ld/20244 (x86).
- Support for three more new POWER9 instructions.
  * Cherry pick backports for AArch64 vulcan support (Dann Frazier).
LP: #1594452.

binutils (2.26-11ubuntu2) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26-11) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160610.
- Fix PR ld/20159, reverting the change for PR ld/16467. LP: #1588123.
  * Use ldconfig triggers instead of calling ldconfig directly.

binutils (2.26-10ubuntu3) yakkety; urgency=medium

  * Fix PR ld/20159, reverting the change for PR ld/16467.

binutils (2.26-10ubuntu2) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26-10) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160601.
- Fix PR ld/20117, PR ld/20030, PR ld/20093.
- Support for a few more new POWER9 instructions.
  * Build for N32 and MIPS r6 (YunQiang Su). Closes: #807377.
  * Mark cross binutils as M-A: foreign (Helmut Grohne). Closes: #824424.
  * More reproducible build fixes (Chris Lamb). Closes: #824413.
  * Fix PR ld/19886, --as-needed regression, taken from the trunk.

binutils (2.26-9ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.
- Fix PR ld/19886, --as-needed regression, taken from the trunk.

binutils (2.26-9) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160512.
- Fix PR ld/19878, PR ld/19827, PR gas/19909, PR ld/20006, PR gold/19047,
  PR gas/20047,  PR 20060.

 -- Matthias Klose   Thu, 30 Jun 2016 11:14:03 +0200

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

Title:
  Pull latest binutils POWER9 support commit that adds support for 3 new
  instructions

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

Bug description:
  Two new ISA 3.0 RFCs have been created that add 3 new instructions
  that will be present in POWER9.  Binutils support for these new
  instructions have been committed to the binutils trunk and 2.26
  release branches with the commits below.  We would like this change to
  be picked up for the next release/update.

  
  binutils trunk:

  commit 19dfcc89e8d94526f011242041b700ede8834996
  Author: Peter Bergner 
  Date:   Thu May 26 19:06:51 2016 -0500

  Add support for new POWER ISA 3.0 instructions.
  
  opcodes/
  
  * ppc-opc.c (CY): New define.  Document it.
  (powerpc_opcodes) : New mnemonics.
  
  gas/
  * testsuite/gas/ppc/altivec3.d : Add test.
  * testsuite/gas/ppc/altivec3.s: Likewise.
  * testsuite/gas/ppc/power9.d : Add tests.
  * testsuite/gas/ppc/power9.s: Likewise.

  binutils 2.26:

  commit 8bfb4f2639cc2a4b5bc6862adbdd3e948e61ace2
  Author: Peter Bergner 
  Date:   Wed Jun 1 09:48:03 2016 -0500

  Add support for new POWER ISA 3.0 instructions.
  
  opcodes/
  
  Backport from master
  2016-05-26  Peter Bergner 
  
  * ppc-opc.c (CY): New define.  Document it.
  (powerpc_opcodes) : New mnemonics.
  
  gas/
  Backport from master
  2016-05-26  Peter Bergner 
  
  * testsuite/gas/ppc/altivec3.d : Add test.
  * testsuite/gas/ppc/altivec3.s: Likewise.
  * testsuite/gas/ppc/power9.d : Add tests.
  * testsuite/gas/ppc/power9.s: Likewise.

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

-- 
Mailing 

[Touch-packages] [Bug 1594452] Re: Add vulcan support

[Launchpad Bug Tracker]

This bug was fixed in the package gcc-5 - 5.4.0-6ubuntu1~16.04.1

---
gcc-5 (5.4.0-6ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * SRU: LP: #1586673. Backport GCC 5.4 to 16.04 LTS.
  * Revert a libstdc++ header reorg done after the 5.3.0 release.
  * Add AArch64 Vulcan cpu support, backport from trunk. LP: #1594452.
  * Revert a libstdc++ header reorg done after the 5.3.0 release (only for
OS releases including a GCC 5 at release time).
  * Fixes C++ ICE. LP: #1593608.

gcc-5 (5.4.0-6ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-5 (5.4.0-6) unstable; urgency=medium

  * Fix gdc cross build.
  * Disable the AArch64 Vulcan cpu support for FSF builds, needs a proper
back port.

gcc-5 (5.4.0-5ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-5 (5.4.0-5) unstable; urgency=medium

  [ Matthias Klose ]
  * Add AArch64 Vulcan cpu support, backport from trunk. LP: #1594452.
  * Revert a libstdc++ header reorg done after the 5.3.0 release (only for
OS releases including a GCC 5 at release time).
  * Enforce build using binutils 2.26.1 for unstable/development series.
  * Mark cross compilers as M-A: foreign. Addresses: #827136.
  * Remove the MIPS r6 support again, dak doesn't like unknown architectures.

  [ Aurelien Jarno ]
  * Drop support for loongson 2f (YunQiang Su). Closes: #827554.
  * Apply proposed patch from Matthew Fortune to fix libjava on mips64el.

gcc-5 (5.4.0-4ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-5 (5.4.0-4) unstable; urgency=medium

  * gdc: Fix linking the runtime library. Closes: #826645.
  * gdc: Fix updates from 5.3.x. Closes: #826583.
  * Update the Linaro support to the 5-2016.06 snapshot.
  * Add MIPS r6 support and bump mipsn32(el) ISA to r2 (YunQiang Su).
Closes: #824986.
  * Avoid storing -fdebug-prefix-map in DW_AT_producer (for better
reproducibility). Taken from the trunk (Daniel Kahn Gillmor).
Closes: #819176.

gcc-5 (5.4.0-3ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-5 (5.4.0-3) unstable; urgency=medium

  * Update Ada patch for KFreeBSD (Steven Chamberlain). Closes: #826332.

gcc-5 (5.4.0-2) unstable; urgency=medium

  * Fix gdc packaging for architectures without libphobos support.

gcc-5 (5.4.0-1) unstable; urgency=medium

  * GCC 5.4.0 release.
- Fix PR target/68696 (AArch64), PR fortran/70350.
  * Update embedded timestamp setting patch, backported from the trunk.
  * Update the Linaro support to the 5-2016.05 snapshot.
  * Update gdc to the gcc-5 branch 20160603.

gcc-5 (5.3.1-21ubuntu11) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-5 (5.3.1-21) unstable; urgency=medium

  * GCC 5.4.0 release candidate 1.
  * Update to SVN 20160528 (r236840, 5.3.1) from the gcc-5-branch.
- Fix PR libstdc++/69703, PR libstdc++/71038, PR libstdc++/71036,
  PR libstdc++/71037, PR libstdc++/71005, PR libstdc++/71004,
  PR libstdc++/70609, PR target/69634, PR middle-end/68142,
  PR middle-end/69845, PR rtl-optimization/68814, PR lto/69003,
  PR ipa/66487, PR target/69252, PR target/67973 (x86),
  PR middle-end/67278, PR target/67278 (x86), PR tree-optimization/69720,
  PR tree-optimization/67921, PR middle-end/70941, PR middle-end/70931,
  PR tree-optimization/70623, PR tree-optimization/70780, PR c++/70347,
  PR c++/70466, PR fortran/71204, PR fortran/69603, PR libffi/65567,
  PR libstdc++/70762.
  * Update the ibm branch to 20160526.

gcc-5 (5.3.1-20ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-5 (5.3.1-20) unstable; urgency=medium

  * Update to SVN 20160519 (r236482, 5.3.1) from the gcc-5-branch.
- Fix PR sanitizer/71160, PR other/61321, PR other/61233, PR c++/70498,
  PR c++/69687, PR c++/70492, PR c++/67394, PR c++/70481, PR target/71161,
  PR ipa/70646, PR tree-optimization/69400, PR target/71145 (alpha),
  PR c++/70353, PR target/70809 (AArch64), PR c++/70613,
  PR target/70963 (PPC), PR c++/70505, PR c++/70494, PR c++/70648,
  PR c++/70353, PR c++/70095, PR c++/70135, PR fortran/69603.

gcc-5 (5.3.1-19ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-5 (5.3.1-19) unstable; urgency=medium

  * Fix dependency resolution for libraries not built anymore from
this source package.

gcc-5 (5.3.1-18) unstable; urgency=medium

  * Update to SVN 20160509 (r236033, 5.3.1) from the gcc-5-branch.
- Fix PR tree-optimization/70526, PR c++/70635, PR ada/70969,
  PR libgfortran/70684, PR target/60290 (Solaris).
  * Call dh_makeshlibs with the --noscripts option when building a
cross compiler.
  * Fix buildi

[Touch-packages] [Bug 1594452] Re: Add vulcan support

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.26.1-1ubuntu1~16.04

---
binutils (2.26.1-1ubuntu1~16.04) xenial-proposed; urgency=medium

  * SRU: LP: #1586673, backport to 16.04 LTS.
- Supports new POWER9 instructions. LP: #1588475.
  * Disable N32 and MIPS r6 cross builds.

binutils (2.26.1-1ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26.1-1) unstable; urgency=medium

  * binutils 2.26.1 release.

binutils (2.26-12ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26-12) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160624.
- Fix PR ld/20254 (AVR), PR ld/20221 (AVR), PR ld/20244 (x86).
- Support for three more new POWER9 instructions.
  * Cherry pick backports for AArch64 vulcan support (Dann Frazier).
LP: #1594452.

binutils (2.26-11ubuntu2) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26-11) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160610.
- Fix PR ld/20159, reverting the change for PR ld/16467. LP: #1588123.
  * Use ldconfig triggers instead of calling ldconfig directly.

binutils (2.26-10ubuntu3) yakkety; urgency=medium

  * Fix PR ld/20159, reverting the change for PR ld/16467.

binutils (2.26-10ubuntu2) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.

binutils (2.26-10) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160601.
- Fix PR ld/20117, PR ld/20030, PR ld/20093.
- Support for a few more new POWER9 instructions.
  * Build for N32 and MIPS r6 (YunQiang Su). Closes: #807377.
  * Mark cross binutils as M-A: foreign (Helmut Grohne). Closes: #824424.
  * More reproducible build fixes (Chris Lamb). Closes: #824413.
  * Fix PR ld/19886, --as-needed regression, taken from the trunk.

binutils (2.26-9ubuntu1) yakkety; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't build cross binutils packages for non-linux architectures.
- Fix PR ld/19886, --as-needed regression, taken from the trunk.

binutils (2.26-9) unstable; urgency=medium

  * Update, taken from the 2.26 branch 20160512.
- Fix PR ld/19878, PR ld/19827, PR gas/19909, PR ld/20006, PR gold/19047,
  PR gas/20047,  PR 20060.

 -- Matthias Klose   Thu, 30 Jun 2016 11:14:03 +0200

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

Title:
  Add vulcan support

Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-6 package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Released
Status in gcc-5 source package in Xenial:
  Fix Released

Bug description:
  Vulcan support has recently landed upstream. Please include this
  backport in Ubuntu.

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

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

[Touch-packages] [Bug 1594452] Update Released

[Martin Pitt]

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

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

Title:
  Add vulcan support

Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-6 package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Released
Status in gcc-5 source package in Xenial:
  Fix Released

Bug description:
  Vulcan support has recently landed upstream. Please include this
  backport in Ubuntu.

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

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

[Touch-packages] [Bug 960157] Update Released

[Martin Pitt]

The verification of the Stable Release Update for lightdm 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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/960157

Title:
  lightdm exits on SIGHUP

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Released
Status in lightdm source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  LightDM quits when it receives SIGUSR1, SIGUSR2 or SIGHUP. But convention 
these signals should not quit a service (they should get it to dump state, 
reload configuration etc).

  [Test Case]
  1. Start lightdm
  2. sudo killall -SIGHUP lightdm

  Expected result:
  Nothing happens

  Observed result:
  LightDM restarts

  [Regression Potential]
  Low. We now just quit only on SIGTERM and SIGINT.

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

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

[Touch-packages] [Bug 1578927] Update Released

[Martin Pitt]

The verification of the Stable Release Update for python2.7 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 python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1578927

Title:
  idle crashes on configure through menu

Status in Python:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Committed

Bug description:
  IDLE crashes when "Configure IDLE" is selected through "Options".
  Terminal output is as follows:

  Exception in Tkinter callback
  Traceback (most recent call last):
File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1540, in __call__
  return self.func(*args)
File "/usr/lib/python2.7/idlelib/EditorWindow.py", line 543, in 
config_dialog
  configDialog.ConfigDialog(self.top,'Settings')
File "/usr/lib/python2.7/idlelib/configDialog.py", line 72, in __init__
  self.LoadConfigs()
File "/usr/lib/python2.7/idlelib/configDialog.py", line 1103, in LoadConfigs
  self.LoadFontCfg()
File "/usr/lib/python2.7/idlelib/configDialog.py", line 1005, in LoadFontCfg
  self.SetFontSample()
File "/usr/lib/python2.7/idlelib/configDialog.py", line 883, in 
SetFontSample
  self.labelFontSample.config(font=newFont)
File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1329, in configure
  return self._configure('configure', cnf, kw)
File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1320, in _configure
  self.tk.call(_flatten((self._w, cmd)) + self._options(cnf))
  TclError: expected integer but got ""

  1) Ubuntu 16.04 LTS
  2) Package idle 2.7.11-1
  3) Expected Options Menu
  4) Instead nothing happened.

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

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

[Touch-packages] [Bug 1581853] Update Released

[Martin Pitt]

The verification of the Stable Release Update for lightdm 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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1581853

Title:
  Source prefs.sh as privileged user to allow user mods

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

Bug description:
  [Impact] including [Test Case]

  The Ask Ubuntu question  called my
  attention to a regression in 16.04 as regards the possibilities for
  the system owner to configure the guest account. Up to 15.10 you can
  put e.g. this line in /etc/guest-session/prefs.sh:

  adduser $USER somegroup

  But if you try that in 16.04, the guest session won't launch. The
  explanation is that after the reorganization of the guest session code
  in 16.04, prefs.sh is sourced by /usr/share/lightdm/guest-
  session/setup.sh, which is not run as root.

  The linked merge proposals restore the previous behavior by letting
  prefs.sh be sourced by /usr/sbin/guest-account again.

  [Regression Potential]

  Low.

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

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

[Touch-packages] [Bug 1581065] Re: incorrect parsing of != dependency versions

[Launchpad Bug Tracker]

This bug was fixed in the package dh-python - 2.20150826ubuntu1.1

---
dh-python (2.20150826ubuntu1.1) wily; urgency=medium

  * dhpython/pydist.py: Ensure that != dependency versions are ignored
(LP: #1581065).

 -- Corey Bryant   Mon, 20 Jun 2016 11:01:05
-0400

** Changed in: dh-python (Ubuntu Wily)
   Status: Fix Committed => Fix Released

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

Title:
  incorrect parsing of != dependency versions

Status in dh-python package in Ubuntu:
  Fix Released
Status in dh-python source package in Wily:
  Fix Released
Status in dh-python source package in Xenial:
  Fix Released
Status in dh-python source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  dh-python incorrectly used != version operators in some cases, resulting in 
failed package builds; this impacts a number of stable updates for Xenial which 
blacklist a specific cryptography version.

  [Test Case]
  Build stable release of glance/keystone/nova for xenial/mitaka (parse problem 
in original bug report)

  [Regression Potential]
  Testing OK in yakkety; change is minimal and ensures != operator is ignored 
when detected.

  [Original Bug Report]
  Some updates to requirements for openstack projects (glance and keystone 
specifically) is causing dh-python to incorrectly generate a != version 
dependency; this is the requires.txt entry:

   cryptography!=1.3.0,>=1.0

  which causes (utimately):

  dpkg-gencontrol: warning: can't parse dependency python-cryptography
  (!= 1.3.0)

  from the generated dependency line:

  "python-castellan, python-crypto (>= 2.6), python-cryptography (!=
  1.3.0), python-debtcollector, python-eventlet, python-futurist,
  python-glance-store, python-httplib2, python-iso8601, python-
  jsonschema, python-keystoneauth1, python-keystoneclient, python-
  keystonemiddleware, python-migrate, python-monotonic, python-openssl,
  python-oslo.concurrency, python-oslo.config, python-oslo.context,
  python-oslo.db, python-oslo.i18n, python-oslo.log, python-
  oslo.messaging, python-oslo.middleware, python-oslo.policy, python-
  oslo.serialization, python-oslo.service, python-oslo.utils, python-
  osprofiler, python-paste, python-pastedeploy, python-pbr, python-
  prettytable, python-retrying, python-semantic-version, python-six (>=
  1.9.0), python-sqlalchemy (>= 1.0~), python-sqlalchemy (<< 1.1),
  python-stevedore, python-taskflow, python-webob, python-wsme,
  python:any (<< 2.8), python:any (>= 2.6~), python:any (>= 2.7.5-5~),
  python:any (>= 2.7~),"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dh-python 2.20151103ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 12 15:15:36 2016
  Dependencies:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-17 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  PackageArchitecture: all
  SourcePackage: dh-python
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1578442] Re: XDMCP Willing/Unwilling messages do not report hostname

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.18.2-0ubuntu1

---
lightdm (1.18.2-0ubuntu1) xenial; urgency=medium

  * New upstream release:
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Use MIR_SERVER_HOST_SOCKET instead of MIR_SOCKET to report compositor
  socket to sessions. This used to work but no longer works in Mir 0.21
  (LP: #1583624)
- Use only a single compositor on xlocal seats (LP: #1594229)
- Fix Mir greeter log filename having "(null)" in the name (LP: #1590582)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix uninitialized memory errors
  * debian/lightdm.dirs:
- Ensure user configuration directories /etc/lightdm/lightdm.conf.d and
  /etc/guest-session exist
  * debian/guest-account.sh:
  * debian/guest-session-setup.sh:
- Source prefs.sh as privileged user to allow user modification
  (LP: #1581853)

 -- Robert Ancell   Tue, 21 Jun 2016
12:49:01 +1200

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

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

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

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

[Touch-packages] [Bug 1578442] Update Released

[Martin Pitt]

The verification of the Stable Release Update for lightdm 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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1578442

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

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

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

[Touch-packages] [Bug 960157] Re: lightdm exits on SIGHUP

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.18.2-0ubuntu1

---
lightdm (1.18.2-0ubuntu1) xenial; urgency=medium

  * New upstream release:
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Use MIR_SERVER_HOST_SOCKET instead of MIR_SOCKET to report compositor
  socket to sessions. This used to work but no longer works in Mir 0.21
  (LP: #1583624)
- Use only a single compositor on xlocal seats (LP: #1594229)
- Fix Mir greeter log filename having "(null)" in the name (LP: #1590582)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix uninitialized memory errors
  * debian/lightdm.dirs:
- Ensure user configuration directories /etc/lightdm/lightdm.conf.d and
  /etc/guest-session exist
  * debian/guest-account.sh:
  * debian/guest-session-setup.sh:
- Source prefs.sh as privileged user to allow user modification
  (LP: #1581853)

 -- Robert Ancell   Tue, 21 Jun 2016
12:49:01 +1200

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

Title:
  lightdm exits on SIGHUP

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Released
Status in lightdm source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  LightDM quits when it receives SIGUSR1, SIGUSR2 or SIGHUP. But convention 
these signals should not quit a service (they should get it to dump state, 
reload configuration etc).

  [Test Case]
  1. Start lightdm
  2. sudo killall -SIGHUP lightdm

  Expected result:
  Nothing happens

  Observed result:
  LightDM restarts

  [Regression Potential]
  Low. We now just quit only on SIGTERM and SIGINT.

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

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

[Touch-packages] [Bug 1509829] Re: lightdm-guest-session profile is too strict to input Japanese text with fcitx-mozc

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.18.2-0ubuntu1

---
lightdm (1.18.2-0ubuntu1) xenial; urgency=medium

  * New upstream release:
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Use MIR_SERVER_HOST_SOCKET instead of MIR_SOCKET to report compositor
  socket to sessions. This used to work but no longer works in Mir 0.21
  (LP: #1583624)
- Use only a single compositor on xlocal seats (LP: #1594229)
- Fix Mir greeter log filename having "(null)" in the name (LP: #1590582)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix uninitialized memory errors
  * debian/lightdm.dirs:
- Ensure user configuration directories /etc/lightdm/lightdm.conf.d and
  /etc/guest-session exist
  * debian/guest-account.sh:
  * debian/guest-session-setup.sh:
- Source prefs.sh as privileged user to allow user modification
  (LP: #1581853)

 -- Robert Ancell   Tue, 21 Jun 2016
12:49:01 +1200

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

Title:
  lightdm-guest-session profile is too strict to input Japanese text
  with fcitx-mozc

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Released
Status in fcitx package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in mozc package in Ubuntu:
  Fix Released
Status in fcitx source package in Xenial:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Released
Status in mozc source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Unable to input Japanese text in guest session.

  [Test Case]
  1. Log into guest session
  2. Enable Japanese input method (fcitx-mozc)
  3. Enter Japanese text in gedit

  Expected result:
  Text can be entered

  Observed result:
  mozc gives an error saying "Failed to start Kana/Kanji conversion program. 
You need to reboot".
  [possibly related messages]
  10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 
audit(1445787629.866:709): apparmor="DENIED" operation="link" 
profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/dev/shm/sem.69ef545277bb" pid=9534 comm="fcitx" requested_mask="l" 
denied_mask="l" fsuid=120 ouid=120 target="/dev/shm/oFbWJv"
  10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 
audit(1445787629.870:710): apparmor="DENIED" operation="bind" 
profile="/usr/lib/lightdm/lightdm-guest-session" pid=9554 comm="mozc_server" 
family="unix" sock_type="stream" protocol=0 requested_mask="bind" 
denied_mask="bind" addr="@tmp/.mozc.d23bc799563c3f748fa591c15f46c971.session"

  [Regression potential]
  Low. More permissions were added to AppArmor configuration.

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

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

[Touch-packages] [Bug 1575200] Re: Error connecting to X server via IPv6

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.18.2-0ubuntu1

---
lightdm (1.18.2-0ubuntu1) xenial; urgency=medium

  * New upstream release:
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Use MIR_SERVER_HOST_SOCKET instead of MIR_SOCKET to report compositor
  socket to sessions. This used to work but no longer works in Mir 0.21
  (LP: #1583624)
- Use only a single compositor on xlocal seats (LP: #1594229)
- Fix Mir greeter log filename having "(null)" in the name (LP: #1590582)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix uninitialized memory errors
  * debian/lightdm.dirs:
- Ensure user configuration directories /etc/lightdm/lightdm.conf.d and
  /etc/guest-session exist
  * debian/guest-account.sh:
  * debian/guest-session-setup.sh:
- Source prefs.sh as privileged user to allow user modification
  (LP: #1581853)

 -- Robert Ancell   Tue, 21 Jun 2016
12:49:01 +1200

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

Title:
  Error connecting to X server via IPv6

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  LightDM doesn't pick the best IPv6 address on offer from clients (picks 
link-local addresses over non link-local).

  [Test Case]
  1. Start LightDM with XDMCP server enabled
  2. Connect XDMCP client that sends IPv6 link-local addresses to LightDM

  Expected result:
  LightDM picks a non link-local address and is able to connect to the client

  Observed result:
  LightDM picks the link-local address address if it is first

  [Regression Potential]
  Small risk of behaviour change due to new IP selection method.

  Original report:

  I've discovered a problem in lightdm XDMCP using link-local IPv6 addresses 
without interface index to connect to X server.
  It has been originally reported at 
https://bugzilla.redhat.com/show_bug.cgi?id=1322775.

  The problem can be fixed by having the XDMCP client not transmitting
  link-local addresses in the request, but if it does, lightdm XDMCP
  server can be a lot smarter if the attached patch is applied.

  It changes the X server address selection order to set the lowest
  preference to link-local addresses, even if matching the source
  address or family.

  This is not 100% full-proof: if only link-local addresses have been
  received, one of them is used anyway. In this case, a complete
  solution would be to determine and set the address interface index if
  not ambiguous.

  However, this patch fixes the problem for most of the non-pathological
  cases.

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

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

[Touch-packages] [Bug 1571198] Update Released

[Martin Pitt]

The verification of the Stable Release Update for python2.7 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 python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1571198

Title:
  Missing symlink in python2.7-dbg package

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Committed

Bug description:
  Extending gdb with python (2.7) doesn't work in 16.04 xenial because
  /usr/share/gdb/auto-load/usr/bin/python2.7-gdb.py
  pointing to
  /usr/share/gdb/auto-load/usr/bin/python2.7m-gdb.py
  is missing from the package!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1571198/+subscriptions

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

[Touch-packages] [Bug 1581853] Re: Source prefs.sh as privileged user to allow user mods

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.18.2-0ubuntu1

---
lightdm (1.18.2-0ubuntu1) xenial; urgency=medium

  * New upstream release:
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Use MIR_SERVER_HOST_SOCKET instead of MIR_SOCKET to report compositor
  socket to sessions. This used to work but no longer works in Mir 0.21
  (LP: #1583624)
- Use only a single compositor on xlocal seats (LP: #1594229)
- Fix Mir greeter log filename having "(null)" in the name (LP: #1590582)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix uninitialized memory errors
  * debian/lightdm.dirs:
- Ensure user configuration directories /etc/lightdm/lightdm.conf.d and
  /etc/guest-session exist
  * debian/guest-account.sh:
  * debian/guest-session-setup.sh:
- Source prefs.sh as privileged user to allow user modification
  (LP: #1581853)

 -- Robert Ancell   Tue, 21 Jun 2016
12:49:01 +1200

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

Title:
  Source prefs.sh as privileged user to allow user mods

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

Bug description:
  [Impact] including [Test Case]

  The Ask Ubuntu question  called my
  attention to a regression in 16.04 as regards the possibilities for
  the system owner to configure the guest account. Up to 15.10 you can
  put e.g. this line in /etc/guest-session/prefs.sh:

  adduser $USER somegroup

  But if you try that in 16.04, the guest session won't launch. The
  explanation is that after the reorganization of the guest session code
  in 16.04, prefs.sh is sourced by /usr/share/lightdm/guest-
  session/setup.sh, which is not run as root.

  The linked merge proposals restore the previous behavior by letting
  prefs.sh be sourced by /usr/sbin/guest-account again.

  [Regression Potential]

  Low.

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

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

[Touch-packages] [Bug 1590582] Update Released

[Martin Pitt]

The verification of the Stable Release Update for lightdm 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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1590582

Title:
  greeter log is called "(null)-greeter" when seat type is xlocal and
  session type is mir

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Released
Status in lightdm source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  LightDM uses a strange name for Mir greeter logs - 
/var/log/lightdm/(null)-greeter.log

  [Test Case]
  1. Start LightDM with a Mir greeter
  2. Check logs in /var/log/lightdm

  Expected result:
  Appropriate named log file

  Observed result:
  Log contains a (null)

  [Regression Potential]
  Low. We now set the NULL value to something appropriate (the seat name, i.e. 
seat0-greeter.log).

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

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

[Touch-packages] [Bug 1590582] Re: greeter log is called "(null)-greeter" when seat type is xlocal and session type is mir

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.18.2-0ubuntu1

---
lightdm (1.18.2-0ubuntu1) xenial; urgency=medium

  * New upstream release:
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Use MIR_SERVER_HOST_SOCKET instead of MIR_SOCKET to report compositor
  socket to sessions. This used to work but no longer works in Mir 0.21
  (LP: #1583624)
- Use only a single compositor on xlocal seats (LP: #1594229)
- Fix Mir greeter log filename having "(null)" in the name (LP: #1590582)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix uninitialized memory errors
  * debian/lightdm.dirs:
- Ensure user configuration directories /etc/lightdm/lightdm.conf.d and
  /etc/guest-session exist
  * debian/guest-account.sh:
  * debian/guest-session-setup.sh:
- Source prefs.sh as privileged user to allow user modification
  (LP: #1581853)

 -- Robert Ancell   Tue, 21 Jun 2016
12:49:01 +1200

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

Title:
  greeter log is called "(null)-greeter" when seat type is xlocal and
  session type is mir

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Released
Status in lightdm source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  LightDM uses a strange name for Mir greeter logs - 
/var/log/lightdm/(null)-greeter.log

  [Test Case]
  1. Start LightDM with a Mir greeter
  2. Check logs in /var/log/lightdm

  Expected result:
  Appropriate named log file

  Observed result:
  Log contains a (null)

  [Regression Potential]
  Low. We now set the NULL value to something appropriate (the seat name, i.e. 
seat0-greeter.log).

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

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

[Touch-packages] [Bug 1583624] Re: Mir cannot open a tty when started by lightdm

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.18.2-0ubuntu1

---
lightdm (1.18.2-0ubuntu1) xenial; urgency=medium

  * New upstream release:
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Use MIR_SERVER_HOST_SOCKET instead of MIR_SOCKET to report compositor
  socket to sessions. This used to work but no longer works in Mir 0.21
  (LP: #1583624)
- Use only a single compositor on xlocal seats (LP: #1594229)
- Fix Mir greeter log filename having "(null)" in the name (LP: #1590582)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix uninitialized memory errors
  * debian/lightdm.dirs:
- Ensure user configuration directories /etc/lightdm/lightdm.conf.d and
  /etc/guest-session exist
  * debian/guest-account.sh:
  * debian/guest-session-setup.sh:
- Source prefs.sh as privileged user to allow user modification
  (LP: #1581853)

 -- Robert Ancell   Tue, 21 Jun 2016
12:49:01 +1200

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

Title:
  Mir cannot open a tty when started by lightdm

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  LightDM reports the system compositor socket to Mir clients using the 
MIR_SOCKET variable. This stopped working in Mir 0.21. The Mir team says the 
correct variable is MIR_SERVER_HOST_SOCKET and MIR_SOCKET was a fallback to 
that.

  [Test Case]
  1. Start LightDM with a Mir greeter

  Expected result:
  Greeter starts

  Observed result:
  Mir greeter fails to start. It is attempting to access the video drivers 
directly (i.e. not through a compositor).

  [Regression Potential]
  Risk of using LightDM with older version of Mir that doesn't support 
MIR_SERVER_HOST_SOCKET. Risk of behaviour change in Mir using 
MIR_SERVER_HOST_SOCKET.

  From mir-greeter.log (and with minor instrumentation from RAOF)

  ERROR: QMirServer - Mir failed to start
  qtmir.screens: ScreenController::ScreenController
  qtmir.mir: MirServer created
  qtmir.mir: Command line arguments passed to Qt: ("/usr/bin/unity8", 
"--mode=greeter")
  ERROR: 
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/server/graphics/default_configuration.cpp(133):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/platforms/mesa/server/kms/linux_virtual_terminal.cpp(238):
 Throw in function int 
mir::graphics::mesa::LinuxVirtualTerminal::find_active_vt_number()
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: Failed to find the current VT. Tried:
   /dev/tty0:
    Failed to open read-only: Permission denied
    Failed to open write-only: Permission denied
   /dev/tty:
    Failed to open read-only: No such device or address
    Failed to open write-only: No such device or address

  This occurs when trying to start the unity8 greeter under unity system
  compositor

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

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

[Touch-packages] [Bug 1594229] Re: Not able to use multiple USC instances

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.18.2-0ubuntu1

---
lightdm (1.18.2-0ubuntu1) xenial; urgency=medium

  * New upstream release:
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Use MIR_SERVER_HOST_SOCKET instead of MIR_SOCKET to report compositor
  socket to sessions. This used to work but no longer works in Mir 0.21
  (LP: #1583624)
- Use only a single compositor on xlocal seats (LP: #1594229)
- Fix Mir greeter log filename having "(null)" in the name (LP: #1590582)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix uninitialized memory errors
  * debian/lightdm.dirs:
- Ensure user configuration directories /etc/lightdm/lightdm.conf.d and
  /etc/guest-session exist
  * debian/guest-account.sh:
  * debian/guest-session-setup.sh:
- Source prefs.sh as privileged user to allow user modification
  (LP: #1581853)

 -- Robert Ancell   Tue, 21 Jun 2016
12:49:01 +1200

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

Title:
  Not able to use multiple USC instances

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Released
Status in lightdm source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  If more than one Mir session is running in an xlocal seat LightDM will 
attempt to launch one Unity System Compositor per session. This used to work 
but now USC only allows a single instance.

  [Test Case]
  1. Start LightDM
  2. Log into a Mir session
  3. Switch to the greeter
  3. Log into another Mir session (with a second user)

  Expected result:
  Second session shows.

  Observed result:
  Can't log in because USC won't start a second time.

  [Regression Potential]
  Some refactoring was required to make this work, which could cause a 
regression. Existing regression tests reduce this risk.

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

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

[Touch-packages] [Bug 1594229] Update Released

[Martin Pitt]

The verification of the Stable Release Update for lightdm 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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1594229

Title:
  Not able to use multiple USC instances

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Released
Status in lightdm source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  If more than one Mir session is running in an xlocal seat LightDM will 
attempt to launch one Unity System Compositor per session. This used to work 
but now USC only allows a single instance.

  [Test Case]
  1. Start LightDM
  2. Log into a Mir session
  3. Switch to the greeter
  3. Log into another Mir session (with a second user)

  Expected result:
  Second session shows.

  Observed result:
  Can't log in because USC won't start a second time.

  [Regression Potential]
  Some refactoring was required to make this work, which could cause a 
regression. Existing regression tests reduce this risk.

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

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

[Touch-packages] [Bug 1591895] Update Released

[Martin Pitt]

The verification of the Stable Release Update for python2.7 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 python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1591895

Title:
  SRU: backport python 2.7.12 to 16.04 LTS

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Committed

Bug description:
  SRU: backport python 2.7.12 to 16.04 LTS

  The idea is to ship a released version with the first point release of
  16.04 LTS.  We updated python2.7 from the the 2.7 branch up to the
  final 2.7.12 release, and then made a test rebuild of the archive
  using the new python2.7 (and some other toolchain packages).

  The test rebuild was done using the release candidate of 2.7.12,
  however the only changes between the rc and the final release are
  Windows related, and include one change in the idle lib. From my point
  of view we don't need another test rebuild.

  The evaluation of the test rebuild is found in LP: #1586673. I'm
  pretty sure that none of the possible regressions can be attributed to
  the python2.7 update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1591895/+subscriptions

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

[Touch-packages] [Bug 1588126] Re: [OTA-11] Wifi never connects since installing OTA-11

[Daniel van Vugt]

Pat:

Yes the wifi password is 19 characters with lots of different character
types but nothing you won't find on a US keyboard.

I just got back from a month away, flashed OTA-11 on mako and have the
same problem. Ubuntu Touch, and only Ubuntu Touch can't connect to wifi
anymore.

** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

Title:
  [OTA-11] Wifi never connects since installing OTA-11

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  I've just flashed clean images of OTA-11 from the stable channel onto
  a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the
  phones can see the wifi networks but can't connect to any of them any
  more.

  The wifi networks continue to work for non-Ubuntu devices.

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

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

[Touch-packages] [Bug 1567085] Re: LUKS swap partition destroyed upon reboot in 15.10 and 16.04

[Launchpad Bug Tracker]

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

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

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

Title:
  LUKS swap partition destroyed upon reboot in 15.10 and 16.04

Status in systemd package in Ubuntu:
  Expired

Bug description:
  Usually on every reboot, sometimes every other, the LUKS encrypted
  swap partition is being destroyed. blkid shows no UUID for the
  partition, cryptsetup doesn't recognize it as a LUKS partition. This
  is logged:

  Tra 06 23:05:41 deltalabs systemd[1]: 
dev-disk-by\x2duuid-9e972bb6\x2df6dc\x2d4e64\x2d8976\x2d2df54bd076f7.device: 
Job 
dev-disk-by\x2duuid-9e972bb6\x2df6dc\x2d4e64\x2d8976\x2d2df54bd076f7.device/start
 tim
  Tra 06 23:05:41 deltalabs systemd[1]: Timed out waiting for device 
dev-disk-by\x2duuid-9e972bb6\x2df6dc\x2d4e64\x2d8976\x2d2df54bd076f7.device.
  Tra 06 23:05:41 deltalabs systemd[1]: Dependency failed for Cryptography 
Setup for sda2_crypt.
  Tra 06 23:05:41 deltalabs systemd[1]: Dependency failed for 
dev-mapper-sda2_crypt.device.
  Tra 06 23:05:41 deltalabs systemd[1]: Dependency failed for 
/dev/mapper/sda2_crypt.
  Tra 06 23:05:41 deltalabs systemd[1]: Dependency failed for Swap.
  Tra 06 23:05:41 deltalabs systemd[1]: Dependency failed for Encrypted Volumes.

  The disk layout is as follows:

  Number  Start   End SizeType File system  Flags
   1  1049kB  1024MB  1023MB  primary  ext4 boot
   2  1024MB  6024MB  5000MB  primary
   3  6024MB  406GB   400GB   primary
   4  406GB   430GB   24,0GB  primary

  #2 is LUKS swap and #3 is LUKS root, which obviously gets decrypted
  and mounted okay. This started happening after an update in 15.10 few
  weeks ago and aparently continues in 16.04 beta 2.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-3ubuntu2 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  6 23:08:06 2016
  InstallationDate: Installed on 2016-01-11 (86 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-17-generic 
root=UUID=73474220-1b0e-46bc-bba1-73fbbbc0a6f5 ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-04-05 (1 days ago)
  dmi.bios.date: 11/26/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: A770DE+
  dmi.board.vendor: ASRock
  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.:bvrP1.40:bd11/26/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA770DE+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1600305] Re: Touch Problem on MX4

[Ronny Fuchs]

a syslog doesn't exists on my phone

I don't know, if I can reproduce the problem, but the morning always
starts the same.

1. alarm clock ringing (two or three times)
2. dekko
3. facebook (sometimes)

Only this morning was the problem even after a time gone. I hope the
dmesg.log helps.


** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1600305/+attachment/4699834/+files/dmesg.log

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

Title:
  Touch Problem on MX4

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

Bug description:
  Can't swipe on the left- and rightside

  Devise-Information:
  current build number: 13
  device name: arale
  channel: ubuntu-touch/stable/meizu.en
  last update: 2016-06-02 05:58:37
  version version: 13
  version ubuntu: 20160524.1
  version tag: OTA-11
  version device: 20160331-e143fc2
  version custom: 20160504-975-19-6

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

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

[Touch-packages] [Bug 1510570] Re: BLE pairing fail

[Robert Liu]

I tried to specify the udev rule more precisely, i.e. only power up a host 
controller.
Is there anybody could give it a try?

#/lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules
# Set bluetooth power up
ACTION=="add", SUBSYSTEM=="bluetooth", KERNEL=="hci[0-9]*", 
ENV{DEVTYPE}=="host", RUN+="/bin/hciconfig %k up"

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

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.

  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

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

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

[Touch-packages] [Bug 1534501] Re: dnsmasq error logs fill up storage drive memory

[Jon Walsh]

I resolved this by disabling the dnsmasq plugin in
/etc/NetworkManager/NetworkManager.conf, as I wanted to keep my own
dnsmasq configuration.

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

Title:
  dnsmasq error logs fill up storage drive memory

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in rsyslog package in Ubuntu:
  Invalid

Bug description:
  snippet of logs.

  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.397836] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.407691] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.419365] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited wit

[Touch-packages] [Bug 1602485] [NEW] fwupd gnome-software

[AboAlfadl]

Public bug reported:

Lately I've been experiencing a weird problem, my CPU (including all 4
cores) are 100% used by some processes like gnome-software(Gnome
software) and fwupd(Firmware update daemon). This makes my work goes
down. If i even kill those processes, they are starting back again.

Is there a solution for these processes to not utilize 100% of my CPU.
And I don't want answers saying use the cpulimit utility to provision
the amount of CPU for those processes. I find this a core problem in
Ubuntu, i'm expecting real solutions for the problem.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Jul 13 03:48:43 2016
DistUpgraded: 2016-04-24 23:10:17,549 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:3824]
InstallationDate: Installed on 2015-12-14 (212 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 80K6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=73fd1edc-d964-40d3-a1dd-b1ca4118cce6 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-24 (79 days ago)
dmi.bios.date: 03/19/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: C2CN17WW(V1.03)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo Z51-70
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Z51-70
dmi.modalias: 
dmi:bvnLENOVO:bvrC2CN17WW(V1.03):bd03/19/2015:svnLENOVO:pn80K6:pvrLenovoZ51-70:rvnLENOVO:rnLenovoZ51-70:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoZ51-70:
dmi.product.name: 80K6
dmi.product.version: Lenovo Z51-70
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Jul 12 23:47:52 2016
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5579 
 vendor CMN
xserver.version: 2:1.18.3-1ubuntu2.2

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


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

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

Title:
  fwupd  gnome-software

Status in xorg package in Ubuntu:
  New

Bug description:
  Lately I've been experiencing a weird problem, my CPU (including all 4
  cores) are 100% used by some processes like gnome-software(Gnome
  software) and fwupd(Firmware update daemon). This makes my work goes
  down. If i even kill those processes, they are starting back again.

  Is there a solution for these processes to not utilize 100% of my CPU.
  And I don't want answers saying use the cpulimit utility to provision
  the amount of CPU for those processes. I find this a core problem in
  Ubuntu, i'm expecting real solutions for the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul 13 03:48:43 2016
  DistUpgraded: 2016-04-24 23:10:17,549 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if

[Touch-packages] [Bug 1602479] Re: package linux-image-extra-3.19.0-25-generic 3.19.0-25.26~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-3.19.0-25-generic 3.19.0-25.26~14.04.1
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  i dont know what this problems means , but since ubuntu found it as
  issue so i report it , im newbie , i think its package problem ,
  thanks ubuntu team :D

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.19.0-25-generic 3.19.0-25.26~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  Uname: Linux 3.19.0-56-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Wed Jul 13 04:09:56 2016
  DuplicateSignature: 
package:linux-image-extra-3.19.0-25-generic:3.19.0-25.26~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2016-03-21 (113 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.19.0-25-generic 3.19.0-25.26~14.04.1 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1602479] [NEW] package linux-image-extra-3.19.0-25-generic 3.19.0-25.26~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return co

[hasan]

Public bug reported:

i dont know what this problems means , but since ubuntu found it as
issue so i report it , im newbie , i think its package problem , thanks
ubuntu team :D

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.19.0-25-generic 3.19.0-25.26~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
Uname: Linux 3.19.0-56-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Wed Jul 13 04:09:56 2016
DuplicateSignature: 
package:linux-image-extra-3.19.0-25-generic:3.19.0-25.26~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2016-03-21 (113 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.6
 apt  1.0.1ubuntu2.13
SourcePackage: initramfs-tools
Title: package linux-image-extra-3.19.0-25-generic 3.19.0-25.26~14.04.1 failed 
to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited 
with return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package linux-image-extra-3.19.0-25-generic 3.19.0-25.26~14.04.1
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  i dont know what this problems means , but since ubuntu found it as
  issue so i report it , im newbie , i think its package problem ,
  thanks ubuntu team :D

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.19.0-25-generic 3.19.0-25.26~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  Uname: Linux 3.19.0-56-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Wed Jul 13 04:09:56 2016
  DuplicateSignature: 
package:linux-image-extra-3.19.0-25-generic:3.19.0-25.26~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2016-03-21 (113 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.19.0-25-generic 3.19.0-25.26~14.04.1 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1602464] Re: package linux-image-extra-3.19.0-59-generic 3.19.0-59.66~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-3.19.0-59-generic 3.19.0-59.66~14.04.1
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  i cant open ubuntu software center , i dont know why , im linux newbie
  , thanks for everything ubuntu team :)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.19.0-59-generic 3.19.0-59.66~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  Uname: Linux 3.19.0-56-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Wed Jul 13 03:09:57 2016
  DpkgHistoryLog:
   Start-Date: 2016-07-13  03:08:48
   Commandline: apt-get -f install
   Install: linux-headers-3.19.0-59:amd64 (3.19.0-59.66~14.04.1, automatic)
   Upgrade: oxideqt-codecs:amd64 (1.14.9-0ubuntu0.14.04.1, 
1.15.8-0ubuntu0.14.04.1), thunderbird:amd64 (38.6.0+build1-0ubuntu0.14.04.1, 
38.8.0+build1-0ubuntu0.14.04.1), liboxideqtcore0:amd64 
(1.13.6-0ubuntu0.14.04.1, 1.15.8-0ubuntu0.14.04.1), liboxideqtquick0:amd64 
(1.14.9-0ubuntu0.14.04.1, 1.15.8-0ubuntu0.14.04.1), liboxideqt-qmlplugin:amd64 
(1.14.9-0ubuntu0.14.04.1, 1.15.8-0ubuntu0.14.04.1)
  DuplicateSignature: 
package:linux-image-extra-3.19.0-59-generic:3.19.0-59.66~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2016-03-21 (113 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.19.0-59-generic 3.19.0-59.66~14.04.1 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1602464] [NEW] package linux-image-extra-3.19.0-59-generic 3.19.0-59.66~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return co

[hasan]

Public bug reported:

i cant open ubuntu software center , i dont know why , im linux newbie ,
thanks for everything ubuntu team :)

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.19.0-59-generic 3.19.0-59.66~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
Uname: Linux 3.19.0-56-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Wed Jul 13 03:09:57 2016
DpkgHistoryLog:
 Start-Date: 2016-07-13  03:08:48
 Commandline: apt-get -f install
 Install: linux-headers-3.19.0-59:amd64 (3.19.0-59.66~14.04.1, automatic)
 Upgrade: oxideqt-codecs:amd64 (1.14.9-0ubuntu0.14.04.1, 
1.15.8-0ubuntu0.14.04.1), thunderbird:amd64 (38.6.0+build1-0ubuntu0.14.04.1, 
38.8.0+build1-0ubuntu0.14.04.1), liboxideqtcore0:amd64 
(1.13.6-0ubuntu0.14.04.1, 1.15.8-0ubuntu0.14.04.1), liboxideqtquick0:amd64 
(1.14.9-0ubuntu0.14.04.1, 1.15.8-0ubuntu0.14.04.1), liboxideqt-qmlplugin:amd64 
(1.14.9-0ubuntu0.14.04.1, 1.15.8-0ubuntu0.14.04.1)
DuplicateSignature: 
package:linux-image-extra-3.19.0-59-generic:3.19.0-59.66~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2016-03-21 (113 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.6
 apt  1.0.1ubuntu2.13
SourcePackage: initramfs-tools
Title: package linux-image-extra-3.19.0-59-generic 3.19.0-59.66~14.04.1 failed 
to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited 
with return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package linux-image-extra-3.19.0-59-generic 3.19.0-59.66~14.04.1
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  i cant open ubuntu software center , i dont know why , im linux newbie
  , thanks for everything ubuntu team :)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.19.0-59-generic 3.19.0-59.66~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  Uname: Linux 3.19.0-56-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Wed Jul 13 03:09:57 2016
  DpkgHistoryLog:
   Start-Date: 2016-07-13  03:08:48
   Commandline: apt-get -f install
   Install: linux-headers-3.19.0-59:amd64 (3.19.0-59.66~14.04.1, automatic)
   Upgrade: oxideqt-codecs:amd64 (1.14.9-0ubuntu0.14.04.1, 
1.15.8-0ubuntu0.14.04.1), thunderbird:amd64 (38.6.0+build1-0ubuntu0.14.04.1, 
38.8.0+build1-0ubuntu0.14.04.1), liboxideqtcore0:amd64 
(1.13.6-0ubuntu0.14.04.1, 1.15.8-0ubuntu0.14.04.1), liboxideqtquick0:amd64 
(1.14.9-0ubuntu0.14.04.1, 1.15.8-0ubuntu0.14.04.1), liboxideqt-qmlplugin:amd64 
(1.14.9-0ubuntu0.14.04.1, 1.15.8-0ubuntu0.14.04.1)
  DuplicateSignature: 
package:linux-image-extra-3.19.0-59-generic:3.19.0-59.66~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2016-03-21 (113 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.19.0-59-generic 3.19.0-59.66~14.04.1 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1578011] Re: Laptop sometimes doesn't detect external monitor when docked

[vik]

I don't know; I don't typically pay too much attention to updates.

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

Title:
  Laptop sometimes doesn't detect external monitor when docked

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Thinkpad Yoga S1 sometimes doesn't detect external monitor when
  docked with a Onelink Pro dock. Problem has also occurred on a non-Pro
  OneLink dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda1: clean, 860723/30769152 files, 38024704/123073521 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed May  4 11:47:20 2016
  DistUpgraded: 2016-04-23 16:11:36,997 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2217]
  InstallationDate: Installed on 2015-12-02 (153 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20C0S1CWAU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=bbf6846f-7622-4638-8e7e-286b6badb71d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (10 days ago)
  dmi.bios.date: 01/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GQET48WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0S1CWAU
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGQET48WW(1.28):bd01/14/2016:svnLENOVO:pn20C0S1CWAU:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S1CWAU:rvr0B98417PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0S1CWAU
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  4 08:27:55 2016
  xserver.configfile: default
  xserver.errors:
   Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1586673] Re: Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS

[Kees Cook]

I'm able to use these (and I can verify they fix the problems I was
having), so +1 to promotion to -updates. Thanks!

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

Title:
  Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS

Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-5-cross package in Ubuntu:
  Fix Released
Status in gcc-5-cross-ports package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Committed
Status in gcc-5 source package in Xenial:
  Fix Committed
Status in gcc-5-cross source package in Xenial:
  Fix Committed
Status in gcc-5-cross-ports source package in Xenial:
  Fix Committed

Bug description:
  Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS.  16.04 LTS ships
  binutils and gcc-5 versions taken from the release branches, which saw
  more regression fixes and support for new hardware until the 5.4.0 and
  2.26.1 point releases. The idea is to include these final point
  releases into 16.04.1 LTS, with test rebuilds done for all packages,
  and regression checks for seeded packages.

  Acceptance criteria should be no regressions for the seeded packages,
  plus a best effort for unseeded packages.  During the analysis of the
  build failures, one gcc regression (libstdc++ header reorg) was found
  and reverted, and validated, that these build failures are fixed (plus
  affected seeded packages were uploaded to xenial-proposed anyway).

  reference test rebuild:
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-baseline-xenial.html

  test rebuild (xenial-release):
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-xenial.html

  test rebuild (xenial-updates):
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-updates-xenial.html

  The test rebuild was done using packages from the ubuntu-
  toolchain-r/ppa.

  Attached is an analysis of the build failures, and whether they are
  regressions, or already are present in the xenial release.

  main component
  ==

  bzr
LP: #1592731, fixed in -proposed
  ecj
LP: #1592801, fixed in -updates
  freerdp
not a regression
  gcc-5-cross
needs update after gcc-5 acceptance
  gnutls28
LP: #1592693, fixed in -updates
  kmod
unrelated, tracked in LP: #1592722
  libnih
not a regression
  llvm-toolchain-3.6
not a regression
  migrate
unrelated (mysql-5.7), tracked in LP: #1592663
  neon27 (s390x)
unrelated, traked in LP: #1592698
  openvswitch
not a regression, tracked in LP: #1592793
  python-pymysql
unrelated (mysql-5.7), tracked in LP: #1592664
  python-tooz
unrelated, tracked in LP: #1592660
  sbsigntool
not a regression
  shim
not a regression
  strongswan
racy test, unrelated, tracked in LP: #1592706
  ubuntu-defaults-builder
unrelated, LP: #1597370, waiting for approval
  upstart
not a regression
  whoopsie
LP: #1592649, fixed in -updates
  yaboot
not a regression

  bzr package set
  ===

  bzr-builder
  bzr-upload
no regressions

  cli-mono package set
  

  gbrainy
  ikvm
  monodevelop
  tangerine
no regressions

  desktop-extra package set
  =

  java-gnome
not a regressions

  edubuntu package set
  

  atomix
  gbrainy
no regressions

  input-methods package set
  =

  fcitx-table-other
  libkkc
no regressions

  kubuntu package set (minus packages from main)
  ==

  avogadro
not a regression
  eigen2
not a regression
  fam
not a regression
  farstream-0.2
not a regression
  gst-plugins-base0.10
not a regression
  gst-plugins-good0.10
not a regression
  gstreamer0.10
not a regression
  kqoauth
not a regression
  kubuntu-web-shortcuts
not a regression
  libmpc
not a regression
  libmygpo-qt
not a regression
  libspe2
not a regression
  networkmanager-qt
obsoleted by version in -updates
  plotutils
not a regression
  qtcurve
not a regression
  tbb
not a regression
  telepathy-haze
not a regression
  telepathy-qt
not a regression

  
  lubuntu package set
  

  hardinfo
not a regression
  libguess
not a regression

  mozilla package set
  

  eclipse
  xiphos
no regressions

  mythbuntu package set
  =

  piston-mini-client
not a regression

  schooltool package set
  ==

  schooltool-book
not a regression

  ubuntu

[Touch-packages] [Bug 1599297] Re: One should be able to request the URL for a specific crash report

[Brian Murray]

** Changed in: apport (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  One should be able to request the URL for a specific crash report

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

Bug description:
  As I said in Bug #1599295, when one submits a crash report and it for
  some reason fails to open a browser tab/window with the reporting bit
  one is unable to find the URL to go to as Apport just silently fails
  (though does log something to syslog).

  So I think that as well as the other bug being fixed, it would be
  really good if one could specify a crash signature or a .crash file
  and then ask Apport to provide the URL to the uploaded contents where
  one can then properly report the crash in question (perhaps this could
  be done by a command-line option or something).

  I am running Ubuntu GNOME 16.04 with GNOME 3.20.

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

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

[Touch-packages] [Bug 1600505] Re: Sometimes I get "[drm:intel_dp_start_link_train] *ERROR* too many full retries, give up" in terminals

[Christopher M. Penalver]

Norbert, thank you for taking the time to report this bug and helping to
make Ubuntu better. However, I am closing it because as per
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1600505/comments/4
the bug has been fixed in the latest development version of Ubuntu.

This is a significant bug in Ubuntu. If you need a fix for the bug in
previous versions of Ubuntu, please perform as much as possible of the
SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Sometimes I get "[drm:intel_dp_start_link_train] *ERROR* too many full
  retries, give up" in terminals

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I have the message "[drm:intel_dp_start_link_train] *ERROR* too many
  full retries, give up" on my Ubuntu 12.04.5 LTS with Intel i7-3537U
  CPU (Asustek UX32A laptop) and 3.13 kernel from Trusty HWE.

  And sometimes I have other error messages about i915 driver for
  example while launching Scilab:

  scilab
  libEGL warning: failed to create a pipe screen for i965

  I do not know, may be these problems are similar.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-91.138~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-91-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,mousepoll,move,gnomecompat,wall,regex,place,resize,snap,session,imgpng,vpswitch,grid,unitymtgrabhandles,animation,expo,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
  CompositorRunning: compiz
  Date: Sat Jul  9 21:41:14 2016
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus: 8192cu, 1.10, 3.13.0-91-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:2135]
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic 
root=UUID=1e3c78e2-1a6e-4afe-8249-40fe7fa81a86 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  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

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

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

[Touch-packages] [Bug 1578011] Re: Laptop sometimes doesn't detect external monitor when docked

[vik]

Hmm; under certain conditions, is now crashing the computer entirely
when I connect the dock.

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

Title:
  Laptop sometimes doesn't detect external monitor when docked

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Thinkpad Yoga S1 sometimes doesn't detect external monitor when
  docked with a Onelink Pro dock. Problem has also occurred on a non-Pro
  OneLink dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda1: clean, 860723/30769152 files, 38024704/123073521 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed May  4 11:47:20 2016
  DistUpgraded: 2016-04-23 16:11:36,997 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2217]
  InstallationDate: Installed on 2015-12-02 (153 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20C0S1CWAU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=bbf6846f-7622-4638-8e7e-286b6badb71d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (10 days ago)
  dmi.bios.date: 01/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GQET48WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0S1CWAU
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGQET48WW(1.28):bd01/14/2016:svnLENOVO:pn20C0S1CWAU:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S1CWAU:rvr0B98417PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0S1CWAU
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  4 08:27:55 2016
  xserver.configfile: default
  xserver.errors:
   Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1578011] Re: Laptop sometimes doesn't detect external monitor when docked

[Christopher M. Penalver]

vik, to clarify your comment:
>"The issue disappeared for a while, but has returned in the past month or so; 
>I'm guess a kernel driver update fixed it, then regressed."

Could you please advise after which update specifically did this issue
start happening with?

** Tags removed: bios-outdated-1.29
** Tags added: latest-bios-1.29

** Changed in: xorg (Ubuntu)
   Importance: Low => Medium

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

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

Title:
  Laptop sometimes doesn't detect external monitor when docked

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Thinkpad Yoga S1 sometimes doesn't detect external monitor when
  docked with a Onelink Pro dock. Problem has also occurred on a non-Pro
  OneLink dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda1: clean, 860723/30769152 files, 38024704/123073521 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed May  4 11:47:20 2016
  DistUpgraded: 2016-04-23 16:11:36,997 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2217]
  InstallationDate: Installed on 2015-12-02 (153 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20C0S1CWAU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=bbf6846f-7622-4638-8e7e-286b6badb71d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (10 days ago)
  dmi.bios.date: 01/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GQET48WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0S1CWAU
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGQET48WW(1.28):bd01/14/2016:svnLENOVO:pn20C0S1CWAU:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S1CWAU:rvr0B98417PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0S1CWAU
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  4 08:27:55 2016
  xserver.configfile: default
  xserver.errors:
   Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1600065] Re: ubuntu-bug -w then click on xeyes fails to report a bug

[Brian Murray]

This might be unique to xeyes as I was able to determine the process id
of gedit and terminator using xprop.  This seems more like a bug in
xprop than apport.

** Also affects: x11-utils (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ubuntu-bug -w then click on xeyes fails to report a bug

Status in apport package in Ubuntu:
  New
Status in x11-utils package in Ubuntu:
  New

Bug description:
  To reproduce run xeyes then run ubuntu-bug -w and close the popup telling you 
to click on a window. Then click on xeyes. I get an error message from apport 
saying xprop failed to determine the process id of the window. 
  apport:
Installed: 2.20.1-0ubuntu2.1
Candidate: 2.20.1-0ubuntu2.1
Version table:
   *** 2.20.1-0ubuntu2.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   2.20.1-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xprop seemingly gives a lot of output from xprop but this fails when trying 
to report a bug on it from apport. Instead I get xprop failed to get the 
process id from the window and this output seems to succeed when I just run 
xprop on xeyes and get this output from xprop. 
  the output from xprop on xeyes is. 
  WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
  WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW
  WM_CLIENT_LEADER(WINDOW): window id # 0x1ca
  WM_LOCALE_NAME(STRING) = "en_US.UTF-8"
  WM_CLASS(STRING) = "xeyes", "XEyes"
  WM_HINTS(WM_HINTS):
Client accepts input or input focus: False
Initial state is Normal State.
bitmap id # to use for icon: 0x1c1
bitmap id # of mask for icon: 0x1c3
  WM_NORMAL_HINTS(WM_SIZE_HINTS):
program specified size: 150 by 100
window gravity: NorthWest
  WM_CLIENT_MACHINE(STRING) = "brendanperrine-coolermastern200"
  WM_COMMAND(STRING) = { "xeyes" }
  WM_ICON_NAME(STRING) = "xeyes"
  WM_NAME(STRING) = "xeyes"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashReports:
   640:1000:115:2970467:2016-07-04 11:51:43.990810416 -0700:2016-07-04 
13:30:51.419527275 -0700:/var/crash/_usr_bin_audacious.1000.crash
   640:1000:115:1606594:2016-07-04 19:22:02.393270616 -0700:2016-07-04 
19:22:00.921303054 -0700:/var/crash/_usr_bin_lxterminal.1000.crash
  CurrentDesktop: i3
  Date: Thu Jul  7 16:58:40 2016
  InstallationDate: Installed on 2015-09-20 (291 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150920)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to xenial on 2016-03-12 (117 days ago)

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

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

[Touch-packages] [Bug 1599297] Re: One should be able to request the URL for a specific crash report

[Brian Murray]

The crash was reported to errors.ubuntu.com since the crash was sent
from a release which is not in development.  whoopsie, which sends the
crash reports to the Error Tracker does log the OOPS ID, so you could
then go to http://errors.ubuntu.com/oops/$OOPSID to find your crash.

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

Title:
  One should be able to request the URL for a specific crash report

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

Bug description:
  As I said in Bug #1599295, when one submits a crash report and it for
  some reason fails to open a browser tab/window with the reporting bit
  one is unable to find the URL to go to as Apport just silently fails
  (though does log something to syslog).

  So I think that as well as the other bug being fixed, it would be
  really good if one could specify a crash signature or a .crash file
  and then ask Apport to provide the URL to the uploaded contents where
  one can then properly report the crash in question (perhaps this could
  be done by a command-line option or something).

  I am running Ubuntu GNOME 16.04 with GNOME 3.20.

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

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

[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)

[Martin Weigl]

It would be great if you could push the libhybris patch together with
ota12 next week. Or otherwise show us a way to push the patch manually.
I don't want to wait some more month for a bugfix.

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

Title:
  Poor microphone quality (mako)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After months of complaints from people talking to me on the phone
  (mako ubuntu touch), I finally got around to use multiROM to dual boot
  Ubuntu Touch and Android. Several people can confirm that there is a
  noticable difference in terms of sound/microphone quality between
  Android and UT in phone calls. With UT, my voice gets distorted to an
  extent that person at the other end have real difficulties to hear
  what I am saying, while with Android call quality is much better with
  no distortion.

  I have had a suspicion for a long time that this might be a software
  and not a hardware issue. After trying Android and Ubuntu on the same
  hardware I believe this suspicion is proved correct. This issue has
  persisted in all the builds I have tried since at least the beginning
  of the year, but probably longer. I am now at r17 of Utopic.

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

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

[Touch-packages] [Bug 1599695] Re: When running cmake from QtC on a webbrowser-app branch it fails

[Olivier Tilloy]

Does the following patch make things better, by any chance?


=== modified file 'src/Ubuntu/CMakeLists.txt'
--- src/Ubuntu/CMakeLists.txt   2016-07-01 13:06:40 +
+++ src/Ubuntu/CMakeLists.txt   2016-07-12 21:18:57 +
@@ -23,7 +23,7 @@
 OUTPUT_VARIABLE UBUNTU_VERSION OUTPUT_STRIP_TRAILING_WHITESPACE)
 add_definitions(-DUBUNTU_VERSION="${UBUNTU_VERSION}")
 
-execute_process(COMMAND ${XVFB_COMMAND} qmlscene --quit 
${CMAKE_CURRENT_SOURCE_DIR}/chromium-version.qml
+execute_process(COMMAND ${XVFB_COMMAND} qmlscene -platform minimal --quit 
${CMAKE_CURRENT_SOURCE_DIR}/chromium-version.qml
 OUTPUT_VARIABLE CHROMIUM_VERSION OUTPUT_STRIP_TRAILING_WHITESPACE)
 string(REGEX MATCH "\\[(.*)\\]" _ ${CHROMIUM_VERSION})
 set(CHROMIUM_VERSION ${CMAKE_MATCH_1})

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

Title:
  When running cmake from QtC on a webbrowser-app branch it fails

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  When running cmake from QtC on a webbrowser-app branch in Xenial it
  fails with the following error:

  CMake Error at src/Ubuntu/CMakeLists.txt:31 (message):
    Invalid chromium version: ''

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

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

[Touch-packages] [Bug 1600877] Re: Undo redo icons in edit mode should be enabled when actions are possible

[Michal Predotka]

No problem Pat :)
I was looking into Gallery code as I wanted to fix other bug on Edit page ( bug 
#1523109 ). The code for that page seems to be here: 
http://bazaar.launchpad.net/~phablet-team/gallery-app/trunk/view/head:/rc/qml/MediaViewer/PhotoEditorPage.qml
Unfortunately it references 'Ubuntu.Components.Extras' and 'PhotoEditor' there, 
which I've no idea what is and where to find it. I believe code for your bug 
will also be there.

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

Title:
  Undo redo icons in edit mode should be enabled when actions are
  possible

Status in camera-app package in Ubuntu:
  New
Status in gallery-app package in Ubuntu:
  New

Bug description:
  Select a photo and go into edit mode.
  The header presents two curly arrows facing up and down.
  Click on the arrow and nothing happens.

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

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

[Touch-packages] [Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[平凡]

** Changed in: linux-mako (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [TOPBLOCKER] file corruption on touch images in rw portions of the
  filesystem

Status in Canonical System Image:
  Fix Released
Status in android package in Ubuntu:
  Fix Released
Status in android-tools package in Ubuntu:
  In Progress
Status in initramfs-tools-ubuntu-touch package in Ubuntu:
  Fix Released
Status in linux-mako package in Ubuntu:
  Fix Released
Status in android package in Ubuntu RTM:
  Fix Released
Status in android-tools package in Ubuntu RTM:
  In Progress
Status in initramfs-tools-ubuntu-touch package in Ubuntu RTM:
  Fix Released
Status in linux-mako package in Ubuntu RTM:
  Confirmed

Bug description:
  Symptoms are that cache files in /var/cache/apparmor and profiles in
  /var/lib/apparmor/profiles are sometimes corrupted after a reboot.
  We've already fixed several bugs in the apparmor and click-apparmor
  and made both more robust in the face of corruption and we've reduced
  the impact when there is a corrupted profile, but we've still not
  found the cause of the corruption. This corruption can still affect
  real-world devices: if a profile in /var/lib/apparmor/profiles is
  corrupted and the cache file is out of date, then the profile won't
  compile and that app/scope won't start.

  Workaround: remove the affected profile and then run 'sudo aa-
  clickhook'. This obviously is not viable on an end-user device.

  The investigation is ongoing and this may not be a problem with the
  kernel at all, so this bug may be retargeted to another project.

  The security team and the kernel team have discussed this a lot and
  Colin King is currently looking at this. This bug is just so it can be
  tracked. Here is an excerpt from my latest email to Colin:

  "I believe I have conclusively ruled out apparmor_parser and aa-
  clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the
  test output:

  http://paste.ubuntu.com/8648109/

  Specifically, home/bug/test-with-true.sh changes the interesting parts
  of the algorithm to:

  1. wait for unity8 to start (this ensures the apparmor upstart job is 
finished)
  2. restore apparmor_parser and aa-clickhook, if needed
  3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles...
     /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser
     and aa-clickhook were /bin/true during boot so they could not have changed
     /var/lib/apparmor/profiles)
  4. verify the profiles, exit with error if they do not
  5. alternately upgrade/downgrade the packages
  6. verify the profiles, exit with error if they do not
  7. copy the known good profiles in the previous step to /home/bug/profiles...
  8. have apparmor_parser and aa-clickhook point to /bin/true
  9. reboot
  10. go to step 1

  In the paste you'll notice that in step 6 the profiles were
  successfully created by the installation of the packages, then
  verified, then copied aside, then apparmor_parser and aa-clickhook
  diverted, then rebooted, only to have the profiles in
  /var/lib/apparmor/profiles be different than what was copied aside. It
  would be nice to verify on your device as well (I reproduced several
  times here) and verify the reproducer algorithm. I think this suggests
  this is a kernel issue and not userspace.

  IMPORTANT: you will want to update the reproducer and refollow all of these 
steps (ie, I updated the scripts, the debs, the sudoers file, etc):
  $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz
  $ tar -zxvf ./aa-corruption.tar.gz
  ...

  $ adb push ./aa-corruption.tar.gz /tmp
  $ adb shell
  phablet@ubuntu-phablet:~$ cd /tmp
  phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz
  phablet@ubuntu-phablet:~$ sudo mount -o remount,rw /
  phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet
  /etc/sudoers.d/
  phablet@ubuntu-phablet:~$ sudo mount -o remount,ro /
  phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home
  phablet@ubuntu-phablet:~$ exit
  $ cd ./aa-corruption
  $ ./test-from-host.sh
  ...

  The old script is still in place. Simply adjust ./test-from-host.sh to have:
  testscript=/home/bug/test.sh
  #testscript=/home/bug/test-with-true.sh"

  The kernel team has verified the above reproducer and symptoms.

  Related bugs:
  * bug 1371771
  * bug 1371765
  * bug 1377338

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

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

[Touch-packages] [Bug 1497872] Re: Possibility to save RAW image files

[Peter Nerlich]

> Is there any software like Lightroom, Photoshop, Capture One, etc.
that can then process those RAW files? If not, then how would you use
the raw files?

Indeed there is, e.g. [darktable](http://www.darktable.org/).

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

Title:
  Possibility to save RAW image files

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu camera-app is missing a feature to save the raw image data from
  the image sensor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1497872/+subscriptions

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

[Touch-packages] [Bug 1594874] Re: App won't open from click scope if it got updated in meantime

[Rodney Dawes]

Found a way to make it work without changing url-dispatcher or libual.

** Changed in: unity-scope-click (Ubuntu)
   Status: Confirmed => In Progress

** No longer affects: url-dispatcher (Ubuntu)

** No longer affects: ubuntu-app-launch (Ubuntu)

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

Title:
  App won't open from click scope if it got updated in meantime

Status in unity-scope-click package in Ubuntu:
  In Progress

Bug description:
  0) Have an app installed that has an available update from the store
  1) Open that app's preview in the click scope
  2) Update the app in System Settings
  3) Click "Open" in the click scope's app preview
  4) Note that the app tries to open, but never does

  Presumably, this is because the click scope is providing a full appid
  including a version.  Either the app preview needs to refresh when an
  update is installed or it needs to provide an appid without a version.

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

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

[Touch-packages] [Bug 1600877] Re: Rotate icons in edit mode don't do anything

[Pat McGowan]

Ha thanks Michal will update the descriptions

** Summary changed:

- Rotate icons in edit mode don't do anything
+ Undo redo icons in edit mode should be enabled when actions are possible

** Description changed:

  Select a photo and go into edit mode.
  The header presents two curly arrows facing up and down.
  Click on the arrow and nothing happens.
- 
- They seem to get activated after using the other rotation option shown
- at the bottom (why do we have two?) but then only one or the other
- control works at a time.

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

Title:
  Undo redo icons in edit mode should be enabled when actions are
  possible

Status in camera-app package in Ubuntu:
  New
Status in gallery-app package in Ubuntu:
  New

Bug description:
  Select a photo and go into edit mode.
  The header presents two curly arrows facing up and down.
  Click on the arrow and nothing happens.

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

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

[Touch-packages] [Bug 1291020] Re: unlzma -l fails to recognize files created by lzma

[Mathew Hodson]

This isn't a bug. Maybe it's a feature request.

The message gives all the information you need. The --list function (or
-l) works only on .xz files not .lzma files.

The command lzma is equivalent to xz --format=lzma so it creates a .lzma
file. If you want to be able to print information about your compressed
file, you need to create it with xz (--format=xz or --format=auto) foo.

$ xz foo
$ xz -l foo.xz 
Strms  Blocks   Compressed Uncompressed  Ratio  Check   Filename
1   0 32 B  0 B---  CRC64   foo.xz

** Changed in: xz-utils (Ubuntu)
   Importance: High => Wishlist

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

Title:
  unlzma -l fails to recognize files created by lzma

Status in One Hundred Papercuts:
  Triaged
Status in xz-utils package in Ubuntu:
  Triaged

Bug description:
  unlzma -l fails to recognize files created by lzma:

#  lzma foo
#  unlzma -l foo.lzma
  unlzma: --list works only on .xz files (--format=xz or --format=auto)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xz-utils 5.1.1alpha+20120614-2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  Date: Tue Mar 11 14:16:20 2014
  Dependencies:
   gcc-4.9-base 4.9-20140222-0ubuntu1
   libc6 2.19-0ubuntu2
   libgcc1 1:4.9-20140222-0ubuntu1
   liblzma5 5.1.1alpha+20120614-2ubuntu2
   multiarch-support 2.19-0ubuntu2
  InstallationDate: Installed on 2014-01-30 (40 days ago)
  InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha i386 (20140129)
  SourcePackage: xz-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1598920] Re: MainView intercepts MouseArea's cursorShape property

[Launchpad Bug Tracker]

** Branch linked: lp:~dubstar-04/ubuntu-ui-toolkit/MainViewMouseFocus

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

Title:
  MainView intercepts MouseArea's cursorShape property

Status in Canonical System Image:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The MouseArea CursorShape doesnt have any effect.

  Docs Here: http://doc.qt.io/qt-5/qml-qtquick-mousearea.html

  Expected Behavour:
  Mouse image shows selected Qt cursor

  Experienced Behavour:
  The regular arrow is displayed.

  Example Code:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  MainView {
  objectName: "mainView"
  applicationName: "mouseTest"

  width: units.gu(100)
  height: units.gu(75)

  Rectangle{
  anchors.fill: parent
  color: UbuntuColors.coolGrey

  MouseArea{
  anchors.fill: parent
  cursorShape: Qt.CrossCursor
  hoverEnabled: true
  onClicked: console.log("In MouseArea")
  }
  }
  }

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

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

[Touch-packages] [Bug 1600877] Re: Rotate icons in edit mode don't do anything

[Michal Predotka]

AFAIK the icons in the header are not for rotating but for undo and
redo. IMO they should only be visible if there is something to undo or
redo to avoid confusions.

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

Title:
  Rotate icons in edit mode don't do anything

Status in camera-app package in Ubuntu:
  New
Status in gallery-app package in Ubuntu:
  New

Bug description:
  Select a photo and go into edit mode.
  The header presents two curly arrows facing up and down.
  Click on the arrow and nothing happens.

  They seem to get activated after using the other rotation option shown
  at the bottom (why do we have two?) but then only one or the other
  control works at a time.

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

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

[Touch-packages] [Bug 1602388] Re: Sudo crashed without I even noticed...

[Vdragon]

** Description changed:

  Yes that's all, I just noticed the apport window popping out when I
  booted.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.1
  Uname: Linux 4.6.0-pf1-buo-ren-autodetected-optimized x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul 12 00:02:24 2016
  ExecutablePath: /usr/bin/sudo
  InstallationDate: Installed on 2016-01-07 (186 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: sudo parted /dev/sda
  SourcePackage: sudo
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (96 days ago)
  VisudoCheck:
-  /etc/sudoers：解析正确
-  
/etc/sudoers.d/Patch_Launchpad_Bug_1373495_don't_preserve_HOME_environment_variable_by_default：解析正确
-  /etc/sudoers.d/Preserve_input_method_required_environmental_variables：解析正确
-  /etc/sudoers.d/README：解析正确
-  /etc/sudoers.d/buildd：解析正确
+  /etc/sudoers：解析正确(=OK)
+  
/etc/sudoers.d/Patch_Launchpad_Bug_1373495_don't_preserve_HOME_environment_variable_by_default：解析正确
+  /etc/sudoers.d/Preserve_input_method_required_environmental_variables：解析正确
+  /etc/sudoers.d/README：解析正确
+  /etc/sudoers.d/buildd：解析正确

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

Title:
  Sudo crashed without I even noticed...

Status in sudo package in Ubuntu:
  New

Bug description:
  Yes that's all, I just noticed the apport window popping out when I
  booted.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.1
  Uname: Linux 4.6.0-pf1-buo-ren-autodetected-optimized x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul 12 00:02:24 2016
  ExecutablePath: /usr/bin/sudo
  InstallationDate: Installed on 2016-01-07 (186 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: sudo parted /dev/sda
  SourcePackage: sudo
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (96 days ago)
  VisudoCheck:
   /etc/sudoers：解析正确(=OK)
   
/etc/sudoers.d/Patch_Launchpad_Bug_1373495_don't_preserve_HOME_environment_variable_by_default：解析正确
   /etc/sudoers.d/Preserve_input_method_required_environmental_variables：解析正确
   /etc/sudoers.d/README：解析正确
   /etc/sudoers.d/buildd：解析正确

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

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

[Touch-packages] [Bug 1602388] [NEW] Sudo crashed without I even noticed...

[Vdragon]

Public bug reported:

Yes that's all, I just noticed the apport window popping out when I
booted.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: sudo 1.8.16-0ubuntu1.1
Uname: Linux 4.6.0-pf1-buo-ren-autodetected-optimized x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jul 12 00:02:24 2016
ExecutablePath: /usr/bin/sudo
InstallationDate: Installed on 2016-01-07 (186 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: sudo parted /dev/sda
SourcePackage: sudo
UpgradeStatus: Upgraded to xenial on 2016-04-07 (96 days ago)
VisudoCheck:
 /etc/sudoers：解析正确
 
/etc/sudoers.d/Patch_Launchpad_Bug_1373495_don't_preserve_HOME_environment_variable_by_default：解析正确
 /etc/sudoers.d/Preserve_input_method_required_environmental_variables：解析正确
 /etc/sudoers.d/README：解析正确
 /etc/sudoers.d/buildd：解析正确

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


** Tags: amd64 apport-crash xenial

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

Title:
  Sudo crashed without I even noticed...

Status in sudo package in Ubuntu:
  New

Bug description:
  Yes that's all, I just noticed the apport window popping out when I
  booted.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.1
  Uname: Linux 4.6.0-pf1-buo-ren-autodetected-optimized x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul 12 00:02:24 2016
  ExecutablePath: /usr/bin/sudo
  InstallationDate: Installed on 2016-01-07 (186 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: sudo parted /dev/sda
  SourcePackage: sudo
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (96 days ago)
  VisudoCheck:
   /etc/sudoers：解析正确
   
/etc/sudoers.d/Patch_Launchpad_Bug_1373495_don't_preserve_HOME_environment_variable_by_default：解析正确
   /etc/sudoers.d/Preserve_input_method_required_environmental_variables：解析正确
   /etc/sudoers.d/README：解析正确
   /etc/sudoers.d/buildd：解析正确

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

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

[Touch-packages] [Bug 1059685] Re: tar hijacks lzma

[Mathew Hodson]

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

** This bug has been marked a duplicate of bug 671972
   Cannot extract lzma compressed archives created with tar

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

Title:
  tar hijacks lzma

Status in tar package in Ubuntu:
  Confirmed

Bug description:
  0 jan@muizenberg:/var/autofs/misc/home/jan$lsb_release -d
  Description:  Ubuntu 12.04.1 LTS
  0 jan@muizenberg:/var/autofs/misc/home/jan$dpkg -l tar|tail -1
  ii  tar 1.26-4ubuntu1 
  GNU version of the tar archiving utility
  0 jan@muizenberg:/var/autofs/misc/home/jan$dpkg -l |grep xz-lzma
  ii  xz-lzma 5.1.1alpha+20110809-3 
  XZ-format compression utilities - compatibility commands
  0 jan@muizenberg:/var/autofs/misc/home/jan$tar --lzma -cf 
pgd-essay-template.tar.lzma pgd-essay-template.tar
  0 jan@muizenberg:/var/autofs/misc/home/jan$unlzma pgd-essay-template.tar.lzma 
  unlzma: pgd-essay-template.tar.lzma: File format not recognised
  1 jan@muizenberg:/var/autofs/misc/home/jan$file pgd-essay-template.tar.lzma 
  pgd-essay-template.tar.lzma: XZ compressed data
  0 jan@muizenberg:/var/autofs/misc/home/jan$rm pgd-essay-template.tar
  0 jan@muizenberg:/var/autofs/misc/home/jan$unxz pgd-essay-template.tar.lzma 
  0 jan@muizenberg:/var/autofs/misc/home/jan$sudo apt-get install lzma
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
xz-lzma
  The following NEW packages will be installed
lzma
  0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
  Need to get 52,2 kB of archives.
  After this operation, 18,4 kB disk space will be freed.
  Do you want to continue [Y/n]? y
  Get:1 http://za.archive.ubuntu.com/ubuntu/ precise/main lzma amd64 
9.22-2ubuntu1 [52,2 kB]
  Fetched 52,2 kB in 0s (53,1 kB/s)
  (Reading database ... 695021 files and directories currently installed.)
  Removing xz-lzma ...
  Processing triggers for man-db ...
  Selecting previously unselected package lzma.
  (Reading database ... 694994 files and directories currently installed.)
  Unpacking lzma (from .../lzma_9.22-2ubuntu1_amd64.deb) ...
  Processing triggers for man-db ...
  Setting up lzma (9.22-2ubuntu1) ...
  update-alternatives: using /usr/bin/lzmp to provide /usr/bin/lzma (lzma) in 
auto mode.
  0 jan@muizenberg:/var/autofs/misc/home/jan$tar --lzma -cf 
pgd-essay-template.tar.lzma pgd-essay-template.tar
  0 jan@muizenberg:/var/autofs/misc/home/jan$rm pgd-essay-template.tar
  0 jan@muizenberg:/var/autofs/misc/home/jan$unlzma pgd-essay-template.tar.lzma
  unlzma: SetDecoderProperties() error
  1 jan@muizenberg:/var/autofs/misc/home/jan$unxz pgd-essay-template.tar.lzma 
  0 jan@muizenberg:/var/autofs/misc/home/jan$

  Whether xz-lzma or lzma is installede, these errors are passed to 
file-roller, meaning
  end users using GUI interfaces like unity, nautilus, and file-roller cannot 
open lzma
  files created by tar, as they are actually xz files.

  Note files created by lzma (and not by tar -J or tar --lzma) work fine, again 
with either
  lzma and xz-lzma installed:

  0 jan@muizenberg:/var/autofs/misc/home/jan$dpkg -l lzma|tail -1
  ii  lzma9.22-2ubuntu1 
  Compression and decompression in the LZMA format - command line 
utility
  0 jan@muizenberg:/var/autofs/misc/home/jan$lzma pgd-essay-template.tar
  0 jan@muizenberg:/var/autofs/misc/home/jan$file pgd-essay-template.tar.lzma 
  pgd-essay-template.tar.lzma: LZMA compressed data, non-streamed, size 1863680
  0 jan@muizenberg:/var/autofs/misc/home/jan$unlzma pgd-essay-template.tar.lzma 
  0 jan@muizenberg:/var/autofs/misc/home/jan$sudo apt-get install xz-lzma 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
lzma
  The following NEW packages will be installed
xz-lzma
  0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
  Need to get 12,4 kB of archives.
  After this operation, 18,4 kB of additional disk space will be used.
  Do you want to continue [Y/n]? y
  Get:1 http://za.archive.ubuntu.com/ubuntu/ precise/main xz-lzma all 
5.1.1alpha+20110809-3 [12,4 kB]
  Fetched 12,4 kB in 0s (12,7 kB/s)   
  (Reading database ... 694999 files and directories currently installed.)
  Removing lzma ...
  Processing triggers for man-db ...
  Selecting previously unselected package xz-lzma.
  (Reading database ... 694994 files and directories currently installed.)
  Unpacking xz-lzma (from .../xz-lzma_5.1.1alpha+20110809-3_all.deb) ...
  Processing triggers for man-db ...
  Setting up xz-lzma (5.1.1alpha+20110809-3) ...
 

[Touch-packages] [Bug 806499] Re: xz should warn before overwriting read-only files

[Mathew Hodson]

** Changed in: xz-utils (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  xz should warn before overwriting read-only files

Status in xz-utils package in Ubuntu:
  Triaged

Bug description:
  running xz --decompress (unxz) on a readonly file will not show any
  warning before writing over the file and changing the extension.

  This is technically expected behaviour but not sympathetic to the end
  user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/806499/+subscriptions

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

[Touch-packages] [Bug 671972] Re: Cannot extract lzma compressed archives created with tar

[Mathew Hodson]

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

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

Title:
  Cannot extract lzma compressed archives created with tar

Status in tar package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: tar

  After upgrading to Maverick I'm not able to open with `unlzma' lzma
  compressed archives created with `tar'.

  Steps to reproduce:

  $ touch file
  $ tar --lzma -cf archive.tar.lzma file
  $ rm file
  $ unlzma archive.tar.lzma 
  unlzma: SetDecoderProperties() error

  Extracting the archive using `tar' works:

  $ tar --lzma -xf archive.tar.lzma 
  $ ls
  archive.tar.lzma  file

  Extracting tar archives compressed with `lzma' works:

  $ rm *
  $ touch file
  $ tar -cf archive.tar file 
  $ lzma archive.tar
  $ rm file
  $ unlzma archive.tar.lzma
  $ tar -xf archive.tar 
  $ ls
  archive.tar  file

  Extracting with `unlzma' compressed archives created with `tar' in Ubuntu 
Lucid works. `lzma' version is the same in Lucid and Maverick, and in Lucid I 
wasn't affected by this problem so I'm addressing `tar'. Package info:
  $ apt-cache policy tar
  tar:
Installed: 1.23-2
Candidate: 1.23-2
Version table:
   *** 1.23-2 0
  500 http://it.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1599812] Re: Version shipped with current 16.04 LTS is way too old and alpha

[Mathew Hodson]

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

** This bug has been marked a duplicate of bug 1493999
   xz-utils package is really, really old and should be updated to 5.2.2 with 
multi-core support

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

Title:
  Version shipped with current 16.04 LTS is way too old and alpha

Status in xz-utils package in Ubuntu:
  New

Bug description:
  1. run "xz --version", you'll get "xz (XZ Utils) 5.1.0alpha"
  2. Browse to http://git.tukaani.org/?p=xz.git;a=blob;f=NEWS;hb=HEAD ; you'll 
find that v5.1.1alpha is from 2011-04-12. 5.1.0alpha is possibly even older.

  Expected result:
  No "alpha software" installed when there's better quality releases available
  No old software installed when there is at least a newer release avaialble

  Actual result:
  Alpha software is installed, 5+ years old software is installed

  Workaround:
  download and install v5.2.2 from http://tukaani.org/xz/

  Solution:
  Package v5.2.2. to the official repositories

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xz-utils 5.1.1alpha+20120614-2ubuntu2
  Uname: Linux 4.4.14-040414-lowlatency x86_64
  NonfreeKernelModules: rfcomm ipt_REJECT nf_reject_ipv4 pci_stub vboxpci 
vboxnetadp vboxnetflt vboxdrv bnep btusb btrtl btbcm btintel xt_multiport 
iptable_filter ip_tables x_tables usblp 8812au ath3k bluetooth cfg80211 uas 
input_leds usb_storage snd_hda_codec_realtek hp_wmi snd_hda_codec_generic 
sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_intel 
coretemp snd_hda_codec snd_hda_core kvm_intel snd_hwdep kvm snd_pcm 
snd_seq_midi snd_seq_midi_event irqbypass crct10dif_pclmul crc32_pclmul 
aesni_intel snd_rawmidi aes_x86_64 lrw gf128mul glue_helper snd_seq ablk_helper 
cryptd snd_seq_device snd_timer snd serio_raw mei_me soundcore mei shpchp 
lpc_ich 8250_fintek mac_hid parport_pc ppdev lp parport autofs4 xfs raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 multipath linear hid_generic usbhid hid raid0 i915 i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse ahci drm 
r8169 libahci mi
 i wmi fjes video
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jul  7 13:18:30 2016
  Dependencies:
   gcc-6-base 6.0.1-1ubuntu11 [origin: unknown]
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-1ubuntu11 [origin: unknown]
   liblzma5 5.1.1alpha+20120614-2ubuntu2
   multiarch-support 2.23-0ubuntu3
  InstallationDate: Installed on 2016-04-22 (75 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: xz-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1599812/+subscriptions

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

[Touch-packages] [Bug 512058] Re: tar should suggest xz-utils

[Mathew Hodson]

tar suggests xz-utils as of tar (1.23-1)

** Tags added: packaging

** Changed in: tar (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  tar should suggest xz-utils

Status in tar package in Ubuntu:
  Fix Released
Status in tar package in Debian:
  Fix Released

Bug description:
  Binary package hint: tar

  Package: tar
  Version: 1.22-1
  Severity: wishlist

  while using tar.xz files one have to install xz-utils, tar should
  suggest that in order to uncompress this kind of files.


  see

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523499

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

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

[Touch-packages] [Bug 1554715] Re: rmt and rmt-tar should not be autoinstalled

[Mathew Hodson]

** Changed in: tar (Ubuntu)
   Importance: Undecided => Wishlist

** Tags added: packaging

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

Title:
  rmt and rmt-tar should not be autoinstalled

Status in tar package in Ubuntu:
  New

Bug description:
  A "remote magtape protocol module? On PCs? In 2016?

  The are potential users for this thing, maybe, on Z-series mainframes,
  but having it be autoinstalled  on vanilla desktop machines, or even
  ordinary servers, is deeply silly.

  Recommendation: split the package.  Yes, tar is essential; rmt is not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: tar 1.27.1-2
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: i3
  Date: Tue Mar  8 15:23:17 2016
  InstallationDate: Installed on 2016-01-02 (65 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: tar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 377604] Re: --strip-components listed twice in man page

[Mathew Hodson]

This isn't an issue anymore in Trusty.

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

** Tags added: manpage

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

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

Title:
  --strip-components listed twice in man page

Status in tar package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: tar

  The man page contains the following:

  "
 --strip-components n
Strip the given number of leading directory components

 --strip, --strip-components N
Strips  the  first  N components from archive members’ pathnames
when unpacking.
  "

  
  This is in tar version 1.20-1 from 8.10. Unknown if it's fixed in 9.04

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

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

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Jose Luis]

I think for this device was the same problem because they have the same Intel 
Atom processor Z8300. Here they solved the problem, I don't know if this 
solution can be ported for ASUS Vivobook E200AH.
http://forum.kodi.tv/showthread.php?tid=261371&page=3

Regards.

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1557026] Re: [SRU]Network Manager sets powersave off by default in xenial

[Jose Gómez]

In Ubuntu Xenial, with the proposed packages (1.2.0-0ubuntu0.16.04.3),
running with the laptop plugged I get:

$ sudo iwconfig wlan0 | grep "Power Management"
  Power Management:off

And with the laptop unplugged:

$ sudo iwconfig wlan0 | grep "Power Management"
  Power Management:on

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

Title:
  [SRU]Network Manager sets powersave off by default in xenial

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

Bug description:
  [Impact]
  NetworkManager consumes more power than previous releases because powersave 
support is not updated.

  [Test Case]
  With the patch applied, network device power management should be on when 
supported, for example:

  $ sudo iwconfig wlan0 | grep "Power Management"
Power Management:on

  [Regression Potential]
  Regression may happen when the power management feature of certain device 
isn't implemented properly in kernel, but since we are quite conservative on 
enabling power management in kernel development such case should be rare.

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

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

[Touch-packages] [Bug 1386237] Re: tar acl support has strange behavior when used with --xattr

[Mathew Hodson]

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

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

Title:
  tar acl support has strange behavior when used with --xattr

Status in tar package in Ubuntu:
  New

Bug description:
  as discovered in bug 1382632 (http://launchpad.net/bugs/1382632), tar's --acl 
has unexpected behaviors.
  The one that caught us there was that extracting a tar file with '--acl' that 
was created without '--acl' results in default acl being set on the top level 
extracted directory.  One would expect that if the source tar file had no acl 
information that the extracted directory would have no 'default' acl.

  I'll attach a script here that shows behavior of multiple combinations of:
    tar -c [--acl / -no-acl / default]
    tar -x [--acl / --no-acl / default ]
  and source directories with acl, without acl and with default "default" acl.

  Related Bugs:
   * bug 1382632: horizon insecure key file permissions
   * bug 1386237: tar strange behavior with --acl
   * bug 1313550: ping broken (xattrs lost in tar extraction)

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: tar 1.27.1-2
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 27 09:42:03 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-10-19 (1104 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: tar
  UpgradeStatus: Upgraded to utopic on 2013-05-20 (525 days ago)

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

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

[Touch-packages] [Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.

[Mathew Hodson]

** No longer affects: lxc (Ubuntu)

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

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

** Changed in: maas (Ubuntu Vivid)
   Status: Confirmed => Won't Fix

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

Title:
  ping does not work as a normal user on trusty tarball cloud images.

Status in curtin:
  Fix Committed
Status in MAAS:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in iputils package in Ubuntu:
  Fix Released
Status in maas package in Ubuntu:
  Fix Released
Status in tar package in Ubuntu:
  Fix Released
Status in tar source package in Precise:
  Confirmed
Status in maas source package in Saucy:
  Won't Fix
Status in tar source package in Saucy:
  Won't Fix
Status in curtin source package in Trusty:
  Fix Released
Status in maas source package in Trusty:
  Confirmed
Status in tar source package in Trusty:
  Fix Released
Status in maas source package in Vivid:
  Won't Fix
Status in maas source package in Wily:
  Fix Released

Bug description:
  With trusty, /bin/ping relies on having extended attributes and kernel
  capabilities to gain the cap_net_raw+p capability. This allows
  removing the suid bit.

  However, the tarball cloud images do not preserve the extended
  attributes, and thus /bin/ping does not work on a system derived from
  them.

  Summary of problem per package:
   * lxc: ubuntu cloud template needs to extract
   * download template needs to extract with xattr flags
   * server side download creation tools need xattr flags
   * [unconfirmed] tarball caches need creation and extraction with xattr flags
   * tar: need the '--xattr' and '--acl' flags backported
   * maas: uec2roottgz needs to use xattr/acl flags
   * curtin: extraction needs to use xattr/acl flags.
   * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags

  Related Bugs:
   * bug 1382632: horizon insecure key file permissions
   * bug 1386237: tar strange behavior with --acl and xattr
   * bug 1313550: ping broken (xattrs lost in tar extraction)

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

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

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

[Alex Bligh]

Hmm, I also found this line in my log (this time it booted OK):

Jul 12 18:41:47 redacted.example.org ntpdate[2184]: name server cannot
be used: Temporary failure in name resolution (-3)

I'm wondering whether it's either

a) failing to start ntp because ntpdate isn't running because it
couldn't resolve names because bind9 had not yet started, and the drift
was too large (sometimes)

b) (the opposite) only working when ntpdate times out if it starts its
query too early.

Seems to me like ntpdate should be waiting to start until name
resolution works - probably ntpd too.

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Confirmed

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

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

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


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

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

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

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

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

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

  What else can I do to debug this further?

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

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

[Touch-packages] [Bug 1598805] Re: implement zoom in/zoom out [desktop]

[dinamic]

nice :D i'm using CTRL + ALT + wheel in compiz

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

Title:
  implement zoom in/zoom out [desktop]

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  implement zoom in/zoom out [desktop]

  i need to zoom in/out when recording videos and since compiz is gone i
  can't do that anymore in unity8.

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

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

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

[Robie Basak]

OK, unduping for now.

** This bug is no longer a duplicate of bug 1575572
   apache2 fails to start if installed via cloud config (on Xenial)

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Confirmed

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

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

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


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

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

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

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

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

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

  What else can I do to debug this further?

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

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

[Touch-packages] [Bug 1556387] Re: Unity8 Login Hangs

[Launchpad Bug Tracker]

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

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

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

Title:
  Unity8 Login Hangs

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Attempted to Install and Login using Unity8 on top of Ubuntu 16.04 Desktop 
Build.
  Am amble to Signon to Unity Desktop distributed by build however when I 
attempt to singon to Unity8, the password accepts but the Signon Screen does 
not go away. The only thing I can do is either shutdown the machine or Restart.

  The following data is from my test image:
  gene@U1604DSKDLYX:~$ uname -a
  Linux U1604DSKDLYX 4.4.4-040404-generic #201603031931 SMP Fri Mar 4 00:34:16 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
  gene@U1604DSKDLYX:~$ sudo apt-get install unity8-desktop-session-mir
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  unity8-desktop-session-mir is already the newest version 
(1.0.12+15.10.20150609-0ubuntu1).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

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

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

[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)

[rinigus]

Happy to help! I hope you could push it to users as early as possible -
it makes such a difference to have a phone that you could use as a phone
:)

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

Title:
  Poor microphone quality (mako)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After months of complaints from people talking to me on the phone
  (mako ubuntu touch), I finally got around to use multiROM to dual boot
  Ubuntu Touch and Android. Several people can confirm that there is a
  noticable difference in terms of sound/microphone quality between
  Android and UT in phone calls. With UT, my voice gets distorted to an
  extent that person at the other end have real difficulties to hear
  what I am saying, while with Android call quality is much better with
  no distortion.

  I have had a suspicion for a long time that this might be a software
  and not a hardware issue. After trying Android and Ubuntu on the same
  hardware I believe this suspicion is proved correct. This issue has
  persisted in all the builds I have tried since at least the beginning
  of the year, but probably longer. I am now at r17 of Utopic.

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

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

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

[Alex Bligh]

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

I'm also seeing this still fail with init-system-helpers 1.29ubuntu2,
also suggesting this is not a duplicate of #1575572.

It does not seem to fail reliably, but for what it's worth this was a
clean install of 16.04 server on a fast-ish real hardware machine.

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Confirmed

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

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

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


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

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

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

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

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

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

  What else can I do to debug this further?

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

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

[Touch-packages] [Bug 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot

[John McAleely]

** No longer affects: ofono (Ubuntu RTM)

** No longer affects: unity8 (Ubuntu RTM)

** No longer affects: indicator-network (Ubuntu RTM)

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

Title:
  Hot-swapped SIMs should be detected and prompt user to reboot

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Our telephony stack doesn't support hot-swapping of SIM cards.  If a
  user hot-swaps a SIM, the telephony stack will become unusable.

  The telephony-service should detect when this happens and display a
  snap-decision informing the user that they need to restart their
  device.

  --

  the functionality is also covered in the OOBE spec pages 9/10
  
https://docs.google.com/a/canonical.com/document/d/1VajNkWbBH61iVixXJAmOvNGiG__GWQTMXGNOZijXWJw/edit#

  --

  Summary of required work:
   - enabling ofono hotswap support through environment variable
   - adding the modal dialog to unity8 side
   - modify i-network to detect the hotswapping and trickering
 the dialog from unity8

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

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

[Touch-packages] [Bug 1599754] Re: Dash restarts when refreshing News scope (VerticalJournal)

[Pat McGowan]

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

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

Title:
  Dash restarts when refreshing News scope (VerticalJournal)

Status in Canonical System Image:
  In Progress
Status in frieza:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  current build number: 15
  device name: frieza
  channel: ubuntu-touch/rc/bq-aquaris-pd.en
  last update: 2016-07-04 18:00:02
  version version: 15
  version ubuntu: 20160629
  version tag: OTA-12-rc
  version device: 20160622.0
  version custom: 20160624--41-15-vivid

  Steps:
  1.Open news scope
  2.Change the number of results in scope setting repeatedly

  actual:
  Sometimes, scopes hangs in refreshing state for ~3 minutes, then dash restarts

  expected:
  no hang and dash restart

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

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

[Touch-packages] [Bug 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot

[John McAleely]

@awe, i think the time has come to start looking at this. It has been
raised by every QA team that has reviewed Ubuntu phone devices.

Does it make sense to use this bug still, or start from fresh?

Perhaps obviously, we may only be able to deliver this on systems which
supply the necessary events (from the discussion above, that may rule
out some of our devices).

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

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

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

Title:
  Hot-swapped SIMs should be detected and prompt user to reboot

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged
Status in indicator-network package in Ubuntu RTM:
  Triaged
Status in ofono package in Ubuntu RTM:
  Triaged
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  Our telephony stack doesn't support hot-swapping of SIM cards.  If a
  user hot-swaps a SIM, the telephony stack will become unusable.

  The telephony-service should detect when this happens and display a
  snap-decision informing the user that they need to restart their
  device.

  --

  the functionality is also covered in the OOBE spec pages 9/10
  
https://docs.google.com/a/canonical.com/document/d/1VajNkWbBH61iVixXJAmOvNGiG__GWQTMXGNOZijXWJw/edit#

  --

  Summary of required work:
   - enabling ofono hotswap support through environment variable
   - adding the modal dialog to unity8 side
   - modify i-network to detect the hotswapping and trickering
 the dialog from unity8

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

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

[Touch-packages] [Bug 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws

[Treviño]

Ensure that unity-control-center is updated in your machine too. There's
a SRU for that too.

Also, the lowgfx setting in CCSM isn't enough for doing a full testing.

You can also force it by running

COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx compiz --replace

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

Title:
  Unity in low-graphics mode has animations and unneeded redraws

Status in compiz package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in compiz source package in Xenial:
  Fix Committed
Status in nux source package in Xenial:
  Fix Committed
Status in unity source package in Xenial:
  Fix Committed
Status in unity-control-center source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  When unity is in Low graphics mode (because of software rendering)
  there are still window animations and fade effects which we should get
  rid of.

  
  [Test case]

  This should apply naturally to a (virtual-)machine with no hardware
  acceleration or There are multiple ways to force low-gfx mode:

  1) Add an upstart job such as:

  cat << EOF > ~/.config/upstart/lowgfx.conf
  start on starting unity7

  pre-start script
#initctl set-env --global UNITY_LOW_GFX_MODE=1
initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1
  end script
  EOF 

  
  2) Run unity with:
 COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx

  On login unity should use opaque views (dash, switcher, launcher,
  shortcut-dialogs) with no fading and reduced effects. Windows should
  also use smaller shadows.

  
  [Regression potential]

  Some settings from unity-control-center couldn't be applied to normal
  profile. Low graphics mode might be used as normal one.

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

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

[Touch-packages] [Bug 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/account-plugins/account-plugins-
ubuntu-xenial-landing-062

** Branch linked: lp:~ci-train-bot/gnome-control-center-signon/gnome-
control-center-signon-ubuntu-xenial-landing-062

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

Title:
  [SRU] Allow plugins to decide which username to set on new accounts

Status in Online Accounts: Account plugins:
  Fix Released
Status in Canonical System Image:
  Fix Committed
Status in Online Accounts: GNOME Control Center:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in account-plugins source package in Xenial:
  Confirmed
Status in gnome-control-center-signon source package in Xenial:
  Confirmed
Status in account-plugins source package in Yakkety:
  Fix Released
Status in gnome-control-center-signon source package in Yakkety:
  Fix Released

Bug description:
  This bug is related to bug 1547647, even though it makes sense in any
  case.

  Currently, the ApOAuthPlugin class in libaccount-plugin gets the
  username from the SignonIdentity, which in turn gets it from signon-
  ui, which in the current WebKit1 implementation gets it from the DOM
  of the login webpage. This is a hack, it's fragile, not trivial to
  port to the Oxide web engine, and possibly against some providers'
  guidelines.

  We should retrieve the username using some REST API provided by the
  service, and in order to do so we need to extend libaccounts-plugin
  with some hooks which subclasses can use to get the username.

  Once we fix this we can also get rid of the files /etc/signon-ui
  /webkit-options.d/, which are conflicting with those installed by the
  KDE account plugins packages.


  SRU information
  ===

  [Impact] The same file /etc/signon-ui/webkit-
  options.d/www.facebook.com.conf is installed by the account-plugin-
  facebook package (used by Unity) and by kaccount-providers (used by
  KDE). See this bug's duplicates to see actual bug reports.

  [Test Case] Install both account-plugin-facebook and kaccount-
  providers and you'll get the conflict.

  [Regression Potential] Users running KDE will be completely unaffected
  by this. Users running Unity might see a change when creating accounts
  in System Settings->Online Accounts: with this bugfix, the account's
  display name is obtained by making a REST API call to the remote
  service, rather than by scrapping the DOM of the server webpages
  (which is a hack, and prone to errors if the providers' webpage
  changes). The new way of retrieving the username is the proper one,
  and it's been tested to work reliably. In any case, the worst thing
  that might happen is that accounts get created with an empty display
  name, which is mostly an aesthetic problem (the display name is used
  only for UI purposes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1565772/+subscriptions

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

[Touch-packages] [Bug 1602339] [NEW] Sliding answer box will make it dissapear

[marius]

Public bug reported:

When sliding by mistake the answer dialog, by touching first the area
outside the rectangle with "< >" on it, will make the whole answering
dialog disappear, so the call can't be answered anymore. The phone still
continues to ring.

** Affects: dialer-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Sliding answer box will make it dissapear

Status in dialer-app package in Ubuntu:
  New

Bug description:
  When sliding by mistake the answer dialog, by touching first the area
  outside the rectangle with "< >" on it, will make the whole answering
  dialog disappear, so the call can't be answered anymore. The phone
  still continues to ring.

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

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

[Touch-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running

[Paul Sladen]

Further discussion at:

  https://irclogs.ubuntu.com/2016/07/12/%23ubuntu-devel.html#t15:20

with a pointer to:

https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/common/crOpenGL/egl.c#L136

And side-discussion of possible better ways of how to detect client GL
vs. server GL, which at the moment is using:

  getenv("DISPLAY") != NULL

and a quick look into how the Nvidia driver packaging is handling this
in postinst using:

  update-alternatives --force --install /etc/ld.so.conf.d/x86_64-linux-
gnu_GL.conf x86_64-linux-gnu_gl_conf /usr/lib/nvidia-361/ld.so.conf 8604

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

Title:
  "low-graphics mode" in VirtualBox guest, but X server running

Status in lightdm package in Ubuntu:
  New

Bug description:
  I sometimes get the "low-graphics mode" message when starting an
  Ubuntu 16.04 virtual machine inside of VirtualBox (current development
  code trunk, somewhere past version 5.1 beta 3 and a debug build).
  When I switch to VT-7 I find the X server running without any visible
  issues (I am the upstream developer of the guest graphics drivers, so
  I have a reasonable but not infallible understanding of the X server).

  The virtual machine has Guest Additions installed, same vintage and
  also a debug build.  Two screens are enabled as is 3D acceleration.
  The host system is also Ubuntu 16.04.  I am still trying to work out
  what triggers the message, but in my last attempts a cold boot failed
  to produce it, while a clean reboot did, but only when the host system
  was not under load (under load as in building VirtualBox).

  Searching the lightdm log files led me to the message "CRITICAL **:
  session_get_login1_session_id: assertion 'session != NULL' failed",
  which in turn led me to this similar-looking Debian bug:

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  7 10:49:27 2016
  InstallationDate: Installed on 2016-06-08 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

  IRC discussion at:

https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52

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

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

[Touch-packages] [Bug 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)

[kevin gunn]

I wanted to add some information that there is a bug very very similar
to this which has been shared upstream. There is a fix from our upstream
that is currently in rc-proposed from upstream that will be rolled out
as part of the OTA12 update that is meant to help address this issue.

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

Title:
  [vegeta] Phone app makes screen stay black during call (so you can't
  hang up)

Status in Canonical System Image:
  Incomplete
Status in vegetahd:
  New
Status in powerd package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  A similar, if not the same bug, has been reported to be fixed for
  OTA6. This bug report explains that it's no necessary to wait for a
  minute or so on the phone call, but the screen turns black
  immediately, and doesn't turn back on again to allow hanging up via a
  screen control.

  Potential duplicate: https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1483127

  Device: Aquaris E5 HD Ubuntu Edition
  OS version: 15.04 (r5)

  A) Incoming phone call:
     - Accept the incoming call by sliding the grey middle button to the 
green button
     - Watch the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (continued from above, screen stays black after taking it away from 
your ear)
     - Press the screen lock/unlock button (= button above volume control)
     - Screen with phone app shows for about half a second, then turns 
black again
     - Press the screen lock/unlock button again, and try to press the red 
hangup button quickly
     - Repeat the previous step until hanging up succeeds

  B) Outbound phone call:
     - Open the phone app
     - Slide up Recent calls list from bottom edge, select a phone number
     - Press green dial button to initiate the call
     - Watch the phone dialling and the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (same procedure as in A. above)
     - Difference in behavior:
   * In some calls after pressing the lock/unlock button for the first 
time the screen stays alight (doesn't turn black again after half a second).

  
  Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list:
  In both cases, covering/uncovering the proximity sensor should turn the 
screen on, if the screen has not been turned off with the power button. (This 
is not happening.)

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

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

[Touch-packages] [Bug 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

[Chris J Arges]

Hello Steve, or anyone else affected,

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

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

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

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

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

** Tags added: verification-needed

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

Title:
  systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or
  /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB
  devices.

  It appears the regression is here:
  * Set MAC based name for USB network interfaces only for universally
  administered (i. e. stable) MACs, not for locally administered (i. e.
  randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link
  (as link files don't currently support globs for MACAddress=) and replace
  with an udev rule in /lib/udev/rules.d/73-special-net-names.rules.
  (Closes: #812575, LP: #1574483)

  As Raspberry Pi's use eth0 via USB, this breaks running systems.

  Before:
  ii  systemd229-4ubuntu4 armhfsystem and service manager
  ii  udev   229-4ubuntu4 armhf/dev/ and hotplug management daem

  3: eth0:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  After:

  ii  systemd  229-4ubuntu6armhf   
system and service manager
  ii  udev 229-4ubuntu6armhf   
/dev/ and hotplug management daemon

  3: enxb827eb1639e9:  mtu 1500 qdisc 
pfifo_fast state UP mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  cat /proc/cmdline
  dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 
bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 
smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 
vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 
rootfstype=ext4 elevator=deadline rootwait

  With the default interfaces configuration, all networking is lost on
  reboot after upgrade.

  
  SRU TEST CASE
  =
   * Boot with "net.ifnames=0" on the kernel command line, and connect an USB 
ethernet device. It will still be called enxDEADBEEF with current xenial. With 
the -proposed version it will instead keep the kernel name, like "usb0" as 
intended.

   * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules"
  (the other documented way to disable ifnames) and do the above
  connect/name check test again.

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

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

[Touch-packages] [Bug 1568094] Re: Many error message such as "Start request repeated too quickly."

[Chris J Arges]

Hello Laurent, or anyone else affected,

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

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

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

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

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

** Tags added: verification-needed

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

Title:
  Many error message such as "Start request repeated too quickly."

Status in laptop-mode-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in laptop-mode-tools source package in Xenial:
  New
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  * Analysis:

  The error messages are caused by a bad interaction between systemd and
  laptop-mode-tools.

  * Fixes:

  There is a fix in systemd:
  https://github.com/systemd/systemd/pull/3148

  The problem can also be fixed by updating laptop-mode-tools.

  * Symptoms:

  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: Starting Show Plymouth Boot Screen...
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File Sys

[Touch-packages] [Bug 1602256] Re: sometimes "systemd-coredump[]: Coredump file descriptor missing." is seen, upstream #2984

[Chris J Arges]

Hello LeK, or anyone else affected,

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

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

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

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

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

** Tags added: verification-needed

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

Title:
  sometimes "systemd-coredump[]: Coredump file descriptor missing."
  is seen, upstream #2984

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

Bug description:
  Please include this upstream fix/pull request:

  coredump: use next_datagram_size_fd instead of ioctl(FIONREAD) #3237
  https://github.com/systemd/systemd/pull/3237

  Reported as
  sometimes "systemd-coredump[]: Coredump file descriptor missing." is 
seen, upstream #2984
  https://github.com/systemd/systemd/issues/2984

  Or make a release using systemd tag=v230

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

  :~$ apt-cache policy systemd
  systemd:
    Installed: 229-4ubuntu6
    Candidate: 229-4ubuntu6
    Version table:
   *** 229-4ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  SRU INFORMATION
  ---
  This only affects systemd-coredump which we don't use in Ubuntu by default 
(we use Apport), so the regression potential is very low. There is no 
straightforward reproducer for this (see upstream bug report: 
https://github.com/systemd/systemd/issues/2984). But our systemd package has 
integration tests for coredump: 
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/tests/boot-and-services?h=ubuntu-xenial#n436
 

  Thus if the updated package still succeeds its autopkgtests, this
  should provide sufficient regression testing for this bug.

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

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

[Touch-packages] [Bug 1585406] Re: package udev 225-1ubuntu9.1 failed to install/upgrade: dpkg-maintscript-helper: error: command symlink_to_dir is unknown

[Chris J Arges]

Hello Chelmite, or anyone else affected,

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

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

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

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

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

** Tags added: verification-needed

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

Title:
  package udev 225-1ubuntu9.1 failed to install/upgrade: dpkg-
  maintscript-helper: error: command symlink_to_dir is unknown

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

Bug description:
  Died during upgrade from 15.10 x86-64.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.2.0-37.43-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CustomUdevRuleFiles: 60-vboxdrv.rules 51-android.rules 99-lexscan.rules
  Date: Tue May 24 16:29:40 2016
  DuplicateSignature: package:udev:225-1ubuntu9.1:subprocess new pre-removal 
script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2013-05-02 (1118 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Serval WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-37-generic 
root=UUID=1fc67f3a-3070-4bdf-b16d-81d1e5d68535 ro
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-05-24 (0 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Serval WS
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serw9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RS76:bd10/26/2015:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.name: Serval WS
  dmi.product.version: serw9
  dmi.sys.vendor: System76, Inc.

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

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

[Touch-packages] [Bug 1260103] Re: oxide should use an app-specific path for shared memory files

[Chris Coulson]

I would modify base::GetShmemTempDir() to lookup a path via
base::PathService and then have Oxide override this. You'll need to add
a new key in base/base_paths_posix.h as well.

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

Title:
  oxide should use an app-specific path for shared memory files

Status in Oxide:
  Triaged
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  Oxide creates shared memory files as /run/shm/.org.chromium.Chromium.*. This 
results in an AppArmor rule like the following:
owner /run/shm/.org.chromium.Chromium.* rwk, 

  But this rule is too lenient because a malicious app could enumerate
  these files and attack shared memory of other applications. Therefore,
  these paths need to be made application specific.

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

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

[Touch-packages] [Bug 1260103] Re: oxide should use an app-specific path for shared memory files

[Chris Coulson]

** Changed in: oxide
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: oxide
   Status: New => Triaged

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

Title:
  oxide should use an app-specific path for shared memory files

Status in Oxide:
  Triaged
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  Oxide creates shared memory files as /run/shm/.org.chromium.Chromium.*. This 
results in an AppArmor rule like the following:
owner /run/shm/.org.chromium.Chromium.* rwk, 

  But this rule is too lenient because a malicious app could enumerate
  these files and attack shared memory of other applications. Therefore,
  these paths need to be made application specific.

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

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

[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)

[Devid Antonio Filoni]

And of course I would like to thank you rinigus for pointing that issue
(and patch) out, you saved my day few weeks ago! ;) Thank you so much!!!

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

Title:
  Poor microphone quality (mako)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After months of complaints from people talking to me on the phone
  (mako ubuntu touch), I finally got around to use multiROM to dual boot
  Ubuntu Touch and Android. Several people can confirm that there is a
  noticable difference in terms of sound/microphone quality between
  Android and UT in phone calls. With UT, my voice gets distorted to an
  extent that person at the other end have real difficulties to hear
  what I am saying, while with Android call quality is much better with
  no distortion.

  I have had a suspicion for a long time that this might be a software
  and not a hardware issue. After trying Android and Ubuntu on the same
  hardware I believe this suspicion is proved correct. This issue has
  persisted in all the builds I have tried since at least the beginning
  of the year, but probably longer. I am now at r17 of Utopic.

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

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

[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)

[Devid Antonio Filoni]

Hi, I'm testing the patch ringius linked in comment #31 since Jun 23
without regressions and looks like mic is working fine now on my Nexus 4
(my friends reported a robot-like voice). morphis (thank you man!)
included that patch in the new libhybris version
(0.1.0+git20151016+6d424c9-0ubuntu18) which will be pushed to our
devices with OTA-13.

Bootloader version: makoz30f
Baseband version: m9615a-cefwmazm-2.0.1701.07

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

Title:
  Poor microphone quality (mako)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After months of complaints from people talking to me on the phone
  (mako ubuntu touch), I finally got around to use multiROM to dual boot
  Ubuntu Touch and Android. Several people can confirm that there is a
  noticable difference in terms of sound/microphone quality between
  Android and UT in phone calls. With UT, my voice gets distorted to an
  extent that person at the other end have real difficulties to hear
  what I am saying, while with Android call quality is much better with
  no distortion.

  I have had a suspicion for a long time that this might be a software
  and not a hardware issue. After trying Android and Ubuntu on the same
  hardware I believe this suspicion is proved correct. This issue has
  persisted in all the builds I have tried since at least the beginning
  of the year, but probably longer. I am now at r17 of Utopic.

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

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

[Touch-packages] [Bug 1599754] Re: Dash restarts when refreshing News scope (VerticalJournal)

[Albert Astals Cid]

** Branch linked: lp:~aacid/unity8/verticalJournalBug1599754

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

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

Title:
  Dash restarts when refreshing News scope (VerticalJournal)

Status in Canonical System Image:
  Triaged
Status in frieza:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  current build number: 15
  device name: frieza
  channel: ubuntu-touch/rc/bq-aquaris-pd.en
  last update: 2016-07-04 18:00:02
  version version: 15
  version ubuntu: 20160629
  version tag: OTA-12-rc
  version device: 20160622.0
  version custom: 20160624--41-15-vivid

  Steps:
  1.Open news scope
  2.Change the number of results in scope setting repeatedly

  actual:
  Sometimes, scopes hangs in refreshing state for ~3 minutes, then dash restarts

  expected:
  no hang and dash restart

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

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

[Touch-packages] [Bug 1354164] Re: No way to show power indicator for wireless mice/keyboards on desktop machines without battery

[平凡]

** Changed in: indicator-power (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  No way to show power indicator for wireless mice/keyboards on desktop
  machines without battery

Status in indicator-power package in Ubuntu:
  Fix Released

Bug description:
  I have a desktop computer running Ubuntu 14.04. Today I discovered
  that the battery status for my wireless mouse and keyboard are shown
  in the Power section of System Settings, which was very pleasing.
  However, there is no way to show the battery status in the menu bar on
  this machine. The options available for this in System Settings are:

  Show battery status in the menu bar when battery is present
  Show battery status in the menu bar when battery is charging/in use
  Show battery status in the menu bar never

  Either the batteries in my wireless keyboard and wireless mouse count
  as a "battery" for the purposes of this menu, or they don't, and I
  don't know which is true, but either way there is a bug.

  If the "Show battery status in the menu bar" dropdown menu applies to
  only a main computer battery (such as is found in a laptop) then there
  is no way to show the battery status of my wireless keyboard and mouse
  if my computer does not *have* a main computer battery (because it is
  a desktop computer plugged into mains power always). Suggested fix:
  add a new option, "when device(s) using a battery are connected",
  which would act as "Show battery status in the menu bar when battery
  is present" but also show the status in the menu bar if battery-using
  peripherals are connected.

  If the "Show battery status in the menu bar" dropdown menu applies to
  all batteries, including those in peripherals such as mice, then the
  setting is incorrectly being ignored because I do not have a power
  indicator.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug  7 21:53:35 2014
  InstallationDate: Installed on 2014-04-07 (122 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to trusty on 2014-04-25 (104 days ago)

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

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

[Touch-packages] [Bug 1582662] Re: no cellular connection and settings

[dinamic]

syslog

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1582662/+attachment/4699492/+files/syslog

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

Title:
  no cellular connection and settings

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed

Bug description:
  no cellular connection and settings (arale/rc-proposed)
  i have no idea how to reproduce this bug but it already happened 3 times to 
me, the cellular icon (indicator) is gone and also the the "Cellular" entry 
from System Settings/Network (see screenshot). when it happens i can't dial or 
receive calls. the most annoying thing is that i am not allays aware that i 
don't have cell connection since the only giveaway is the missing cell icon.

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

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