beeep icon indicating copy to clipboard operation
beeep copied to clipboard

Hanging on Notify

Open lordofscripts opened this issue 4 months ago • 5 comments

I am running the LXDE desktop on a Debian 13 installation.

I used your library and since it hangs on the call to notify, I noticed it never returns from calling dbus1() on notify1().

I saw it is using notify-send which is what I originally used. When invoking notify-send from a terminal window, it hangs there too.

lordofscripts avatar Aug 20 '25 19:08 lordofscripts

It is using notify-send only as a fallback when DBus fails for some reason. Anyway, if even notify-send doesn't work, it is not an issue here.

gen2brain avatar Aug 20 '25 19:08 gen2brain

The DBus didn't work either. So what needs to be set up or installed (and how) for this library to work?

lordofscripts avatar Aug 21 '25 01:08 lordofscripts

Every DE already comes with a notification daemon; there are many different ones, but they all implement this https://specifications.freedesktop.org/notification-spec/1.3/protocol.html. If you don't have one, you would get errors and not hang, so yours is somehow broken. Without any details from you, we can only guess. It is also out of the scope of this project.

gen2brain avatar Aug 22 '25 07:08 gen2brain

Apparently I needed to logout and then login again. Now notifications are working. Except the Notification icon is not shown even though I use a full path to the PNG file (100x100).

lordofscripts avatar Aug 27 '25 21:08 lordofscripts

beeep.Notify() accepts the icon parameter as type any. When I passed the filepath as a string parameter, the icon was not being displayed in the notification body. But when I loaded the icon data into memory (from the file path) and passed it as []byte then the icon was displayed in the body.

lordofscripts avatar Aug 28 '25 18:08 lordofscripts