Bug 19749 - Mageia 6: no graphical display, title changed not to find it
Summary: Mageia 6: no graphical display, title changed not to find it
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: https://bugs.mageia.org/show_bug.cgi?...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-10 13:50 CET by Lewis Smith
Modified: 2016-11-14 21:35 CET (History)
0 users

See Also:
Source RPM: prefdm, sddm
CVE:
Status comment:


Attachments

Description Lewis Smith 2016-11-10 13:50:30 CET
Description of problem:
Many installations of pre-release Mageia 6 end up unable to start the graphical interface with a "Good Luck" console message. The causes of this are thought to be diverse, and a special bug was created (URL above). It is now agreed that the problem is fundmentally different for real hardware and VBox, so this bug is being created to separate the two: this for real hardware, another for VBox.

The original bug is overloaded and too diverse to pin down the problem. This bug (and its VBox companion) may be split again if other key differentiating factors emerge. It is being initiated with all Comments from Bug 19216 that are or could be related to real hardware M6 installs. Future reports should be added to the most appropriate bug, *not* this one.

Version-Release number of selected component (if applicable):
Mageia 6, Cauldron

How reproducible:
Very variable.

Steps to Reproduce:
1. Install Mageia 6 on real hardware.
2. Re-boot.
3. The error may or may not happen.
Comment 1 Lewis Smith 2016-11-10 13:52:57 CET
Correction:
> Future reports should be added to the most appropriate bug, *not* 19216.
Comment 2 Lewis Smith 2016-11-10 13:54:46 CET
William Kenney  2016-08-18 22:49:54 CEST 
On real hardware, M6, Plasma, 64-bit

Install from todays x86_64 boot.iso

Test platform:
Intel Core i7-2600K Sandy Bridge 3.4GHz
GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo
GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB
RTL8111/8168B PCI Express 1Gbit Ethernet
DRAM 16GB (4 x 4GB)
Mageia 5 64-bit, Nvidia driver
Plasma DM

After initial install I was successful to get to a working Plasma desktop.
System rebooted successfully. Upon MCC -> Boot -> select autologin
System boots to the now called "good luck" error.
Comment 3 Lewis Smith 2016-11-10 13:55:07 CET
William Kenney  2016-08-18 22:50:09 CEST 
In Vbox, M6, Plasma & Gnome, 64-bit

Install from the latest CI's. All four platforms.
Gnome, 32 & 64 bit
Plasma, 32 & 64 bit.

Never gets to a working desktop. Immediately goes to the "good luck" error.
Comment 4 Lewis Smith 2016-11-10 13:56:33 CET
Blast: editing problem. IGNORE previous Comment 3 (re VBox).
Comment 5 Lewis Smith 2016-11-10 14:00:05 CET
Lewis Smith  2016-08-19 09:22:19 CEST 
Real hardware x64 EFI, AMD/ATI/Radeon HD7310 graphics.
All booting the most recent ISO from USB.

Plasma Live 22 July: Shows this error.
Run: fails to boot "Good luck".
Install: fails to boot "Good luck".

