Description of problem: system-config-firewall won't start Version-Release number of selected component (if applicable): system-config-firewall-1.2.29-21.fc29.noarch How reproducible, Actual results: # /usr/bin/system-config-firewall Traceback (most recent call last): File "/usr/bin/system-config-firewall", line 36, in <module> import fw_gui File "/usr/share/system-config-firewall/fw_gui.py", line 47, in <module> import fw_dbus File "/usr/share/system-config-firewall/fw_dbus.py", line 24, in <module> import slip.dbus ImportError: No module named slip.dbus Expected results: Startup of system-config-firewall, possibility to modify firewall configuration Additional info: As I can still file a bug against system-config-firewall, why was python2-slip-dbus >= 0.2.7 removed? Doesn't Fedora check against these inconsistencies? So what is fedora trying to do here? And in other places: pending removal network-scripts, dependencies for bolt, iio-sensors-proxy, etc on components that do NOT require these interfaces/things at all. It does appear no real wisdom is going into these things. We do not need NetworkManager, we do not need bolt, we do not need iio-sensors-proxy, we do not need flatpak, we do not need tracker, etc, etc.
There is a python3-slip-dbus. Why isn't this one depended on in a new release of system-config-firewall?
That would require the whole system-config-firewall package to be updated from Python 2 to Python 3. As lokkit & system-config-firewall are replaced by firewalld, this is not necessary. *** This bug has been marked as a duplicate of bug 1715019 ***
firewalld is not a replacement. It is a different approach.