https://bugs.kde.org/show_bug.cgi?id=425271
Jim <hardlo...@gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hardlo...@gmx.de
--- Comment #53 from Jim <hardlo...@gmx.de> ---
This is probably caused by the fix to
https://bugs.kde.org/show_bug.cgi?id=357443.
There's this bit in fdoselectionmanager.cpp
> else if (responseType == XCB_VISIBILITY_NOTIFY) {
> const auto event = reinterpret_cast<xcb_visibility_notify_event_t
> *>(ev);
> // it's possible that something showed our container window, we have
> to hide it
> // workaround for BUG 357443: when KWin is restarted, container window
> is shown on top
> if (event->state == XCB_VISIBILITY_UNOBSCURED) {
> for (auto sniProxy : m_proxies.values()) {
> sniProxy->hideContainerWindow(event->window);
> }
> }
> }
Where does the XCB_VISIBILITY_UNOBSCURED event originate? Is it a bug that a
window is reported as unobscured if it's located on an offscreen position? Or
is it the responsibility of the client to check if the window is unobscured and
on-screen?
--
You are receiving this mail because:
You are watching all bug changes.
