The upstream bug report <https://bugzilla.mozilla.org/show_bug.cgi?id=1245811> is not about uBlock Origin. It is about resolving alias names in fontconfig files. But neither uBlock Origin nor Font Awesome use any fontconfig files. So these are different issues.

The original extension at Mozilla.org [1] doesn't include a symbolic link for Linux. This wouldn't make much sense, since the relative path to the original file may be different on different distributions. Also, an extension on Mozilla.org can't require a font package on Linux.


I don't think, that a Firefox extension can actually resolve Linux symbolic links. Extensions are written in JavaScript, XML and CSS, and they are run by Firefox. So I don't think, that extensions have an understanding of the underlying file system.

The symbolic link was introduced on your side, possibly by an automatic system to search for duplicate files and replace them with symbolic links to their canonical installation paths.

But it just doesn't work in this case. You should replace the symbolic link with the original font file, and then it works now, and not someday in Firefox 48.


[1] https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/

Just download the xpi file from this site, and open it in Xarchiver. You will find, that the original extension has its own copy of the font file.

--
Hartmut Buhrmester

_______________________________________________
Pkg-mozext-maintainers mailing list
Pkg-mozext-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mozext-maintainers

Reply via email to