Trying to run KDE 6 Plasma with Wayland....

astyle said:
Sometimes, correctly understanding the dependency graph and specifying what should be a dependency and what should NOT be a dependency is in fact the important thing, the theme of the conversation. But this thread is about something else. Something else is the theme of this thread.

Ports and dependencies were an issue long before anyone knew about Wayland.

This thread is about Wayland. All posts are supposed to revolve around Wayland, and the showstoppers that stand in the way of Wayland.

Dependencies and generally running/compiling KDE are NOT of interest in this thread. Therefore, they are off-topic. Please start another thread if you want to talk about dependencies and generally running KDE.

Participants in this conversation already know about dependencies and running KDE, that stuff is already ironed out, and is of no importance to the crowd. The important part is Wayland - and whatever's getting in the way.
Click to expand...
 
It's about KDE running on a graphical screen provided by the Wayland display server? I have it installed as dependency of something X-related but never used it specifically. Is it possible to run a Wayland screen without anything else and not depending on X.org?
 
MG said:
It's about KDE running on a graphical screen provided by the Wayland display server? I have it installed as dependency of something X-related but never used it specifically. Is it possible to run a Wayland screen without anything else and not depending on X.org?
Click to expand...
Wayland is a protocol. Weston (a compositor) is a reference implementation of that protocol.

KDE's kwin is KDE's own implementation of a compositor that implements the Wayland protocol. And yes, it's separate from kwin-x11.

In this thread/conversation, even the very term dependency has a somewhat different meaning than in the context of ports/packages.

I'd advise you to catch up on the contents of this thread, play with what's available, and report on what works.

Yeah, the port graphics/wayland is a dependency of a LOT of other ports in the Ports Collection - that is of no importance to this thread.

But to answer your question:
MG said:
Is it possible to run a Wayland screen without anything else and not depending on X.org?
Click to expand...
Yeah, it's possible, the Handbook walks you through installing a few such compositors.
 
What I am interested in is reliably surving a compositor crash, ala x11. To this day, it's not a question of if , it's a matter of when a wayland session will crash.
 
siladi said:
What I am interested in is reliably surving a compositor crash, ala x11. To this day, it's not a question of if , it's a matter of when a wayland session will crash.
Click to expand...
In my experience I had some sporadic crashes when adding/removing items from a panel, but after few seconds plasmashell just restarted.
 
Maxnix said:
In my experience I had some sporadic crashes when adding/removing items from a panel, but after few seconds plasmashell just restarted.
Click to expand...
And the running apps survive and reconnect to the wayland session? I know that QT_WAYLAND_RECONNECT is a thing in QT6 ... not sure if GTK4 has something for that. Perhaps I should reframe it as a stoic exercise 😏
 
This is regarding surviving compositor crash and not loosing app state.
Looked a bit more into the wayland socket handover situation and according to the very dated resources available (link below) it seems that:

- QT6 apps you get the best reliability
- QT5 apps mmmaybe
- GTK4 being worked on (maybe)
- rest of the universe (sdl, xwayland,wine, etc...) not yet

There are apparently also wayland socket handover patches for other compositors as well (sway,labwc,dwm,hyprland) . not merged of course...

invent.kde.org

Restarting · Wiki · Plasma / KWin · GitLab

Easy to use, but flexible, Wayland Compositor
invent.kde.org invent.kde.org
github.com

GitHub - Ferdi265/wl-restart: restart your compositor when it crashes

restart your compositor when it crashes. Contribute to Ferdi265/wl-restart development by creating an account on GitHub.
github.com github.com

That about captures the current state of the union. If someone knows more about this, please chime in.
 
siladi said:
What I am interested in is reliably surving a compositor crash, ala x11. To this day, it's not a question of if , it's a matter of when a wayland session will crash.
Click to expand...
The reliability of apps surviving a compositor crash is actually pretty good, and not a showstopper any more, to the best of my knowledge.

What remains a showstopper is the page flip timeout bug that seems to be triggered most often by KDE Plasma Wayland sessions. It's an AMD GPU firmware driver bug, but it is one hell of a showstopper when the driver crashes, and takes the whole system down with it, complete with kernel panics on both Linux and BSDs. There's some noise that NVidia users have similar issues, and that downgrading the NVidia firmwares can help.

I've had apps like Konsole and Firefox get restarted after a GPU driver crash (which took the whole system down and forced me to do a hard reboot). After logging back in, I noticed that Firefox remembered its tabs (default behavior under both Xorg and Wayland). Konsole, OTOH, while it did get restarted with the 5 tabs I had open in a Konsole window, I was logged out of SSH sessions, and root sessions that I had open in a couple tabs. Not that much of a problem there, I'd say, but instead a good practice and graceful handling of the crash.
 
