Yeah, I don't want to do it with packages, just need a manual method without removing regular kwin.
Announcement
Collapse
No announcement yet.
KDE's Plasma Wayland Session Continues Seeing More Crash Fixes
Collapse
X
-
Originally posted by bple2137 View Post
I don't think that Archlinux is favoring one DE or another. It usually means that maintainers responsible for the packages are busy or there are some problems with the new version that holds them from updating.
Quick check: KDE Plasma and GNOME are being packaged by completely different people. You can find their emails easyli and ask them why it takes so long.
I'm waiting for the new version too, but I like when updates are as much painless as possible and just being patient. In time when it makes it into stable, my extensions will be compatible again ☺️
Comment
-
Logic would have it that before solving multi monitor problems, you have to troubleshoot single monitor problems, as it is the most used. Not saying multi monitor issues on wayland are not taken into consideration, but it is just a matter of priority.
- Likes 1
Comment
-
Originally posted by tomas View PostTemplarGR
.
.
Have you considered Manjaro?
KDE, Xfce and Gnome are all official flavors:
https://manjaro.org/downloads/official/gnome/
As someone who has used both, saying "run Manjaro" to an Arch user is like telling a Debian person to run Ubuntu 18.04 because Debian 11 isn't up-to-date enough.
- Likes 1
Comment
-
It's great to so many crash fixes in every release, but it's horrible there are so many crashes in the previous release... I guess it's all Xorg to Wayland labor pain?
If a Gnome fanboy group kept, say, Arch Gnome packages up-to-date, and KDE guys did the same for theirs, one would assume it's only a good thing. As long as they don't attack each other, and are able to discuss technicalities in a civilized manner. The same kind of infighting happens in companies, too, and it's just so very sad...
Comment
-
Originally posted by TemplarGR View PostNo, the real reason is they have an anti-gnome agenda and i am tired of that. Fanboism has no place in a distro.
- Likes 2
Comment
-
Originally posted by direc85 View PostIt's great to so many crash fixes in every release, but it's horrible there are so many crashes in the previous release... I guess it's all Xorg to Wayland labor pain?
If a Gnome fanboy group kept, say, Arch Gnome packages up-to-date, and KDE guys did the same for theirs, one would assume it's only a good thing. As long as they don't attack each other, and are able to discuss technicalities in a civilized manner. The same kind of infighting happens in companies, too, and it's just so very sad...
This is a snippet script that .zshrc sources and it helps with some Wayland and X issues I've had (especially when going between Wayland and X desktops). What it does is set environment variables based on X or Wayland and unsets them for non-GUI sessions. It covers GNOME (GTK), Enlightenment, and KDE with some stuff for Firefox, Qt, and SDL. SDL forced to Wayland will break older 1.2 SDL games since that doesn't have Wayland support. Either set those games manually or comment SDL out.
Code:# Wayland/X11 if [[ $XDG_SESSION_TYPE = "wayland" ]] then # Clutter export CLUTTER_BACKEND="wayland" # GTK export GDK_BACKEND="wayland" # EFL/Enlightenment export ECORE_EVAS_ENGINE="wayland_egl" export ELM_DISPLAY="wl" export ELM_ACCEL="opengl" # Firefox export MOZ_ENABLE_WAYLAND=1 # Qt export QT_QPA_PLATFORM="wayland" # SDL export SDL_VIDEODRIVER="wayland" elif [[ $XDG_SESSION_TYPE = "x11" ]] then # Clutter export CLUTTER_BACKEND="x11" # GTK export GDK_BACKEND="x11" # EFL/Enlightenment export ECORE_EVAS_ENGINE="x11" unset ELM_DISPLAY unset ELM_ACCEL # Firefox export MOZ_ENABLE_WAYLAND="0" # Qt export QT_QPA_PLATFORM="xcb" # SDL export SDL_VIDEODRIVER="x11" else # Clutter unset CLUTTER_BACKEND # GTK unset GDK_BACKEND # EFL/Enlightenment unset ECORE_EVAS_ENGINE unset ELM_DISPLAY unset ELM_ACCEL # Firefox unset MOZ_ENABLE_WAYLAND # Qt unset QT_QPA_PLATFORM # SDL unset SDL_VIDEODRIVER fi
- Likes 2
Comment
-
Originally posted by shmerl View PostYeah, I don't want to do it with packages, just need a manual method without removing regular kwin.
Comment
-
Originally posted by skeevy420 View Post
I don't think KWin is designed to be replaced like that....have multiple, different versions installed alongside each other. IMHO, doing it with packages is the best you'll get unless you want to dig into the sources.
Comment
Comment