Bug 458824 - Plasma-Firewall "Disconnects" from the Backend on Use
Summary: Plasma-Firewall "Disconnects" from the Backend on Use
Status: REOPENED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_firewall (show other bugs)
Version: 5.25.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-07 00:57 UTC by nekonexus
Modified: 2023-08-03 11:34 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.27


Attachments
Screenshot of Error (52.06 KB, image/png)
2022-09-07 00:57 UTC, nekonexus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description nekonexus 2022-09-07 00:57:49 UTC
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
Comment 1 thebluequasar 2022-11-12 10:14:48 UTC
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
Comment 2 Lucas Biaggi 2022-11-17 14:54:57 UTC
thebluequasar@mailo.com, can you build and test this patch https://invent.kde.org/plasma/plasma-firewall/-/merge_requests/55?
Comment 3 Nate Graham 2022-12-06 21:31:00 UTC
Fixed by the commits in https://invent.kde.org/plasma/plasma-firewall/-/merge_requests/55, written by Lucas Biaggi!
Comment 4 nekonexus 2023-06-25 22:46:19 UTC
@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)
Comment 5 Martin Steigerwald 2023-08-03 11:34:39 UTC
I also see this with Plasma Firewall 5.27.5-2 on Devuan Ceres.