You are not logged in.

Pages: 1

#1 2024-02-25 00:14:02

STEELBAS
Member
From: The Netherlands
Registered: 2010-01-18
Posts: 82

[SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

Hi all,

I'm not usually one for making forum posts here, as I can usually figure stuff out with Google-fu. Not in this case though, I've been trying to figure this out for a couple of days now.

I've actually had this problem before, but it went away after a while. Not sure what did it, then. The other day I decided to uninstall NoMachine (as it didn't work, anyway) and update my system, and then KDE under Wayland didn't start anymore. Or, that is—it does start, sort of: I see a black screen for a long time, but my keyboard shortcuts still work, so I can start a terminal and a browser and file manager et cetera.

After a while with only a black screen, the desktop environment suddenly loads up, with panel and desktop wallpaper. In the journalctl log linked below, this is around 00:15:58. The computer still doesn't work properly at this point, though: many programs fail to start. When I start Kodi, for instance, this happens in journalctl:

feb 25 00:48:52 pcbas plasmashell[4190]: QString::arg: 2 argument(s) missing in Kodi
feb 25 00:48:53 pcbas plasmashell[4190]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:286: Unable to assign [undefined] to QString
feb 25 00:48:53 pcbas systemd[1052]: Started Kodi.
feb 25 00:48:53 pcbas pipewire[1361]: spa.alsa: front:3p: Rate doesn't match (requested 88200Hz, got 96000Hz)
feb 25 00:48:53 pcbas plasmashell[8211]: libEGL warning: failed to open /dev/dri/renderD128: Permission denied
feb 25 00:48:53 pcbas plasmashell[8211]: libEGL warning: failed to open /dev/dri/renderD128: Permission denied
feb 25 00:48:53 pcbas plasmashell[8211]: libEGL warning: wayland-egl: could not open /dev/dri/renderD128 (Permission denied)
feb 25 00:48:53 pcbas plasmashell[8211]: MESA: error: ZINK: vkEnumeratePhysicalDevices failed (VK_ERROR_INITIALIZATION_FAILED)
feb 25 00:48:53 pcbas plasmashell[8211]: MESA: error: ZINK: failed to choose pdev
feb 25 00:48:53 pcbas plasmashell[8211]: libEGL warning: egl: failed to create dri2 screen
feb 25 00:48:53 pcbas plasmashell[8211]: VA error: wayland: failed to open /dev/dri/renderD128: Permission denied (errno 13)
feb 25 00:48:53 pcbas plasmashell[8211]: VA error: wayland: did not get DRM device
feb 25 00:48:53 pcbas kernel: kodi.bin[8211]: segfault at 0 ip 000074ca076a68c7 sp 00007fffecf1a1a0 error 4 in libva-wayland.so.2.2000.0[74ca076a6000+1000] likely on CPU 9 (core 4, socket 0)
feb 25 00:48:53 pcbas kernel: Code: 00 00 31 c0 31 ed e8 98 f8 ff ff e9 39 ff ff ff 0f 1f 00 41 57 41 56 41 55 49 89 f5 41 54 49 89 d4 55 53 48 81 ec 98 01 00 00 <8b> 3f 64 48 8b 04 25 28 00 00 00 48 89 84 24 88 01 00 00 31 c0 ff
feb 25 00:48:53 pcbas systemd[1]: Created slice Slice /system/systemd-coredump.
feb 25 00:48:53 pcbas systemd[1]: Started Process Core Dump (PID 8229/UID 0).
feb 25 00:48:54 pcbas systemd-coredump[8230]: [?] Process 8211 (kodi.bin) of user 1000 dumped core.
                                              
                                              Stack trace of thread 8211:
                                              #0  0x000074ca076a68c7 n/a (libva-wayland.so.2 + 0x28c7)
                                              #1  0x000074ca076b4cdf vaInitialize (libva.so.2 + 0x5cdf)
                                              #2  0x0000580200015f90 _ZN16CRendererVAAPIGL8RegisterEPN5VAAPI15IVaapiWinSystemEPvS3_RbS4_ (kodi.bin + 0xaa3f90)
                                              #3  0x0000580200c20c00 _ZN4KODI9WINDOWING7WAYLAND29CWinSystemWaylandEGLContextGL16InitWindowSystemEv (kodi.bin + 0x16aec00)
                                              #4  0x00005802004ed34c _ZN12CApplication9CreateGUIEv (kodi.bin + 0xf7b34c)
                                              #5  0x0000580200359646 XBMC_Run (kodi.bin + 0xde7646)
                                              #6  0x00005801ffdbb751 main (kodi.bin + 0x849751)
                                              #7  0x000074ca05df6cd0 n/a (libc.so.6 + 0x25cd0)
                                              #8  0x000074ca05df6d8a __libc_start_main (libc.so.6 + 0x25d8a)
                                              #9  0x00005801ffe208a5 _start (kodi.bin + 0x8ae8a5)
                                              
                                              Stack trace of thread 8223:
                                              #0  0x000074ca05ecc0bf __poll (libc.so.6 + 0xfb0bf)
                                              #1  0x000074ca077d29b7 n/a (libpulse.so.0 + 0x339b7)
                                              #2  0x000074ca077bc45c pa_mainloop_poll (libpulse.so.0 + 0x1d45c)
                                              #3  0x000074ca077c661c pa_mainloop_iterate (libpulse.so.0 + 0x2761c)
                                              #4  0x000074ca077c66d1 pa_mainloop_run (libpulse.so.0 + 0x276d1)
                                              #5  0x000074ca077d6bf2 n/a (libpulse.so.0 + 0x37bf2)
                                              #6  0x000074ca058e12b7 n/a (libpulsecommon-17.0.so + 0x5c2b7)
                                              #7  0x000074ca05e5c55a n/a (libc.so.6 + 0x8b55a)
                                              #8  0x000074ca05ed9a3c n/a (libc.so.6 + 0x108a3c)
                                              
                                              Stack trace of thread 8221:
                                              #0  0x000074ca05e58ebe n/a (libc.so.6 + 0x87ebe)
                                              #1  0x000074ca05e5b750 pthread_cond_wait (libc.so.6 + 0x8a750)
                                              #2  0x000074ca056d9e11 __gthread_cond_wait (libstdc++.so.6 + 0xd9e11)
                                              #3  0x0000580200327526 n/a (kodi.bin + 0xdb5526)
                                              #4  0x0000580200a8248d _ZN12ANNOUNCEMENT20CAnnouncementManager7ProcessEv (kodi.bin + 0x151048d)
                                              #5  0x0000580200328037 _ZN7CThread6ActionEv (kodi.bin + 0xdb6037)
                                              #6  0x0000580200cb37ef n/a (kodi.bin + 0x17417ef)
                                              #7  0x0000580200328aae n/a (kodi.bin + 0xdb6aae)
                                              #8  0x000074ca056e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
                                              #9  0x000074ca05e5c55a n/a (libc.so.6 + 0x8b55a)
                                              #10 0x000074ca05ed9a3c n/a (libc.so.6 + 0x108a3c)
                                              
                                              Stack trace of thread 8224:
                                              #0  0x000074ca05e58ebe n/a (libc.so.6 + 0x87ebe)
                                              #1  0x000074ca05e5bd35 pthread_cond_clockwait (libc.so.6 + 0x8ad35)
                                              #2  0x00005801ffe447fe n/a (kodi.bin + 0x8d27fe)
                                              #3  0x00005801fffe4363 _ZN5CLirc7ProcessEv (kodi.bin + 0xa72363)
                                              #4  0x0000580200328037 _ZN7CThread6ActionEv (kodi.bin + 0xdb6037)
                                              #5  0x0000580200cb37ef n/a (kodi.bin + 0x17417ef)
                                              #6  0x0000580200328aae n/a (kodi.bin + 0xdb6aae)
                                              #7  0x000074ca056e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
                                              #8  0x000074ca05e5c55a n/a (libc.so.6 + 0x8b55a)
                                              #9  0x000074ca05ed9a3c n/a (libc.so.6 + 0x108a3c)
                                              ELF object binary architecture: AMD x86-64
