-
Notifications
You must be signed in to change notification settings - Fork 12
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
X11 does not work after atta vaapidevice #123
Comments
Unable to reproduce this within my Gentoo setup. The similar effect might occur when using Intel's media-driver with unsupported hardware (read: Haswell).
|
i found the problem, but don't know how to solve it. |
Unable to reproduce the reported bug in a windowed mode either using the current GIT master. I'm having a bit newer kernel (4.19.8) and ffmpeg (4.1) than you, but only one monitor and that might make a difference. |
Did some other tests. When i deactivate 2 Monitors with randr everthing works but if there is more than one Monitor activ atta vaapidevice X11 freezes. |
So it's definitely a more then 1 Monitor Problem. |
yesterday i have tried it again after a System Update, and it works, no more system freeze. VAAPIDEVICE SYSTEM INFORMATION REPORTinxi
vainfo
ffmpeg
gcc
svdrpsend
INCLUDE THIS REPORT INTO YOUR GITHUB ISSUE |
After updating my Gentoo system vaapidevice don't work as expected.
I start my Notebook and vdr is started with vaapidevice in detached.mode.
If i attach (svdrpsend plug vaapidevice atta) a window open with black surface is opened and i can hear audio.
But i can't switch to any other open programm nor can i open the OSD.
If i detach vaapidevice audio is gone but the black screen is still there.
I also stop vdr but the black screen remains open and i have to restart X.
It has something todo with the driver i use with X it's the modesetting driver if i change X to use the deprecated intel driver from xf86-video-intel everything works as expected.
VAAPIDEVICE SYSTEM INFORMATION REPORT
inxi
vainfo
ffmpeg
gcc
svdrpsend
INCLUDE THIS REPORT INTO YOUR GITHUB ISSUE
The text was updated successfully, but these errors were encountered: