| Summary: | [wayland] KRDC main window elements stop being properly repainted/refreshed after disconnecting RDP session. | ||
|---|---|---|---|
| Product: | [Applications] krdc | Reporter: | S.Trzmiel <xeno> |
| Component: | general | Assignee: | Urs Wolfer <uwolfer> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | aacid, ctrlaltca, mike |
| Priority: | NOR | Keywords: | wayland-only |
| Version First Reported In: | 22.08.1 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
S.Trzmiel
2022-10-17 17:12:26 UTC
This is also affecting me after just upgrading to Ubuntu 22.10. But I'm running KRDC under GNOME 43 and Xorg, not Wayland. This issue is worse for me, just opening a new connection then going back to the first shows me a blank blue screen for my connections and eventually KRDC becomes unresponsive and unusable. I will try running under a KDE session on a new user account as well (I tried under KDE session on Xephyr under my account and same thing happens). Recent updates (Plasma 5.26.4-1, KF5-5.100) made it even worse now even with searchbar empty window refuses to refresh. Is this app even maintained? (In reply to S.Trzmiel from comment #3) > Recent updates (Plasma 5.26.4-1, KF5-5.100) made it even worse now even with > searchbar empty window refuses to refresh. Is this app even maintained? actually I think they said the maintainer is not really able to keep up with it anymore which is a shame because it really is useful when it works. however i found in https://bugs.kde.org/show_bug.cgi?id=460089 that Qt 5.15.7 does fix these problems. It's just not so easy to get it compiled, but Fedora might move faster to get that version in the repos. > Those issues are not present under X11
This is your answer.
Well, so that's not right answer as Plasma is moving towards wayland sesion by default. It's sad to see KDE apps bitrot :( (In reply to Mike Russo from comment #4) > however i found in https://bugs.kde.org/show_bug.cgi?id=460089 that Qt > 5.15.7 does fix these problems. It's just not so easy to get it compiled, > but Fedora might move faster to get that version in the repos. Hi, Thanks for headsup, but unfortunately this bug is not fixed by Qt5 5.15.7 update. I'm already on KF5-5.100/Qt5 5.15.7 , yet still krdc under wayland open remote desktop in separate window leaving main app window corrupted. (In reply to S.Trzmiel from comment #7) > > Hi, > Thanks for headsup, but unfortunately this bug is not fixed by Qt5 5.15.7 > update. I'm already on KF5-5.100/Qt5 5.15.7 , yet still krdc under wayland > open remote desktop in separate window leaving main app window corrupted. Ah, sorry about that - I know I saw that under wayland it's always opened in a separate window, because they are using X11 embed to put the xfreerdp inside krdc window. It would need rewrite to work with window inside. Though you can probably run only krdc through Xwayland somehow? TBH I don't min't running freerdp in separate window, the thing that makes krdc unusable is corrupted and unresponsive main window. (In reply to S.Trzmiel from comment #9) > TBH I don't min't running freerdp in separate window, the thing that makes > krdc unusable is corrupted and unresponsive main window. What happens if you start up a Konsole window, set the environment variable to run in X11 like export QT_QPA_PLATF0RM=xcb and then run krdc from that window? That will let you have the rest of your desktop using Wayland, but start up Xwayland (if it's not already running) and run krdc in Xwayland. Launching krdc with env variable QT_QPA_PLATF0RM set made no changes. Krdc used to have problems with RDP connections under Wayland, since it ran xfreerdp directly. RDP support has been rewritten as of 24.* version, and now it works fine for most of the people under wayland. Feel free to open a new ticket if you experience bugs on a more recent version. 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |