/usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_with_reply_and_block_for_at_most

303 crashes on errors.u.c as of today https://errors.ubuntu.com/bucket/?id=/usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service%3A6%3A__gnu_cxx%3A%3A__verbose_terminate_handler%3A__cxxabiv1%3A%3A__terminate%3Astd%3A%3Aterminate%3A__cxxabiv1%3A%3A__cxa_throw%3Acore%3A%3Adbus%3A%3ABus%3A%3Asend_with_reply_and_block_for_at_most

https://errors.ubuntu.com/oops/b91df592-1924-11e4-a0bb-fa163e525ba7 might be related

The stack trace on this bug has improved, please look again at the errors.u.c link

This is currently the most common crash on the phone

I have a video of one of the crashes here: https://chinstrap.canonical.com/~chrisgagnon/v6.vlc

This bug was fixed in the package indicator-network - 0.5.1+14.10.20140826-0ubuntu1

---------------
indicator-network (0.5.1+14.10.20140826-0ubuntu1) utopic; urgency=low

  [ Jussi Pakkanen ]
  * Exit gracefully on dbus error conditions. (LP: #1343341)
 -- Ubuntu daily release <email address hidden> Tue, 26 Aug 2014 15:04:09 +0000

Do we have any reliable method to invoke the crash manually?

frankly no.. The only thing you could try is to tap repeatedly on an akready connected access point. That should trigger the timeout.You notice hitting this bug when the indicator goes blank and repopulates. There should be no crash file under /var/crash/ for indicator-network after this.

This bug was fixed in the package indicator-network - 0.5.1+14.10.20140826-0ubuntu1

---------------
indicator-network (0.5.1+14.10.20140826-0ubuntu1) 14.09; urgency=low

  [ Jussi Pakkanen ]
  * Exit gracefully on dbus error conditions. (LP: #1343341)
 -- Ubuntu daily release <email address hidden> Tue, 26 Aug 2014 15:04:09 +0000

NOT fixed in RTM yet.

arvhice src-copy

https://errors.ubuntu.com/oops/ba473ca0-2ec1-11e4-861b-fa163e339c81 Shows this is still broken in indicator-network version(0.5.1+14.10.20140826-0ubuntu1)

There are 26 crashes for this on the 20140827.1 image which is using indicator-network version(0.5.1+14.10.20140826-0ubuntu1) moving from fix released to confirmed

Oh, it's another Properties.Get() default timeout, Jussi, please give this the usual treatment:
#10 0x000950da in platform::nmofono::wifi::Link::connect_to (this=0xaafea0, accessPoint=...) at /build/buildd/indicator-network-0.5.1+14.10.20140826/src/connectivity-cpp/src/platform/nmofono/wifi/link.cpp:333

Jussi, just come to think of it.. Just extend the try-catch to the entire Link::connect_to()

This is still a bug in the latest image

https://errors.ubuntu.com/oops/1672f12a-3d1a-11e4-b050-fa163e22e467

current build number: 40
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
version version: 40
version ubuntu: 20140915
version device: 20140908-d8c11f3
version custom: 1410739265

indicator-network 0.5.1+14.10.20140829~rtm-0ubuntu1 [origin: Ubuntu RTM]

This is happening again in the non-rtm image. I reopened the bug. It doesn't happen as often as it used to.

current build number: 245
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/utopic-proposed
last update: 2014-09-18 22:34:55
version version: 245
version ubuntu: 20140918
version device: 20140917
version custom: mako-0.5

https://errors.ubuntu.com/oops/d0a92ba8-400e-11e4-ad89-fa163e22e467

https://errors.ubuntu.com/oops/602cbf8e-4009-11e4-9d61-fa163e4ccdf2

sigh,, ok. thanks!

This was the #2 crasher on the 20140925 image.

Jussi, please take a look ASAP.

This bug was fixed in the package indicator-network - 0.5.1+14.10.20141007.1-0ubuntu1

---------------
indicator-network (0.5.1+14.10.20141007.1-0ubuntu1) utopic; urgency=low

  [ Jussi Pakkanen ]
  * Dbus-cpp crash fix. (LP: #1343341)
  * Mark modem as unavailable if modem manager is missing. (LP:
    #1356200)
 -- Ubuntu daily release <email address hidden> Tue, 07 Oct 2014 12:48:40 +0000