Black Screen with blinking cursor apears 30 seconds after the desktop loads

Greetings,

  • OpenMandriva Lx version: ROME 25.02 x86_64

  • Desktop environment (KDE, LXQT…): KDE Plasma 6.3.1 on real hardware

  • Description of the issue (screenshots if relevant): Around 30 seconds after the desktop loads, the screen turns black with a white blinking line in the top left (which also happens for about 10 seconds after I login in before the splash screen starts) after which I am sent back to the login screen which again turns to black with the white blinking cursor a few moments later which remains present for at least 30 minutes (that’s the longest I waited to see if anything happens, but this is basically where it ends). (Edit while drafting: After a few days and some more boots it became a gamble if the OS boots normally, this happens or it gets stuck right after I choose it from the grub menu)

  • Relevant informations (hardware involved, software version, logs or output…): I am on a Hybrid System (Intel+Nvidia) with the NVidia drivers installed from the Welcome app. Currently the only way to use the desktop successfully is to boot in Console Mode and use startx (found out from this forum post and the same way as that user startplasma-x11 gives $DISPLAY is not set or cannot connect to the X server) though with a significant performance loss in games (and everything that relates to physics moves in slow motion).

  • Files: inxi-F_Output.txt (3.5 KB)

Worth mentioning that this is the third time installing OM (the difference being that this install is the slim version, all of them X11 tho) and it happens every time. First boot I enabled the Extra and Non-Free repos then installed the NVidia drivers. Rebooted then installed some more apps and played some non native games through Proton-GE (which ran very well, some better than on Windows) and after the third boot the problem started happening. From here on out, the only way to make it work would be to either Ctrl Alt F5, login in then use startx, or reboot and boot in Console Mode. (both ways, the output of echo $XDG_SESSION_TYPE becomes tty).

I don’t know if this may affect something but the sddm screen is changed from the default with “Where_is_my_SDDM_theme”.

I have tried to debug with ChatGPT as it was useful when I had problems with Linux and one suggestion was to reset the xorg config file. When I tried I got xorg: command not found but when I searched for packages everything xorg related was installed.

If there is some info that I haven’t provided and may be useful please tell me and I’ll send it as soon as possible. I tried to follow the “How to get better results when posting about problems” as closely as I could.

I am also aware that this post exist but a friend of mine suggested to make another topic. I apolocheese if this may crowd the forum.

1 Like

Welcome! We are glad to see you.

I reinstalled a few times getting past this and right now I am running without my nvidia card, so I am not the one to help with this, but I know someone will be able to help.

So here is what you will have to do. I have had this problem. It is a problem with sddm.

You will have to alt-f3 into terminal
Then Log in
uninstall sddm (plasma6-sddm I believe)
and install lightdm. sudo dnf in lightdm

That fixes that, there is a major bug within sddm for all systems it seems

If you do that, you will have to start by

sudo systemctl disable sddm.service

and finish with

sudo systemctl enable lightdm.service

and reboot

1 Like

I had the same problem with lx 5.0 xfce4 spin. When the screen went black I could use all the apps if I new the kbd shortcuts, Alt-f3 for ‘app finder’ dialog for example. The app would show perfectly but the desktop would stay black. It seemed to happen whenever upgrade to 6.13 kernel. I’ve been using 6.12 kernel for week+ now, no problem. I didn’t get here for this problem, so I’m sorry I don’t have any of the error msgs. It seemed to be a problem with the 6.13 and X11.
I just upped to 6.13 today and so far ok.

1 Like

Welcome! We are glad to see you here.

Thank you, glad to be here…

1 Like

I am running ROME 25.02 x86_64, plasma (also LXQt on another partition) and up to date with an Hybrid config. (AMD+Nvidia), on my side it is running better and much more stable with open kernel module rather than the proprietary driver.

1 Like

And Welcome to OpenManriva btw :+1:

1 Like

I have tried many things to solve that problem, currently only one help in my case - using kernel-server instead of kernel-desktop package and boot option in grub. Install kernel-server package using dnf, then in grub menu advanced options choose kernel-server-omxxxx and run. Until nvidia or sddm will fix this I am going to use this kernel version.

I have used pastorczo13 solution (along with WilsonsPhillips’ tip) and currently it is stable (I still have the slow motion issue in a game but I’ll fiddle with Proton versions to try and fix it). The only thing is that now the black screens when I Alt Tab from a full screen app and on the splash screen (when I believe it changes from Wayland to X11) is now the Flower Background that the Grub Menu uses, which is not really a problem but it’s something. Wanted to try what engine suggested but when I want to install “kernel-server” (and an nvidia related dependency) I get none of the providers can be installed.

Also, I don’t know if this is related but after this DnfDrake fixed itself and is now not bigger than my monitor.

Thanks for the Welcomes btw!

1 Like

You can install protonplus in the repos and use the protonge latest version

1 Like

I have GE-Proton9-25 (which is currently the latest as far I can see) as my default on Steam.
I installed it with ProtonUp-Qt tho but I don’t think it makes a difference, didn’t knew about ProtonPlus but I’m going to use that one from now.
I did a distro sync then rebooted and the slow motion problem got fixed once (after 20 minutes of Vulkan Shaders processing) tho now it continues again.

Did you try Steam’s verifying data integrity on that game’s files ?

Yep, verified the files, purged my mods and verified again, tho I fixed it. Apparently it was because of the launch option arguments that I set which should’ve helped with performance but I guess they did the exact opposite.