You are not logged in.
Hello everyone,
I'm running KDE Plasma + X, but I want to install Wayland. I installed the packages for Wayland from Arch Linux's tutorial. When I start the Wayland session via SDDM, only the KDE cog appears and it doesn't turn either. Only when I keep moving the mouse does the gear turn and at some point the desktop starts.
It looks like the desktop only works as long as I move the mouse. This is also the case on the desktop, because when I start Firefox, for example, nothing happens. Only when I move the mouse continuously does Firefox appear at some point.
I don't want to reinstall ArchLinux, do you have any advice for me?
Kernel: 5.15.10-hardened1-1-hardened
SDDM: sddm 0.19.0-7
NVIDIA: nvidia-dkms 495.46-1
Wayland: wayland 1.20.0-1
Thanks very much!
Offline
Hello,
Well, wayland doesn't work that well for KDE+NVidia. I wouldn't say it's usable right now.
But you should be able to see firefox, have you installed the necessary packages?
gl-wayland 2:1.1.9+r3+g582b2d3-1
kwayland 5.89.0-1
kwayland-integration 5.23.4-1
kwayland-server 5.23.4-1
lib32-wayland 1.20.0-1
plasma-wayland-protocols 1.5-1
plasma-wayland-session 5.23.4-1
qt5-wayland 5.15.2+kde+r38-1
qt6-wayland 6.2.2-1
wayland 1.20.0-1
wayland-protocols 1.24-1
wayland-utils 1.0.0-2
xorg-xwayland 21.1.4-1
In particular the last one (xorg)
Offline
Hello and thanks for the answer. I checked all the packages and they are all installed. Firefox starts in Wayland but I have to keep moving the mouse back and forth. If I let go of the mouse, it seems as if the computer / desktop is no longer working. I would have to make a video of it.
EDIT: Wayland works very well on my notebooks and NVIDIA graphics cards are also installed there. Are there any settings files that I would have to look at?
Last edited by localhorst (2021-12-23 08:19:33)
Offline
I have two machines with AMD graphics and with no proprietary drivers plasma-wayland works fine. Going with amdgpu for me works well for the desktop in recent months. Perhaps others users who do use Nvidia drivers could report on whether they have managed to get plasma-wayland to work with them.
Mike C
Offline
Sorry, I won't be able to help you there. As I am trying to make it work as well, I am also much interested in feedback by others!
Good for you if your laptop works well. Does it use nouveau or nvidia driver?
Offline
I tried to make a video once. I hope you can see the mistake there.
Offline
Sorry, I won't be able to help you there. As I am trying to make it work as well, I am also much interested in feedback by others!
Good for you if your laptop works well. Does it use nouveau or nvidia driver?
Neither nouveau nor Nvidia - but amdgpu:
$ lsmod| grep nouveau
$ lsmod| grep amdgpu
amdgpu 7946240 7
iommu_v2 24576 1 amdgpu
gpu_sched 45056 1 amdgpu
drm_ttm_helper 16384 1 amdgpu
ttm 86016 2 amdgpu,drm_ttm_helper
drm_kms_helper 319488 1 amdgpu
i2c_algo_bit 16384 1 amdgpu
drm
Mike C
Offline
Anyway, like @localhorst , if anybody has a good Wayland + KDE Plasma + Proprietary NVidia installation that works fine, feedbacks are welcome
Offline
You probably already saw this but upstream has a brief set of hints about it: https://community.kde.org/Plasma/Wayland/Nvidia and I noticed they push that you need Nvidia modesetting.
Last edited by mcloaked (2021-12-23 13:17:38)
Mike C
Offline
Yes absolutely. Some problems remains even after enabling modesetting, though. Taskbar icons like ibus integration are not working properly. The taskbar itself lags when I click on it. Windows blink randomly... But we are getting there. A few months will certainly be necessary, still.
Offline
You can't use a wayland session in the first place if you don't enable modesetting, it's a basic requirement.
To be frank lots of these things don't work reliably on AMD either. On a multi monitor setup, menu drop downs are misplaced for native Qt/Wayland windows, taskbar seems to break previews, window rules are improperly/strangely applied (I have a rule to maximise konsole windows vertically, doesn't work on the bigger of the three monitors) and I recently had a unreproducible taskbar crash that didn't lead to a coredump.
Offline
I know a user who has multi-monitor setup and has a few issues with plasma wayland also - so I wonder if that is an area where it gets less testing by kde developers if they don't have the hardware - I have two AMD machines, one being a desktop with an HDMI connected monitor, and the other a laptop and both have been working pretty reliably for some months now for plasma-wayland. The few window rules I have work reliably, and taskbar and panel as well as widgets have not had any issues - of course I may be lucky and not hit the particular ones where bugs have occurred.
Mike C
Offline
It's all very weird. I have 3 computers, all three with ArchLinux.
- Desktop PC: with X and Wayland -> only X works (proprietary driver)
- Notebook 1: only Wayland -> also works with a second monitor (nouveau)
- Notebook 2: X and Wayland, both work, but the second monitor does not work. (proprietary driver)
So I have 3 times ArchLinux with Wayland and on every PC it works differently.
So there seem to be problems with the original NVIDIA drivers after all. It works on the notebook with the nouveau driver. But is the nouveau on the desktop not of much use to me because I can probably no longer play games because of 3D? Unfortunately, I don't know how far 3D is already in the nouveau driver.
Last edited by localhorst (2021-12-24 06:23:11)
Offline