Skip to content
This repository has been archived by the owner on Nov 1, 2021. It is now read-only.

make_current should fail on noop output #1662

Closed
emersion opened this issue Apr 23, 2019 · 2 comments · Fixed by #1683
Closed

make_current should fail on noop output #1662

emersion opened this issue Apr 23, 2019 · 2 comments · Fixed by #1683
Labels

Comments

@emersion
Copy link
Member

Making it succeed can trick the caller into thinking it can render.

@ammen99 Thoughts?

@emersion emersion added the bug label Apr 23, 2019
@ammen99
Copy link
Member

ammen99 commented Apr 23, 2019

I am fine with such a change, since the typical scenario is to use make_current when you get a frame event (which you don't get for noop outputs anyway).

The only other place where make_current is used is in wlr_output_preferred_read_format. The read_format in turn is called only in wlr_screencopy_v1.c which will trigger an assertation failure on outputs without renderers (seems like there is an implicit assumption that noop outputs shouldn't be exposed to clients?)

@emersion
Copy link
Member Author

emersion commented Apr 23, 2019

Ah, indeed. Screen capture interfaces should probably stop assuming all outputs have a renderer.

emersion added a commit to emersion/wlroots that referenced this issue Apr 29, 2019
ddevault pushed a commit that referenced this issue Apr 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

Successfully merging a pull request may close this issue.

2 participants