the service check is racy, KLockFile is as not (assuming the combination of
O_EXCL and O_CREAT is not racy which is not KLockFile's responsibility)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
cleaning up the mess, everything but KNotificationConfigWidget is
implemented.
not only does it not require additional D-Bus service (knotify) to
function but also does not transmit pixmaps over D-Bus, the features
to execute command or log to file are dropped and will not be
implemented.
also about markup support in notifications - if the server does not
support markup then it is supposed to strip it, see the spec:
https://specifications.freedesktop.org/notification-spec/notification-spec-latest.html#backwards-compat
meaning nothing should be done by KNotification itself because it is not
a server, it is just a proxy.
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
that way the UI will not freeze while the method is executed, beware
signals and slots if you connect it to one (or even more) tho
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
dead-lock may happen if QStandardPaths (which KStandardDirs uses and
thus KDebug indirectly) warns about something
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
