After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 142721 - not all scripts listed, no runlevel boot (gentoo)
not all scripts listed, no runlevel boot (gentoo)
Status: RESOLVED WONTFIX
Product: gnome-system-tools
Classification: Deprecated
Component: services-admin
unspecified
Other Linux
: Normal major
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2004-05-18 13:45 UTC by Dennis Möhlmann
Modified: 2012-11-24 20:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description Dennis Möhlmann 2004-05-18 13:45:38 UTC
- Runlevel dropdown menu does not list runlevel "boot". 
- Scripts currently assigned to runlevel boot are not listed (meaning: not just
inactive but not even in the list)
- Scripts containing a "." are not listed, no matter if inactive or active and
if active, no matter which runlevel. Examples are net.eth0, net.ppp0 etc.
- For some reason, "alsasound" and "modules" which are in runlevel boot are in
the list. With runlevel "default" selected from the dropdown, they are marked
inactive. ("alsasound" and "modules" are not in my default runlevel, they are
only active in runlevel boot. This is strange because other runlevel boot
scripts are not listed at all)

Expected results:
- Runlevel boot available from dropdown
- All scripts in /etc/init.d/ not ending with ".sh" should be listed
- Scripts which are active in "boot" should be marked as active if "boot" is
selected from dropdown
- Same goes for default and potentially other softlevels.
Comment 1 Dennis Möhlmann 2004-05-18 14:33:03 UTC
Unfortunatly I got to correct myself. Runlevel boot is displayed in the dropdown
list, it's just greyed out (but selectable) and named "starts all system
neccessary services" which is just odd.
Selecting runlevel "starts all system neccessary services" also lists alsasound
and modules as active. So this is what I should have written (sorry for the
"buggy" report):

------------------------------------

- Runlevel boot is named "starts neccessary system services" and greyed out
- Scripts currently assigned to runlevel boot are not listed
- Scripts containing a "." are not listed, no matter if inactive or active and
if active, no matter which runlevel. Examples are net.eth0, net.ppp0 etc.

Expected results:
- Runlevel boot should be named "Boot runlevel" and should not be greyed out
initially
- All scripts in /etc/init.d/ not ending with ".sh" should be listed

------------------------------------
Comment 2 Carlos Garnacho 2004-05-19 12:46:21 UTC
Just a few comments:

- the "first option in the menu shows inactive" is a Gtk+ bug, hopefully it will
get fixed when GST uses the Gtk+ 2.4 GtkComboBox
- there are scripts that are hidden for 2 reasons:
    * in the net.* case, services-admin is for running services, not network
interfaces, this is for the network tool :)
    * all services that in some way should remain untouchable (as
running/stopping/removing or adding in a runlevel might suppose a risk) are hidden

So sorry, but I'm tempted to mark this bug as NOTABUG, unless you tell me that
there's a essential editable service hidden :)
Comment 3 Dennis Möhlmann 2004-05-19 16:29:14 UTC
This is a bug. I assume you missed a few points thanks to my screwed report. So
here are the highlights again:

- Scripts currently assigned to runlevel boot are not __listed__

This is essential. They are not even listed, not just inactive. They must be
listed, otherwise "starts all system neccessary services" (runlevel boot) is a
useless option (essentially all scripts in this runlevel are missing!) and
should be removed along with it, i.e. "consolefont" and "keymap" sure don't
sound like they need to be untouchable, especially not when we're talking about
a Gentoo system.


- Runlevel boot is named "starts neccessary system services"

Other runlevels contain their name. Unless you have a good feeling with
obscuring things so the user doesn't understand you, this needs to be changed
and is a bug. Right now it sounds like a headline for the other runlevels.


As for hiding network services, this might be ok. I will have to file another
bug against the network tool then, because my network services are marked
inactive there. I though this was the same backend problem and therefore didn't
open another bug.

Finally, if you still want to close this bug, please post again before doing so.
The current application behaviour is not acceptable on a Gentoo system and makes
the application appear buggy and therefore not thrustworthy to modify
systemcritical settings.
Comment 4 André Klapper 2012-11-24 20:30:36 UTC
According to its developer(s), gnome-system-tools is not under active development anymore. Functionality has been mostly integrated into GNOME Control Center / "[System] Settings".

It is unlikely that there will be any further active development.

Closing this report as WONTFIX as part of Bugzilla Housekeeping - Please feel
free to reopen this bug report in the future if anyone takes the responsibility
for active development again.