gustavo-iniguez-goya
commented
3 years ago hey @sylkat
The display managers don't start if the opensnitch daemon is up, which is happening at least on my Debian system.
I haven't ran into this problem (yet).
The system will hang without showing the display manager.
Can you reproduce this problem again and post the output of journalctl -ar --since=today? .
Also set the log level to DEBUG (preferences -> nodes -> defult log level), and post the log /var/log/opensnitchd.log
I guess that the daemon DefaultAction is allow in /etc/opensnitchd/default-action.json.
In any of those environments the coming back to the Display Manager either ligthdm or sddm will give us a hang login screen again due to the impossibility to kill the ui process:
I'm aware of this problem on KDE, but in my case it only prevents to reboot the system the first time you click on logout/shutdown/reboot. If I click again then it exits as expected.
Hi, First of all, congrats for the great app i believe is so useful for some scenarios.
The display managers don't start if the opensnitch daemon is up, which is happening at least on my Debian system. I've tried different dm as sddm, ligthdm, all of them refused to start.
To reproduce this bug i just had to install the last release package of debian:
opensnitch_1.3.0-1_amd64.deb
And enabling it with:
systemctl enable opensnitchThe system will hang without showing the display manager.
Once fixed that, i have some other issues with the display managers logout.
I see that starting the opensnitch service after the Display Service i can bypass this issue and start these Desktop Managers:
These are the ones that i have and all are working well until the logout happens.
In any of those environments the coming back to the Display Manager either ligthdm or sddm will give us a hang login screen again due to the impossibility to kill the ui process:
/usr/bin/python3 /usr/bin/opensnitch-uiI saw a process trying to kill the ui, not sure if is due to the window manager logout or the ui code try to catch the signal or the daemon, i didn't see the code deeply and i prefer to ask before going to it, was something like:
pkill -15 PID;opensnitch-uiLooks like a window manager way to kill their own started apps, but not sure at all due to the last 'opensnitch-ui' command after the ";"
All of them kde plasma, xfce4 and cinammon didn't leave the session cleanly due to this process still there, very strange, but this happens to me.
So kill the process will let the Display Manager go the login screen again.
Sddm has not a feature to launch scripts as root when the login session starts or logout, but ligthdm does and is easy to add some fixing for this bug in my environment...but could be nice to see whats going and why the daemon interferes with them.
So creating a start script of session, starting the service will fix the log in issue after a logout.
And creating a second script when the logout session, stopping the service and killing the ui will fix the return back to the Display Manager login screen.
All this worked for xfce4 and cinammon, Plasma refuse to log in after one logout, with daemon started or not, it keeps that environment not accessible until a restart of the box, ive tried to:
Even doing all of that, was for me impossible to start again a Plasma session once i did a logout from it, only a reboot made me log in again to plasma.