[Bug 77891] Re: Kcontrol doesn't open the system services module

Jay Smith jay.smith at noaa.gov
Fri Oct 26 23:12:05 UTC 2007


I ran into the System Services module not loading problem with both
Feisty Fawn and Gutsy Gibbon. I have figured out what my problem was and
can work around it.

In my case, the Python script /var/lib/python-
support/python2.5/serviceconfig.py could not find the rc#.d directories
on the file system which prevented the System Services module from
loading. Different Linux distributions put the rc#.d directories in
different locations. Debian systems put them directly under the /etc
directory while Red Hat and Mandrake systems place them under the
/etc/rc.d directory. The serviceconfig.py uses the /etc/issue file to
try and determine if the machine is running Debian or not. This is done
by checking to see if first line of the /etc/issue file starts with
"Debian" or "Ubuntu". I'm using Kubuntu in an environment that requires
"Unauthorized Access Warnings" be provided to users before they log on
and one of the files that has to be modified to provide the warnings is
/etc/issue. Of course, I replaced the /etc/issue file with the warning
text so the /etc/issue file no longer started with "Ubuntu" which caused
the serviceconfig.py script to conclude I was running Mandrake Linux and
look for the rc#.d directories in the wrong location. I have modified my
/etc/issue file to append the warning text to the delivered /etc/issue
file. Now, the System Services module loads just fine. (Note: in my up-
to-date Kubuntu 7.10 installation, the code of interest is the
"getServiceContext" function of serviceconfig.py which appears on lines
243-271.)

I've attached a possible replacement for the getServiceContext function
which does not use the /etc/issue file as a means to check which Linux
distro is being run.

** Attachment added: "getServiceContext.txt"
   http://launchpadlibrarian.net/10181226/getServiceContext.txt

-- 
Kcontrol doesn't open the system services module
https://bugs.launchpad.net/bugs/77891
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for kde-guidance in ubuntu.




More information about the kubuntu-bugs mailing list