| Summary: | Minimal install with X results frozen (XDM) screen | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jüri Ivask <jyri2000> |
| Component: | Release (media or process) | Assignee: | Anne Nicolas <ennael1> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11, sysadmin-bugs, yochenhsieh |
| Version: | Cauldron | Keywords: | 6dev1 |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | task-x11-1-7mga6 | CVE: | |
| Status comment: | |||
| Attachments: | log from journalctl --boot=-1 | ||
|
Description
Jüri Ivask
2016-03-09 10:26:10 CET
Created attachment 7529 [details]
log from journalctl --boot=-1
Attached log when booted to recovery and: journalctl --boot=-1 > lastboot.txt
(In reply to Jüri Ivask from comment #0) > > However, when I perform the same install using Mageia5 and then at once > upgrade it to Cauldron, the XDM screen is operational and it is possible to > start icewm session. In your output, I do see märts 08 09:40:42 localhost systemd[1]: Started Display Manager. but not one line about xdm after that, nothing like the lines about sddm that I see on my system mrt 09 18:08:36 cldrn_64 sddm[848]: Initializing... mrt 09 18:08:36 cldrn_64 sddm[848]: Starting... mrt 09 18:08:36 cldrn_64 sddm[848]: Adding new display on vt 1 ... mrt 09 18:08:37 cldrn_64 sddm[848]: Display server starting... etc. However, I do not know whether they should be there for xdm, too. Do you mind checking your working 5=>cauldron upgrade for that? Apart from that, please attach 5toCauldron.txt that is the result of rpm -qa | sort > 5toCauldron.txt for the Mga5 install that you upgraded to cauldron and attach /root/drakx/report.bug.xz from your cauldron install (the buggy install) Keywords:
(none) =>
NEEDINFO that's not an installer bug Component:
Installer =>
RPM Packages Sorry, can't check that Mga5toCauldron install now - that was my previous attempt to perform Cauldron minimal install with X and it was about month ago. I know, I should have reported this bug already then... This time, after that failed attempt I performed a Cauldron network install using: 1.Desktop Selection -> Custom 2.Package Group Selection -> Unselect All -> Plasma Desktop -> Next and it was successfull - installed system booted to operational SDDM. The reason I try to use minimal install with X is that I want to get minimal and pure kde4free Plasma5 system using later urpmi --no-recommends task-plasma5-minimal.
You-Cheng Hsieh
2016-04-09 16:12:33 CEST
CC:
(none) =>
yochenhsieh Can be reporduced with Mageia-6-dev1-i586-DVD. If checked "Install recommended packages", the system will work fine after first boot. So this might be a dependency problem? OK. I think this bug is a duplicate of bug #18026 - no input driver by minimal install. The reason it is reproducible in Mageia-6-dev1 is because it should be fixed in task-x11-1-8mga6, but the package in iso is task-x11-1-7mga6. The iso was built before it fixed, but released later. Mar 9 - bug17920 reported. Mar 10 - Mageia-6-dev1-i586-DVD. Mar 16 - Mageia-6-dev1-x86_64-DVD. Mar 17 - bug18026 reported. Mar 18 - bug18026 fixed <- also fixed 17920. Mar 27 - Mageia-6-dev1 released. (In reply to You-Cheng Hsieh from comment #6) > OK. I think this bug is a duplicate of bug #18026 - no input driver by > minimal install. > > The reason it is reproducible in Mageia-6-dev1 is because it should be fixed > in task-x11-1-8mga6, but the package in iso is task-x11-1-7mga6. The iso was > built before it fixed, but released later. > > Mar 9 - bug17920 reported. > Mar 10 - Mageia-6-dev1-i586-DVD. > Mar 16 - Mageia-6-dev1-x86_64-DVD. > Mar 17 - bug18026 reported. > Mar 18 - bug18026 fixed <- also fixed 17920. > Mar 27 - Mageia-6-dev1 released. Thanks for the debugging :-) Changing the Component to "Release", then, and leaving this bug open until the 6dev2 isos get tested by QA team Keywords:
NEEDINFO =>
6dev1 Just tested today and the bug (frozen XDM screen after minimal install with X) seems to be fixed now. BTW Why is evolution-data-server included in minimal install? Should I create a separate bug for it? Closing this bug as it's fixed now Status:
NEW =>
RESOLVED |