https://bugs.kde.org/show_bug.cgi?id=447385
Bug ID: 447385
Summary: After KDE connect starts, calling
org.freedesktop.Notifications.Notify returns incorrect
ids when replaceId=0, making replacing notifications
impossible
Product: kdeconnect
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: common
Assignee: albertv...@gmail.com
Reporter: bals...@balsoft.ru
Target Milestone: ---
SUMMARY
When KDE connect (the sendnotifications plugin specifically) starts,
calling the `Notify` method on `org.freedesktop.Notifications` with
`replace_id == 0` returns incorrect ids. From my understanding, these
IDs are KDE Connect's internal ids assigned to notifications, and not
the notification manager's IDs. With more spec-relaxed servers, such
as Dunst, it is a lot less annoying since they just allow us to use
KDE Connect's internal notification IDs.
With spec-strict servers (like Mako), this makes it almost impossible
to replace notifications, since the IDs clients get from D-Bus are
useless.
STEPS TO REPRODUCE
1. Make sure you are running a notification manager which is strict about
notification IDs, e.g. Mako
2. `curl
https://raw.githubusercontent.com/vlevit/notify-send.sh/master/notify-send.sh >
notify-send; chmod +x notify-send`
3. Start kdeconnectd with sendnotifications plugin enabled, and connect to a
device (make sure that the sendnotifications plugin activates)
4. Run `./notify-send -R test test` repeatedly
OBSERVED RESULT
Multiple notifications appear, one for each `notify-send` invocation
EXPECTED RESULT
Only one notification appears (and gets updated on new notify-send invocations)
SOFTWARE/OS VERSIONS
NixOS GNU/Linux 21.11pre (nixpkgs 263ef4cc4146c9fab808085487438c625d4426a9)
Sway 1.6.1
Mako 1.6
kdeconnect 21.08.3
--
You are receiving this mail because:
You are watching all bug changes.
