Your message dated Mon, 17 Apr 2017 23:00:02 +0100
with message-id <[email protected]>
and subject line Re: Bug#860490: libass5 crashed ffmpeg and in vlc
has caused the Debian Bug report #860490,
regarding libass5 crashed ffmpeg and in vlc
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
860490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860490
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libass5
Version: 0.13.6-1
Severity: important
Dear Maintainer,
While using libass5 in combination with various media players I encountered a
bug which rendered mpv and totem completely useless and disabled most subtitles
in vlc:
"ffmpeg: symbol lookup error: /usr/lib/x86_64-linux-gnu/libass.so.5: undefined
symbol: FT_Outline_EmboldenXY"
&
"Codec not supported:
VLC could not decode the format "ssa " (SubStation Alpha subtitles)"
However, I could fix it by simply updating the package manually with a
checkinstall package from the git https://github.com/libass/libass/ and linking
the libraries manually to the newer versions so ffmpeg could find them:
"sudo ln -s /usr/local/lib/libass.so.9 /usr/lib/x86_64-linux-gnu/libass.so.5
sudo ln -s /usr/local/lib/libass.so.9.0.0 /usr/lib/x86_64-linux-
gnu/libass.so.5.3.2"
So please consider updating the package to the latest version, because
according to this thread http://forums.debian.net/viewtopic.php?f=10&t=131764
I'm not the only one with the package. I describe my solution there at the end
too.
Cheers!
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
(In the future, remember to CC the bug on all replies)
On 17/04/17 22:51, Jan Röhrbein wrote:
> Hello there,
>
>>A bug similar to this happened before (#842522) >and was caused by having
>>freetype-infinality installed. Do you have that >installed?
>
> Yes I have freetype-infinality installed.
>
>>There is no version 0.13.6-1 of libass5 - maybe you >got this package from
>>somewhere else?
>
> The version 0.13.6-1 is a checkinstall package based on the most recent
> release of libass on github which is working fine with infinality. The
> debian packages have a 1: at the beginning front, so I guess it should
> be 1:0.13.6-1 correctly. Sorry for the confusion, I should have reverted
> to the old version for the bug report.
>
> I mainly reported it because the update to the latest github release
> fixed it for me. I didn't know about the infinality bug.
>
> I will send you the output you asked for tomorrow.
Given that you have freetype-infinality installed, I don't need that
information since I already know what the problem is. To use libass from
Stretch you need freetype 2.4.10 and I'm guessing you don't have that
version. I don't know much about infinality but you may have to find
some newer patches and upgrade freetype yourself.
Since this isn't a bug in any Debian packages - I'm closing the bug.
Thanks,
James
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
pkg-multimedia-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