feb 25 00:48:54 pcbas systemd[1]: systemd-coredump@0-8229-0.service: Deactivated successfully.
feb 25 00:48:54 pcbas plasmashell[8206]: /usr/bin/kodi: line 181:  8211 Segmentation fault      (core dumped) ${KODI_BINARY} $SAVED_ARGS
feb 25 00:48:57 pcbas plasmashell[8303]: find: ‘/home/steelbas/.config/Code - OSS/Code Cache’: Permission denied
feb 25 00:48:57 pcbas systemd[1]: home-steelbas-Windows.automount: Got automount request for /home/steelbas/Windows, triggered by 8303 (find)
feb 25 00:48:57 pcbas systemd[1]: Mounting /home/steelbas/Windows...
feb 25 00:48:58 pcbas ntfs-3g[8411]: Version 2022.10.3 external FUSE 29
feb 25 00:48:58 pcbas ntfs-3g[8411]: Mounted /dev/sda2 (Read-Write, label "", NTFS 3.1)
feb 25 00:48:58 pcbas ntfs-3g[8411]: Cmdline options: rw,users,nosuid,nodev,exec
feb 25 00:48:58 pcbas ntfs-3g[8411]: Mount options: users,nosuid,nodev,exec,allow_other,nonempty,relatime,rw,fsname=/dev/sda2,blkdev,blksize=4096
feb 25 00:48:58 pcbas ntfs-3g[8411]: Ownership and permissions disabled, configuration type 7
feb 25 00:48:58 pcbas systemd[1]: Mounted /home/steelbas/Windows.
feb 25 00:49:08 pcbas blueman-tray[4465]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
feb 25 00:49:19 pcbas kioslave5[4518]: kf.kio.workers.http: Can't communicate with kded_kcookiejar!
feb 25 00:49:31 pcbas plasmashell[8206]: Crash report available at /home/steelbas/kodi_crashlog-20240225_004854.log
feb 25 00:49:31 pcbas systemd[1052]: app-Kodi-f0959142e1c14cc98a10f1cb8c84eaa9.scope: Consumed 6.551s CPU time.
feb 25 00:49:33 pcbas blueman-tray[4465]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed

I've been Googling on the errors around 

libEGL warning: failed to open /dev/dri/renderD128: Permission denied

and 

MESA: error: ZINK: vkEnumeratePhysicalDevices failed (VK_ERROR_INITIALIZATION_FAILED

as those pop up during the booting process, too, but that didn't really lead to anything helpful.

Things I've tried that didn't work:

  • Downgrading Mesa to 23.3.5

  • Using the KDE version from kde-unstable

  • Remove all autostarted programs from ~/.config/autostart

Starting Plasma with X11 does start normally.


Journalctl -d: http://0x0.st/H55G.txt

I ran some other commands that have been requested in other forum posts that were similar to my problem. Here's the output of those:

eglinfo -B

GBM platform:
amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-13)
amdgpu: amdgpu_device_initialize failed.
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 24.0.1-arch1.1
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 24.0.1-arch1.1
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 24.0.1-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Wayland platform:
libEGL warning: failed to open /dev/dri/renderD128: Permission denied

libEGL warning: failed to open /dev/dri/renderD128: Permission denied

libEGL warning: wayland-egl: could not open /dev/dri/renderD128 (Permission denied)
MESA: error: ZINK: vkEnumeratePhysicalDevices failed (VK_ERROR_INITIALIZATION_FAILED)
MESA: error: ZINK: failed to choose pdev
libEGL warning: egl: failed to create dri2 screen
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 24.0.1-arch1.1
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 24.0.1-arch1.1
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 24.0.1-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

