← Back to team overview

touch-packages team mailing list archive

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

 

I tried switching to the new libunity-scopes3 from the PPA but Today
scope would not load anymore its contents after a reboot. Reverting back
to the original one fixed the problem.

Note that this is my main phone and I don't want to modify the filesystem in any abnormal way. Therefore my method is:
- Check which packages from a PPA are actually installed - in this case, libunity-scopes3 only
- Unpack both the old and new .deb and do diff:s of them - files scoperegistry, smartscopesproxy, scoperunner, libunity-scopes.so.1.0.2, version in their respective directories were changed
- Do old and new tarballs of changed contents
- Remount / as rw only for the moment of unpacking either the new or old tarball
- Remount / as ro again

It took me 3 days of normal use after OTA-8 upgrade (with Telegram in
Today scope enabled right after upgrade) before I hit this, so it's not
that easy to reproduce.

-- 
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:
  Triaged
Status in libqtelegram package in Ubuntu:
  Invalid
Status in unity-scope-mediascanner package in Ubuntu:
  Invalid
Status in unity-scopes-api package in Ubuntu:
  In Progress

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


References