KDE Is Down To Just One Wayland Showstopper Bug Remaining

[Brittle2]

Note that there's work being done to solve that specific use case :-)

btw it's already merged on plasma 6 :-D
(why it convert my face to emoji :/)

[openminded]

What I wonder is how anybody could consider that a showstopper. It might be annoying for sure and it prevents certain workflows but a *showstopper*? It makes me think of this: https://xkcd.com/1172/

For the record, I am forced to use Mac OSX at work and the "always above others" doesn't exist and I can still work without major issues (and that missing feature is *really* annoying). I only say this because this is clearly not a *showstopper*

To me, this is certainly a showstopper, as well as non-existent (in that list) feature called window shading. Both features served me well for ages, in fact, this is one of the most convenient ways to work with multiple windows without using virtual desktops and window tiling.
Built-in touchpad gestures getting in a way of other, more feature-rich tools to control gestures, is absent in the list too. This is ridiculous. It IS a showstopper. When I do a swipe on my touchpad, I expect Plasma doing some single action, not both built-in action and another one, configured by me. This could be a non-showstopper if those built-in action were not hardcoded without any way to switch them off, but KDE devs deliberately made them this way.

[mercster]

non-existent (in that list) feature called window shading. Both features served me well for ages, in fact, this is one of the most convenient ways to work with multiple windows without using virtual desktops and window tiling.

Hah... I love window shading! Good for quickly getting a window out of your way but keeping it in place. I don't think many people use that anymore, or even know it exists.

[oleid]

1. I don't use those as most people don't.
2. Never used those as most people don't.

Did you ask them all?

3. NetworkManager has replaced that years ago.
4. blueman-manager has replaced that years ago.

The point is that those things are not well-integrated.
Granted, you can tailor IceWM to do most of the things listed here.
But then you'll get the same -- as you put it -- bloat as the bigger desktops have.

DE have become redundant bloatware most pieces of which are of zero use.

Insert obligatory your-mama-joke here.

[TNZfr]

Which low level X11 layers?

You can have a look here : https://wayland.freedesktop.org/faq.html
Wayland doesn't provide network forwarding. Wayland is not compatible with old X11 apps, but there's a way to manage them thru Wayland, etc ...

Those points were unavoidable at the begining. Now Wayland evolved and x11 compatibility is less and less used in Wayland (for example, synaptic, the package manager, doesn't have have issues anymore under Wayland).

Today, the last issue I meet is screen sharing in Teams client (doesn't work) so I must connect with X11. Other apps, now, seem to work fine. Maybe that's why distros offers wayland by default.

[oleid]

You can have a look here : https://wayland.freedesktop.org/faq.html
Wayland doesn't provide network forwarding. Wayland is not compatible with old X11 apps, but there's a way to manage them thru Wayland, etc

So these are the layers Wayland needs? I expected something different ...

Considering network forwarding: waypipe works fine. So does screen sharing via RDP. There may be more but those were the ones I tested.

I was wondering since you can get a fully functional Wayland environment without any dependencies to X11, if you choose it. It's possible with e.g. Gentoo Linux today.

Those points were unavoidable at the begining. Now Wayland evolved and x11 compatibility is less and less used in Wayland (for example, synaptic, the package manager, doesn't have have issues anymore under Wayland).

Today, the last issue I meet is screen sharing in Teams client (doesn't work) so I must connect with X11. Other apps, now, seem to work fine. Maybe that's why distros offers wayland by default.

Well, but that's an issue with this proprietary software. There _are_ established protocols which are used by contemporary browsers.

[woddy]

This is one of main stoppers for me to switch to wayland, recently firefox and google-chrome fixed their icons, but still lots of apps are crippled! (W generic wayland icon)

I understand it can be a nuisance, but fixing it is really simple, go to where the launcher is (usually /user/share/applications, if it's a flatpak look for it in /var it can change depending on how it's installed, if installed as a user it's in your /home/var/app), now copy the name. Now go to the problematic app, click on the title panel, other actions and choose configure specific settings for application, in the window that appears choose add properties, scroll to the bottom and select desktop file name, delete and replace the name with the copied one, restart the 'apps and icons will be correct. It seems like a long process but in fact it takes 15 seconds.

[TNZfr]

Ok, but did you test Teams in client mode and browser mode ?
It's the same issue with VMWare Horizon. When you must work 8 hours a day with it, browser approach is not your friend.

[MadCatX]

Ok, but did you test Teams in client mode and browser mode ?
It's the same issue with VMWare Horizon. When you must work 8 hours a day with it, browser approach is not your friend.

I might not be remembering correctly but I think that screensharing worked for me from browser Teams. I had a feeling that the standalone Teams package is dragging behind its browser counterpart in terms of features and bugfixes.

[avis]

- NM does not provide a GUI
- NM does not provide a secure password storage

1. It has provided UI for a over decade now, NM applet + NM connection editor. This is not an exclusive Gnome component, this works perfectly anywhere under Linux where you have UI (Xorg or Wayland, whatever). XFCE includes and does use it.



2. Secure storage for passwords? It has zero relationship to DE. I've used Gnome and KDE for quite a lot, never used KWallet or whatever Gnome offers for that. It's a totally arbitrary feature you've just made up. And how is storing passwords in files owned by the root user is not secure storage?