Hey,
`QT_LOGGING_RULES="*.*=true;qt.*=false" akonadictl start`
^^ restart does not work here - killed it from a different terminal
with `akonadictl stop`
Is it possible to add a TIMESTAMP?
QT_MESSAGE_PATTERN="[%{time process} %{type}] %{appname} %{category} % {function} - %{message}" QT_LOGGING_RULES="..."
you have full control about the log format - see the documentation:
https://doc.qt.io/qt-6/qtlogging.html#qSetMessagePattern
btw. you can enable/disable different categories in QT_LOGGING_RULES. I use *.*=true to see everything. Most of the time, if I'm debugging KDEPIM stuff the issue is not inside qt, that's why I disable every qt category (qt.*=false).
As qt will log very much.
To see all different logging categories you can run kdebugsettings, you can also use it to modify the logging for your system. BUT ATTENTION: this can fill your log files very fast! That's why I suggest to use QT_LOGGING_RULES for debug exactly one call of a program, if needed.
regards,
hefee
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEOewRoCAWtykmSRoG462wCFBgVjYFAmcMJo8ACgkQ462wCFBg VjZfmA/7B3Ru/LKzR29Kx+ayd3Gf0k9WUX5dR5pl9XfnN/jNdX8wyznmYpGt02A/ iNkHp+MiYGNyg2aHWg2dVnAhn/X6oM0CAUvUOiu69Bc0UUIA8OxaDxIgX8JLb13R w7A1IXqzNmf9SOLSd2XrM9zLEzDBSEDXBx6Jhz1ejGboMGmX9XJXrQjk41Qz/Uo5 xyqjdI3MXXCBqxr4zcjmnluxKkqveXieUSlIUcZ+DTaHbX9YSGZk1Dw8GhGxyPBX 2LprmUYTJTtGBQuRGZ6JdQJ2CphHemGv8TtK3tihCMGbWl/0lhYmMU4q6qT3MG2r wVlp6psL5tZ1qQZETRkESvqTns/i/4Xji8nxNLy80YZOOwtYNdORF6ybjVzW+SUy jAW4ShX9PGRqXLL79pT75YiylrIKVzQTcGEJlNIu7vqqMEfffF8mrDv6BOfFYYEy euymfcOFIOMIq6jiQcggb3t5ez1p99KV+OY4RukNpHypj6yF49DR3uoW+Jv4oLUr nvOkOWG7+pX7GYyqOlRmEevZITZfZ4ahcLquaR3Q1ePgm0Y1SmHAyEHwPdfUw36F Mp0PW1Ab55OQZ8r1lq+KcCbqRSl0iTaFX6ZtQA1/ERl4jflMN7b//siNlXnX8hw8 XAnR9G1lMuCyER2juQ2e/CbTqg+GY7ckgYkjrVZVzIi4Igt1rTQ=
=Oe4E
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)