This affects any apps that uses notifications (like Dino shows that in the logs, and notify-send just shows it and refuses to send the notification)
How do I troubleshoot it?
Haiku does not use a message bus or notify-send. The way to send notifications in Haiku is this api: The Haiku Book: BNotification Class Reference
Then - why do notify-send exist in the first place? Why isn’t it (or whatever backend it uses - probably dbus) modified to use BNotification in the first place?
These probably came from haikuports, they are not from Haiku itself. You can verify this by checking the attributes of the file.
Something like “catatrr $(command -v notify-send) SYS:PACKAGE_FILE”
Note that I’m not sure that’s the right attribute name so you might have to use listattr first 
Looking at Haikuports repo, it comes from libnotify (I’m not on Haiku rn - just looking at Haikuports to assume)
I’ve checked issues, and I see no reports of libnotify being broken. It’s really weird for a port of a library for sending notifications to exist, if it was never tested to begin with. It’s definitely something on my end, or Haiku’s updates causing it.
Well some ports are just here to please other ports. For example, Haiku doesn’t use dbus but, some package needs it to be installed. So the port does the minimum to please apps and otherwise it is not really functional. I suspect that it is the same thing for libnotify, it probably just please Gtk apps and relay information to the actual lib but is not meant to be use directly.
2 Likes
I don’t have a github acc so don’t really contribute to Haikuport, I guess this is ported because some apps expect this api, even if haiku does simply not provide a freedesktop conformant api :g
If you install the needed software from haikuports, it does. And you should get native notifications from it.
But Haiku “core” developers may be unable to help. Let’s wait for someone involved in maintaining this software stack to show up
1 Like