X11 platform:
eglinfo: eglInitialize failed

Surfaceless platform:
libEGL warning: failed to open /dev/dri/renderD128: Permission denied

libEGL warning: failed to open /dev/dri/renderD128: Permission denied

EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 24.0.1-arch1.1
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 24.0.1-arch1.1
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 24.0.1-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
libEGL warning: failed to open /dev/dri/renderD128: Permission denied

libEGL warning: failed to open /dev/dri/renderD128: Permission denied

amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-13)
amdgpu: amdgpu_device_initialize failed.
libEGL warning: egl: failed to create dri2 screen
eglinfo: eglInitialize failed

Device #1:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 24.0.1-arch1.1
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 24.0.1-arch1.1
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 24.0.1-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

sudo eglinfo -B:

GBM platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon RX 5600 XT (radeonsi, navi10, LLVM 16.0.6, DRM 3.57, 6.7.6-zen1-1-zen)
OpenGL core profile version: 4.6 (Core Profile) Mesa 24.0.1-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon RX 5600 XT (radeonsi, navi10, LLVM 16.0.6, DRM 3.57, 6.7.6-zen1-1-zen)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 24.0.1-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon RX 5600 XT (radeonsi, navi10, LLVM 16.0.6, DRM 3.57, 6.7.6-zen1-1-zen)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 24.0.1-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Wayland platform:
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
eglinfo: eglInitialize failed

X11 platform:
eglinfo: eglInitialize failed

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon RX 5600 XT (radeonsi, navi10, LLVM 16.0.6, DRM 3.57, 6.7.6-zen1-1-zen)
OpenGL core profile version: 4.6 (Core Profile) Mesa 24.0.1-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon RX 5600 XT (radeonsi, navi10, LLVM 16.0.6, DRM 3.57, 6.7.6-zen1-1-zen)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 24.0.1-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon RX 5600 XT (radeonsi, navi10, LLVM 16.0.6, DRM 3.57, 6.7.6-zen1-1-zen)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 24.0.1-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon RX 5600 XT (radeonsi, navi10, LLVM 16.0.6, DRM 3.57, 6.7.6-zen1-1-zen)
OpenGL core profile version: 4.6 (Core Profile) Mesa 24.0.1-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon RX 5600 XT (radeonsi, navi10, LLVM 16.0.6, DRM 3.57, 6.7.6-zen1-1-zen)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 24.0.1-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon RX 5600 XT (radeonsi, navi10, LLVM 16.0.6, DRM 3.57, 6.7.6-zen1-1-zen)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 24.0.1-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #1:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 24.0.1-arch1.1
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 24.0.1-arch1.1
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 24.0.1-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

systemctl list-units --type=service --state=active,running | awk '/.*\.service/ {print $1}':

alsa-restore.service
avahi-daemon.service
bluetooth.service
colord.service
cups.service
dbus-broker.service
dhcpcd.service
geoclue.service
jackett.service
kmod-static-nodes.service
ldconfig.service
lircd.service
lvm2-monitor.service
mullvad-daemon.service
NetworkManager-wait-online.service
NetworkManager.service
nohang-desktop.service
plymouth-quit-wait.service
plymouth-quit.service
plymouth-read-write.service
plymouth-start.service
polkit.service
rtkit-daemon.service
sddm.service
smartd.service
sshd.service
syncthing@steelbas.service
systemd-binfmt.service
systemd-fsck@dev-disk-by\x2duuid-05add354\x2de0db\x2d431c\x2d810a\x2dd3e3e3a2b76b.service
systemd-fsck@dev-disk-by\x2duuid-95afa354\x2d848d\x2d40a2\x2d8df0\x2dbd737b11dd52.service
systemd-fsck@dev-disk-by\x2duuid-e45fd7c0\x2d241b\x2d4734\x2d9e7f\x2d3140366963cb.service
systemd-journal-catalog-update.service
systemd-journal-flush.service
systemd-journald.service
systemd-logind.service
systemd-modules-load.service
systemd-random-seed.service
systemd-remount-fs.service
systemd-sysctl.service
systemd-sysusers.service
systemd-timesyncd.service
systemd-tmpfiles-setup-dev-early.service
systemd-tmpfiles-setup-dev.service
systemd-tmpfiles-setup.service
systemd-udev-trigger.service
systemd-udevd.service
systemd-update-done.service
systemd-update-utmp.service
systemd-user-sessions.service
systemd-vconsole-setup.service
udisks2.service
upower.service
user-runtime-dir@1000.service
user@1000.service
wpa_supplicant.service

systemctl --user list-units --type=service --state=active,running | awk '/.*\.service/ {print $1}'

app-blueman@autostart.service
app-geoclue\x2ddemo\x2dagent@autostart.service
app-kaccess@autostart.service
app-mullvad\x2dvpn@autostart.service
app-org.kde.discover.notifier@autostart.service
app-org.kde.kalendarac@autostart.service
app-pasystray@autostart.service
at-spi-dbus-bus.service
dbus-:1.2-org.kde.kpasswdserver@1.service
dbus-:1.96-org.a11y.atspi.Registry@0.service
dbus-broker.service
dconf.service
gvfs-daemon.service
pipewire-pulse.service
pipewire.service
plasma-gmenudbusmenuproxy.service
plasma-kactivitymanagerd.service
plasma-kded.service
plasma-kwin_wayland.service
plasma-plasmashell.service
plasma-polkit-agent.service
plasma-powerdevil.service
plasma-xdg-desktop-portal-kde.service
plasma-xembedsniproxy.service
wireplumber.service
xdg-desktop-portal.service
xdg-document-portal.service
xdg-permission-store.service

I would really appreciate some help. Please let me know if I need to run some more commands or add more logs.

Last edited by STEELBAS (2024-02-26 22:28:47)

Offline

#2 2024-02-25 22:23:24

STEELBAS
Member
From: The Netherlands
Registered: 2010-01-18
Posts: 82

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

Okay, so, strangely, in desperation I installed NoMachine again, and lo, the systems works as expected again. Very strange—why does this piece of software (that doesn't even work the way it's supposed to) have such influence on the workings of Wayland?

I'll try turning off the systemd service now, see what that does...

Edit: So, it turns out NoMachine is really the culprit, strangely. No idea how to get around this.

I disabled NoMachine's systemd service, and plasma-wayland still boots as it's supposed to. Checking after a reboot, the systemd service is really disabled.

Uninstalling NoMachine again, however, immediately results in the same problems as described in my first post.

I figured it might be related to one of the other packages installed because of NoMachine (i.e. nawk elfutils rpm-sequoia and rpm-tools), so I tried uninstalling NoMachine and then explicitly installing those four packages, but that was not it either.

The Wiki also mentions a polkit rules file that should be removed, but doing so after uninstalling NoMachine also didn't make any difference.


I suppose it's fine to leave NoMachine installed, as long as it's not running it's not taking up any memory and I can spare the disk space. But I don't understand at all. Not sure if I can count this as Solved...

Last edited by STEELBAS (2024-02-25 23:15:53)

Offline

#3 2024-02-25 23:27:08

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,802

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

Just an aside, Plasma has a major upgrade coming at the end of the month.  One of the goals of that release is to make the transition from preferring Xorg to preferring Wayland.  You might defer spending any more time on this until after that upgrade.

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#4 2024-02-25 23:39:14

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,754

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

This still sounds like a nomachine issue. It sets up something that isn't cleanly removed... Check your .profile and/or /etc/profile(.d) or so, maybe grep for nomachine tokens. The permission denied message sounds like it breaks the logind session somehow, what's your output of 

printenv

? does DBUS_SESSION_BUS_ADDRESS get messed up?

Offline

#5 2024-02-26 09:25:39

seth
Member
Registered: 2012-09-03
Posts: 51,553

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

failed to open /dev/dri/renderD128: Permission denied

ls -l /dev/dri/
getfacl /dev/dri/renderD128

Also: Is the simpledrm device simply disabled in the zen kernels?

Also

feb 25 00:11:40 pcbas kernel: amdgpu 0000:08:00.0: [drm] *ERROR* No EDID read.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#6 2024-02-26 10:46:00

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,754

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

It's not 