For me, Plasma Wayland (Intel GPU) stopped working with the latest pkg updates (latest branch).
In dmesg I see a lot of:
pid 3393 (kwin_wayland), jid 0, uid 1001: exited on signal 11 (no core dump - denied by kern.coredump)
Any ideas?
 
Same here, the Wayland session doesn't start, but the X11 one works.
However, seems there are problems with the new version of Qt libraries: in some pages of sysutils/plasma6-systemsettings controls like checkboxes, radio buttons and sliders are not themed, and the same happens with the config windows of widgets (i.e. the digital clock).
Schermata_20260525_173435.png
Schermata_20260525_173516.png

This is the output I got launching it from the terminal:
Code: 
qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
QLayout: Attempting to add QLayout "" to KCModuleProxyInternal "", which already has a layout
qt.core.qobject.connect: QObject::connect: No such signal KFocusConfig::defaultsIndicatorsVisibleChanged(bool)
QLayout: Attempting to add QLayout "" to KCModuleProxyInternal "", which already has a layout
QLayout: Attempting to add QLayout "" to KCModuleProxyInternal "", which already has a layout
QLayout: Attempting to add QLayout "" to KCModuleProxyInternal "", which already has a layout
QLayout: Attempting to add QLayout "" to KCModuleProxyInternal "", which already has a layout
kf.configwidgets: A widget named "kcfg_AllowKDEAppsToRememberWindowPositions" was found but there is no setting named "AllowKDEAppsToRememberWindowPositions"
kf.configwidgets: A widget named "kcfg_ShadeHover" was found but there is no setting named "ShadeHover"
kf.configwidgets: A widget named "kcfg_ShadeHoverInterval" was found but there is no setting named "ShadeHoverInterval"
kf.configwidgets: A widget named "kcfg_Placement" was found but there is no setting named "Placement"
kf.configwidgets: A widget named "kcfg_ActivationDesktopPolicy" was found but there is no setting named "ActivationDesktopPolicy"
 
