touch-packages team mailing list archive

[Michał Karnicki <michal.karnicki@xxxxxxxxxxxxx>]

I believe I may have found the source of the problem. When the scope is aggregated, the author assumed they can access results[0], which may not be true if:
1) the user is signed in
2) but has no messages whatsoever

That'd mean the scope would crash for all users, who have set up
Telegram account, but not really used it.

Michi, if you have time, perhaps you could verify my finding. In the
mean time, I'm rewriting the scope source as the backing database schema
has changed (after we moved to making use of TelegramQML plugin).

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

-- 
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:
  /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in
  `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': corrupted
  double-linked list: ADDR ***

Status in Canonical System Image:
  Confirmed
Status in libqtelegram package in Ubuntu:
  Triaged
Status in unity-scope-mediascanner package in Ubuntu:
  Invalid
Status in unity-scopes-api package in Ubuntu:
  Confirmed

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.

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