** 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
This continues to happen, tens of reports each day, so it'd be useful to
keep the bug open somehow regardless if we know where the actual problem
lies or not.
** Changed in: unity-scopes-api (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: unity-scopes-api (Ubuntu RTM)
** Changed in: canonical-devices-system-image
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-scope-mediascanner
in Ubuntu.
https://bugs.launchpad.net/bugs/1472755
Title:
** 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-scope-mediascanner
in Ubuntu.
https://bugs.launchpad.net/bugs/1472755
Title:
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
** Changed in: canonical-devices-system-image
Assignee: Michi Henning (michihenning) => Alejandro J. Cura (alecu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** 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-scope-mediascanner
in Ubuntu.
https://bugs.launchpad.net/bugs/1472755
Title:
** Branch linked: lp:~michihenning/unity-scopes-api/ditch-boost-log
--
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
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
log4cxx is what I've used before, works just like the extremely popular
log4j, and is used by a wide variety of projects, not suffering from
stupid initialisation issues like google logging.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Yes, I saw. It's caused by a global singleton object in boost::log. The
crash happens due to ordering issues with global destructors. The only
known fix would be to hold a boost::log instance in scope for the
duration of main(). However, that's not possible because we have custom
scope runners for
Still happened on OTA-9, although only once for me so far according to
error logs (Feb 1th) even though I've kept Telegram enabled in the Today
scope for the whole time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: canonical-devices-system-image
Milestone: ww02-2016 => ww08-2016
--
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 am reopening this report. It happened again today with:
current build number: 210
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
https://errors.ubuntu.com/oops/540179b8-b3ba-11e5-b371-fa163e4aaad4
** Changed in: canonical-devices-system-image
Status: Fix Committed => In
This bug was fixed in the package unity-scopes-api -
1.0.2+16.04.20151218.2-0ubuntu1
---
unity-scopes-api (1.0.2+16.04.20151218.2-0ubuntu1) xenial; urgency=medium
[ Michi Henning ]
* Changed version number generation to use a common script. Removed
symbols files because we
unity-scopes-api (1.0.2+15.04.20151218.2-0ubuntu1) vivid; urgency=medium
[ Michi Henning ]
* Changed version number generation to use a common script. Removed
symbols files because we are now using abi-compliance-checker.
* Replaced global dummy loggers for testing with heap-allocated
** Changed in: canonical-devices-system-image
Status: Triaged => In Progress
--
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:
Timo, thanks for trying!
I normally just do a citrain device-upgrade to install a PPA, and the
right magic happens automatically.
I haven't tried with this particular PPA on my Nexus. I can try
tomorrow, but don't expect anything unusual.
--
You received this bug notification because you are a
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
My /var/crash is still empty, although I can't say I've done much
testing beyond browsing the scopes and refreshing them now and then.
(The bug was hard to reproduce for me earlier in general.) I'll repeat
my request for other folks on Telegram feedback group to give this a try
if they can.
--
Michi, this needs no explanation, I completely agree with every sentence
you said. Same goal, just trying to get more data :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-mediascanner
in Ubuntu.
Hi Michał, thanks for trying.
Unfortunately, it's a partially decidable problem. If you don't see the bug,
that doesn't mean that the bug is fixed :-(
All we can be sure of is that, if you still do see the bug, it isn't fixed…
I have good reason to believe that the code in the PPA gets rid of
Hi Michi. I myself have seen it rarely, but I've asked Timo and in the
folks in Telegram Feedback group to give this a try, as Timo seemed he
was able to reproduce this quite easily. I'll install it too, and pay
attention if I notice anything.
--
You received this bug notification because you
Wow, great catch Michi!!
--
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
** Branch linked: lp:~michihenning/unity-scopes-api/atexit-crash
--
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
Michał, I've built a branch that I believe will fix things in silo 26.
Have you at all been able to make the crash happen on your phone? (As
far as I know, it only happens on Arm, but I haven't been able to
reproduce.) If you can reproduce the problem, could you please try with
the PPA in silo 26
OK, I think I finally found it. There are some dummy loggers in the run
time that I added because some of the unit tests run without a fully
initialized run time (which provides access to the logger), but still
need a working logger. For these tests, a global dummy instance is used.
It's the
You're a rockstar Michi, thank you for all this.
We don't have mock data for this purpose, but you could run Telegram off
this branch (README.md will quickly tell you how to, basically
./setup.sh -t desktop -d && ./setup.sh -t desktop -b will download deps
and build it for you). The branch is a
Hi Michael, which branch were you referring to?
The more I look, the more I'm sure that the problem isn't in the
telegram scope or scopes API, but probably due to the use of the checked
singleton in boost::log. I'm fresh out of ideas as to how to fix it at
the moment :-(
--
You received this
BTW, I haven't read enough of the code to know... Is there any chance
that one of the libraries that the telegram scope calls into uses
boost::log?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-mediascanner
in
Replied on IRC, for record purposes:
Sorry I only now noticed your comments, I forgot to leave the link :/
lp:~libqtelegram-team/telegram-app/telegram2-all-platforms
I will verify the external library for use of boost.
--
You received this bug notification because you are a member of Ubuntu
Talked on IRC, but for the record:
While the app uses two dependencies, these don't use boost - and the
scope uses none of those altogether. The scope's pure Qt talking to an
sqlite db and surfacing results to scopes-api, not much going on in
there, so at least on that end it's not related to
Looking through the unresolved externals in libsqlite.so, it doesn't
appear to be using boost::log either, so that's not it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-mediascanner
in Ubuntu.
I've spent a lot of hours on this so far, without getting closer :-(
Up front, Timo, if there are shell crashes, that's almost certainly an
unrelated problem. I don't see (even in theory) how a crashing scope
could be responsible for that. For starters, the scope is a separate
unrelated process.
Hi guys, sorry for late reply. I've been pulled to Tg unrelated
assignment and was neck down in documentation. First of all, thank you
for your input, I appreciate this wasn't just left here.
Michi, I'm sorry, but I have not had chance to run this with valgrind on
the desktop. I'll have to
@Michi it happens when I have the Telegram setting enabled in Today
scope, but otherwise I don't know. I didn't do anything Telegram related
if I recall correctly, but Unity 8 just crashed and it was apparently
caused by this scoperunner crash.
I used to disable the setting but enabled it again
Note that this particular crash was traceable to the
https://errors.ubuntu.com/problem/21d9e7ddf91a26b21abfb2758315ad41fcfd3fa9
problem, but I also had already one other unrelated unity8 crash with
OTA-8 that lacks "Disassembly" field and thus there's no 'problem' page
for that. So there are
Timo, any idea what it was you did to make the problem show up?
--
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
Got this on OTA-8 / Telegram 2.
--
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
errors.u.c is still reporting a significant number of crashes with
telegram 2.0.4
--
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
Since Jean-Baptiste raised this affects Telegram 2.0.4.* as well,
perhaps we could get some fellow developers to review the code, as it
seems we're out of luck trying to address this, and it's not really much
code in the query.cpp
http://bazaar.launchpad.net/~libqtelegram-team/telegram-
Did you run the code under valgrind or with MALLOC_CHECK_=2 ?
Is there any way for me to reproduce the issue? I'd like to help, but
it's difficult without any more info.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: canonical-devices-system-image
Milestone: ww46-2015 => ww02-2016
--
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: canonical-devices-system-image
Status: Confirmed => 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:
corrupted
43 matches
Mail list logo
