After doing a sudo zypper dup I’m unable to login to KDE wayland session (screen turns black and then boots back to the login screen). KDE X11 works fine.
Any ideas?
After doing a sudo zypper dup I’m unable to login to KDE wayland session (screen turns black and then boots back to the login screen). KDE X11 works fine.
Any ideas?
Review this topic first:
FWIW, a similar recent topic:
Based on the update log you shared, Mesa (from Packman) is the likely cause here.
ok, well i downloaded everything Mesa related from Tumbleweed repos rather than Packman, no difference whatsoever, still same login issue so I’m guessing it’s probably something other than Mesa (at least you would think so given that all mesa drivers are now from openSUSE?).
What Nvidia driver are you using?
Can you share the output of inxi -G
No Nvidia drivers.
inxi -G:
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics]
driver: radeon v: kernel
Display: x11 server: X.Org v: 21.1.12 with: Xwayland v: 24.1.2 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: radeonsi gpu: radeon
resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz
API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.5 vendor: amd mesa v: 24.1.3 renderer: KAVERI (radeonsi
LLVM 18.1.8 DRM 2.50 6.10.8-1-default)
API: Vulkan Message: No Vulkan data available.
No, i rolled system back, removed the Packman repo, done a zypper dup, 14 packages changed vendor to openSUSE, after doing a full update and reboot the same issue of not being able to login to KDE wayland (was able to before zypper dup issued).
Did you try the approach described here?
Then review the wayland.log file for errors.
OK, creating a new user didn’t make a difference like it did for him. Will try dbus-run-session startplasma-wayland > wayland.log from run level 3 later see if it brings anything to light.
OK, I get “could not create wayland socket” when i rundbus-run-session startplasma-wayland, and wayland.log is empty.
org.kde.ksplash exited with status 1 is one error.
Also, i get pretty much the same screen as here: https://forums.opensuse.org/t/wayland-will-not-start/172287/14
Unfortunately, none of that provides enough information to allow others to help with progressing further.
Nothing precedes that error? Vague snippets of information don’t provide enough of a picture here.
Does sudo zypper ve --dry-run
show any package inconsistencies?
Nothing:
Retrieving repository ‘home:Dead_Mozay’ metadata …[done]
Building repository ‘home:Dead_Mozay’ cache …[done]
Retrieving repository ‘Waterfox (deb/pkg.tar.xz/rpm/AppImage) (openSUSE_Slowroll)’ metadata …[done]
Building repository ‘Waterfox (deb/pkg.tar.xz/rpm/AppImage) (openSUSE_Slowroll)’ cache …[done]
Loading repository data…
Reading installed packages…
Dependencies of all installed packages are satisfied.
Since it’s not writing to wayland.log as the system is waiting for something to happen which never does then the only option would be to provide screenshot via my phone?
Better than nothing I suppose.
Please also show the results from
ls -l /run/user/1000
and
echo $XDG_RUNTIME_DIR
spaceboy@localhost.localdomain /home/spaceboy > ls -l /run/user/1000
total 12
drwx------ 2 spaceboy spaceboy 60 Sep 11 10:53 at-spi/
srw-rw-rw- 1 spaceboy spaceboy 0 Sep 11 10:53 bus=
drwx------ 3 spaceboy spaceboy 60 Sep 11 10:53 dbus-1/
drwx------ 2 spaceboy spaceboy 60 Sep 11 10:53 dconf/
dr-x------ 2 spaceboy spaceboy 0 Jan 1 1970 doc/
srw------- 1 spaceboy spaceboy 0 Sep 11 10:53 drkonqi-coredump-launcher=
prw------- 1 spaceboy spaceboy 0 Sep 11 10:53 fish_universal_variables.notifier|
dr-x------ 2 spaceboy spaceboy 0 Sep 11 10:53 gvfs/
drwx------ 2 spaceboy spaceboy 40 Sep 11 10:53 gvfsd/
-rw------- 1 spaceboy spaceboy 378 Sep 11 10:53 iceauth_xWvLTr
-rw-r--r-- 1 spaceboy spaceboy 101 Sep 11 10:53 KSMserver__1
srwxr-xr-x 1 spaceboy spaceboy 0 Sep 11 10:53 kwallet5.socket=
srw-rw-rw- 1 spaceboy spaceboy 0 Sep 11 10:53 pipewire-0=
-rw-r----- 1 spaceboy spaceboy 0 Sep 11 10:53 pipewire-0.lock
srw-rw-rw- 1 spaceboy spaceboy 0 Sep 11 10:53 pipewire-0-manager=
-rw-r----- 1 spaceboy spaceboy 0 Sep 11 10:53 pipewire-0-manager.lock
drwx------ 2 spaceboy spaceboy 80 Sep 11 10:53 pulse/
drwxr-xr-x 7 spaceboy spaceboy 180 Sep 11 10:53 systemd/
srwxr-xr-x 1 spaceboy spaceboy 0 Sep 11 10:53 wayland-0=
-rw-r----- 1 spaceboy spaceboy 0 Sep 11 10:53 wayland-0.lock
-rw------- 1 spaceboy spaceboy 111 Sep 11 10:53 xauth_oKenfj
spaceboy@localhost.localdomain /home/spaceboy > echo $XDG_RUNTIME_DIR
/run/user/1000
The above checks out as expected ^^
Review
journalctl -b | egrep -i "wayland|plasma"
You can examine form a working Plasma X11 session.