[SOLVED] KDE Plasma Wayland Black Screen With Cursor.

Samcon30 · 2024-09-28 00:15:24

Hi, I have encountered an issue where when I login via sddm into my plasma–wayland desktop, I get a blackscreen with my cursor and nothing else. I’ve been using the system for a few years (Kinda, actually had an issue before which neccesitated a full reinstall a few weeks ago) and haven't encountered this before. For what happened leading up to this issue, I will explain. For a while I've had issues with plasma Wayland. Nothing major just if my system ever goes to sleep or screen blanks it just breaks. I commonly go into terminal and stop it and start it via kstart. By “break” I mean my background is gone and no icons appear unless I hover over them, and it commonly just stops producing audio. It hasn't hindered me that much so I haven't tried to fix it. In any case, I commonly leave my system on for multiple days at a time usually without updating. I don't have a specific reason yet, I used to run various server softwares (Stash, jellyfin, etc) and a website but don't since the reinstall I just kept doing it. In any case, It had been a few days so I decided I would update my system and let it reboot. I took it off the screen blanking by moving my mouse restarted kde plasma Wayland and updated via sudo pacman -Syu, how I have updated many times before. Once it was done I rebooted via sudo reboot to the issue I now have now. I get into sddm, put in my login info, and get nothing. At first I thought maybe something went wrong with the update somehow even though it didn't say anything. So I entered a terminal via Ctrl alt f1 f3 and logged in as root and updated again. Of course that didn't work, so I used pacman -Qnp | pacman -S - to reinstall all base system packages, rebooted and nothing. Tried just reinstalling my nvidia driver as I heard that could be the issue (I use official Nvidia driver). No change. I considered perhaps the driver updated and it broke something maybe I just need a downgrade, unfortunately I had not installed the automatic system for it and yay wouldn't. With the error libalpm.so.14: cannot open shared object file: No such file or directory. I did run that command in my user account. I did run journalctl, I didn't see anything abnormal except for a long list of The same error saying kwin_wayland_drm failed to create framebuffer invalid argument. And that's where I am now. Thank you to anyone who attempts to help me with this, it is greatly appreciated.

Last edited by Samcon30 (2024-09-28 21:38:30)

Samcon30 · 2024-09-28 02:10:40

GPU is an RTX 2060 Super, Using Linux-Zen.

seth · 2024-09-28 08:01:47

https://en.wikipedia.org/wiki/Paragraph
You're post is just rambling about what you randomly do in a day and paraphrase some things you saw
Try to structure your thoughts before writing them down.

With the error libalpm.so.14: cannot open shared object file: No such file or directory.
The same error saying kwin_wayland_drm failed to create framebuffer invalid argument.

libalpm is at .15 w/ pacman 7 and apparently your GPU configuration is also broken.
Please post your complete system journal for the boot and your package integrity

sudo journalctl -b | curl -F 'file=@-' 0x0.st
sudo LC_ALL=C pacman -Qkk |& grep -v ', 0 altered files' | grep -v backup > /tmp/howbadisit.txt
cat /tmp/howbadisit.txt | curl -F 'file=@-' 0x0.st

FarStar07 · 2024-09-28 12:34:46

Hello,
Isn't it the same problem as described here? => Kwin - stopped loading with black screen and mouse cursor only.
https://bbs.archlinux.org/viewtopic.php?id=299450

seth · 2024-09-28 12:44:43

Maybe.
The thread seems to be about nvidida-open, though?
To block the simplydumb device, you can just enable https://wiki.archlinux.org/title/NVIDIA … de_setting and use the "nvidia_drm.modeset=1" kernel parameter (modprobe.conf won't do!) which everybody should just do unconditionally because that thing serves no actual purpose but getting in the way.

Samcon30 · 2024-09-28 19:55:29

Sorry for being a bit rambly. A little stressed a frazzled. Not entirely sure I executed these peoperly. Also, if there's a way to upload them here directly please tell me. This is my first time posting in the form. The result of the first command:
https://drive.google.com/file/d/1uIZ74t … p=drivesdk

And this is the result of the second/third:
https://drive.google.com/file/d/1uIMpuk … p=drivesdk

seth · 2024-09-28 19:58:42

Also, if there's a way to upload them here directly please tell me.

The commands I posted handed you some 0x0.st urls, you can just share those.

Samcon30 · 2024-09-28 20:00:55

Oh, ok. I didn't realize. Here.
http://0x0.st/Xgbt.txt
http://0x0.st/Xgb6.txt

seth · 2024-09-28 20:20:03

https://bbs.archlinux.org/viewtopic.php?id=299450
Can you still boot w/ the LTS kernel?
(Don't forget to install nvidia-lts as well)

Samcon30 · 2024-09-28 20:21:59

Sorry, I've used Arch for a few years now, but I'm still pretty much a noob. How would I go about doing that?

Samcon30 · 2024-09-28 20:25:24

Switching to lts kernal I mean.

seth · 2024-09-28 20:29:27

You install it, add it to your bootloader and select it when booting.

Samcon30 · 2024-09-28 21:14:21

I can. I did just that switched to the LTS kernal, And I'm into KDE Plasma Wayland.

seth · 2024-09-28 21:27:00

Probably same as https://bbs.archlinux.org/viewtopic.php?id=299450 then

Samcon30 · 2024-09-28 21:30:15

So the ultimate solution is to use the LTS kernal untill the patch currently in testing is applied to the current kernals and nvidia-dkms?

seth · 2024-09-28 21:35:22

"kernel" but otherwise yes - the alternatives would be to build the package yourself or switch to the testing repos, nb. the latter is an all-or-nothing move, don't just install random packages from the testing repos in isolation.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Samcon30 · 2024-09-28 21:37:05

No thank you. I probably wouldn't have even thought to try that.

pxeger · 2024-10-04 08:10:13

This seems to be properly fixed - at least for me - with the latest nvidia (560.35.03-10)

Arch Linux

#1 2024-09-28 00:15:24

[SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#2 2024-09-28 02:10:40

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#3 2024-09-28 08:01:47

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#4 2024-09-28 12:34:46

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#5 2024-09-28 12:44:43

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#6 2024-09-28 19:55:29

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#7 2024-09-28 19:58:42

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#8 2024-09-28 20:00:55

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#9 2024-09-28 20:20:03

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#10 2024-09-28 20:21:59

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#11 2024-09-28 20:25:24

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#12 2024-09-28 20:29:27

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#13 2024-09-28 21:14:21

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#14 2024-09-28 21:27:00

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#15 2024-09-28 21:30:15

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#16 2024-09-28 21:35:22

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#17 2024-09-28 21:37:05

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

#18 2024-10-04 08:10:13

Re: [SOLVED] KDE Plasma Wayland Black Screen With Cursor.

Board footer