Artix Linux Forum

Login to Wayland failing

20 January 2025, 18:15:15

Hi I had the following issue I addressed in this Reddit post (https://www.reddit.com/r/artixlinux/comments/1i4hgnl/wont_log_into_wayland/)

When installing the KDE-Plasma OpenRC .iso to my Thinkpad T460 Intel CPU i7 as my daily driver, Wayland was erroring by showing a black screen before reverting back to the login screen. Only X11 works.

I thought it was only because I didn't have plasma-wayland-protocols installed, but I realized that in my other laptop that I experimented w/ (Thinkpad T440 Intel CPU i5) that I had changed the /usr/share/xsessions/ to include /plasmawayland.desktop and that's the reason it worked.

So I did that with my T460... and Wayland worked, except that the loginscreen was in the background and the Wayland desktop was in a small box (1/3 of the screen still) in the top-left of the screen. Very odd since my T440 didn't do that.

I realized then that I should've added plasmawayland.desktop to wayland-sessions (a directory I didn't know existed before which had x11 in it (as xsessions did too). So I added it to there, then finding (wayland) (wayland) as a duplicate (I mean that the login screen had Plasma (wayland), Plasma (wayland) (wayland), and then Plasma (X11)).

After that, having realized that xsessions didn't need plasmawayland.desktop since wayland-sessions is where the plasmawayland.desktop config needed to be, I deleted the xsessions one and the duplicate (wayland)(wayland) disappeared.

Plasma (Wayland) didnt work tho (in T460), and that's when I realized that I should've left plasmwayland.desktop in xsessions (which in the T440 actually did have plasmawayland.desktop in wayland-sessions directory without me having added it, which the T460 didn't have.

But when trying to add xsessions plasmawayland.desktop back to it, the (wayland)(wayland) wouldn't show up on the login, just plasma (wayland), so that's where I've rage quitted.

There's so many things that haven't made sense, and btw I did set permissions to the xsessions one, even tho before it had worked without setting permissions... and this time it isn't working.

I believe there's some serious issues with the wayland directory stuff, however it works. This is my first going through directories and I was sure I figured it out in the T440, but since Wayland only worked in Xsessions (which is supposed to be for X11 only)... there's something wrong

Anyway if there's a quick fix that I can make to get Wayland working on the T460 that'd be great. I was hoping that with my experiments done on the T440 that having duplicated those changes to the T460 would've worked (I did all the same updates and everything).

I'm not switching distros as my daily driver since OpenRC has been great on Artix otherwise, and I've gotten comfortable w/ the Arch lingo on here. Though for security purposes I hope Wayland get's a patch on KDE-Plasma! For now I'm going to install the Artix base install on the T440 and see if there's issues installing KDE-Plasma on it, if Wayland works then I might do it on the T460... or just wait for a patch. Thanks for reading this!

Re: Login to Wayland failing

Reply #1 – 20 January 2025, 19:04:06

Does this PC have an Nvidia gpu? If so then check https://wiki.archlinux.org/title/NVIDIA#Wayland_configuration for setup requirements.

artist

Re: Login to Wayland failing

Reply #2 – 20 January 2025, 19:08:28

Intel i5-i7 (T460 has i7) w/ integrated GPU (so Intel). There's 2 other users in the Reddit thread I linked that have my issue, I'm not sure what GPU they have but one of them had issues with Dinit it seems, tho I asked them for clarification.

Also in case this matters, I did Offline install of the KDE-Plasma OpenRC .iso from the Stable Iso images (no mirrors or tested .iso)

Re: Login to Wayland failing

Reply #3 – 21 January 2025, 21:59:28

What is the output of: pacman -Q|grep 'intel\|mesa'

artist

Re: Login to Wayland failing

Reply #4 – 22 January 2025, 02:18:36

Here's the output:

pacman -Q | grep 'intel\|mesa'

intel-ucode 20241112-1
libva-intel-driver 2.4.1-3
mesa 1:24.3.3-2
mesa-utils 9.0.0-5
vulkan-intel 1:24.3.3-2
xf86-video-intel 1:2.99.917+923+gb74b67f0-2.2

Re: Login to Wayland failing

Reply #5 – 22 January 2025, 10:00:55

The xf86-video-intel package should maybe not be present as per https://wiki.archlinux.org/title/Intel_graphics#Installation

To see what the error is, stop and disable the DM service and run start kde from the console.

artist

Re: Login to Wayland failing

Reply #6 – 22 January 2025, 17:56:42

Thanks I'll check that and reply soon.

For now I ran the command pacman -Qs xf86-video-intel in both my T440 (has KDE-Plasma Wayland working) and my T460 (Wayland not working).

The T440 did not come back with an input, but the T460 did:

local/xf86-video-intel 1:2.99.917+923+gb74b67f0-2.2 (xorg-drivers)
X.org Intel i810/i830/i915/945G/G965+ video drivers

Would it be wise to remove this driver since it can cause issues? And replace it with a different driver, if needed?

I'm still confused w/ the xsessions and wayland-session directory and how the T440 ran once I made the changes to xsessions (what I noted in the first response) along with installing plasma-wayland-protocols, yet the T460 has not worked with these changes (except that I didn't change the xsessions directory), yet it includes the xf86 driver.

Re: Login to Wayland failing

Reply #7 – 22 January 2025, 19:22:47

@Artist  I just got a huge error… I’ve checked into it before and tried to troubleshoot, that’s where I thought it had to do with the directories.

There was a dbus error firstly that said it wasn't running, which I checked in a command and it said dbus was running. Then I did the command dbus-launch startplasma-wayland so that it could clear any occurrence of dbus that was running and focus solely on startplasma-wayland, and I got this very long error:

(kwin_wayland: 4462 (another w/ 4501, 4503, 4505, 4507, 4509, 4511... and up to 4517)): Gtk-WARNING **: 13:33:37:204 (and .401,.512,.629,.742,.853,.963,.075,.187,.299,.410): cannot open display:

qt.qpa.wayland: "wl-shell" is a deprecated shell extension, prefer using "xdg-shell" if supported by the compositor by setting the environment variable QT_WAYLAND_SHELL_INTEGRATION
qt.qpa.wayland: Loading shell integration failed.
qt.qpa.wayland: Attempted to load the following shells QList ("xdg-shell", "wl-shell", "ivi-shell", "qt-shell'")
Error: could not determine $DISPLAY
Error: Can not contact kdeinit5!
org.kde.startup: "kdeinit5_shutdown" QList() exited with code 255
startplasma-wayland: Shutting down... (and then the startplasmacompositor says done)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
artix:[oj]:~$ qt.qpa.xcb: could not connect to display :1
qt.qpa.plugin: From 6.5.0 xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.

This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem (My note: I think I already did this).
Available platform plugins are: wayland (a whole bunch of others, but it said it was found before...?)

Re: Login to Wayland failing

Reply #8 – 22 January 2025, 20:24:12

Do you have package libcxb installed?

Try this command: /usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland

artist

Re: Login to Wayland failing

Reply #9 – 22 January 2025, 21:35:10

libcxb is not on the T460, but neither is it on the T440 (where Wayland is working).

Also I forgot to update that I changed distros on the T440 to Endeavor OS which is Arch-based, except for the fact that it’s Systemd (so maybe not a fair comparison anymore?)

As for the command, I entered it into T460 and the error message was larger than the last, if needed I could send the screenshot (I can’t figure out images on this forum so it’d have to send thru Discord, email, or like Bluesky).

Most outputs were a form of: GLib-GIO-CRITICAL **: 15:27:42:764: Error while sending AddMatch() message: connection is closed.

Would be nice if this was solved by -r and -S a driver

Re: Login to Wayland failing

Reply #10 – 22 January 2025, 21:43:50

Just paste the output in pastebin and upload the link

artist