/usr/bin/unity8:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::remove_match

[errors.ubuntu.com bug bridge]

This is HW specific

build #201

TEST CASE:
Connect to the device and run as phablet:
while sleep 1; do
    gdbus call --system -d com.canonical.Unity.Screen -o /com/canonical/Unity/Screen \
        -m com.canonical.Unity.Screen.setScreenPowerMode on 3
    sleep 1
    gdbus call --system -d com.canonical.Unity.Screen -o /com/canonical/Unity/Screen \
        -m com.canonical.Unity.Screen.setScreenPowerMode off 3
done

Let it run until the device crashes.

== original description ==
I get this crash when an incoming calls ends and the caller hangs up. This is rather frequent (3 times on 4 incoming calls)

The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.00+14.10.20140817-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1b1bfdcf7c57cb67053a35e55bbd34f1826e7ae2 contains more details.

u-s-c crash https://errors.ubuntu.com/oops/6b639636-287e-11e4-a37b-fa163e78b027 always occurs at the same time.

[Michał Sawicz (saviq)]

Guessing slightly here:

unity-system-compositor crashes, session dies, unity8 is trying to exit, but tries to talk to dbus when destroying core::dbus::Signal<mpris::Player::Signals::PlaybackStatusChanged, core::ubuntu::media::Player::PlaybackStatus>::~Signal, but dbus is no moar, so abort.

[Michał Sawicz (saviq)]

The underlying cause seems to be the u-s-c crash really.

[Michał Sawicz (saviq)]

Oh and yeah, it's between dbus-cpp and media-hub that the abort happens (probably shouldn't happen if you're just trying to shut down but dbus isn't there).

[Thomas Voß (thomas-voss)]

I agree with saviq's conclusions here. At any rate, dbus::~Signal<...> should never throw. I logged a respective bug here: https://launchpad.net/bugs/1359258

[Thomas Voß (thomas-voss)]

Please note that I'm hesitant to call an ordinary abort due to an exception being throw as a non-critical issue.

[Thomas Voß (thomas-voss)]

Let me rephrase :) I don't think this issue as critical as we are observing an ordinary abort due to an uncaught exception here.

[Michał Sawicz (saviq)]

Sure, the original issue of u-s-c crashing in the first place is the critical one.

[Michael Terry (mterry)]

Can I get some more concrete reproduction steps?

I tried the following with phonesim:
 - /usr/share/ofono/scripts/dial-number 199 # to trigger an incoming call
 - Answer call, dialer-app appears
 - /usr/share/ofono/scripts/hangup-all # to end call

I couldn't get a crash. Do I need to be in a certain state (like in the greeter), or is this just not reproducable with phonesim?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Loïc Minier (lool)]

I've tried this on:
current build number: 3
device name: mako
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2014-08-22 13:06:36
version version: 3
version ubuntu: 20140822
version device: 20140811.1

for ~5mn and about 100 cycles and it didn't crash; I guess this doesn't affect nexus 4

[Alexander Sack (asac)]

Hi,

any update on this one? Any preliminary patch we could try?

[Alberto Aguirre (albaguirre)]

Unfortunately it seems to be a driver issue.