My problem is: Black screen with only cursor when I boot to Wayland session. I searched on the net and found solutions which didnt work for me so I decided to ask here. I can run Konsole on Wayland session when I move cursor up left and than type konsole to run it, I can run Yandex.Browser to, Dolphin, dnfdragora and YumEx but it cant remove or install any package.
I am desperate to solve this… Need help.
Edit:
[stefanm@Draguljche-PC ~]$ journalctl /usr/bin/plasmashell -f 2> plasmashell.log
Jul 19 17:04:47 Draguljche-PC plasmashell[6739]: kf.plasma.quick: Applet preload policy set to 1
Jul 19 17:04:47 Draguljche-PC plasmashell[6739]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:195:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
Jul 19 17:04:47 Draguljche-PC plasmashell[6739]: Toolbox not loading, toolbox package is either invalid or disabled.
Jul 19 17:04:47 Draguljche-PC plasmashell[6739]: [destroyed object]: error 7: importing the supplied dmabufs failed
Jul 19 17:04:47 Draguljche-PC plasmashell[6739]: The Wayland connection broke. Did the Wayland compositor die?
Jul 19 17:04:48 Draguljche-PC plasmashell[6875]: kf.plasma.quick: Applet preload policy set to 1
Jul 19 17:04:48 Draguljche-PC plasmashell[6875]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:195:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
Jul 19 17:04:48 Draguljche-PC plasmashell[6875]: Toolbox not loading, toolbox package is either invalid or disabled.
Jul 19 17:04:48 Draguljche-PC plasmashell[6875]: [destroyed object]: error 7: importing the supplied dmabufs failed
Jul 19 17:04:48 Draguljche-PC plasmashell[6875]: The Wayland connection experienced a fatal error: Protocol error
If you don’t find what you are looking for, try an Internet search. One can find out a lot from documentation or forum posts at other Linux distros. If user finds something written for another distro but you have some doubt ask at OpenMandriva Chat.
For serious technical issues and package/feature requests please file a bug report here.
Note: We are a small group. All the contributors and developers here are unpaid volunteers.
You can make OpenMandriva grow and improve by getting involved
Any help with testing would be appreciated whether one is technically proficient or a very non-technical user. The more people and more hardware we can get involved the better we can make OMLx releases and packaging. We do a lot of testing in VM’s as well. Developers tend to use Qemu, most user level testers use VirtualBox.
We probably need more details to problem solve this. Does system boot using X11? That would be first thing to try. Booting the Plasma6 Wayland iso? Booting an installed system using Wayland? If installed system is it existing system recently upgraded or fresh install? Which nvidia drivers in use? How was Wayland installed? the plasmashell lines in journal look like there is some software missing.
Your post implies you are on hardware. If you are trying to use Wayland in VirtualBox it is unlikely that will work. Probably same for VMWare but I do not know much about VMWare.
Edit: Is there any information in wayland-session.log (in /home/yourusername/.local/share/sddm)? You can post that log here as a .txt file. Also post:
journalctl -b > journal-wayland-boot-fail.txt
And post the file created here.
If you boot to terminal (console mode shown here):
I will try that tonight or tomorow. Right now Im busy. I installed .run file from Nvidia Driver Version: 555.58.02. It is the same as Driver from OM repos, and its working. On wayland and X11. On wayland no black screen and everithing seems to work fine, I didnt try gaming yet. It would be better if OM Nvidia driver from Repos work…
Thanks for reporting this issue. What this problem really needs is a bug report so developers can dig in to why this happened. The workaround you used by installing the driver from nvidia.com is great but won’t solve the issue for other OM users. But the fact you did that and it works helps with problem solving.
What iso did you use to install, if possible what is the build ID number? There may be some problems with the Wayland iso itself.
Or if you installed the X11 iso and added wayland what command did you use to do that? What command did you use to install OM nvidia driver?
Edit: I just went through testing of ROME Plasma6 Wayland iso #3247 and I do not believe there would be anything on the iso that would cause a problem related to @Draguljche’s issue. Unless there is some package missing from the install or something I am not knowledgable enough to see. This should, as far as I know, apply to earlier ROME Wayland isos. We still need to know if install was from Wayland or X11 iso and what command used to install OM nvidia drivers.
Yeah it is earlier ISO, I cant remember what I was downloaded Build 3200 or Build 3156. This is wayland only ISOs. I tried with YumEx and with command line. And I installed nvidia-dkms-kmod which installs all other deps for Nvidia.
Edit: Command linue means sudo dnf install nvidia-dkms-kmod. And yeah I installed dkms package as well.
I do not have nVidia hw and can not test beyond whether packages will install. I do not know if nvidia-dkms-kmod works properly, as I recall I have read people saying it does not. You might try instead sudo dnf in nvida or this:
In OM wiki ROME Errata page it does not tell user how to install nvidia drivers but if I remember correctly either installing from OM Welcome or sudo dnf in nvidia is what works. Which means that the nvidia package has to be updated for new kernel installation. I know OM devs have seemed to be more diligent in seeing that the nvida packages are updated with new kernel updates.
We would like to know if either of these methods work. Also we always need help if anyone with nvidia hw wants to help with building or testing these drivers.
Installing : nvidia-modprobe-555.58.02-2.x86_64 11/13
Running scriptlet: nvidia-persistenced-555.58.02-2.x86_64 12/13
groupadd: invalid group ID '/usr/bin/nvidia-persistenced'
useradd: invalid user ID '/usr/bin/nvidia-persistenced'
Installing : nvidia-persistenced-555.58.02-2.x86_64 12/13
warning: user nvidia-persistenced does not exist - using root
warning: group nvidia-persistenced does not exist - using root
Installing : nvidia-555.58.02-2.x86_64 13/13
Running scriptlet: nvidia-555.58.02-2.x86_64 13/13
warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.exec(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
login.defs specifies UID allocation range 101–999 that is different than the built-in defaults (1–999)
login.defs specifies GID allocation range 101–999 that is different than the built-in defaults (1–999)
Creating group 'nvidia-persistenced' with GID 976.
Creating user 'nvidia-persistenced' (NVIDIA persistent software state) with UID 976 and GID 976.
Installed:
lib64crypto1.1-1.1.1m-1.x86_64 lib64nvidia-egl-wayland1-1.1.13-2.x86_64
libx11_6-1.8.9-1.x86_64 libxau6-1.0.11-1.x86_64
libxcb1-1.17.0-1.x86_64 libxdmcp6-1.1.5-1.x86_64
libxext6-1:1.3.6-1.x86_64 nvidia-555.58.02-2.x86_64
nvidia-32bit-555.58.02-2.x86_64 nvidia-kmod-common-555.58.02-2.noarch
nvidia-kmod-desktop-555.58.02-2_6.10.0_1.x86_64 nvidia-modprobe-555.58.02-2.x86_64
nvidia-persistenced-555.58.02-2.x86_64
Complete!
