Bugzilla – Bug 1094376
Last modified: 2018-05-23 15:30:04 UTC
Created attachment 771124 [details]
backtrace kactivitymanagerd crash
kactivitymanagerd always immediately crashes and restarts again, filling /var/lib/systemd/coredump if coredumps are enabled. A backtrace taken with "coredumpctl gdb /usr/bin/kactivitymanagerd" is attached.
$ rpm -qi kactivitymanagerd
Version : 5.12.5
Release : 1.1
Build Date : Di 08 Mai 2018 14:06:40 CEST
Distribution: openSUSE Tumbleweed
> "KActivities: Database can not be opened in WAL mode. Check the SQLite version (required >3.7.0). And whether your filesystem supports shared memory"
Your activities database is corrupted and cannot be opened. Delete ~/.local/share/kacivitymanagerd/ to recreate it from scratch.
(You will lose favorites though and the history of recently opened files/applications though, I think)
KDE Frameworks 5.46.0 (that already has been submitted to Factory and should appear in Tumbleweed soon) will fix that crash, but kactivitymanagerd will run in "read-only" mode then and not save anything.
The long-term upstream plan is to backup the database regularly and restore it in case of problems, AFAIK.
*** This bug has been marked as a duplicate of bug 1093567 ***
(In reply to Wolfgang Bauer from comment #1)
> KDE Frameworks 5.46.0 (that already has been submitted to Factory and should
> appear in Tumbleweed soon) will fix that crash, but kactivitymanagerd will
> run in "read-only" mode then and not save anything.
Sorry, that change/fix will be in Plasma/kactivitymanagerd 5.13.
* Sat May 19 2018 firstname.lastname@example.org
- Update to 5.12.90
* New feature release
* For more details please see:
- Changes since 5.12.5:
* Allowing KAMD to run without a database backend <=====