Andrew J. Buehler wrote:
Package: fontconfig-config
Version: 2.6.0-3
Followup-For: Bug #506552
I have just tested downgrading each obviously-could-be-related package
(see list below) to the version in my package archive immediately
preceding the one installed on the same day as the change, and the
problem persists despite the downgrades (which are now reverted).
Therefore, either I've missed a relevant package (possible), or I no
longer have the correct "working" version in my archive (unlikely), or
the problem is one of configuration which is only indirectly affected by
the package contents - e.g. perhaps my local configuration was wiped out
by the upgrade but naturally enough not restored by the downgrade.
Testing was performed by shutting down and reopening Icedove, since it
is much less of a hassle to restart than is Iceweasel, and shows the
problem (in the form in which I see it) far more prominently. There is a
faint chance that this is insufficient - that it would be necessary to
restart X to see a change - but as that would be even more of a hassle
than restarting Iceweasel, I have not tested it yet.
The packages I tested downgrading are, in no particular order but with
the "tested all at once" packages grouped together:
package from to
xulrunner-1.9 1.9.0.4-2 1.9.0.3-1
fontconfig 2.6.0-3 2.6.0-1
fontconfig-config 2.6.0-3 2.6.0-1
libfontconfig1 2.6.0-3 2.6.0-1
libfontconfig1-dev 2.6.0-3 2.6.0-1
icedove 2.0.0.17-1 2.0.0.16-1
x-ttcidfont-conf 31 30
ttf-liberation 1.04.92.dfsg-4 1.04~beta2-2
ttf-opensymbol 1%3a2.4.1-14 1%3a2.4.1-11
I also considered testing ttf-dejavu and libttf2, but the former has not
been updated on my system since four months before the problem
manifested (and seems to be up to date), and the latter has no older
version on my system with which to test.
Any suggestions for packages I could have missed testing, or other
things I might want to try?
--
This line is here because, while I don't want my usual .sig, it
seems unnatural not to have one at all.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
