Opensnitch no longer starts on my machine #1214
Comments
|
Can you check the logs and status of the service? Service: Logs: Maybe something of note comes up. If you need more context on the second command, use |
|
hey @SeaDude , could you provide the info suggested by @CPioGH2002 ? More tests that can be useful to troubleshoot this issue:
I tested it on an up-to-date ubuntu 22.04 machine and works fine. |
Apologies for the long wait... Service logs: Logs: |
|
FYI, still passes all checks but won't start. |
|
After setting LogLevel to 0 and restarting the service: |
|
Not saying that I'm an expert but, to me, it looks like the service does ok but the (Python-based) UI app does not in your case. Besides, the version should be at 1.6.6 since a while, so perhaps consider updating, just in case: https://github.com/evilsocket/opensnitch/releases |
|
ah I see @SeaDude , the problem is this: This is a known issue https://github.com/evilsocket/opensnitch/wiki/GUI-known-problems The temporal solution is to downgrade python3-protobuf: One solution could be distributing two protobuffers compiled with different versions, to support old and new python3-grpcio versions. |
|
@gustavo-iniguez-goya ...there is no |
|
Man, I really liked the piece of mind that opensnitch provided me. I felt protected. When the UI stopped suddenly yet running I'll sponsor you for what I can, for all the hard work you've done and check back in the future. Thank you |
|
I'm really sorry to hear this @SeaDude . I'm working on a solution for this case. We'll see if it works. |
|
Quick update on what's going on here. tl;dr: There're two problems in Ubuntu 22.x:
The solution I'm testing that solves the second problem is to distribute 2 protobuffers instead of 1 (it should help for future incompatibilities):
The first problem with Regarding the error you have reported in this issue, it seems that somehow your system now has You can check it with: |
|
Hi, sorry to comment on a closed issue. I also have this aids. I try all the pip install 'no dont do that it break everything' ok apt install python3-blah pip3 cartwheel go python3 hail mary venv python3.11 == version song and dance but now I only want to smash the monitor. Is there a fix merge? I also try to build clone but same problems |
|
hey @netstat-peanut , It's really unfortunate that you've run into this problem. Could you tell us more info about your system?
Remember that sometimes is ok to smash the monitor ;) |
|
@gustavo-iniguez-goya requested informations here:
i try 101 things to fix this before so i dont know which gets these grpcio or protobuf versions |
|
@netstat-peanut , your issue seems different than this one. Would you mind opening a new issue, or better, a new discussion https://github.com/evilsocket/opensnitch/discussions/new?category=general ? Please, describe in detail the problem like I'm 5. Post also the Desktop Environment you're using. And some general questions:
|
|
@gustavo-iniguez-goya it is a protobuf error no? its ok i will uninstall and wait for working version. sorry for bother here |
|
No, that's a daemon error. It can happen for example when there's a popup asking to take action on a connection. Version v1.6.6 should work fine, we haven't received issues saying otherwise. |
Protobuffers compiled with protobuf < 3.20.0 are incompatible with protobuf >= 4.0.0: https://github.com/evilsocket/opensnitch/wiki/GUI-known-problems#gui-does-not-show-up This has been a source of problems for some users (#1214, #647), and in some distributions, previous protobuffer does no longer work due to incompatibility with the protobuf package version installed (OpenSuse Tumbleweed). So in order to solve this issue, we provide several protobuffers, for old and new protobuf versions: proto/ui_pb2* for protobuf >= 4.0.0 proto/pre3200/ui_pb2* for protobuf >= 3.6.0 and < 3.20.0 To avoid import errors, each protobuffer must be placed in its own directory, and the name of the protobuffer files must be named with the syntax <prefix>_pb2.py/<prefix>_pb2_grpc.py: ui_pb2.py and ui_pb2_grpc.py The default compiled protobuffer will be opensnitch/proto/ui_*.py instead of opensnitch/ui_*.py
Protobuffers compiled with protobuf < 3.20.0 are incompatible with protobuf >= 4.0.0: https://github.com/evilsocket/opensnitch/wiki/GUI-known-problems#gui-does-not-show-up This has been a source of problems for some users (#1214, #647), and in some distributions, previous protobuffer does no longer work due to incompatibility with the protobuf package version installed (OpenSuse Tumbleweed). So in order to solve this issue, we provide several protobuffers, for old and new protobuf versions: proto/ui_pb2* for protobuf >= 4.0.0 proto/pre3200/ui_pb2* for protobuf >= 3.6.0 and < 3.20.0 To avoid import errors, each protobuffer must be placed in its own directory, and the name of the protobuffer files must be named with the syntax <prefix>_pb2.py/<prefix>_pb2_grpc.py: ui_pb2.py and ui_pb2_grpc.py The default compiled protobuffer will be opensnitch/proto/ui_*.py instead of opensnitch/ui_*.py
Describe the bug
Opensnitch doesn't start anymore.
Include the following information:
Linux system9 6.9.3-76060903-generic #202405300957~1721174657~22.04~abb7c06~dev-Ubuntu SMP PREEMPT_DY x86_64 x86_64 x86_64 GNU/LinuxTo Reproduce
Opensnitch doesn't start by default anymore.
If the daemon doesn't start or doesn't intercept connections:
opensnitchd -check-requirementsto see if your kernel is compatible.The text was updated successfully, but these errors were encountered: