*** This bug is a duplicate of bug 1655936 ***
https://bugs.launchpad.net/bugs/1655936
Marked this bug as duplicate of #1655936 to unconfuse errors.ubuntu.com
(even though the bugs are technically different issues and the one from
this bug was fixed long time ago).
** This bug has been
Yeah, it's a different issue altogether
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1655936
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363946
Title:
unity8-dash crashed with SIGABRT
@Daniel I see your point about Mir. Anyway, all I'm saying is this
problem manifested via
https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb
is completely different from the original problem described in this bug.
The only common thing is qFatal() gets called. In the
None of that is from the Mir source code :)
It just means Unity8 has gone AWOL, hence the dash can't find its Mir
server any more.
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Status: New =>
Priority bump just so this bug gets attention. Still the #1 Unity8
crash...
https://errors.ubuntu.com/?package=unity8=month
** Changed in: canonical-devices-system-image
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Daniel, it seems that all bugs that end up in qFatal() fall into the
same bucket.. The error you linked
https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb
aborts because of Mir:
#4 QMessageLogger::fatal (this=0xb6410088 ,
this@entry=0xb6fa9000, msg=0xb4160e50
Still #4 top Unity8 crash according to errors.ubuntu.com. And this is #2
of those that are still happening in 16.10.
** Changed in: unity-scopes-api (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is still one of the top Unity8 crashes apparently...
https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363946
Title:
Also, can you attach unity8-dash.log when this happens? I wonder why you
don't see a blank dash instead...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363946
Title:
unity8-dash crashed with
Hi Timo, how did you manage to end up with a broken locale setup?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363946
Title:
unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect
I got this crash on my Pro 5 with OTA-11. Went back to the ubuntu dots
animation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363946
Title:
unity8-dash crashed with SIGABRT in qt_message_fatal()
** Changed in: unity-scopes-shell (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363946
Title:
unity8-dash crashed with SIGABRT in
** Branch linked: lp:~stolowski/unity-scopes-shell/invalid-locale-
crashfix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363946
Title:
unity8-dash crashed with SIGABRT in qt_message_fatal() under
After trying to come up with a fallback for wrong locale I've to say
this cannot be fixed at the point we hit the problem in unity-scopes-
shell. It's already too late, and moreover there seem to be issues with
the libstdc++ library when locale setup is broken and it's impossible to
recover.
And a new bug just reported by Michi against GCC with a minimal test
case: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70493
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363946
Title:
Ok, after discussing it on the standup we agreed that unity-scopes-shell should
handle this exception and fallback to standard locale if the two conditions
hold true:
- scopes api runtime initialization throws and
- current locale is not "" or "C" already
** Changed in: unity-scopes-shell
** Also affects: unity-scopes-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363946
Title:
unity8-dash crashed with SIGABRT in
unity-scopes-shell, rather
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363946
Title:
unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect
locale
To manage notifications
I don't think scopes API can do anything here. It can't fiddle with the
locale because that's a process-wide attribute.
We just propagate the exception up the caller, so the crash would appear
to happen because the dash doesn't handle the exception when it
initializes the runtime.
It seems this
It happened this morning on krillin rc-proposed 202
https://errors.ubuntu.com/oops/55295946-a23a-11e5-a948-fa163e4aaad4
** This bug is no longer a duplicate of bug 1303637
scoperunner in RegistryI test fails if locale is not set
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1303637 ***
https://bugs.launchpad.net/bugs/1303637
** This bug has been marked a duplicate of bug 1303637
scoperunner in RegistryI test fails if locale is not set
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I expect the exception comes out of the bowels of the glib ini parser.
There is probably little that the scopes API can do, other than to maybe
throw a separate exception for the parsing failure. But the shell should
not try and initialize the run time without catching the exception and
handling
The retrace is unfortunately that of a different crash, but the
difference is really just the error message as seen in the description.
Let me know if you need a real retrace of the problem in question
** Information type changed from Private to Public
--
You received this bug notification
** Changed in: unity-scopes-api (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363946
Title:
unity8-dash crashed with SIGABRT in qt_message_fatal() under
24 matches
Mail list logo
