Description of problem: I was modifying a contact in Contacts that seemed not to be synched with Nextcloud. I just add a note with "test" to the contact and clicked update. Later, I saw in the system journal that there were many log messages regarding a contact that had an invalid email adres. The invalid email adress was basically just a name with spaces, not an email adress at all. Version-Release number of selected component: gnome-contacts-40.0-1.fc34 Additional info: reporter: libreport-2.14.0 backtrace_rating: 3 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-dbus\x2d:1.2\x2dorg.gnome.Contacts.slice/dbus-:1.2-org.gnome.Contacts cmdline: /usr/bin/gnome-contacts --gapplication-service crash_function: contacts_fake_persona_apply_changes_to_real_co.isra.0 executable: /usr/bin/gnome-contacts journald_cursor: s=062cdee0011a4581bd8e5dadc9479008;i=3229ef;b=52aaabd2c01f4d5eb60638e401f2f132;m=1e5be90560;t=5c15db3953666;x=8bf331a09577995d kernel: 5.11.16-200.fc33.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1778725 [details] File: backtrace
Created attachment 1778726 [details] File: core_backtrace
Created attachment 1778727 [details] File: cpuinfo
Created attachment 1778728 [details] File: dso_list
Created attachment 1778729 [details] File: environ
Created attachment 1778730 [details] File: limits
Created attachment 1778731 [details] File: maps
Created attachment 1778732 [details] File: mountinfo
Created attachment 1778733 [details] File: open_fds
Created attachment 1778734 [details] File: proc_pid_status
Created attachment 1778735 [details] File: var_log_messages
Similar problem has been detected: I tried to update a contact in GNOME Contacts that does not synchronize well with the Nextcloud address book, configured via GNOME Online Accounts (GOA). GNOME Contacts does not show the address of this contact. Moreover, GNOME Contacts seems to delete the address of the contact in Nextcloud. I started GNOME Contacts from the command line, and have these warnings and error when editing the contact: (gnome-contacts:122243): gnome-contacts-CRITICAL **: 09:13:46.420: contacts_fake_individual_set_primary_persona: assertion 'self != NULL' failed (gnome-contacts:122243): folks-WARNING **: 09:13:46.428: email-details.vala:55: Empty e-mail address passed to EmailFieldDetails. (gnome-contacts:122243): folks-WARNING **: 09:13:46.431: phone-details.vala:72: Empty phone number passed to PhoneFieldDetails. (gnome-contacts:122243): folks-WARNING **: 09:13:49.538: url-details.vala:91: Empty URI passed to UrlFieldDetails. (gnome-contacts:122243): folks-WARNING **: 09:13:49.551: postal-address-details.vala:285: Empty postal address passed to PostalAddressFieldDetails. (gnome-contacts:122243): folks-WARNING **: 09:13:49.565: note-details.vala:78: Empty note passed to NoteFieldDetails. (gnome-contacts:122243): folks-WARNING **: 09:14:13.261: postal-address-details.vala:285: Empty postal address passed to PostalAddressFieldDetails. (gnome-contacts:122243): gnome-contacts-ERROR **: 09:14:53.827: contacts-fake-persona-store.vala:402: Couldn't write property: Unknown error setting property ‘urls’: Changing the ‘urls’ property failed due to reaching the timeout. Trace/breakpoint trap (core dumped) As a side note, I see hundreds of these warnings as well: (gnome-contacts:122243): folks-WARNING **: 09:10:24.553: Invalid e-mail address when looking for potential match: test reporter: libreport-2.14.0 backtrace_rating: 3 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0a4547b1-182d-4797-ab17-1cf77c7d9df2.scope cmdline: gnome-contacts crash_function: contacts_fake_persona_apply_changes_to_real_co.isra.0 executable: /usr/bin/gnome-contacts journald_cursor: s=062cdee0011a4581bd8e5dadc9479008;i=3240b7;b=52aaabd2c01f4d5eb60638e401f2f132;m=20f029858f;t=5c16713b6c63c;x=5f8363d36007851b kernel: 5.11.16-200.fc33.x86_64 package: gnome-contacts-40.0-1.fc34 reason: gnome-contacts killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
See also: bug 1830774. See also: https://gitlab.gnome.org/GNOME/gnome-contacts/-/issues/186.
Maybe this issue is related to linked contacts.
*** Bug 1958034 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I have GNOME contacts connected to my Nextcloud instance. I have many contacts and Nextcloud is quite slow. Maybe this triggered the issue. The crash happened when I was just updating and editing and adding contacts. reporter: libreport-2.15.2 backtrace_rating: 3 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-dbus\x2d:1.2\x2dorg.gnome.Contacts.slice/dbus-:1.2-org.gnome.Contacts cmdline: /usr/bin/gnome-contacts --gapplication-service crash_function: contacts_fake_persona_apply_changes_to_real_co.isra.0 executable: /usr/bin/gnome-contacts journald_cursor: s=78b3685347c8400cb7f43b84174c895f;i=f3e42;b=3ef545b960764af2b9b4487eb3d3192f;m=ff2e7b8d7;t=5c96fb03e9d17;x=b59b42698bb7b88b kernel: 5.13.8-200.fc34.x86_64 package: gnome-contacts-40.0-1.fc34 reason: gnome-contacts killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was editing a contact and when I clicked on Done, the program crashed. reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Contacts cmdline: /usr/bin/gnome-contacts --gapplication-service crash_function: contacts_fake_persona_apply_changes_to_real_co.isra.0 executable: /usr/bin/gnome-contacts journald_cursor: s=4cc7477ddb9843af859fe887512a462d;i=158e1;b=c062625a10fd49c2be6a0e70a910f628;m=8bf74fe9f;t=5cfa532c92a3a;x=9724219d3372a39a kernel: 5.14.12-200.fc34.x86_64 package: gnome-contacts-40.0-1.fc34 reason: gnome-contacts killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1838690 [details] File: backtrace
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.