[    0.000000] Linux version 6.7.6-zen1-1-zen (linux-zen@archlinux) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.42.0) #1 ZEN SMP PREEMPT_DYNAMIC Fri, 23 Feb 2024 16:32:48 +0000
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux-zen root=UUID=ec20646f-753b-4f4a-9598-7abd897a0cd8 rw quiet audit=0
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux-zen root=UUID=ec20646f-753b-4f4a-9598-7abd897a0cd8 rw quiet audit=0
[    0.000000] Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-linux-zen", will be passed to user space.
[    0.472029] [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
[    0.472646] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
[    1.136522]     BOOT_IMAGE=/boot/vmlinuz-linux-zen

(yes I don't know why I haven't killed it with fire yet either)

@STEELBAS try adding "initcall_blacklist=simpledrm_platform_driver_init" to your kernel parameters

Offline

#7 2024-02-26 13:25:25

seth
Member
Registered: 2012-09-03
Posts: 51,553

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

Thing is that it doesn't show up in any capacity in the provided journal: http://0x0.st/H55G.txt

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#8 2024-02-26 15:21:39

Raxion
Member
Registered: 2024-02-26
Posts: 3

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

Hello,

Wanted to chime in since I'm similarly curious what NoMachine might have done to my own system. I did unfortunately add and uninstall NMX during some massive updates to my Nvidia, kernel, and DE's so it's been a bit of a trip these last few weeks trying to figure out what problem came from where but I am curious why NMX specifically had such a big hand in wrecking my system.

Here are the NoMachine installation logs in hopes they might help shed light on what all it did:
https://0x0.st/HRP7.txt

I don't believe my environment variables were messed up:

DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus

Offline

#9 2024-02-26 15:37:34

seth
Member
Registered: 2012-09-03
Posts: 51,553

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

NX> 700 Key: EnableEGLCapture already exists in config file. Not inserted.
NX> 700 Key: EnableEGLCapture already exists in config file. Not inserted.
NX> 700 Running: '/etc/NX/nxserver' --eglcapture yes.
NX> 700 Result: NX> 900 EnableEGLCapture key set to: 1.
NX> 900 Enabled EGL screen capture in '/usr/lib/plasma-sourceenv.sh'.
NX> 900 Enabled EGL screen capture in '/usr/share/applications/org.gnome.Shell.desktop'.
NX> 900 Enabled EGL screen capture in '/usr/lib/plasma-dbus-run-session-if-needed'.
NX> 900 Enabled EGL screen capture in '/usr/lib/systemd/user/org.gnome.Shell@wayland.service'..

https://bbs.archlinux.org/viewtopic.php … 4#p2153214
Same permission issues w/ that file?
What does it look like?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#10 2024-02-26 16:11:10

Raxion
Member
Registered: 2024-02-26
Posts: 3

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

Yes, the exact same permission issues or at least I recall having seen errors more around libEGL and Zink. After having reinstalled NMX thanks to @STEELBAS' suggestion suddenly I can actually turn on my DE's as well (though I wrecked them bad with my prior attempts to fix).

Here's the permissions with ls:
https://0x0.st/HRZV.txt

Here's the getfacl:

getfacl /dev/dri/renderD128
getfacl: Removing leading '/' from absolute path names
# file: dev/dri/renderD128
# owner: root
# group: root
user::rw-
group::rw-
other::rw-

Edit:
Here's my journalctl -b from the 21st of Feb a little while after I'd taken NMX off and trying to get any of my DEs to even turn on to make sure we're not two totally different problems:
https://0x0.st/H58k.txt

Edit2:
Taking a closer inspection no, definitely not the exact same but the symptoms of libEGL and ZINK errors/warnings definitely have come up multiple times in the last few weeks unless my memory is failing me. Sorry about that, should have taken a bit more time to read through.

Last edited by Raxion (2024-02-26 16:39:54)

Offline

#11 2024-02-26 20:53:30

STEELBAS
Member
From: The Netherlands
Registered: 2010-01-18
Posts: 82

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

ewaller wrote:

Just an aside, Plasma has a major upgrade coming at the end of the month.  One of the goals of that release is to make the transition from preferring Xorg to preferring Wayland.  You might defer spending any more time on this until after that upgrade.

I am aware, thank you! I tried the Plasma version from kde-unstable, but that didn't make any difference, so I don't believe it's related. Perhaps it will fix my issues, though, you never know.

V1del wrote:

what's your output of 

printenv

? does DBUS_SESSION_BUS_ADDRESS get messed up?

I tested with NoMachine installed and uninstalled, to see the difference.

With NoMachine installed it's 

SHELL=/bin/bash
COLORTERM=truecolor
CSF_MDTVTexturesDirectory=/usr/share/opencascade/resources/Textures
XDG_CONFIG_DIRS=/home/steelbas/.config/kdedefaults:/etc/xdg
KGLOBALACCELD_PLATFORM=org.kde.kwin
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
HISTCONTROL=erasedups:ignoredups:ignorespace
CSF_DrawPluginDefaults=/usr/share/opencascade/resources/DrawResources
HISTSIZE=5000
LANGUAGE=en_US.utf8
TERMINATOR_DBUS_PATH=/net/tenshu/Terminator2
LESS_TERMCAP_se=
LESS_TERMCAP_so=
LC_ADDRESS=nl_NL.utf8
CSF_LANGUAGE=us
LC_NAME=nl_NL.utf8
CSF_MIGRATION_TYPES=/usr/share/opencascade/resources/StdResource/MigrationSheet.txt
GRADLE_HOME=/usr/share/java/gradle
MEMORY_PRESSURE_WRITE=c29tZSAyMDAwMDAgMjAwMDAwMAA=
TERMINATOR_UUID=urn:uuid:bafd83d5-9bc5-48dd-bbdf-2360f5c70db8
DESKTOP_SESSION=plasmawayland
LC_MONETARY=nl_NL.utf8
CSF_OCCTResourcePath=/usr/share/opencascade/resources
XCURSOR_SIZE=48
CSF_STEPDefaults=/usr/share/opencascade/resources/XSTEPResource
EDITOR=geany
XDG_SEAT=seat0
PWD=/home/steelbas
XDG_SESSION_DESKTOP=KDE
LOGNAME=steelbas
XDG_SESSION_TYPE=wayland
DRAWHOME=/usr/share/opencascade/resources/DrawResources
SYSTEMD_EXEC_PID=986
XAUTHORITY=/run/user/1000/xauth_HBMaQO
CSF_StandardLiteDefaults=/usr/share/opencascade/resources/StdResource
MOTD_SHOWN=pam
HOME=/home/steelbas
LC_PAPER=nl_NL.utf8
LANG=en_US.utf8
LS_COLORS=no=00:fi=00:di=00;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.ogg=01;35:*.mp3=01;35:*.wav=01;35:*.xml=00;31:
XDG_CURRENT_DESKTOP=KDE
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service/memory.pressure
VTE_VERSION=7402
WAYLAND_DISPLAY=wayland-0
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
CLICOLOR=1
INVOCATION_ID=0752ac558a3d40c9ac66179109880a02
TERMINATOR_DBUS_NAME=net.tenshu.Terminator25ef4b219e3b005583550f2b0f9f990c3
MANAGERPID=803
CSF_ShadersDirectory=/usr/share/opencascade/resources/Shaders
CSF_EXCEPTION_PROMPT=1
CSF_XmlOcafResource=/usr/share/opencascade/resources/XmlOcafResource
QT_QPA_PLATFORM=xcb;wayland
KDE_SESSION_UID=1000
CSF_SHMessage=/usr/share/opencascade/resources/SHMessage
XDG_ACTIVATION_TOKEN=kwin-8
XDG_SESSION_CLASS=user
ANDROID_HOME=/opt/android-sdk
TERM=xterm
LC_IDENTIFICATION=nl_NL.utf8
LESS_TERMCAP_mb=
LESS_TERMCAP_me=
LESS_TERMCAP_md=
USER=steelbas
PLASMA_USE_QT_SCALING=1
CSF_StandardDefaults=/usr/share/opencascade/resources/StdResource
KDE_SESSION_VERSION=5
CSF_IGESDefaults=/usr/share/opencascade/resources/XSTEPResource
QT_WAYLAND_FORCE_DPI=96
DISPLAY=:1
CSF_XCAFDefaults=/usr/share/opencascade/resources/StdResource
LESS_TERMCAP_ue=
SHLVL=1
MOZ_ENABLE_WAYLAND=1
LESS_TERMCAP_us=
LC_TELEPHONE=nl_NL.utf8
ANDROID_SDK_ROOT=/opt/android-sdk
LC_MESSAGES=en_US.utf8
LC_MEASUREMENT=nl_NL.utf8
XDG_VTNR=1
CSF_PluginDefaults=/usr/share/opencascade/resources/StdResource
CSF_TObjMessage=/usr/share/opencascade/resources/TObj
XDG_SESSION_ID=1
CASROOT=/usr
XDG_RUNTIME_DIR=/run/user/1000
DEBUGINFOD_URLS=https://debuginfod.archlinux.org
LC_TIME=nl_NL.utf8
QT_AUTO_SCREEN_SCALE_FACTOR=0
JOURNAL_STREAM=8:13259
CSF_XSMessage=/usr/share/opencascade/resources/XSMessage
LC_COLLATE=nl_NL.utf8
XCURSOR_THEME=breeze_cursors
MMGT_CLEAR=1
XDG_DATA_DIRS=/home/steelbas/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop
KDE_FULL_SESSION=true
QSG_RENDER_LOOP=basic
BROWSER=/usr/bin/firefox
PATH=/home/steelbas/.gem/ruby/3.0.0/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/android-sdk/platform-tools:/opt/android-sdk/tools:/opt/android-sdk/tools/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/var/lib/snapd/snap/bin:/home/steelbas/.gem/ruby/3.0.0/bin:/opt/android-sdk/platform-tools:/opt/android-sdk/tools:/opt/android-sdk/tools/bin:/home/steelbas/Scripts:/home/steelbas/.local/bin:/home/steelbas/.rvm/bin:/home/steelbas/.gem/ruby/3.0.0/bin
CSF_TObjDefaults=/usr/share/opencascade/resources/StdResource
HISTFILESIZE=100000
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
KDE_APPLICATIONS_AS_SCOPE=1
MAIL=/var/spool/mail/steelbas
DRAWDEFAULT=/usr/share/opencascade/resources/DrawResources/DrawDefault
LC_NUMERIC=nl_NL.utf8
_=/usr/bin/printenv

Without NoMachine, it's this:

SHELL=/bin/bash
COLORTERM=truecolor
CSF_MDTVTexturesDirectory=/usr/share/opencascade/resources/Textures
XDG_CONFIG_DIRS=/home/steelbas/.config/kdedefaults:/etc/xdg
KGLOBALACCELD_PLATFORM=org.kde.kwin
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
HISTCONTROL=erasedups:ignoredups:ignorespace
CSF_DrawPluginDefaults=/usr/share/opencascade/resources/DrawResources
HISTSIZE=5000
LANGUAGE=en_US.utf8
TERMINATOR_DBUS_PATH=/net/tenshu/Terminator2
LESS_TERMCAP_se=
LESS_TERMCAP_so=
LC_ADDRESS=nl_NL.utf8
CSF_LANGUAGE=us
LC_NAME=nl_NL.utf8
CSF_MIGRATION_TYPES=/usr/share/opencascade/resources/StdResource/MigrationSheet.txt
GRADLE_HOME=/usr/share/java/gradle
MEMORY_PRESSURE_WRITE=c29tZSAyMDAwMDAgMjAwMDAwMAA=
TERMINATOR_UUID=urn:uuid:12589018-86e8-41ca-8445-fe5a3dbe17c4
DESKTOP_SESSION=plasmawayland
LC_MONETARY=nl_NL.utf8
CSF_OCCTResourcePath=/usr/share/opencascade/resources
XCURSOR_SIZE=48
CSF_STEPDefaults=/usr/share/opencascade/resources/XSTEPResource
EDITOR=geany
XDG_SEAT=seat0
PWD=/home/steelbas
XDG_SESSION_DESKTOP=KDE
LOGNAME=steelbas
XDG_SESSION_TYPE=wayland
DRAWHOME=/usr/share/opencascade/resources/DrawResources
SYSTEMD_EXEC_PID=860
CSF_StandardLiteDefaults=/usr/share/opencascade/resources/StdResource
MOTD_SHOWN=pam
HOME=/home/steelbas
LC_PAPER=nl_NL.utf8
LANG=en_US.utf8
LS_COLORS=no=00:fi=00:di=00;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.ogg=01;35:*.mp3=01;35:*.wav=01;35:*.xml=00;31:
XDG_CURRENT_DESKTOP=KDE
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service/memory.pressure
VTE_VERSION=7402
WAYLAND_DISPLAY=wayland-0
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
CLICOLOR=1
INVOCATION_ID=c1f00c003cc241c6886ded94b5a56e73
TERMINATOR_DBUS_NAME=net.tenshu.Terminator25ef4b219e3b005583550f2b0f9f990c3
MANAGERPID=793
CSF_ShadersDirectory=/usr/share/opencascade/resources/Shaders
CSF_EXCEPTION_PROMPT=1
CSF_XmlOcafResource=/usr/share/opencascade/resources/XmlOcafResource
QT_QPA_PLATFORM=xcb;wayland
KDE_SESSION_UID=1000
CSF_SHMessage=/usr/share/opencascade/resources/SHMessage
XDG_ACTIVATION_TOKEN=kwin-2
XDG_SESSION_CLASS=user
ANDROID_HOME=/opt/android-sdk
TERM=xterm
LC_IDENTIFICATION=nl_NL.utf8
LESS_TERMCAP_mb=
LESS_TERMCAP_me=
LESS_TERMCAP_md=
USER=steelbas
PLASMA_USE_QT_SCALING=1
CSF_StandardDefaults=/usr/share/opencascade/resources/StdResource
KDE_SESSION_VERSION=5
CSF_IGESDefaults=/usr/share/opencascade/resources/XSTEPResource
QT_WAYLAND_FORCE_DPI=96
CSF_XCAFDefaults=/usr/share/opencascade/resources/StdResource
LESS_TERMCAP_ue=
SHLVL=1
MOZ_ENABLE_WAYLAND=1
LESS_TERMCAP_us=
LC_TELEPHONE=nl_NL.utf8
ANDROID_SDK_ROOT=/opt/android-sdk
LC_MESSAGES=en_US.utf8
LC_MEASUREMENT=nl_NL.utf8
XDG_VTNR=1
CSF_PluginDefaults=/usr/share/opencascade/resources/StdResource
CSF_TObjMessage=/usr/share/opencascade/resources/TObj
XDG_SESSION_ID=1
CASROOT=/usr
XDG_RUNTIME_DIR=/run/user/1000
DEBUGINFOD_URLS=https://debuginfod.archlinux.org
LC_TIME=nl_NL.utf8
QT_AUTO_SCREEN_SCALE_FACTOR=0
JOURNAL_STREAM=8:13457
CSF_XSMessage=/usr/share/opencascade/resources/XSMessage
LC_COLLATE=nl_NL.utf8
XCURSOR_THEME=breeze_cursors
MMGT_CLEAR=1
XDG_DATA_DIRS=/home/steelbas/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop
KDE_FULL_SESSION=true
QSG_RENDER_LOOP=basic
BROWSER=/usr/bin/firefox
PATH=/home/steelbas/.gem/ruby/3.0.0/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/android-sdk/platform-tools:/opt/android-sdk/tools:/opt/android-sdk/tools/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/var/lib/snapd/snap/bin:/home/steelbas/.gem/ruby/3.0.0/bin:/opt/android-sdk/platform-tools:/opt/android-sdk/tools:/opt/android-sdk/tools/bin:/home/steelbas/Scripts:/home/steelbas/.local/bin:/home/steelbas/.rvm/bin:/home/steelbas/.gem/ruby/3.0.0/bin
CSF_TObjDefaults=/usr/share/opencascade/resources/StdResource
HISTFILESIZE=100000
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
KDE_APPLICATIONS_AS_SCOPE=1
MAIL=/var/spool/mail/steelbas
DRAWDEFAULT=/usr/share/opencascade/resources/DrawResources/DrawDefault
LC_NUMERIC=nl_NL.utf8
_=/usr/bin/printenv

DBUS_SESSION_BUS_ADDRESS is the same in both cases, at least. Running diff on both files doesn't net many differences apart from some different PIDs and XDG_ACTIVATION_TOKEN, though perhaps interestingly, DISPLAY=:1 doesn't show up when NoMachine is uninstalled.

seth wrote:
ls -l /dev/dri/
getfacl /dev/dri/renderD128

With NoMachine still installed, it's this:

ls -l /dev/dri/

total 0
drwxr-xr-x  2 root root       80 feb 26 17:14 by-path
crw-rw-rw-+ 1 root root 226,   0 feb 26 17:14 card0
crw-rw-rw-  1 root root 226, 128 feb 26 17:14 renderD128

getfacl /dev/dri/renderD128

getfacl: Removing leading '/' from absolute path names
# file: dev/dri/renderD128
# owner: root
# group: root
user::rw-
group::rw-
other::rw-

Without NoMachine (so with a broken desktop experience), this:

ls -l /dev/dri/

total 0
drwxr-xr-x  2 root root           80 feb 26 21:15 by-path
crw-rw----+ 1 root vglusers 226,   0 feb 26 21:15 card0
crw-rw----  1 root vglusers 226, 128 feb 26 21:15 renderD128

getfacl /dev/dri/renderD128

getfacl: Removing leading '/' from absolute path names
# file: dev/dri/renderD128
# owner: root
# group: vglusers
user::rw-
group::rw-
other::--

Not sure where "vglusers" comes from...

V1del wrote:

@STEELBAS try adding "initcall_blacklist=simpledrm_platform_driver_init" to your kernel parameters

Did that, here's the resulting journalctl: https://0x0.st/HRqq.txt

It didn't solve any of the problems in starting Wayland, unfortunately.


Raxion wrote:

Yes, the exact same permission issues or at least I recall having seen errors more around libEGL and Zink. After having reinstalled NMX thanks to @STEELBAS' suggestion suddenly I can actually turn on my DE's as well (though I wrecked them bad with my prior attempts to fix).

Glad I was able to help there, at least!

V1del wrote:

It's not 

[    0.000000] Linux version 6.7.6-zen1-1-zen (linux-zen@archlinux) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.42.0) #1 ZEN SMP PREEMPT_DYNAMIC Fri, 23 Feb 2024 16:32:48 +0000
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux-zen root=UUID=ec20646f-753b-4f4a-9598-7abd897a0cd8 rw quiet audit=0
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux-zen root=UUID=ec20646f-753b-4f4a-9598-7abd897a0cd8 rw quiet audit=0
[    0.000000] Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-linux-zen", will be passed to user space.
[    0.472029] [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
[    0.472646] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
[    1.136522]     BOOT_IMAGE=/boot/vmlinuz-linux-zen

(yes I don't know why I haven't killed it with fire yet either)

As an aside: is linux-zen discouraged? I was under the impression it was a good choice for desktop computers, but I haven't really looked into it for a while.

Last edited by STEELBAS (2024-02-26 21:01:30)

Offline

#12 2024-02-26 21:00:20

seth
Member
Registered: 2012-09-03
Posts: 51,553

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

Not sure where "vglusers" comes from...

https://wiki.archlinux.org/title/VirtualGL
Try to add yourself to that group, no idea wha's up w/ the permission change at hand.

Edit: https://archlinux.org/packages/extra/x86_64/virtualgl/
Do you have bublebee installed?
https://wiki.archlinux.org/title/Talk:VirtualGL - apparently you can configure whether to restrict the access.

You're btw. runnig NM and dhcpcd concurently

feb 26 21:35:39 pcbas NetworkManager[621]: <info>  [1708979739.4390] dhcp: init: Using DHCP client 'internal'
feb 26 21:35:39 pcbas dhcpcd[638]: no interfaces have a carrier

Last edited by seth (2024-02-26 21:02:22)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#13 2024-02-26 21:05:29

STEELBAS
Member
From: The Netherlands
Registered: 2010-01-18
Posts: 82

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

seth wrote:

Not sure where "vglusers" comes from...

https://wiki.archlinux.org/title/VirtualGL
Try to add yourself to that group, no idea wha's up w/ the permission change at hand.

I'll try that! Here I go uninstalling NoMachine again, yay. If it turns out that fixes it, is simply adding myself to that group the way to go? Is there any way to find out what the permissions should look like? And how do I go about fixing those? I'm guessing chown/chmod is not the way to solve that.

seth wrote:

You're btw. runnig NM and dhcpcd concurently

feb 26 21:35:39 pcbas NetworkManager[621]: <info>  [1708979739.4390] dhcp: init: Using DHCP client 'internal'
feb 26 21:35:39 pcbas dhcpcd[638]: no interfaces have a carrier

Oh, thanks! You're right. I'll get rid of dhcpd.

Offline

#14 2024-02-26 21:13:03

STEELBAS
Member
From: The Netherlands
Registered: 2010-01-18
Posts: 82

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

Yes, adding myself to the vglusers group solved my issues. Still, I imagine I wasn't part of that group before I installed NoMachine... Is this a "neat" enough way of solving the issue, or should I try to fix these issues at the root of the problem more?

seth wrote:

Edit: https://archlinux.org/packages/extra/x86_64/virtualgl/
Do you have bublebee installed?
https://wiki.archlinux.org/title/Talk:VirtualGL - apparently you can configure whether to restrict the access.

Oh, I missed your edit earlier. No, I do not have bumblebee installed, I have an AMD video card (thankfully).

Last edited by STEELBAS (2024-02-26 21:16:58)

Offline

#15 2024-02-26 21:23:19

seth
Member
Registered: 2012-09-03
Posts: 51,553

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

Why do you have virtualgl installed itfp?
Why did you configure it to restrict the device access?
If you want the restrictions in place but be able to use the device you'll have to add yourself to the group, yes.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#16 2024-02-26 21:34:03

STEELBAS
Member
From: The Netherlands
Registered: 2010-01-18
Posts: 82

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

seth wrote:

Why do you have virtualgl installed itfp?

I do not have virtualgl installed, actually! Neither have I configured it to restrict the device access. That is, I'm assuming you mean the package you linked, this one?

I'm not sure what's being discussed in the Talk page you linked, but I've certainly never knowingly restricted device access. Or perhaps I have, I've done all kinds of stuff on this PC in the years. But I wouldn't know why, I never ran Bumblebee here. How could I best go about lifting those access restrictions?

Last edited by STEELBAS (2024-02-26 21:44:01)

Offline

#17 2024-02-26 21:48:14

seth
Member
Registered: 2012-09-03
Posts: 51,553

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

Might be a nomachine thing, https://kb.nomachine.com/AR11K00737

NOTE:
To restore the original configuration on the system, run:
/usr/NX/scripts/vgl/vglserver_config -unconfig

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#18 2024-02-26 21:51:04

STEELBAS
Member
From: The Netherlands
Registered: 2010-01-18
Posts: 82

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

I see! Urgh. Okay, well, here I go installing NoMachine again, to get that script on my system again. I'll try running "/usr/NX/scripts/vgl/vglserver_config -unconfig" and then uninstalling NoMachine again, and removing myself from the vglusers group to test.

Edit:

$ sudo /usr/NX/scripts/vgl/vglserver_config -unconfig
... Removing /etc/opt/VirtualGL directory ...
... Removing X server access from /usr/share/sddm/scripts/Xsetup script ...
... Removing /usr/share/gdm/greeter/autostart/virtualgl.desktop ...
... Removing /etc/modprobe.d/virtualgl.conf to restore default permissions for
    /dev/nvidia* ...
... Removing /etc/udev/rules.d/99-virtualgl-dri.rules to restore default
    permissions for /dev/dri/card* and /dev/dri/renderD* at next boot ...
... Removing /etc/X11/xorg.conf.d/99-virtualgl-dri to restore default
    permissions for /dev/dri/card* ...

Done. You must restart the display manager for the changes to take effect.

Well, that certainly looks relevant. Now to uninstall NoMachine and reboot...

Edit: I'm back to the borked desktop experience, but small wonder: checking for all the files mentioned in the uninstall script above, none of those things got removed. So that either never actually happened when I ran the script in the first place, or it got restored when I uninstalled NoMachine. I'm now manually going to try to do the things the script mentions.

The contents of /etc/udev/rules.d/99-virtualgl-dri.rules seem especially relevant:

KERNEL=="card*|renderD*", MODE="0660", OWNER="root", GROUP="vglusers"

Edit: Yes, that solved the issue. I feel like we found a satisfactory solution to the issue, I suppose those changes made by NoMachine never got removed when uninstalling the program. I'll mark this topic as solved and make a comment on the NoMachine AUR page. Oh, and I suppose I'll add it to the NoMachine Arch wiki page, too.

Thanks a million for your help everyone, and especially @seth.

Last edited by STEELBAS (2024-02-26 22:30:39)

Offline

#19 2024-02-26 22:26:19

Raxion
Member
Registered: 2024-02-26
Posts: 3

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

seth wrote:

Might be a nomachine thing, https://kb.nomachine.com/AR11K00737

NOTE:
To restore the original configuration on the system, run:
/usr/NX/scripts/vgl/vglserver_config -unconfig

Chiming in to say thanks, threw that command in as well and it cleared up the NoMachine problems for me and I could cleanly uninstall it without any newer troubles.

Offline

#20 2024-02-26 22:29:50

STEELBAS
Member
From: The Netherlands
Registered: 2010-01-18
Posts: 82

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

Raxion wrote:

Chiming in to say thanks, threw that command in as well and it cleared up the NoMachine problems for me and I could cleanly uninstall it without any newer troubles.

Make sure you reboot after uninstalling NoMachine, too. For me, those files came right back.

Offline

#21 2024-03-10 08:33:51

artemklevtsov
Member
Registered: 2015-08-24
Posts: 4

Re: [SOLVED]KDE under Wayland has issues starting. libEGL and Mesa invo...

Faced the same problem after uninstall nomachine package. Remove /etc/udev/rules.d/99-virtualgl-dri.rules solve the problem.

Offline

Pages: 1

Board footer

Powered by FluxBB