Description of problem: I noticed that Mageia 6 screen got black and could not see the login screen.. I tried by getting the brightness up and it didn't work at first. I typed the password (Blindly) and a couple of minutes later I noticed the Welcome To Mageia window appeared.. the screen was hardly recognizable, it was like 85% dark.. So I started clicking on the Brightness key and Voilá.. I got a clean bright screen, but If I reboot I get the same problem. I started modifying the xorg.conf file and was able to make it work, but after upgrading to Mageia 7 Cauldron I got the same problem without making it work with the working xorg.conf file. The only way is to type the password on the black screen, wait until I can see the dark plasma5 screen and press the bightness key.. The only way to make it boot with Mageia 7 was by using nodkmsboot at grub2. Kernel: 4.14.34-desktop-1.mga7 nvidia driver: 390.48 Please Help. Regards
Summary: Login Screen is Black => Login Screen is Black with dkms-nvidia-current - NVIDIA
Summary: Login Screen is Black with dkms-nvidia-current - NVIDIA => Login Screen is Black with dkms-nvidia-current
lspcidrake show the video card as: Card:NVIDIA GeForce 420 series and later: NVIDIA Corporation|GF119M [GeForce 410M] [DISPLAY_VGA] (rev: a1) Using Kernel: 4.14.34-desktop-1.mga
It was the wrong time to upgrade your Plasma install to cauldron :-( You missed neoclust's "[dev] Breaking Cauldron => Qt 5 update" mail from little over a week ago https://ml.mageia.org/l/arc/dev/2018-04/msg00064.html SDDM (the display manager you're most likely using) depends on Qt5, too Neoclust has not yet sent a message that it is safe to update your Qt5 packages. Assigning to KDE team, because of the problem you had before upgrading. Is there anything in your journalctl logs from when you had to blindly type your password?
Assignee: bugsquad => kdeSummary: Login Screen is Black with dkms-nvidia-current => Login Screen is Black with dkms-nvidia-current (mga6=>cauldron upgrade)CC: (none) => marja11
Sorry I didn't answer before.. I was definitely the but you mention and it was fixed in later updates.. I will mark this as Resolved. Thanks
Resolution: (none) => FIXEDStatus: NEW => RESOLVED