Bug 845176

Description of problem:
having invalid but iptables-save compliant custom rules file causes the firewall to become unset with no error notification.

the -tui version shows
Job failed. See system journal and 'systemctl status' for details.
Redirecting to /bin/systemctl start  ip6tables.service
Failed to start iptables.

but the gui does not show anything.

Version-Release number of selected component (if applicable):
1.2.29-7.fc17

How reproducible:


Steps to Reproduce:
1. iptables-save > /etc/sysconfig/iptables.al-filter
2. lokkit --custom-rules=ipv4:filter:/etc/sysconfig/iptables.al-filter
3. system-config-firewall
4. # in the gui check and then uncheck any previously unchecked service to enable apply button
5. # hit apply
6. # close
7. iptables -vnL
  
Actual results:
In gui completely silent.
Chain INPUT (policy ACCEPT 589 packets, 48788 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 413 packets, 85092 bytes)
 pkts bytes target     prot opt in     out     source               destination         

In tui error message which can be easily overlooked.
[root@puppetmaster aledvink]# system-config-firewall-tui 

Configuration failed
/usr/sbin/lokkit -f -v --enabled --service=ssh --port=8140:tcp --custom-rules=ipv4:filter:/etc/sysconfig/iptables.al-filter
Redirecting to /bin/systemctl stop  iptables.service
Redirecting to /bin/systemctl stop  ip6tables.service
Redirecting to /bin/systemctl start  iptables.service
Job failed. See system journal and 'systemctl status' for details.
Redirecting to /bin/systemctl start  ip6tables.service
Failed to start iptables.


Hit enter to continue.



Expected results:
error message visible also in gui version? either error dialog or at least review of the command stdout+stderr as in tui.

Additional info: