answered
2016-03-12 06:30:53 +0300
I had the same symptom not spontaneously, but after a factory reset of the phone (and installing every upgrade up until 2.0.0.10). After some investigation, I found I had lots of these error messages in journalctl:
Mar 11 22:04:18 Jolla invoker[7658]: /usr/bin/commhistoryd: symbol lookup error: /usr/bin/commhistoryd: undefined symbol: _ZN11CommHistory10GroupModel20enableContactChangesEb
What fixed it for me was to re-install commhistoryd as root and restart it as nemo:
# pkcon install commhistoryd
$ systemctl --user restart commhistoryd.service
I had, in the BAD state:
[root@Jolla nemo]# pkcon search name commh
[...]
Installed all-translations-pack-0.0.34-10.4.5.jolla.noarch Collection of all translations in one binary rpm
Installed commhistory-daemon-0.7.3-1.38.1.armv7hl Communications event history database daemon
Installed libcommhistory-qt5-1.9.7.1-1.30.1.armv7hl Communications event history database API
Installed libcommhistory-qt5-declarative-1.9.7.1-1.30.1.armv7hl QML plugin for libcommhistory
Installed libcommhistory-qt5-tools-1.9.7.1-1.30.1.armv7hl Command line tools for libcommhistory
[...non-installed packages trimmed...]
After running pkcon install commhistoryd:
[root@Jolla nemo]# pkcon search name commh
[...]
Installed all-translations-pack-0.0.34-10.4.5.jolla.noarch Collection of all translations in one binary rpm
Installed commhistory-daemon-0.7.3-1.38.1.armv7hl Communications event history database daemon
Installed libcommhistory-qt5-1.9.7.1-1.30.1.armv7hl Communications event history database API
Installed libcommhistory-qt5-declarative-1.9.7.1-1.30.1.armv7hl QML plugin for libcommhistory
Installed libcommhistory-qt5-tools-1.9.7.1-1.30.1.armv7hl Command line tools for libcommhistory
...so no changes in version numbers.
Thank you for your report.
What version of commhistory-daemon do you have installed? (
devel-su -p pkcon get-details commhistory-daemon)Can you get the following log:
devel-su journalctl -b | grep ofonoand send it to chris dot adams at jolla dot com and I will forward it onto our messaging experts for analysis.Cheers, Chris.
chris.adams ( 2015-10-23 07:30:18 +0300 )editI had the same problems when running 1.1.9.28. Usually, retrying much later or rebooting would make the SMS being sent. And further, I had serious problems sending, and sometimes receiving MMS, don't know if related to SMS though. I have just updated to 2.0.0.10, so I will have to investigate if the problem is still there or not. Currently I have
nick75 ( 2015-10-23 08:56:23 +0300 )editcommhistory-deamon-0.7.3-1.38.1.armv7hlinstalled.Thanks Chris, I sent you the info. Meanwhie I'm considering upgrading to the next sailfish version. Or you think it shoud not matter?
JayBeRayBearGun ( 2015-10-24 00:31:16 +0300 )editHi Chris, seems like it is nog just SMS but all messaging stuff. Sending works receiving not. I guess the commhistory.db is damaged right?
JayBeRayBearGun ( 2015-10-24 23:21:55 +0300 )editJust noticed that making "Messages" backups fails. Seems to me a clear indication :)
JayBeRayBearGun ( 2015-10-25 00:49:39 +0300 )edit