Description of problem: After installing 4.14.14-desktop-1.mga6 64-bit from the "Classical" ISO support, my system fails to reboot : - The installation process performs correctly, - GRUB2 is correctly generated and displayed at the reboot, - Then MAGEIA's welcome screen (with the cauldron) is correctly displayed, - Then it disappears and the boot process simply stops . Except shuting down and restarting the piece of equipment (with the same "result" ..), the only way I found to escape this situation is a [Crtl][Alt][F2] break to get the login prompt. At this point it is possible to launch manually the X server with a "startX" command and then .. the graphical interface (GNOME in my case) appears and everything seems to work correctly .. (but the problem will be the same the next time I start my system). THIS PROBLEM DOES NOT OCCUR WITH THE LIVE ISO, it's only induced by the Classical ISO ! The installation from the Live ISO CD gave me NO problem at all. I did try several video drivers, from NVIDIA or XOrg (VESA, Nouveau ..), I tried to activate/deactivate the ACPI options, without any result. I tried Plasma and GNOME : no result . In fact I'm happy with my installation from the Live support and I report this bug only to inform the community . Version-Release number of selected component (if applicable): 4.14.14-desktop-1.mga6 64-bit How reproducible: - Every time the system is relaunched Steps to Reproduce: 1. Download & verify (checksum) the "Classical" ISO installation of Mageia 6 from the Web site; 2. Burn a CD; 3. Install it from scratch (reformat the "/" partition); 4. At the end of the installation process, reboot the system as asked by the installer; 5. GRUB2 is displayed and works normaly; 6. The MAGEIA Cauldron screen is displayed correctly; 7. It disappears and the system stops; Workaround : A. 1. Break by [Ctrl][Alt][F2] 2. Get the prompt and login 3. Launch manually the X server with "startx" command . B. ALternative : Reinstall the system from the Live ISO support .
Hi Michel, Can you please boot into such an Classical install that needs that workaround and then fetch /root/drakx/report.bug.xz and attach it to this bug report. Also please attach log.txt that is the result of running, as root, journalctl -b > log.txt in the "workaround" install. Thanks :-)
CC: (none) => marja11Keywords: (none) => NEEDINFO
Howdy Marja and thanks for your answer, But does it mean I should have to completely crush ONE MORE TIME my current roughly stable - for the moment - configuration to reinstall this thingy ? If that's the case, my answer is simply "sorry, no thanks" .. I have only one computer and only one life at my disposal, and a huge of things to do with both of them in the next days ..
(In reply to Michel AUTEM from comment #2) > Howdy Marja and thanks for your answer, > > But does it mean I should have to completely crush ONE MORE TIME my current > roughly stable - for the moment - configuration to reinstall this thingy ? I understand that your only current installation was done from a Live medium.... in that case you don't have the needed log files :-( > > If that's the case, my answer is simply "sorry, no thanks" .. I have only > one computer and only one life at my disposal, and a huge of things to do > with both of them in the next days .. No problem, but it means we should close this report as invalid, because it is too incomplete: it lacks the log files we need to have the slightest idea what could cause this bug. I'll close it as old, though, that doesn't sound as if we don't believe you hit a real bug. Please don't get discouraged and please do keep filing bug reports. just read the following about reporting bugs in general https://wiki.mageia.org/en/How_to_report_a_bug_properly To see which additional information is needed for traditional and live installer bugs, please read https://wiki.mageia.org/en/Triage_guide#Installer-related_bugs
Resolution: (none) => OLDStatus: NEW => RESOLVED