Package: installation-reports
Boot method: netinst CD
Image version:
http://caesar.acc.umu.se/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64-netinst.iso
Date: 2013-02-08 ~10pm to 2013-02-09 ~ 8am
Machine: Dell Inspiron 7520
Processor: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz,
This is actually an issue with FreeType 2.6.3.
The problem seen here was introduced with [[truetype] Another GX
sanity test.][1] in FreeType VER-2-6-2 and fixed with [[truetype] More
fixes for handling of GX deltas.][2] in FreeType VER-2-7. This will
affect Chromium and Firefox as they are using
Package: libfreetype6
Version: 2.9.1-3
Severity: normal
Tags: patch
With FreeType 2.9 to 2.10.1 (inclusive) and viewing the Oswald font
[0] in Chromium 76 or later (or just in ftview from the freetype-demos
package) the glyph metrics do not scale with the text size.
Issue was tracked upstream
Package: libfontconfig1
Version: 2.13.1-2+b1
Severity: normal
Tags: patch
Request that upstream commits
e2f9f28aed1470a07c33a57940d68b6a3cbe235b [0]
61573ad5f7c4dd0860d613d99d0086433240eb75 [1]
(which are in 2.13.92 and later) be patched into libfontconfig1 2.13.1-3 .
These fix several leaks
$ which kwin
/usr/bin/kwin
$ dpkg -S usr/bin/kwin
kwin-x11: /usr/bin/kwin
kwin-x11: /usr/bin/kwin_x11
$ ls -l /usr/bin/kwin
/usr/bin/kwin -> kwin_x11
$ dpkg --list kwin-x11
ii kwin-11 4:5.17.5-4 amd64 KDE window manager, X11 version
$ kwin --version
kwin: symbol lookup error:
Package: libkscreenlocker5
Version: 5.19.5-4
Severity: serious
Justification: Policy 8.1
X-Debbugs-Cc: bunge...@chromium.org
$ kwin --replace
kwin: symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5: undefined
symbol: _ZN12ScreenLocker7KSldApp30greeterClientConnectionChangedEvy
$ ldd
It's quite interesting to submit a bug report without a working window
manager, but I think this may be related to the commit
https://salsa.debian.org/qt-kde-team/kde/kscreenlocker/-/commit/2320b40c8d6f3ba316c83a31bdba79dc8db6d208
not listing the symbol
Package: freetype
Version: 2.12.1+dfsg-5
This is a request to remove the very experimental COLRv1 support from
libfreetype 2.12.1. The easiest means of doing so would be to patch
the PUT_COLOR_LAYERS_V1 macro [0] like
- #define PUT_COLOR_LAYERS_V1( a ) PUT_COLOR_LAYERS( a )
+ #define
I will take a look into this, but I am confused.
FT_Get_Color_Glyph_Paint cannot be NULL as it is a regular exported
function. This change will affect its behavior to always return 0
(false) but that often happens anyway even without this change (most
fonts don't have COLRv1 tables). For now it's
] is needed in addition to the the COLRv1
disable [1].
[0]
https://gitlab.freedesktop.org/freetype/freetype/-/commit/16f311d72582c117796a23e22074fe9624760ee1
[1]
https://salsa.debian.org/debian/freetype/-/commit/f65637c7f84fa2ccfb14c11d0ed0f315fe83636d
On Thu, Sep 28, 2023 at 10:36 AM Ben Wagner
Package: libfreetype6
Version: 2.12.1+dfsg-2
Severity: important
Tags: patch upstream
X-Debbugs-Cc: bunge...@chromium.org
With FreeType commit f93a897afedf4a634c74d3d2871519e675ee0d83 (which was
released in FreeType 2.12.0) support for OT-SVG was added. However, this
implementation contained a
11 matches
Mail list logo
