Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Krunner redraw glitch #70

Open
adriaandegroot opened this issue Mar 15, 2018 · 2 comments
Open

Krunner redraw glitch #70

adriaandegroot opened this issue Mar 15, 2018 · 2 comments

Comments

@adriaandegroot
Copy link
Contributor

With no other windows open, hit alt-space to open krunner. Type in a search string -- I used calc here, but qua will also do enough of a search. I had networking / wifi enabled. There are several sections of results returned by krunner. Hitting ESC when the first section is shown, but before Discover results are in, leaves the krunner results drawn on-screen as a glitch.

krunner

Here the red arrow labeled 1 shows where krunner was before it was canceled. Arrow 2 points to the drawn results from krunner, which are still showing even after canceling krunner. The draw results disappear when something else is drawn, e.g. when another window gets the focus. That's why it is important to have no other windows showing, or to have them well-down on the screen and un-focused, to trigger this redraw issue.

Sometimes -- more rarely than the scenario above -- hitting ESC when the Discover results have been show, also leaves drawing artifacts behind. Again, in this screenshot (1) points to where krunner was, and (2) to the graphical artifacts left behind.

krunner2

@notmart
Copy link

notmart commented Mar 15, 2018

so is a piece of window that stays on screen because an area wasn't redrawn?
is the qt patch about sending the proper damage area landed?

@davidedmundson
Copy link

If you mean my one with net_wm_sync, yeah. But I don't think it'd be relevant here. If a window is unmapped the client shouldn't need to send anything else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants