People app does not start (and how to fix it)

asked 2020-05-06 11:03:07 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2020-05-06 14:30:08 +0300

jiit gravatar image

For some reasons, today my People App (jolla-contacts) did not start from GUI (tapping on the icon).

It did however launch successfully when started from terminal (/usr/bin/jolla-contacts).

In my case, I have been able to fix it the following way. YMMV.

From another thread: check that the contacts database is OK:

$ devel-su
# sqlite3 /home/nemo/.local/share/system/privileged/Contacts/qtcontacts-sqlite/contacts.db 
sqlite> pragma integrity_check;
ok
sqlite> ^D

Getting anything else than "ok" is NOT ok, and you need to find some way of fixing the database. STOP HERE if you get errors here.

Now, we make a backup to be safe and see who is using the database:

# cd /home/nemo/.local/share/system/privileged/Contacts/qtcontacts-sqlite/
# sqlite3 contacts.db .dump > /home/nemo/contacts_db_dump.sql-$(date -I)
# fuser *

here you get a list of PIDs back. Each of those has the database open. We will stop or close them, after finding out which processes they are with ps -ef | grep <<PID>> and various calls to systemctl status <<foo>>

# systemctl stop contactsd.service --user
# systemctl stop commhistoryd  --user
# systemctl stop voicecall-ui-prestart.service --user
# killall jolla-contacts
# fuser *

Now no processes should show up any more in the fuser call.

Now, PROBABLY just restarting the services will be enough. But while we're here, let's vacuum the database for good measure. This doesn't really do anything except make the disk usage smaller but it can't hurt.

# sqlite3 contacts.db 
sqlite> vacuum;
sqlite> ^D

Lets start everything again:

# systemctl start voicecall-ui-prestart.service --user
# systemctl start commhistoryd  --user
# systemctl start contactsd.service --user

From this point, People App started again.

edit retag flag offensive close delete

Comments

1

Simply uninstalling and reinstalling the app normally fixes the problem.

Spam Hunter ( 2020-05-06 12:22:44 +0300 )edit
1

I probably was overthinking it, yes. A reboot possibly would have done it as well :D

nephros ( 2020-05-07 16:34:09 +0300 )edit

Yes, i was experiencing this bug at least twice and a restart did help.

sailr ( 2020-05-09 12:44:32 +0300 )edit