KDE black screen

biggynb · 2025-02-13 05:04:39

sddm works normally, but when I log in to Plasma using sddm, the only thing on my screen is my mouse cursor. My mouse can move normally, but there is nothing else on my screen. There are no (EE)s in /var/log/Xorg.0.log. I tried using hyprland, but I was kicked out of the WM 3 seconds after I logged in using sddm.

GPU: AMD 6500XT

seth · 2025-02-13 08:15:30

https://bbs.archlinux.org/viewtopic.php?id=57855

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General (all of it!)
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

steak · 2025-02-13 11:59:43

i just upgraded and i'm getting a black screen as well i get a mouse but no log in i have to switch tty and login using startplasma-wayland

journalctl: https://0x0.st/8ZIU.txt

xorg: https://pastebin.com/w2ti2Hed

i also just upgraded using pacman -Syu and had no visible errors before upgrading

Last edited by steak (2025-02-13 12:01:28)

biggynb · 2025-02-13 12:42:17

xorg log (The warnings and errors): https://pastebin.com/0qzhTuGs

seth · 2025-02-13 16:15:48

The warnings and errors

isn't very useful, but there're no obvious problems in steak's log (while you have some page flip errors - the two of you seem to use different HW, steak runs nvidia)

@steak, you're running plasma on wayland, though?

Feb 13 06:04:47 steakmachine kwin_wayland[2139]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
Feb 13 06:04:47 steakmachine kwin_wayland[2139]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Feb 13 06:04:47 steakmachine kwin_wayland[2139]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Framebuffer name must be generated before being bound.
Feb 13 06:04:47 steakmachine kwin_wayland[2139]: kwin_scene_opengl: 0x506: GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid because a bound framebuffer is not framebuffer complete.
…
Feb 13 06:07:01 steakmachine kwin_wayland[2139]: kwin_core: Failed to open /dev/dri/renderD128 device (No such device)
Feb 13 06:07:01 steakmachine kwin_wayland[2139]: kwin_wayland_drm: failed to open drm device at "/dev/dri/renderD128"
Feb 13 06:07:01 steakmachine kwin_wayland[2139]: kwin_wayland_drm: failed to open drm device at ""
Feb 13 06:07:01 steakmachine kwin_wayland[2139]: kwin_wayland_drm: failed to open drm device at ""
Feb 13 06:07:01 steakmachine kwin_wayland[2139]: kwin_wayland_drm: failed to open drm device at ""
Feb 13 06:07:01 steakmachine kwin_wayland[2139]: kwin_wayland_drm: failed to open drm device at ""

Feb 13 06:03:28 steakmachine kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
Feb 13 06:03:28 steakmachine kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
Feb 13 06:03:28 steakmachine kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
Feb 13 06:03:28 steakmachine kernel: nvme 0000:03:00.0: platform quirk: setting simple suspend
Feb 13 06:03:28 steakmachine kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
Feb 13 06:03:29 steakmachine systemd[1]: Started Simple Desktop Display Manager.

Add "nvidia_drm.modeset=1" to the https://wiki.archlinux.org/title/Kernel_parameters - it /has/ to be there, not! in some modprobe.conf.
If that alone doesn't help, also try "nvidia_drm.fbdev=0"

steak · 2025-02-14 01:19:06

Add "nvidia_drm.modeset=1" to the https://wiki.archlinux.org/title/Kernel_parameters - it /has/ to be there, not! in some modprobe.conf.
If that alone doesn't help, also try "nvidia_drm.fbdev=0"

tried this still no dice i tried running it at boot and found the arch.conf file since im running systemd( at least i think i am because i could find arch.conf the only thing is i didnt find the file in (/boot/loader/entries/arch.conf) i found it in (/usr/share/systemd/bootctl/) )

there is this file in /boot/loader/entries/ 2025-02-05_05-05-42_linux.conf cause i installed using archinstall should i put them there even if they didnt work putting them in at boottime?

biggynb · 2025-02-14 04:35:10

The issue is solved for me by reinstalling archlinux.
Should I left it open for steak?

