Closed aditiambadkar closed 3 years ago
Hello,
it looks like ubuntu's systemd problem. There's systemd-245.8-2.fc32.x86_64 on my Fedora system and it works. If the current code works with the latest systemd it is sufficient. If I'm correct and this is ubuntu only problem because of old systemd then it should be fixed in ubuntu downstream.
Yes, you are correct. After a lot of research even I came to the conclusion that it's a systemd version issue. USBGuard 0.7.8 works perfectly on Ubuntu 20.04 (systemd version 245 and in Ubuntu 18.04 systemd version is 237). Thank you for confirmation from your side.
I have installed USBGuard 0.7.8 on Ubuntu 18.04 using the following steps:
This is the output of
sudo systemctl status usbguard.service
If I stop the usbguard.service and start again this is the output:
After this, I restarted my Ubuntu and this was the output:
I also tried stop, restart and status:
I also tried setting
#DefaultStartLimitBurst=5
in the /etc/systemd/system.conf toDefaultStartLimitBurst=0
but the service still doesn't get active.This is my systemd version:
This is the output of
sudo systemd-analyze verify usbguard.service
This is the output of
sudo systemd-analyze syscall-filter
There is no @system-service present in systemd 237.
If I comment out the line
SystemCallFilter=@system-service
in the usbguard.service.in file and follow the same installation and configuration steps, the USBGuard works perfectly.I want to run USBGuard 0.7.8 on my Ubuntu 18.04 using systemd without removing the
SystemCallFilter=@system-service
.Please help me with the issue.