[SOLVED] Display Link - slow redraw of task bar in KDE Plasma

exup · 2022-12-22 05:39:48

Hi,
I have displaylink working ok for my new laptop Lenovo T14 and it can play back video scroll fine in applications, windows can be dragged around ok. But the KDE task bar and widget are very slow to respond or using and KDE apps like Systems settings. If I drag it onto the internal monitor they work fine, just issues on the external monitors.
I think it related to this Wiki article here HERE

My question, does plasma desktop use Webkit2 and this is the issue I am facing, else what is the issue?
the Wiki suggests to set the env LIBGL_ALWAYS_SOFTWARE=1 which I did by just running and rebooting.

 sudo env LIBGL_ALWAYS_SOFTWARE=1

additionally I am not sure if I am even using the GPU for Hardware video encoding as if I run vainfo I get the known message saying I need to configure VA-API

libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

can someone help me walk through ensuring I am leveraging the AMDGPU (AMD Ryzen 5 PRO 6650U with Radeon Graphics) I did follow this guide for XORG and MESA for the AMD drivers. Looking at PLASMA hardware info I see errors in openGL

amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-13)
amdgpu: amdgpu_device_initialize failed.
amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-13)
amdgpu: amdgpu_device_initialize failed.
EGL client extensions string:
    EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query
    EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses
    EGL_EXT_client_extensions EGL_KHR_debug EGL_EXT_platform_device
    EGL_EXT_platform_wayland EGL_KHR_platform_wayland
    EGL_EXT_platform_x11 EGL_KHR_platform_x11 EGL_EXT_platform_xcb
    EGL_MESA_platform_gbm EGL_KHR_platform_gbm
    EGL_MESA_platform_surfaceless

Last edited by exup (2023-01-03 05:32:51)

Lone_Wolf · 2022-12-22 10:10:16

Many people confuse DisplayPort and DisplayLink .
fortunately there's a simple check :
Do you own a hardware device which name starts with DL and sits between your laptop and your monitors ?

If yes : exactly which model & type is it ?

If not :
- nothing on the DisplayLink wiki page is applicable to your hardware. remove anything related to DisplayLink from your system
- post full lspci -k
- install mesa-utils
- post the full output of glxinfo -B and the first 100 lines of eglinfo

exup · 2022-12-22 12:05:55

Its a lenovo thinkpad dock USB C type with a sticker on the bottom saying displaylink plug and play.
The output of lspci -k is https://pastebin.com/zX9jBALV

lsusb shows

Bus 004 Device 005: ID 17e9:433f DisplayLink ThinkPad USB 3.0 Pro Dock

mesa-utils already installed

output of glxinfo -B https://pastebin.com/3bG6LDdH

output of egifo https://pastebin.com/a0rz0YG5

I have one of the monitors currently using the display port on the laptop so I can function ok. I normally run two monitors off the displaylink dock. Especially at work.

Lone_Wolf · 2022-12-23 17:36:50

Outputs look ok, you only have one videocard in your system and do appear to have a genuine DisplayLink device.

My question, does plasma desktop use Webkit2 and this is the issue I am facing, else what is the issue?

Nope plasma doesn't use webkit2 (and never has).

How did you setup your monitors ?
Post xrandr -q output with & without the extra monitors .

Are you using X or wayland ?
is xf86-video-amdgpu installed ?

is libva-mesa-driver installed ?

seth · 2022-12-24 15:39:42

the Wiki suggests to set the env LIBGL_ALWAYS_SOFTWARE=1 which I did by just running and rebooting.
sudo env LIBGL_ALWAYS_SOFTWARE=1

That does absolutely nothing.

echo 'export LIBGL_ALWAYS_SOFTWARE=1' > ~/.config/plasma-workspace/env/gl_force_sw.sh
chomd +x ~/.config/plasma-workspace/env/gl_force_sw.sh

Log out and back in.

