[Touch-packages] [Bug 1567776] Re: UITK segfault when running qmlplugindump on s390x on Qt 5.6

[Timo Jyrinki]

(Original changelog entry didn't have the bug numbers included)

qtdeclarative-opensource-src (5.6.1-4ubuntu1~4) yakkety; urgency=medium

  * Merge with Debian.
  * Update symbols.
  * Drop backported upstream patches now included:
- Add-QQuickAsyncImageProvider.patch
- Add-isTabFence-private-flag.patch
- Don-t-change-the-currentItem-after-a-viewport-resize.patch
- Don-t-make-currentIndex-skip-an-extra-item-on-remova.patch
- Fix-memory-leak-when-using-async-image-providers.patch
- Flickable-avoid-perturbing-the-timeline-further-whil.patch
- Image-fix-crash-when-switching-between-multiple-scre.patch
- Make-sure-we-stop-animators-if-they-are-yet-to-be-st.patch
- MultiPointTouchArea-Fixed-released-duplication-on-mo.patch
- QQuickItem-fix-an-infinite-loop-nextItemInFocusChain.patch
- WIP-QQuickItem-fix-another-infinite-loop-in-nextItem.patch
- qmlplugindump-Don-t-try-to-import-Qt.test.qtestroot.patch
  * Refresh QML cache and test binary location patches to apply.
  * Modify QML cache patch to Qt 5.6 and 5.6.1 changes. (LP: #1556824)
  * Mark private symbols.
  * Update for Qt 5.6.1:
- Drop debian/patches/Fix-crash-in-hasAtlasTexture.patch now in upstream.
  * Add build dep on libqt5opengl5-dev to execute a test successfully
  * debian/patches/V4-Always-set-the-tag-when-boxing-a-pointer-in-QV4-V.patch
debian/patches/Fix-QQmlEngine-crash-on-big-endian-64-bit-architectu.patch:
- Fix a crasher affecting s390x (LP: #1567481) (LP: #1572496) (LP: #1567776)


** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  UITK segfault when running qmlplugindump on s390x on Qt 5.6

Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Build log at:

  https://launchpadlibrarian.net/252154396/buildlog_ubuntu-xenial-s390x
  .ubuntu-ui-toolkit_1.3.1908+16.04.20160324.4+qttest-
  0ubuntu1~test3_BUILDING.txt.gz

  There is also a segfault when running tests of qtfeedback, so there
  might be some new problem with s390x with Qt 5.6. However most things
  have compiled fine for s390x.

  Information about Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1567481] Re: maliit-framework test failure on powerpc and s390x with Qt 5.6

[Timo Jyrinki]

(Original changelog entry didn't have the bug numbers included)

qtdeclarative-opensource-src (5.6.1-4ubuntu1~4) yakkety; urgency=medium

  * Merge with Debian.
  * Update symbols.
  * Drop backported upstream patches now included:
- Add-QQuickAsyncImageProvider.patch
- Add-isTabFence-private-flag.patch
- Don-t-change-the-currentItem-after-a-viewport-resize.patch
- Don-t-make-currentIndex-skip-an-extra-item-on-remova.patch
- Fix-memory-leak-when-using-async-image-providers.patch
- Flickable-avoid-perturbing-the-timeline-further-whil.patch
- Image-fix-crash-when-switching-between-multiple-scre.patch
- Make-sure-we-stop-animators-if-they-are-yet-to-be-st.patch
- MultiPointTouchArea-Fixed-released-duplication-on-mo.patch
- QQuickItem-fix-an-infinite-loop-nextItemInFocusChain.patch
- WIP-QQuickItem-fix-another-infinite-loop-in-nextItem.patch
- qmlplugindump-Don-t-try-to-import-Qt.test.qtestroot.patch
  * Refresh QML cache and test binary location patches to apply.
  * Modify QML cache patch to Qt 5.6 and 5.6.1 changes. (LP: #1556824)
  * Mark private symbols.
  * Update for Qt 5.6.1:
- Drop debian/patches/Fix-crash-in-hasAtlasTexture.patch now in upstream.
  * Add build dep on libqt5opengl5-dev to execute a test successfully
  * debian/patches/V4-Always-set-the-tag-when-boxing-a-pointer-in-QV4-V.patch
debian/patches/Fix-QQmlEngine-crash-on-big-endian-64-bit-architectu.patch:
- Fix a crasher affecting s390x (LP: #1567481) (LP: #1572496) (LP: #1567776)


** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  maliit-framework test failure on powerpc and s390x with Qt 5.6

Status in maliit-framework package in Ubuntu:
  Invalid
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  Build log at: https://launchpadlibrarian.net/252116453
  /buildlog_ubuntu-xenial-powerpc.maliit-framework_0.99.1+git20151118
  +62bd54b-0ubuntu4~xenial1~qt560~1_BUILDING.txt.gz

  https://launchpadlibrarian.net/258778769/buildlog_ubuntu-yakkety-s390x
  .maliit-framework_0.99.1+git20151118+62bd54b-
  0ubuntu4~1_BUILDING.txt.gz

  --
  FAIL!  : Ut_MInputMethodQuickPlugin::testQmlSetup(Hello world) 'not 
testee->inputMethodArea().isEmpty()' returned FALSE. ()
     Loc: [ut_minputmethodquickplugin.cpp(89)]
  --

  It passes on other architectures, including the more modern powerpc64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1567481/+subscriptions

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

[Touch-packages] [Bug 1572496] Re: s390x build/run failure with Qt 5.6 gsettings-qt and ubuntu-ui-toolkit

[Timo Jyrinki]

(Original changelog entry didn't have the bug numbers included)

qtdeclarative-opensource-src (5.6.1-4ubuntu1~4) yakkety; urgency=medium

  * Merge with Debian.
  * Update symbols.
  * Drop backported upstream patches now included:
- Add-QQuickAsyncImageProvider.patch
- Add-isTabFence-private-flag.patch
- Don-t-change-the-currentItem-after-a-viewport-resize.patch
- Don-t-make-currentIndex-skip-an-extra-item-on-remova.patch
- Fix-memory-leak-when-using-async-image-providers.patch
- Flickable-avoid-perturbing-the-timeline-further-whil.patch
- Image-fix-crash-when-switching-between-multiple-scre.patch
- Make-sure-we-stop-animators-if-they-are-yet-to-be-st.patch
- MultiPointTouchArea-Fixed-released-duplication-on-mo.patch
- QQuickItem-fix-an-infinite-loop-nextItemInFocusChain.patch
- WIP-QQuickItem-fix-another-infinite-loop-in-nextItem.patch
- qmlplugindump-Don-t-try-to-import-Qt.test.qtestroot.patch
  * Refresh QML cache and test binary location patches to apply.
  * Modify QML cache patch to Qt 5.6 and 5.6.1 changes. (LP: #1556824)
  * Mark private symbols.
  * Update for Qt 5.6.1:
- Drop debian/patches/Fix-crash-in-hasAtlasTexture.patch now in upstream.
  * Add build dep on libqt5opengl5-dev to execute a test successfully
  * debian/patches/V4-Always-set-the-tag-when-boxing-a-pointer-in-QV4-V.patch
debian/patches/Fix-QQmlEngine-crash-on-big-endian-64-bit-architectu.patch:
- Fix a crasher affecting s390x (LP: #1567481) (LP: #1572496) (LP: #1567776)


** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  s390x build/run failure with Qt 5.6 gsettings-qt and ubuntu-ui-toolkit

Status in gsettings-qt package in Ubuntu:
  Invalid
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Ubuntu UI Toolkit FTBFS:s on s390x when used with Qt 5.6:
  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-011/+build/9600469 (Error: SEGV)

  gsettings-qt segmentation fault is similar and may be faster to debug
  https://launchpadlibrarian.net/254348976/buildlog_ubuntu-xenial-s390x
  .gsettings-
  qt_0.1+16.04.20160329-0ubuntu2~xenialoverlay1~2_BUILDING.txt.gz

  It is probably during executing 'qmlplugindump' (via build time Qt
  generated wrapper.sh script), which is from qtdeclarative-opensource-
  src.

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1615401] Re: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Steve Langasek]

The error in the log is:

> Setting up sysv-rc (2.88dsf-59.3ubuntu2) ...
> info: Reordering boot system, log to /var/lib/insserv/run-20160821T0837.log
> error: Something failed while migrating.

Please attach the indicated /var/lib/insserv/run-20160821T0837.log file.

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

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

Title:
  package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in sysvinit package in Ubuntu:
  Incomplete

Bug description:
  error indicated that the system would be in an unstable state

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 08:37:35 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-08-30 (722 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: sysvinit
  Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-21 (0 days ago)

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

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

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Douglas Santos]

Aravind Gopal, I think you should try a fresh install. I have a Epson
L355 working fine and Google Earth x64 working with a small issue
(sometimes it closes right after launching, but on the 2nd time it
works...).

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1615463] Re: package libfontconfig1:i386 2.11.94-0ubuntu1.1 failed to install/upgrade: package libfontconfig1:i386 is already installed and configured

[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 fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1615463

Title:
  package libfontconfig1:i386 2.11.94-0ubuntu1.1 failed to
  install/upgrade: package libfontconfig1:i386 is already installed and
  configured

Status in fontconfig package in Ubuntu:
  New

Bug description:
  bug reported at startup.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libfontconfig1:i386 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Thu Aug 18 10:46:24 2016
  DuplicateSignature:
   package:libfontconfig1:i386:2.11.94-0ubuntu1.1
   Processing triggers for ufw (0.35-0ubuntu2) ...
   dpkg: error processing package fontconfig-config (--configure):
package fontconfig-config is already installed and configured
  ErrorMessage: package libfontconfig1:i386 is already installed and configured
  InstallationDate: Installed on 2016-08-13 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package libfontconfig1:i386 2.11.94-0ubuntu1.1 failed to 
install/upgrade: package libfontconfig1:i386 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1615463] [NEW] package libfontconfig1:i386 2.11.94-0ubuntu1.1 failed to install/upgrade: package libfontconfig1:i386 is already installed and configured

[kamal pradhan]

Public bug reported:

bug reported at startup.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libfontconfig1:i386 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Thu Aug 18 10:46:24 2016
DuplicateSignature:
 package:libfontconfig1:i386:2.11.94-0ubuntu1.1
 Processing triggers for ufw (0.35-0ubuntu2) ...
 dpkg: error processing package fontconfig-config (--configure):
  package fontconfig-config is already installed and configured
ErrorMessage: package libfontconfig1:i386 is already installed and configured
InstallationDate: Installed on 2016-08-13 (8 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: fontconfig
Title: package libfontconfig1:i386 2.11.94-0ubuntu1.1 failed to 
install/upgrade: package libfontconfig1:i386 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed apport-package i386 xenial

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

Title:
  package libfontconfig1:i386 2.11.94-0ubuntu1.1 failed to
  install/upgrade: package libfontconfig1:i386 is already installed and
  configured

Status in fontconfig package in Ubuntu:
  New

Bug description:
  bug reported at startup.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libfontconfig1:i386 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Thu Aug 18 10:46:24 2016
  DuplicateSignature:
   package:libfontconfig1:i386:2.11.94-0ubuntu1.1
   Processing triggers for ufw (0.35-0ubuntu2) ...
   dpkg: error processing package fontconfig-config (--configure):
package fontconfig-config is already installed and configured
  ErrorMessage: package libfontconfig1:i386 is already installed and configured
  InstallationDate: Installed on 2016-08-13 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package libfontconfig1:i386 2.11.94-0ubuntu1.1 failed to 
install/upgrade: package libfontconfig1:i386 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

[Rahul]

Confirmed Fix on #5,works permanently on Ubuntu 16.04

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

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

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

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Aravind Gopal]

Google earth also not working..

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1604701] Re: Animated cursors don't animate in Unity8

[Daniel van Vugt]

Sorry, I should have tested it. But The new qtmir release in yakkety with:
   lp:~dandrader/qtmir/consecutiveCustomCursors

Does not fix this bug at all. If anything it's now much worse (cursor
not only doesn't animate but also pauses and stops responding to
movement too).

** Changed in: qtmir (Ubuntu)
   Status: Fix Released => Triaged

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

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

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

** Changed in: qtmir (Ubuntu)
 Assignee: Daniel d'Andrada (dandrader) => (unassigned)

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

Title:
  Animated cursors don't animate in Unity8

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

Bug description:
  Animated cursors don't animate in Unity8.

  Test case:
   mir_demo_client_animated_cursor -- --desktop_file_hint=unity8

  Works in Mir demo servers but not in Unity8.

  I mentioned this in bug 1447839 but that one appears to have closed
  prematurely.

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

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

[Touch-packages] [Bug 1540702] Re: While resizing Qt apps window contents jitter about erratically (including during animations)

[Daniel van Vugt]

I think the web browser's resizing is uniquely broken in ways not seen
in other apps. It might be better to discuss browser resizing in bug
1585278 instead.

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

Title:
  While resizing Qt apps window contents jitter about erratically
  (including during animations)

Status in Canonical System Image:
  Confirmed
Status in QtMir:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Resizing a window (Scopes) the window contents jitter about
  erratically. Obviously they should appear to remain stationary unless
  being significantly repositioned.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160129-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Tue Feb  2 10:23:02 2016
  InstallationDate: Installed on 2015-12-03 (60 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.unity8-dash.log:
   ubuntumirclient: Got invalid serialized mime data. Ignoring it.
   ubuntumirclient: Got invalid serialized mime data. Ignoring it.
   ubuntumirclient: Got invalid serialized mime data. Ignoring it.

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

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

[Touch-packages] [Bug 1585278] Re: Browser window does not fill the screen width when starting

[Daniel van Vugt]

The browser seems to be more broken than other apps in resizing so
probably needs a fix all of its own. So that's this bug.

The more general resize problem is covered by bug 1540702.

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

Title:
  Browser window does not fill the screen width when starting

Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  bq M10 rc-proposed r112

  When staring Browser app in landscape first I see splash screen, then the 
Browser window which is squared and then the complete Browser window with tabs 
opened. For the beter UX the second step should be skipped or that window 
should take the full width of the tablet. 
  Screenshot of the problem attached.

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

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

[Touch-packages] [Bug 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]

[Daniel van Vugt]

Fix reapplied in lp:qtubuntu r335 and now fix released to yakkety in:
  qtubuntu 0.63+16.10.20160809-0ubuntu1

** Changed in: qtubuntu
   Status: Triaged => Fix Released

** Changed in: qtubuntu (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: qtdeclarative (Ubuntu)
   Status: Confirmed => Invalid

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

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

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

** Tags added: unity8-desktop

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

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

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

Title:
  Unity8-dash on Intel Atom graphics crashes and restarts continuously
  [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) ==
  EGL_TRUE"]

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Invalid
Status in qtubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtdeclarative package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in qtubuntu package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Qt clients are failing to create an egl context when running on Intel
  Diamondville and Pineview, but not Cherryview systems under Mir.

  eglCreateContext fails with a EGL_BAD_MATCH error code.

  When it fails, Qt tries to delete & recreate the context, which then
  crashes the client (bug 1580118)

  === Original bug description ===
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.12+16.04.201604.01.1
  Version of Mir : 0.21

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

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

[Touch-packages] [Bug 1603091] Re: mir_test_framework::server_platform_path(), mir_test_framework::server_platform() don't support use in a downstream test built against mir-test-assist

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mir_test_framework::server_platform_path(),
  mir_test_framework::server_platform() don't support use in a
  downstream test built against mir-test-assist

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  These functions assume the platform path/library is built or installed
  relative to the executable.

  This is not the case for a downstream executable being built against
  an installed version of Mir.

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

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

[Touch-packages] [Bug 1581385] Re: [testsfail] in MirSurfaceVisibilityEvent.exposed_received_when_surface_raised_over_occluding_surface [never called]

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [testsfail] in
  
MirSurfaceVisibilityEvent.exposed_received_when_surface_raised_over_occluding_surface
  [never called]

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  This is the same test failing as we had in as lp:1556045, but details
  are different ("never called" here vs "called twice" there).

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1067/consoleFull

  17:30:23 11: [ RUN ] 
MirSurfaceVisibilityEvent.exposed_received_when_surface_raised_over_occluding_surface
  17:30:23 11: [2016-05-11 17:30:23.826743] mirserver: Starting
  17:30:23 11: [2016-05-11 17:30:23.831572] mirserver: Selected driver: dummy 
(version 0.23.0)
  17:30:23 11: [2016-05-11 17:30:23.875837] mirserver: Using software cursor
  17:30:23 11: [2016-05-11 17:30:23.883206] mirserver: Initial display 
configuration:
  17:30:23 11: [2016-05-11 17:30:23.883871] mirserver: 1.1: VGA 0.0" 0x0mm
  17:30:23 11: [2016-05-11 17:30:23.884094] mirserver: Current mode 1600x1600 
60.00Hz
  17:30:23 11: [2016-05-11 17:30:23.884285] mirserver: Preferred mode 1600x1600 
60.00Hz
  17:30:23 11: [2016-05-11 17:30:23.884441] mirserver: Logical position +0+0
  17:30:23 11: [2016-05-11 17:30:23.919692] mirserver: Selected input driver: 
mir:stub-input (version: 0.23.0)
  17:30:23 11: [2016-05-11 17:30:23.922070] mirserver: Mir version 0.23.0
  17:30:26 11: 
/��BUILDDIR��/mir-0.23.0+xenial1095bzr3507/tests/acceptance-tests/test_client_surface_visibility.cpp:135:
 Failure
  17:30:26 11: Actual function call count doesn't match EXPECT_CALL(callback, 
handle(surface, visibility))...
  17:30:26 11: Expected: to be called once
  17:30:26 11: Actual: never called - unsatisfied and active
  17:30:26 11: [2016-05-11 17:30:26.907873] mirserver: Stopping
  17:30:26 11: [ FAILED ] 
MirSurfaceVisibilityEvent.exposed_received_when_surface_raised_over_occluding_surface
 (3128 ms)

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

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

[Touch-packages] [Bug 1587604] Re: ClientCredsTestFixture.session_authorizer_receives_pid_of_connecting_clients failure

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  ClientCredsTestFixture.session_authorizer_receives_pid_of_connecting_clients
  failure

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  with lp:mir, running:

  tools/detect_fd_leaks.bash valgrind --trace-children=yes --leak-
  check=full --show-leak-kinds=definite --errors-for-leak-kinds=definite
  --track-fds=yes --num-callers=128 nbuild/bin/mir_acceptance_tests
  --gtest_filter="ClientCredsTestFi*"

  alongside
  stress -c 12 -i 3 

  can produce a failure like:
  Note: Google Test filter = ClientCredsTestFi*
  [==] Running 2 tests from 1 test case.
  [--] Global test environment set-up.
  [--] 2 tests from ClientCredsTestFixture
  [ RUN ] 
ClientCredsTestFixture.session_authorizer_receives_pid_of_connecting_clients
  unknown file: Failure
  C++ exception with description "Poll on readfd for pipe timed out" thrown in 
the test body.

  
  and, if running under CI, will time-out, and report a fd leak.

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

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

[Touch-packages] [Bug 1583536] Re: mirtest-dev is hard to use as the objects used are compiled with LTO

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mirtest-dev is hard to use as the objects used are compiled with LTO

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Linking against mirtest-dev in a downstream project fails as no
  symbols are not found in the archive.

  nm -gC /usr/lib/x86_64-linux-gnu/libmir-test-assist.a

  gives lots of "nm: FOO.cpp.o: plugin needed to handle lto object"
  errors

  Replacing the archive with one built without LTO fixes the problems.

  Adding LTO to the downstream project didn't.

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

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

[Touch-packages] [Bug 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Need to support pointer confinement in Mir and toolkits using Mir

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in MirAL:
  Triaged
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  We need to support pointer confinement set by the client. This way we
  can generate relative mouse events on a surface without the cursor
  being able to leave the edge of the window.

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

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

[Touch-packages] [Bug 1602646] Re: [testsfail] failure in NestedInput.on_input_device_state_nested_server_emits_input_device_state

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [testsfail] failure in
  NestedInput.on_input_device_state_nested_server_emits_input_device_state

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  builders fail (more often than not) on 
  NestedInput.on_input_device_state_nested_server_emits_input_device_state

  eg: https://launchpadlibrarian.net/272753315/buildlog_ubuntu-yakkety-
  amd64.mir_0.24.0+16.10.20160713-0ubuntu1_BUILDING.txt.gz

  Can be reproduced easily with stress.

  If this is indicative of a production code problem, it should be fixed
  for 0.24. If its a racy test that's failing often in builder, it'll
  probably also have to be fixed for the 0.24 release.

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

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

[Touch-packages] [Bug 1583532] Re: mir_demo_client_eglplasma falls back to software rendering on i915 (Intel Atoms), which explains why it's so slow

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mir_demo_client_eglplasma falls back to software rendering on i915
  (Intel Atoms), which explains why it's so slow

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  mir_demo_client_eglplasma falls back to software rendering on i915
  (e.g. Intel Atom systems), which explains why it's so slow...

  env INTEL_DEBUG=perf mir_demo_client_eglplasma
  ...
  i915_program_error: Program contains too many instructions
  i915_program_error: Program contains too many instructions
  i915_program_error: Program contains too many instructions
  i915_program_error: Program contains too many instructions
  i915_program_error: Program contains too many instructions
  i915_program_error: Program contains too many instructions
  i915_program_error: Program contains too many instructions
  i915_program_error: Exceeded max ALU instructions (96 out of 64)
  ENTER FALLBACK 1: Program

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

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

[Touch-packages] [Bug 1581368] Re: [regression] MIR_CLIENT_PERF_REPORT is showing bogus render times and buffer lag

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] MIR_CLIENT_PERF_REPORT is showing bogus render times and
  buffer lag

Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  MIR_CLIENT_PERF_REPORT is showing bogus render times:

  $ env MIR_CLIENT_PERF_REPORT=log bin/mir_demo_client_egltriangle
  ...
  [2016-05-13 16:20:12.972236] perf: mir_demo_client_egltriangle.bin: 62.68 
FPS, render time 23216586.29ms, buffer lag 0.00ms (3 buffers)
  [2016-05-13 16:20:13.973084] perf: mir_demo_client_egltriangle.bin: 60.00 
FPS, render time 23217610.93ms, buffer lag 0.00ms (3 buffers)
  [2016-05-13 16:20:14.973926] perf: mir_demo_client_egltriangle.bin: 60.00 
FPS, render time 23218611.88ms, buffer lag 0.00ms (3 buffers)
  ^CSignal 2 received. Good night.

  I haven't bisected it yet but know:
  FAULTY: Mir 0.24 lp:mir
  WORKING: Mir 0.21 (xenial)

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

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

[Touch-packages] [Bug 1584605] Re: [ FAILED ] ClientLogging.reports_performance (Value of: render)

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [ FAILED ] ClientLogging.reports_performance (Value of: render)

Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  10:32:32 9: [ RUN ] ClientLogging.reports_performance
  10:32:32 9: [2016-05-20 10:32:32.094437] mirserver: Starting
  10:32:32 9: [2016-05-20 10:32:32.101512] mirserver: Selected driver: dummy 
(version 0.23.0)
  10:32:32 9: [2016-05-20 10:32:32.146166] mirserver: Initial display 
configuration:
  10:32:32 9: [2016-05-20 10:32:32.146653] mirserver: 1.1: VGA 0.0" 0x0mm
  10:32:32 9: [2016-05-20 10:32:32.146953] mirserver: Current mode 1600x1600 
60.00Hz
  10:32:32 9: [2016-05-20 10:32:32.147272] mirserver: Preferred mode 1600x1600 
60.00Hz
  10:32:32 9: [2016-05-20 10:32:32.147527] mirserver: Logical position +0+0
  10:32:32 9: [2016-05-20 10:32:32.151831] mirserver: Using software cursor
  10:32:32 9: [2016-05-20 10:32:32.188313] mirserver: Selected input driver: 
mir:stub-input (version: 0.23.0)
  10:32:32 9: [2016-05-20 10:32:32.190056] mirserver: Mir version 0.23.0
  10:32:43 9: 
/��BUILDDIR��/mir-0.23.0+vivid1136bzr3514/tests/acceptance-tests/test_client_logging.cpp:114:
 Failure
  10:32:46 9: Value of: render
  10:32:47 9: Expected: is < 100
  10:32:47 9: Actual: 696.43 (of type float)
  10:32:47 9: 
/��BUILDDIR��/mir-0.23.0+vivid1136bzr3514/tests/acceptance-tests/test_client_logging.cpp:115:
 Failure
  10:32:47 9: Value of: lag
  10:32:47 9: Expected: is > 50
  10:32:47 9: Actual: 0 (of type float)
  10:32:47 9: 
/��BUILDDIR��/mir-0.23.0+vivid1136bzr3514/tests/acceptance-tests/test_client_logging.cpp:117:
 Failure
  10:32:47 9: Value of: Test::HasFailure()
  10:32:47 9: Actual: true
  10:32:47 9: Expected: false
  10:32:47 9: Log line = {[StringStreamLogger] perf: Rumpelstiltskin: 1.41 FPS, 
render time 696.43ms, buffer lag 0.00ms (3 buffers)}
  10:32:47 9: [ FAILED ] ClientLogging.reports_performance (8692 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/1107/consoleFull

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

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

[Touch-packages] [Bug 1253486] Re: memory leaks in unit tests on android

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  memory leaks in unit tests on android

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  description:
  memory leaks in unit tests on android

  steps:
  run unit tests with valgrind on armhf

  expected results:
  no leaks

  actual results:
  memory leaks

  full logs at:
  
https://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-trusty-armhf-ci/139/console

  ==23292== HEAP SUMMARY:
  ==23292== in use at exit: 2,393 bytes in 31 blocks
  ==23292== total heap usage: 1,022,708 allocs, 1,022,677 frees, 52,791,074 
bytes allocated
  ==23292==
  ==23292== LEAK SUMMARY:
  ==23292== definitely lost: 160 bytes in 2 blocks
  ==23292== indirectly lost: 0 bytes in 0 blocks
  ==23292== possibly lost: 22 bytes in 1 blocks
  ==23292== still reachable: 2,211 bytes in 28 blocks
  ==23292== suppressed: 0 bytes in 0 blocks
  ==23292== Rerun with --leak-check=full to see details of leaked memory
  ==23292==
  ==23292== For counts of detected and suppressed errors, rerun with: -v
  ==23292== Use --track-origins=yes to see where uninitialised values come from
  ==23292== ERROR SUMMARY: 664 errors from 10 contexts (suppressed: 5 from 3)

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

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

[Touch-packages] [Bug 1583970] Re: [testsfail] ClientLogging.reports_performance [Value of: lag]

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [testsfail] ClientLogging.reports_performance [Value of: lag]

Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Doesn't seem to be quite the same thing as lp:1563148 (although
  probably related to the same underlying dependence on realtime).

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1095/consoleFull

  17:18:25 13: [ RUN ] ClientLogging.reports_performance
  17:18:25 13: [2016-05-19 17:18:25.480624] mirserver: Starting
  17:18:25 13: [2016-05-19 17:18:25.483906] mirserver: Selected driver: dummy 
(version 0.23.0)
  17:18:25 13: [2016-05-19 17:18:25.517901] mirserver: Using software cursor
  17:18:25 13: [2016-05-19 17:18:25.523291] mirserver: Initial display 
configuration:
  17:18:25 13: [2016-05-19 17:18:25.523635] mirserver: 1.1: VGA 0.0" 0x0mm
  17:18:25 13: [2016-05-19 17:18:25.523889] mirserver: Current mode 1600x1600 
60.00Hz
  17:18:25 13: [2016-05-19 17:18:25.524090] mirserver: Preferred mode 1600x1600 
60.00Hz
  17:18:25 13: [2016-05-19 17:18:25.524267] mirserver: Logical position +0+0
  17:18:25 13: [2016-05-19 17:18:25.551303] mirserver: Selected input driver: 
mir:stub-input (version: 0.23.0)
  17:18:25 13: [2016-05-19 17:18:25.552840] mirserver: Mir version 0.23.0
  17:18:29 13: 
/��BUILDDIR��/mir-0.23.0+xenial1124bzr3512/tests/acceptance-tests/test_client_logging.cpp:115:
 Failure
  17:18:29 13: Value of: lag
  17:18:29 13: Expected: is > 50
  17:18:29 13: Actual: 20.89 (of type float)
  17:18:29 13: 
/��BUILDDIR��/mir-0.23.0+xenial1124bzr3512/tests/acceptance-tests/test_client_logging.cpp:117:
 Failure
  17:18:29 13: Value of: Test::HasFailure()
  17:18:29 13: Actual: true
  17:18:29 13: Expected: false
  17:18:29 13: Log line = {[StringStreamLogger] perf: Rumpelstiltskin: 8.56 
FPS, render time 3.67ms, buffer lag 20.89ms (3 buffers)}
  17:18:29 13: [ FAILED ] ClientLogging.reports_performance (4524 ms)

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

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

[Touch-packages] [Bug 1598267] Re: [regression] x11 platform only draws to a small part of the x11 window

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] x11 platform only draws to a small part of the x11 window

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  When the X11 platform is used mir only draws into a small portion of
  the x11 window. Also the reported resolution is way smaller than the
  window.

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

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

[Touch-packages] [Bug 1602966] Re: [regression] The Super/Windows key doesn't work any more

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] The Super/Windows key doesn't work any more

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  [regression] Zoom/contrast/negative desktop effects don't work any
  more in mir_proving_server on lp:mir.

  That's Super + mousewheel,C,N respectively

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

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

[Touch-packages] [Bug 1582066] Re: --display-report=log shows some invalid uninitialized EGL attribute values

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  --display-report=log shows some invalid uninitialized EGL attribute
  values

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  I noticed the value 77 appears a bit too often, and it is a bug...

  $ sudo env EGL_LOG_LEVEL=debug mir_demo_server --display-report=log
  ...
  [2016-05-16 11:30:50.561021] graphics: Display EGL Configuration:
  [2016-05-16 11:30:50.561034] graphics: [EGL_BUFFER_SIZE] : 24
  [2016-05-16 11:30:50.561037] graphics: [EGL_ALPHA_SIZE] : 0
  [2016-05-16 11:30:50.561041] graphics: [EGL_BLUE_SIZE] : 8
  [2016-05-16 11:30:50.561044] graphics: [EGL_GREEN_SIZE] : 8
  [2016-05-16 11:30:50.561047] graphics: [EGL_RED_SIZE] : 8
  [2016-05-16 11:30:50.561050] graphics: [EGL_DEPTH_SIZE] : 0
  [2016-05-16 11:30:50.561052] graphics: [EGL_STENCIL_SIZE] : 0
  [2016-05-16 11:30:50.561056] graphics: [EGL_CONFIG_CAVEAT] : 12344
  [2016-05-16 11:30:50.561060] graphics: [EGL_CONFIG_ID] : 11
  [2016-05-16 11:30:50.561063] graphics: [EGL_LEVEL] : 0
  [2016-05-16 11:30:50.561066] graphics: [EGL_MAX_PBUFFER_HEIGHT] : 0
  [2016-05-16 11:30:50.561070] graphics: [EGL_MAX_PBUFFER_PIXELS] : 0
  [2016-05-16 11:30:50.561074] graphics: [EGL_MAX_PBUFFER_WIDTH] : 0
  [2016-05-16 11:30:50.561077] graphics: [EGL_NATIVE_RENDERABLE] : 1
  [2016-05-16 11:30:50.561080] graphics: [EGL_NATIVE_VISUAL_ID] : 875713112
  [2016-05-16 11:30:50.561084] graphics: [EGL_NATIVE_VISUAL_TYPE] : 12344
  [2016-05-16 11:30:50.561088] graphics: [EGL_SAMPLES] : 0
  [2016-05-16 11:30:50.561091] graphics: [EGL_SAMPLE_BUFFERS] : 0
  [2016-05-16 11:30:50.561094] graphics: [EGL_SURFACE_TYPE] : 4
  [2016-05-16 11:30:50.561098] graphics: [EGL_TRANSPARENT_TYPE] : 12344
  [2016-05-16 11:30:50.561101] graphics: [EGL_TRANSPARENT_BLUE_VALUE] : 0
  [2016-05-16 11:30:50.561104] graphics: [EGL_TRANSPARENT_GREEN_VALUE] : 0
  [2016-05-16 11:30:50.561108] graphics: [EGL_TRANSPARENT_RED_VALUE] : 0
  [2016-05-16 11:30:50.56] graphics: [EGL_BIND_TO_TEXTURE_RGB] : 0
  [2016-05-16 11:30:50.561114] graphics: [EGL_BIND_TO_TEXTURE_RGBA] : 0
  [2016-05-16 11:30:50.561117] graphics: [EGL_MIN_SWAP_INTERVAL] : 0
  [2016-05-16 11:30:50.561121] graphics: [EGL_MAX_SWAP_INTERVAL] : 0
  [2016-05-16 11:30:50.561124] graphics: [EGL_LUMINANCE_SIZE] : 0
  [2016-05-16 11:30:50.561127] graphics: [EGL_ALPHA_MASK_SIZE] : 0
  [2016-05-16 11:30:50.561130] graphics: [EGL_COLOR_BUFFER_TYPE] : 12430
  [2016-05-16 11:30:50.561134] graphics: [EGL_RENDERABLE_TYPE] : 77
  libEGL debug: EGL user error 0x3004 (EGL_BAD_ATTRIBUTE) in eglGetConfigAttrib

  [2016-05-16 11:30:50.561140] graphics: [EGL_MATCH_NATIVE_PIXMAP] : 77
  [2016-05-16 11:30:50.561144] graphics: [EGL_CONFORMANT] : 77
  libEGL debug: EGL user error 0x3004 (EGL_BAD_ATTRIBUTE) in eglGetConfigAttrib

  [2016-05-16 11:30:50.561149] graphics: [EGL_SLOW_CONFIG] : 77
  libEGL debug: EGL user error 0x3004 (EGL_BAD_ATTRIBUTE) in eglGetConfigAttrib

  [2016-05-16 11:30:50.561154] graphics: [EGL_NON_CONFORMANT_CONFIG] : 77
  libEGL debug: EGL user error 0x3004 (EGL_BAD_ATTRIBUTE) in eglGetConfigAttrib

  [2016-05-16 11:30:50.561158] graphics: [EGL_TRANSPARENT_RGB] : 77
  libEGL debug: EGL user error 0x3004 (EGL_BAD_ATTRIBUTE) in eglGetConfigAttrib

  [2016-05-16 11:30:50.561162] graphics: [EGL_RGB_BUFFER] : 77
  libEGL debug: EGL user error 0x3004 (EGL_BAD_ATTRIBUTE) in eglGetConfigAttrib

  [2016-05-16 11:30:50.561167] graphics: [EGL_LUMINANCE_BUFFER] : 77
  libEGL debug: EGL user error 0x3004 (EGL_BAD_ATTRIBUTE) in eglGetConfigAttrib

  [2016-05-16 11:30:50.561171] graphics:
  [EGL_FRAMEBUFFER_TARGET_ANDROID] : 77

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

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

[Touch-packages] [Bug 1576760] Re: [testsfail] NestedServer.when_monitor_plugged_in_client_is_notified_of_new_display_configuration

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [testsfail]
  
NestedServer.when_monitor_plugged_in_client_is_notified_of_new_display_configuration

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/988/consoleFull

  
  14:35:03 11: [ RUN ] 
NestedServer.when_monitor_plugged_in_client_is_notified_of_new_display_configuration
  14:35:03 11: [2016-04-29 14:35:03.286577] mirserver: Starting
  14:35:03 11: [2016-04-29 14:35:03.292398] mirserver: Selected driver: dummy 
(version 0.23.0)
  14:35:03 11: [2016-04-29 14:35:03.387793] mirserver: Using software cursor
  14:35:03 11: [2016-04-29 14:35:03.461134] mirserver: Selected input driver: 
mir:stub-input (version: 0.23.0)
  14:35:03 11: [2016-04-29 14:35:03.464205] mirserver: Mir version 0.23.0
  14:35:03 11: [2016-04-29 14:35:03.519323] mirserver: Starting
  14:35:03 11: [2016-04-29 14:35:03.601671] mirserver: Using nested cursor
  14:35:04 11: [2016-04-29 14:35:04.204721] mirserver: Initial display 
configuration:
  14:35:04 11: [2016-04-29 14:35:04.220584] mirserver: 1.1: VGA 0.0" 0x0mm
  14:35:04 11: [2016-04-29 14:35:04.223951] mirserver: Current mode 640x480 
60.00Hz
  14:35:04 11: [2016-04-29 14:35:04.224285] mirserver: Preferred mode 640x480 
60.00Hz
  14:35:04 11: [2016-04-29 14:35:04.224558] mirserver: Logical position +0+0
  14:35:04 11: [2016-04-29 14:35:04.225189] mirserver: 1.2: VGA 0.0" 0x0mm
  14:35:04 11: [2016-04-29 14:35:04.225510] mirserver: Current mode 1920x1080 
60.00Hz
  14:35:04 11: [2016-04-29 14:35:04.225794] mirserver: Preferred mode 1920x1080 
60.00Hz
  14:35:04 11: [2016-04-29 14:35:04.226046] mirserver: Logical position +640+0
  14:35:04 11: [2016-04-29 14:35:04.267754] mirserver: Mir version 0.23.0
  14:35:05 11: [2016-04-29 14:35:05.004565] mirserver: New display 
configuration:
  14:35:05 11: [2016-04-29 14:35:05.005621] mirserver: 1.1: VGA 0.0" 0x0mm
  14:35:05 11: [2016-04-29 14:35:05.005929] mirserver: Current mode 640x480 
60.00Hz
  14:35:05 11: [2016-04-29 14:35:05.006339] mirserver: Preferred mode 640x480 
60.00Hz
  14:35:05 11: [2016-04-29 14:35:05.008157] mirserver: Logical position +0+0
  14:35:05 11: [2016-04-29 14:35:05.009499] mirserver: 1.2: VGA 0.0" 0x0mm
  14:35:05 11: [2016-04-29 14:35:05.011271] mirserver: Current mode 1920x1080 
60.00Hz
  14:35:05 11: [2016-04-29 14:35:05.012256] mirserver: Preferred mode 1920x1080 
60.00Hz
  14:35:05 11: [2016-04-29 14:35:05.013489] mirserver: Logical position +0+0
  14:35:05 11: [2016-04-29 14:35:05.014507] mirserver: 1.3: VGA 0.0" 0x0mm
  14:35:05 11: [2016-04-29 14:35:05.014809] mirserver: Current mode 640x480 
60.00Hz
  14:35:05 11: [2016-04-29 14:35:05.016170] mirserver: Preferred mode 640x480 
60.00Hz
  14:35:05 11: [2016-04-29 14:35:05.016449] mirserver: Logical position +0+0
  14:35:05 11: 
/��BUILDDIR��/mir-0.23.0+xenial1015bzr3478/tests/acceptance-tests/test_nested_mir.cpp:1076:
 Failure
  14:35:06 11: Value of: client_config_changed.raised()
  14:35:06 11: Actual: false
  14:35:06 11: Expected: true
  14:35:06 11: [2016-04-29 14:35:06.070023] mirserver: Stopping
  14:35:06 11: [2016-04-29 14:35:06.397423] mirserver: Stopping
  14:35:06 11: [ FAILED ] 
NestedServer.when_monitor_plugged_in_client_is_notified_of_new_display_configuration
 (3260 ms)

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

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

[Touch-packages] [Bug 1576690] Re: [testsfail] ClientLatency.triple_buffered_client_has_less_than_two_frames_latency

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [testsfail]
  ClientLatency.triple_buffered_client_has_less_than_two_frames_latency

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  lp:1509291 & lp:1554572 are "Fix Released" but...

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/987/consoleFull

  12:02:55 14: [ RUN  ] 
ClientLatency.triple_buffered_client_has_less_than_two_frames_latency
  12:02:55 14: [2016-04-29 12:02:55.779524] mirserver: Starting
  12:02:55 14: [2016-04-29 12:02:55.779973] mirserver: Selected driver: dummy 
(version 0.23.0)
  12:02:55 14: [2016-04-29 12:02:55.785579] mirserver: Using software cursor
  12:02:55 14: [2016-04-29 12:02:55.786033] mirserver: Initial display 
configuration:
  12:02:55 14: [2016-04-29 12:02:55.791067] mirserver: Selected input driver: 
mir:stub-input (version: 0.23.0)
  12:02:55 14: [2016-04-29 12:02:55.791323] mirserver: Mir version 0.23.0
  12:02:57 14: [  debug   ] 98 frames sampled, averaging 2.6 frames latency
  12:02:57 14: [  debug   ]  0:  2  2  2  2  2  2  2  2  2  2
  12:02:57 14: [  debug   ] 10:  2  2  2  2  2  2  2  2  2  2
  12:02:57 14: [  debug   ] 20:  2  2  2  2  2  2  2  2  2  2
  12:02:57 14: [  debug   ] 30:  2  2  2  2  2  2  2  2  2  2
  12:02:57 14: [  debug   ] 40:  3  3  3  3  3  3  3  3  3  3
  12:02:57 14: [  debug   ] 50:  3  3  2  3  3  3  3  3  3  3
  12:02:57 14: [  debug   ] 60:  3  3  3  3  3  3  3  3  3  3
  12:02:57 14: [  debug   ] 70:  3  3  3  3  3  3  3  3  3  3
  12:02:57 14: [  debug   ] 80:  3  3  3  3  3  3  3  3  3  3
  12:02:57 14: [  debug   ] 90:  3  3  3  3  3  3  3  3
  12:02:57 14: 
/��BUILDDIR��/mir-0.23.0+xenial1014bzr3479/tests/acceptance-tests/test_latency.cpp:296:
 Failure
  12:02:57 14: Value of: observed_latency
  12:02:57 14: Expected: is < 2.4
  12:02:57 14:   Actual: 2.58163 (of type float)
  12:02:57 14: [2016-04-29 12:02:57.596475] mirserver: Stopping
  12:02:57 14: [  FAILED  ] 
ClientLatency.triple_buffered_client_has_less_than_two_frames_latency

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

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

[Touch-packages] [Bug 1579630] Re: mir server crashed in what(): drmModeMoveCursor failed (returned -13)

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mir server crashed in what():  drmModeMoveCursor failed (returned -13)

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  mir-demos crashed while I was trying to kill mir_proving_server from
  another VT. The log says:

  terminate called after throwing an instance of 
'boost::exception_detail::clone_impl'
what():  drmModeMoveCursor failed (returned -13)

  The error report is less informative:
  https://errors.ubuntu.com/oops/88953040-15b0-11e6-9c36-fa163ebeb28a

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

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

[Touch-packages] [Bug 1603303] Re: Autolanding keeps failing: mock_egl.h:89:7: error: type 'struct MockEGL' violates one definition rule [-Werror=odr]

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Autolanding keeps failing: mock_egl.h:89:7: error: type 'struct
  MockEGL' violates one definition rule [-Werror=odr]

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Autolandings are failing with this error:

  03:37:16 ../../../../../../include/test/mir/test/doubles/mock_egl.h:89:7: 
error: type 'struct MockEGL' violates one definition rule [-Werror=odr]
  03:37:16  class MockEGL
  03:37:16^
  03:37:16 ../../../../../../include/test/mir/test/doubles/mock_egl.h:89:7: 
note: a different type is defined in another translation unit
  03:37:16  class MockEGL
  03:37:16^
  03:37:16 ../../../../../../include/test/mir/test/doubles/mock_egl.h:106:6: 
note: the first difference of corresponding definitions is field 
'gmock1_eglGetDisplay_106'
  03:37:16  MOCK_METHOD1(eglGetDisplay, EGLDisplay(NativeDisplayType));
  03:37:16   ^
  03:37:16 ../../../../../../include/test/mir/test/doubles/mock_egl.h:106:6: 
note: a field of same name but different type is defined in another translation 
unit
  03:37:16  MOCK_METHOD1(eglGetDisplay, EGLDisplay(NativeDisplayType));
  03:37:16   ^
  03:37:16 /usr/include/gmock/gmock-generated-function-mockers.h:81:7: note: 
type name 'testing::internal::FunctionMocker' should match type 
name 'testing::internal::FunctionMocker'
  03:37:16  class FunctionMocker : public
  03:37:16^
  03:37:16 /usr/include/gmock/gmock-generated-function-mockers.h:81:7: note: 
the incompatible type is defined here
  03:37:16  class FunctionMocker : public
  03:37:16^
  03:37:16 /usr/include/gmock/gmock-generated-nice-strict.h:80:7: error: type 
'struct NiceMock' violates one definition rule [-Werror=odr]
  03:37:16  class NiceMock : public MockClass {
  03:37:16^
  03:37:16 /usr/include/gmock/gmock-generated-nice-strict.h:80:7: note: a type 
with different bases is defined in another translation unit
  03:37:16  class NiceMock : public MockClass {
  03:37:16^
  03:37:16 lto1: all warnings being treated as errors
  03:37:16 lto-wrapper: fatal error: /usr/bin/i686-linux-gnu-g++ returned 1 
exit status
  03:37:16 compilation terminated.
  03:37:16 /usr/bin/ld.gold: fatal error: lto-wrapper failed

  
  
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial+overlay/1527/consoleFull
  
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/1527/consoleFull

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

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

[Touch-packages] [Bug 1602199] Re: [testsfail] Process.* (memory leak in libhybris generated when probing android platforms)

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [testsfail] Process.* (memory leak in libhybris generated when probing
  android platforms)

Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/1493/consoleFull

  09:10:14 15: [ FAILED ] Process.a_main_fn_is_executed
  09:10:14 15: [ FAILED ] Process.a_successful_exit_function_succeeds

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/1493/consoleFull

  09:06:54 17: [ FAILED ] Process.a_main_fn_is_executed
  09:06:54 17: [ FAILED ] Process.a_successful_exit_function_succeeds

  I can only imagine the build agent got no CPU for so long that
  wait_for_termination() timed out.

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

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

[Touch-packages] [Bug 1584603] Re: [ FAILED ] ClientLogging.reports_performance (Value of: nbuffers)

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [ FAILED ] ClientLogging.reports_performance (Value of: nbuffers)

Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  10:23:22 [ RUN ] ClientLogging.reports_performance
  10:23:22 [2016-05-20 10:18:25.500861] mirserver: Starting
  10:23:22 [2016-05-20 10:18:25.504499] mirserver: Selected driver: dummy 
(version 0.23.0)
  10:23:22 [2016-05-20 10:18:25.548064] mirserver: Using software cursor
  10:23:22 [2016-05-20 10:18:25.552896] mirserver: Initial display 
configuration:
  10:23:22 [2016-05-20 10:18:25.553212] mirserver: 1.1: VGA 0.0" 0x0mm
  10:23:22 [2016-05-20 10:18:25.553415] mirserver: Current mode 1600x1600 
60.00Hz
  10:23:22 [2016-05-20 10:18:25.553592] mirserver: Preferred mode 1600x1600 
60.00Hz
  10:23:22 [2016-05-20 10:18:25.553758] mirserver: Logical position +0+0
  10:23:22 [2016-05-20 10:18:25.580332] mirserver: Selected input driver: 
mir:stub-input (version: 0.23.0)
  10:23:22 [2016-05-20 10:18:25.581448] mirserver: Mir version 0.23.0
  10:23:22 
/��BUILDDIR��/mir-0.23.0+xenial1136bzr3514/tests/acceptance-tests/test_client_logging.cpp:116:
 Failure
  10:23:22 Value of: nbuffers
  10:23:22 Expected: is equal to 3
  10:23:22 Actual: 2 (of type int)
  10:23:22 
/��BUILDDIR��/mir-0.23.0+xenial1136bzr3514/tests/acceptance-tests/test_client_logging.cpp:117:
 Failure
  10:23:22 Value of: Test::HasFailure()
  10:23:22 Actual: true
  10:23:22 Expected: false
  10:23:22 Log line = {[StringStreamLogger] perf: Rumpelstiltskin: 8.77 FPS, 
render time 3.51ms, buffer lag 120.30ms (2 buffers)}
  10:23:22 [ FAILED ] ClientLogging.reports_performance (4266 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial/1107/consoleFull

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

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

[Touch-packages] [Bug 1603080] Re: mirtest-dev provides an incorrect .pc file

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mirtest-dev provides an incorrect .pc file

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  In (e.g. /usr/lib/x86_64-linux-gnu/pkgconfig/mirtest.pc) there are
  missing library dependencies:

  -lboost_filesystem -lboost_system

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

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

[Touch-packages] [Bug 1580774] Re: mouse is getting stuck on a phantom edge

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mouse is getting stuck on a phantom edge

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in Mir 0.22 series:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  frieza build 101/rc-proposed

  Steps:
  1. connect mouse & keyboard to M10
  2. launch xchat
  3. go full screen
  4. mouse move around across the entirety of the screen (landscape)

  expected: mouse can range over entire screen
  actual: gets stuck moving right

  note: i noticed it happening on xchat, but when changing focus to dash
  it was also continuing to happen

  So, i kinda suspect this may be related to rotation maybe.
  I do admit i did the full OOBE in portrait mode

  Problem is also persisting across reboot.

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

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

[Touch-packages] [Bug 1589632] Re: Mir on X11 ignores mir::graphics::GLConfig depth & stencil buffer size

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Mir on X11 ignores mir::graphics::GLConfig depth & stencil buffer size

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  QtMir implements mir::graphics::GLConfig to have Mir choose a GL
  config with depth & stencil buffers enabled.

  However the Mir-on-X11 platform does not take this into account.

  Please do. Qt needs it for the QML renderer to draw correctly!

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

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

[Touch-packages] [Bug 1603114] Re: mir_acceptance_tests.bin: double free or corruption (fasttop)

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mir_acceptance_tests.bin: double free or corruption (fasttop)

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Seen a few times, typical thing seen is a memory issue in the acceptance 
tests:
  https://launchpadlibrarian.net/272973212/buildlog_ubuntu-yakkety-
  i386.mir_0.24.0+16.10.20160714-0ubuntu1_BUILDING.txt.gz

  8: CMakeFiles CTestTestfile.cmake Makefile cmake_install.cmake 
mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags 
precompiled.hpp.compileflags.processed throwback Error in 
`/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin':
 double free or corruption (fasttop): 0x0a1b5e40 CMakeFiles CTestTestfile.cmake 
Makefile cmake_install.cmake mir_acceptance_tests_precompiled.hpp.gch 
precompiled.hpp.compileflags precompiled.hpp.compileflags.processed throwback
  8: === Backtrace: =
  8: /lib/i386-linux-gnu/libc.so.6(+0x672d7)[0xf70872d7]
  8: /lib/i386-linux-gnu/libc.so.6(+0x6d227)[0xf708d227]
  8: /lib/i386-linux-gnu/libc.so.6(+0x6dae1)[0xf708dae1]
  8: /usr/lib/i386-linux-gnu/libstdc++.so.6(_ZdlPv+0x18)[0xf72884b8]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZNSt6vectorISt8weak_ptrIN3mir5input11InputDeviceEESaIS4_EED2Ev+0x8b)[0x86213bb]
  8: /lib/i386-linux-gnu/libc.so.6(+0x2e933)[0xf704e933]
  8: /lib/i386-linux-gnu/libc.so.6(+0x2e98f)[0xf704e98f]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN18mir_test_framework28InterprocessClientServerTestD1Ev+0x12a)[0x8615eda]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin[0x8352b85]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing4Test11DeleteSelf_Ev+0x28)[0x8647494]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal38HandleSehExceptionsInMethodIfSupportedINS_4TestEvEET0_PT_MS4_FS3_vEPKc+0x45)[0x86536f9]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal35HandleExceptionsInMethodIfSupportedINS_4TestEvEET0_PT_MS4_FS3_vEPKc+0x50)[0x864ddff]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8TestInfo3RunEv+0x13b)[0x86318a7]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8TestCase3RunEv+0x103)[0x8631ffd]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal12UnitTestImpl11RunAllTestsEv+0x2e7)[0x8639a51]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal38HandleSehExceptionsInMethodIfSupportedINS0_12UnitTestImplEbEET0_PT_MS4_FS3_vEPKc+0x45)[0x8654bd7]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal35HandleExceptionsInMethodIfSupportedINS0_12UnitTestImplEbEET0_PT_MS4_FS3_vEPKc+0x50)[0x864ed4f]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8UnitTest3RunEv+0xc6)[0x86383c2]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN18mir_test_framework4mainEiPPc+0x3c)[0x82822dc]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(main+0x6d)[0x828250d]
  8: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf7)[0xf70385f7]
  8: 
/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin[0x828267e]
  8: === Memory map: 

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

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

[Touch-packages] [Bug 1577262] Re: Screen is squashed/distorted when rotated in Mir-on-X11

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Screen is squashed/distorted when rotated in Mir-on-X11

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Screen is squashed/distorted when rotated in Mir-on-X11.

  Just run mir_proving_server and use Ctrl+Alt+arrows

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

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

[Touch-packages] [Bug 1601810] Re: ftbfs in linking libmir-test-assist.a in xenial+overlay and yakkety+overlay

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  ftbfs in linking libmir-test-assist.a in xenial+overlay and
  yakkety+overlay

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(char const*, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::PolymorphicMatcher > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::internal::AnyMatcherImpl::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(char const*, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::PolymorphicMatcher > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::internal::AnyMatcherImpl::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(char const*, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::PolymorphicMatcher > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::internal::AnyMatcherImpl::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(char const*, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::PolymorphicMatcher > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::internal::AnyMatcherImpl::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::DescribeTo(std::ostream*) const':
  /usr/include/gmock/gmock-matchers.h:242: undefined reference to 
`testing::internal::AnyMatcherImpl::DescribeTo(std::ostream*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(char const*, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::PolymorphicMatcher > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::internal::AnyMatcherImpl::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const'
  collect2: error: ld returned 1 exit status

  full log:
  

[Touch-packages] [Bug 1420581] Re: [enhancement] Add support for full OpenGL compositing

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [enhancement] Add support for full OpenGL compositing

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  [enhancement] Add support for full OpenGL compositing.

  libmirserver/platform presently is only compiled to use the "ES"
  subset of OpenGL. This works for mobile devices and many desktop use
  cases but not all.

  There are a few pending reasons to compile for full OpenGL on desktop
  (and/or switch at runtime!):

  1. Qt only understands full OpenGL on desktop. Presently we use a hack
  that makes it call ES functions pretending to be full OpenGL, but this
  hack will fail when we support non-Mesa desktop drivers.

  2. Proprietary desktop drivers sometimes don't support ES.

  3. Proprietary desktop drivers often (last I checked) perform better
  with full OpenGL. Not sure why, probably just driver maturity.

  4. There is evidence (bug 1420574) that ES doesn't work at all on some
  older chipsets and regular OpenGL is required.

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

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

[Touch-packages] [Bug 1570353] Re: [testsfail] ServerSignal.terminate_handler_is_called_for_SIGINT|SIGTERM

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [testsfail]
  ServerSignal.terminate_handler_is_called_for_SIGINT|SIGTERM

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  11:06:23 11: [ RUN ] ServerSignal.terminate_handler_is_called_for_SIGINT
  11:06:23 11: [2016-04-14 11:06:22.427413] mirserver: Starting
  11:06:23 11: [2016-04-14 11:06:22.632446] mirserver: Selected driver: dummy 
(version 0.22.0)
  11:06:25 11: [2016-04-14 11:06:25.145457] mirserver: Using software cursor
  11:06:29 11: [2016-04-14 11:06:29.035208] mirserver: Initial display 
configuration:
  11:06:29 11: [2016-04-14 11:06:29.145985] mirserver: 1.1: VGA 0.0" 0x0mm
  11:06:29 11: [2016-04-14 11:06:29.197116] mirserver: Current mode 1600x1600 
60.00Hz
  11:06:29 11: [2016-04-14 11:06:29.14] mirserver: Preferred mode 1600x1600 
60.00Hz
  11:06:29 11: [2016-04-14 11:06:29.223729] mirserver: Logical position +0+0
  11:06:31 11: [2016-04-14 11:06:31.352705] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  11:06:31 11: [2016-04-14 11:06:31.593246] mirserver: Mir version 0.22.0
  11:08:22 11: unknown file: Failure
  11:08:22 11: C++ exception with description "Poll on readfd for pipe timed 
out" thrown in the test body.
  11:09:22 11: unknown file: Failure
  11:09:22 11: C++ exception with description "Timeout while waiting for child 
to change state" thrown in TearDown().
  11:09:22 11: 
  11:09:22 11: GMOCK WARNING:
  11:09:22 11: Uninteresting mock function call - returning directly.
  11:09:22 11: Function call: terminate_handler(15)
  11:09:22 11: Stack trace:
  11:09:22 11: [2016-04-14 11:09:22.547570] mirserver: Stopping
  11:09:23 11: unknown file: Failure
  11:09:23 11: C++ exception with description "Failed to start server thread" 
thrown in the test body.
  11:09:23 11: [2016-04-14 11:09:23.821255] mirserver: Stopping
  11:09:24 11: ==8442==
  11:09:24 11: ==8442== FILE DESCRIPTORS: 4 open at exit.
  11:09:24 11: ==8442== Open file descriptor 4: 
/��BUILDDIR��/mir-0.22.0+xenial869bzr3458/obj-i686-linux-gnu/Testing/Temporary/LastTest.log.tmp
  11:09:24 11: ==8442== 
  11:09:24 11: ==8442==
  11:09:24 11: ==8442== Open file descriptor 2:
  11:09:24 11: ==8442== 
  11:09:24 11: ==8442==
  11:09:24 11: ==8442== Open file descriptor 1:
  11:09:24 11: ==8442== 
  11:09:25 11: ==8442==
  11:09:25 11: ==8442== Open file descriptor 0: /dev/null
  11:09:25 11: ==8442== 
  11:09:25 11: ==8442==
  11:09:25 11: ==8442==
  11:09:25 11: ==8442== HEAP SUMMARY:
  11:09:25 11: ==8442== in use at exit: 32,950 bytes in 36 blocks
  11:09:25 11: ==8442== total heap usage: 34,086 allocs, 34,050 frees, 
1,748,971 bytes allocated
  11:09:25 11: ==8442==
  11:09:25 11: ==8442== LEAK SUMMARY:
  11:09:25 11: ==8442== definitely lost: 0 bytes in 0 blocks
  11:09:25 11: ==8442== indirectly lost: 0 bytes in 0 blocks
  11:09:25 11: ==8442== possibly lost: 0 bytes in 0 blocks
  11:09:25 11: ==8442== still reachable: 32,950 bytes in 36 blocks
  11:09:25 11: ==8442== suppressed: 0 bytes in 0 blocks
  11:09:25 11: ==8442== Reachable blocks (those to which a pointer was found) 
are not shown.
  11:09:25 11: ==8442== To see them, rerun with: --leak-check=full 
--show-leak-kinds=all
  11:09:25 11: ==8442==
  11:09:25 11: ==8442== For counts of detected and suppressed errors, rerun 
with: -v
  11:09:25 11: ==8442== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 
from 0)
  11:09:25 11: [ FAILED ] ServerSignal.terminate_handler_is_called_for_SIGINT 
(182929 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/851/consoleFull

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

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

[Touch-packages] [Bug 1598802] Re: CI failure in DemoInProcessServerWithStubClientPlatform.surface_creation_does_not_leak_fds

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  CI failure in
  DemoInProcessServerWithStubClientPlatform.surface_creation_does_not_leak_fds

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  09:49:44 15: [--] 1 test from 
DemoInProcessServerWithStubClientPlatform
  09:49:44 15: [ RUN ] 
DemoInProcessServerWithStubClientPlatform.surface_creation_does_not_leak_fds
  09:49:44 15: [2016-07-04 09:49:44.614378] mirplatform: Found graphics driver: 
mir:mesa-kms (version 0.24.0)
  09:49:44 15: [2016-07-04 09:49:44.616132] mirplatform: Found graphics driver: 
mir:mesa-x11 (version 0.24.0)
  09:49:44 15: [2016-07-04 09:49:44.631209] mirplatform: Found graphics driver: 
mir:android (version 0.24.0)
  09:49:44 15: [2016-07-04 09:49:44.632648] mirplatform: Found graphics driver: 
throw-on-creation (version 0.24.0)
  09:49:44 15: [2016-07-04 09:49:44.632940] mirplatform: Found graphics driver: 
mir:stub-graphics (version 0.24.0)
  09:49:44 15: [2016-07-04 09:49:44.708688] mirserver: Initial display 
configuration:
  09:49:44 15: [2016-07-04 09:49:44.709629] mirserver: 1.1: VGA 0.0" 0x0mm
  09:49:44 15: [2016-07-04 09:49:44.709836] mirserver: Current mode 1600x1600 
60.00Hz
  09:49:44 15: [2016-07-04 09:49:44.710034] mirserver: Preferred mode 1600x1600 
60.00Hz
  09:49:44 15: [2016-07-04 09:49:44.710200] mirserver: Logical position +0+0
  09:49:44 15: [2016-07-04 09:49:44.723052] mirserver: Mir version 0.24.0
  09:49:45 15: 
/��BUILDDIR��/mir-0.24.0+vivid1459bzr3569/tests/integration-tests/test_test_framework.cpp:117:
 Failure
  09:49:45 15: Expected: (new_fd_count) <= 
(fd_count_after_one_surface_lifetime), actual: 121 vs 40
  09:49:45 15: [ FAILED ] 
DemoInProcessServerWithStubClientPlatform.surface_creation_does_not_leak_fds 
(792 ms)
  09:49:45 15: [--] 1 test from 
DemoInProcessServerWithStubClientPlatform (797 ms total)

  As seen here: https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/1431/consoleFull

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

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

[Touch-packages] [Bug 1591354] Re: [tests] given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset fails

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [tests]
  
given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset
  fails

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  18:48:48 13: [ RUN ] 
NestedServer.given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset
  ...
  18:48:51 13: [2016-06-10 18:48:50.931481] mirserver: Logical position +0+0
  18:48:52 13: 
/��BUILDDIR��/mir-0.23.0+xenial1328bzr3533/tests/acceptance-tests/test_nested_mir.cpp:1135:
 Failure
  18:48:52 13: Value of: condition.raised()
  18:48:52 13: Actual: false
  18:48:52 13: Expected: true
  18:48:52 13: 
/��BUILDDIR��/mir-0.23.0+xenial1328bzr3533/tests/acceptance-tests/test_nested_mir.cpp:1129:
 Failure
  18:48:52 13: Actual function call count doesn't match 
EXPECT_CALL(*the_mock_display_configuration_report(), 
new_configuration(mt::DisplayConfigMatches(expected_config)))...
  18:48:52 13: Expected: to be called once
  18:48:52 13: Actual: never called - unsatisfied and active
  18:48:52 13: [2016-06-10 18:48:52.115583] mirserver: Stopping
  18:48:52 13: [2016-06-10 18:48:52.280421] mirserver: Stopping
  18:48:52 13: [ FAILED ] 
NestedServer.given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset
 (3916 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial/1297/consoleFull

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

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

[Touch-packages] [Bug 1593655] Re: Servers based on Mir need a hook to execute code when the server is closing

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Servers based on Mir need a hook to execute code when the server is
  closing

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  There are multiple ways that a server can be closed because we hook
  into SIGINT & SIGTERM to stop the Mir server and the client code can
  call stop() directly.

  There should be an "on_stop(function)" facility to run client
  cleanup code before the server shuts down.

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

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

[Touch-packages] [Bug 1596051] Re: Physical "screen" size reported by the X11 backend is same as pixel count, fixing dpi to 25.4

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Physical "screen" size reported by the X11 backend is same as pixel
  count, fixing dpi to 25.4

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Hey, I'm testing mir on X11.

  Qt is calculating the DPI value based on information Mir gives it
  about the screen. It uses either the DPI value Mir calculates, or the
  physical size of the screen to calculate DPI itself.

  But the X11 backend reports the physical size equal to the number of
  pixels, so 1mm = 1 pixel. This makes the DPI calculation always return
  25.4dpi, which causes Qt to render tiny fonts.

  Could you please mock the physical screen size to return something so
  that DPI becomes something more sensible?

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

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

[Touch-packages] [Bug 1590765] Re: OSK flickers and buttons are sometimes invisble

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  OSK flickers and buttons are sometimes invisble

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often
  invisible (pressing white part will refresh it and buttons are visible
  again) and OSK flickers a lot.

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

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

[Touch-packages] [Bug 1556045] Re: CI failure in MirSurfaceVisibilityEvent.exposed_received_when_surface_raised_over_occluding_surface [called twice - over-saturated and active]

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  CI failure in
  
MirSurfaceVisibilityEvent.exposed_received_when_surface_raised_over_occluding_surface
  [called twice - over-saturated and active]

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/431/consoleFull

  11:08:37 11: [ RUN ] 
MirSurfaceVisibilityEvent.exposed_received_when_surface_raised_over_occluding_surface
  11:08:37 11: [2016-03-11 11:08:37.041108] mirserver: Starting
  11:08:37 11: [2016-03-11 11:08:37.043789] mirserver: Selected driver: dummy 
(version 0.20.0)
  11:08:37 11: [2016-03-11 11:08:37.067340] mirserver: Initial display 
configuration:
  11:08:37 11: [2016-03-11 11:08:37.067738] mirserver: 1.1: VGA 0.0" 0x0mm
  11:08:37 11: [2016-03-11 11:08:37.067972] mirserver: Current mode 1600x1600 
60.00Hz
  11:08:37 11: [2016-03-11 11:08:37.068220] mirserver: Preferred mode 1600x1600 
60.00Hz
  11:08:37 11: [2016-03-11 11:08:37.068423] mirserver: Logical position +0+0
  11:08:37 11: [2016-03-11 11:08:37.070976] mirserver: Using software cursor
  11:08:37 11: [2016-03-11 11:08:37.088056] mirserver: Selected input driver: 
mir:stub-input (version: 0.20.0)
  11:08:37 11: [2016-03-11 11:08:37.089304] mirserver: Mir version 0.20.0
  11:08:37 11: 
/��BUILDDIR��/mir-0.20.1+16.04.20160225.1+vivid444bzr3385/tests/acceptance-tests/test_client_surface_visibility.cpp:179:
 Failure
  11:08:37 11: Mock function called more times than expected - returning 
directly.
  11:08:37 11: Function call: handle(0x1222c330, 0)
  11:08:37 11: Expected: to be called once
  11:08:37 11: Actual: called twice - over-saturated and active
  11:08:38 11: [2016-03-11 11:08:38.077075] mirserver: Stopping
  11:08:38 11: [ FAILED ] 
MirSurfaceVisibilityEvent.exposed_received_when_surface_raised_over_occluding_surface
 (1072 ms)

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

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

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

[Touch-packages] [Bug 1506358] Re: unity8/libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  unity8/libmirclient gives up and terminates prematurely with
  "std::exception::what: disconnected: no new buffers" via
  ExchangeSemantics::submit()

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Under heavy resizing (stress testing under Valgrind), my Mir client
  (Xmir) crashed with:

  [1444895332.392862]  MirBufferStreamAPI: Caught exception at client 
library boundary (in mir_buffer_stream_swap_buffers): 
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
 Throw in function virtual MirWaitHandle* 
{anonymous}::ExchangeSemantics::submit(const std::function&, 
mir::geometry::Size, MirPixelFormat, int)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: disconnected: no new buffers

  The strange thing is it's only the client that died. The server
  survived and I can connect new clients to it.

  ---
  Duplicate bug reports now show Unity8 is another such client suffering from 
this crash. It's occurring on phones and desktops in the wild.

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

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

[Touch-packages] [Bug 1600343] Re: mir ftbfs in yakkety builders

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mir ftbfs in yakkety builders

Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  example:

  https://launchpadlibrarian.net/271776684/buildlog_ubuntu-yakkety-
  amd64.mir_0.24.0+16.10.20160708-0ubuntu1_BUILDING.txt.gz

  [ 58%] Building C object 
examples/CMakeFiles/mir_demo_client_cursors.dir/cursors_demo_client.c.o
  cd /«BUILDDIR»/mir-0.24.0+16.10.20160708/obj-x86_64-linux-gnu/examples && 
/usr/bin/x86_64-linux-gnu-gcc  -DLOG_NDEBUG=1 -DMESA_EGL_NO_X11_HEADERS 
-DMIR_LIBINPUT_HAS_ACCEL_PROFILE=1 
-DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API 
-DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT 
-DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" 
-DMIR_VERSION_MAJOR=0 -DMIR_VERSION_MICRO=0 -DMIR_VERSION_MINOR=24 
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE 
-I/«BUILDDIR»/mir-0.24.0+16.10.20160708/include/common 
-I/«BUILDDIR»/mir-0.24.0+16.10.20160708/include/cookie 
-I/«BUILDDIR»/mir-0.24.0+16.10.20160708/obj-x86_64-linux-gnu/src/protobuf 
-I/«BUILDDIR»/mir-0.24.0+16.10.20160708/include/server 
-I/«BUILDDIR»/mir-0.24.0+16.10.20160708/include/client 
-I/«BUILDDIR»/mir-0.24.0+16.10.20160708/include/platform 
-I/«BUILDDIR»/mir-0.24.0+16.10.20160708/include/renderers/gl  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -pthread -g -Werror -Wall -pedantic -Wextra -fPIC -flto 
-std=c99 -Wall -fno-strict-aliasing -Wextra   -o 
CMakeFiles/mir_demo_client_cursors.dir/cursors_demo_client.c.o   -c 
/«BUILDDIR»/mir-0.24.0+16.10.20160708/examples/cursors_demo_client.c
  In file included from /usr/include/stdint.h:25:0,
   from /usr/lib/gcc/x86_64-linux-gnu/5/include/stdint.h:9,
   from 
/«BUILDDIR»/mir-0.24.0+16.10.20160708/include/client/mir_toolkit/events/event.h:23,
   from 
/«BUILDDIR»/mir-0.24.0+16.10.20160708/include/client/mir_toolkit/client_types.h:24,
   from 
/«BUILDDIR»/mir-0.24.0+16.10.20160708/include/client/mir_toolkit/mir_connection.h:21,
   from 
/«BUILDDIR»/mir-0.24.0+16.10.20160708/include/client/mir_toolkit/mir_client_library.h:21,
   from 
/«BUILDDIR»/mir-0.24.0+16.10.20160708/examples/cursors_demo_client.c:21:
  /usr/include/features.h:148:3: error: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Werror=cpp]
   # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"

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

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

[Touch-packages] [Bug 1584601] Re: Mir fails to build in: COMPOSITOR_TRACE_CALL

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Mir fails to build in: COMPOSITOR_TRACE_CALL

Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  13:08:37 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/src/server/report/lttng/compositor_report.cpp:30:1:
 error: use of GNU statement expression extension 
[-Werror,-Wgnu-statement-expression]
  13:08:37 COMPOSITOR_TRACE_CALL(started)
  13:08:37 ^
  13:08:37 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/src/server/report/lttng/compositor_report.cpp:28:37:
 note: expanded from macro 'COMPOSITOR_TRACE_CALL'
  13:08:37 #define COMPOSITOR_TRACE_CALL(name) 
MIR_LTTNG_VOID_TRACE_CALL(CompositorReport, mir_server_compositor, name)
  13:08:37 ^
  13:08:37 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/src/server/report/lttng/lttng_utils.h:28:9:
 note: expanded from macro 'MIR_LTTNG_VOID_TRACE_CALL'
  13:08:37 mir_tracepoint(comp, name, 0);   \
  13:08:37 ^
  13:08:37 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/src/include/common/mir/report/lttng/mir_tracepoint.h:22:32:
 note: expanded from macro 'mir_tracepoint'
  13:08:37 #define mir_tracepoint(c, ...) tracepoint(c, __VA_ARGS__)
  13:08:37^
  13:08:37 note: (skipping 1 expansions in backtrace; use 
-fmacro-backtrace-limit=0 to see all)
  13:08:37 /usr/include/lttng/tracepoint.h:50:15: note: expanded from macro 
'tracepoint_enabled'
  13:08:37 
caa_unlikely(CMM_LOAD_SHARED(__tracepoint_##provider##___##name.state))
  13:08:37  ^
  13:08:37 /usr/include/urcu/system.h:35:3: note: expanded from macro 
'CMM_LOAD_SHARED'
  13:08:37 ({  \
  13:08:37  ^

  
  --- or ---

  
  13:13:56 /usr/bin/cmake -E cmake_progress_report 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/obj-arm-linux-gnueabihf/CMakeFiles 
  13:13:56 ../../../../../src/server/report/lttng/compositor_report.cpp: In 
member function 'virtual void mir::report::lttng::CompositorReport::started()':
  13:13:56 ../../../../../src/server/report/lttng/compositor_report.cpp:30:87: 
error: ISO C++ forbids braced-groups within expressions [-Werror=pedantic]
  13:13:56  COMPOSITOR_TRACE_CALL(started)
  13:13:56  
  ^
  13:13:56 ../../../../../src/server/report/lttng/compositor_report.cpp: In 
member function 'virtual void mir::report::lttng::CompositorReport::stopped()':
  13:13:56 ../../../../../src/server/report/lttng/compositor_report.cpp:31:87: 
error: ISO C++ forbids braced-groups within expressions [-Werror=pedantic]
  13:13:56  COMPOSITOR_TRACE_CALL(stopped)
  13:13:56

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

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

[Touch-packages] [Bug 1584784] Re: Using NBS, X apps under Unity8 need interaction to start in pocket-desktop

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Using NBS, X apps under Unity8 need interaction to start in pocket-
  desktop

Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in QtMir:
  Invalid
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  With Mir 0.23.0, X apps under Unity8 need some interaction to get the
  applications to start. 0.23.0 is blocked pending fix.

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

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

[Touch-packages] [Bug 1579866] Re: Android graphics platform doesn't get packaged for arm64

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Android graphics platform doesn't get packaged for arm64

Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  The android platform code is currently gated to i386,amd64,armhf
  because the libhybris upstream dependency is gated to these
  architectures.

  Upstream recently added builds for arm64, so it would be good to
  enable our android code on this arch as well.

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

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

[Touch-packages] [Bug 1577357] Re: package-built mir_demo_server does not start on device

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  package-built mir_demo_server does not start on device

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  when running the packaged mir_demo_server:

  root@ubuntu-phablet:/home/phablet/mir/binln -s /usr/local/lib/mir 
/home/phablet/mir/lib/mir/^C
  root@ubuntu-phablet:/home/phablet/mir/bin# mir_demo_server
  [2016-05-02 06:43:48.502123] mirplatform: Found graphics driver: mir:android 
(version 0.23.0)
  [2016-05-02 06:43:48.506548] mirserver: Starting
  [2016-05-02 06:43:48.508196] mircommon: Loading modules from: 
/usr/lib/arm-linux-gnueabihf/mir/server-platform
  [2016-05-02 06:43:48.508959] mircommon: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.9
  [2016-05-02 06:43:48.509691] mircommon: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/server-platform/input-evdev.so.5
  [2016-05-02 06:43:48.513048] mirplatform: Found graphics driver: mir:android 
(version 0.23.0)
  [2016-05-02 06:43:48.514024] mirserver: Selected driver: mir:android (version 
0.23.0)
  ERROR: Dynamic exception type: St12system_error
  std::exception::what: Enable multithreading to use std::thread: Operation not 
permitted

  root@ubuntu-phablet:/home/phablet/mir/bin#

  
  running a built-and-copied over mir_demo_server works, and the packaged 
mir_proving_server also starts.

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

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

[Touch-packages] [Bug 1578159] Re: Performance loss with NBS and overlays on

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Performance loss with NBS and overlays on

Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  If you run a server with overlays enabled on android devices with a
  client, sporadically, the performance will dip between 1/2 vsync rate
  and vsync rate. The dip is dependent on load, (it seems loads that tax
  the system at near-vsync rates seem to cause the problem).

  Should be fixed before 0.23 is published, so tagging as critical.

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

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

[Touch-packages] [Bug 1597717] Re: [regression] unity8 fails to start when built with 0.24 series (lp:mir)

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] unity8 fails to start when built with 0.24 series
  (lp:mir)

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Unity8 fails to start when built with tip lp:mir (0.24 series). USC
  comes up, but will remain displaying the spinner. Log (attached)
  indicates that u8 was disconnected from USC during startup.

  I did a bisection that indicates rev 3539 (introduction of the nested
  input platform) was the 1st problematic revision.

  note: qtmir compatibility branch in use:
  https://code.launchpad.net/~kdub/qtmir/0.24-compatibility

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

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

[Touch-packages] [Bug 1612256] Re: [regression] Trust prompt not shown when starting camera

[Daniel van Vugt]

** Changed in: mir/0.24
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Trust prompt not shown when starting camera

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.24 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Installed bq-aquaris.en (rev 405) and mir 0.24.0 from silo 36.
  Clicking camera, the application appears to be stuck waiting for the
  trust prompt.

  This does not happen with 0.23.5.

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

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

[Touch-packages] [Bug 1599867] Re: usage of std:call_once in mirclient causes TLS collisions with some android devices

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  usage of std:call_once in mirclient causes TLS collisions with some
  android devices

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  usage of std:call_once in src/client/error_connections.cpp in
  libmirclient causes TLS collisions with some android devices.

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

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

[Touch-packages] [Bug 1577967] Re: During surface creation, first stream in spec becomes default stream.

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  During surface creation, first stream in spec becomes default stream.

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  A surface creation spec can have multiple streams. The code currently,
  by happenstance, makes the first stream the "default stream", i.e.
  instantiates a MirSurface using that stream. The MirSurface object's
  methods then use that stream for various purposes, e.g. to set the
  swap interval, to set size during resize, to query parameters of the
  surface, etc. Here's a list of MirSurface methods that use the default
  stream :

  MirSurface::get_parameters(),
  MirSurface::configure(),
  MirSurface::attrib(),
  MirSurface::handle_event()

  We need to define the precise semantics of MirSurface properly in
  regards to the streams that may be associated with it.

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

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

[Touch-packages] [Bug 1579076] Re: [regression] NBS causes sudden loss of performance after surface resizes

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] NBS causes sudden loss of performance after surface
  resizes

Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Seems that the dash gets resized() very shortly after its created.
  This seems to cause a degradation from "triple-buffered" operation to
  "double-buffered" operation. On some device loads (eg, krillin+dash,
  where the rendering needs to be triple buffering to stay at vsync
  rate), this can cause the performance to dip

  tagging as critical, as it should block 0.23.

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

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

[Touch-packages] [Bug 1610215] Re: Mir build and test failures with gcc-6 and LTO

[Daniel van Vugt]

** Changed in: mir/0.24
   Status: Fix Committed => Fix Released

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

Title:
  Mir build and test failures with gcc-6 and LTO

Status in Mir:
  Fix Committed
Status in Mir 0.24 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  The exact failure mode is different depending on whether ld.bfd or
  ld.gold is used. In both cases, however, the core issue seems to be
  that implicit destructor symbols cannot be found.

   ld.bfd ===

  Build error for mir_acceptance_tests:

  ../libmir-test-assist.a(fake_display.cpp.o): In function 
`mir::test::doubles::NullDisplaySyncGroup::NullDisplaySyncGroup()':
  /root/mir/include/test/mir/test/doubles/null_display_sync_group.h:68: 
undefined reference to `vtable for mir::test::doubles::NullDisplaySyncGroup'
  ../libmir-test-assist.a(fake_display.cpp.o): In function 
`mir::test::doubles::NullDisplayBuffer::NullDisplayBuffer()':
  /root/mir/include/test/mir/test/doubles/null_display_buffer.h:31: undefined 
reference to `vtable for mir::test::doubles::NullDisplayBuffer'
  ../libmir-test-assist.a(fake_display.cpp.o): In function 
`mir::test::doubles::NullDisplaySyncGroup::NullDisplaySyncGroup()':
  /root/mir/include/test/mir/test/doubles/null_display_sync_group.h:68: 
undefined reference to `vtable for mir::test::doubles::NullDisplaySyncGroup'
  ../libmir-test-assist.a(fake_display.cpp.o): In function 
`mir::test::doubles::NullDisplayBuffer::NullDisplayBuffer()':
  /root/mir/include/test/mir/test/doubles/null_display_buffer.h:31: undefined 
reference to `vtable for mir::test::doubles::NullDisplayBuffer'
  collect2: error: ld returned 1 exit status
  tests/acceptance-tests/CMakeFiles/mir_acceptance_tests.dir/build.make:1450: 
recipe for target 'bin/mir_acceptance_tests.bin' failed
  make[2]: *** [bin/mir_acceptance_tests.bin] Error 1
  CMakeFiles/Makefile2:9407: recipe for target 
'tests/acceptance-tests/CMakeFiles/mir_acceptance_tests.dir/all' failed
  make[1]: *** [tests/acceptance-tests/CMakeFiles/mir_acceptance_tests.dir/all] 
Error 2

  Build error for mir_unit_tests:

  ../mir_test_framework/libmir-test-framework-static.a(stub_session.cpp.o): In 
function `_GLOBAL__sub_I_stub_session.cpp':
  /root/mir/tests/mir_test_framework/stub_session.cpp:161: undefined reference 
to `mir::test::doubles::StubSession::~StubSession()'
  
../mir_test_framework/libmir-test-framework-static.a(stub_session.cpp.o):(.data.rel.ro._ZTVN3mir4test7doubles11StubSessionE[_ZTVN3mir4test7doubles11StubSessionE]+0x10):
 undefined reference to `mir::test::doubles::StubSession::~StubSession()'
  
../mir_test_framework/libmir-test-framework-static.a(stub_session.cpp.o):(.data.rel.ro._ZTVN3mir4test7doubles11StubSessionE[_ZTVN3mir4test7doubles11StubSessionE]+0x18):
 undefined reference to `mir::test::doubles::StubSession::~StubSession()'
  
../mir_test_framework/libmir-test-framework-static.a(stub_session.cpp.o):(.debug_info+0xbb84):
 undefined reference to `mir::test::doubles::StubSession::~StubSession()'
  
../mir_test_framework/libmir-test-framework-static.a(testing_server_options.cpp.o):
 In function `mir::ServerConfiguration::ServerConfiguration()':
  /root/mir/src/include/server/mir/server_configuration.h:89: undefined 
reference to `vtable for mir::ServerConfiguration'
  /root/mir/src/include/server/mir/server_configuration.h:89: undefined 
reference to `vtable for mir::ServerConfiguration'
  
../mir_test_framework/libmir-test-framework-static.a(stubbed_server_configuration.cpp.o):
 In function `mir::ServerConfiguration::ServerConfiguration()':
  /root/mir/src/include/server/mir/server_configuration.h:89: undefined 
reference to `vtable for mir::ServerConfiguration'
  collect2: error: ld returned 1 exit status
  tests/unit-tests/CMakeFiles/mir_unit_tests.dir/build.make:4588: recipe for 
target 'bin/mir_unit_tests.bin' failed
  make[2]: *** [bin/mir_unit_tests.bin] Error 1
  CMakeFiles/Makefile2:10841: recipe for target 
'tests/unit-tests/CMakeFiles/mir_unit_tests.dir/all' failed
  make[1]: *** [tests/unit-tests/CMakeFiles/mir_unit_tests.dir/all] Error 2
  Makefile:138: recipe for target 'all' failed
  make: *** [all] Error 2

  
  === ld.gold ===

  No build errors, but we get segfaults when running the mir_unit_tests
  during the destruction of StubSession objects.

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

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

[Touch-packages] [Bug 1615455] [NEW] package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[santosh kumar]

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

sant-64@sant64-desktop:~$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
apt-cache policy  libglib2.0-0:amd64
libglib2.0-0:
  Installed: 2.48.1-1~ubuntu16.04.1
  Candidate: 2.48.1-1~ubuntu16.04.1
  Version table:
 *** 2.48.1-1~ubuntu16.04.1 500
500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2.48.0-1ubuntu4 500
500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

3) What you expected to happen
Installation/upgradation

4) What happened instead
Error as desibed above

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Aug 21 20:19:49 2016
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2015-09-19 (337 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: glib2.0
Title: package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to xenial on 2016-08-21 (0 days ago)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  sant-64@sant64-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  apt-cache policy  libglib2.0-0:amd64
  libglib2.0-0:
Installed: 2.48.1-1~ubuntu16.04.1
Candidate: 2.48.1-1~ubuntu16.04.1
Version table:
   *** 2.48.1-1~ubuntu16.04.1 500
  500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.48.0-1ubuntu4 500
  500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) What you expected to happen
  Installation/upgradation

  4) What happened instead
  Error as desibed above

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 20:19:49 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-09-19 (337 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: glib2.0
  Title: package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-08-21 (0 days ago)

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

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

[Touch-packages] [Bug 1615454] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

[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 fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1615454

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 20:05:59 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-06-16 (66 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-22 (0 days ago)

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

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

[Touch-packages] [Bug 1615454] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

[Ben Hanson]

Public bug reported:

?

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Aug 21 20:05:59 2016
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2016-06-16 (66 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to xenial on 2016-08-22 (0 days ago)

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


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

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 20:05:59 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-06-16 (66 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-22 (0 days ago)

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

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

[Touch-packages] [Bug 1614870] Re: Problems with font cache after update

[Jeremy]

This also started to happen to me in 16.04.
When I remove a certain folder with lots of fonts (the ones I copied from Mac 
OS X partition) from my fonts folder, the problem seems to go away.

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

Title:
  Problems with font cache after update

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  After last update on my 14.04 trusty machine, it takes a long time to
  regenerate the fonts cache. Now after that, most graphical
  applications take about 30 seconds to start with 100% CPU load. It is
  impossible to work with my system in this state.

  I already tried purging and reinstallong all fontconfig-related
  packages and completely deleted and rebuildt my font cache, but the
  problem persists. Before the update everything was fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: fontconfig 2.11.0-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Aug 19 10:11:10 2016
  InstallationDate: Installed on 2014-04-16 (856 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1614870] Re: Problems with font cache after update

[Launchpad Bug Tracker]

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

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

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

Title:
  Problems with font cache after update

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  After last update on my 14.04 trusty machine, it takes a long time to
  regenerate the fonts cache. Now after that, most graphical
  applications take about 30 seconds to start with 100% CPU load. It is
  impossible to work with my system in this state.

  I already tried purging and reinstallong all fontconfig-related
  packages and completely deleted and rebuildt my font cache, but the
  problem persists. Before the update everything was fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: fontconfig 2.11.0-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Aug 19 10:11:10 2016
  InstallationDate: Installed on 2014-04-16 (856 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1615449] Re: Use upstream manpages instead of stub Debian-provided man page

[Jeremy Bicha]

** Patch added: "p11kit-manpages-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1615449/+attachment/4725258/+files/p11kit-manpages-xenial.debdiff

** Also affects: gnome-taquin (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: p11-kit (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: gnome-taquin (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: gnome-taquin (Ubuntu)

** No longer affects: gnome-taquin (Ubuntu Xenial)

** Changed in: p11-kit (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: p11-kit (Ubuntu)
   Importance: Wishlist => Low

** Tags added: patch xenial yakkety

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

Title:
  Use upstream manpages instead of stub Debian-provided man page

Status in p11-kit package in Ubuntu:
  New
Status in p11-kit source package in Xenial:
  New

Bug description:
  Impact
  ==
  The Debian provided stub manpage is not very useful. Now that upstream 
includes manpages, we should build and ship those instead.

  This replaces p11-kit1. with the much more verbose and useful
  trust.1, pkcs11.conf.5 and p11-kit.8

  Test Case
  
  Run man p11-kit, man trust and man pkcs11.conf

  Regression Potential
  
  For yakkety, please sync p11-kit 0.23.2-5.

  For xenial, I am including a debdiff to backport the changes from
  0.23.2-4 and 0.23.2-5 with the exception of enabling all hardening
  flags since I think the SRU policy discourages making changes like
  that.

  0.23.2-4 updates the package descriptions in debian/control.

  Please sync p11-kit 0.23.2-5 (main) from Debian unstable (main)

  Changelog entries since current yakkety version 0.23.2-4:

  p11-kit (0.23.2-5) unstable; urgency=medium

* Build and ship upstream manpages. (Thanks, Julien Cristau)
  + Add b-d on gtk-doc-tools.
  + Pass --enable-doc to ./configure.
  + Drop minimal debian/p11-kit.1 manpage.
  Closes: #834992

   -- Andreas Metzler   Sun, 21 Aug 2016 16:03:45
  +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1615449/+subscriptions

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

[Touch-packages] [Bug 1615449] [NEW] Use upstream manpages instead of stub Debian-provided man page

[Jeremy Bicha]

Public bug reported:

Impact
==
The Debian provided stub manpage is not very useful. Now that upstream includes 
manpages, we should build and ship those instead.

This replaces p11-kit1. with the much more verbose and useful
trust.1, pkcs11.conf.5 and p11-kit.8

Test Case

Run man p11-kit, man trust and man pkcs11.conf

Regression Potential

For yakkety, please sync p11-kit 0.23.2-5.

For xenial, I am including a debdiff to backport the changes from
0.23.2-4 and 0.23.2-5 with the exception of enabling all hardening flags
since I think the SRU policy discourages making changes like that.

0.23.2-4 updates the package descriptions in debian/control.

Please sync p11-kit 0.23.2-5 (main) from Debian unstable (main)

Changelog entries since current yakkety version 0.23.2-4:

p11-kit (0.23.2-5) unstable; urgency=medium

  * Build and ship upstream manpages. (Thanks, Julien Cristau)
+ Add b-d on gtk-doc-tools.
+ Pass --enable-doc to ./configure.
+ Drop minimal debian/p11-kit.1 manpage.
Closes: #834992

 -- Andreas Metzler   Sun, 21 Aug 2016 16:03:45
+0200

** Affects: p11-kit (Ubuntu)
 Importance: Low
 Status: New

** Affects: p11-kit (Ubuntu Xenial)
 Importance: Low
 Status: New


** Tags: patch xenial yakkety

** Changed in: p11-kit (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Use upstream manpages instead of stub Debian-provided man page

Status in p11-kit package in Ubuntu:
  New
Status in p11-kit source package in Xenial:
  New

Bug description:
  Impact
  ==
  The Debian provided stub manpage is not very useful. Now that upstream 
includes manpages, we should build and ship those instead.

  This replaces p11-kit1. with the much more verbose and useful
  trust.1, pkcs11.conf.5 and p11-kit.8

  Test Case
  
  Run man p11-kit, man trust and man pkcs11.conf

  Regression Potential
  
  For yakkety, please sync p11-kit 0.23.2-5.

  For xenial, I am including a debdiff to backport the changes from
  0.23.2-4 and 0.23.2-5 with the exception of enabling all hardening
  flags since I think the SRU policy discourages making changes like
  that.

  0.23.2-4 updates the package descriptions in debian/control.

  Please sync p11-kit 0.23.2-5 (main) from Debian unstable (main)

  Changelog entries since current yakkety version 0.23.2-4:

  p11-kit (0.23.2-5) unstable; urgency=medium

* Build and ship upstream manpages. (Thanks, Julien Cristau)
  + Add b-d on gtk-doc-tools.
  + Pass --enable-doc to ./configure.
  + Drop minimal debian/p11-kit.1 manpage.
  Closes: #834992

   -- Andreas Metzler   Sun, 21 Aug 2016 16:03:45
  +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1615449/+subscriptions

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

[Touch-packages] [Bug 1612708] Re: Symbolic Link does not work in 16.04 LTS as in 14.04 LTS

[mohican]

But differently from you I can read and write files accessed through the
symbolic link.

It's only moving them to the trash that fails.

- Using the 'move to trash' menu fails.
- Manually cutting the file then trying to paste it into the trash fails.
- Manually cutting the file then trying to paste it into the 
/media/DATA/.Trash-1000/files/ directory works.

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

Title:
  Symbolic Link does not work in 16.04 LTS as in 14.04 LTS

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.1 LTS

  colord:
Installiert:   1.2.12-1ubuntu1
Installationskandidat: 1.2.12-1ubuntu1
Versionstabelle:
   *** 1.2.12-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Under Ubuntu 14.04 LTS I have created NAS access by using 'gvfs-mount
  smb://nasdo/public'. It is linked to '/run/user/1000/gvfs/ als smb-
  share:server=nasdo,share=public' and I have created a Symbolic Link to
  this point with 'ln -s /run/user/1000/gvfs/smb-
  share\:server\=nasdo\,share\=public ~/nasdo_public'. Using this link
  folders, and files on the NAS have been accessable with r/w from
  Ubuntu 14.04 LTS. This is, what I expect from 16.04, too.

  Since I have upgraded to ubuntu 16.04 LTS a few days ago, all the
  links seem to be the same, but opening a file does not work. It comes
  to an input/output error. I can use the links to folders to navigate,
  but there is no chance to open e.g. an LibreOffice Calc Sheet, nor do
  I have access to mail folder via Thunderbird.

  Using gvfs-mount creates a shared folder in Nautilus called public.
  Using this way to access the NAS, and open the Calc file works with
  ubuntu 16.04 LTS fine.

  Locking to the syslog while trying to open a file creates the following 
entries:
  Aug 12 16:47:19 UDO systemd[1]: Started Hostname Service.
  Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: 
dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der 
Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt
  Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (process:8645): WARNING **: 
Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: 
Der angegebene Ort ist nicht eingehängt
  Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: 
dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der 
Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt
  Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (process:8663): WARNING **: 
Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: 
Der angegebene Ort ist nicht eingehängt
  Aug 12 16:47:48 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:50:15 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:54:32 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:55:01 UDO dbus[2427]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
  Aug 12 16:55:01 UDO systemd[1]: Starting Hostname Service...
  Aug 12 16:55:01 UDO dbus[2427]: [system] Successfully activated service 
'org.freedesktop.hostname1'
  Aug 12 16:55:01 UDO systemd[1]: Started Hostname Service.

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

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

[Touch-packages] [Bug 1612708] Re: Symbolic Link does not work in 16.04 LTS as in 14.04 LTS

[mohican]

I ran into a bug that may be the same as yours :

My data is on a different partition than the system.
I use symbolic links in the ~ directory to access these files.

e.g. /home/me/Download is a symbolic link to /media/DATA/me/Download/

When I try to delete a file from the Download folder, accessing it
through the symbolic link, I have a message that says (I translate)
'unable to move the file to the trash do you want to delete it
completely ?' or (using Thunar on Xubuntu 16.04) **"invalid cross-device
link"**

This is the same whether the data partition is EXT4 or NTFS formated.

When I access the file directly from the /media/DATA partition I can
move it into the trash normally.

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

Title:
  Symbolic Link does not work in 16.04 LTS as in 14.04 LTS

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.1 LTS

  colord:
Installiert:   1.2.12-1ubuntu1
Installationskandidat: 1.2.12-1ubuntu1
Versionstabelle:
   *** 1.2.12-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Under Ubuntu 14.04 LTS I have created NAS access by using 'gvfs-mount
  smb://nasdo/public'. It is linked to '/run/user/1000/gvfs/ als smb-
  share:server=nasdo,share=public' and I have created a Symbolic Link to
  this point with 'ln -s /run/user/1000/gvfs/smb-
  share\:server\=nasdo\,share\=public ~/nasdo_public'. Using this link
  folders, and files on the NAS have been accessable with r/w from
  Ubuntu 14.04 LTS. This is, what I expect from 16.04, too.

  Since I have upgraded to ubuntu 16.04 LTS a few days ago, all the
  links seem to be the same, but opening a file does not work. It comes
  to an input/output error. I can use the links to folders to navigate,
  but there is no chance to open e.g. an LibreOffice Calc Sheet, nor do
  I have access to mail folder via Thunderbird.

  Using gvfs-mount creates a shared folder in Nautilus called public.
  Using this way to access the NAS, and open the Calc file works with
  ubuntu 16.04 LTS fine.

  Locking to the syslog while trying to open a file creates the following 
entries:
  Aug 12 16:47:19 UDO systemd[1]: Started Hostname Service.
  Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: 
dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der 
Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt
  Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (process:8645): WARNING **: 
Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: 
Der angegebene Ort ist nicht eingehängt
  Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: 
dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der 
Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt
  Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (process:8663): WARNING **: 
Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: 
Der angegebene Ort ist nicht eingehängt
  Aug 12 16:47:48 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:50:15 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:54:32 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:55:01 UDO dbus[2427]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
  Aug 12 16:55:01 UDO systemd[1]: Starting Hostname Service...
  Aug 12 16:55:01 UDO dbus[2427]: [system] Successfully activated service 
'org.freedesktop.hostname1'
  Aug 12 16:55:01 UDO systemd[1]: Started Hostname Service.

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

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

[Touch-packages] [Bug 1615423] Re: it was working fine from original install, one day it just stopped! sounds like a cocked up update by someone

[Till Kamppeter]

What does not work?

Please follow the instructions on

https://wiki.ubuntu.com/DebuggingPrintingProblems

when you report printing-related bugs.

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

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

Title:
  it was working fine from original install, one day it just stopped!
  sounds like a cocked up update by someone

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  from install it was fine, but all of a sudden it lost all printers and
  will not add any

  16.04.1
  chris@chris-Aspire-ES1-531:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug 21 19:16:31 2016
  InstallationDate: Installed on 2016-05-08 (105 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer Aspire ES1-531
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=UUID=10bd2765-6533-408d-9409-e1af69fef990 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire ES1-531
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd07/21/2015:svnAcer:pnAspireES1-531:pvrV1.11:rvnAcer:rnAspireES1-531:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.name: Aspire ES1-531
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1612708] Re: Symbolic Link does not work in 16.04 LTS as in 14.04 LTS

[Marc Neiger]

oddly enough it depends on how one accesses the remote files.
opening and modifying a text file with xed work on direct access (through 
/run/user )
through the symbolic link, I can read it but attempt to save after 
modifications will fail 

Could not save the file 
xed cannot handle file: locations in write mode. Please check that you typed 
the location correctly and try again.

other text editors will fail differently, leafpad truncates the file to
0 bytes!

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

Title:
  Symbolic Link does not work in 16.04 LTS as in 14.04 LTS

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.1 LTS

  colord:
Installiert:   1.2.12-1ubuntu1
Installationskandidat: 1.2.12-1ubuntu1
Versionstabelle:
   *** 1.2.12-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Under Ubuntu 14.04 LTS I have created NAS access by using 'gvfs-mount
  smb://nasdo/public'. It is linked to '/run/user/1000/gvfs/ als smb-
  share:server=nasdo,share=public' and I have created a Symbolic Link to
  this point with 'ln -s /run/user/1000/gvfs/smb-
  share\:server\=nasdo\,share\=public ~/nasdo_public'. Using this link
  folders, and files on the NAS have been accessable with r/w from
  Ubuntu 14.04 LTS. This is, what I expect from 16.04, too.

  Since I have upgraded to ubuntu 16.04 LTS a few days ago, all the
  links seem to be the same, but opening a file does not work. It comes
  to an input/output error. I can use the links to folders to navigate,
  but there is no chance to open e.g. an LibreOffice Calc Sheet, nor do
  I have access to mail folder via Thunderbird.

  Using gvfs-mount creates a shared folder in Nautilus called public.
  Using this way to access the NAS, and open the Calc file works with
  ubuntu 16.04 LTS fine.

  Locking to the syslog while trying to open a file creates the following 
entries:
  Aug 12 16:47:19 UDO systemd[1]: Started Hostname Service.
  Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: 
dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der 
Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt
  Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (process:8645): WARNING **: 
Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: 
Der angegebene Ort ist nicht eingehängt
  Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: 
dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der 
Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt
  Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (process:8663): WARNING **: 
Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: 
Der angegebene Ort ist nicht eingehängt
  Aug 12 16:47:48 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:50:15 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:54:32 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:55:01 UDO dbus[2427]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
  Aug 12 16:55:01 UDO systemd[1]: Starting Hostname Service...
  Aug 12 16:55:01 UDO dbus[2427]: [system] Successfully activated service 
'org.freedesktop.hostname1'
  Aug 12 16:55:01 UDO systemd[1]: Started Hostname Service.

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

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

[Touch-packages] [Bug 1612708] Re: Symbolic Link does not work in 16.04 LTS as in 14.04 LTS

[Launchpad Bug Tracker]

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

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

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

Title:
  Symbolic Link does not work in 16.04 LTS as in 14.04 LTS

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.1 LTS

  colord:
Installiert:   1.2.12-1ubuntu1
Installationskandidat: 1.2.12-1ubuntu1
Versionstabelle:
   *** 1.2.12-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Under Ubuntu 14.04 LTS I have created NAS access by using 'gvfs-mount
  smb://nasdo/public'. It is linked to '/run/user/1000/gvfs/ als smb-
  share:server=nasdo,share=public' and I have created a Symbolic Link to
  this point with 'ln -s /run/user/1000/gvfs/smb-
  share\:server\=nasdo\,share\=public ~/nasdo_public'. Using this link
  folders, and files on the NAS have been accessable with r/w from
  Ubuntu 14.04 LTS. This is, what I expect from 16.04, too.

  Since I have upgraded to ubuntu 16.04 LTS a few days ago, all the
  links seem to be the same, but opening a file does not work. It comes
  to an input/output error. I can use the links to folders to navigate,
  but there is no chance to open e.g. an LibreOffice Calc Sheet, nor do
  I have access to mail folder via Thunderbird.

  Using gvfs-mount creates a shared folder in Nautilus called public.
  Using this way to access the NAS, and open the Calc file works with
  ubuntu 16.04 LTS fine.

  Locking to the syslog while trying to open a file creates the following 
entries:
  Aug 12 16:47:19 UDO systemd[1]: Started Hostname Service.
  Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: 
dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der 
Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt
  Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (process:8645): WARNING **: 
Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: 
Der angegebene Ort ist nicht eingehängt
  Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: 
dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der 
Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt
  Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (process:8663): WARNING **: 
Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: 
Der angegebene Ort ist nicht eingehängt
  Aug 12 16:47:48 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:50:15 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:54:32 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:55:01 UDO dbus[2427]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
  Aug 12 16:55:01 UDO systemd[1]: Starting Hostname Service...
  Aug 12 16:55:01 UDO dbus[2427]: [system] Successfully activated service 
'org.freedesktop.hostname1'
  Aug 12 16:55:01 UDO systemd[1]: Started Hostname Service.

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

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

[Touch-packages] [Bug 1615421] Re: package fontconfig-config 2.11.0-0ubuntu4.2 failed to install/upgrade: cannot compute MD5 hash for file '/etc/fonts/conf.avail/70-force-bitmaps.conf': failed to read

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

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

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

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

Title:
  package fontconfig-config 2.11.0-0ubuntu4.2 failed to install/upgrade:
  cannot compute MD5 hash for file '/etc/fonts/conf.avail/70-force-
  bitmaps.conf': failed to read (Input/output error)

Status in fontconfig package in Ubuntu:
  Invalid

Bug description:
  idk

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fontconfig-config 2.11.0-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-92-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  Date: Sun Aug 21 10:43:51 2016
  DpkgTerminalLog: Log started: 2016-08-21  10:38:52
  ErrorMessage: cannot compute MD5 hash for file 
'/etc/fonts/conf.avail/70-force-bitmaps.conf': failed to read (Input/output 
error)
  InstallationDate: Installed on 2014-11-13 (646 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: fontconfig
  Title: package fontconfig-config 2.11.0-0ubuntu4.2 failed to install/upgrade: 
cannot compute MD5 hash for file '/etc/fonts/conf.avail/70-force-bitmaps.conf': 
failed to read (Input/output error)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1549531] Re: package linux-image-extra-4.4.0-7-generic 4.4.0-7.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[L. P. Luigi Espenlaub]

I got only the "some packages did not ..." "System might be unusable"
messages. Since I am not experienced in Ubuntu I do not know what to do
to get more specific information. Nor do I have a workaround. Afraid to
reboot.

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

Title:
  package linux-image-extra-4.4.0-7-generic 4.4.0-7.22 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Upgrade failure.
  But system is still running ...

  Edit (of 2016-02-25):
  Package in question is installed. So what's the issue? Is it just a wrong 
message I received from the system? (It was telling me that my system would be 
corrupted and probably unusable ... I'm happy it is not the case ...)

  Edit (of 2016-02-26):
  Because of some sound issues I applied following command to reinstall recent 
kernel: sudo apt-get install --reinstall linux-image-$(uname -r) 
  That fixed my sound problems so far.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-7-generic 4.4.0-7.22
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  heiko  2026 F pulseaudio
  Date: Thu Feb 25 00:27:59 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=b80b33ed-aad7-449d-a704-2b3c4433fc09
  InstallationDate: Installed on 2015-12-29 (57 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 6468AF4
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic 
root=UUID=f4457ebc-0b50-4985-af9f-ef80749359d2 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-7-generic 4.4.0-7.22 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-02-24 (0 days ago)
  dmi.bios.date: 02/27/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETD0WW (2.30 )
  dmi.board.name: 6468AF4
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 6468AF4L3C2596
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETD0WW(2.30):bd02/27/2012:svnLENOVO:pn6468AF4:pvrThinkPadT61:rvnLENOVO:rn6468AF4:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 6468AF4
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO

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

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

Re: [Touch-packages] [Bug 1615281] Re: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Greg]

I tried to reinstall all of the perl packages, but, got this error:

Couldn't  configure liblocale-gettext-perl:i386, probably a dependency
cycle problem.

I have not done anything out of the order in installing and updating
packages, so, I do not know why this is happening.

On Sun, Aug 21, 2016 at 11:26 AM Greg Silverman 
wrote:

> Hi Steve,
>
> /usr/share/perl is not present on my machine. I never did anything special
> with the perl installation, in fact, I never directly use perl. I am doing
> a complete reinstall of perl to see if that fixes the problem.
>
> Thanks,
>
> Greg
>
> On Sat, Aug 20, 2016 at 11:50 PM Steve Langasek <
> steve.langa...@canonical.com> wrote:
>
>> The error in the log is:
>>
>> Can't locate strict.pm in @INC (you may need to install the strict
>> module) (@INC contains: /etc/perl /usr/local/lib/i386-linux-gnu/perl/5.20.2
>> /usr/local/share/perl/5.20.2 /usr/lib/i386-linux-gnu/perl5/5.20
>> /usr/share/perl5 /usr/lib/i386-linux-gnu/perl/5.20 /usr/share/perl/5.20
>> /usr/local/lib/site_perl .) at /usr/sbin/update-rc.d line 6.
>> BEGIN failed--compilation aborted at /usr/sbin/update-rc.d line 6.
>> dpkg: error processing package initscripts (--configure):
>>
>> The strict.pm module is part of the perl-base package, which is an
>> Essential package.  With perl-base 5.20.2-6ubuntu0.2 in 15.10, this is
>> available at /usr/share/perl/5.20/strict.pm, which is part of the listed
>> path.
>>
>> This looks to me like a broken installation, rather than a bug in an
>> Ubuntu package.  What version of perl-base is installed at this system,
>> and is /usr/share/perl/5.20/strict.pm present?
>>
>> ** Changed in: sysvinit (Ubuntu)
>>Status: New => Incomplete
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1615281
>>
>> Title:
>>   package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade:
>>   subprocess installed post-installation script returned error exit
>>   status 2
>>
>> Status in sysvinit package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   Simply upgrading from 15.10 to 16.04.
>>
>>   ProblemType: Package
>>   DistroRelease: Ubuntu 16.04
>>   Package: initscripts 2.88dsf-59.3ubuntu2
>>   ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
>>   Uname: Linux 4.2.0-27-generic i686
>>   ApportVersion: 2.19.1-0ubuntu5
>>   Architecture: i386
>>   Date: Sat Aug 20 12:56:57 2016
>>   DuplicateSignature: package:initscripts:2.88dsf-59.3ubuntu2:subprocess
>> installed post-installation script returned error exit status 2
>>   ErrorMessage: subprocess installed post-installation script returned
>> error exit status 2
>>   InstallationDate: Installed on 2015-08-05 (381 days ago)
>>   InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
>>   RelatedPackageVersions:
>>dpkg 1.18.4ubuntu1.1
>>apt  1.2.12~ubuntu16.04.1
>>   SourcePackage: sysvinit
>>   Title: package initscripts 2.88dsf-59.3ubuntu2 failed to
>> install/upgrade: subprocess installed post-installation script returned
>> error exit status 2
>>   UpgradeStatus: Upgraded to xenial on 2016-08-20 (0 days ago)
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1615281/+subscriptions
>>
>

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

Title:
  package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in sysvinit package in Ubuntu:
  Incomplete

Bug description:
  Simply upgrading from 15.10 to 16.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initscripts 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  Date: Sat Aug 20 12:56:57 2016
  DuplicateSignature: package:initscripts:2.88dsf-59.3ubuntu2:subprocess 
installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2015-08-05 (381 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: sysvinit
  Title: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-08-20 (0 days ago)

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

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

[Touch-packages] [Bug 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]

[Emanuele Antonio Faraone]

With the last version of QtUbuntu mir and unity8 work on Atom, thanks
Gerry! It is very slow ( but faster than the old EGL convenience
version) but it works.

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

Title:
  Unity8-dash on Intel Atom graphics crashes and restarts continuously
  [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) ==
  EGL_TRUE"]

Status in Mir:
  Invalid
Status in qtubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtdeclarative package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Qt clients are failing to create an egl context when running on Intel
  Diamondville and Pineview, but not Cherryview systems under Mir.

  eglCreateContext fails with a EGL_BAD_MATCH error code.

  When it fails, Qt tries to delete & recreate the context, which then
  crashes the client (bug 1580118)

  === Original bug description ===
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.12+16.04.201604.01.1
  Version of Mir : 0.21

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

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

Re: [Touch-packages] [Bug 1615281] Re: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Greg]

Hi Steve,

/usr/share/perl is not present on my machine. I never did anything special
with the perl installation, in fact, I never directly use perl. I am doing
a complete reinstall of perl to see if that fixes the problem.

Thanks,

Greg

On Sat, Aug 20, 2016 at 11:50 PM Steve Langasek <
steve.langa...@canonical.com> wrote:

> The error in the log is:
>
> Can't locate strict.pm in @INC (you may need to install the strict
> module) (@INC contains: /etc/perl /usr/local/lib/i386-linux-gnu/perl/5.20.2
> /usr/local/share/perl/5.20.2 /usr/lib/i386-linux-gnu/perl5/5.20
> /usr/share/perl5 /usr/lib/i386-linux-gnu/perl/5.20 /usr/share/perl/5.20
> /usr/local/lib/site_perl .) at /usr/sbin/update-rc.d line 6.
> BEGIN failed--compilation aborted at /usr/sbin/update-rc.d line 6.
> dpkg: error processing package initscripts (--configure):
>
> The strict.pm module is part of the perl-base package, which is an
> Essential package.  With perl-base 5.20.2-6ubuntu0.2 in 15.10, this is
> available at /usr/share/perl/5.20/strict.pm, which is part of the listed
> path.
>
> This looks to me like a broken installation, rather than a bug in an
> Ubuntu package.  What version of perl-base is installed at this system,
> and is /usr/share/perl/5.20/strict.pm present?
>
> ** Changed in: sysvinit (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1615281
>
> Title:
>   package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade:
>   subprocess installed post-installation script returned error exit
>   status 2
>
> Status in sysvinit package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Simply upgrading from 15.10 to 16.04.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: initscripts 2.88dsf-59.3ubuntu2
>   ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
>   Uname: Linux 4.2.0-27-generic i686
>   ApportVersion: 2.19.1-0ubuntu5
>   Architecture: i386
>   Date: Sat Aug 20 12:56:57 2016
>   DuplicateSignature: package:initscripts:2.88dsf-59.3ubuntu2:subprocess
> installed post-installation script returned error exit status 2
>   ErrorMessage: subprocess installed post-installation script returned
> error exit status 2
>   InstallationDate: Installed on 2015-08-05 (381 days ago)
>   InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.1
>apt  1.2.12~ubuntu16.04.1
>   SourcePackage: sysvinit
>   Title: package initscripts 2.88dsf-59.3ubuntu2 failed to
> install/upgrade: subprocess installed post-installation script returned
> error exit status 2
>   UpgradeStatus: Upgraded to xenial on 2016-08-20 (0 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1615281/+subscriptions
>

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

Title:
  package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in sysvinit package in Ubuntu:
  Incomplete

Bug description:
  Simply upgrading from 15.10 to 16.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initscripts 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  Date: Sat Aug 20 12:56:57 2016
  DuplicateSignature: package:initscripts:2.88dsf-59.3ubuntu2:subprocess 
installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2015-08-05 (381 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: sysvinit
  Title: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-08-20 (0 days ago)

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

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

[Touch-packages] [Bug 1615423] [NEW] it was working fine from original install, one day it just stopped! sounds like a cocked up update by someone

[chris]

Public bug reported:

from install it was fine, but all of a sudden it lost all printers and
will not add any

16.04.1
chris@chris-Aspire-ES1-531:~$ apt-cache policy pkgname
N: Unable to locate package pkgname

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups (not installed)
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug 21 19:16:31 2016
InstallationDate: Installed on 2016-05-08 (105 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Acer Aspire ES1-531
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=UUID=10bd2765-6533-408d-9409-e1af69fef990 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.11
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire ES1-531
dmi.board.vendor: Acer
dmi.board.version: V1.11
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.11
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd07/21/2015:svnAcer:pnAspireES1-531:pvrV1.11:rvnAcer:rnAspireES1-531:rvrV1.11:cvnAcer:ct10:cvrV1.11:
dmi.product.name: Aspire ES1-531
dmi.product.version: V1.11
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug xenial

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

Title:
  it was working fine from original install, one day it just stopped!
  sounds like a cocked up update by someone

Status in cups package in Ubuntu:
  New

Bug description:
  from install it was fine, but all of a sudden it lost all printers and
  will not add any

  16.04.1
  chris@chris-Aspire-ES1-531:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug 21 19:16:31 2016
  InstallationDate: Installed on 2016-05-08 (105 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer Aspire ES1-531
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=UUID=10bd2765-6533-408d-9409-e1af69fef990 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire ES1-531
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd07/21/2015:svnAcer:pnAspireES1-531:pvrV1.11:rvnAcer:rnAspireES1-531:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.name: Aspire ES1-531
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1615341] Re: Yakkety desktop fails to start

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 231-4ubuntu1

---
systemd (231-4ubuntu1) yakkety; urgency=medium

  * debian/patches/units-graphical-session-pre-dont-refusemanualstart.patch:
Add a new patch to let graphical-session-pre.target be manually started
for now (LP: #1615341)

 -- Iain Lane   Sun, 21 Aug 2016 13:46:28
+0100

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

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

Title:
  Yakkety desktop fails to start

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Following a set of updates (attached) Saturday 20th I lost a working
  desktop.

  Further to that dailies for Xubuntu and Mate both fail to start a
  working desktop either by:

  1 - booting Try option from the first menu
  2 - booting Try option from the Try/Install dialogue
  3 - logging into installed system

  For Xubuntu (both locally and in installed daily)

  Changing the Exec line in /usr/share/xsessions/xubuntu.desktop from

  Exec=/usr/share/xfce4/scripts/run-systemd-session xubuntu-
  session.target

  to

  Exec=startxfce4 and my normal desktop runs again.

  (Found all this out after I reported bug 1615338, which I've now
  marked invalid)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-4
  ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5
  Uname: Linux 4.6.0-10-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 21 08:59:13 2016
  InstallationDate: Installed on 2016-06-11 (70 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-10-generic 
root=UUID=246fbeaf-5feb-4078-9c56-10a03b4fafa1 ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  modified.conffile..etc.systemd.journald.conf: [modified]
  mtime.conffile..etc.systemd.journald.conf: 2016-07-21T07:46:55.198735

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

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

[Touch-packages] [Bug 1615421] [NEW] package fontconfig-config 2.11.0-0ubuntu4.2 failed to install/upgrade: cannot compute MD5 hash for file '/etc/fonts/conf.avail/70-force-bitmaps.conf': failed to re

[clark]

Public bug reported:

idk

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fontconfig-config 2.11.0-0ubuntu4.2
ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
Uname: Linux 3.13.0-92-generic i686
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: i386
Date: Sun Aug 21 10:43:51 2016
DpkgTerminalLog: Log started: 2016-08-21  10:38:52
ErrorMessage: cannot compute MD5 hash for file 
'/etc/fonts/conf.avail/70-force-bitmaps.conf': failed to read (Input/output 
error)
InstallationDate: Installed on 2014-11-13 (646 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: fontconfig
Title: package fontconfig-config 2.11.0-0ubuntu4.2 failed to install/upgrade: 
cannot compute MD5 hash for file '/etc/fonts/conf.avail/70-force-bitmaps.conf': 
failed to read (Input/output error)
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 trusty

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

Title:
  package fontconfig-config 2.11.0-0ubuntu4.2 failed to install/upgrade:
  cannot compute MD5 hash for file '/etc/fonts/conf.avail/70-force-
  bitmaps.conf': failed to read (Input/output error)

Status in fontconfig package in Ubuntu:
  New

Bug description:
  idk

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fontconfig-config 2.11.0-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-92-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  Date: Sun Aug 21 10:43:51 2016
  DpkgTerminalLog: Log started: 2016-08-21  10:38:52
  ErrorMessage: cannot compute MD5 hash for file 
'/etc/fonts/conf.avail/70-force-bitmaps.conf': failed to read (Input/output 
error)
  InstallationDate: Installed on 2014-11-13 (646 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: fontconfig
  Title: package fontconfig-config 2.11.0-0ubuntu4.2 failed to install/upgrade: 
cannot compute MD5 hash for file '/etc/fonts/conf.avail/70-force-bitmaps.conf': 
failed to read (Input/output error)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04

[Rüdiger Plantiko]

For me, the behaviour is completely the opposite of those reported by
others:

Apps with Compose key working:
- Gnome Terminal, Dash search field

Apps with Compose key ineffective
- Gedit, LibreOffice, Chrome, Firefox

But when creating a new user and copying my .XCompose to him, for that
user the Compose key works in all applications.

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

Title:
  Compose and dead keys stopped working with XIM after upgrade to 16.04

Status in firefox package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Invalid
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04, entering characters using dead keys and
  using the Compose key stopped working in Gnome Terminal, acting like
  they are normal (non-dead) keys.

  Other applications, even those who use the same libvte (e.g. ROXTerm),
  don't have this issue.

  This happens with both the "Belgian" and "English international with
  AltGr dead keys" layouts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 20:45:33 2016
  InstallationDate: Installed on 2013-12-16 (857 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

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

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

[Touch-packages] [Bug 1615416] [NEW] feature request: automatically change timezone based on location

[Tom Dunlap]

Public bug reported:

When I travel, I often find myself changing by Ubuntu laptop's timezone,
so that it displays the local time. The clock's menu configuration
already has the ability to show the "Time in auto-detected location,"
but there is no way to display that in the indicator (without clicking
on it to display the menu.)  It would be nice if there were a way to
either:

a) change the system's timezone based on the computer's location (as if
I went in and changed it manually myself, which I often do when I
travel,) or

b) have the option to display the time of the auto-detected location
alongside the system's time in the indicator.

System Information:
○ → lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04


Package Information:
○ → apt-cache policy indicator-datetime
indicator-datetime:
  Installed: 15.10+16.04.20160406-0ubuntu1
  Candidate: 15.10+16.04.20160406-0ubuntu1
  Version table:
 *** 15.10+16.04.20160406-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  feature request: automatically change timezone based on location

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  When I travel, I often find myself changing by Ubuntu laptop's
  timezone, so that it displays the local time. The clock's menu
  configuration already has the ability to show the "Time in auto-
  detected location," but there is no way to display that in the
  indicator (without clicking on it to display the menu.)  It would be
  nice if there were a way to either:

  a) change the system's timezone based on the computer's location (as
  if I went in and changed it manually myself, which I often do when I
  travel,) or

  b) have the option to display the time of the auto-detected location
  alongside the system's time in the indicator.

  System Information:
  ○ → lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  
  Package Information:
  ○ → apt-cache policy indicator-datetime
  indicator-datetime:
Installed: 15.10+16.04.20160406-0ubuntu1
Candidate: 15.10+16.04.20160406-0ubuntu1
Version table:
   *** 15.10+16.04.20160406-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1615413] [NEW] Ubuntu Phone lost resolution switching from front camera

[costales]

Public bug reported:

Steps:
1. Open camera with back camera.
2. Set resolution 20.7MP (4:3).
3. Set selfie (front) camera.
4. Set back camera again, bug > Resolution is 12MP (5:3).

Sometimes I don't see it and I'm doing pictures in 12MP and not 20.7MP.

Thanks in advance!

** Affects: camera-app (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- Ubuntu Phone lost resolution changing switching from front camera
+ Ubuntu Phone lost resolution switching from front camera

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

Title:
  Ubuntu Phone lost resolution switching from front camera

Status in camera-app package in Ubuntu:
  New

Bug description:
  Steps:
  1. Open camera with back camera.
  2. Set resolution 20.7MP (4:3).
  3. Set selfie (front) camera.
  4. Set back camera again, bug > Resolution is 12MP (5:3).

  Sometimes I don't see it and I'm doing pictures in 12MP and not
  20.7MP.

  Thanks in advance!

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

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

[Touch-packages] [Bug 1615411] [NEW] using surudark copy/paste text selection text/icons not visible - background color not themed

[Mateo Salta]

Public bug reported:

Using UUTK 1.3 with MainView, selecting text within a WebView

- set theme to suru dark withing MainView `theme.name: 
"Ubuntu.Components.Themes.SuruDark"`
- notice that most items are themed

What happens
- forground color of text selection is set to same color of the background
- text and icons are invisible

What should happen: 
-text selection should have the background themed

Picture:

http://i.stack.imgur.com/EVvik.png

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

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

Title:
  using surudark copy/paste text selection text/icons not visible -
  background color not themed

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

Bug description:
  Using UUTK 1.3 with MainView, selecting text within a WebView

  - set theme to suru dark withing MainView `theme.name: 
"Ubuntu.Components.Themes.SuruDark"`
  - notice that most items are themed

  What happens
  - forground color of text selection is set to same color of the background
  - text and icons are invisible

  What should happen: 
  -text selection should have the background themed

  Picture:

  http://i.stack.imgur.com/EVvik.png

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

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

[Touch-packages] [Bug 1615401] Re: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[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 sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1615401

Title:
  package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in sysvinit package in Ubuntu:
  New

Bug description:
  error indicated that the system would be in an unstable state

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 08:37:35 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-08-30 (722 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: sysvinit
  Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-21 (0 days ago)

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

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

[Touch-packages] [Bug 1615401] [NEW] package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Ken Behrens]

Public bug reported:

error indicated that the system would be in an unstable state

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sysv-rc 2.88dsf-59.3ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Aug 21 08:37:35 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2014-08-30 (722 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: sysvinit
Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-08-21 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in sysvinit package in Ubuntu:
  New

Bug description:
  error indicated that the system would be in an unstable state

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 08:37:35 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-08-30 (722 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: sysvinit
  Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-21 (0 days ago)

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

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

[Touch-packages] [Bug 1364647] Re: Can't hear clock alarm when headphones are plugged in but not in your ears

[Devid Antonio Filoni]

** Branch linked: lp:~d.filoni/indicator-datetime/lp1364647

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

Title:
  Can't hear clock alarm when headphones are plugged in but not in your
  ears

Status in Band-aids for Ubuntu Phone:
  In Progress
Status in Canonical System Image:
  Confirmed
Status in Ubuntu Clock App:
  Invalid
Status in Ubuntu UX:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When a bluetooth or wired headset the phone embedded speakerphone
  should ring anyway as you probably won't wear an headset while
  sleeping, while you prefer keeping your headset connected all the
  times.

  -- SOLUTION --
  Alarms should *always* be played to the speaker phones, as well as in the 
wired/wireless headset.

  (The equivalent for the ringtone is bug 1583981.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/band-aids-uphone/+bug/1364647/+subscriptions

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

[Touch-packages] [Bug 1615230] Re: Policykit broken with latest systemd

[Launchpad Bug Tracker]

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

** Changed in: policykit-1 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Policykit broken with latest systemd

Status in policykit-1 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ex. - 
  Try to start synaptic, fails
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  Ex.2 try to unlock user accounts in system settings, fails to unlock
  unity-control-center:7708): Gtk-WARNING **: Error acquiring permission: 
Failed to acquire permission for action-id 
com.canonical.controlcenter.user-accounts.administration

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-4
  ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15
  Uname: Linux 4.4.0-9134-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Aug 20 08:59:47 2016
  InstallationDate: Installed on 2016-08-20 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160820)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9134-generic.efi.signed 
root=UUID=97a635b6-c912-465b-949d-4a4c6e8eb354 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1615230] Re: Policykit broken with latest systemd

[Launchpad Bug Tracker]

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

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

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

Title:
  Policykit broken with latest systemd

Status in policykit-1 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ex. - 
  Try to start synaptic, fails
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  Ex.2 try to unlock user accounts in system settings, fails to unlock
  unity-control-center:7708): Gtk-WARNING **: Error acquiring permission: 
Failed to acquire permission for action-id 
com.canonical.controlcenter.user-accounts.administration

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-4
  ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15
  Uname: Linux 4.4.0-9134-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Aug 20 08:59:47 2016
  InstallationDate: Installed on 2016-08-20 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160820)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9134-generic.efi.signed 
root=UUID=97a635b6-c912-465b-949d-4a4c6e8eb354 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1615395] [NEW] Ubuntu 16.04 no sound devices showing

[Anil]

Public bug reported:

I recently upgraded my laptop from Ubuntu 15.04 to 16.04. After that no
sound is working, there is no sound devices listed in sound settings.
Please help to fix it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Sun Aug 21 20:52:55 2016
InstallationDate: Installed on 2015-05-28 (451 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to xenial on 2016-08-20 (1 days ago)
dmi.bios.date: 08/05/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 02RD2H
dmi.board.vendor: Dell Inc.
dmi.board.version: A04
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn02RD2H:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3542
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Ubuntu 16.04 no sound devices showing

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I recently upgraded my laptop from Ubuntu 15.04 to 16.04. After that
  no sound is working, there is no sound devices listed in sound
  settings. Please help to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sun Aug 21 20:52:55 2016
  InstallationDate: Installed on 2015-05-28 (451 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to xenial on 2016-08-20 (1 days ago)
  dmi.bios.date: 08/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 02RD2H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn02RD2H:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1615389] [NEW] Searching for files and folders in AO takes much longer than previously

[Nikita Yerenkov-Scott]

Public bug reported:

I have noticed that after upgrading from Ubuntu GNOME 15.10 to 16.04
with GNOME 3.20 that searching for files and folders in the Activities
Overview takes much much longer when previously (before upgrading) it
would find them almost instantly as it currently does with applications.

In the preferences for Tracker I have it set up so that it is meant to
index content. What is interesting though is that for instance it might
take 5 minutes to find my Artwork folder in my Documents directory
through the AO. But if I run 'locate Artwork' in Terminal it finds it
almost instantly.

So that makes me think that perhaps it is an issue with it not properly
indexing the content or not being able to retrieve the information or
something and being forced to do a real-time search.

But it is becoming rather annoying so I thought I would report it so
that we can try to figure out what the issue is and hopefully find a
solution.

** Affects: ubuntu-gnome
 Importance: Undecided
 Status: New

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: xenial

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Searching for files and folders in AO takes much longer than
  previously

Status in Ubuntu GNOME:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in tracker package in Ubuntu:
  New

Bug description:
  I have noticed that after upgrading from Ubuntu GNOME 15.10 to 16.04
  with GNOME 3.20 that searching for files and folders in the Activities
  Overview takes much much longer when previously (before upgrading) it
  would find them almost instantly as it currently does with
  applications.

  In the preferences for Tracker I have it set up so that it is meant to
  index content. What is interesting though is that for instance it
  might take 5 minutes to find my Artwork folder in my Documents
  directory through the AO. But if I run 'locate Artwork' in Terminal it
  finds it almost instantly.

  So that makes me think that perhaps it is an issue with it not
  properly indexing the content or not being able to retrieve the
  information or something and being forced to do a real-time search.

  But it is becoming rather annoying so I thought I would report it so
  that we can try to figure out what the issue is and hopefully find a
  solution.

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

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

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

[Mario Olmedo]

same issue here on two laptops. This workaround seems to work for me
until I get a real fix.

http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-
after-16-04-upgrade

-Mario

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

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

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

[Touch-packages] [Bug 1615387] [NEW] lenovot420s power off instead of hibernate

[Aleksei]

Public bug reported:

after 14-->16 upgrade find the bug: when my battery is critically low -
laptop powers out, not hibernate as expected in spite of correct
settings

lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

uname -a
Linux atatarnikov-lt 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

** Affects: d-conf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: dist-upgrade

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

Title:
  lenovot420s power off instead of hibernate

Status in d-conf package in Ubuntu:
  New

Bug description:
  after 14-->16 upgrade find the bug: when my battery is critically low
  - laptop powers out, not hibernate as expected in spite of correct
  settings

  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  uname -a
  Linux atatarnikov-lt 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1615387/+subscriptions

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

[Touch-packages] [Bug 1491612] Re: doesn't scan for available wifi networks often enough + no way to manually force a scan

[teo1978]

> I think do frequent automatic rescan could hurt battery life, 
> so menu item for manual rescan would be better idea.

They don't need to be *very* frequent. Yes, the menu item for manual
rescan is an absolute MUST (see below though), but it also has to rescan
automatically from time to time.

Also note that the system knows when it's attached to power, and hence
can scan more frequently in that case (assuming battery consumption
really is affected).

Actually, when you manually unfold the network menu, *that* should
already trigger a rescan (if the fact that it is scanning was indicated
by an animation/icon, which it should, then there would be no need for a
specific menu item), and also automatic rescan should be more frequent
when the menu is unfolded. You aren't going to keep that menu open all
the time anyway.

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

Title:
  doesn't scan for available wifi networks often enough + no way to
  manually force a scan

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  - turn on a wifi router nearby
  - click on the network applet icon

  Expected behavior:
  As soon as the new network becomes available, it should become visible in the 
list within few seconds (and if it is a network you have already configured and 
set to automatically connect to, it should connect)

  Observed behavior:
  You won't see the network show up in the list, or perhaps it will, after a 
few minutes. Way too much time.

  
  Additionally, there should be an item in the menu such as "scan for networks 
now" to force scanning for available networks. But there's no such thing even.

  So the only workaround is to physically disable and reenable wifi on
  hardware, if your computer has a button for that. That will trigger
  re-scanning for available networks.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep  2 23:48:42 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-11 (691 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.167
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-08-15 (18 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-20T16:52:59.722501
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION   CON-UUID  CON-PATH
   
   wlan0  wifi  connected 
/org/freedesktop/NetworkManager/Devices/2  Sixty-Seven  
2dfa6e3a-076f-48f9-a40c-d182c47e4178  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   43:29:1A:07:53:91  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --   --  
  -- 
   eth0   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/1  --   --  
  -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  --   --  
  --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Aravind Gopal]

** Attachment added: "Epson scan utility cannot identify hardware(Epson L210) 
but Printer setting identifies."
   
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1536353/+attachment/4725038/+files/ScanVsPrinter%20setting6.png

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Aravind Gopal]

** Attachment added: "Simple scan is not identifying Epson L210 , But printer 
utility identifies.."
   
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1536353/+attachment/4725037/+files/ScanVsPrinter%20setting3.png

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Aravind Gopal]

Scan function of L210 multifunction is not working With the latest
Ubuntu(Xubuntu 16.04) update.

** Attachment added: "Xsane and printer utility identifies the device 
didfferently, Scan funtion not working."
   
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1536353/+attachment/4725036/+files/ScanVsPrinter%20setting1.png

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1085218] Re: upgrade to kernel 2.6.32-45 fails with "disk full error"

[Jarno Suni]

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

** This bug has been marked a duplicate of bug 1089195
   linux-headers will eat your inodes on LTS.

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

Title:
  upgrade to kernel 2.6.32-45 fails with "disk full error"

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Unable to upgrade the package 'linux-headers-2.6.32-45' either using
  Update Manager or apt-get.

  Error: There are almost 3GB of free space, but apt-get says no disk
  space. See below for details.

  I attempted the usual tricks like apt-get clean, autoclean,
  autoremove, but it made no change.

  Kind Regards.

  $ sudo apt-get upgrade

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be upgraded:
linux-headers-2.6.32-45
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 10.2MB of archives.
  After this operation, 0B of additional disk space will be used.
  Do you want to continue [Y/n]? y
  Get:1 http://mirror.anl.gov/pub/ubuntu/ lucid-updates/main 
linux-headers-2.6.32-45 2.6.32-45.100 [10.2MB]
  Fetched 10.2MB in 0s (11.7MB/s)   
  (Reading database ... 598967 files and directories currently installed.)
  Preparing to replace linux-headers-2.6.32-45 2.6.32-45.99 (using 
.../linux-headers-2.6.32-45_2.6.32-45.100_all.deb) ...
  Unpacking replacement linux-headers-2.6.32-45 ...
  dpkg: error processing 
/var/cache/apt/archives/linux-headers-2.6.32-45_2.6.32-45.100_all.deb 
(--unpack):
   unable to create 
`/usr/src/linux-headers-2.6.32-45/arch/s390/include/asm/nmi.h.dpkg-new' (while 
processing `./usr/src/linux-headers-2.6.32-45/arch/s390/include/asm/nmi.h'): No 
space left on device
  No apport report written because the error message indicates a disk full error

dpkg-deb: subprocess paste killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-headers-2.6.32-45_2.6.32-45.100_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ df -h

  FilesystemSize  Used Avail Use% Mounted on
  /dev/sda5 9.4G  6.2G  2.8G  70% /
  none  2.0G  388K  2.0G   1% /dev
  none  2.0G  212K  2.0G   1% /dev/shm
  none  2.0G  360K  2.0G   1% /var/run
  none  2.0G 0  2.0G   0% /var/lock
  none  2.0G 0  2.0G   0% /lib/init/rw
  /dev/sda6  94G   45G   45G  51% /home

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: apt 0.7.25.3ubuntu9.14
  ProcVersionSignature: Ubuntu 2.6.32-45.99-generic-pae 2.6.32.60+drm33.26
  Uname: Linux 2.6.32-45-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri Nov 30 15:33:28 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: apt

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

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

[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel

[Jarno Suni]

I suppose this may happen with unattended-upgrades, too, if user has
configured removing of old kernels.

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

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  New

Bug description:
  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run 
  /etc/kernel/postinst.d/
  during each boot (e.g. by using cron).

  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
apt-get needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 21 16:11:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (114 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 
2016-07-30T12:15:32.706300

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

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