Bug 5122

Summary:	MCC Services and Daemons control screen fails to show all service state change
Product:	Mageia	Reporter:	Richard Walker <richard.j.walker>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia, wilcal.int
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Bug Depends on:	1025
Bug Blocks:	2120

Description Richard Walker 2012-03-26 22:53:46 CEST

Description of problem:
The majority of the services registered on my system are set to run on boot. Most of them are indicated in MCC as being stopped. The stop/start buttons have no visible effect on the status indicator in MCC though many of the services are in fact starting and stopping.

Version-Release number of selected component (if applicable):
drakconf version 12.23-1.mga2

How reproducible:
Consistent

Steps to Reproduce:
1.in MCC Services and Daemons screen, choose one of:
acpid
alsa
atd
avahi-daemon
crond
gpm
ip6tables
iptables
irqbalance
messagebus
msec
netconsole
network-auth
network-up
ntpd
rpcbind
rsyslog
smartd
sound

2.the chosen service will indicate it is "stopped" so click its start button
3.the pop-up may indicate the service is starting, or restarting but the on-screen state indication does not change.
4. observe the cpufreq service status. If is says "stopped" then click on the start button, else click on the stop button
5. If cpufreq is started then the status indication will change accordingly
6. If cpufreq is stopped then the status indication will not change

Comment 1 Bit Twister 2012-03-27 01:12:42 CEST

Maybe drakxservices could call systemadm, found in the systemd-ui package/rpm,
if default system is initialized with systemd.

Source RPM: (none) => drakxtools-14.1-2.mga2.src.rpm

Comment 2 Richard Walker 2012-03-27 02:03:14 CEST

Are the other service notifications (the ones that do work with MCC Services & Daemons) implemented like that? As far as I can tell there is only systemd available to initialise the system as the option not to use it has been removed from the kernel boot parameters in the grub menu.

I've just had a quick look. systemadm is not installed on my system so it can't be using that method at the moment, but presumably this has already been considered in the changeover to systemd. There must already be an alternative method to support drakconf - it just isn't working as well as it might at the moment.

Comment 3 Manuel Hiebel 2012-03-27 03:08:06 CEST

see https://bugs.mageia.org/show_bug.cgi?id=1025#c2
Not a draxktools issue.
this service always return the value returned by gprintf instead of 1/0

we need to fix all these package

Source RPM: drakxtools-14.1-2.mga2.src.rpm => (none)
Blocks: (none) => 2120

Manuel Hiebel 2012-03-27 03:08:15 CEST

Depends on: (none) => 1025

Comment 4 Bit Twister 2012-03-27 03:27:22 CEST

(In reply to comment #2)
> Are the other service notifications (the ones that do work with MCC Services &
> Daemons) implemented like that?

Guessing, no. 

> As far as I can tell there is only systemd available to initialise the system
> as the option not to use it has been removed from the kernel boot parameters
> in the grub menu.

With only systemd supported in Mageia 3, I would guess not much work will be put into Mageia 2 to to make MCC completely transparent regardless of system initialization application.

> I've just had a quick look. systemadm is not installed on my system so it 
> can't be using that method at the moment, 

Yep, I'm guessing it was installed when I had added the systemd-tools package after installation. Going to have to spend some time looking at what was installed.

> but presumably this has already been considered in the changeover to systemd.

My comment was just a quick kludge to solve the problem. I have no idea if there is a task afoot to make that a reality.

> There must already be an alternative method to support drakconf - it just
> isn't working as well as it might at the moment.

Yep, even systemadm would need an enable/disable button and info if there is time before release.

Currently the command line 
     "systectl start/stop/enable/disable/status daemon.service"
is the best workaround.  :(

Comment 5 Dave Hodgins 2012-04-05 03:12:31 CEST

*** Bug 5235 has been marked as a duplicate of this bug. ***

CC: (none) => wilcal.int

Comment 6 Colin Guthrie 2012-04-25 12:42:56 CEST

This should be fixed (at least for the most part) in latest drakxtools. Not all systemd services are listed (e.g. template units), but most of the simpler services are now shown and should be configurable (I'm not sure about the update of display of the current status, but if it's broken, it's an old issue not directly related to systemd)

Status: NEW => RESOLVED
CC: (none) => mageia
Resolution: (none) => FIXED