[bug] Contacts disappear if Google account contact sync fails

answered 2018-08-10 17:10:24 +0300

shubell
111 ●1 ●5 ●4

Same issue here. Contacts dissapering. After a new sync contacts are back. Really anoying when you don't know who is calling. I think my issues started when i readded my google account.

answered 2019-01-08 09:40:44 +0300

wosrediinanatour
1216 ●34 ●55 ●61

updated 2019-01-09 23:28:23 +0300

Bug still exists in SailfishOS X 3.0.1.11. :-/ (Note that this is wrong, see Update 3)

Update 1:

Journal tells:

Jan 08 16:12:05 Sailfish [3138]: [W] unknown:0 - CDExport: triggering contacts remote sync: ""    
Jan 08 16:01:23 Sailfish google-contacts-client[24126]: [W] unknown:0 - This device does not have a BT adapter
Jan 08 16:01:24 Sailfish google-contacts-client[24126]: [W] unknown:0 - The 'mergePresenceChanges' option has not been configured - presence changes will only be reported via ContactManagerEngine::contactsPresenceChanged()
Jan 08 16:01:25 Sailfish invoker[1705]: SailfishKeyProvider_ini_read: reached end of file
Jan 08 16:01:25 Sailfish invoker[1705]: SailfishKeyProvider_ini_read: reached end of file
Jan 08 16:01:25 Sailfish google-contacts-client[24126]: [D] unknown:0 - connection-manager.cpp 107 setupSocketConnection p2p error: QDBusError("org.freedesktop.DBus.Error.FileNotFound", "Failed to connect to socket /run/user/100000/signond/socket: No existe el fichero o el directorio") 1
Jan 08 16:01:25 Sailfish google-contacts-client[24126]: [D] unknown:0 - connection-manager.cpp 148 init Peer connection unavailable, activating service
Jan 08 16:01:25 Sailfish google-contacts-client[24126]: [D] unknown:0 - identityimpl.cpp 96 updateState Updating state:  "PendingRegistration" SignOn::IdentityImpl(0x1bcda0)
Jan 08 16:01:25 Sailfish google-contacts-client[24126]: [D] unknown:0 - authsessionimpl.cpp 94 initInterface
Jan 08 16:01:25 Sailfish google-contacts-client[24126]: [D] unknown:0 - authsessionimpl.cpp 94 initInterface
Jan 08 16:01:25 Sailfish dbus-daemon[1604]: Activating service name='com.google.code.AccountsSSO.SingleSignOn'
Jan 08 16:01:25 Sailfish [19971]: signondaemon.cpp 388 init Failed to SUID root. Secure storage will not be available.
Jan 08 16:01:25 Sailfish dbus-daemon[1604]: Successfully activated service 'com.google.code.AccountsSSO.SingleSignOn'
Jan 08 16:01:25 Sailfish google-contacts-client[24126]: [D] unknown:0 - connection-manager.cpp 165 init Connected to "libsignon-qt1"
Jan 08 16:01:25 Sailfish google-contacts-client[24126]: [D] unknown:0 - identityimpl.cpp 96 updateState Updating state:  "Ready" SignOn::IdentityImpl(0x1bcda0)
Jan 08 16:01:25 Sailfish google-contacts-client[24126]: [D] unknown:0 - identityimpl.cpp 96 updateState Updating state:  "NeedsUpdate" SignOn::IdentityImpl(0x1bcda0)
Jan 08 16:01:25 Sailfish google-contacts-client[24126]: [D] unknown:0 - identityimpl.cpp 96 updateState Updating state:  "PendingUpdate" SignOn::IdentityImpl(0x1bcda0)
Jan 08 16:01:25 Sailfish google-contacts-client[24126]: [D] unknown:0 - identityimpl.cpp 442 infoUpdated SERVER INFO UPDATED. NeedsUpdate " 17 "

Msync log:

D] unknown:0 - Sync session started
[D] unknown:0 - Synchronizer::getBackUpRestoreState
[D] unknown:0 - Start sync requested for profile: "google.Contacts-14"
[D] unknown:0 - ProfileManager::syncProfile( "google.Contacts-14" )
[D] unknown:0 - found a valid sync profile with the given name: "google.Contacts-14"
[D] unknown:0 - Synchronizer::getBackUpRestoreState
[D] unknown:0 - Starting sync with profile "google.Contacts-14"
[D] unknown:0 - Disable sync on change: false false
[D] unknown:0 - Starting oop plugin  "google.Contacts-14"
[D] unknown:0 - Starting process  "/usr/lib/buteo-plugins-qt5//oopp/google-contacts-client"  with plugin name  "google-contacts"  and profile name  "google.Contacts-14"
[W] unknown:0 - This device does not have a BT adapter
[D] unknown:0 - New network state: true  New type:  "WLAN" ( 2 )
[D] unknown:0 - Network status:
[D] unknown:0 -     Online:: true
[D] unknown:0 -     Connection:: 2
[D] unknown:0 - attempting to register dbus service: "com.buteo.msyncd.plugin.google.Contacts-14"
[D] unknown:0 - Plugin  "google-contacts"  with profile  "google.Contacts-14"  registered at dbus  "com.buteo.msyncd.plugin.google.Contacts-14"  and path  /
[D] unknown:0 - Process  "/usr/lib/buteo-plugins-qt5//oopp/google-contacts-client"  started with pid  9183
[D] unknown:0 - Client plug-in runner initialized
[D] unknown:0 - New network state: true  New type:  "WLAN" ( 2 )
...
...
...
[D] unknown:0 - found a valid sync profile with the given name: "google.Contacts"
[D] unknown:0 - No sync log found for profile: "google.Contacts"
[D] unknown:0 - ProfileManager::syncProfile( "google.Signon" )
...
[D] unknown:0 - debug:  successfully triggered sync with profile: "google.Contacts-14"
...
[D] unknown:0 - info :  finalCleanup() fixed up avatars from 0 Google contacts
[D] unknown:0 - info :  Finished "google" "Contacts" sync at: "2019-01-08T16:58:21"
[D] unknown:0 - Session finished: "google.Contacts-14" , status: 4
[D] unknown:0 - ProfileManager::enableStorages
[D] unknown:0 - ProfileManager::enableStorages
[D] unknown:0 - aStatus 4
[D] unknown:0 - ProfileManager::syncProfile( "google.Contacts-14" )
[D] unknown:0 - found a valid sync profile with the given name: "google.Contacts-14"
[D] unknown:0 - Stopping the OOP process for  "google-contacts"
[D] unknown:0 - Process  "/usr/lib/buteo-plugins-qt5//oopp/google-contacts-client"  finished with exit code 15
[D] unknown:0 - ProfileManager::syncProfile( "google.Contacts-14" )
[D] unknown:0 - found a valid sync profile with the given name: "google.Contacts-14"
[D] unknown:0 - Sync status changed for account "14"

I don't want to post all logs here, since they include calendar events.

Update 2:

I found in the logs that I still had "Voicecall combined patch" installed using Patch Manager 3.0.55. I removed the patch, restarted, and haven't observed the error in the first 20 minutes.

Update 3:

Sorry...my patchmanager installation interferred with the latest Google Contacts Client. In my case, the error have been fixed with 3.0.1.11!*

answered 2019-03-19 10:37:01 +0300

mcencora
601 ●3 ●9 ●12

Problem still shows up in 3.0.2.8