You are not logged in.
@muziknavi did you account for the reportedly relevant window state (maximized) condition?
@zebulon, the qlayout error should™ not be fatal, you don't get that whe using xcb?
Have you tried to move away the ktorrent config?
Are any other Qt6 clients affected?
Online
@muziknavi did you account for the reportedly relevant window state (maximized) condition?
Yeah, maximized window also invisible in F41-rawhide
Offline
No problem here either on KDE Plasma/Wayland, but I do remember running into similar issues as you describe on Gnome before, using some user themes.
Offline
No problem here either on KDE Plasma/Wayland, but I do remember running into similar issues as you describe on Gnome before, using some user themes.
I don't use user themes, this extension is disabled in my system. I don't even change default wallpaper
So, themes is unrelated.
UPD: updated to telegram-desktop-4.16.7-1, bug with "transparent/non-visible" media viewer is still present.
Last edited by Bodyash (2024-04-16 07:17:55)
Offline
It looks like rolling back of qt6-wayland to version 6.6.3-1 is enough to restore functionality, given the completely updated system at the time of writing this post. I use only qBittorrent and telegram-desktop. All other packages, including qt6-base, seem unimportant (but I can’t vouch for that, of course).
Offline
It looks like rolling back of qt6-wayland to version 6.6.3-1 is enough to restore functionality, given the completely updated system at the time of writing this post. I use only qBittorrent and telegram-desktop. All other packages, including qt6-base, seem unimportant (but I can’t vouch for that, of course).
That's not supposed to work. It will simply prevent Qt's Wayland support from initializing, thus making the affected programs fall back to X11.
Last edited by intelfx (2024-04-16 11:19:55)
Offline
I didn’t say that this was a way out of the situation, I just tried to narrow down the search area for the problem.
Offline
@muziknavi did you account for the reportedly relevant window state (maximized) condition?
@zebulon, the qlayout error should™ not be fatal, you don't get that whe using xcb?
Have you tried to move away the ktorrent config?
Are any other Qt6 clients affected?
With wayland, there is no window whatsoever. Only the icon in the desktop bar.
With xcb, A window appears, but the content is black. I can rsize it and move it, but I cannot close it with the cross (I need to kill it).
The qlayout error appears in both cases.
I am wondering if I am having a completely different problem.
Offline
Not sure if it helps to narrow down the problem. I had the issue using Okular thus I resort to flatpak and it runs normally.
Offline
Because you're not using the system-provided Qt 6.7 but whatever version is shipped with that flatpak.
@zebulon
Have you tried to move away the ktorrent config?
Online
I didn’t say that this was a way out of the situation, I just tried to narrow down the search area for the problem.
You missed my point. It does not narrow the search area in any way because all you're doing is basically breaking Qt's wayland backend; what you described is exactly equivalent to uninstalling qt6-wayland altogether.
It was known from the start that the issue only affects Wayland and is mitigated by forcing X11 backend.
Last edited by intelfx (2024-04-16 23:27:42)
Offline
Offline
If anyone wants to stay on Qt 6.6 for the time being but keep updating the rest of the system, I've created a simple repo with Qt 6 and all its reverse dependencies pinned to Qt 6.6.3: https://outpost.intelfx.name/repo/qt663
It should be enough to add this repo above [extra] and force a one-time downgrade with pacman -Syuu (followed by rebuilding any dependent foreign packages, if you have any).
(Note that this will still break if any of Qt's _forward_ dependencies get incompatibly updated in the meantime, so this is still in some ways a partial upgrade, but must be more robust than just downgrade-ing packages one by one.)
Last edited by intelfx (2024-04-17 14:06:13)
Offline
Because you're not using the system-provided Qt 6.7 but whatever version is shipped with that flatpak.
@zebulon
seth wrote:Have you tried to move away the ktorrent config?
I had removed .config/ktorrent files but it did not work
However, removing .local/share/ktorrent fix it!
Of course I lost the info regarding all torrents. This suggest this is a ktorrent bug indeed. Thank you!
Offline
Looks like this bisected to https://github.com/qt/qtwayland/commit/ … 1812a39a29
Per the QT bug report:
https://bugreports.qt.io/browse/QTBUG-124450
Offline
Starting the broken apps with QT_QPA_PLATFORM=xcb and resizing them from their maximized state, then closing and reopening normally with Wayland and then maximizing seems to mitigate the issue. You just have to make sure to resize it before closing it so you can launch it normally with Wayland next time as well. Otherwise you'd have to repeat this process.
Offline
The issue has been fixed in mutter https://gitlab.gnome.org/GNOME/mutter/-/issues/3435
Offline
Verified this issue is fixed with mutter 46.1 tagged release.
Offline
Yes, after fresh update everything is working.
Offline