[Bug Report] UI frequently becomes unresponsive under Ubuntu 26.04

Aperta
#1,654 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
grpc, linux, python, ubuntu

Direzione di ricerca

Inizia dal punto di ingresso opensnitch-ui su Ubuntu 26.04/GNOME Wayland, riproducendo il problema con e senza --debug mentre raccogli l’avviso gRPC ripetuto di thread_pool.cc. Il lavoro è completato quando l’interfaccia utente rimane reattiva, continua a mostrare i popup delle connessioni bloccate e apre la finestra principale senza che l’avviso ricompaia.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
Describe the bug:

Sometimes, seemingly randomly as far as I can tell, opensnitch-ui will become unresponsive. That is, I will stop getting popups for blocked network connections, and clicking on the tray icon won't bring up the main window. When this happens, the following gets logged to my journal continuously until I kill it:
E0819 06:42:00.448313487 665408 thread_pool.cc:253] Waiting for thread pool to idle before forking
Just now, even killing and restarting opensnitch-ui didn't clear the issue. As soon as it launches, it starts outputting that same message, and clicking "Open main window" from the tray icon menu does nothing. This was happening repeatedly, so I launched it with --debug, and of course then it seemed to work perfectly. I'm sorry this isn't a whole lot to go on.

Include the following information:

  • OpenSnitch version: 1.8.0
  • OS: Ubuntu
  • OS version: 26.04
  • Window Manager: GNOME Shell 50 (Wayland)
  • Kernel version: 7.0.0-28
To Reproduce:

Non-deterministic, or at least I haven't been able to figure out a way to reproduce this yet.

Post error logs:
❯ QT_QPA_PLATFORMTHEME= opensnitch-ui
/usr/lib/python3/dist-packages/opensnitch/utils/themes/themes.py:118: SyntaxWarning: 'return' in a 'finally' block
  return themes
Loaded network aliases from /usr/lib/python3/dist-packages/opensnitch/utils/network_aliases/network_aliases.json
/usr/lib/python3/dist-packages/opensnitch/dialogs/stats.py:1131: SyntaxWarning: 'return' in a 'finally' block
  return True
/usr/lib/python3/dist-packages/opensnitch/dialogs/stats.py:1203: SyntaxWarning: 'return' in a 'finally' block
  return True
/usr/lib/python3/dist-packages/opensnitch/dialogs/stats.py:1317: SyntaxWarning: 'return' in a 'finally' block
  return True
/usr/lib/python3/dist-packages/opensnitch/dialogs/stats.py:1368: SyntaxWarning: 'return' in a 'finally' block
  return True
/usr/lib/python3/dist-packages/opensnitch/dialogs/stats.py:3514: SyntaxWarning: 'return' in a 'finally' block
  return qstr
qt.sql.qsqldatabase: QSqlDatabase requires a QCoreApplication
qt.sql.qsqldatabase: QSqlDatabase requires a QCoreApplication
qt.sql.qsqldatabase: QSqlDatabase requires a QCoreApplication
qt.sql.qsqldatabase: QSqlDatabase requires a QCoreApplication
         ~ OpenSnitch GUI - 1.8.0 ~
        protobuf: 4.21.12 - grpc: 1.51.1
--------------------------------------------------

QT_AUTO_SCREEN_SCALE_FACTOR: True
QT_QPA_PLATFORM: wayland
Using theme: 8 dark_purple.xml inverted: False dark: True
gRPC Max Message Length: 4MiB
                  Bytes: 4194304
[server] addr: unix:///tmp/osui.sock
is new file, or IN MEMORY, setting initial schema version
setting schema version to: 3
setting schema version to: 3
Setting journal_mode:  OFF
Setting DB memory optimizations
schema version: 3
db schema is up to date
actions.__init__ exception: [Errno 17] File exists: '/home/hackel/.config//opensnitch/actions/'
actions.__init__ exception: [Errno 17] File exists: '/home/hackel/.config//opensnitch/actions/'
Loading translations: /usr/lib/python3/dist-packages/opensnitch/utils/../i18n locale: en_GB
using IPASN DB: /usr/lib/python3/dist-packages/data/ipasn_20140513_v12.dat.gz
actions.__init__ exception: [Errno 17] File exists: '/home/hackel/.config//opensnitch/actions/'
is new file, or IN MEMORY, setting initial schema version
setting schema version to: 3
setting schema version to: 3
Setting DB memory optimizations
schema version: 3
db schema is up to date
[server] using address: unix:///tmp/osui.sock auth type: simple
qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
2026-08-19 06:41:42.583870 [Subscribe] unix:
Setting daemon DefaultAction to: deny
2026-08-19 06:41:42.802160 [Notifications] channel started: unix:

new node connected, listening for client responses... /local
[Nodes]:   reply notification not in the list: 0
E0819 06:41:48.447525214  665408 thread_pool.cc:253]                   Waiting for thread pool to idle before forking
E0819 06:41:51.447767296  665408 thread_pool.cc:253]                   Waiting for thread pool to idle before forking
E0819 06:41:54.447931229  665408 thread_pool.cc:253]                   Waiting for thread pool to idle before forking
E0819 06:41:57.448177349  665408 thread_pool.cc:253]                   Waiting for thread pool to idle before forking
E0819 06:42:00.448313487  665408 thread_pool.cc:253]                   Waiting for thread pool to idle before forking
E0819 06:42:03.448504053  665408 thread_pool.cc:253]                   Waiting for thread pool to idle before forking
E0819 06:42:06.448685579  665408 thread_pool.cc:253]                   Waiting for thread pool to idle before forking
E0819 06:42:09.448891603  665408 thread_pool.cc:253]                   Waiting for thread pool to idle before forking
Expected behavior (optional):

opensnitch-ui continues to remain functional and responsive indefinitely.

Lingua principale
Python
Stelle
14.3k
Fork
689
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di evilsocket/opensnitch

Tutte le issue di evilsocket/opensnitch

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.