Sanity check:
https://wiki.archlinux.org/title/Displa … xx_Devices
Do you have evdi-git?
(I don't have a displaylink device and don't know whether it's -stricly- required for your HW config, but sounds related)

exup · 2022-12-29 06:08:58

Not sure if I should close this thread and start a new one given I have changed the image and now have a different issue. Mouse moving to new monitors causes it to reset displaylink.

I wanted to see if Manjaro image would make any difference so nuked and installed it. Plasma Wayland but could not get evdi to properly installed.
So Ive returned to manual install of Arch as per the wiki with Plasma and Wayland.
installed https://aur.archlinux.org/packages/evdi-git
and https://aur.archlinux.org/packages/displaylink/
Displaylink service starts with no complaints.

I have installed mesa plasma-wayland-session vulkan-icd-loader and vulkan-radeon
I am starting plasma with startplasma-wayland (i am not using a display manager, I did try sddm-git in the aur as sddm is not supported under wayland but made no difference)

glxgears runs ok at 60FPS on main laptop screen.
vulkaninfo shows no errors and displays correctly
ls /usr/share/vulkan/icd.d/ shows I am using radeon_icd.x86_64.json

Here is a summary of my hardware.

OS: Arch Linux x86_64
Host: 21CGS0VT0B ThinkPad T14 Gen 3
Kernel: 6.1.1-arch1-1
Uptime: 26 mins
Packages: 804 (pacman)
Shell: bash 5.1.16
Resolution: 1920x1080
DE: Plasma 5.26.4
WM: kwin
Theme: [Plasma], Breeze [GTK2/3]
Icons: [Plasma], breeze [GTK2/3]
Terminal: konsole
Terminal Font: Hack 13
CPU: AMD Ryzen 5 PRO 6650U with Radeon Graphics (12) @ 2.900GHz
GPU: AMD ATI Radeon 680M
Memory: 2606MiB / 30851MiB

I plug in the lenovo display port (with two monitors connected)
Screens automatically come on with the plasma default wallpaper displayed.
I can view them and configure them in Plasma display manager.
But as soon as my mouse moves the the new monitor the monitors flickers and the plasma gui for display configuration shows monitors have been updated.
Monitor remain on, but issue persists.

I can move windows into the new monitors as long as my mouse does not cross over.
I can move windows in the monitor using keyboard short cuts ok even run video fine.

Perhaps I now have another issue to what I had before.

xrandr -q without external monitors https://pastebin.com/GfQw69TA
xrandr -q with external monitors https://pastebin.com/0134ZMUy

dmesg -W plugging in displaylink dock then I have marked when my mouse moves into the new screen https://pastebin.com/pSa4EJuX

journalctl as above, plug in displaylink dock then marked when I move the mouse https://pastebin.com/Rfpkjzh2
lspci https://pastebin.com/j5XH2ULQ
glxinfo https://pastebin.com/pC7FTiav
eglinfo https://pastebin.com/ujMgmSJU

and finally

seth wrote:

echo 'export LIBGL_ALWAYS_SOFTWARE=1' > ~/.config/plasma-workspace/env/gl_force_sw.sh
chomd +x ~/.config/plasma-workspace/env/gl_force_sw.sh

I didnt add this yet as not sure if I should now that I have blown away the original build from my first post. So should I still need too?

Last edited by exup (2022-12-29 07:04:44)

seth · 2022-12-29 07:49:34

xorg log?
For xf86-video-amdgpu see https://wiki.archlinux.org/title/AMDGPU … corruption

progandy · 2022-12-29 09:14:45

It seems like the cursor plane to accept hardware cursors in evdi is still buggy. You should be able to force plasma to use software cursors instead with KWIN_FORCE_SW_CURSOR

https://github.com/DisplayLink/evdi/issues/388
https://bugs.kde.org/show_bug.cgi?id=459929
https://invent.kde.org/plasma/kwin/-/wi … _sw_cursor

seth, as exup is now using wayland, there will be no xorg logs, at most there could be some for xwayland.

Last edited by progandy (2022-12-29 09:15:53)

exup · 2022-12-29 11:06:49

OK I am not too familiar yet with setting environment variables in linux. So is this correct as per the wiki in your last link
Create a script file kwin_env.sh with the variables you wish to set.
Create a file as per:

#!/bin/sh
export KWIN_FORCE_SW_CURSOR

Make the script executable (file properties or chmod +x kwin_vars.sh)
Place the script in a sourced path (I am not sure what this is and what it means)
Then copy to ~/.config/plasma-workspace/env/ (why duplicate the file also this file and folder do not exist currently)

seth · 2022-12-29 13:21:05

So is this correct as per the wiki in your last link

Yes.
Except you need only the file in ~/.config/plasma-workspace/env/ which is sourced by plasma and the variable is irrelevent in other contexts.

exup · 2022-12-30 09:28:20

Hi after the changes I still have the same issue.

Here is the contents of the file

#!/bin/sh
export KWIN_FORCE_SW_CURSOR

and the file location name and attributes

-rwxr-xr-x 1 user1 user1 39 Dec 30 20:24 /home/user1/.config/plasma-workspace/env/kwin_vars.sh

V1del · 2022-12-30 09:30:18

It should probably read

export KWIN_FORCE_SW_CURSOR=1

so that a value is assigned

exup · 2022-12-30 10:24:16

Awesome, all good, I have three screens functioning correctly. Also gone are the issues with the plasma launch bar lag issue (which were under xorg) and learnt a little about wayland along the way.

I suppose I should monitor this bug as posted above to see if I can eventually turn off the work around. https://bugs.kde.org/show_bug.cgi?id=459929 although its been flagged as resolved upstream. So maybe I should add/follow to this bug https://github.com/DisplayLink/evdi/issues/388

I will give it 48 hours and mark this solved if no issues tomorrow my time.

exup · 2022-12-31 07:59:04

One issue I still see issue in both wayland and xorg setups is the OpenGL is complaining about the amdgpu. See below

amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-13)
amdgpu: amdgpu_device_initialize failed.
amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-13)
amdgpu: amdgpu_device_initialize failed.
EGL client extensions string:
EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query
EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses
EGL_EXT_client_extensions EGL_KHR_debug EGL_EXT_platform_device
EGL_EXT_platform_wayland EGL_KHR_platform_wayland
EGL_EXT_platform_x11 EGL_KHR_platform_x11 EGL_EXT_platform_xcb
EGL_MESA_platform_gbm EGL_KHR_platform_gbm
EGL_MESA_platform_surfaceless
GBM platform:
EGL API version: 1.4
EGL vendor string: Mesa Project
EGL version string: 1.4
EGL client APIs: OpenGL OpenGL_ES
EGL driver name: kms_swrast
EGL extensions string:

see above for eglinfo full details in pastebin.

seth · 2022-12-31 09:04:37

Post teh entire system journal and (for an xorg session) your xorg log.

Lone_Wolf · 2022-12-31 11:13:59

No logs needed, this is very likely due to the way eglinfo works .

Ensure nothing graphical is active ((Boot to multi-user target, login to console as user or stop x, wayland, display manager from a tty) , then run eglinfo and there will be no error message.

see https://gitlab.freedesktop.org/mesa/mesa/-/issues/7289

exup · 2023-01-01 06:41:38

Hi,

ok no error reported after running eglinfo and the first few lines of the output are below. So I can take it I can ignored what is being reported in the GUI of OpenGL.

EGL client extensions string:
EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query
EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses
EGL_EXT_client_extensions EGL_KHR_debug EGL_EXT_platform_device
EGL_EXT_platform_wayland EGL_KHR_platform_wayland
EGL_EXT_platform_x11 EGL_KHR_platform_x11 EGL_EXT_platform_xcb
EGL_MESA_platform_gbm EGL_KHR_platform_gbm
EGL_MESA_platform_surfaceless
GBM platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
EGL driver name: radeonsi
EGL extensions string:

there was an failed message later in the out put but I assume thats because Wayland and or Xorg are not started. (no graphical service are running)

Wayland platform:
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
EGL driver name: radeonsi
EGL extensions string:

Arch Linux

#1 2022-12-22 05:39:48

[SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#2 2022-12-22 10:10:16

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#3 2022-12-22 12:05:55

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#4 2022-12-23 17:36:50

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#5 2022-12-24 15:39:42

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#6 2022-12-29 06:08:58

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#7 2022-12-29 07:49:34

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#8 2022-12-29 09:14:45

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#9 2022-12-29 11:06:49

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#10 2022-12-29 13:21:05

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#11 2022-12-30 09:28:20

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#12 2022-12-30 09:30:18

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#13 2022-12-30 10:24:16

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#14 2022-12-31 07:59:04

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#15 2022-12-31 09:04:37

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#16 2022-12-31 11:13:59

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

#17 2023-01-01 06:41:38

Re: [SOLVED] Display Link - slow redraw of task bar in KDE Plasma

Board footer