evilsocket / evilsocket/opensnitch

gui: DesktopNotifications not available (python3-notify2 installed)

Open
#1,005 8 comments 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
14.1k
Forks
665
PR merge metrics
No merged PRs in 30d

Description

**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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.