Wayland session dropping to command line login, X11 session is fine

Desktop Environments Plasma
1

Hello, when I boot my computer and attempt to log in via SDDM, my Plasma/Wayland session crashes and I get dumped to a terminal login prompt. This only seems to happen for my Wayland session. X11 works fine (and is how I’m posting this message).

Things I’ve tried:

  • Ensure my system is up to date via pacman -Syu
  • Reinstalling various wayland and plasma packages
  • Reading through dmsg and journalctl output, but it’s not clear to me which of the various errors might be the root issue.

Some additional context that may help: I’m running an AMD 7900 XTX. I was successfully using mesa-git for awhile but noticed that mesa released a new version that should support my card (it’s final release of the version I was using via mesa-git). I was able to boot into Wayland once after swapping back to mesa proper, but now I’m unable to. I don’t think it was related to this change unless there is some Wayland specific package I missed reinstalling. It also seems like X11 wouldn’t be working if there was a driver issue.

Output for journalctl -b -1: https://gist.github.com/jimsimon/9a4c0aad667a0d2a03186527cf8cd165
Output for journalctl -k -b -1: https://gist.github.com/jimsimon/ce757329a35b513642d455f31c4d898c

And for good measure, here’s glxinfo -B when running via X11:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon Graphics (gfx1100, LLVM 15.0.7, DRM 3.49, 6.1.11-arch1-1) (0x744c)
    Version: 22.3.4
    Accelerated: yes
    Video memory: 24576MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 21385 MB, largest block: 21385 MB
    VBO free aux. memory - total: 31761 MB, largest block: 31761 MB
    Texture free memory - total: 21385 MB, largest block: 21385 MB
    Texture free aux. memory - total: 31761 MB, largest block: 31761 MB
    Renderbuffer free memory - total: 21385 MB, largest block: 21385 MB
    Renderbuffer free aux. memory - total: 31761 MB, largest block: 31761 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 24576 MB
    Total available memory: 56685 MB
    Currently available dedicated video memory: 21385 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon Graphics (gfx1100, LLVM 15.0.7, DRM 3.49, 6.1.11-arch1-1)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.3.4
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.3.4
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.3.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.2

Please let me know if there’s any more information I can provide. Thanks in advance for any help!

2

sounds dangerous… only plasma-wayland-session needed for kde wayland session … and reinstalling packages will not do much in most cases.

Feb 13 03:39:57 desktop kwalletd5[918]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Feb 13 03:39:57 desktop kwalletd5[918]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
                                        
                                        Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Feb 13 03:39:57 desktop sddm[701]: Display server stopped.

Feb 13 03:39:57 desktop kwalletd5[918]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.

but looks like something missing

3

Yep, that error is why I was reinstalling packages. I walked a few levels down the dependency tree of plasma-wayland-session to see if anything obvious was missing.

I’m not sure if something was missing so much as something is maybe misconfigured? That error talks about it being present but unable to be loaded. I could be way off here though.

4

you could check if it is about users config/setup and create a second user:
sudo useradd -m -G wheel username
sudo passwd username
sudo systemctl restart sddm
and try wayland session with the new user…

5

Good idea! I’ll give this a shot tomorrow. Heading to bed for now.

6

:zzz:
good night from the other side of the planet :wink: here we have 11 in the morning

7

Maybe. Your real problem seems video drivers connected IMHO.


Feb 13 03:39:57 desktop sunshine[943]: [2023:02:13:03:39:57]: Info: Found monitor for DRM screencasting
Feb 13 03:39:57 desktop kwin_wayland[945]: kwin_core: Failed to open /dev/dri/card0 device (Device or resource busy)
Feb 13 03:39:57 desktop kwin_wayland[945]: kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
Feb 13 03:39:57 desktop kwin_wayland[945]: kwin_wayland_drm: No suitable DRM devices have been found

Is it possible the sunshine is blocking the light road to wayland? :smiley:

Is it possible to disable it, for testing?

I suppose you have to review the mentioned configuration/package changes, and possibly delete (with backup) local configuration files.

8

Good catch! I’ll try disabling that service. It was recently installed, but I was able to boot fine with it in the past. I wonder if it’s just intermittently causing issues.

9

Disabling the sunshine service appears to have resolved the issue. Now to figure out why… :joy:

1 Like
10

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.