After update Plasma to 5.12.1 on Manjaro KDE Edition the plasmashell crashes when I click menu or taskbar. When I run plasmashell from terminal I get a lot of that message: "KActivities: FATAL ERROR: Failed to contact the activity manager daemon" Unfortunately on Manjaro there is no debug symbols so I am not able to produce usable bt. I will try to compile plasmashell myself. (gdb) bt #0 0x00007ffff138a860 in raise () at /usr/lib/libc.so.6 #1 0x00007ffff138bec9 in abort () at /usr/lib/libc.so.6 #2 0x00007ffff1b2d8c8 in () at /usr/lib/libQt5Core.so.5 #3 0x00007fff3c0a6227 in () at /usr/lib/libKF5ActivitiesStats.so.1 #4 0x00007fff3c089d84 in KActivities::Stats::ResultSet::ResultSet(KActivities::Stats::Query) () at /usr/lib/libKF5ActivitiesStats.so.1 #5 0x00007fff3c36cd50 in () at /usr/lib/qt/qml/org/kde/plasma/private/kicker/libkickerplugin.so #6 0x00007fff3c366a2b in () at /usr/lib/qt/qml/org/kde/plasma/private/kicker/libkickerplugin.so #7 0x00007fff3c39b98a in () at /usr/lib/qt/qml/org/kde/plasma/private/kicker/libkickerplugin.so #8 0x00007fff3c39e510 in () at /usr/lib/qt/qml/org/kde/plasma/private/kicker/libkickerplugin.so #9 0x00007ffff4cfc6ba in () at /usr/lib/libQt5Qml.so.5 #10 0x00007ffff4c755c6 in () at /usr/lib/libQt5Qml.so.5 #11 0x00007ffff4c76d3f in () at /usr/lib/libQt5Qml.so.5 #12 0x00007ffff4c778ea in QV4::QObjectMethod::callInternal(QV4::CallData*, QV4::Scope&) const () at /usr/lib/libQt5Qml.so.5 #13 0x00007ffff4c90afb in QV4::Runtime::method_callProperty(QV4::ExecutionEngine*, int, QV4::CallData*) () at /usr/lib/libQt5Qml.so.5 #14 0x00007fff3cff67ea in () #15 0x00007fffffff178a in () #16 0x0003800000000000 in () #17 0x00007fffffff1794 in () #18 0x0003400000000001 in () #19 0x0000000000000000 in ()
Created attachment 110840 [details] ksysguard screenshot Something is wrong with kactivitymanagerd - in ksysguard I can see a lot of kactivitymanagerd processes.
When I run manually kactivitymanagerd: Config timer connecting... Setting the name of 0x55c52c9b93e0 to "org.kde.ActivityManager.ActivityTemplates" Setting the name of 0x55c52c9b92f0 to "org.kde.ActivityManager.RunApplication" Setting the name of 0x55c52c9c8d50 to "org.kde.ActivityManager.Resources.Scoring" Creating directory: "/home/kamil/.local/share/kactivitymanagerd/resources/" SQL: error: QSqlError("11", "Nie można wykonać polecenia", "database disk image is malformed") query: "PRAGMA synchronous = 1" SQL: error: QSqlError("11", "Nie można wykonać polecenia", "database disk image is malformed") query: "PRAGMA journal_mode = WAL" KActivities: Database can not be opened in WAL mode. Check the SQLite version (required >3.7.0). And whether your filesystem supports shared memory Service started, version: Cleaning up...
I compiled plasma-desktop and kactivities-stats and have this: (gdb) bt #0 0x00007ffff118d860 in raise () at /usr/lib/libc.so.6 #1 0x00007ffff118eec9 in abort () at /usr/lib/libc.so.6 #2 0x00007ffff19308c8 in () at /usr/lib/libQt5Core.so.5 #3 0x00007fff3615c760 in Common::Database::instance(Common::Database::Source, Common::Database::OpenMode) (source=source@entry=Common::Database::ResourcesDatabase, openMode=openMode@entry=Common::Database::ReadOnly) at /home/kamil/pkg/kactivities-stats/src/kactivities-stats-5.43.0/src/common/database/Database.cpp:205 #4 0x00007fff3613f774 in KActivities::Stats::ResultSet::ResultSet(KActivities::Stats::Query) (this=0x7fffffff0b28, query=...) at /home/kamil/pkg/kactivities-stats/src/kactivities-stats-5.43.0/src/resultset.cpp:479 #5 0x00007fff363b0fc8 in KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString) (this=0x555555bec3c0, parent=<optimized out>, clientId=...) at /home/kamil/pkg/plasma-desktop/src/plasma-desktop-5.12.1/applets/kicker/plugin/kastatsfavoritesmodel.cpp:229 #6 0x00007fff363ab16b in KAStatsFavoritesModel::initForClient(QString const&) (this=0x55555899ee80, clientId=...) at /home/kamil/pkg/plasma-desktop/src/plasma-desktop-5.12.1/applets/kicker/plugin/kastatsfavoritesmodel.cpp:488 #7 0x00007fff363dca3a in KAStatsFavoritesModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0x55555899ee80, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=16, _a=_a@entry=0x7fffffff0e70) at /home/kamil/pkg/plasma-desktop/src/build/applets/kicker/kickerplugin_autogen/7RBZBFH7CH/moc_kastatsfavoritesmodel.cpp:182 #8 0x00007fff363de275 in KAStatsFavoritesModel::qt_metacall(QMetaObject::Call, int, void**) (this=0x55555899ee80, _c=QMetaObject::InvokeMetaMethod, _id=16, _a=0x7fffffff0e70) at /home/kamil/pkg/plasma-desktop/src/build/applets/kicker/kickerplugin_autogen/7RBZBFH7CH/moc_kastatsfavoritesmodel.cpp:264 #9 0x00007ffff4aff6ba in () at /usr/lib/libQt5Qml.so.5 #10 0x00007ffff4a785c6 in () at /usr/lib/libQt5Qml.so.5 #11 0x00007ffff4a79d3f in () at /usr/lib/libQt5Qml.so.5 #12 0x00007ffff4a7a8ea in QV4::QObjectMethod::callInternal(QV4::CallData*, QV4::Scope&) const () at /usr/lib/libQt5Qml.so.5 ---Type <return> to continue, or q <return> to quit--- #13 0x00007ffff4a93afb in QV4::Runtime::method_callProperty(QV4::ExecutionEngine*, int, QV4::CallData*) () at /usr/lib/libQt5Qml.so.5 #14 0x00007fffd01757ea in () #15 0x00007fffffff137a in () #16 0x0003800000000000 in () #17 0x00007fffffff1384 in () #18 0x0003400000000001 in () #19 0x0000000000000000 in ()
I have looked at source code and I see that the crash started because of that: kactivities-stats-5.43.0/src/common/database/Database.cpp:205 if (walResult != "wal") { qFatal("KActivities: Database can not be opened in WAL mode. Check the " "SQLite version (required >3.7.0). And whether your filesystem " "supports shared memory"); } I think that error in database shouldn't make plasmashell crash.
I've created patch for crash: https://phabricator.kde.org/D10691
I have the same problem like in post 1 but kactivitymanagerd seems to start without an issue: "Message recipient disconnected from message bus without replying" Service started, version: Cleaning up... Nonetheless, plasmashell prints this line every half second: KActivities: FATAL ERROR: Failed to contact the activity manager daemon
@Maximilian Can you do kactivitymanagerd start-daemon from the terminal?
Yes, I can start "kactivitymanagerd start-daemon" but don’t get any return. Now, I have just renamed ~/.local/share/kactivitymanagerd/resources which fixed this problem for me. Kickoff favorites are lost but this is no big deal. The mount plasmoid opens a dialog window "Fehler – KIO-Client: Unzulässige Adresse (URL): [here it stops]" (Error – KIO-Client: Inadmissible address (URL):") when I mount one specific HDD, but works on second try. Might this be an effect of deleting the resources folder or is this unrelated?
Forgot to say that you should kill kactivitymanagerd before starting with 'start-daemon'. Anyhow, the solution to this will be two-step: 1. KActivity* libraries will have to provide dummy implementations instead of asserting on database error 2. KActivityManagerD will need to backup the important parts of the database from time to time to be able to restore when the db gets corrupted
p.s. The mount plasmoid should have nothing to do with this
Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!