Bug 11333 - RazorQT from DualCD asks to install XDM after main package installation on screen titled Warning - 4alpha3
Summary: RazorQT from DualCD asks to install XDM after main package installation on sc...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Anne Nicolas
QA Contact:
URL:
Whiteboard: 4alpha3
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-01 11:20 CEST by claire robinson
Modified: 2013-10-02 12:33 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
report.bug.xz (83.09 KB, application/x-xz)
2013-10-01 11:52 CEST, claire robinson 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description claire robinson 2013-10-01 11:20:54 CEST 
4alpha3 DualCD 2nd build (Date.txt Sept 30th)

Installed main packages and after entering user details it displays a 'Warning' screen asking to install XDM.

Reproducible: 

Steps to Reproduce:
Comment 1 claire robinson 2013-10-01 11:21:49 CEST 
See also bug 11325 which is similar. I'll attach report.bug when it's finished installing.

Whiteboard: (none) => 4alpha3

Comment 2 claire robinson 2013-10-01 11:52:37 CEST 
Created attachment 4396 [details]
report.bug.xz
Comment 4 Anne Nicolas 2013-10-01 15:55:51 CEST 
Well not necesseraly. xdm is proposed as no dm manager was installed previously. At least in that case lightm was removed by error when cleaning packages list.
Comment 5 Manuel Hiebel 2013-10-01 16:04:38 CEST 
anyway this dm is missing too in the any.pm (on mga3 dual, lxdm was included)
Comment 6 Manuel Hiebel 2013-10-01 16:06:30 CEST 
and if we use lightdm for everything bingo (so this bug is a duplicate of the 11325)
Marja Van Waes 2013-10-01 20:31:22 CEST

CC: (none) => marja11
Hardware: i586 => All

Comment 7 claire robinson 2013-10-02 12:33:09 CEST 
fixed in build 3 (1st October)

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