[Touch-packages] [Bug 160999] Re: Apport doesn't overwrite existing core files

2020-02-18 Thread Michi Henning
And nearly 13 years later, we are still here.

If I have a core file in the Current directory and another run of the
program encounters a fault, the old core (possibly months old) prevents
the current core file from being written. Outstanding!

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

Title:
  Apport doesn't overwrite existing core files

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  While debugging some code, I noticed that existing core files aren't
  being overwritten when they should be.  According to core(5), the
  following file should be overwritten, but it's not:

  bam:/tmp$ id -un
  gerald
  bam:/tmp$ ls -l core
  -rw--- 1 gerald gerald 3407872 2007-10-30 21:22 core
  bam:/tmp$ date
  Thu Nov  8 09:36:23 PST 2007
  bam:/tmp$ ./coretst 
  Segmentation fault (core dumped)
  bam:/tmp$ ls -l core
  -rw--- 1 gerald gerald 3407872 2007-10-30 21:22 core

  Creating the initial core file works fine:

  bam:/tmp$ rm core
  bam:/tmp$ ./coretst 
  Segmentation fault (core dumped)
  bam:/tmp$ ls -l core
  -rw--- 1 gerald gerald 163840 2007-11-08 09:36 core
  bam:/tmp$ date
  Thu Nov  8 09:36:49 PST 2007

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

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


[Touch-packages] [Bug 1782613] Re: Periodically remove very old thumbnails or cap thumbnail cache size to avoid filling up disk with thumbnails

2018-07-19 Thread Michi Henning
This is the wrong project for that bug. The KDE thumbnailer has nothing
to do with this thumbnailer (which does enforce a size limit).

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

Title:
  Periodically remove very old thumbnails or cap thumbnail cache size to
  avoid filling up disk with thumbnails

Status in thumbnailer package in Ubuntu:
  New

Bug description:
  The cross-desktop thumbnail spec contains no provision for removing
  thumbnails, and as a result, the thumbnail cache (~/.cache/thumbnails)
  can grow without limit. For some users with large numbers of images,
  the cache can wind up taking up quite a lot of space and even causing
  free space issues. We should consider setting a maximum size for the
  cache, or removing old thumbnails not accessed in the last few years,
  or something like that.

  More information, including proposed cleanup scripts, can be found in
  the following upstream KDE bug report that was reported to track this
  issue: https://bugs.kde.org/show_bug.cgi?id=79943

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

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


[Touch-packages] [Bug 1744631] [NEW] package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit stat

2018-01-21 Thread Michi Henning
Public bug reported:

Happened during dist-upgrade from 17.04 to 17.10.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Mon Jan 22 12:37:27 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-03-22 (306 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
IpRoute:
 default via 192.168.20.1 dev enp4s0 proto static metric 100 
 169.254.0.0/16 dev enp4s0 scope link metric 1000 
 192.168.20.0/24 dev enp4s0 proto kernel scope link src 192.168.20.95 metric 100
IwConfig:
 lono wireless extensions.
 
 enp4s0no wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
RfKill:
 
SourcePackage: network-manager
Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
 Wired connection 1  ab27d84f-6bda-350b-b1c1-1cb2c4f13e6f  802-3-ethernet  
1516588648  Mon 22 Jan 2018 12:37:28 AEST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 enp4s0  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  Wired 
connection 1  ab27d84f-6bda-350b-b1c1-1cb2c4f13e6f  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  Happened during dist-upgrade from 17.04 to 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Jan 22 12:37:27 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-03-22 (306 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  IpRoute:
   default via 192.168.20.1 dev enp4s0 proto static metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   192.168.20.0/24 dev enp4s0 proto kernel scope link src 192.168.20.95 metric 
100
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  RfKill:
   
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 
failed to 

[Touch-packages] [Bug 1326105] Re: AppArmor policy for scope zmq access is too lenient

2017-05-12 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu)
 Assignee: Michi Henning (michihenning) => (unassigned)

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

Title:
  AppArmor policy for scope zmq access is too lenient

Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  Currently in apparmor-easyprof-ubuntu 1.2.3 we have:
    owner /run/user/[0-9]*/zmq/Registry-s   rw,
    owner /run/user/[0-9]*/zmq/Registry-pr,
    owner /run/user/[0-9]*/zmq/c-*-r rw,

  Note that all scopes, regardless of whether they use the ubuntu-scope-
  network or ubuntu-scope-local-content templates have access to these
  overlapped accesses. While we discussed the apparmor policy at length
  at the recent sprint, in thinking about this more there are still a
  few issues:

   1. How will the scope-registry handle when either
  /run/user/[0-9]*/zmq/Registry-s or /run/user/[0-9]*/zmq/Registry-p
  already exists?

   2. In addition to dealing with /run/user/[0-9]*/zmq/c-*-r possibly
  already existing, there is an additional issue with this access--
  because the ubuntu-scope-network and ubuntu-scope-local-content
  templates both allow this access, this allows a malicious scope author
  to create a scope using the ubuntu-scope-local-content template, then
  collect files off the filesystem and store them in
  /run/user/[0-9]*/zmq/c-I_can_leak_your_files.tar.gz-c, then upload a
  new version of the scope using the ubuntu-scope-network template,
  which can then ship
  /run/user/[0-9]*/zmq/c-I_can_leak_your_files.tar.gz-c off to a remote
  server when the user upgrades (the fact that it is in /run doesn't
  really help-- the malicious scope can save the file in its scope-
  specific directory then copy it in to place to make sure it is always
  there).

  For '1', standard defensive programming should be sufficient and
  someone should verify that the scopes API is handling when these files
  already exist (as sockets, regular files, etc, etc).

  For '2', standard defensive programming should also be used, but that
  isn't enough. I suggested at the sprint that these endpoints should be
  made application specific by their name like with the other endpoints,
  but was told this is problematic. I can (and will) update the apparmor
  policy to use this rule:

    owner
  
/run/user/[0-9]*/zmq/c-[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f]-r
  rw,

  but this doesn't solve the problem since a malicious app writer will
  just pick something matching that apparmor regular expression (AARE).
  AIUI, it is difficult/impossible to make these endpoints application
  specific (eg, "/run/user/[0-9]*/zmq/c-@{APP_PKGNAME}-r" which would be
  the preferred fix). If that is the case, we can either namespace this
  endpoint in zmq/local-fs/c-*r and zmq/local-net/c-*r and adjust the
  policy templates accordingly. I have a feeling this will have the same
  problems (or worse) as making the endpoint application specific since
  you'd need to track the type of scope this is. Alternatively, you
  could have a garbage collector to unconditionally remove any non-unix
  domain socket files and unused unix domain socket files that match
  zmq/c-*-r. While making these endpoints application specific would be
  cleanest from a policy point of view, implementing good garbage
  collection (perhaps triggered on scope start/register) would be
  sufficient to close this bug.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1326105/+subscriptions

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


[Touch-packages] [Bug 1545600] Re: Need to track abigail updates

2017-05-12 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu)
 Assignee: Michi Henning (michihenning) => (unassigned)

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

Title:
  Need to track abigail updates

Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  There are some issues with abigail, such as getting false positives
  when running abidiff with base.xml and lib.so, but not when running
  with abidiff base.xml lib.xml.

  We need to track progress here and, once a new version lands, re-test
  the abi checker and see if we can make it go faster by extracting
  directly from the latest library instead of going via an intermediate
  dump file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1545600/+subscriptions

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


[Touch-packages] [Bug 1540876] Re: Not all results recieved when there is a lot of them (>=3000?)

2017-05-12 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu)
 Assignee: Michi Henning (michihenning) => (unassigned)

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

Title:
  Not all results recieved when there is a lot of them (>=3000?)

Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  It looks like ZMQ high water-mark limits the number of results that
  can succesfuly be received by a client to something around 2000; this
  may depend on the result size and delays between pushes though. With
  3000 results in my test code I was receiving approximately 1900, the
  remainder was dropped on the floor. While these numbers are probably
  more than we will ever need, it may be worth looking into it. Perhaps
  ZMQ queue size can be increased, also a meaningful error in the logs
  about hitting such cases would be nice (if possible at all).

  I'll add a pointer to a sample test case from unity-scopes-shell at a
  later time, please contact me if I forget to do so ;)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1540876/+subscriptions

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


[Touch-packages] [Bug 1302656] Re: Scoperunner needs to be versioned using SOVERSION

2017-05-12 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu)
 Assignee: Michi Henning (michihenning) => (unassigned)

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

Title:
  Scoperunner needs to be versioned using SOVERSION

Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  If we want to provide compatibility with scopes compiled against older
  versions of the library, we need to properly version also scoperunner,
  not just the library itself. Otherwise the runner would link against
  latest version of libunity-scopes and the loaded .so against an older
  version, and things would be pretty likely to blow up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1302656/+subscriptions

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


[Touch-packages] [Bug 1469770] Re: ZmqConfig is missing tests

2017-05-12 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu)
 Assignee: Michi Henning (michihenning) => (unassigned)

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

Title:
  ZmqConfig is missing tests

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  ZmqConfig is missing unit tests (and because of that it doesn't even
  count for coverage reports).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1469770/+subscriptions

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


[Touch-packages] [Bug 1546364] Re: Links not detected in scopes

