** Changed in: unity-mir
Status: In Progress = 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/1240400
Title:
dialer-app crashed with SIGSEGV in __GI___pthread_mutex_lock()
To
This bug was fixed in the package unity-mir -
0.3+14.04.20140311.1-0ubuntu1
---
unity-mir (0.3+14.04.20140311.1-0ubuntu1) trusty; urgency=low
[ Michael Zanetti ]
* expose ApplicationImage's sourceSize (LP: #1282126)
[ Andreas Pokorny ]
* Use the process id found in the
** Branch linked: lp:ubuntu/unity-mir
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240400
Title:
dialer-app crashed with SIGSEGV in __GI___pthread_mutex_lock()
To manage notifications about this
** Changed in: unity-mir
Status: New = Confirmed
** Changed in: unity-mir
Importance: Undecided = High
** Changed in: unity-mir
Importance: High = Critical
** Changed in: unity-mir
Status: Confirmed = In Progress
** Changed in: mir
Status: Confirmed = Invalid
**
** Branch linked: lp:~andreas-pokorny/unity-mir/fix-1240400
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240400
Title:
dialer-app crashed with SIGSEGV in __GI___pthread_mutex_lock()
To manage
ApplicationManager only uses the app-id to track processes, and hence
mismatches start/stop reports and authorization request.
** Also affects: dialer-app
Importance: Undecided
Status: New
** No longer affects: dialer-app
** Also affects: unity-mir
Importance: Undecided
A fix for that bug would hide the issue here, but we should not crash in
that case.
When the incoming call is accepted another session is created for
another dialer-app which for some reason is not launched. The final
crash happens in unity-mir ApplicationManager::suspendApplication
** No longer affects: unity8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240400
Title:
dialer-app crashed with SIGSEGV in __GI___pthread_mutex_lock()
To manage notifications about this bug go
I can reproduce the issue easily too. But only when I start dialer-app
from the command line. Additionally dialer-app does not crash as far as
I can tell, it only terminates due to unity8 crashing.
** Also affects: unity8
Importance: Undecided
Status: New
--
You received this bug
just a short update - the crash does not occur when the application is
launched with upstart-launch-app
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240400
Title:
dialer-app crashed with SIGSEGV
So should this be marked as duplicate of bug 1263182, or should Mir be
fixed to not crash in this case?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240400
Title:
dialer-app crashed with SIGSEGV
** Changed in: mir (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240400
Title:
dialer-app crashed with SIGSEGV in __GI___pthread_mutex_lock()
To
** Changed in: mir (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) = Andreas Pokorny (andreas-pokorny)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240400
Title:
dialer-app crashed with SIGSEGV
** Changed in: dialer-app (Ubuntu)
Assignee: rosa maria (rprosamaria383) = (unassigned)
** Changed in: mir
Assignee: rosa maria (rprosamaria383) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mir
Assignee: (unassigned) = rosa maria (rprosamaria383)
** Changed in: dialer-app (Ubuntu)
Assignee: (unassigned) = rosa maria (rprosamaria383)
** Changed in: dialer-app (Ubuntu)
Assignee: rosa maria (rprosamaria383) = (unassigned)
** Changed in: dialer-app
** Changed in: mir (Ubuntu)
Status: New = Triaged
** Changed in: mir (Ubuntu)
Importance: Undecided = Critical
** Changed in: mir (Ubuntu)
Assignee: (unassigned) = Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: mir (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/1240400
Title:
dialer-app crashed with SIGSEGV in __GI___pthread_mutex_lock()
This bug was fixed in the package dialer-app -
0.1+14.04.20140130-0ubuntu1
---
dialer-app (0.1+14.04.20140130-0ubuntu1) trusty; urgency=low
[ Bill Filler ]
* o not pass the phone number as a parameter when pushing the live
call view for an outgoing call. The correct value
I can reproduce that even without using autopilot, just start dialer-app
from command line:
dialer-app --desktop_file_hint=/usr/share/applications/dialer-
app.desktop
Then call the phone and answer the call in the snap decision. The focus
will get back to the dialer-app, and as soon as you try
this is not fixed. using build 152 on Nexus 4 the dialer-app autopilot
tests (from trunk, where the test in question is re-enabled), I get the
same problem as described in the original bug. Screen goes black and
then the shell crashes. I am going to re-add the try catch in the
dialer-app autopilot
Seems this is fixed now, https://code.launchpad.net/~pitti/dialer-app
/drop-expected-crash/+merge/199754 succeeded.
** Changed in: mir
Status: New = Fix Released
** Changed in: dialer-app (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1233988 ***
https://bugs.launchpad.net/bugs/1233988
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1233988, so it is being marked as such. Please
Unduping for the rationale above, quickly discussed with Daniel on IRC.
** This bug is no longer a duplicate of bug 1233988
With Mir enabled: platform-api apps crash with SIGABRT in
__gnu_cxx::__verbose_terminate_handler(), thrown from
mir::client::DisplayConfiguration::copy_to_client()
--
Adding a Mir task as the stack trace has Mir all over the place.
** Also affects: mir
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/1240400
Title:
Most probably a duplicate of bug 1233988. I'll re-test once that fix
lands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240400
Title:
dialer-app crashed with SIGSEGV in
Nope, I do have that Mir version, and moreover this is a segfault while
bug 1233988 is an ABRT (most probably an assertion failure).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240400
Title:
This is actually most likely a duplicate of bug 1233988. Even with all
the fixes for 1233988, you will still get a abort/crash (qFatal()) if
the app can't connect to the server for some reason, but you should also
get a FATAL:... stderr (I think) message from Qt. Previously, the
platform API would
The exact error message is QUbuntu: Could not create application
instance you should get is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240400
Title:
dialer-app crashed with SIGSEGV in
Alexandros, but dialer-app already connected to Mir.. I see this crash
while dialer-app is already visible, it just crashes in the middle of
receiving a phone call. (Also, it's NOT a SIGABRT, and I don't see any
FATAL: messages anywhere)
--
You received this bug notification because you are a
29 matches
Mail list logo
