Looks like kwin 5.17 needs libdrm to make it work on wayland. Too bad this one went unnoticed. Fixed here https://github.com/OpenMandrivaAssociation/kwin/commit/fc37673f51601927e367d51b1fcf75d6efbba330
pt., 18 paź 2019 o 18:12 Tomasz Gajc <[email protected]> napisał(a): > After last updates i've noticed that plasma on wayland acts weird. After > some digging i found this when i run glxinfo: > > Extended renderer info (GLX_MESA_query_renderer): > Vendor: VMware, Inc. (0xffffffff) > Device: llvmpipe (LLVM 9.0, 256 bits) (0xffffffff) > Version: 19.2.1 > Accelerated: no > Video memory: 15874MB > Unified memory: no > Preferred profile: core (0x1) > Max core profile version: 3.3 > Max compat profile version: 3.1 > Max GLES1 profile version: 1.1 > Max GLES[23] profile version: 3.0 > OpenGL vendor string: VMware, Inc. > > This means Plasma on wayland somehow switches to software renederes > instead of DRM one. > When i run weston glxinfo says i'm running i915 DRM renderer, which is ok. > > Digging more in ./local/share/sddm/wayland-session.log with some exported > debug variables (QT_QPA_PLATFORM=wayland-egl EGL_LOG_LEVEL=debug > MESA_DEBUG=1 LIBGL_DEBUG=verbose) > > [tpg@tpg-80xl sddm]$ cat wayland-session.log > dbus-update-activation-environment: warning: error sending to systemd: > org.freedesktop.DBus.Error.ServiceUnknown: The name > org.freedesktop.systemd1 was not provided by any .service files > QCommandLineParser: already having an option named "h" > QCommandLineParser: already having an option named "help-all" > QCommandLineParser: already having an option named "v" > No backend specified through command line argument, trying auto resolution > _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed > _XSERVTransMakeAllCOTSServerListeners: server already running > libGL: Can't open configuration file /etc/drirc: No such file or directory. > libGL: Can't open configuration file /home/tpg/.drirc: No such file or > directory. > libEGL debug: pci id for fd 7: 8086:5917, driver i965 > > libEGL debug: MESA-LOADER: dlopen(/usr/lib64/dri/i965_dri.so) > > libEGL debug: found extension `DRI_Core' > libEGL info: found extension DRI_Core version 2 > libEGL debug: found extension `DRI_IMAGE_DRIVER' > libEGL info: found extension DRI_IMAGE_DRIVER version 1 > libEGL debug: found extension `DRI_DRI2' > libEGL debug: found extension `DRI_DriverVtable' > libEGL debug: found extension `DRI_ConfigOptions' > libEGL debug: found extension `DRI_Core' > libEGL debug: found extension `DRI_IMAGE_DRIVER' > libEGL debug: found extension `DRI_DRI2' > libEGL debug: found extension `DRI_DriverVtable' > libEGL debug: found extension `DRI_ConfigOptions' > libEGL info: found extension DRI_ConfigOptions version 1 > libGL: Can't open configuration file /etc/drirc: No such file or directory. > libGL: Can't open configuration file /home/tpg/.drirc: No such file or > directory. > libGL: Can't open configuration file /etc/drirc: No such file or directory. > libGL: Can't open configuration file /home/tpg/.drirc: No such file or > directory. > libEGL debug: found extension `DRI_TexBuffer' > libEGL info: found extension DRI_TexBuffer version 3 > libEGL debug: found extension `DRI2_Fence' > libEGL debug: found extension `DRI2_Flush' > libEGL info: found extension DRI2_Flush version 4 > libEGL debug: found extension `DRI_IMAGE' > libEGL info: found extension DRI_IMAGE version 16 > libEGL debug: found extension `DRI_RENDERER_QUERY' > libEGL debug: found extension `DRI_MutableRenderBufferDriver' > libEGL debug: found extension `DRI_CONFIG_QUERY' > libEGL debug: found extension `DRI_Robustness' > libEGL debug: found extension `DRI_NoError' > libEGL debug: found extension `DRI2_Blob' > libEGL debug: found extension `DRI_TexBuffer' > libEGL debug: found extension `DRI2_Fence' > libEGL info: found extension DRI2_Fence version 2 > libEGL debug: found extension `DRI2_Flush' > libEGL debug: found extension `DRI_IMAGE' > libEGL info: found extension DRI_IMAGE version 16 > libEGL debug: found extension `DRI_RENDERER_QUERY' > libEGL info: found extension DRI_RENDERER_QUERY version 1 > libEGL debug: found extension `DRI_MutableRenderBufferDriver' > libEGL info: found extension DRI_MutableRenderBufferDriver version 1 > libEGL debug: found extension `DRI_CONFIG_QUERY' > libEGL info: found extension DRI_CONFIG_QUERY version 1 > libEGL debug: found extension `DRI_Robustness' > libEGL info: found extension DRI_Robustness version 1 > libEGL debug: found extension `DRI_NoError' > libEGL info: found extension DRI_NoError version 1 > libEGL debug: found extension `DRI2_Blob' > libEGL info: found extension DRI2_Blob version 1 > libEGL debug: did not find optional extension DRI2_BufferDamage version 1 > libEGL debug: did not find optional extension DRI2_Interop version 1 > libEGL debug: did not find optional extension DRI_FlushControl version 1 > glamor: No eglstream capable devices found > glamor: 'wl_drm' not supported > Missing Wayland requirements for glamor GBM backend > Missing Wayland requirements for glamor EGLStream backend > Failed to initialize glamor, falling back to sw > libGL: Can't open configuration file /etc/drirc: No such file or directory. > libGL: Can't open configuration file /home/tpg/.drirc: No such file or > directory. > libGL: Can't open configuration file /etc/drirc: No such file or directory. > libGL: Can't open configuration file /home/tpg/.drirc: No such file or > directory. > The XKEYBOARD keymap compiler (xkbcomp) reports: > > Warning: Unsupported high keycode 372 for name <I372> ignored > > X11 cannot support keycodes above 255. > > This warning only shows for the first high keycode. > Errors from xkbcomp are not fatal to the X server > dbus-update-activation-environment: warning: error sending to systemd: > org.freedesktop.DBus.Error.ServiceUnknown: The name > org.freedesktop.systemd1 was not provided by any .service files > libKF5KIOCore.so.5 was not found. > libKF5Parts.so.5 was not found. > libKF5Plasma.so.5 was not found. > kdeinit5: preparing to launch '/usr/lib64/libexec/kf5/klauncher' > kdeinit5: Launched KLauncher, pid = 20907, result = 0 > > Googling around gives nothing :( > No i have to use x11 session. > >