2017-05-12 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu)
 Assignee: Michi Henning (michihenning) => (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/1546364

Title:
  Links not detected in scopes

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in unity-scopes-api package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Expected Result:
  When texts from data sources includes links, these links should be 
automatically detected and should be clickable.

  Actual Result:
  The links are treated as simple texts and are not clickable.

  Best example of this is the twitter scope. There are usually links on
  posts however you need to open the tweet first just to open the link
  instead of directly clicking it from the scope.

  I think it should be automatic or let the developers decide to do it
  or maybe add a new action to open links from the post instead of
  making the link clickable  the actual content.

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

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


[Touch-packages] [Bug 1660242] Re: Thumbnailer should be packaged as a snap

2017-01-29 Thread Michi Henning
> Thumbnailer sounds like something that should already be part of other
snaps, not something that is potentially stand-alone...?

If each snap includes its own thumbnailer, each snap will redundantly
store thumbnails (making the idea of a cache much less useful).
Moreover, all the databases for the thumbnails will eat disk space like
crazy.

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

Title:
  Thumbnailer should be packaged as a snap

Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  We need to package Thumbnailer as a snap.  Some requirements are:

1. package should use strict confinement
2. service should be usable from other strictly confined snaps
3. ???

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

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


[Touch-packages] [Bug 1360247] Re: JSON format for Variant encoding uses system locale for doubles

2017-01-15 Thread Michi Henning
** Changed in: unity-scopes-api (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 unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1360247

Title:
  JSON format for Variant encoding uses system locale for doubles

Status in unity-scopes-api package in Ubuntu:
  Fix Released

Bug description:
  e.g. Variant(1.23).serialize_json() is going to give you different
  results depending on your system locale setting.

  This seems highly risky to use in any situation where the result could
  either be saved to disk (and then the system locale is changed) or if
  two different machines with different locales were communicating.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1360247/+subscriptions

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


[Touch-packages] [Bug 1238979] Re: [Scopes] Scope result models are cleared on updates

2017-01-15 Thread Michi Henning
** Changed in: unity-scopes-api (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 unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1238979

Title:
  [Scopes] Scope result models are cleared on updates

Status in Canonical System Image:
  Fix Released
Status in Ubuntu UX:
  Fix Released
Status in Unity Media Scanner Scope:
  Invalid
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  The result models are cleared when updated, which causes abrupt
  changes in the dash. We need a better way for updating the models
  without clearing them :/

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

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


[Touch-packages] [Bug 1446216] Re: [Dash] CategoryHeaderBackground is not implemented

2017-01-15 Thread Michi Henning
** Changed in: unity-scopes-api (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 unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1446216

Title:
  [Dash] CategoryHeaderBackground is not implemented

Status in Canonical System Image:
  Fix Released
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  CategoryHeaderBackground is supposed to be change appearance but has
  no effect. Quickly checking code revealed that it hasn't been
  implemented.

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

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


[Touch-packages] [Bug 1548718] Re: Need to update micro version in shlibs file when symbols are added

2017-01-15 Thread Michi Henning
** Changed in: unity-scopes-api (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 unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1548718

Title:
  Need to update micro version in shlibs file when symbols are added

Status in unity-scopes-api package in Ubuntu:
  Fix Released

Bug description:
  Currently, we are writing only major.minor into the shlibs file. But,
  if we add a new symbol to the public API and only increment the micro
  version, we really need to write the micro version as well.

  Unfortunately, that's a manual process, so we need to remember. With
  the next version of abigail, it might be possible to spit out some
  big-time warning or some such when new symbols are added to the public
  API. At least that would help to remind us.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1548718/+subscriptions

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


[Touch-packages] [Bug 1656042] Re: unity-scopes-api FTBFS with Qt 5.7.1

2017-01-15 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

** Changed in: unity-scopes-api (Ubuntu)
   Importance: Undecided => Critical

** Changed in: unity-scopes-api (Ubuntu)
   Status: New => In Progress

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

Title:
  unity-scopes-api FTBFS with Qt 5.7.1

Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  As part of test building Qt reverse dependencies, it was found unity-
  scopes-api fails to build (at least) when built against Qt 5.7.1 on
  zesty.

  As unity-scopes-api continues to work without a rebuild, it's not a
  blocker for Qt 5.7.1 transition but should be fixed for the next
  upload.

  Log: https://launchpadlibrarian.net/301312233/buildlog_ubuntu-zesty-
  amd64.unity-scopes-
  
api_1.0.7+17.04.20161115-0ubuntu2~~testrebuild1~~testrebuild1~57~57_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1656042/+subscriptions

-- 
Mailing list: https://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 1656042] Re: unity-scopes-api FTBFS with Qt 5.7.1

2017-01-13 Thread Michi Henning
Thanks for that Pete.

>From the build log, I think the issue is simply that gtest changed, and
we need to pull in your cmake fixes. I think we have those in devel
already, but not released yet. I’ll figure it out on Monday :)

Michi.


> On 13 Jan 2017, at 21:09 , Pete Woods <1656...@bugs.launchpad.net> wrote:
> 
> There seems to be some weirdness with Qt5.7 messing with build flags.
> For indicator-network, where we have C++14 enabled, Qt seemed to be
> inserting -std-c++11 (or whatever the exact flag is) in addition.
> 
> Switching to the new set(CMAKE_CXX_STANDARD 14) and set(CMAKE_C_STANDARD
> 11) seemed to resolve it.
> 
> -- 
> You received this bug notification because you are subscribed to unity-
> scopes-api in Ubuntu.
> https://bugs.launchpad.net/bugs/1656042
> 
> Title:
>  unity-scopes-api FTBFS with Qt 5.7.1
> 
> Status in unity-scopes-api package in Ubuntu:
>  New
> 
> Bug description:
>  As part of test building Qt reverse dependencies, it was found unity-
>  scopes-api fails to build (at least) when built against Qt 5.7.1 on
>  zesty.
> 
>  As unity-scopes-api continues to work without a rebuild, it's not a
>  blocker for Qt 5.7.1 transition but should be fixed for the next
>  upload.
> 
>  Log: https://launchpadlibrarian.net/301312233/buildlog_ubuntu-zesty-
>  amd64.unity-scopes-
>  
> api_1.0.7+17.04.20161115-0ubuntu2~~testrebuild1~~testrebuild1~57~57_BUILDING.txt.gz
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1656042/+subscriptions

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

Title:
  unity-scopes-api FTBFS with Qt 5.7.1

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  As part of test building Qt reverse dependencies, it was found unity-
  scopes-api fails to build (at least) when built against Qt 5.7.1 on
  zesty.

  As unity-scopes-api continues to work without a rebuild, it's not a
  blocker for Qt 5.7.1 transition but should be fixed for the next
  upload.

  Log: https://launchpadlibrarian.net/301312233/buildlog_ubuntu-zesty-
  amd64.unity-scopes-
  
api_1.0.7+17.04.20161115-0ubuntu2~~testrebuild1~~testrebuild1~57~57_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1656042/+subscriptions

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-12-20 Thread Michi Henning
** Changed in: thumbnailer (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 taglib in Ubuntu.
https://bugs.launchpad.net/bugs/1640326

Title:
  FTBFS on zesty

Status in leveldb package in Ubuntu:
  Confirmed
Status in taglib package in Ubuntu:
  Invalid
Status in thumbnailer package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1472755] Re: corrupted double-linked list probably cause by telegram scope

2016-12-20 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: unity-scopes-api (Ubuntu RTM)
   Status: Confirmed => Fix Released

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

Title:
  corrupted double-linked list probably cause by telegram scope

Status in Canonical System Image:
  Fix Released
Status in libqtelegram package in Ubuntu:
  Incomplete
Status in unity-scope-mediascanner package in Ubuntu:
  Invalid
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-api package in Ubuntu RTM:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-scope-mediascanner.  This problem was most recently
  seen with version 1.7.16, the problem page at
  https://errors.ubuntu.com/problem/21d9e7ddf91a26b21abfb2758315ad41fcfd3fa9
  contains more details.

  "/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in
  `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': corrupted
  double-linked list: ADDR ***"

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

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


[Touch-packages] [Bug 1649313] Re: SD card not recognized on M10 with ubuntu-touch/staging/ubuntu

2016-12-19 Thread Michi Henning
** Summary changed:

- frieza_arm64, staging #99: SD card not mounted
+ SD card not recognized on M10 with ubuntu-touch/staging/ubuntu

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

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

Title:
  SD card not recognized on M10 with ubuntu-touch/staging/ubuntu

Status in Canonical System Image:
  New
Status in mediascanner2 package in Ubuntu:
  Invalid
Status in udisks2 package in Ubuntu:
  New

Bug description:
  Story: looks like this is a well known bug but there wasn't a bug
  report yet so I'm opening it. Sdcards detection doesn't work in
  frieza_arm64.

  Environment:

  current build number: 99
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-12-12 12:21:18
  version version: 99
  version ubuntu: 20161210
  version device: 20161014.0
  version custom: 20161210

  Steps:

  1º Put some media files(songs,videos) on a sdcard
  2º Install the sdcard in frieza
  3º Open music app or music/video scopes

  Current result: music app reports no songs were found and music/video
  scopes don't show the media files either

  Expected result: all files from sdcard or other external devices
  should be detected

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

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


[Touch-packages] [Bug 1649313] Re: Mediascanner is not working

2016-12-18 Thread Michi Henning
** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  Mediascanner is not working

Status in Canonical System Image:
  New
Status in mediascanner2 package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New

Bug description:
  Story: looks like this is a well known bug but there wasn't a bug
  report yet so I'm opening it. Sdcards detection doesn't work in
  frieza_arm64.

  Environment:

  current build number: 99
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-12-12 12:21:18
  version version: 99
  version ubuntu: 20161210
  version device: 20161014.0
  version custom: 20161210

  Steps:

  1º Put some media files(songs,videos) on a sdcard
  2º Install the sdcard in frieza
  3º Open music app or music/video scopes

  Current result: music app reports no songs were found and music/video
  scopes don't show the media files either

  Expected result: all files from sdcard or other external devices
  should be detected

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

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


[Touch-packages] [Bug 1649313] Re: Mediascanner is not working

2016-12-15 Thread Michi Henning
I downloaded the latest image from ubuntu-touch/staging/ubuntu

"OS Build Details" in system settings reports r85, 20161215

Unfortunately, I can't provide the output from system-image-cli because,
since flashing this image, USB is broken. I can no longer get my desktop
to recognize the USB port. It's as if the USB port is dead (lsusb
doesn't find the device). Developer mode is on, and when I plug my
Aquaris E5 into the same port using the same cable, it's recognized just
fine.

Anyway, after installing this image, the SD card is no longer recognized
at all, no matter how many times I insert it. (The same card works fine
in the E5.)

I guess the problem is with the image from ubuntu-touch/staging/ubuntu

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

Title:
  Mediascanner is not working

Status in mediascanner2 package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New

Bug description:
  Story: looks like this is a well known bug but there wasn't a bug
  report yet so I'm opening it. Sdcards detection doesn't work in
  frieza_arm64.

  Environment:

  current build number: 99
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-12-12 12:21:18
  version version: 99
  version ubuntu: 20161210
  version device: 20161014.0
  version custom: 20161210

  Steps:

  1º Put some media files(songs,videos) on a sdcard
  2º Install the sdcard in frieza
  3º Open music app or music/video scopes

  Current result: music app reports no songs were found and music/video
  scopes don't show the media files either

  Expected result: all files from sdcard or other external devices
  should be detected

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

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


[Touch-packages] [Bug 1649313] Re: Mediascanner is not working

2016-12-15 Thread Michi Henning
I just tried with OTA-14, and it works fine there too. However, the
first time I inserted the card, it wasn't recognized. It was only after
I ejected and re-inserted it that it was mounted.

This may just be dodgy connectors in the card slot.

I'll also try with image you linked to.

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

Title:
  Mediascanner is not working

Status in mediascanner2 package in Ubuntu:
  New

Bug description:
  Story: looks like this is a well known bug but there wasn't a bug
  report yet so I'm opening it. Sdcards detection doesn't work in
  frieza_arm64.

  Environment:

  current build number: 99
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-12-12 12:21:18
  version version: 99
  version ubuntu: 20161210
  version device: 20161014.0
  version custom: 20161210

  Steps:

  1º Put some media files(songs,videos) on a sdcard
  2º Install the sdcard in frieza
  3º Open music app or music/video scopes

  Current result: music app reports no songs were found and music/video
  scopes don't show the media files either

  Expected result: all files from sdcard or other external devices
  should be detected

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

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


[Touch-packages] [Bug 1649313] Re: Mediascanner is not working

2016-12-15 Thread Michi Henning
It could be just that the card slot is dirty or some such. I would also
try a reboot. Possibly, some other low-level piece of machinery got
stuck. At any rate, I don't think this is a mediascanner problem. If the
card isn't mounted, mediascanner can't possibly see it.

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

Title:
  Mediascanner is not working

Status in mediascanner2 package in Ubuntu:
  New

Bug description:
  Story: looks like this is a well known bug but there wasn't a bug
  report yet so I'm opening it. Mediascanner doesn't work in
  frieza_arm64 so files in sdcards aren't detected.

  Environment:

  current build number: 99
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-12-12 12:21:18
  version version: 99
  version ubuntu: 20161210
  version device: 20161014.0
  version custom: 20161210

  Steps:

  1º Put some media files(songs,videos) on a sdcard
  2º Install the sdcard in frieza
  3º Open music app or music/video scopes

  Current result: music app reports no songs were found and music/video
  scopes don't show the media files either

  Expected result: all files from sdcard r other external devices should
  be detected

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

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


[Touch-packages] [Bug 1649313] Re: Mediascanner is not working

2016-12-14 Thread Michi Henning
I tried it with build 191 from ubuntu-touch/rc-proposed/bq-aquaris-pd.en.
After inserting an SD card with a few music and image files, the music scope 
shows the tracks, and gallery app shows all the images on the card.

I'm about to try with OTA 14. But I expect to see the same results.

Can you install the file manager app from the store and check if you can
see the card contents with that? If not, mediascanner is innocent; it
can't see the card if it isn't mounted.

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

Title:
  Mediascanner is not working

Status in mediascanner2 package in Ubuntu:
  New

Bug description:
  Story: looks like this is a well known bug but there wasn't a bug
  report yet so I'm opening it. Mediascanner doesn't work in
  frieza_arm64 so files in sdcards aren't detected.

  Environment:

  current build number: 99
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-12-12 12:21:18
  version version: 99
  version ubuntu: 20161210
  version device: 20161014.0
  version custom: 20161210

  Steps:

  1º Put some media files(songs,videos) on a sdcard
  2º Install the sdcard in frieza
  3º Open music app or music/video scopes

  Current result: music app reports no songs were found and music/video
  scopes don't show the media files either

  Expected result: all files from sdcard r other external devices should
  be detected

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

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


[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-14 Thread Michi Henning
It looks like click-scope is the only scope that is failing. Queries to
the music scope work just fine, as do queries to remote scopes (via
smartscopesproxy). All these scopes run the exact same code in the
runtime.

I have no idea what exactly is going wrong, but I strongly suspect that
it is in click scope or one of the dependencies it calls into.

Note that the messages about the closed socket may well be consequential
if a thread that wasn't created by the scopes run time throws. (If
click-scope uses QtDBus, possibly an exception could escape from one of
its threads? Or maybe net-cpp underneath or some such?)

It would be really useful to have some trace from click scope to see
what it is up to when it receives a query.

Also, it looks like I'm not getting any core dumps in the
unity8-session. Is there a way to enable those? It might give us a
chance at getting a stack trace from the click-scope.

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-13 Thread Michi Henning
I've spent pretty much all day trying to track this down. The debug
cycle time with core 16 in a VM doesn't help :-(

What I can see is that crap comes out of the ZmqReceiver when an object
adapter tries to dispatch an incoming request to the scope. The problem
doesn't manifest itself in the same way on each run. Sometimes, the read
from the socket returns zero bytes, which triggers the "socket was
closed" error.

Other times, the number of bytes read doesn't divide by the word size,
which triggers an "impossible message size" error.

Yet other times, things fall over in the ObjectAdapter::dispatch()
method when something throws during unmarshaling (presumably because the
data that was read is crap), which is reported as "error unmarshaling
request header".

It all points to some problem with zmq not respecting framing boundaries
or indicating that a socket has a message ready to read, but then
delivering incomplete or crap data.

I don't understand at this point why this happens with core 16 and not
on classic. The library versions for zmq match what I have on my
desktop.

I'll try this again tomorrow on classic and see whether I can figure out
what's going wrong by comparing trace.

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-09 Thread Michi Henning
@dobey: There is in the log: terminate called after throwing an instance
of 'unity::scopes::MiddlewareException'

I don't know where this exception comes from. It would be great to find
out. I believe that, if an exception is thrown (no matter what kind of
exception) from one of the threads we send into the scope, the runtime
will handle it correctly. (If not, that's a bug in scopes-api.) But, if
the exception is thrown by a thread that wasn't created by the scopes
runtime, there is obviously nothing much we can do. (In that case, the
other errors are consequential errors, I'd say.)

@mterry: Yes, I did this in side the VM after starting the session.
There is no /run/user/0/dbus-session.

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-08 Thread Michi Henning
Michael, the command fails because /run/user/0/dbus-session doesn't exist.
I also looks like I have a different version installed. I see 264 and 277 
(besides common) in /root/snap/unity8-session.

I adjusted your command to not set DBUS_SESSION_ADDRESS and explicitly
set LD_LIBRARY_PATH (without using snappyenv):

1_DEBUG=1 SNAP_USER_COMMON=/root/snap/unity8-session/common
SNAP_USER_DATA=/root/snap/unity8-session/277 SNAP_ARCH=amd64
HOME=/root/snap/unity8-session/277
LD_LIBRARY_PATH=/snap/unity8-session/current/usr/lib/x86_64-linux-gnu
/snap/unity8-session/current/usr/lib/x86_64-linux-gnu/unity-
scopes/scoperunner "" /snap/unity8-session/current/usr/lib/x86_64-linux-
gnu/unity-scopes/clickapps/clickscope.ini

This yields:

# U1_DEBUG=1 SNAP_USER_COMMON=/root/snap/unity8-session/common 
SNAP_USER_DATA=/root/snap/unity8-session/277 SNAP_ARCH=amd64 
HOME=/root/snap/unity8-session/277 
LD_LIBRARY_PATH=/snap/unity8-session/current/usr/lib/x86_64-linux-gnu 
/snap/unity8-session/current/usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner 
"" 
/snap/unity8-session/current/usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini
 QSqlDatabase: QSQLITE driver not loaded
QSqlDatabase: available drivers: 
QSqlDatabase: an instance of QCoreApplication is required for loading driver 
plugins
Failed to open departments db: Cannot open departments database
[2016-12-09 05:56:44.991] ERROR: clickscope: unity::scopes::ConfigException: 
Cannot instantiate run time for clickscope, config file: :
unity::scopes::MiddlewareException: cannot initialize zmq middleware for 
scope clickscope:
unity::scopes::ConfigException: No endpoint directories specified, and 
XDG_RUNTIME_DIR environment variable not set
scoperunner: unity::scopes::ConfigException: Cannot instantiate run time for 
clickscope, config file: :
unity::scopes::MiddlewareException: cannot initialize zmq middleware for 
scope clickscope:
unity::scopes::ConfigException: No endpoint directories specified, and 
XDG_RUNTIME_DIR environment variable not set

Running this with snappyenv, I get:

# U1_DEBUG=1 SNAP_USER_COMMON=/root/snap/unity8-session/common 
SNAP_USER_DATA=/root/snap/unity8-session/277 SNAP_ARCH=amd64 
HOME=/root/snap/unity8-session/277 /snap/unity8-session/current/snappyenv 
/snap/unity8-session/current/usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner 
"" 
/snap/unity8-session/current/usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini
 ERROR: ld.so: object '/lib/libsnap-preload-shim.so' from LD_PRELOAD cannot be 
preloaded (cannot open shared object file): ignored.
mkdir: cannot create directory ‘/lightdm-data’: Read-only file system
/snap/unity8-session/current/snappyenv: 113: exec: /bin/desktop-launch: not 
found

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-08 Thread Michi Henning
** Also affects: unity-scopes-api (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity-scopes-api (Ubuntu)
   Importance: Undecided => Critical

** Changed in: unity-scopes-api (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

** Changed in: unity-api (Ubuntu)
   Status: In Progress => Invalid

** Changed in: unity-scopes-api (Ubuntu)
   Status: New => In Progress

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-08 Thread Michi Henning
> "BFB" is "Big Flavorful Button" ;)

Ah, as in "BFG-9000" :-)

> So, from your screenshot it looks like you are hitting case number 2 from my 
> previous post. Is
> there a crash report in /var/crash/ for the scoperunner?

/var/crash doesn't exist on a snappy machine. I have no idea where core
dumps end up. It looks like core dumps are disabled. I can't find any
cores anywhere.

> If not, does running "ubuntu-app-launch-appids" on this system show
any snap results?

ubuntu-app-launch doesn't exist either.

> Can you attach the unity8-dash.log and scope-registry.log files? Normally 
> they are in
> ~/.cache/upstart/ but not sure where exactly that equates to for the unity8 
> snap on core.

I'm seeing an unhandled exception from the click scope.

Registry log: pastebin.ubuntu.com/23602020

I suspect that the exception isn't coming from one of the threads that
we hand to the scope. (We very carefully handle all exceptions that a
scope might throw.) It seems more likely that the exception comes from a
thread that wasn't created by the scopes run time.

The trail of exceptions from shutdown() is unsurprising because the
scopes runtime realises that something isn't right and just logs the
error.

unity8-dash log: pastebin.ubuntu.com/23602037

There is a line with "results invalidated". Not sure whether that is
significant.

Note that no network is present inside the core 16 VM. I don't know how
to get that working, and I don't know whether that relates to the crash.
I set up the VM following the instructions Kevin posted:

https://docs.google.com/document/d/1o-
jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc/edit?pli=1#heading=h.q06bivmaid8f

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1310186] Re: mediascanner prevents unmounting usb device

2016-12-08 Thread Michi Henning
There doesn't appear to be a way to be notified of unmount attempts at
the moment. There is an fschange modification about ten years ago
(http://stefan.buettcher.org/cs/fschange/), but that never made it into
the kernel.

It looks like it's impossible for mediascanner to automatically back off
when an unmount attempt is made.

You can kill the mediascanner process and then unmount. (Not of much
help to naive user, I admit.)

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

Title:
  mediascanner prevents unmounting usb device

Status in mediascanner2 package in Ubuntu:
  Triaged

Bug description:
  Trying to unmount a block device I just mounted, I get the following
  error (sorry for not resetting the locale. It says "Device is busy"):

  :~$ sudo umount /media/tkluck/tjk-backup 
  umount2: Apparaat of hulpbron is bezig
  umount: /media/tkluck/tjk-backup: apparaat is bezig
  (Welke processen het apparaat gebruiken kan mogelijk
   gevonden worden met behulp van lsof(8) of fuser(1).)
  umount2: Apparaat of hulpbron is bezig

  I get the same error in a dialog window when trying to unmount from
  the file manager.

  Using lsof shows that the media-scanner daemon is the culprit:

  tkluck@ultrabook-tjk:~$ lsof /media/tkluck/tjk-backup 
  COMMANDPID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
  mediascan 2898 tkluck   16r   DIR  252,3   2498562 
/media/tkluck/tjk-backup
  mediascan 2898 tkluck   17r   DIR  252,3 4096 50855937 
  mediascan 2898 tkluck   18r   DIR  252,3 4096 39080372 
  mediascan 2898 tkluck   19r   DIR  252,312288 39080513 
  mediascan 2898 tkluck   20r   DIR  252,320480 39080525 
  mediascan 2898 tkluck   21r   DIR  252,3 4096 46792990 
  mediascan 2898 tkluck   22r   DIR  252,3 4096 46792991 
  mediascan 2898 tkluck   23r   DIR  252,316384 46793749 
  mediascan 2898 tkluck   24r   DIR  252,3 4096 47317994 
  mediascan 2898 tkluck   25r   DIR  252,3 4096 47317997 
  mediascan 2898 tkluck   26r   DIR  252,3 4096 47317999 

  Sending it

  sudo kill -9 2898

  solved this for me.

  This is on Ubuntu GNOME 14.04. I uninstalled the mediascanner2.0 to
  solve this "once and for all" (which has no other impact since I do
  not use Unity).

  My guess is that the scan usually finishes quickly after mounting. But
  because this particular drive contains a big filetree, it doesn't,
  resulting in the issue.

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

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


[Touch-packages] [Bug 1648450] Re: Mediascanner keeps volume busy when removing and gives errors

2016-12-08 Thread Michi Henning
*** This bug is a duplicate of bug 1310186 ***
https://bugs.launchpad.net/bugs/1310186

** This bug has been marked a duplicate of bug 1310186
   mediascanner prevents unmounting usb device

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

Title:
  Mediascanner keeps volume busy when removing and gives errors

Status in mediascanner2 package in Ubuntu:
  New

Bug description:
  This annoying thing happens when I connect a USB drive with a lot of
  media content and then shortly try to "safely remove" the device.

  Step to reproduce:
  1) Connect a USB drive with a lot of media content (not sure if a lot of 
media is really needed, but I'm not going to delete stuff from my disk to test)
  2) From Nautilus right-click the device icon and choose "safely remove the 
device"
  3) Observe that a dialog opens saying that "Volume is busy"
  4) Click "Eject Anyway"
  5) Observe an error dialog saying something like "Unable to stop "WDC 
WD10JPVX-22JC3T0"

  So did it fail or what? Is this good or bad? Will I corrupt my data if
  I just disconnect it after possibly copying some files? This is not
  good usability, at least.

  What should happen:
  - The device should get disconnected without errors. If not right after 
safely removing, but after having clicked "Eject Anyway".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mediascanner2.0 0.111+16.04.20160317-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec  8 14:43:21 2016
  InstallationDate: Installed on 2016-09-13 (86 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: mediascanner2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-07 Thread Michi Henning
Sorry, I don't know what a "BFB result" is. It does show "Apps". I've
attached a screenshot.

** Attachment added: "Screenshot from 2016-12-08 14-23-54.png"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645798/+attachment/477/+files/Screenshot%20from%202016-12-08%2014-23-54.png

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  In Progress
Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-06 Thread Michi Henning
The assertion failure appears to be unrelated to the click scope not showing 
any results.
What is interesting is that the other scopes seems to work fine, it's only the 
click scope that is empty. With the missing applications dir in place, I'm not 
seeing any errors at all in the logs, just the empty search results from the 
click scope. This suggests that the scopes-api infrastructure is working and 
the problem is somewhere in click scope or its dependencies.

** Also affects: unity-scope-click (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  In Progress
Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1647946] [NEW] Latest online accounts breaks unity-scopes-api

2016-12-06 Thread Michi Henning
Public bug reported:

We just got this test failure on zesty:

https://jenkins.canonical.com/unity-
api-1/job/build-2-binpkg/arch=armhf,release=zesty/1022/consoleFull

Search for "OnlineAccountClientTest.service_update_callback"

In the log, we see
"GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.MethodNotKnown:
Authentication method is not known."

This test has worked for well over a year and has never failed.
Something must have changed outside scopes-api.

** Affects: account-plugins
 Importance: Undecided
 Status: New

** Affects: unity-scopes-api (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: unity-scopes-api (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Latest online accounts breaks unity-scopes-api

Status in Online Accounts: Account plugins:
  New
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  We just got this test failure on zesty:

  https://jenkins.canonical.com/unity-
  api-1/job/build-2-binpkg/arch=armhf,release=zesty/1022/consoleFull

  Search for "OnlineAccountClientTest.service_update_callback"

  In the log, we see
  "GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.MethodNotKnown:
  Authentication method is not known."

  This test has worked for well over a year and has never failed.
  Something must have changed outside scopes-api.

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1647946/+subscriptions

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


[Touch-packages] [Bug 1631171] Re: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-12-06 Thread Michi Henning
*** This bug is a duplicate of bug 1643169 ***
https://bugs.launchpad.net/bugs/1643169

See comment #2 here: https://bugs.launchpad.net/ubuntu/+source/unity-
scopes-api/+bug/1643169

** This bug has been marked a duplicate of bug 1643169
   package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1

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

Title:
  package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  appears upon logging in

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  5 19:25:54 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-07-01 (96 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-04 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1631171/+subscriptions

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


[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-06 Thread Michi Henning
The missing applications dir was coincidental and isn't the root cause of this 
problem.
The issue is racy, so I'm seeing different things in the logs each time.
Still digging...

** Branch unlinked: lp:~michihenning/unity-scopes-api/create-
applications-dir

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  In Progress

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-05 Thread Michi Henning
I'll push a branch to have the registry create the applications dir if
it doesn't exist. That should be good enough for the moment. But the
whole .desktop file generation thing is a hack. As far as we can work
out, this was needed because online accounts refused to work unless
there was a .desktop file.

** Changed in: unity-api (Ubuntu)
   Importance: Undecided => Critical

** Changed in: unity-api (Ubuntu)
   Status: New => In Progress

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  In Progress

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-05 Thread Michi Henning
I would like to track down what causes the assertion failure in scopes-
api regardless.

DBUS_SESSION_BUS_ADDRESS=`cat /run/user/0/dbus-session | cut -f2- -d=`
HOME=/root/snap/unity8-session/264
SNAP_USER_DATA=/root/snap/unity8-session/264
SNAP_USER_COMMON=/root/snap/unity8-session/common SNAP_ARCH=amd64
SNAP=/snap/unity8-session/current U1_DEBUG=1 /root/snappyenv
/snap/unity8-session/current/usr/lib/x86_64-linux-gnu/unity-
scopes/scoperunner "" /snap/unity8-session/current/usr/lib/x86_64-linux-
gnu/unity-scopes/clickapps/clickscope.ini

This won't run for me because I don't have /root/snappyenv. What's in
that file? It looks like it's a script that sets up a bunch of env vars
and execs the remainder of the command line?

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  New

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-05 Thread Michi Henning
Looking at /root/snap/unity8-session/common/.cache/upstart/scope-
registry.log, there are lots of messages along the following lines:

scoperegistry: ignoring scope "clickscope": cannot create metadata:
unity::SyscallException: RegistryObject::create_desktop_file: unable to
create desktop file:
"/root/snap/unity8-session/common/.local/share/applications/clickscope.desktop"
(errno = 2)

The problem is that the applications subdirectory does not exist, but
scopes expect that directory to be pre-installed. In turn, failure to
create the desktop file causes the registry to not add metadata for
local scopes.

After creating the directory, the errors go away, and unity8-dash.log
looks clean. I'm seeing results from 7digital and amazon on a search
(albeit without thumbnails) once the applications directory exists,
which indicates that the scopes infrastructure is working.

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  New

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-11-30 Thread Michi Henning
I've added Pawel because of the "Invalid departments database" error.

I'm looking at the other errors. I suspect what's happening is that some
of the local socket path names are wrong.

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  New

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-11-11 Thread Michi Henning
** Changed in: thumbnailer (Ubuntu)
   Status: New => Fix Committed

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

Title:
  FTBFS on zesty

Status in leveldb package in Ubuntu:
  Confirmed
Status in taglib package in Ubuntu:
  Invalid
Status in thumbnailer package in Ubuntu:
  Fix Committed

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-11-11 Thread Michi Henning
Sorry wrong link for upstream bug. It's here:
https://github.com/google/leveldb/issues/425

** Bug watch added: github.com/google/leveldb/issues #425
   https://github.com/google/leveldb/issues/425

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

Title:
  FTBFS on zesty

Status in leveldb package in Ubuntu:
  New
Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-11-10 Thread Michi Henning
Upstream bug here: https://github.com/Level/leveldown/issues/321

** Bug watch added: github.com/Level/leveldown/issues #321
   https://github.com/Level/leveldown/issues/321

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

Title:
  FTBFS on zesty

Status in leveldb package in Ubuntu:
  New
Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-11-10 Thread Michi Henning
The builder uses libleveldb 1.19-2, but the zesty archives still have 
libleveldb 1.18-5.
After installing 1.19-2 locally, I instantly got the same failure.

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

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

Title:
  FTBFS on zesty

Status in leveldb package in Ubuntu:
  New
Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-11-10 Thread Michi Henning
After lots of debugging and tracing, I found the root cause with
valgrind. The interesting thing is that this happens only in the silo.
When I run the same code on my zesty VM, everything is fine. So, what is
different in the silo builders from a vanilla zesty install? (Installed
zesty about two days ago. Is it possible that the builders are missing
some updates?)

1: ==8494== Process terminating with default action of signal 11 (SIGSEGV)
1: ==8494==  Access not within mapped region at address 0x61632F6D6F6347
1: ==8494==at 0x4EB5804: 
leveldb::InternalFilterPolicy::CreateFilter(leveldb::Slice const*, int, 
std::__cxx11::basic_string*) const (in /usr/lib/aarch64-linux-gnu/libleveldb.so.1.19)
1: ==8494==by 0x4ECBBAF: leveldb::FilterBlockBuilder::GenerateFilter() (in 
/usr/lib/aarch64-linux-gnu/libleveldb.so.1.19)
1: ==8494==by 0x4ECBD87: leveldb::FilterBlockBuilder::StartBlock(unsigned 
long) (in /usr/lib/aarch64-linux-gnu/libleveldb.so.1.19)
1: ==8494==by 0x4ED1F8F: leveldb::TableBuilder::Flush() (in 
/usr/lib/aarch64-linux-gnu/libleveldb.so.1.19)
1: ==8494==by 0x4ED2113: leveldb::TableBuilder::Add(leveldb::Slice const&, 
leveldb::Slice const&) (in /usr/lib/aarch64-linux-gnu/libleveldb.so.1.19)
1: ==8494==by 0x4EA68AB: 
leveldb::BuildTable(std::__cxx11::basic_string const&, leveldb::Env*, leveldb::Options const&, 
leveldb::TableCache*, leveldb::Iterator*, leveldb::FileMetaData*) (in 
/usr/lib/aarch64-linux-gnu/libleveldb.so.1.19)
1: ==8494==by 0x4EAD183: 
leveldb::DBImpl::WriteLevel0Table(leveldb::MemTable*, leveldb::VersionEdit*, 
leveldb::Version*) (in /usr/lib/aarch64-linux-gnu/libleveldb.so.1.19)
1: ==8494==by 0x4EAEECF: leveldb::DBImpl::CompactMemTable() (in 
/usr/lib/aarch64-linux-gnu/libleveldb.so.1.19)
1: ==8494==by 0x4EAFD3F: leveldb::DBImpl::BackgroundCompaction() (in 
/usr/lib/aarch64-linux-gnu/libleveldb.so.1.19)
1: ==8494==by 0x4EB051F: leveldb::DBImpl::BackgroundCall() (in 
/usr/lib/aarch64-linux-gnu/libleveldb.so.1.19)
1: ==8494==by 0x4ED7C3B: ??? (in 
/usr/lib/aarch64-linux-gnu/libleveldb.so.1.19)
1: ==8494==by 0x53E901B: start_thread (pthread_create.c:335)

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

Title:
  FTBFS on zesty

Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-11-10 Thread Michi Henning
Almost certainly not related. The test that triggers this is far away
from the core dump. Still worth following up on though.

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

Title:
  FTBFS on zesty

Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-11-10 Thread Michi Henning
I'm seeing this report from valgrind on zesty. On xenial, the test runs
clean. Not sure whether this might be related.

==63566== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 10 from 10)
==63463== Conditional jump or move depends on uninitialised value(s)
==63463==at 0x4C33E26: rawmemchr (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==63463==by 0x792D701: _IO_str_init_static_internal (strops.c:41)
==63463==by 0x791F6B6: vsscanf (iovsscanf.c:40)
==63463==by 0x79198F6: sscanf (sscanf.c:32)
==63463==by 0x61D1486: aa_query_label (in 
/lib/x86_64-linux-gnu/libapparmor.so.1.4.0)
==63463==by 0x17B207: (anonymous namespace)::query_file((anonymous 
namespace)::Access, std::__cxx11::basic_string const&, std::__cxx11::basic_string const&) (check_access.cpp:59)
==63463==by 0x17B379: 
unity::thumbnailer::internal::apparmor_can_read(std::__cxx11::basic_string const&, 
std::__cxx11::basic_string 
const&) (check_access.cpp:80)
==63463==by 0x16B6B1: unity::thumbnailer::internal::(anonymous 
namespace)::LocalThumbnailRequest::check_client_credentials(unsigned int, 
std::__cxx11::basic_string 
const&) (thumbnailer.cpp:546)
==63463==by 0x14E5CC: ThumbnailerTest_check_client_access_Test::TestBody() 
(thumbnailer_test.cpp:579)
==63463==by 0x1AAFC3: void 
testing::internal::HandleSehExceptionsInMethodIfSupported(testing::Test*, void (testing::Test::*)(), char const*) (gtest.cc:2078)
==63463==by 0x1A630E: void 
testing::internal::HandleExceptionsInMethodIfSupported(testing::Test*, void (testing::Test::*)(), char const*) (gtest.cc:2114)
==63463==by 0x18BF7B: testing::Test::Run() (gtest.cc:2151)
==63463==by 0x18C7C7: testing::TestInfo::Run() (gtest.cc:2326)
==63463==by 0x18CE33: testing::TestCase::Run() (gtest.cc:2444)
==63463==by 0x193E91: testing::internal::UnitTestImpl::RunAllTests() 
(gtest.cc:4315)
==63463==by 0x1ABF06: bool 
testing::internal::HandleSehExceptionsInMethodIfSupported(testing::internal::UnitTestImpl*, bool 
(testing::internal::UnitTestImpl::*)(), char const*) (gtest.cc:2078)
==63463==by 0x1A70D2: bool 
testing::internal::HandleExceptionsInMethodIfSupported(testing::internal::UnitTestImpl*, bool 
(testing::internal::UnitTestImpl::*)(), char const*) (gtest.cc:2114)
==63463==by 0x192A8C: testing::UnitTest::Run() (gtest.cc:3926)
==63463==by 0x15B30B: RUN_ALL_TESTS() (gtest.h:2288)
==63463==by 0x15942E: main (thumbnailer_test.cpp:1042)

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

Title:
  FTBFS on zesty

Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-11-09 Thread Michi Henning
I think we can rule out leveldb. It's at revision 1.18-5 in both xenial
and zesty.

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

Title:
  FTBFS on zesty

Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-11-09 Thread Michi Henning
Taglib fix is in the linked branch.

The thumbnailer test dumps core on all architectures on zesty. The fault
keeps moving around, looks like a race condition. We are not using
threads ourselves, so the problem likely is in a something we call into.
Candidates would be QT and (unlikely) leveldb.

I've run the tests for several hours continuously on my zesty amd64 VM,
without error. The fault shows up only in the silo.

For added amusement, the qml test for vivid arm64 is segfaulting. I have
no idea what might be causing this. The thumbnailer code has been stable
for many months and hasn't ever had this kind of problem.

I suspect that the issue is with something that is installed on the
builder. But there is no way to get a core dump when something fails in
a builder, so I don't know how to debug this. Without a core dump, we
are stabbing around in the dark :-(

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

Title:
  FTBFS on zesty

Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-11-09 Thread Michi Henning
I have a fix for the taglib issue that does not require changes to
taglib. (taglib 1.11 added a new API for getting images out of
VorbisComments and broke the behavior (not API) of the existing one.)

Still looking at the other issues.

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

Title:
  FTBFS on zesty

Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-11-09 Thread Michi Henning
Taglib 1.11 has broken extraction of VorbisComments.

I've opened a bug here: https://github.com/taglib/taglib/issues/770

Looking at the taglib source now to see whether there is an easy fix.

** Changed in: thumbnailer (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

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

** Changed in: thumbnailer (Ubuntu)
   Importance: High => Critical

** Bug watch added: github.com/taglib/taglib/issues #770
   https://github.com/taglib/taglib/issues/770

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

Title:
  FTBFS on zesty

Status in taglib package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-11-08 Thread Michi Henning
Unfortunately, just suppressing the Qt tests doesn't fix this. It turns
out that, on zesty, the tests for all architectures fail. It looks like
a problem with taglib. Every test that tries to extract artwork from an
ogg video file fails.

There is also a segfault in the thumbnailer test. That failure is either
caused by a problem with max_size_in_bytes(), or by a problem in
gsettings on zesty. Need to follow up.

There are also a bunch of gstreamer critical messages in the test log:

10: (vs-thumb:9542): GStreamer-CRITICAL **: Registering meta implementation 
'GstVideoMeta' without init function
10: thumbnailer-service: [22:50:37.499] "thumbnail: 
/<>/thumbnailer-2.4+17.04.20161108/tests/media/testvideo.ogg 
(256,256): 0.832444 [q: 0.01, d: 0.524390] sec (MISS)"

These are not normal, need to figure out what is going on there.

It doesn't look like this will be a quick fix :-(

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

Title:
  FTBFS on zesty

Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-11-08 Thread Michi Henning
Fix is in a silo: https://bileto.ubuntu.com/#/ticket/2175

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

Title:
  FTBFS on zesty

Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1640326] Re: FTBFS on zesty

2016-11-08 Thread Michi Henning
Thanks for that, will fix now.

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

Title:
  FTBFS on zesty

Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Hello,

  A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in
  the test suite exclusions?

  Could you please take a look and fix? This is blocking boost1.62
  transition.

  The following tests FAILED:
  1 - art_extractor (Failed)
  3 - dbus (Failed)
  9 - qml (Failed)
 10 - libthumbnailer-qt (Failed)
 14 - thumbnailer (SEGFAULT)
 15 - thumbnailer-admin (Failed)
  Errors while running CTest
  Makefile:130: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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


[Touch-packages] [Bug 1638586] Re: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-11-08 Thread Michi Henning
Looks like this is caused by packages installed in /usr/local that
conflict with click.

** Changed in: unity-scopes-api (Ubuntu)
   Status: New => Invalid

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

Title:
  package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in unity-scopes-api package in Ubuntu:
  Invalid

Bug description:
  no se instalo al actualizar version

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  2 03:56:47 2016
  DuplicateSignature:
   package:libunity-scopes1.0:amd64:1.0.7+16.10.20160921-0ubuntu2
   Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package libunity-scopes1.0:amd64 (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-04 (211 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1638586/+subscriptions

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


[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

2016-11-04 Thread Michi Henning
The connectivity status is something that is *not* set by scopes-api.
Instead, the status is received by scopes-api from whoever makes the
query (typically, the shell) and then passed through to the scope. In
turn, the shell just passes on what it gets from QNetworkAccessManager,
I believe.

We had bugs open against QNAM for this and there were some changes made,
but it's still flaky.

At any rate, the connectivity status is unlikely to be useful in
debugging this issue because scopes-api never pays attention to it.

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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


[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

2016-11-03 Thread Michi Henning
Thanks for all the detective work!

I suspect that the MiddlewareException in coincidental and caused by an
earlier timeout. But we shouldn't get stuck like this and things should
recover transparently if the network goes away. I'll have a look and see
what's going on.

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-10-19 Thread Michi Henning
** Changed in: thumbnailer (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1310186] Re: mediascanner prevents unmounting usb device

2016-10-13 Thread Michi Henning
It's difficult to see how to fix this. External devices are scanned
because people quite often use USB sticks or external drives with their
music collections.

I'm not sure whether it is even possible for mediascanner to find out
that some other arbitrary process has asked for a filesystem to be
unmounted. If so, the daemon could back off. If not, I don't know what
else it could/should do.

For what it's worth, placing a file called .nomedia into a directory
prevents scanning of that directory (and all its subdirectories).

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

Title:
  mediascanner prevents unmounting usb device

Status in mediascanner2 package in Ubuntu:
  Confirmed

Bug description:
  Trying to unmount a block device I just mounted, I get the following
  error (sorry for not resetting the locale. It says "Device is busy"):

  :~$ sudo umount /media/tkluck/tjk-backup 
  umount2: Apparaat of hulpbron is bezig
  umount: /media/tkluck/tjk-backup: apparaat is bezig
  (Welke processen het apparaat gebruiken kan mogelijk
   gevonden worden met behulp van lsof(8) of fuser(1).)
  umount2: Apparaat of hulpbron is bezig

  I get the same error in a dialog window when trying to unmount from
  the file manager.

  Using lsof shows that the media-scanner daemon is the culprit:

  tkluck@ultrabook-tjk:~$ lsof /media/tkluck/tjk-backup 
  COMMANDPID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
  mediascan 2898 tkluck   16r   DIR  252,3   2498562 
/media/tkluck/tjk-backup
  mediascan 2898 tkluck   17r   DIR  252,3 4096 50855937 
  mediascan 2898 tkluck   18r   DIR  252,3 4096 39080372 
  mediascan 2898 tkluck   19r   DIR  252,312288 39080513 
  mediascan 2898 tkluck   20r   DIR  252,320480 39080525 
  mediascan 2898 tkluck   21r   DIR  252,3 4096 46792990 
  mediascan 2898 tkluck   22r   DIR  252,3 4096 46792991 
  mediascan 2898 tkluck   23r   DIR  252,316384 46793749 
  mediascan 2898 tkluck   24r   DIR  252,3 4096 47317994 
  mediascan 2898 tkluck   25r   DIR  252,3 4096 47317997 
  mediascan 2898 tkluck   26r   DIR  252,3 4096 47317999 

  Sending it

  sudo kill -9 2898

  solved this for me.

  This is on Ubuntu GNOME 14.04. I uninstalled the mediascanner2.0 to
  solve this "once and for all" (which has no other impact since I do
  not use Unity).

  My guess is that the scan usually finishes quickly after mounting. But
  because this particular drive contains a big filetree, it doesn't,
  resulting in the issue.

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

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


[Touch-packages] [Bug 1445755] Re: Provide a way to hide images from a particular location

2016-09-28 Thread Michi Henning
** Also affects: canonical-scopes-project
   Importance: Undecided
   Status: New

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

Title:
  Provide a way to hide images from a particular location

Status in Canonical System Image:
  In Progress
Status in canonical-scopes-project:
  New
Status in gallery-app package in Ubuntu:
  Fix Released
Status in mediascanner2 package in Ubuntu:
  Invalid

Bug description:
  I've put about 30GB of music in my SD card. Some of the music files
  don't have embedded cover art and their folders contain those cover
  art images.

  When I then opened the Gallery app, I noticed I now have thousands of
  "pictures" imported from the cover art images showing up in my Events
  and Pictures tabs, cluttering the real pictures I've taken with the
  camera.

  Is there a way to tell either mediascanner or the Gallery app to
  ignore a path and not import/show the images there? E.g. similar to
  Android, where you can put a .nomedia file in a folder and its images
  won't show up in the picture viewer.

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

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


[Touch-packages] [Bug 1445755] Re: Provide a way to hide images from a particular location

2016-09-28 Thread Michi Henning
This is fixed in gallery app, but the photo scope also has this problem.
I'm still seeing loads of album covers when I open the photo scope.

Adding photo scope as affected.

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

Title:
  Provide a way to hide images from a particular location

Status in Canonical System Image:
  In Progress
Status in canonical-scopes-project:
  New
Status in gallery-app package in Ubuntu:
  Fix Released
Status in mediascanner2 package in Ubuntu:
  Invalid

Bug description:
  I've put about 30GB of music in my SD card. Some of the music files
  don't have embedded cover art and their folders contain those cover
  art images.

  When I then opened the Gallery app, I noticed I now have thousands of
  "pictures" imported from the cover art images showing up in my Events
  and Pictures tabs, cluttering the real pictures I've taken with the
  camera.

  Is there a way to tell either mediascanner or the Gallery app to
  ignore a path and not import/show the images there? E.g. similar to
  Android, where you can put a .nomedia file in a folder and its images
  won't show up in the picture viewer.

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

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-27 Thread Michi Henning
Looks like 1991 has landed now.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1625930] Re: thumbnailer FTBFS on arm64 ppc64el

2016-09-27 Thread Michi Henning
** Changed in: thumbnailer (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 qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1625930

Title:
  thumbnailer FTBFS on arm64 ppc64el

Status in gcc-6 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in thumbnailer package in Ubuntu:
  Fix Released

Bug description:
  See bug #1613561.

  --
  still ftbfs on arm64 and ppc64el, where it built before:
  https://launchpad.net/ubuntu/+source/thumbnailer/2.4+16.10.20160825-0ubuntu1
  --
  For the record, the so far included post-5.6.1 QDBus patches in our packages:

  https://codereview.qt-project.org/#/c/167480/
  https://codereview.qt-project.org/#/c/170356/

  Thiago is the main contact in upstream.
  --
  We had also problems with telepathy-qt and signon with QDBus, but two patches 
were landed that made QDBus ok with those. However, do note that the QDBus 
rewrite in Qt 5.6 from event loop based to threaded might easily require 
changes in our code, as it did for telepathy-qt:

  
http://launchpadlibrarian.net/280893997/telepathy-qt_0.9.6.1-6ubuntu1_0.9.6.1-7ubuntu2.diff.gz
  
http://launchpadlibrarian.net/284273846/telepathy-qt_0.9.6.1-7ubuntu2_0.9.6.1-9ubuntu6.diff.gz

  Maybe those could give some ideas on what to change in thumbnailer?

  --

  ...although the thumbnailer problems seems a bit different as it's
  limited to two rarer 64-bit architectures instead of happening on all
  of them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/1625930/+subscriptions

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


[Touch-packages] [Bug 1627252] Re: Recognize album artwork with "Album title.supported_extension" filename

2016-09-25 Thread Michi Henning
** Changed in: mediascanner2 (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  Recognize album artwork with "Album title.supported_extension"
  filename

Status in Ubuntu Music App:
  Invalid
Status in mediascanner2 package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  Invalid

Bug description:
  At this time, Music currently supports the following filenames for local 
album artwork (i.e. album artwork which is stored locally in the same folder as 
the music for which it should be associated):
  * cover
  * album
  * albumart
  * .folder
  * folder

  These filenames must have one of the following extensions:
  * jpeg
  * jpg
  * png

  However most applications and programs also support (provided it matches the 
folder name and metadata album title exactly):
  Album Title.supported_extension

  I propose that "Album Title.supported_extension" be added to the list
  of recognized filenames for album artwork, to bring Music into line
  with most other music players...

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

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-25 Thread Michi Henning
Changes are in silo 1991.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-25 Thread Michi Henning
Tests are disabled for on arm64, ppc64, and ppc64le for yakkety and
xenial. That's where we've seen failures, and we don't particularly care
about these arches at the moment.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1627252] Re: Recognize album artwork with "Album title.supported_extension" filename

2016-09-24 Thread Michi Henning
Do you have any examples for music players that recognise
.? (I'm not aware of any at this point.)

The existing list of file names exists because they are widely used by
various players, so we are just following established precedent here. We
can look at supporting this, but I'd prefer to do this only if there are
popular music players that already support this. If not, I don't think
we'd be doing the world a favour by adding yet another file name
convention to the already messy situation.

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

Title:
  Recognize album artwork with "Album title.supported_extension"
  filename

Status in Ubuntu Music App:
  Invalid
Status in mediascanner2 package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  At this time, Music currently supports the following filenames for local 
album artwork (i.e. album artwork which is stored locally in the same folder as 
the music for which it should be associated):
  * cover
  * album
  * albumart
  * .folder
  * folder

  These filenames must have one of the following extensions:
  * jpeg
  * jpg
  * png

  However most applications and programs also support (provided it matches the 
folder name and metadata album title exactly):
  Album Title.supported_extension

  I propose that "Album Title.supported_extension" be added to the list
  of recognized filenames for album artwork, to bring Music into line
  with most other music players...

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

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


[Touch-packages] [Bug 1627252] Re: Recognize album artwork with "Album title.supported_extension" filename

2016-09-24 Thread Michi Henning
** Also affects: mediascanner2 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Recognize album artwork with "Album title.supported_extension"
  filename

Status in Ubuntu Music App:
  Invalid
Status in mediascanner2 package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  At this time, Music currently supports the following filenames for local 
album artwork (i.e. album artwork which is stored locally in the same folder as 
the music for which it should be associated):
  * cover
  * album
  * albumart
  * .folder
  * folder

  These filenames must have one of the following extensions:
  * jpeg
  * jpg
  * png

  However most applications and programs also support (provided it matches the 
folder name and metadata album title exactly):
  Album Title.supported_extension

  I propose that "Album Title.supported_extension" be added to the list
  of recognized filenames for album artwork, to bring Music into line
  with most other music players...

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

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


[Touch-packages] [Bug 1626767] Re: Tests should be re-enabled / fixed

2016-09-23 Thread Michi Henning
I don't think what we are seeing in thumbnailer is the same thing. Your
issue and the telepathy one is related to shutdown. Ours strike all over
the place. But there are definitely problems with Qt 5.6, whatever the
details.

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

Title:
  Tests should be re-enabled / fixed

Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  https://code.launchpad.net/~charlesk/indicator-network/flight-mode-
  handle-missing-urfkill disables all tests because of multiple (eleven,
  by my count) separate failing tests.

  Nearly all the failures occurred on Yakkety + arm64 or ppc64el, so
  it's possible that this is some issue in Yakkety and the test fails
  will resolve themselves when the distro is fixed. Or maybe these
  really are lots of real bugs that need to be addressed.

  What I'm sure of, though: they're *not* all related to this three-line
  change that needs to land. So I'm making this separate ticket to track
  it separately.

  Sample list of test failures:

  WpaPsk/TestSecretAgentGetSecrets.ProvidesPasswordForWpaPsk/0
  
https://launchpadlibrarian.net/286072925/buildlog_ubuntu-xenial-armhf.indicator-network_0.8.0+16.04.20160922.5-0ubuntu1_BUILDING.txt.gz

  TestIndicator.UnlockSIM2_IncorrectPin
  
https://launchpadlibrarian.net/286052502/buildlog_ubuntu-yakkety-i386.indicator-network_0.8.0+16.10.20160922.3-0ubuntu1_BUILDING.txt.gz

  TestIndicator.OneDisconnectedAccessPointAtStartup
  
https://launchpadlibrarian.net/286051922/buildlog_ubuntu-yakkety-amd64.indicator-network_0.8.0+16.10.20160922.3-0ubuntu1_BUILDING.txt.gz

  TestIndicator.UnlockSIM_CancelFirstUnlockSecond
  
https://launchpadlibrarian.net/286065695/buildlog_ubuntu-vivid-ppc64el.indicator-network_0.8.0+15.04.20160922.4-0ubuntu1_BUILDING.txt.gz

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

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-23 Thread Michi Henning
Hmmm... The xenial failure is highly suspicious because that particular
test has never failed before. I'm quite confident that the failure
exists on xenial too, just doesn't manifest as often.

I did look at the telepathy code changes, and they address a completely
different issue. What we are seeing is different, I believe.

If you consider what's proposed now unacceptable, what should we do? We
can disable for yakkety only, or for yakkety arm64 and ppc64el only, or
whatever. Please let me know, so we can get this unblocked.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1607531] Re: Music ignores local album artwork.

2016-09-23 Thread Michi Henning
You cannot drop an arbitrary jpg file into a music folder and expect it
to be picked up as artwork. This simply doesn't work. The following file
basenames are recognised cover art:

cover
album
albumart
.folder
folder

These base names must have one of the following extensions:

jpeg
jpg
png

Capitalisation is irrelevant. So, if you have a file called

AlbumArt.JPG

it will be used as the album cover.

If a song contains embedded artwork, it will be used. Otherwise, if one
of these files is present, the contents of the file are used. Otherwise,
we try to retrieve albumart from a database. The accuracy of the lookup
depends on the accuracy of the tags in the song and whether the database
(7digital) has a corresponding entry.

At any rate, there is no bug here. You can embed cover art in your
songs, or use one of the filenames listed above if you don't want to do
that.

** Changed in: thumbnailer (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Music ignores local album artwork.

Status in Ubuntu Music App:
  Invalid
Status in thumbnailer package in Ubuntu:
  Invalid

Bug description:
  When using "Music", local album artwork is ignored, seemingly in favor
  of online album artwork, which is frequently incorrect.

  This appears to be a different issue to
  https://bugs.launchpad.net/thumbnailer/+bug/1372000 , because
  https://bugs.launchpad.net/thumbnailer/+bug/1372000 is apparently
  "fixed" and I still experience this issue.

  --

  Reproduce:
  - Copy music to your Ubuntu mobile device, ensuring that each folder contains 
appropriately-named album artwork (in my case, exactly the same name as the 
album and the folder in which the music is contained).
  - Launch/open Music, browse your library and playback music.

  Result:
  - Most tracks are shown with no or incorrect album artwork.

  Expectation:
  - That Music would utilize or otherwise prioritize local album artwork.

  --

  Music: 2.4.1003

  bq Aquaris E5 HD Ubuntu Edition:
  * OS build number: OTA-12
  * Ubuntu Image part: 20160708
  * Ubuntu build description: Ubuntu 15.04 - armhf (20160708-091336)
  * Device Image part: 20160606-540a47f
  * Device build description: VEGETA01A-S23A_BQ_L100EN_2014_160708
  * Customization Image part: 20160701-981-38-14

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

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


[Touch-packages] [Bug 1607531] Re: Music ignores local album artwork.

2016-09-22 Thread Michi Henning
Gregory, can you please attach an example of what you think are the
failing files?

We need a directory that shows the problem. It should contain at least
one music track for which you see incorrect online artwork or no
artwork, plus whatever files you think should be used to display the
artwork you want.

We need these files *exactly* as they are in your Music folder, with the
exact same file names and contents please.

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

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

Title:
  Music ignores local album artwork.

Status in Ubuntu Music App:
  Invalid
Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  When using "Music", local album artwork is ignored, seemingly in favor
  of online album artwork, which is frequently incorrect.

  This appears to be a different issue to
  https://bugs.launchpad.net/thumbnailer/+bug/1372000 , because
  https://bugs.launchpad.net/thumbnailer/+bug/1372000 is apparently
  "fixed" and I still experience this issue.

  --

  Reproduce:
  - Copy music to your Ubuntu mobile device, ensuring that each folder contains 
appropriately-named album artwork (in my case, exactly the same name as the 
album and the folder in which the music is contained).
  - Launch/open Music, browse your library and playback music.

  Result:
  - Most tracks are shown with no or incorrect album artwork.

  Expectation:
  - That Music would utilize or otherwise prioritize local album artwork.

  --

  Music: 2.4.1003

  bq Aquaris E5 HD Ubuntu Edition:
  * OS build number: OTA-12
  * Ubuntu Image part: 20160708
  * Ubuntu build description: Ubuntu 15.04 - armhf (20160708-091336)
  * Device Image part: 20160606-540a47f
  * Device build description: VEGETA01A-S23A_BQ_L100EN_2014_160708
  * Customization Image part: 20160701-981-38-14

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

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


[Touch-packages] [Bug 1528058] Re: settings not readable from confined app/scope

2016-09-22 Thread Michi Henning
** Changed in: thumbnailer (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 thumbnailer in Ubuntu.
https://bugs.launchpad.net/bugs/1528058

Title:
  settings not readable from confined app/scope

Status in Canonical System Image:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Fix Released

Bug description:
  The trace-client gsetting does not work and always returns false when
  running under confinement. We need a different way to enable this.

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

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


[Touch-packages] [Bug 1625930] Re: thumbnailer FTBFS on arm64 ppc64el

2016-09-22 Thread Michi Henning
After discussions with mterry and alecu, we decided to disable the
failing tests on xenial and yakkety. The linked branch does this.

I've opened a separate bug to make sure we don't forget to turn those
tests back on:

https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1626815

** Branch linked: lp:~michihenning/thumbnailer/disable-tests

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

Title:
  thumbnailer FTBFS on arm64 ppc64el

Status in gcc-6 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  In Progress

Bug description:
  See bug #1613561.

  --
  still ftbfs on arm64 and ppc64el, where it built before:
  https://launchpad.net/ubuntu/+source/thumbnailer/2.4+16.10.20160825-0ubuntu1
  --
  For the record, the so far included post-5.6.1 QDBus patches in our packages:

  https://codereview.qt-project.org/#/c/167480/
  https://codereview.qt-project.org/#/c/170356/

  Thiago is the main contact in upstream.
  --
  We had also problems with telepathy-qt and signon with QDBus, but two patches 
were landed that made QDBus ok with those. However, do note that the QDBus 
rewrite in Qt 5.6 from event loop based to threaded might easily require 
changes in our code, as it did for telepathy-qt:

  
http://launchpadlibrarian.net/280893997/telepathy-qt_0.9.6.1-6ubuntu1_0.9.6.1-7ubuntu2.diff.gz
  
http://launchpadlibrarian.net/284273846/telepathy-qt_0.9.6.1-7ubuntu2_0.9.6.1-9ubuntu6.diff.gz

  Maybe those could give some ideas on what to change in thumbnailer?

  --

  ...although the thumbnailer problems seems a bit different as it's
  limited to two rarer 64-bit architectures instead of happening on all
  of them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/1625930/+subscriptions

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


[Touch-packages] [Bug 1626815] [NEW] Re-enable DBus tests once Qt 5.6 issue is resolved

2016-09-22 Thread Michi Henning
Public bug reported:

See https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-
src/+bug/1625930

We need to track this problem and re-enable the tests ASAP.

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

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

Title:
  Re-enable DBus tests once Qt 5.6 issue is resolved

Status in thumbnailer package in Ubuntu:
  New

Bug description:
  See https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-
  src/+bug/1625930

  We need to track this problem and re-enable the tests ASAP.

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

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


[Touch-packages] [Bug 1625930] Re: thumbnailer FTBFS on arm64 ppc64el

2016-09-22 Thread Michi Henning
** Changed in: thumbnailer (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

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

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

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

Title:
  thumbnailer FTBFS on arm64 ppc64el

Status in gcc-6 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  In Progress

Bug description:
  See bug #1613561.

  --
  still ftbfs on arm64 and ppc64el, where it built before:
  https://launchpad.net/ubuntu/+source/thumbnailer/2.4+16.10.20160825-0ubuntu1
  --
  For the record, the so far included post-5.6.1 QDBus patches in our packages:

  https://codereview.qt-project.org/#/c/167480/
  https://codereview.qt-project.org/#/c/170356/

  Thiago is the main contact in upstream.
  --
  We had also problems with telepathy-qt and signon with QDBus, but two patches 
were landed that made QDBus ok with those. However, do note that the QDBus 
rewrite in Qt 5.6 from event loop based to threaded might easily require 
changes in our code, as it did for telepathy-qt:

  
http://launchpadlibrarian.net/280893997/telepathy-qt_0.9.6.1-6ubuntu1_0.9.6.1-7ubuntu2.diff.gz
  
http://launchpadlibrarian.net/284273846/telepathy-qt_0.9.6.1-7ubuntu2_0.9.6.1-9ubuntu6.diff.gz

  Maybe those could give some ideas on what to change in thumbnailer?

  --

  ...although the thumbnailer problems seems a bit different as it's
  limited to two rarer 64-bit architectures instead of happening on all
  of them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/1625930/+subscriptions

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-22 Thread Michi Henning
The failure happens in both yakkity and xenial (because both use Qt
5.6). The failure moves around. In the latest build, we got a failure on
xenial ppc64el (which is a first).

If we disable tests, we have to disable *all* integration tests that use
DBus for *both* xenial and yakkety. We haven't seen a failure on vivid
so far, and I don't expect that we will, seeing that vivid uses an
earlier version of Qt.

I'm uncomfortable about turning off tests wholesale like this though. In
particular, we have a lurking time bomb here. Absolutely anything that
uses QDBus with Qt 5.6 can blow up without warning. I'm fairly sure that
this is a race condition that shows up mainly because the timings when
we run on the build machines are different. So, we may end up with tons
of seemingly random failures in the field for anything that uses QDBus,
just because a machine is more heavily loaded than usual. Random
segfaults are very hard to debug if they are not reproducible :-(

Is there any chance of backing out of the Qt 5.6 upgrade? It doesn't
look like that version is ready for prime time yet.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-22 Thread Michi Henning
I decided to kick the build in silo 1968 to see whether the fault would
move. This time, it failed on yakkety on arm64 and ppc64el as before,
but also failed on xenial powerpc. The failure on xenial is in a test
that uses QDBus to talk between client and server. The client fails
because it doesn't any responses from DBus, suggesting that the server
crashed.

Kicking off another build now. It sure looks more and more like a race
in QDbus.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-22 Thread Michi Henning
I install a yakkety arm64 chroot on my M10 and built the thumbnailer.
The tests run fine, over and over. I do not see any failures.

dpkg reports:

libc6:arm64  2.24-0ubuntu1
arm64
gcc-66.2.0-3ubuntu15  
arm64
libqt5dbus5:arm645.6.1+dfsg-3ubuntu5~1
arm64

Is it possible that there is a problem with the builder we are running
this on?

I'm fresh out of ideas what else I could check locally.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-22 Thread Michi Henning
Another option: it could simply a race that shows up in the train only
because the builders are VMs (I believe) and the underlying hardware
might be loaded more heavily. I'd expect CPU and I/O timings to be
different in the train than on my M10. So, it is still possible that
this is simply a race QDBus that gets tickled only when we run the tests
in the train.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-21 Thread Michi Henning
Silo 1968 contains a no-change rebuild of the thumbnailer. As expected,
things are again blowing up for arm64 and ppc64el on yakkety.

Interestingly, things worked with xenial, even though the same QDBus is
installed there, as far as I can see.

I don't think the telepathy code changes you linked to are related to
what we are seeing. I'll double-check tomorrow.

I'm asking the trainguards to copy the packages from 1960 into 1968, so
we can check if the upstream patches affect what we are seeing.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-20 Thread Michi Henning
So, as best as we can tell, this is caused by an upgrade to Qt.
Specifically, anything that uses QDBus is falling over. We are seeing
similar problems with unity-scope-click here:

https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-
src/+bug/1618590

Basically, the code works with Qt 5.5, and doesn't with Qt 5.6. The ftbs
for thumbnailer here

https://launchpad.net/ubuntu/+source/thumbnailer/2.4+16.10.20160825-0ubuntu1

shows that the tests failed only on yakkety arm64 and ppc64el. That's
because that silo was built before Qt 5.6 was added to the Xenial
overlay. If I were to build in a silo now, I expect I'd see the same
failures on both xenial and yakkety.

Not sure what we can do to help here. The problem isn't in the
thumbnailer code, but somewhere in QDBus, by the looks of things.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-15 Thread Michi Henning
The tests that are failing are all Qt related. I suspect a problem in Qt
rather than our code. (The thumbnailer code hasn't changed in ages, and
the fact that it fails only on Yakkity suggest a problem with one of our
dependencies.)

8: thumbnailer-service: [23:19:59.671] failure cache:   0 entries, 0 bytes, hit 
rate 0.00 (0/0), avg hit run 0.00, avg miss run 0.00
8: Segmentation fault (core dumped)
8: 
8:  Xvfb log file 
8: _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be 
created.
 8/26 Test  #8: image-provider ..***Timeout 1500.00 
sec

Might indicate some X11 related issue? I we don't normally see this.

Similar trace here:

9: * Start testing of Thumbnailer *
9: Config: Using QtTest library 5.6.1, Qt 5.6.1 (arm64-little_endian-lp64 
shared (dynamic) release build; by GCC 6.2.0 20160830)
9: PASS   : Thumbnailer::OnlineArt::initTestCase()
9: Segmentation fault (core dumped)
9: 
9:  Xvfb log file 
9: _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
 9/26 Test  #9: qml .***Timeout 1500.00 
sec

The following looks like it simply got stuck and ended up being killed
eventually. No trace at all:

10: thumbnailer-service: [00:09:59.863] failure cache:   0 entries, 0 bytes, 
hit rate 0.00 (0/0), avg hit run 0.00, avg miss run 0.00
10/26 Test #10: libthumbnailer-qt ...***Timeout 1500.00 
sec
[==] Running 20 tests from 1 test case.

I very much doubt that the problem is in our code. I have no idea how to
do track this down. I don't have an arm64 or ppc machine. Last time I
tried to use one of the porter boxes, it wasn't possible to install the
overlay on them, so that looks like a no-go as well :-(

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1548718] Re: Need to update micro version in shlibs file when symbols are added

2016-09-14 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Need to update micro version in shlibs file when symbols are added

Status in unity-scopes-api package in Ubuntu:
  Fix Committed

Bug description:
  Currently, we are writing only major.minor into the shlibs file. But,
  if we add a new symbol to the public API and only increment the micro
  version, we really need to write the micro version as well.

  Unfortunately, that's a manual process, so we need to remember. With
  the next version of abigail, it might be possible to spit out some
  big-time warning or some such when new symbols are added to the public
  API. At least that would help to remind us.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1548718/+subscriptions

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-09 Thread Michi Henning
I didn't even know that there was a failed build. Looking at the build
log, the test failures are almost certainly caused by a flaky builder.
We have seen this sort of thing recently on another project too.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1621950] Re: Cpu load 99-100% of Smartscope

2016-09-09 Thread Michi Henning
There is no direct evidence in the log to indicate something spinning.
But it shows that dash.ubuntu.com wasn't responding for much of the
time, as evidenced by the periodic retries. We should check that the
code doesn't do something silly when that happens.

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

Title:
  Cpu load 99-100% of Smartscope

Status in Canonical System Image:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Smartscope always in top (cpu load 99-100%)

  Meizu MX4 OTA-12 stable

  top - 22:39:36 up 1 day,  4:15,  1 user,  load average: 0.00, 0.01, 0.05
  Tasks: 321 total,  13 running, 308 sleeping,   0 stopped,   0 zombie
  %Cpu0  :  2.9 us,  4.9 sy,  0.0 ni, 92.2 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 
st
  %Cpu4  : 35.2 us, 64.8 sy,  0.0 ni,  0.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 
st
  KiB Mem:   1937784 total,  1176564 used,   761220 free,19248 buffers
  KiB Swap:   524284 total,0 used,   524284 free.   187348 cached Mem
  21308 phablet   20   0  380652   7304   5648 S  99.1  0.4   1:09.39 
smartscope+
  21324 root  20   06288   1300816 R   3.8  0.1   0:10.33 top   
  
   1754 root  20   0  853780  13060   9284 S   1.0  0.7   6:19.79 
unity-syst+ 
  19931 root  10 -10   0  0  0 S   1.0  0.0   0:00.45 rx_thread 
  
  21244 root  20   0   0  0  0 S   1.0  0.0   0:02.50 
kworker/0:2 
  1 root  20   03948   2428   1080 S   0.0  0.1   0:26.57 init  
  
  2 root  20   0   0  0  0 S   0.0  0.0   0:00.04 kthreadd  
  
  3 root  20   0   0  0  0 S   0.0  0.0   0:04.13 
ksoftirqd/0 
  5 root   0 -20   0  0  0 S   0.0  0.0   0:00.00 
kworker/0:+ 
  7 root -99   0   0  0  0 S   0.0  0.0   0:01.86 
migration/0 
  8 root  20   0   0  0  0 S   0.0  0.0   0:19.10 
rcu_preempt 
  9 root  20   0   0  0  0 S   0.0  0.0   0:00.00 rcu_bh
  
 10 root  20   0   0  0  0 S   0.0  0.0   0:00.32 rcu_sched 
  
 11 root -99   0   0  0  0 R   0.0  0.0   0:01.63 
migration/1 
 12 root  20   0   0  0  0 R   0.0  0.0   0:00.82 
ksoftirqd/1 
 14 root   0 -20   0  0  0 S   0.0  0.0   0:00.04 
kworker/1:+

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

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-09 Thread Michi Henning
Well, it's not ftbfs anymore. More pertinently, should I publish now or
wait until after OTA-13?

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1367551] Re: [MIR] capnproto

2016-09-09 Thread Michi Henning
That was fixed quite some time ago, so it should no longer be a problem.
(We are at 0.5.3 now; that's in yakkety, not sure about Vivid and
Xenial.) I never managed to reproduce the problem on arm.

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

Title:
  [MIR] capnproto

Status in capnproto package in Ubuntu:
  Incomplete

Bug description:
  Can we please include this in main? unity-scopes-api has a dependency
  on capnproto.

  Source and bug tracking for this are here:
  https://github.com/kentonv/capnproto

  There are no dependencies other than C++ 11 (gcc 4.7 or later work).

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

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


[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-09 Thread Michi Henning
Silo 54 is approved for QA. I was told not to publish this until after
OTA-13. If this needs to go in now, someone let me know please, and I'll
publish it.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1367551] Re: [MIR] capnproto

2016-09-09 Thread Michi Henning
Lukasz and Pawel have been been working on getting the MIR for this
happening. I'm out of that loop though, so I don't know the details.

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

Title:
  [MIR] capnproto

Status in capnproto package in Ubuntu:
  Incomplete

Bug description:
  Can we please include this in main? unity-scopes-api has a dependency
  on capnproto.

  Source and bug tracking for this are here:
  https://github.com/kentonv/capnproto

  There are no dependencies other than C++ 11 (gcc 4.7 or later work).

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

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


[Touch-packages] [Bug 1621002] Re: Mediascanner2 test failure on yakkety/{armhf, arm64, ppc64el} with latest dbus-cpp

2016-09-09 Thread Michi Henning
+1!

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

Title:
  Mediascanner2 test failure on yakkety/{armhf,arm64,ppc64el} with
  latest dbus-cpp

Status in dbus-cpp package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  New

Bug description:
  When trying to build a new mediascanner2 release, tests failed on a
  number of architectures when building under Yakkety.  Some relevant
  logs:

  
https://launchpadlibrarian.net/281862518/buildlog_ubuntu-yakkety-armhf.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/282074929/buildlog_ubuntu-yakkety-arm64.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/281862178/buildlog_ubuntu-yakkety-ppc64el.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz

  The failure is occurring in code not touched by the changes in the
  silo, and I suspect that this is related to dbus-cpp or possibly GCC
  6.

  The segfault doesn't occur on x86, but I was able to reproduce it on
  my Chromebook.  Attached is a stacktrace from the test_dbus test
  program.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1621002/+subscriptions

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


[Touch-packages] [Bug 1612461] Re: [MIR] unity-scopes-api

2016-09-09 Thread Michi Henning
** Branch linked: lp:~michihenning/unity-scopes-api/shlib-fix

** Changed in: unity-scopes-api (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  [MIR] unity-scopes-api

Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues

  [Quality assurance]
   * This package has unit tests

  [Dependencies]
   * 

  [Standards compliance]
   * This package uses cmake and is properly translated

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1612461/+subscriptions

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


[Touch-packages] [Bug 1548718] Re: Need to update micro version in shlibs file when symbols are added

2016-09-09 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu)
   Status: New => In Progress

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

Title:
  Need to update micro version in shlibs file when symbols are added

Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  Currently, we are writing only major.minor into the shlibs file. But,
  if we add a new symbol to the public API and only increment the micro
  version, we really need to write the micro version as well.

  Unfortunately, that's a manual process, so we need to remember. With
  the next version of abigail, it might be possible to spit out some
  big-time warning or some such when new symbols are added to the public
  API. At least that would help to remind us.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1548718/+subscriptions

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


[Touch-packages] [Bug 1612461] Re: [MIR] unity-scopes-api

2016-09-07 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

** Changed in: unity-scopes-api (Ubuntu)
   Importance: Undecided => High

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

Title:
  [MIR] unity-scopes-api

Status in unity-scopes-api package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues

  [Quality assurance]
   * This package has unit tests

  [Dependencies]
   * 

  [Standards compliance]
   * This package uses cmake and is properly translated

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1612461/+subscriptions

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


[Touch-packages] [Bug 1621002] Re: Mediascanner2 test failure on yakkety/{armhf, arm64, ppc64el} with latest dbus-cpp

2016-09-07 Thread Michi Henning
Good catch!

I've seen this in the past due to uninitialised variables. With
optimisation, the compiler gets more aggressive about register re-use,
so a bug can manifest under optimisation when the uninitialised variable
ends up in a register that had a previous value in it. (In debug mode,
the variable often picks up a zero value instead.)

Not sure if there is an easy way to track down whether this is the case
or if this is a genuine code generation problem.

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

Title:
  Mediascanner2 test failure on yakkety/{armhf,arm64,ppc64el} with
  latest dbus-cpp

Status in dbus-cpp package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  New

Bug description:
  When trying to build a new mediascanner2 release, tests failed on a
  number of architectures when building under Yakkety.  Some relevant
  logs:

  
https://launchpadlibrarian.net/281862518/buildlog_ubuntu-yakkety-armhf.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/282074929/buildlog_ubuntu-yakkety-arm64.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/281862178/buildlog_ubuntu-yakkety-ppc64el.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz

  The failure is occurring in code not touched by the changes in the
  silo, and I suspect that this is related to dbus-cpp or possibly GCC
  6.

  The segfault doesn't occur on x86, but I was able to reproduce it on
  my Chromebook.  Attached is a stacktrace from the test_dbus test
  program.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1621002/+subscriptions

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


[Touch-packages] [Bug 1615614] Re: dash is empty, scopes are missing

2016-08-25 Thread Michi Henning
If this is with boost 1.61, either the problem is still present in boost
or, if the local files were messed up somehow, the exception would
legitimately be raised because the locale definition is broken.

Comment #9 seems to indicate that the problem was fixed after
regenerating the locale. In that case, the exception is perfectly
legitimate, and there is no bug at all. If the locale info is broken, we
can't parse essential configuration files in scopes-api, which prevents
the runtime from being started. In that case, all scopes are
inaccessible, period.

If the problem indeed went away after regenerating the local info, there
is no bug here. In that case, can you close as invalid please?

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

Title:
  dash is empty, scopes are missing

Status in boost package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.10
  dash is empty, scopes are missing

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

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


[Touch-packages] [Bug 1615614] Re: dash is empty, scopes are missing

2016-08-24 Thread Michi Henning
The problem is caused by boost, and we are defenseless until we get 1.57
or later into the image. There is an earlier bug about this here:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1303637

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

Title:
  dash is empty, scopes are missing

Status in boost package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.10
  dash is empty, scopes are missing

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

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


[Touch-packages] [Bug 1445755] Re: Provide a way to hide images from a particular location

2016-08-23 Thread Michi Henning
This happens if someone inserts a flash card or copies a collection from
some other music library, such as iTunes. For songs that don't have
embedded artwork, various music players store the artwork in a file
inside an album's folder. iTunes uses AlbumArtSmall.jpg and Folder.jpg.
Other players use cover.ext, album.ext, album art.ext, .folder.ext, or
folder.ext (where ext could be png, jpg, or jpeg).

It seems that gallery app shows these files as if they were photos taken
with the camera app.

For a test case, drop an image called AlbumArtSmall.jpg or cover.jpg
into a music album folder somewhere. I believe you'll find that image in
the gallery app then.

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

Title:
  Provide a way to hide images from a particular location

Status in Canonical System Image:
  New
Status in gallery-app package in Ubuntu:
  Confirmed
Status in mediascanner2 package in Ubuntu:
  Confirmed

Bug description:
  I've put about 30GB of music in my SD card. Some of the music files
  don't have embedded cover art and their folders contain those cover
  art images.

  When I then opened the Gallery app, I noticed I now have thousands of
  "pictures" imported from the cover art images showing up in my Events
  and Pictures tabs, cluttering the real pictures I've taken with the
  camera.

  Is there a way to tell either mediascanner or the Gallery app to
  ignore a path and not import/show the images there? E.g. similar to
  Android, where you can put a .nomedia file in a folder and its images
  won't show up in the picture viewer.

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

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


[Touch-packages] [Bug 1445755] Re: Provide a way to hide images from a particular location

2016-08-23 Thread Michi Henning
> Mediascanner is driving the local photos scope though, and these
pieces of folder cover art will likely show up there.

Indeed, they do, which is annoying. For me, it picks up images from
AlbumArtSmall.jpg and Folder.jpg. (These names are used by iTunes.)

Would be good to ignore those.

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

Title:
  Provide a way to hide images from a particular location

Status in Canonical System Image:
  New
Status in gallery-app package in Ubuntu:
  Confirmed
Status in mediascanner2 package in Ubuntu:
  Confirmed

Bug description:
  I've put about 30GB of music in my SD card. Some of the music files
  don't have embedded cover art and their folders contain those cover
  art images.

  When I then opened the Gallery app, I noticed I now have thousands of
  "pictures" imported from the cover art images showing up in my Events
  and Pictures tabs, cluttering the real pictures I've taken with the
  camera.

  Is there a way to tell either mediascanner or the Gallery app to
  ignore a path and not import/show the images there? E.g. similar to
  Android, where you can put a .nomedia file in a folder and its images
  won't show up in the picture viewer.

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

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


  1   2   3   4   5   6   7   8   9   10   >