Nestor_013 · 2025-02-14 09:05:31

Same here... Black screen with Wayland, working on X11. I've set the nvidia_drm stuff as mentioned.
Here are my
- boot log: http://0x0.st/8NiK.txt
- xorg.log: https://pastebin.com/2wKbk5JG

I noticed the reservation of 24GB of memory by nvidia, which seems a bit odd too me since I don't have that memory.

Thanks for any help...

Nestor_013 · 2025-02-14 10:03:50

I followed this: https://bbs.archlinux.org/viewtopic.php … 9#p2226369 and this seems to have done the job...

steak · 2025-02-14 16:36:54

i also tried deleting kwinoutputconfig.json to no avail ^

Nestor_013 · 2025-02-14 17:03:54

Digging a bit more... it sounds to be related to ICC. I've rebuilt my ICC with Displaycal... then reapplied. All worked fine.

And now suddenly 'blackout'. And no simple way to come back, except by re-deleting the ICC profile and emptying .config/color.jcnf.
Why did it happen ? Mystery !!! The only thing I can think of is that the night light started to activate...

steak · 2025-02-14 17:33:37

Nestor_013 wrote:

Digging a bit more... it sounds to be related to ICC. I've rebuilt my ICC with Displaycal... then reapplied. All worked fine.
And now suddenly 'blackout'. And no simple way to come back, except by re-deleting the ICC profile and emptying .config/color.jcnf.
Why did it happen ? Mystery !!! The only thing I can think of is that the night light started to activate...

i didnt think i had that installed and i dont have that file.

steak · 2025-02-14 17:36:11

im not entirely against reinstalling but ive already reinstalled like 3 times in the past month luckly i have settings and what not backed up on my server.

Nestor_013 · 2025-02-14 17:52:16

@steak: I'm far from an expert... just trying to solve my own problems too without reinstalling

For the record, I've made the experiment to re-enable NightLight and bam. I'll live without it.
So, on my system, there is something there, but what ???

seth · 2025-02-14 20:38:52

@biggynb you can just tag the thread as solved, it'll remain open for posting

@steak, please post an udpated system journal, you (or rather KDE) were missing drm devices - can you run kde on X11?
In that case please also post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

steak · 2025-02-14 21:22:46

seth wrote:

@biggynb you can just tag the thread as solved, it'll remain open for posting
@steak, please post an udpated system journal, you (or rather KDE) were missing drm devices - can you run kde on X11?
In that case please also post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

its missing the "nvidia_drm.modeset=1" and "nvidia_drm.fbdev=0" as ive rebooted since then and as i said it tried at boot time.
http://0x0.st/8NB_.txt i have no idea ive been running wayland since i installed like 3 weeks ago.

this is when i try xinit and startplasma-x11
https://imgur.com/a/NAqSvXz

if theres another way to start x11 i have no clue( im going off super old memories just did get back into linux).

also if youd like i can do a reboot with those in at boot time if youd like to see the change there to show you for good faith.

Last edited by steak (2025-02-14 21:47:34)

steak · 2025-02-14 21:24:01

Nestor_013 wrote:

@steak: I'm far from an expert... just trying to solve my own problems too without reinstalling
For the record, I've made the experiment to re-enable NightLight and bam. I'll live without it.
So, on my system, there is something there, but what ???

nah u cool i was just saying things suggested so incase that comes up as a question u all good my dude/ette

seth · 2025-02-15 10:04:48

http://0x0.st/8NB_.txt has neither of those parameters either?
It also

root=/dev/ArchinstallVg/root

looks like it's some intallation system?

The system ran for almost 24h and only at the end starts to crash in numerous nullptr resolutions and is generally a mess.
=> reboot w/ those parameters set, log into plasma, witness the blackscreen and then immediately post that journal.

_Six-VI · 2025-02-15 20:19:10

Nestor_013 wrote:

