MX 23 KDE Firewall [Solved]

[~FLOW~]

Greetings my excellent friends,
I was trying to open the firewall to SAMBA .. but I get this error.

Screenshot_20230804_223540.png

I installed gufw and added from there the rulles. After, I see those rulles in Plasma Firewall.
But still from Plasma Firewall I can't add anything...is it just me ?

[dolphin_oracle]

Greetings my excellent friends,
I was trying to open the firewall to SAMBA .. but I get this error.
Screenshot_20230804_223540.png
I installed gufw and added from there the rulles. After, I see those rulles in Plasma Firewall.
But still from Plasma Firewall I can't add anything...is it just me ?

nope doesn't work unless you boot up via systemd

[~FLOW~]

Got it and test it.
Thank you !

[rambo919]

Greetings my excellent friends,
I was trying to open the firewall to SAMBA .. but I get this error.
Screenshot_20230804_223540.png
I installed gufw and added from there the rulles. After, I see those rulles in Plasma Firewall.
But still from Plasma Firewall I can't add anything...is it just me ?

nope doesn't work unless you boot up via systemd

OK but can you boot into systemd, change the settings and then reboot to init with them still working?

With this and the system monitor bug it seems that for KDE6 systemd is going to be mandatory....

[~FLOW~]

Unfortunately I don't know, I switched distros

[Eadwine Rose]

If you are no longer using MX, please mark this solved on your post stating you went elsewhere. Thanks.

[Dawnbreaker]

Hey, sorry for "necroing" this, I made sure to read the rules:

Do not reply to or "bump" old topics unless you have something useful to contribute. Do not unnecessarily bump your own topics. Wait at least 24 hours for a reply.

... so I've got a useful question which somewhat indirectly contributes about the original topic, because I faced this oddish behaviour too, and it bugs my mind ever since: So, could it be possible to implement a transition layer which makes it so, to use plasma-firewall under sysvinit? Also, isn't systemd-shim supposed to work as a transition layer? As per the manual:

MX Linux uses systemd-shim, which emulates the systemd
functions that are required to run the helpers without actually using the service. This means that
SysVinit remains the default init yet MX Linux can use Debian packages that have systemd
dependencies such as CUPS and Network Manager. This approach also allows the user to retain
the ability to choose his/her preferred init at boot by selecting the desired entry.

I read this as it works if I used a systemd ("tricking" the apps to think so), while in truth using sysvinit.

Thanks in advance.

[dolphin_oracle]

Hey, sorry for "necroing" this, I made sure to read the rules:

Do not reply to or "bump" old topics unless you have something useful to contribute. Do not unnecessarily bump your own topics. Wait at least 24 hours for a reply.

... so I've got a useful question which somewhat indirectly contributes about the original topic, because I faced this oddish behaviour too, and it bugs my mind ever since: So, could it be possible to implement a transition layer which makes it so, to use plasma-firewall under sysvinit? Also, isn't systemd-shim supposed to work as a transition layer? As per the manual:

MX Linux uses systemd-shim, which emulates the systemd
functions that are required to run the helpers without actually using the service. This means that
SysVinit remains the default init yet MX Linux can use Debian packages that have systemd
dependencies such as CUPS and Network Manager. This approach also allows the user to retain
the ability to choose his/her preferred init at boot by selecting the desired entry.

I read this as it works if I used a systemd ("tricking" the apps to think so), while in truth using sysvinit.

Thanks in advance.

this is already fixed for MX23 users, as long as you are running sddm login manager with our modified init script (the default on the KDE iso).

[Dawnbreaker]

is already fixed for MX23 users, as long as you are running sddm login manager with our modified init script (the default on the KDE iso).

Thanks for the answer @dolphin_oracle, I tested KDE for a few days now, this screenshot was taken from a pure vanilla untouched MX install inside a VBox (but I got a test machine with same symptoms), leaving every settings at default while installing (sorry, I couldn't make this view to go in english, LC_ALL=C didn't worked, but it translates into the same message the OP wrote basically)

[davidy]

Solved, Please delete