So I went ahead and installed the 20231113 KDE PLASMA RPI4 img. Running on the PI5
I get it to boot up and I have chosed X11 PLASMA instead of wayload.
I can go into the desktop wayland or Xorg no problem.
problem I have run into is that the .Xauthority file is not create, I can touch it and chmod etc but the magic cookie is not generated, meaning .Xauthority stays empty.
I will have to chalk it up as buggy img, I tried fresh again, sudo is broken and .Xauthority doesn’t get generated.
Are you sure it should be ?
.Xauthority is sorta legacy … modern sddm/kde creates the file dynamically…
something like /run/sddm/xauth_EWhnye
So … do you need a static one or a way to reliably find it for a reason?
If so there are ways to handle that …
https://wiki.archlinux.org/title/SDDM#X_authority_(aka_MIT-MAGIC-COOKIE)_file
And I do not use KDE but seems like some where here in the forums there was some issue with some one using KDE and sudo; the keyboard not getting set right. Seems like there was a setting some where in it’s Settings that had to be set for your country. Also I installed it one time and had an issue with ssh. Seems like it had it’s own firewall settings somewhere that had to be changed.
plasma too heavy for Pi4, may be create LXQT profile to build img?
had install LXQT-1.4 but never make it wayland-session 
no problem with xcb, but want wayland.
That sounds like one of the issues, but also get authorization messages when I try to run glxinfo -B -display :0 (via ssh)
The actual desktop loads and works fine, in autologin, but throw ups issues when logging out then in)
You use -display :10.0 and with login to the device with ssh -Y user@device-ip-address. I do not seem to get a true report headless though as I am logged in via a terminal or could be a diff in graphics between the devices.
Default ssh X11DisplayOffset:
[ray@jellyfin ~]$ cat /etc/ssh/sshd_config | grep Display
#X11DisplayOffset 10
[ray@vim3 ~]$ glxinfo -B -display :0
Invalid MIT-MAGIC-COOKIE-1 key
Error: unable to open display :0
[ray@vim3 ~]$ glxinfo -B -display :10.0
Error: unable to open display :10.0
[ray@vim3 ~]$ glxinfo -B -display :0
Invalid MIT-MAGIC-COOKIE-1 key
Error: unable to open display :0
[ray@vim3 ~]$ glxinfo -B -display :10.0
name of display: :10.0
display: :10 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Mesa (0xffffffff)
Device: llvmpipe (LLVM 16.0.6, 128 bits) (0xffffffff)
Version: 23.1.8
Accelerated: no
Video memory: 3783MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 4.5
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
VBO free memory - total: 42 MB, largest block: 42 MB
VBO free aux. memory - total: 3525 MB, largest block: 3525 MB
Texture free memory - total: 42 MB, largest block: 42 MB
Texture free aux. memory - total: 3525 MB, largest block: 3525 MB
Renderbuffer free memory - total: 42 MB, largest block: 42 MB
Renderbuffer free aux. memory - total: 3525 MB, largest block: 3525 MB
Memory info (GL_NVX_gpu_memory_info):
Dedicated video memory: 4293967379 MB
Total available memory: 4293971163 MB
Currently available dedicated video memory: 42 MB
OpenGL vendor string: Mesa
OpenGL renderer string: llvmpipe (LLVM 16.0.6, 128 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 23.1.8-arch.1
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.5 (Compatibility Profile) Mesa 23.1.8-arch.1
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.1.8-arch.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
[ray@jellyfin ~]$ glxinfo -B -display :10.0
name of display: :10.0
display: :10 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Mesa (0xffffffff)
Device: llvmpipe (LLVM 16.0.6, 128 bits) (0xffffffff)
Version: 23.2.1
Accelerated: no
Video memory: 7808MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 4.5
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
VBO free memory - total: 42 MB, largest block: 42 MB
VBO free aux. memory - total: 5382 MB, largest block: 5382 MB
Texture free memory - total: 42 MB, largest block: 42 MB
Texture free aux. memory - total: 5382 MB, largest block: 5382 MB
Renderbuffer free memory - total: 42 MB, largest block: 42 MB
Renderbuffer free aux. memory - total: 5382 MB, largest block: 5382 MB
Memory info (GL_NVX_gpu_memory_info):
Dedicated video memory: 4294805987 MB
Total available memory: 4294813795 MB
Currently available dedicated video memory: 42 MB
OpenGL vendor string: Mesa
OpenGL renderer string: llvmpipe (LLVM 16.0.6, 128 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 23.2.1+rpt2.1
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.5 (Compatibility Profile) Mesa 23.2.1+rpt2.1
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.2.1+rpt2.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
[ray@jellyfin ~]$ glxinfo -B -display :0
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Broadcom (0x14e4)
Device: V3D 4.2 (0xffffffff)
Version: 23.2.1
Accelerated: yes
Video memory: 7808MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 3.1
Max compat profile version: 3.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.1
OpenGL vendor string: Broadcom
OpenGL renderer string: V3D 4.2
OpenGL core profile version string: 3.1 Mesa 23.2.1+rpt2.1
OpenGL core profile shading language version string: 1.40
OpenGL core profile context flags: (none)
OpenGL version string: 3.1 Mesa 23.2.1+rpt2.1
OpenGL shading language version string: 1.40
OpenGL context flags: (none)
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 23.2.1+rpt2.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
I tried that , uncommented X11DisplayOffset 10
no joy
sddm plasma KDE all work fine but remotely (ssh) I can’t make it work?
The commented lines in that file are showing the defaults. You only uncomment if you want to change the value.
Give more info. I do not know what you are getting when you are logged in using KDE or how you logged in with ssh or what you are getting logged in via ssh. You have not been giving complete info
so this is the message when I run glxinfo -B -display :0
[user@pi5 ~]$ glxinfo -B -display :0
Authorization required, but no authorization protocol specified
Error: unable to open display :0
I run the below and it gives the :0 output.
ls /tmp/.X11-unix | tr ‘X’ ‘:’
:0
Xorg is running.
I disabled the inbuilt firewall.
Also I am trying to run x11vnc.
x11vnc -auth guess -forever -loop -noxdamage -repeat -rfbauth /home/user/.vnc/passwd -rfbport 5900 -shared
xauth: file /home/user/.Xauthority does not exist
16/11/2023 16:17:58 -auth guess: failed for display=‘unset’
I tried to explain above what works and what does not work by giving examples.
What is the complete ssh command you are using to log in to the pi. Supposed to be ssh -Y. Here it would be:
ssh -Y ray@192.168.1.23
This will not work via ssh to the pi; only if used locally in a DE. Use this:
glxinfo -B -display :10.0
Ive tried it with -X or -Y
it would work on the previous install that I migrated from xfce to kde xorg (rpi4 to rpi5 post).
This fresh img is giving me this issue. glxinfo -display :0 would usually always give me a working output as long as ssh and a Xorg server was enabled on the desktop os.
I installed KDE Plasma here and noticed who ever was maintaining the image did not enable X11Forwarding yes like I do in the images I maintain.
Change /etc/ssh/sshd_config
#X11Forwarding no
To:
X11Forwarding yes
Restart sshd.service
Logout and back in to your ssh session with ssh -Y Then glxinfo -B -display :10.0
I still am getting it using SW llvmpipe renderer instead of V3D via ssh. I believe that is what you are going to get also.
I do not use or have a use for any screen sharing program. If I occasionally have to use a GUI I use ssh -Y.
I have uncommented X11Fordwaring yes.
I have compared it the the working bookworm install and seems to match.
I even managed to install mesa from git .
not sure why it points to .Xauthority, maybe a KDE5 or SDDM thing?
I noticed that also yesterday when testing. I do not see that with my non KDE images. Guessing it’s a warning put out checking ways to connect. It does not seem to affect anything. Might have to do with what @cscs said in his above post.
Ok,
I tested KDE manjaro in my PC, and yest it has the same issue with ssh and running glxinfo -B -display :0
cookie issue. I cant be bothered with KDE5
so switching back to the xfce platform where all works as I want.
I reinstalled the latest plasma image, was there ever a working solution ?
vnc to wayland
wayvnc etc