Red Hat Bugzilla – Bug 980207
red color used for inactive services falsely suggests problems
Last modified: 2013-12-28 18:37:04 EST
Created attachment 767459 [details]
Example of problem listing
Description of problem:systemd System Manager displays many problems in red, but does not offer way to fix or explanation of what to do.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The red color here is not meant to indicate problems. systemdadm just uses a crazy color scheme.
Heck, that doesn't even begin to scratch the surface. In fact, I didn't even think of that.
The real serious issues include the line where it says that a particular item wants a certain thing but it is dead. That can't be good. Even required things are dead.
If that is wrong, then the program is absolutely misleading and worthless to the average user. Are you saying those things are just wrong?
And let's not forget that the menu calls the program "Services", rather than "systemd System Manager". Is any part of it actually useful?
Your edit of the title is totally improper and insulting. Or is it a self-serving method you apply to something you don't want to fix?
This program is not maintained and not ready for general consumption.
It is more a prototype of what *could* be done, than anything useful.
It might not get fixed any time soon, unless someone takes it over the
Please don't expect any work to be done with it, none of us has the time
to work on it. At the moment it's the best to just ignore it entirely.
(In reply to KitchM from comment #2)
> The real serious issues include the line where it says that a particular
> item wants a certain thing but it is dead. That can't be good. Even
> required things are dead.
Your screenshot shows the view of shutdown.target, which itself is inactive (dead). Therefore it is not a problem that some of its requirement dependencies are inactive as well.
> If that is wrong, then the program is absolutely misleading and worthless to
> the average user. Are you saying those things are just wrong?
The information it shows is not wrong, but it needs to be properly understood. Admittedly systemadm's GUI is not very well designed and it can be quite confusing to some users. This is one of the reasons we do not install it by default.
> Your edit of the title is totally improper and insulting. Or is it a
> self-serving method you apply to something you don't want to fix?
Editing bug titles is a proper procedure in bug triage. And now I am insulted.
I will remove the worthless program. Since it isn't by default and isn't useful, it should be removed from the repositories as well, unless it is in testing.
Don't be insulted. You took it upon yourself to totally change the meaning of my post. You obviously felt you could handle any reprecussions.
I am the only one that should be insulted, because now you are trying to shift the blame for your mistake upon me. Put it back like it was.
systemd-ui-3-1.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-ui-3-1.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
systemd-ui-3-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.