Bug 4728 - drakedm cannot restart dm service when requested
Summary: drakedm cannot restart dm service when requested
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-28 05:40 CET by You-Cheng Hsieh
Modified: 2012-03-26 09:34 CEST (History)
2 users (show)

See Also:
Source RPM: initscripts
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description You-Cheng Hsieh 2012-02-28 05:40:30 CET 
Description of problem:
Except kdm, drakedm cannot restart dm service when user want to switch to another dm(gdm, xdm, lxdm, slim).

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

How reproducible:
Switch to different dm in drakedm.

Steps to Reproduce:
1.Start mcc.
2.Go to Boot -> Setup Display Manager
3.Switch to other dm except kdm
4.Drakedm will ask to restart dm service. Select OK.
5.the desired dm will fail to start and user can only use tty1~6.
Manuel Hiebel 2012-02-28 19:51:13 CET

Assignee: bugsquad => thierry.vignaud
Severity: major => normal

Comment 1 papoteur 2012-03-25 21:55:00 CEST 
Seen the same problem in commuting from lxdm to xdm.
Yves

CC: (none) => yves.brungard_mageia

Comment 2 Thierry Vignaud 2012-03-25 22:25:32 CEST 
We're just doing a service restart.
So it's either a initscripts issue (it provides the dm service) or an issue in those dms

Source RPM: drakxtools => initscripts

Comment 3 You-Cheng Hsieh 2012-03-26 04:52:49 CEST 
I cannot reproduce this bug anymore. It seems there're some initscripts updates regarding to dm services after this bug been reported. Now it works for me.

initscripts-9.34-10mga2
Comment 4 Sander Lepik 2012-03-26 09:34:08 CEST 
Marking as fixed then, please reopen if needed.

Status: NEW => RESOLVED
CC: (none) => sander.lepik
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.