https://bugs.kde.org/show_bug.cgi?id=514073
--- Comment #2 from [email protected] --- I have originally faced this issue with Telegram Desktop. Based on my basic (and probably incorrect) understanding of XDG Portal mechanism, I've incorrectly assumed that this issue should be present for all uses of KDE XDG Portal, but that seems to be NOT the case on practice. I have done a bit more testing and do NOT see this issue for most of my apps (including Firefox and Chrome browsers), but still see it for Telegram (screencast attached). The only relevant entries I see in Telegram debug logs are stuff like: ``` qt.qpa.wayland.textinput: virtual void QtWaylandClient::QWaylandTextInputv3::enableSurface(wl_surface*) Try to enable surface 0x560cd98bb5d0 with focusing surface 0x560ccfead8f0 qt.qpa.wayland.textinput: virtual void QtWaylandClient::QWaylandTextInputv3::enableSurface(wl_surface*) Try to enable surface 0x560ccfead8f0 with focusing surface 0x560cd98bb5d0 qt.qpa.wayland.textinput: virtual void QtWaylandClient::QWaylandTextInputv3::enableSurface(wl_surface*) Try to enable surface 0x560cd9c02e30 with focusing surface 0x560ccfead8f0 qt.qpa.wayland.textinput: virtual void QtWaylandClient::QWaylandTextInputv3::enableSurface(wl_surface*) Try to enable surface 0x560cd662c0a0 with focusing surface 0x560ccfead8f0 ``` If it matters, I am using official Telegram Desktop client from Arch repo (version 6.3.10-1). -- You are receiving this mail because: You are watching all bug changes.
