In T8408#237431, @brenthuisman wrote:

@knauss Did any development occur? On NLNet I see the project is still at 'Open' status.

Thanks for the patch from first glance it looks fine. @dvratil - fine to merge?

@ngraham: this is a feature for the weekly report. What is the proposed way to ping you for things to blog about?

In D29030#665411, @lukaskaras wrote:

• kcrash and drkonqi - this only happens, if Akonadi crashes and it does not crash for me yet - fully accepted

You may try to abort akonadi server by command:

killall -s ABRT akonadiserver

it should trigger Dr Konqi for your akonadiserver process

In D29416#665213, @winterz wrote:

Ideally "German (German) - Feiertage fur Deutschland (Bayern)" would become tr("Germany/Berlin (German)")?
I don't think we need to see "Feiertage fur Deutschland"

Seems fine. But this should get a testcase. Unfortuantelly there is more to do to create one (src/autotests/kmcommandstest.cpp) Do you need/want help with that?

Thanks dvratil and lukaskaras for explaining me how to debug Akonadi - I haven't done it yet. Btw. is there documentation existing for this?

Can you explain me how you get strace output for akonadi?

Build dependencies of Frameworks in 5.69 (additionally with porting aids):

Okay I want to verify on my system first. I may find time to do this next week.

Me get funding from nlnet to work on this. The rough ETA is to finish this in June.

Wait you add mysql stuff to the akonadiserver, that is totally wrong! The problem is that the mysql-akonadi script is not triggering the correct profile. The workaround with mysql-akonadi script was added because mysql start shipping AppArmor and Kubuntu/Debian mainatiners at that time created this script to make sure to workaround the AppArmor of mysql. Because this was triggering issues for Debian unstable I set down and started to do a proper AppArmor profile for Akonadi and there I learnt, that the mysql-akonadi script is not needed at all.

In D28903#654405, @dvratil wrote:

The patch still correct, though. The assumption that the process is always called simply mysqld is wrong.

In D28915#653566, @junghans wrote:

I just applied for a developer account. Once approved and got access to the kldap repository, I'll commit the changes. If things do not work this way, you can commit the changes too.

@lukaskaras: this whole foo with mysqld-akonadi is not needed anymore. Me as the maintainer of Debian packages I investigate the situation and found this proper solution with AppArmor rules, so I could removed the mysqld-akonadi workaround.

This dbus feature was added with newer AppArmor versions - I havn't heard about it until today ;) But this makes totally sense that also DBus access it controlled.

Released with KDE Pim 19.12.

Released with KDE Pim 19.12.

Released with KDE Pim 19.12.

cleanup tests.

cleanup - do cast only one time.

cleanup.

cleanup.

fixed raised issues.

it is now ready for review.

Add a job chain test.

In D28495#641098, @andreylegayev wrote:

I'll try to request it via page "Apply for a Developer Account".

cleanup.

cleanup.

Upload the new patch ;)

Address laurents comments and improve the test a little bit.

Address laurent's comments.

@andreylegayev - as this seems your first patch to KDE via Phabrictor and this got accepted, the next step is to push your change to the git repostory.
Do you have a developer account to push your changes to our git repository yourself? If others need to do this, we need your name and email address for the git commit, as Phabrictor often does not give us these information.

Can't https://doc.qt.io/qt-5/qtglobal.html#qSetMessagePattern used? If Kleopatra using "normal" qtlogging you can easily test if you set the environmental variable QT_MESSAGE_PATTERN to print timestamps something like:
QT_MESSAGE_PATTERN="[%{time yyyyMMdd h:mm:ss.zzz t} - %{if-category}%{category}: %{endif} - %{file}:%{line} - %{message}