This bug supersedes bug 19216 https://bugs.mageia.org/show_bug.cgi?id=19216 by separating reports between: - real hardware - VBox [this bug] 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 on 32bit host - i586 on 64bit host - x86_64 on 64bit host - What VBox graphics equivalent? - 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 - vboxvideo.nomodeset - Is 'vboxvideo' blacklisted in /etc/modprobe.conf ? - 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.
@ 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 19782 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) => TRACKERCC: (none) => kde, kernel, mageiatools, marja11
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=19781
CC: (none) => hhielscher
CC: (none) => mageia
Host: Hardware: Lenovo ThinkPad W701 Software: x86_64 VisualBox 5.1..2_OSE r108956 Guest: Kernel: 4.8.10-desktop-3.mga6 Booting to KDE Plasma failed Before update to kernel 4.8.10 booting with kernel 4.8.2 succed but after update even kernel 4.8.2 failed. Installed GDM No succes to boot. Again get the message: Sorry, but there has been a problemstarting your grafical display Installed GDM succes to boot
CC: (none) => jan
Couldn't loggin as normal user, only as root
@ Jan, Please file a separate bug report :-) This one is a _tracker_ In trackers, we do not comment about related bugs we find. Instead, we let the tracker depend on the bug reports it tracks. See e.g. tracker bug 17523 (Adding "[TRACKER]" to the summary, in case the TRACKER keyword alone isn't clear enough)
Summary: Mageia 6 VBOX: "Good luck" failure to start graphical interface, display manager => [TRACKER] Mageia 6 VBOX: "Good luck" failure to start graphical interface, display manager
Depends on: (none) => 19834
CC: (none) => ngompa13Depends on: 19834 => (none)Summary: [TRACKER] Mageia 6 VBOX: "Good luck" failure to start graphical interface, display manager => [TRACKER] Mageia 6 Virtualized: "Good luck" failure to start graphical interface, display manager
Priority: Normal => release_blocker
Assignee: bugsquad => pkg-bugs
Status comment: (none) => Waiting for new 6 sta2 ISOs for tests of the current state
Depends on: (none) => 19833
CC: (none) => bittwister2Depends on: (none) => 19771
Depends on: 19833 => (none)
It should be fixed now.
Status comment: Waiting for new 6 sta2 ISOs for tests of the current state => Should be fixed since the 30th of November
QA Contact: (none) => stormi
Since change to KDM I doesn't get the "good luck" message
(In reply to Jan Pihlgren from comment #6) > Since change to KDM I doesn't get the "good luck" message You shouldn't have the error with sddm either now.
I encounter the bug this week, in Bios mode. Trying to update it, the VM is now completely unusable and I'm unable to help with more information.
CC: (none) => yves.brungard_mageia
Found a mean to get something without splash option. Note that I have no more the good luck message. Host:Mageia 5, Intel graphic card VirtualBox : Version 5.0.20_OSE r106931 Guest: kernel 4.8.12-desktop-1 x86_64 By switching to a console, I installed xdm and switched to it with drakdm. No success. The system seems to loop trying something again and again.
CC: (none) => dglent
(In reply to papoteur from comment #9) > Found a mean to get something without splash option. > Note that I have no more the good luck message. > > Host:Mageia 5, Intel graphic card > VirtualBox : Version 5.0.20_OSE r106931 > > > Guest: > kernel 4.8.12-desktop-1 x86_64 > > By switching to a console, I installed xdm and switched to it with drakdm. > No success. > The system seems to loop trying something again and again. Please create a dedicated bug report. I'm closing this tracker since the bug it is about was fixed. Attaching /var/log/Xorg.0.log and the output of journalctl -ab as root, to the new bug report, might help diagnosing the issue.
Status: NEW => RESOLVEDResolution: (none) => FIXED