[i.e. this happened when booting the ISO, not the installed system]
Comment 7 Lewis Smith 2016-11-10 14:01:09 CET
Frédéric Buclin  2016-08-19 13:25:51 CEST 
(In reply to William Kenney from comment #7)
> Removing /etc/sysconfig/desktop changes nothing.
> A reboot results in the same error message.

The point is *not* to remove /etc/sysconfig/desktop. The point is to make sure this file exists and contains DISPLAYMANAGER=SDDM.
Comment 8 Lewis Smith 2016-11-10 14:03:37 CET
Ulrich Beckmann  2016-08-20 13:42:34 CEST 
Created attachment 8357 [details]
CLI output of journalctl -b --no-pager | grep sddm

Installed Plasma 5, display manager sddm, from classical iso of 13th Aug. (usb),
Real Hardware, UEFI, [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M], driver Radeon. Reboot sucessful, system is clean. See https://bugs.mageia.org/show_bug.cgi?id=17233#c16

Switched after system upgrade to autologin. It leads to the "good luck" error, journal attached. 
# cat /etc/sysconfig/desktop
DISPLAYMANAGER=sddm
Note the error message: Unable to find autologin session entry ".desktop"

The workaround described in https://bugs.mageia.org/show_bug.cgi?id=17233#c12 (Dave Hodgins) let you recover the desktop.
Comment 9 Lewis Smith 2016-11-10 14:05:09 CET
Ulrich Beckmann  2016-08-20 17:13:26 CEST 
I found a bug regarding autologin.

See the autologin section in /etc/sddm.conf

[Autologin]
User=bequimao
#Session=.desktop
Session=01plasma.desktop

The name 01plasma.desktop refers to the file in
/usr/share/xsession
Comment 10 Lewis Smith 2016-11-10 14:05:47 CET
William Kenney  2016-08-20 19:26:39 CEST 
OK many thanks to Ulrich Beckmann. On my real hardware system ( Comment 3 )
that was booting to the "good luck" error message. The end of the /etc/sddm.conf
file looks like this with no autologin:

.......
......
#Session=
#       Name of the session to automatically log in when the system starts first time.  Default value is empty.
#
#Relogin=
#       If true and User and Session are set automatic login will kick in again on session exit, otherwise it will work  only  the  first  time.
#       Default value is false.
#

#### Mageia-specific configuration

[Users]
MinimumUid=500
# hide system users
# system users using real shells and hence cannot be hidden via HideShells
HideUsers=mysql,apache,mldonkey
HideShells=/sbin/nologin,/bin/false,/usr/sbin/nologin,/bin/true

[Theme]
# use our new custom theme without a userlist
Current=mga-coffee
# use our custom theme based on Maui but with default Mageia background
# Current=mga-maui
# maui is the default theme, when none is specified
#Current=maui
#Current=maldives
#Current=elarun
#Current=numix
#Current=circles
# allow display of user icons from a central system location
# requires accountsservice to be installed which is not the default
# FacesDir=/var/lib/AccountsService/icons/


MCC -> Boot -> enable autologin adds the following to the end of the sddm.conf file:

......
......
# requires accountsservice to be installed which is not the default
# FacesDir=/var/lib/AccountsService/icons/
[Autologin]
Session=.desktop
User=wilcal

Which results in the "good luck" error message on boot and a bricked system.
Under this condition I was able to open a root terminal and command:

vi /etc/sddm.conf

and remove:
[Autologin]
Session=.desktop
User=wilcal

and on reboot the system went back to the manual login mode and I was able to
get back to a working desktop.
Comment 11 Lewis Smith 2016-11-10 14:09:43 CET
William Kenney  2016-08-22 17:09:17 CEST 

As we progress forward on this I will execute a clean new install using
the latest x86_64 boot.iso to a blank harddrive. The platform will be:

Test platform:
Intel Core i7-2600K Sandy Bridge 3.4GHz
GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo
GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB
RTL8111/8168B PCI Express 1Gbit Ethernet
DRAM 16GB (4 x 4GB)
Mageia 5 64-bit, Nvidia driver
Plasma DM

Nvidia driver invoked. Repo will be my local mirror of:
mirrors.kernel.org

rsync'd just minutes before the test. I'll try to do this at least
several times per week or as often as necessary. Testing will be the
same as I executed in Comment #3. After the "good luck" error
manifests itself I will recover the system by removing the three
autologin commands at the end of /etc/sddm.conf See Comment #20

This mornings install resulted in the same "good luck" error.
Recovery was successful.
Comment 12 Lewis Smith 2016-11-10 14:14:10 CET
Ulrich Beckmann  2016-08-22 22:12:53 CEST 

I have filed a bug for the autologin issue
https://bugs.mageia.org/show_bug.cgi?id=19234
There you see a fix to get autologin to work.

[So henceforth, that bug 19234 will be for the auto-login related problem; and subsequent bug 19216 relevant Comments will not be copied to this new bug].
Comment 13 Lewis Smith 2016-11-10 14:14:48 CET
pat leny  2016-08-24 14:01:20 CEST 
hello
i have install mga6 sta1 whit the driver nvidia 367.27;XX on a old pc (pentium 64 ) the graphic card is a gtx 750 ti
after the first boot, the pc and the display is ok (kernel 4.6.3 and nvidia driver 367.27;XX ) .after the update (kernel 4.7.2.... and driver nvidia 367.35....) the display fails and i have the message "Good luck "
Comment 14 Lewis Smith 2016-11-10 14:16:41 CET
Ulrich Beckmann  2016-08-25 08:20:51 CEST 
(In reply to pat leny from comment #38)

Which desktop environment and which display manager? Did you activate autologin?

pat leny  2016-08-25 11:18:23 CEST 
i use plasma 5.7 and the display manager is sddm. the bug is with autologin or not ( but the bug appear when installing the driver nvidia) i have a message than there is a error when the system is installing module

i install the kernel 4.7.2 server and my pc is good now
Comment 15 Lewis Smith 2016-11-10 14:19:30 CET
William Kenney  2016-08-25 19:22:32 CEST 
This morning I went at this with a different platform:

Intel i5
8GB DRAM
Gigabyte: GA-B85M-D3H ( non-Nvidia )
This is one of the most popular MoBo's out there.

Install with x86_64 boot.iso, Plasma ( 08/22/16 )
Local repo mirrored to mirrors.kernel.org just minutes before the test.
Start with a blank drive.

Initial boot resulted in a brief display of the "good luck" error
but then the system proceeded to the Plasma login screen and the login
was successful. Subsequent reboots did not present the "good luck" error.
Comment 16 Lewis Smith 2016-11-10 14:21:11 CET
Mike Rambo  2016-08-26 19:08:54 CEST 
Experienced the 'good luck' message at first boot on a fresh boot-nonfree.iso installation. Removing xorg.conf was all that was required to remedy the problem. Adding or removing auto login did not appear to influence behavior in any way and auto login worked fine.
Comment 17 Samuel Verschelde 2016-11-10 14:21:24 CET
Splitting the bug was necessary, but copying the comments isn't, in my opinion. The new bug report is not really easier to follow. It would be better to have a summary of current findings with links to existing comments, and small quotings if needed.
Comment 18 Lewis Smith 2016-11-10 14:27:02 CET
OK Samuel.
Do you want to - can you - *delete* this new bug? If so, please do. Or hide it.
I tried long ago on the QA mailList to summarise findings, but the problem remains of all comments being put into one bucket. We need as many buckets as possible.
I agree with cross-referring comments from here (or whatever other split bug) to the original, but that original alone is unworkable.
I have time today to work on this (it was agreed I should). So let us agree ASAP what to do.
Comment 19 Samuel Verschelde 2016-11-10 14:29:33 CET
We can't delete bugs, but you can close this one as duplicate or invalid and start a new one. Thanks!
Comment 20 Rémi Verschelde 2016-11-10 14:31:11 CET
(In reply to Samuel Verschelde from comment #19)
> We can't delete bugs, but you can close this one as duplicate or invalid and
> start a new one. Thanks!

Or even better: RESOLVED MOVED.
Comment 21 Lewis Smith 2016-11-10 14:33:36 CET
I will delete this 'invalid'. Can we discuss it immediately on QA IRC?
Comment 22 Lewis Smith 2016-11-10 14:50:23 CET
Closing as 'invalid'. Will re-start the split better.

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

Comment 23 Lewis Smith 2016-11-14 21:35:47 CET
I changed the title a little in the hope that searching will not find this!
See bugs 19781 & 19782 for the real thing.

Summary: Mageia 6: no graphical display, "good luck" error on real hardware => Mageia 6: no graphical display, title changed not to find it


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