gui: DesktopNotifications not available (python3-notify2 installed)

[slynobody]

Describe the bug
after the last update opensnitch-ui needs 1-2 minutes to start, giving the above output: seemingly 'python3-notify2' should be installed – and it is. no pip3 / pipx-install (debian-packages, python3-minimal installed incl. dependencies). Downgraded dbus / rebooted, no changes.
Error does only occur on an amd-machine, maybe dbus-security-measures / hardening there could intervene? where to look exactly?

• OpenSnitch 1.6.1
• OS: Debian
• Version: trixie
• Window Manager: KDE
• Kernel version: 6.5

Post error logs:
~ OpenSnitch GUI - 1.6.1 ~
protobuf: 4.21.12 - grpc: 1.51.1

gRPC Max Message Length: 4MiB
Bytes: 4194304
is new file, or IN MEMORY, setting initial schema version
setting schema version to: 2
setting schema version to: 2
schema version: 2
db schema is up to date
Loading translations: /usr/lib/python3/dist-packages/opensnitch/utils/../i18n locale: de_DE
DesktopNotifications not available (install python3-notify2): org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
using IPASN DB: /usr/lib/python3/dist-packages/data/ipasn_20140513_v12.dat.gz
DesktopNotifications not available (install python3-notify2): org.freedesktop.DBus.Error.ServiceUnknown: Could not activate remote peer: unit failed.
Using server address: unix:///tmp/osui.sock
new node connected, listening for client responses... /local
[Nodes]: reply notification not in the list: 0

Expected behavior (optional)
gui should start directly.

[gustavo-iniguez-goya]

Hi @slynobody ,

There have been a lot of python3 updates lately on Sid (July + August), maybe it has affected somehow.

See if you have the python3-notify2 package under /usr/lib/python3*:

~ $ find /usr/lib/python* -name 'notify2.py'
~ $ dpkg -L python3-notify2

And your python version: python3 --version

On the other hand, we didn't change the notifications module from v1.6.0 to v1.6.1: v1.6.0...v1.6.1

There was only 1 commit to receive notifications from the firewall changes, but the notifs module itself was not changed.

This change though, could explain the delay starting up, I've also seen it sometimes, but I haven't had time to debug it.

org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

I haven't seen this error before, but I'll try to run the GUI on Sid to see if I can reproduce it.

[slynobody]

thank you for your help. notify2 is installed and found. this was not the issue.

opensnitch 1.6.1+ seems to have introduced a new dependecy for working on kde directly after starting it: strangely notifications have to be set to any other option than 'off' as well as 'notification-daemon' must be installed and running.
i removed notifications as well as according services a while back while removing other unneeded system-services. strangely qt-notifications do not show up at all while system-notifications do now. so i would second 'qt6' on the wishlist (as well as some 'dont think about it'-automated-way (user-friendlyness) to the great feature 'ssl-cert'-communication you thankfully introduced lately (that to my knowledge littlesnitch does not have, right?) - keep up the great work!

[luzpaz]

any progress here?

[gustavo-iniguez-goya]

not yet @luzpaz , I need to reproduce the problem. Do you experience the same behaviour?

[Stocktradesoft]

No GUI ~ OpenSnitch GUI - 1.6.5.1 ~
protobuf: 3.12.4 - grpc: 1.30.2
OS Lubuntu 22.04