Bug 19781 - Mageia 6 REAL HARDWARE: "Good luck" failure to start graphical interface, display manager
Summary: Mageia 6 REAL HARDWARE: "Good luck" failure to start graphical interface, dis...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker critical
Target Milestone: ---
Assignee: All Packagers
QA Contact: Samuel Verschelde
URL: https://bugs.mageia.org/show_bug.cgi?...
Whiteboard:
Keywords: TRACKER
Depends on: 19849 19854
Blocks: 19798
  Show dependency treegraph
 
Reported: 2016-11-14 21:13 CET by Lewis Smith
Modified: 2016-12-06 19:24 CET (History)
7 users (show)

See Also:
Source RPM:
CVE:
Status comment: Should be fixed since the 30th of November


Attachments

Description Lewis Smith 2016-11-14 21:13:09 CET
This bug supersedes bug 19216
  https://bugs.mageia.org/show_bug.cgi?id=19216
by separating reports between:
- real hardware [this bug]
- VBox

If the problem is related to AutoLogin, please note it on bug:
 https://bugs.mageia.org/show_bug.cgi?id=19234

Please be careful to note all the factors which might be relevant (real HW | VBox are already implied). There is no need to list them all, but certainly those which might be applicable. You might even Copy/Paste the list below as a template, deleting irrelevant lines:

- Architecture [also part of the ISO name below]:
  - i586
  - x86_64
- What graphics hardware?
- Which ISO are you testing (title & date)?
- BIOS boot or UEFI?
- At what stage do you see the message?
  - Booting the ISO from [what medium]
  - Later during the installation
  - Re-booting the installed system:
    - Without non-free [video] software
    - With non-free [video] software
    - Without installation update
    - With installation update
  - Subsequent re-boots without updates
  - Subsequent re-boots after updates
- Kernel version(s)
- In the case of nvidia does the kmod build succeed?
- What graphics driver?
- If you added a kernel parameter to succeed: what? Among:
  - nomodeset
  - nokmsboot
- Which display manager?
  * Please try others (if you have >1, from a console: # drakdm)
  * If you have only 1, install another if you are able to (have network, repos enabled) # urpmi GDM|LightDM|LXDM|SDDM
  * Re-boot
- The presence and contents of /etc/sddm.conf
- The presence and contents of /etc/sysconfig/desktop
- /etc/X11/xorg.conf: does removing it change the situation?
- Whether Autologin is active or not.
Lewis Smith 2016-11-14 21:14:00 CET

Priority: Normal => release_blocker

Comment 1 Marja Van Waes 2016-11-15 11:19:15 CET
@ all

Please use this bug as tracker, and file a fresh bug report when you hit this issue, while providing as much information as possible, as Lewis suggested above.

After filing it, please set the new bug to _block_ this one by adding 19781 in the "Blocks:" field of the new bug.

The reason is, that there are most likely several bugs leading to this error. Each needs a separate bug report. Accidentally filing duplicates is less bad, in this case, than getting a bug report like bug 19216 that contains mixed issues.

Thanks!
Marja

Keywords: (none) => TRACKER
CC: (none) => kde, kernel, mageiatools, marja11

Marja Van Waes 2016-11-15 11:20:23 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=19782

Helge Hielscher 2016-11-15 14:49:53 CET

CC: (none) => hhielscher

Stephen Butler 2016-11-16 06:18:05 CET

Blocks: (none) => 19798

Samuel Verschelde 2016-11-17 15:23:31 CET

Assignee: bugsquad => pkg-bugs

Rémi Verschelde 2016-11-23 21:48:07 CET

Status comment: (none) => Waiting for new 6 sta2 ISOs for tests of the current state

Marja Van Waes 2016-11-27 17:52:07 CET

Depends on: (none) => 19849

Marja Van Waes 2016-11-28 11:46:07 CET

Depends on: (none) => 19854

Comment 2 Samuel Verschelde 2016-12-01 22:25:05 CET
Should be fixed since the 30th of November via a systemd-units update.

Status comment: Waiting for new 6 sta2 ISOs for tests of the current state => Should be fixed since the 30th of November

Samuel Verschelde 2016-12-01 22:25:21 CET

QA Contact: (none) => stormi

Comment 3 Thomas Andrews 2016-12-06 15:45:00 CET
I ran into this bug after installing Plasma from an older iso, the problematic RC I think, after enabling autologin. I had done other things during that session, so I can't be sure that it was autologin that made it show up, but the way it acted when booting after that suggested it. Soon after, I replaced that install with an Mga5 install to use for testing updates, and have not been back to Mga6 until now.

I have not yet seen the problem after installing from the sta2 iso, on two machines, despite having done all the things I remember doing after installing from the earlier iso, and more. Autologin seems to be working perfectly.

CC: (none) => andrewsfarm

Comment 4 Samuel Verschelde 2016-12-06 15:52:03 CET
Closing as fixed since everything indicates that the fix worked. Anybody still having an issue, it will probably be something different so please create a new bug report for that.

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

Comment 5 William Kenney 2016-12-06 19:24:10 CET
My original bug, 19216,, Plasma, I found the "Good Luck" error by setting
the log in to automatic. On real hardware now setting auto log in
to automatic results in a good boot to the log in screen then after
log in it continues on to the Plasma desktop. While auto log in does
not work the "Good Luck" error seems to have gone away.

CC: (none) => wilcal.int


Note You need to log in before you can comment on or make changes to this bug.