Maxnix said:
Same here, the Wayland session doesn't start, but the X11 one works.
However, seems there are problems with the new version of Qt libraries: in some pages of sysutils/plasma6-systemsettings controls like checkboxes, radio buttons and sliders are not themed, and the same happens with the config windows of widgets (i.e. the digital clock).
View attachment 26278View attachment 26279
This is the output I got launching it from the terminal:
Code: 
qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
QLayout: Attempting to add QLayout "" to KCModuleProxyInternal "", which already has a layout
qt.core.qobject.connect: QObject::connect: No such signal KFocusConfig::defaultsIndicatorsVisibleChanged(bool)
QLayout: Attempting to add QLayout "" to KCModuleProxyInternal "", which already has a layout
QLayout: Attempting to add QLayout "" to KCModuleProxyInternal "", which already has a layout
QLayout: Attempting to add QLayout "" to KCModuleProxyInternal "", which already has a layout
QLayout: Attempting to add QLayout "" to KCModuleProxyInternal "", which already has a layout
kf.configwidgets: A widget named "kcfg_AllowKDEAppsToRememberWindowPositions" was found but there is no setting named "AllowKDEAppsToRememberWindowPositions"
kf.configwidgets: A widget named "kcfg_ShadeHover" was found but there is no setting named "ShadeHover"
kf.configwidgets: A widget named "kcfg_ShadeHoverInterval" was found but there is no setting named "ShadeHoverInterval"
kf.configwidgets: A widget named "kcfg_Placement" was found but there is no setting named "Placement"
kf.configwidgets: A widget named "kcfg_ActivationDesktopPolicy" was found but there is no setting named "ActivationDesktopPolicy"
Click to expand...
This is interesting.... my stuff looks fine. I have to run scfb (because I'm on a new IdeaPad 5 2-in-1 laptop with Ryzen AI 7 445, for which GPU drivers still need to be properly cooked), which only allows an Xorg session. Sometimes, an actual reboot of the system helps...
1779733889536.png
 
elgrande said:
Unfortunately it does not work.
To my knowledge this workaround is Nvidia-related though.
Click to expand...
Hi

I prefer to use Nvidia Proffessional/Quadro cards ( low power consumption, no fan noise )
I dont have a machine with AMDGPU installed.

15-Stable ( now 15.1 STABLE ) has been much better WAYLAND Platform than 15-Release.
This Bug was never fixed on 15.0-Release.

288565 – graphics/nvidia-drm-61-kmod and 66-kmod stopped working on 15-current

bugs.freebsd.org bugs.freebsd.org



I have had good results with WAYLAND by building ports form source code ( Xorg , Gnome, KDE ) and make sure that "wayland " Build option is included everywhere in all the packages.

from /etc/make.conf :

{
OPTIONS_SET_FORCE += NLS DOCS OPTIMIZED_CFLAGS MANPAGES INFO GSSAPI_MIT X11 WAYLAND THREADS OPENMP GMP MMX SIMD SSE SSE2 SSE3 AVX AVX2 AVX512
OPTIONS_UNSET_FORCE += EXAMPLES TEST GSSAPI_BASE GSSAPI_HEIMDAL LANG_TH
DEFAULT_VERSIONS+=ssl=openssl linux=rl9
}

ofcousre you also need to have SEATD and CONSOLEKIT2 installed. to run Wayland as stated in the Handbook.

for wayland you need : two environment variables in the .profile to get an operational Cursor.
This probably is an NVIDIA dependency.

export WLR_NO_HARDWARE_CURSORS=1
export KWIN_FORCE_SW_CURSOR=1




This Last month I have been working on commisioning a new Desktop computer with modern CPU + GPU
Initially the machine suffered Kernel Panic when trying to activate DRM 6.6 or DRM 6.9
I was shown the DRM 6.12 repository on GITHUB. which now has been turned in to a port ( graphics/drm-612-kmod ) which i built and installed.
Then T-Aoki was kind to show how to adapt graphics/nvidia-latest-drm-kmod to use the DRM 612 code.
After the Nvida-latest-drm-612-kmod had been recompiled both WAYLAND and X11 Kde desktops worked on the new Desktop computer.
 
drsnx60 said:
Hi

I prefer to use Nvidia Proffessional/Quadro cards ( low power consumption, no fan noise )
I dont have a machine with AMDGPU installed.

15-Stable ( now 15.1 STABLE ) has been much better WAYLAND Platform than 15-Release.
This Bug was never fixed on 15.0-Release.

288565 – graphics/nvidia-drm-61-kmod and 66-kmod stopped working on 15-current

bugs.freebsd.org bugs.freebsd.org



I have had good results with WAYLAND by building ports form source code ( Xorg , Gnome, KDE ) and make sure that "wayland " Build option is included everywhere in all the packages.

from /etc/make.conf :

{
OPTIONS_SET_FORCE += NLS DOCS OPTIMIZED_CFLAGS MANPAGES INFO GSSAPI_MIT X11 WAYLAND THREADS OPENMP GMP MMX SIMD SSE SSE2 SSE3 AVX AVX2 AVX512
OPTIONS_UNSET_FORCE += EXAMPLES TEST GSSAPI_BASE GSSAPI_HEIMDAL LANG_TH
DEFAULT_VERSIONS+=ssl=openssl linux=rl9
}

ofcousre you also need to have SEATD and CONSOLEKIT2 installed. to run Wayland as stated in the Handbook.

for wayland you need : two environment variables in the .profile to get an operational Cursor.
This probably is an NVIDIA dependency.

export WLR_NO_HARDWARE_CURSORS=1
export KWIN_FORCE_SW_CURSOR=1




This Last month I have been working on commisioning a new Desktop computer with modern CPU + GPU
Initially the machine suffered Kernel Panic when trying to activate DRM 6.6 or DRM 6.9
I was shown the DRM 6.12 repository on GITHUB. which now has been turned in to a port ( graphics/drm-612-kmod ) which i built and installed.
Then T-Aoki was kind to show how to adapt graphics/nvidia-latest-drm-kmod to use the DRM 612 code.
After the Nvida-latest-drm-612-kmod had been recompiled both WAYLAND and X11 Kde desktops worked on the new Desktop computer.
Click to expand...
Well everything worked with Intel GPU until the recent qt update in latest ports.
 
astyle said:
This is interesting.... my stuff looks fine. I have to run scfb (because I'm on a new IdeaPad 5 2-in-1 laptop with Ryzen AI 7 445, for which GPU drivers still need to be properly cooked), which only allows an Xorg session.
Click to expand...
Even with Qt version 6.11.1? In this case the problem could be related to how drivers interact with the new libraries? :-/
Maybe using the scfb driver is worth a try (at least for testing).
astyle said:
Sometimes, an actual reboot of the system helps...
Click to expand...
Tried already, no good. :(
drsnx60 said:
15-Stable ( now 15.1 STABLE ) has been much better WAYLAND Platform than 15-Release.
Click to expand...
I have hopes for 15.1-RELEASE. :)
drsnx60 said:
you also need to have SEATD and CONSOLEKIT2 installed. to run Wayland as stated in the Handbook.
Click to expand...
I never used seatd, with just consolekit2 everything worked (regarding KDE, other compositors may have different dependencies).
 
You must log in or register to reply here.
Back
Top