Wayland session failing to start

camorri · 02-18-2021, 12:35 PM

The problem, I can not start a Wayland session on one system. The symptoms; the monitor show only a cursor in the top left corner on a black background. The keyboard is unresponsive. Ctrl + Alt + backspace does nothing.

I have re-installed these files :

Code:

ls -l /var/lib/pkgtools/packages | grep wayland
-rw-r--r-- 1 root root    6634 Feb 17 06:56 kwayland-5.79.0-x86_64-1
-rw-r--r-- 1 root root    1263 Feb 17 06:56 kwayland-integration-5.21.0-x86_64-1
-rw-r--r-- 1 root root    4433 Feb 17 06:56 kwayland-server-5.21.0-x86_64-1
-rw-r--r-- 1 root root    2323 Feb 16 17:34 plasma-wayland-protocols-1.1.1-x86_64-3
-rw-r--r-- 1 root root    1946 Feb 16 17:46 wayland-1.19.0-x86_64-2
-rw-r--r-- 1 root root    4254 Feb 16 17:46 wayland-protocols-1.20-noarch-3
-rw-r--r-- 1 root root     814 Feb 16 17:50 xisxwayland-1-x86_64-3
-rw-r--r-- 1 root root    1098 Feb 16 17:51 xorg-server-xwayland-1.20.10-x86_64-5

The problem persists. Wayland sessions will start on my other three systems, all systems are fully up to date. The updates all come from the same server, a Pi3 with DH attached.

I can kill the hung session by connecting to the system via ssh, displaying the active wayland files, and killing the active ones.

Here is the output from the wayland session log.

Quote:

