Re: strange vlc error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 13 Aug 2018 18:35:36 +0200
François Patte <francois.patte@xxxxxxxxxxxxxxxxxxxx> wrote:

> Bonjour,
> 
> I had some problem with vlc after an upgrade to f28.
> 
> For *one* user vlc crashed on startup with these messages:
> 
> libva info: VA-API version 1.1.0
> libva info: va_getDriverName() returns 0
> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
> libva info: va_openDriver() returns -1
> [00007f72ac002c50] glconv_vaapi_x11 gl error: vaInitialize: unknown
> libva error
> libva info: VA-API version 1.1.0
> libva info: va_getDriverName() returns 0
> libva info: Trying to open /usr/lib64/dri/r600_drv_video.so
> libva info: Found init function __vaDriverInit_1_1
> radeon: Failed to allocate virtual address for buffer:
> radeon:    size      : 65536 bytes
> radeon:    alignment : 4096 bytes
> radeon:    domains   : 4
> radeon:    va        : 0x0000000000800000
> radeon: Failed to deallocate virtual address for buffer:
> radeon:    size      : 65536 bytes
> radeon:    va        : 0x800000
> 
> 3 times
> 
> then:
> 
> radeonsi: Failed to create a context.
> 
> then crash!
> 
> This did not occur for other users. So I deleted all vlc config and
> cache files, but the problem remained.
> 
> I installed libva-intel-driver package and the problem disappeared.
> 
> I am wondering why this package was missing for only one user....

Pure speculation.  Does the computer have dual graphics, the other
device being intel?  Did the user who fails ever use vlc with the intel
graphics?  It is possible that vlc kept that information internally,
and checked whether the intel card was available.  Are you sure you
deleted all vlc configuration information?  Maybe it checks
somewhere else to see if the user has access to, or ever accessed, the
intel device? When it failed the intel call, the call by radeon to
allocate the buffer failed for some associated reason, wreckage left
over from the intel call.

Easy to check.  You know it is working now.  Remove
libva-intel-driver.  Is the problem still gone, or does it now occur
again?

What does the output show on the users that succeed?  Is there still a
call to the intel device?
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/7O5O7ZZ464XPUVHSCYGFQ4GPW5VAIY2D/



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux