Created attachment 151875 [details] Screenshot of Error SUMMARY When attempting to add rules with UFW installed (and enabled) via plasma-firewall, attempting to use advanced settings after using a simple-setting rule throws an error message to restart plasma-firewall because it "disconnected" from the backend. However, restarting neither plasma-firewall nor UFW fixes this issue, effectively breaking the application and rendering it useless. This is an old issue for me; I'm not 100% sure if this is the only way to trigger it, because I encounter this issue *every time* I've *ever* used plasma-firewall since release, but this is pretty much all I did besides trying to edit a newly created rule because it was mis-labeled. STEPS TO REPRODUCE 1. Start the UFW service and daemon-reload, if necessary 2. Open systemsettings 3. Go to Firewall 4. Enable the firewall, if not already enabled 5. Add a new rule (in this example, just add Minecraft from the "simple" menu and permit incoming traffic for it) 6. Add a new rule for SSH (actually select it in the "simple" menu first) and select any destination port in the advanced menu (this should probably work) 7. See that it labeled this new rule as "Minecraft" for some reason 8. Attempt to edit this rule and change its application name back to SSH and click apply 9. A "backend" error occurs and new rules aren't able to be created OBSERVED RESULT An error occurs that prevents editing and adding rules to the firewall list EXPECTED RESULT Plasma-firewall shouldn't throw errors when editing existing rules nor prevent new rules from being created SOFTWARE/OS VERSIONS Linux: Arch Linux x86_64 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION N/A
I got this error, too, while adding some rule without using the application list. However, restart plasma firewall seems to have fixed the issue for me. OS: KDE Neon User (based on Ubuntu 22.04 LTS, Jammy Jellyfish) Plasma Version: 5.26.2 Kernel: 5.15.0-52 generic 64bit UFW version: 0.36.1-4build1
thebluequasar@mailo.com, can you build and test this patch https://invent.kde.org/plasma/plasma-firewall/-/merge_requests/55?
Fixed by the commits in https://invent.kde.org/plasma/plasma-firewall/-/merge_requests/55, written by Lucas Biaggi!
@Nate Graham this is still apparently an issue (plasma-firewall 5.27.6) Adding a rule doesn't necessarily cause the disconnect now, but enabling logging via the interface does also still trigger these odd disconnects (something I couldn't really check at that time because the issue was more severe then than it is now)
I also see this with Plasma Firewall 5.27.5-2 on Devuan Ceres.
The same happens on three computers with MX Linux 23.4 KDE, one of which is freshly installed.
(In reply to nutzloserwerbemuell from comment #6) > The same happens on three computers with MX Linux 23.4 KDE, one of which is > freshly installed. Edit - just forgot: it happens with any rule there, not only with advanced rules. System info is: Operating System: MX Linux 23 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-28-amd64 (64-bit) Graphics Platform: X11
It does not work on MX and Devuan because the plasma config now relies heavily on systemd. @Lucas: if there is no support for non-systemd systems, please just disable that dialog entirely on such systems. Its better to use the CLI (can't help but observed I used UI firewall tools 20 years ago on linux and they worked fine... I will never understand why this mess is needed.)
Hi - I can't reproduce this issue on a Kubuntu 25.04 device (Plasma 6.3.4), which uses ufw as a firewall. Could a reporter here please check if this issue remains on your device with an updated Plasma installation? Thanks!
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
It still fails on 6.3.4. Also please read before reporting worksforme: it is clearly mentioned that it does not work on systemd-free systems.