Summary: | media-video/ffmpeg-4.3.2: ffplay broken (?): "Could not initialize SDL - No available video device" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | sphakka <marcoep> |
Component: | Current packages | Assignee: | Gentoo Media-video project <media-video> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | ionen, jstein, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
sphakka
2021-02-27 13:54:39 UTC
4.3.1 work? Don't know, I'll try. But I upgraded from 4.2.4 in which it was already broken. Didn't look much into this but I can reproduce with libsdl2[-X] Try to rebuild libsdl2 with USE=X enabled. Yes USE=X on libsdl2 fixes it! Thanks for the tip ^^ Having "X" flag set for libsdl2 may be not enough to fix this problem. I had the same issue with media-video/ffmpeg-4.4.3 and media-libs/libsdl2-2.0.20-r1. In my case libsdl2 already had "X" flag set, but didn't have any additional sound-related flags set (except "sound" flag itself) like "alsa" or "pulseaudio" etc. I've also enabled "alsa" flag for libsdl2 and upgraded it to the version 2.24.2. That fixed the issue. Honestly unless it /only/ works with specifics (e.g. doesn't build with -X, or doesn't work with wayland, only works with pulse, etc...), then this isn't something the ebuild should be looking at. And then libSDL2 technically always has a "usable" backend with USE=sound/video (dummy or diskwrite) if selected, and doesn't know what the users are using. On a desktop profile this is all pretty sane out-of-the-box, otherwise users will need to enable what they use. |