Plasma-Firewall "Disconnects" from the Backend on Use #191
Labels
bug-priority-3
Medium priority bug. Noticeable impact, some functionality affected.
upstream-bug
Issues that are determined to not be caused by our configuration.
Issue Description
Describe the bug
Plasma Firewall displays an error when editing rules.
Steps to reproduce the bug
Expected behavior
Plasma Firewall successfully edits rules.
Screenshots
Additional context
Launching the KCM from the terminal displays the following relevant message:
This message appears despite
ufw
being enabled and active.This issue is an upstream bug reported at the KDE Bug Tracker.
Additionally, there's this other message:
ufw.client: SystemdJob Error: 100 "The name org.freedesktop.systemd1 was not provided by any .service files"
This indicates that the KCM tries to interact with the service unit to do something, such as maybe reloading the service after editing a rule. This interaction of the KCM with systemd will fail in Nitrux since systemd is not present in the distribution. This explains that to the KCM, the "engine," i.e., ufw, is "disconnected" since it's waiting for the service's status.
OS version and Desktop information
Operating System: Nitrux 3.7.0 build.300924.ub
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.10.12-1-liquorix-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 7900X3D 12-Core Processor
Memory: 61.8 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 XTX
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B650M AORUS ELITE AX
Disclaimer: Please report issues to the appropriate developer(s). Nitrux is a Linux distribution that comprises dozens of free and open-source software projects.
The text was updated successfully, but these errors were encountered: