Bug 25510 - lokkit rpm does not fill fields with current info in customize option
lokkit rpm does not fill fields with current info in customize option
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: gnome-lokkit (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
:
: 36658 44028 55289 63902 72678 76688 78440 81530 91802 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-02-01 14:07 EST by Denice
Modified: 2014-03-16 22:18 EDT (History)
9 users (show)

See Also:
Fixed In Version: 1.3.5-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-03-11 00:50:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Denice 2001-02-01 14:07:30 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.16-3 i686; Nav)


Sorry, there is no 'lokkit' choice from bugzilla, so I chose setuptool.
When you have previously customized the firewall configuration, and you use
the
tool again to make changes, then the previous customization options are not
filled in.

Reproducible: Always
Steps to Reproduce:
1. customize firewall during install
2. run lokkit and choose the customize option; the fields are always blank

	

otherwise the tool works :o)
Comment 1 Bill Nottingham 2001-02-01 19:37:00 EST
Yes, it does not read the current config.
Comment 2 Bill Nottingham 2001-02-05 10:59:24 EST
*** Bug 25951 has been marked as a duplicate of this bug. ***
Comment 3 Bill Nottingham 2001-04-23 23:27:11 EDT
*** Bug 36658 has been marked as a duplicate of this bug. ***
Comment 4 Bill Nottingham 2001-06-17 22:27:42 EDT
*** Bug 44028 has been marked as a duplicate of this bug. ***
Comment 5 Bill Nottingham 2001-10-29 09:46:58 EST
*** Bug 55289 has been marked as a duplicate of this bug. ***
Comment 6 Need Real Name 2002-10-11 17:57:10 EDT
I can confirm this bug on redhat 8.0 - quite annoying indeed
Comment 7 Bill Nottingham 2002-10-24 18:52:57 EDT
*** Bug 76688 has been marked as a duplicate of this bug. ***
Comment 8 Bill Nottingham 2002-10-24 18:53:31 EDT
*** Bug 72678 has been marked as a duplicate of this bug. ***
Comment 9 Brent Fox 2002-11-26 10:28:40 EST
*** Bug 78440 has been marked as a duplicate of this bug. ***
Comment 10 Mattias Dahlberg 2002-12-06 18:24:19 EST
What is plan b? If lokkit doesn't get a "read current config" feature in time 
for the next version of Red Hat, I mean. Maybe the only option is to scrap 
lokkit as a back-end for the Red Hat tool and work directly towards iptables 
instead?
Comment 11 Bill Nottingham 2003-01-09 23:26:09 EST
*** Bug 81530 has been marked as a duplicate of this bug. ***
Comment 12 Bill Nottingham 2003-05-28 12:31:24 EDT
*** Bug 91802 has been marked as a duplicate of this bug. ***
Comment 13 Mattias Dahlberg 2003-05-28 12:45:16 EDT
This seems to be fixed in Red Hat 9.
Comment 14 Ken Marsh 2003-12-11 13:33:18 EST
It is not fixed in *my* Red Hat 9.
Comment 15 Bill Nottingham 2004-03-11 00:50:40 EST
Fixed in system-config-securitylevel-1.3.5-1.
Comment 16 Miloslav Trmač 2004-09-28 18:42:59 EDT
*** Bug 63902 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.