http://bugzilla.suse.com/show_bug.cgi?id=1114807 http://bugzilla.suse.com/show_bug.cgi?id=1114807#c8 David Diaz <dgonzalez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |dgonzalez@suse.com --- Comment #8 from David Diaz <dgonzalez@suse.com> --- (In reply to lili zhao from comment #5) Hi!
Found no this issue on SLES15-SP1-B102.1, (checked by "# systemctl stats firewalld.service" and "# firewall-cmd --state")
I could reproduce it in the latest openSUSE TW (Snapshot-20181124). If you check the status of service immediately after click on "Stop now" the result is "not running". The problem appears after click "Accept", when the you can see that the service state is "running" again. The good news is that we are going to use the new ServiceWidget[1] in this module, which resolves the problem. I just test it using the PR in the yast-network module[2], which I plan to merge in the coming days, in 2019 :) [1] https://lizards.opensuse.org/2018/08/22/yast-squad-sprint-59-60/ -> See "A New Widget To Manage Services" section. [2] https://github.com/yast/yast-firewall/pull/109 -- You are receiving this mail because: You are on the CC list for the bug.