So, after trying this in other user, the problems persist. They work the same that with QT_QPA_PLATFORM=xcb environment variable. Does this mean that our settings aren’t the problem after all?
I don’t want to believe it, but disconnecting one monitor fixed it.
Now, the question is why hahaha.
1 Like
So we could say is something developers have to fix?
I forgot to mention that I did try downgrading Kdenlive to fix the issue, to no avail.
As for QT updates on the day I started experiencing the issue.
There were many QT packages that received updates.
I’ll wait for the updates to become available and report back if it is fixed.
The general why is: Wayland isn’t ready for all setups yet. Some people have a perfect experience, others don’t. While the experience varies on x11 as well, it is usually just Nvidia-related.
And though sometimes people experience the same issue on both Wayland and x11, it would not surprise if it is due to some settings that are Wayland-related interfering with x11. ← This, though, is completely just a guess.
That makes sense with Wayland.
If I recall correctly, Wayland on Gnome is still experimental and that would make sense why the program works better on Plasma Wayland.
With what we know now, mostly likely hahaha.
Wayland is experimental on all DEs/WMs. Some just work better.
1 Like
Well, someone had to suffer first to make Pipewire available for mainstream use. Now It’s our turn.
1 Like
No. Now it’s your turn. I don’t use Wayland at all. 
I barely even use a DE as much. I mean, I have Cinnamon installed, and I logged into the Wayland session to test it. Things were mostly okay, but there were a few glitches.
I will wait it out, as I know x11 is not going anywhere for at least 5 years from now. So, when Wayland is at x11’s level in terms of compatibility, especially with Nvidia, then I’ll use it.
That being said, by then I’m likely to have another device with AMD instead, but I shouldn’t feel forced to use either Nvidia or AMD based on a DE or window compositor/manager.
1 Like
It was a mistake, I mean our like everyone else who uses Wayland besides me. English is not the best language when you talk about others, I mean you can use the word “you” for singular and plural, that’s confusing.
1 Like
I get what you mean. Next time say, “Now It’s someone else’s turn.”
1 Like
Starting now I will speak in binary XD. 01011000 01000100
1 Like
I had to explain something similar to someone on the forum where I typed “you”, but in English, based on the context, that just means “people/users/etc.” - a group in general.
The person got very angry, thinking that I meant him/her specifically. 
I love my English, though. I can be as specific as I want or as vague as I want, using different words or just using my tone (in person, of course).
1 Like
After 5 - 6 beers, it’s all the same language. 
3 Likes
Update on the bug from the report made in the first post of this thread.
Seems to be a Mutter related issue and looks to be fixed upstream.
https://bugreports.qt.io/browse/QTBUG-124450
Another stopgap solution is running affected apps non-maximized.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.