Thanks for the heads-up! log4cxx is not in main, and I've never used it. The question is whether we should risk trying this out, or just run with something really simple based on what Rodney knocked up some time ago. I'm just trying to minimise risk here. There are zero function point in this exercise for us :-(
-- 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: In Progress 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 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