Digging a bit more... it sounds to be related to ICC. I've rebuilt my ICC with Displaycal... then reapplied. All worked fine.
And now suddenly 'blackout'. And no simple way to come back, except by re-deleting the ICC profile and emptying .config/color.jcnf.
Why did it happen ? Mystery !!! The only thing I can think of is that the night light started to activate...

Since I ended up on this same thread finding what happened and whether this is a known issue, but for anyone who ends up on this thread with calibrated screens this could be the cause. However I haven't had issues with random blackouts though. Although for me this was after a full system update (And then restart) that I do every Saturday.

I had to do the same thing as this quoted post, I removed the calibration profiles and everything was displaying correctly again but I was aware of the new KDE update on Plasma initially so my suspicion was there (And I use Wayland with AMD CPU and GPU so not an Nvidia issue). I already had two user profiles and noticed the issue only affected one user login and not the other, the other user I intentionally created and never use it to test stuff like this and doesn't have any ICC profiles set up. I renamed the folder where I keep my calibration profiles (So they can't be accessed or used) and now all issues with the screens are gone. Before all of this my main user profile was working with one screen off and my primary screen on, when I modified the color accuracy setting from "color efficiency" to "color accuracy" for the primary screen it went black too and I could only use the system via TTY afterwards but this is how I figured out it was a setting with KDE or something KDE was interacting with.

Testing with a newly generated profile I found that efficiency mode is fine, and it's actually the color accuracy mode in the new KDE Plasma update that makes the screen go black (With another calibration I made both efficiency and accurate makes screen go black. KDE bug report here with more specifics of my issue, I found it today: https://bugs.kde.org/show_bug.cgi?id=499789

And yep I deleted kwinoutputconfig.json initially and this didn't fix it for me, I would then restart the PC and a new generated one with the calibration profile paths was automatically generated, I tried editing this file too to remove the ICC profile paths but then it would re-add it again itself so I ended up just renaming the folder with the ICC profiles inside so they couldn't be used. My old profiles were well overdue being updated anyway so I may as well redo them.

A bit of a long message, it is solved for me so nothing to help me with but just wanted to add this in case anyone comes across this thread like I did looking to clarify the cause of the issue, even though I know this thread issue is not the same I wasn't going to make a new thread just to say all this.

Last edited by _Six-VI (2025-02-16 17:33:00)

steak · 2025-02-15 20:42:03

seth wrote:

http://0x0.st/8NB_.txt has neither of those parameters either?
It also
root=/dev/ArchinstallVg/root
looks like it's some intallation system?
The system ran for almost 24h and only at the end starts to crash in numerous nullptr resolutions and is generally a mess.
=> reboot w/ those parameters set, log into plasma, witness the blackscreen and then immediately post that journal.

its an LV thats my main drive, i installed using archinstall off the livecd

heres a very new copy of the xorg logs

https://0x0.st/8NyD.txt

also still black screen with mouse.

Last edited by steak (2025-02-15 20:44:19)

seth · 2025-02-15 22:50:01

The problem is only w/ SDDM, you can run KDE from the console "fine" (the session looks like it end up being degraded, but you can see something?)

Feb 15 15:37:03 steakmachine sddm[2021]: The configured theme "default" doesn't exist, using the embedded theme instead

And it doesn't look like any greeter starts, also make sure your disk isn't full: https://wiki.archlinux.org/title/SDDM#B … eter_shows

steak · 2025-02-15 23:08:56

seth wrote:

The problem is only w/ SDDM, you can run KDE from the console "fine" (the session looks like it end up being degraded, but you can see something?)
Feb 15 15:37:03 steakmachine sddm[2021]: The configured theme "default" doesn't exist, using the embedded theme instead
And it doesn't look like any greeter starts, also make sure your disk isn't full: https://wiki.archlinux.org/title/SDDM#B … eter_shows

i tried reinstalling SDDM and regen'd the profile to no avail. none of the partitions on myserver are over 60% used and the largest one i have used is efivarfs /home is at 53% and / is at 49%.

im not specifically tied to SDDM can i just swap to say GDM or LightDM?

i dont know if this at all relevant either but when it goes to sleep/screens turn off the lockscreen works fine dont know if that kdeplasma handling that or sddm ( after ive logged in and started the system through cli)