dbus-daemon[1345]: [session uid=1000 pid=1345] Activating service name='org.kde.KSplash' requested by ':1.0' (uid=1000 pid=1346 comm="/usr/bin/startplas>
dbus-daemon[1345]: [session uid=1000 pid=1345] Successfully activated service 'org.kde.KSplash'
kdeinit5: preparing to launch '/usr/lib64/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 1366, result = 0
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :0
kdeinit5: Got SETENV 'XCURSOR_THEME=Oxygen_Blue' from launcher.
kdeinit5: Got SETENV 'XCURSOR_SIZE=24' from launcher.
kdeinit5: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/cliff/.gtkrc:/home/cliff/.config/gtkrc' from launcher.
kdeinit5: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/cliff/.gtkrc-2.0:/home/cliff/.config/gtkrc-2.0' from launcher.
org.kde.plasma.session: process job "kcminit_startup" finished with exit code 0
QObject::connect: No such signal QDBusAbstractInterface::StateChanged(uint)
Installing the delayed initialization callback.
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5079:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5081:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5083:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5087:47: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5089:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5097:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5101:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5103:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5107:45: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5110:46: this compose sequence is a duplicate of another; skipping line
dbus-daemon[1345]: [session uid=1000 pid=1345] Activating service name='org.kde.ActivityManager' requested by ':1.7' (uid=1000 pid=1384 comm="/usr/bin/k>
dbus-daemon[1345]: [session uid=1000 pid=1345] Successfully activated service 'org.kde.ActivityManager'
dbus-daemon[1345]: [session uid=1000 pid=1345] Activating service name='org.kde.kglobalaccel' requested by ':1.8' (uid=1000 pid=1395 comm="/usr/lib64/ka>
dbus-daemon[1345]: [session uid=1000 pid=1345] Successfully activated service 'org.kde.kglobalaccel'
Qt: Session management error: networkIdsList argument is NULL
kdeinit5: Got SETENV 'SESSION_MANAGER=local/alienware.cliffshome.org:@/tmp/.ICE-unix/1404,unix/alienware.cliffshome.org:/tmp/.ICE-unix/1404' from launch>
kdeinit5: Got SETENV 'SESSION_MANAGER=local/alienware.cliffshome.org:@/tmp/.ICE-unix/1404,unix/alienware.cliffshome.org:/tmp/.ICE-unix/1404' from launch>
org.kde.plasma.session: Starting autostart service "/etc/kde/xdg/autostart/xembedsniproxy.desktop" ("/usr/bin/xembedsniproxy")
org.kde.plasma.session: Starting autostart service "/etc/kde/xdg/autostart/kaccess.desktop" ("/usr/bin/kaccess")
org.kde.plasma.session: Starting autostart service "/etc/kde/xdg/autostart/powerdevil.desktop" ("/usr/lib64/org_kde_powerdevil")
org.kde.plasma.session: Starting autostart service "/etc/kde/xdg/autostart/org.kde.plasmashell.desktop" ("/usr/bin/plasmashell")
Xlib XKB extension major= 1 minor= 0
org.kde.plasma.session: Starting autostart service "/etc/kde/xdg/autostart/polkit-kde-authentication-agent-1.desktop" ("/usr/lib64/polkit-kde-authentic>
Delayed initialization.

There is a QT session management error. Any ideas how I fix this?

This system is the last one I have running on an MBR BIOS system. My other systems are on GPT and UEFI. Not sure if that is relevant or not.

ZhaoLin1457 · 02-18-2021, 12:48 PM

Let me guess...

The graphics card is NVIDIA?

I have friends who say that they experienced lockups with Nouveau, and the proprietary blob is usable only for the really modern cards.

Also, the Wayland needs at least a support for OpenGL 2.1, if you have only OpenGL 1.4 looks like that it will not work.

camorri · 02-18-2021, 01:46 PM

Yes, I have an Nvidia card on the both working and failing systems. The failing system:

Quote:

inxi -G --display
Graphics: Device-1: NVIDIA GK107 [GeForce GTX 650] driver: nvidia v: 460.32.03
Display: x11 server: X.org 1.20.10 driver: loaded: nvidia unloaded: modesetting,nouveau,nv,vesa
Message: No advanced graphics data found on this system.

and one of my working systems,

Quote:

Graphics: Device-1: NVIDIA GK208B [GeForce GT 710] driver: nvidia v: 460.32.03
Display: x11 server: X.Org 1.20.10 driver: loaded: nvidia resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 460.32.03

ZhaoLin1457 · 02-18-2021, 01:57 PM

Quote:

Originally Posted by camorri

Yes, I have an Nvidia card on the both working and failing systems. The failing system:

Code:

 inxi -G --display
Graphics: Device-1: NVIDIA GK107 [GeForce GTX 650] driver: nvidia v: 460.32.03
Display: x11 server: X.org 1.20.10 driver: loaded: nvidia unloaded: modesetting,nouveau,nv,vesa
Message: No advanced graphics data found on this system.

and one of my working systems,

Code:

Graphics: Device-1: NVIDIA GK208B [GeForce GT 710] driver: nvidia v: 460.32.03
Display: x11 server: X.Org 1.20.10 driver: loaded: nvidia resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 460.32.03

Did you noticed the differences on third line?

Looks like you have some issues with the proprietary blob installation on the failing box.

camorri · 02-22-2021, 10:26 AM

Quote:

Looks like you have some issues with the proprietary blob installation on the failing box.

This could be true, however, it works perfectly running X11, either KDE or XFCE. So, if its the driver Nvidia blob, how to get a handle on the problem?

I suspect this is just another problem with Wayland. Its buggy at best, and is still very much a work in progress.

Here are a few of the things that fail in Wayland.

If I'm running chromium, opening up the bookmarks, with the mouse pointer, and navigate to one of the items like Slackware, and try to navigate into the sub menu, it will not work with the mouse pointer, the highlight shoots up the main list. I can use the sub-menus IF I use the arrow keys.

Geeqie seg-faults in Wayland, works perfectly in X11.

If I try to log out of Wayland, after closing all applications I started, every background app for KDE blows up, I wind up with about 20 failure messages on the screen asking if I wan to report a bug to KDE.

I'm interested to here from other slackers on their experience with Wayland.

bassmadrigal · 02-22-2021, 11:46 AM

From my memory, Nvidia binary drivers weren't working properly on Wayland. It seems they have some patches that are pending or recently added that will hopefully improve Wayland support on Nvidia hardware using the binary driver.

I'm not sure if the issue is tied to drivers or just some issues with Wayland itself, but issues like these are why it is not yet the primary display server in Slackware (and probably any distro).