Dialer segfaults when creating a new contact with photo from the camera roll widget

[quandan]

$ system-image-cli -i
current build number: 120
device name: krillin
channel: ubuntu-touch/devel-proposed/krillin.en
last update: 2015-07-12 08:45:29
version version: 120
version ubuntu: 20150624
version device: 20150529-8e13c5f
version custom: 20150528-722-29-15-vivid
Steps:
1) Load address book app
2) Create contact from dialer and add photo
3) Select camera as image source
4) Switch to the photoroll
5) Select a photo
6) Save contact
Expectation:
 choose the photo and save contact successfully
Actual result:
 After action 5#, all the information disappeared, and automatically return to the contact list panel , that contact doesn't exist.

[Renato Araujo Oliveira Filho (renatofilho)]

I was able to save a contact using the photo from photoroll.

Could you try to reproduce the problem and attache the log file from address-book-app: /home/phablet/.cache/upstart/application-legacy-address-book-app-.log

[Sebastien Bacher (seb128)]

Renato, I can reproduce on current rc-proposed/bq, adding the log from the dialer app since addressbook is not being used as far as I can say (the components are imported by dialer rather)

[Sebastien Bacher (seb128)]

The dialer hits a segfault there

#0 QCoreApplication::notifyInternal (this=0xbedfa358,
    receiver=receiver@entry=0x24d4cb8, event=event@entry=0x23349d8)
    at kernel/qcoreapplication.cpp:934
#1 0xb6df7584 in sendEvent (event=0x23349d8, receiver=0x24d4cb8)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:228
#2 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
    event_type=event_type@entry=0, data=0x1d2e498)
    at kernel/qcoreapplication.cpp:1552
#3 0xb6df797a in QCoreApplication::sendPostedEvents (
    receiver=receiver@entry=0x0, event_type=event_type@entry=0)
    at kernel/qcoreapplication.cpp:1410
#4 0xb6e30950 in postEventSourceDispatch (s=0x1d840a0)
    at kernel/qeventdispatcher_glib.cpp:271
#5 0xb5f36f68 in g_main_context_dispatch ()
   from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
#6 0xb5f37114 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0

Seems like an important issue, could we get it on the ota8 list?

[Renato Araujo Oliveira Filho (renatofilho)]

I still did not find the source of the problem, but I got some new info:

- The crash only happens when running the app from the launcher (starting the app from the command line does not cause the crash)
- The only crash reported by apport is on content-hub (attached), but does not contains any crash file

[Renato Araujo Oliveira Filho (renatofilho)]

The crash only happens if the addres-book-app and dilar app are running at the same time,

[Launchpad Janitor (janitor)]

This bug was fixed in the package address-book-app - 0.2+16.04.20151028.2-0ubuntu1

---------------
address-book-app (0.2+16.04.20151028.2-0ubuntu1) xenial; urgency=medium

  * Does not export contact extend detail into vcard. (LP: #1510259)
  * Ignore default actions on contact view. (LP: #1466759)
  * Updated autopilot tests, with the new ABContactEditorPage.
  * Use Runnable implementation instead of thread to avoid overload cpu
    usage. Implement async copyImage support. (LP: #1469005)
  * Used import icon in the "import from sim" button (LP: #1424819)

 -- Renato Araujo Oliveira Filho <email address hidden> Wed, 28 Oct 2015 20:36:53 +0000