| Summary: | VAAPI crash when playing h264 video | ||
|---|---|---|---|
| Product: | [Unmaintained] phonon-backend-gstreamer | Reporter: | Richard Z. <rz> |
| Component: | general | Assignee: | Daniel Vrátil <dvratil> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | myriam, romain.perier, sitter, tdfischer |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | debugging output | ||
|
Description
Richard Z.
2015-03-11 20:30:19 UTC
*** Bug 345049 has been marked as a duplicate of this bug. *** #6 0xffffffff in __vaDriverInit_0_36 () at /usr/lib/dri/i965_drv_video.so Looks like a GPU driver bug to me, so there's probably not much we can do about it in Phonon, but still let's take a look: could you run Dolphin from terminal with the following command: PHONON_BACKEND_DEBUG=5 PHONON_GST_DEBUG=5 dolphin &> dolphin.log and try to reproduce the crash? This will create a dolphin.log file with lots of debug output. Attach the file here, maybe we can find out some more details in there ;) Created attachment 91913 [details]
debugging output
https://bugzilla.redhat.com/show_bug.cgi?id=1192654 - the workaround described there should solve your problem, but unfortunately there's nothing we can do about this in Phonon, this is an upstream vaapi/intel driver bug. I don't think it is that bug. For me vlc works (as do kaffeine, mplayer and many other). Neither get any kernel msg like the other bug. Also I am 99% sure the issue appeared long after I installed F21 and not long before I first reported it. Dolphin preview and gwenview are the only ones crashing programs. What do gwenview and dolphin preview have in common that the other don't have? Dolphin and GwenView are both using Phonon Gstreamer, the others you listed are not using Phonon at all, but that still does not convince me it's a Phonon bug ;-) It is possible that the other programs simply ignore VAAI, and thus don't crash, because they don't try to initialize it. Can you reproduce the crash by running vainfo from libva-utils package? no coredump from vainfo $ vainfo libva info: VA-API version 0.36.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/dri/i915_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit note that vainfo tries to open a nonexisting file /usr/lib/dri/i915_drv_video.so while gwenview opens the exisitng /usr/lib/dri/i965_drv_video.so and crashes. (915 vs 956) My mainboard seems to have a 915, [ 1.310217] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 1.323470] [drm] initialized overlay support [ 1.323494] [drm] Initialized i915 1.6.0 20141121 for 0000:00:02.0 on minor 0 it would appear that dolphin first tries to open i915 and when that fails somehow fails back to 965? libva info: VA-API version 0.36.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/dri/i915_drv_video.so libva info: va_openDriver() returns -1 libva info: VA-API version 0.36.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/dri/i915_drv_video.so libva info: va_openDriver() returns -1 libva info: VA-API version 0.36.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_36 Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |