[gentoo-user] Wayland assorted problems

[gentoo-user] Wayland assorted problems

[Wol]

[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]

I'm still trying to get Wayland to work reliably. At the moment I log in 
at a TTY, then fire it up with "startplasma-wayland" ... except it 
doesn't start properly!

I'm GUESSING part of the problem is my video card isn't set up properly. 
But I thought I'd followed the gentoo guide, and compiled the Radeon and 
R600 drivers into my kernel. I prefer to compile stuff in the kernel and 
not as modules, and I told it to load the drivers into the kernel, but 
am worried I might have missed something. I've changed it for the next 
kernel so it'll be a module loading what it wants from the firmware 
directory, so hopefully that'll be better but I'm not sure.

I did an lspci -k and got this for the video card ...

09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] RV710 [Radeon HD 4350/4550]
	Subsystem: ASUSTeK Computer Inc. RV710 [Radeon HD 4350/4550]
	Kernel driver in use: radeon
	Kernel modules: radeon

I notice it says "VGA compatible", and not what the wiki page leads me 
to expect - something like "Video driver" - which makes me think the 
card isn't set up properly.

The symptoms basically are that wayland always hangs the first attempt 
to start it. Once killed from another tty it MAY (or may not) start 
successfully.


I mentioned Thunderbird - that keeps on losing contact with the 
compositor or something which is why it keeps crashing ...


And I run a multi-user system. I tried to fire up wayland as a second 
user, and got the error

kwin_xwl: /tmp/.X11-unix is not owned by root or us

Of course it isn't - it's not a user specific link so of course it's 
going to clash with another user!

I attach the wayland log I got in case it gives anybody any other clues 
as to what's going on.

Cheers,
Wol

[-- Attachment #2: geoff.wayland.log --]
[-- Type: text/plain, Size: 4869 bytes --]

No backend specified through command line argument, trying auto resolution
kwin_wayland_drm: drmSetClientCap for Atomic Mode Setting failed. Using legacy mode on GPU "/dev/dri/card0"
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5089:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5091:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5093:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5097:47: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5099:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5107:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5111:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5113:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5117:45: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5120:46: this compose sequence is a duplicate of another; skipping line
OpenGL vendor string:                   X.Org
OpenGL renderer string:                 AMD RV710 (DRM 2.50.0 / 5.10.74-gentoo, LLVM 13.0.0)
OpenGL version string:                  3.0 Mesa 21.2.5
OpenGL shading language version string: 1.30
Driver:                                 R600G
GPU class:                              Unknown
OpenGL version:                         3.0
GLSL version:                           1.30
Mesa version:                           21.2.5
Linux kernel version:                   5.10.74
Requires strict binding:                no
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no
Filter multi-plane format 961959257
Filter multi-plane format 825316697
Filter multi-plane format 842093913
Filter multi-plane format 909202777
Filter multi-plane format 875713881
Filter multi-plane format 961893977
Filter multi-plane format 825316953
Filter multi-plane format 842094169
Filter multi-plane format 909203033
Filter multi-plane format 875714137
Filter multi-plane format 842094158
Filter multi-plane format 909203022
kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP
kwin_xwl: /tmp/.X11-unix is not owned by root or us
kwin_xwl: Failed to create Xwayland connection sockets
kdeinit5: Aborting. $DISPLAY is not set. 
kdeinit5: Aborting. $DISPLAY is not set. 
kwin_libinput: Libinput: event7  - Chicony USB Keyboard: client bug: event processing lagging behind by 20ms, your system is too slow

startplasma-waylandsession: Starting up...qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
libpng warning: iCCP: known incorrect sRGB profile
qt.svg: <input>:406:376: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:407:130: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:408:130: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:408:393: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:409:130: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:410:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:411:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:412:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:413:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:413:379: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:413:631: Could not add child element to parent element because the types are incorrect.
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
libpng warning: iCCP: known incorrect sRGB profile
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
"kwin_wayland_wrapper" ("--xwayland", "/usr/lib64/libexec/startplasma-waylandsession") exited with code 15
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
kwin_wayland_drm: Mode setting failed

Re: [gentoo-user] Wayland assorted problems

[Jack]

On 2021.11.14 17:51, Wol wrote:
> I'm still trying to get Wayland to work reliably. At the moment I log  
> in at a TTY, then fire it up with "startplasma-wayland" ... except it  
> doesn't start properly!
> 
> I'm GUESSING part of the problem is my video card isn't set up  
> properly. But I thought I'd followed the gentoo guide, and compiled  
> the Radeon and R600 drivers into my kernel. I prefer to compile stuff  
> in the kernel and not as modules, and I told it to load the drivers  
> into the kernel, but am worried I might have missed something. I've  
> changed it for the next kernel so it'll be a module loading what it  
> wants from the firmware directory, so hopefully that'll be better but  
> I'm not sure.
> 
> I did an lspci -k and got this for the video card ...
> 
> 09:00.0 VGA compatible controller: Advanced Micro Devices, Inc.  
> [AMD/ATI] RV710 [Radeon HD 4350/4550]
> 	Subsystem: ASUSTeK Computer Inc. RV710 [Radeon HD 4350/4550]
> 	Kernel driver in use: radeon
> 	Kernel modules: radeon
> 
> I notice it says "VGA compatible", and not what the wiki page leads  
> me to expect - something like "Video driver" - which makes me think  
> the card isn't set up properly.
I haven't tried Wayland in quite a while, but this motivates me to try  
again soon.  However, my equivalent line is:

1c:00.0 VGA compatible controller: Advanced Micro Devices, Inc.  
[AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X]

and Wayland did run for me when I last tried it.  What wiki page are  
you looking at, since I don't see any reference to "video driver."
> 
> The symptoms basically are that wayland always hangs the first  
> attempt to start it. Once killed from another tty it MAY (or may not)  
> start successfully.
> 
> 
> I mentioned Thunderbird - that keeps on losing contact with the  
> compositor or something which is why it keeps crashing ...
> 
> 
> And I run a multi-user system. I tried to fire up wayland as a second  
> user, and got the error
> 
> kwin_xwl: /tmp/.X11-unix is not owned by root or us
> 
> Of course it isn't - it's not a user specific link so of course it's  
> going to clash with another user!
> 
> I attach the wayland log I got in case it gives anybody any other  
> clues as to what's going on.
> 
> Cheers,
> Wol

Re: [gentoo-user] Wayland assorted problems

[Marco Rebhan]

[-- Attachment #1: Type: text/plain, Size: 404 bytes --]

On Sunday, 14 November 2021 23:51:37 CET Wol wrote:
> I'm still trying to get Wayland to work reliably. At the moment I log
> in at a TTY, then fire it up with "startplasma-wayland" ... except it
> doesn't start properly!

Have you tried starting it with "dbus-run-session startplasma-wayland"? 
IIRC that's needed and it won't start correctly without, at least I 
start it that way on my system.

-Marco

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Wayland assorted problems

[Wol]

On 17/11/2021 19:13, Marco Rebhan wrote:
> On Sunday, 14 November 2021 23:51:37 CET Wol wrote:
>> I'm still trying to get Wayland to work reliably. At the moment I log
>> in at a TTY, then fire it up with "startplasma-wayland" ... except it
>> doesn't start properly!
> 
> Have you tried starting it with "dbus-run-session startplasma-wayland"?
> IIRC that's needed and it won't start correctly without, at least I
> start it that way on my system.
> 
I'll try that (again) but I know first time round I was trying all sorts 
of ways, and it probably included that, and didn't seem to have any effect.

Cheers,
Wol

Re: [gentoo-user] Wayland assorted problems

[Wol]

On 17/11/2021 20:59, Wol wrote:
> On 17/11/2021 19:13, Marco Rebhan wrote:
>> On Sunday, 14 November 2021 23:51:37 CET Wol wrote:
>>> I'm still trying to get Wayland to work reliably. At the moment I log
>>> in at a TTY, then fire it up with "startplasma-wayland" ... except it
>>> doesn't start properly!
>>
>> Have you tried starting it with "dbus-run-session startplasma-wayland"?
>> IIRC that's needed and it won't start correctly without, at least I
>> start it that way on my system.
>>
> I'll try that (again) but I know first time round I was trying all sorts 
> of ways, and it probably included that, and didn't seem to have any effect.
> 
Well, just tried starting wayland again (my system locked up so I had to 
reboot), and wayland won't start. With or without dbus-run-session.

Weirdly, I've noticed it seems to start working after a kernel upgrade, 
and then won't start again after a reboot or two ... WHY!?!?

Cheers,
Wol

Re: [gentoo-user] Wayland assorted problems

[Jack]

On 2021.11.14 17:51, Wol wrote:
> I'm still trying to get Wayland to work reliably. At the moment I log  
> in at a TTY, then fire it up with "startplasma-wayland" ... except it  
> doesn't start properly!
Seems to work fine for me (with minimal testing.)
> 
> I'm GUESSING part of the problem is my video card isn't set up  
> properly. But I thought I'd followed the gentoo guide, and compiled  
> the Radeon and R600 drivers into my kernel. I prefer to compile stuff  
> in the kernel and not as modules, and I told it to load the drivers  
> into the kernel, but am worried I might have missed something. I've  
> changed it for the next kernel so it'll be a module loading what it  
> wants from the firmware directory, so hopefully that'll be better but  
> I'm not sure.
> 
> I did an lspci -k and got this for the video card ...
> 
> 09:00.0 VGA compatible controller: Advanced Micro Devices, Inc.  
> [AMD/ATI] RV710 [Radeon HD 4350/4550]
> 	Subsystem: ASUSTeK Computer Inc. RV710 [Radeon HD 4350/4550]
> 	Kernel driver in use: radeon
> 	Kernel modules: radeon
1c:00.0 VGA compatible controller: Advanced Micro Devices, Inc.  
[AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X]
         Subsystem: XFX Pine Group Inc. Cape Verde XT [Radeon HD  
7770/8760 / R7 250X]
         Kernel driver in use: radeon
         Kernel modules: radeon, amdgpu
> 
> I notice it says "VGA compatible", and not what the wiki page leads  
> me to expect - something like "Video driver" - which makes me think  
> the card isn't set up properly.
> 
> The symptoms basically are that wayland always hangs the first  
> attempt to start it. Once killed from another tty it MAY (or may not)  
> start successfully.
> 
> 
> I mentioned Thunderbird - that keeps on losing contact with the  
> compositor or something which is why it keeps crashing ...
No crash, although I didn't run it very long.
> 
> 
> And I run a multi-user system. I tried to fire up wayland as a second  
> user, and got the error
> 
> kwin_xwl: /tmp/.X11-unix is not owned by root or us
> 
> Of course it isn't - it's not a user specific link so of course it's  
> going to clash with another user!
When you run multiple copies of xorg, each one runs in a different  
console.  I wouldn't be surprised if wayland simply isn't set up to do  
that.
> 
> I attach the wayland log I got in case it gives anybody any other  
> clues as to what's going on.
The attached log includes the above kwin error.  Can you post one where  
there isn't another wayland session running?  I'd also confirm that  
directory does go away when no X or wayland is running.  You might need  
to manually delete it.

Jack

Re: [gentoo-user] Wayland assorted problems

[Wol]

[-- Attachment #1: Type: text/plain, Size: 3726 bytes --]

On 17/11/2021 23:54, Jack wrote:
> On 2021.11.14 17:51, Wol wrote:
>> I'm still trying to get Wayland to work reliably. At the moment I log 
>> in at a TTY, then fire it up with "startplasma-wayland" ... except it 
>> doesn't start properly!
> Seems to work fine for me (with minimal testing.)
>>
>> I'm GUESSING part of the problem is my video card isn't set up 
>> properly. But I thought I'd followed the gentoo guide, and compiled 
>> the Radeon and R600 drivers into my kernel. I prefer to compile stuff 
>> in the kernel and not as modules, and I told it to load the drivers 
>> into the kernel, but am worried I might have missed something. I've 
>> changed it for the next kernel so it'll be a module loading what it 
>> wants from the firmware directory, so hopefully that'll be better but 
>> I'm not sure.
>>
>> I did an lspci -k and got this for the video card ...
>>
>> 09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
>> [AMD/ATI] RV710 [Radeon HD 4350/4550]
>>     Subsystem: ASUSTeK Computer Inc. RV710 [Radeon HD 4350/4550]
>>     Kernel driver in use: radeon
>>     Kernel modules: radeon
> 1c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
> [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X]
>          Subsystem: XFX Pine Group Inc. Cape Verde XT [Radeon HD 
> 7770/8760 / R7 250X]
>          Kernel driver in use: radeon
>          Kernel modules: radeon, amdgpu
>>
>> I notice it says "VGA compatible", and not what the wiki page leads me 
>> to expect - something like "Video driver" - which makes me think the 
>> card isn't set up properly.
>>
>> The symptoms basically are that wayland always hangs the first attempt 
>> to start it. Once killed from another tty it MAY (or may not) start 
>> successfully.
>>
>>
>> I mentioned Thunderbird - that keeps on losing contact with the 
>> compositor or something which is why it keeps crashing ...
> No crash, although I didn't run it very long.
>>
>>
>> And I run a multi-user system. I tried to fire up wayland as a second 
>> user, and got the error
>>
>> kwin_xwl: /tmp/.X11-unix is not owned by root or us
>>
>> Of course it isn't - it's not a user specific link so of course it's 
>> going to clash with another user!
> When you run multiple copies of xorg, each one runs in a different 
> console.  I wouldn't be surprised if wayland simply isn't set up to do 
> that.
>>
>> I attach the wayland log I got in case it gives anybody any other 
>> clues as to what's going on.
> The attached log includes the above kwin error.  Can you post one where 
> there isn't another wayland session running?  I'd also confirm that 
> directory does go away when no X or wayland is running.  You might need 
> to manually delete it.
> 
Okay, I rebooted the system, and tried to start Wayland. The first log 
is the output of my first attempt. This hung and I had to kill it. 
Actually, it was worse than that, <ctrl><alt><f2> caused the video 
driver or somesuch to crash - I ended up with a scrambled display, and 
had to ssh in and reboot ...

I then googled, and because it said DISPLAY is not set, I tried setting 
it to both DISPLAY=localhost:0 and DISPLAY=0:0. This gave two identical 
logs, the second one, which didn't hang - it just failed to start and 
terminated.

I'm trying to install and run the latest kernel - the current kernel has 
compiled the driver and firmware into the kernel, I've told the new 
kernel to build it as a module and not load the firmware into the 
kernel, but you've seen my post about genkernel ... where simply trying 
to tell genkernel to put the final initramfs somewhere other than the 
default causes fatal errors in the build ...

Cheers,
Wol

[-- Attachment #2: wayland.211120-2.log --]
[-- Type: text/plain, Size: 183 bytes --]

No backend specified through command line argument, trying auto resolution
KWin exited with code 1
Launching kwin
startplasmacompositor: Shutting down...
startplasmacompositor: Done.

[-- Attachment #3: wayland.211120.log --]
[-- Type: text/plain, Size: 3634 bytes --]

No backend specified through command line argument, trying auto resolution
kwin_wayland_drm: drmSetClientCap for Atomic Mode Setting failed. Using legacy mode on GPU "/dev/dri/card0"
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5089:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5091:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5093:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5097:47: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5099:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5107:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5111:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5113:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5117:45: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5120:46: this compose sequence is a duplicate of another; skipping line
OpenGL vendor string:                   X.Org
OpenGL renderer string:                 AMD RV710 (DRM 2.50.0 / 5.10.61-gentoo, LLVM 13.0.0)
OpenGL version string:                  3.0 Mesa 21.2.5
OpenGL shading language version string: 1.30
Driver:                                 R600G
GPU class:                              Unknown
OpenGL version:                         3.0
GLSL version:                           1.30
Mesa version:                           21.2.5
Linux kernel version:                   5.10.61
Requires strict binding:                no
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no
Filter multi-plane format 961959257
Filter multi-plane format 825316697
Filter multi-plane format 842093913
Filter multi-plane format 909202777
Filter multi-plane format 875713881
Filter multi-plane format 961893977
Filter multi-plane format 825316953
Filter multi-plane format 842094169
Filter multi-plane format 909203033
Filter multi-plane format 875714137
Filter multi-plane format 842094158
Filter multi-plane format 909203022
kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP
kwin_xwl: /tmp/.X11-unix does not exist. Please check your installation
kwin_xwl: Failed to create Xwayland connection sockets
kdeinit5: Aborting. $DISPLAY is not set. 
kdeinit5: Aborting. $DISPLAY is not set. 
startplasma-waylandsession: Starting up...qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
libpng warning: iCCP: known incorrect sRGB profile
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
libpng warning: iCCP: known incorrect sRGB profile
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
"kwin_wayland_wrapper" ("--xwayland", "/usr/lib64/libexec/startplasma-waylandsession") exited with code 15
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
The Wayland connection broke. Did the Wayland compositor die?

Re: [gentoo-user] Wayland assorted problems IDENTIFIED

[Wol]

On 20/11/2021 19:59, Wol wrote:

> Okay, I rebooted the system, and tried to start Wayland. The first log 
> is the output of my first attempt. This hung and I had to kill it. 
> Actually, it was worse than that, <ctrl><alt><f2> caused the video 
> driver or somesuch to crash - I ended up with a scrambled display, and 
> had to ssh in and reboot ...
> 
> I then googled, and because it said DISPLAY is not set, I tried setting 
> it to both DISPLAY=localhost:0 and DISPLAY=0:0. This gave two identical 
> logs, the second one, which didn't hang - it just failed to start and 
> terminated.
> 
> I'm trying to install and run the latest kernel - the current kernel has 
> compiled the driver and firmware into the kernel, I've told the new 
> kernel to build it as a module and not load the firmware into the 
> kernel, but you've seen my post about genkernel ... where simply trying 
> to tell genkernel to put the final initramfs somewhere other than the 
> default causes fatal errors in the build ...
> 
> Cheers,
> Wol

 From the KDE Wayland web page ...

 > Now switching back to the tty KWin is running on should show the 
started window and allow to interact with it. Support for running KWin 
on a tty is still in it's early stages. Bugs are to be expected and 
there are known missing features. Please consider it only as a mode to 
experiment with.

Hmmm .... so I need to be running from sddm or similar if I want it to 
work ... which will open a complete 'nother can of worms ...

Cheers,
Wol