This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours
Bug 467057 - The enable/disable/custom icon isn't properly updated in the gui
The enable/disable/custom icon isn't properly updated in the gui
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: system-config-services (Show other bugs)
10
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nils Philippsen
Fedora Extras Quality Assurance
:
Depends On:
Blocks: F10DesktopTarget
  Show dependency treegraph
 
Reported: 2008-10-15 10:30 EDT by Bruno Wolff III
Modified: 2009-04-28 09:45 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-04-28 09:45:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Bruno Wolff III 2008-10-15 10:30:53 EDT
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Enable a service and without leaving scs disable it (tested with bluetooth and ebtables)
2.
3.
  
Actual results:
The disable icon changes to enable, but then does not change back to disable. (Though chkconfig shows that it was actually disabled.)

Expected results:
The icon would change to match the current status.

Additional info:
Comment 1 Bruno Wolff III 2008-10-15 13:41:57 EDT
I forgot to include the version. It is system-config-services-0.99.23-1.fc10.noarch.
Comment 2 Bug Zapper 2008-11-25 22:53:36 EST
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 3 Bruno Wolff III 2009-04-28 09:45:06 EDT
Things seem to be working OK in rawhide now, so I am going to closes this.

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