https://bugs.kde.org/show_bug.cgi?id=388287
--- Comment #8 from Tony <jodr...@live.com> ---
(In reply to Ivan Čukić from comment #6)
> Sorry, I wasn't precise. If QMessageLogger::fatal was called, it should have
> written the message passed to the fatal function to the stderr.
>
> Can you just execute
> kactivitymanagerd
> in console and report its output?
Running it, kactivitymanagerd, shows not error, it says its already running.
Stopping it, "kactivitymanagerd stop" and running it again shows:
joder@linux-7q70:~> kactivitymanagerd
Config timer connecting...
Setting the name of 0x561592ae0db0 to
"org.kde.ActivityManager.Resources.Scoring"
Creating directory: "/home/joder/.local/share/kactivitymanagerd/resources/"
KActivities: Database connection:
"kactivities_db_resources_140138526054592_readwrite"
query_only: QVariant(qlonglong, 0)
journal_mode: QVariant(QString, "wal")
wal_autocheckpoint: QVariant(qlonglong, 100)
synchronous: QVariant(qlonglong, 1)
Setting the name of 0x561592b2c7b0 to
"org.kde.ActivityManager.ActivityTemplates"
Setting the name of 0x561592b2fe40 to
"org.kde.ActivityManager.RunApplication"
Service started, version: 7.0.0
Cleaning up...
--
You are receiving this mail because:
You are watching all bug changes.
