Mageia forum

Having run a update on a SSD, then doing the same for another partition using a HDD then doing an update for Windows also on a HDD I started my primary system only to see that I only had a full screen tty1 login as a command prompt.

So tried running sddm - failed, then did a sudo sddn but found looking at a created file it was owned by root - so that idea failed.

What is the correct way of restoring the KDE gui on boot up ?

This is causing a lot of problems so in the meanwhile I am using my secondary HDDD MGA9 boot, but there are a lot of software / packages not installed and worse it is running on a WD Red HDD - very slow.


How do I fix this ?

it may be that your graphics card driver is not being loaded.

log in as your normal user at the tty and then change to root:

Code: Select all

$ su -
Password:

and enter the root password,

or login as root.

then run

Code: Select all

drakx11

and check all settings are correct.

be sure to not run the test function, and check that

Code: Select all

[X] Automatically start the graphical interface (Xorg ) upon booting

has the [X]

check also to see if there is a

Code: Select all

/home/your_user_name/.Xauthority

file, and if so, delete it

Also check that you have task-plasma-minimal installed, to make sure you have at least a complete minimal Plasma desktop installed.

The run drakx11 did the trick, the run gui option was not set.

I do not understand why it lost the setting though but many thanks for the suggestion.

Vincent

Would you mark your topic as [SOLVED]? Thanks.

vbcoen wrote:I do not understand why it lost the setting

apart from the usual suspects ( cosmic rays and Murphy and His Laws ), an update that included Nvidia drivers, ( and DKMS ), grub and or the kernel are also good suspects.
if you had rebooted after a kernel update that required a grub update, but before grub updated, this could have caused the issue, but I am clutching at straws here, because there is so little information given.

you should also consider a HDD/SSD failure, so check for failed sectors.

perhaps the output of

Code: Select all

$ rpm -qa --last | grep 'date_of_update'

as this would give a list of installed packages installed just prior to the issue.

e.g.

Code: Select all

$ rpm -qa --last | grep '23 Mar 2025'

for me lists all packages installed on that date ( 31 packages )