** Description changed:
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
** Changed in: canonical-devices-system-image
Assignee: Alejandro J. Cura (alecu) => Yuan-Chen Cheng (ycheng-twn)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-mediascanner
in Ubuntu.
As I suggested previously, this is memory corruption. The "corrupted
double-linked list" message shows up whenever glibc detects memory
corruption. The fact that this always shows up with the telegram scope
is a strong suggestion that the problem is caused by the telegram scope.
(We regularly run
And another one from today while switching between scopes:
https://errors.ubuntu.com/oops/6fc6ca80-78ce-11e5-b660-fa163e707a72
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-mediascanner
in Ubuntu.
** Changed in: canonical-devices-system-image
Milestone: ww40-2015 => ww46-2015
--
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:
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
I definitely did have
https://errors.ubuntu.com/oops/0bb39a78-1c08-11e5-9c34-fa163e78b027 when
I already had Telegram discussions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-mediascanner
in Ubuntu.
Some more recent that may be related (but are incomplete as reports):
https://errors.ubuntu.com/oops/72595200-5186-11e5-a598-fa163e5bb1a2
https://errors.ubuntu.com/oops/73424db6-5186-11e5-8e22-fa163e22e467
And a more recent full report:
** Changed in: canonical-devices-system-image
Milestone: ww34-2015 = ww40-2015
--
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:
** Changed in: libqtelegram (Ubuntu)
Assignee: (unassigned) = Michał Karnicki (karni)
--
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:
The stack trace indicates that the crash happens after main() completes, when
global objects are destroy via at_exit().
The crash happens inside the destructor for boost::log::core. (Boost log uses a
global singleton instance.) However, I suspect that this is co-incidental. Most
likely, memory
This is reported to happen at boot and a symptom is that the today scope is not
initialized with the current date
These reports coincide with the release of ota4
** Changed in: unity-scope-mediascanner (Ubuntu)
Importance: Medium = High
** Changed in: unity-scope-mediascanner (Ubuntu)
dobey found that some of those crashes are coming from other scopes too
(dashboard, video aggregator).
I'm moving the bug to scopes-api
** Also affects: unity-scopes-api (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity-scopes-api (Ubuntu)
Importance: Undecided =
Most of the errors are for the telegram scope, but here are a few that
dobey found:
14:38:35 dobey
https://errors.ubuntu.com/oops/d7fb3514-31ed-11e5-9eb1-fa163e525ba7 - this one
is dashboard
14:39:00 dobey
https://errors.ubuntu.com/oops/36ab2c3c-3229-11e5-a54e-fa163e373683 is
videoaggregator
Looking at the error tracker, all examples of the crash seem to come
from the telegram scope. I'm reassigning there.
** Changed in: unity-scope-mediascanner (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: unity-scope-mediascanner (Ubuntu)
Importance: Undecided = Medium
--
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:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity-scope-mediascanner (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-mediascanner
17 matches
Mail list logo