Last edited by steak (2025-02-16 00:20:33)

seth · 2025-02-16 08:55:18

im not specifically tied to SDDM can i just swap to say GDM or LightDM?

Yes, do you need a DM at all?
https://wiki.archlinux.org/title/Getty# … al_console
https://wiki.archlinux.org/title/Start_X_at_login
https://wiki.archlinux.org/title/KDE#From_the_console
Make sure

echo $DBUS_SESSION_BUS_ADDRESS

says sth. like

unix:path=/run/user/1000/bus

and "loginctl session-status" reports the session as active, otherwise you don't be able to shutdow the system from there etc.

SDDM ships w/ two themes, elarun and maya - does either of them work?
Resp. plasma ships breeze?
https://wiki.archlinux.org/title/SDDM#T … g)_a_theme

The screenlocker and sddm are made to look similar but are completely different processes.

steak · 2025-02-19 19:58:43

seth wrote:

im not specifically tied to SDDM can i just swap to say GDM or LightDM?
Yes, do you need a DM at all?
https://wiki.archlinux.org/title/Getty# … al_console
https://wiki.archlinux.org/title/Start_X_at_login
https://wiki.archlinux.org/title/KDE#From_the_console
Make sure
echo $DBUS_SESSION_BUS_ADDRESS
says sth. like
unix:path=/run/user/1000/bus
and "loginctl session-status" reports the session as active, otherwise you don't be able to shutdow the system from there etc.
SDDM ships w/ two themes, elarun and maya - does either of them work?
Resp. plasma ships breeze?
https://wiki.archlinux.org/title/SDDM#T … g)_a_theme
The screenlocker and sddm are made to look similar but are completely different processes.

as much as i enjoy typing i prefer to have a graphical UI to log into i know i can do startplasma-wayland i tried -x11 and it threw an error because it didnt have defined display to launch to.
so i installed the aur package for the sddm-git and it seems to work about 50% of the time and im still working out the reason the virtual keyboard wants half the screen. but if i log out sddm crashes and i have to swap ttys again and log in using cli so i think my issue is somewhere related to a bug with sddm and less something i did

seth · 2025-02-20 08:57:29

For X11 you'd autologin and implicitly run startx, you don't type anything but boot straight into an (optionally locked) KDE session.
Have you tried a different SDDM theme?

Arch Linux

#1 2025-02-13 05:04:39

KDE black screen

#2 2025-02-13 08:15:30

Re: KDE black screen

#3 2025-02-13 11:59:43

Re: KDE black screen

#4 2025-02-13 12:42:17

Re: KDE black screen

#5 2025-02-13 16:15:48

Re: KDE black screen

#6 2025-02-14 01:19:06

Re: KDE black screen

#7 2025-02-14 04:35:10

Re: KDE black screen

#8 2025-02-14 09:05:31

Re: KDE black screen

#9 2025-02-14 10:03:50

Re: KDE black screen

#10 2025-02-14 16:36:54

Re: KDE black screen

#11 2025-02-14 17:03:54

Re: KDE black screen

#12 2025-02-14 17:33:37

Re: KDE black screen

#13 2025-02-14 17:36:11

Re: KDE black screen

#14 2025-02-14 17:52:16

Re: KDE black screen

#15 2025-02-14 20:38:52

Re: KDE black screen

#16 2025-02-14 21:22:46

Re: KDE black screen

#17 2025-02-14 21:24:01

Re: KDE black screen

#18 2025-02-15 10:04:48

Re: KDE black screen

#19 2025-02-15 20:19:10

Re: KDE black screen

#20 2025-02-15 20:42:03

Re: KDE black screen

#21 2025-02-15 22:50:01

Re: KDE black screen

#22 2025-02-15 23:08:56

Re: KDE black screen

#23 2025-02-16 08:55:18

Re: KDE black screen

#24 2025-02-19 19:58:43

Re: KDE black screen

#25 2025-02-20 08:57:29

Re: KDE black screen

Board footer