Over the past week, some of our users have encountered a known error message where the default osd_cat font was not found. This problem occurs for a number of reasons. We’ll cover them below.
Approved: Fortect
Origin of xfontsel. It can show you the fonts that may be available on your system.
Using * instead of Definites also makes the font name more portable, like With:
– * – bold helvetica – * – * – * – 34 – * – * – * – * – * – *
begin – * – helvetica – * – * – * – * – * – * – * – * – * – * – * to see if the font is present at all.
Appendix: the iirc encoding at the end will not have the iso8859 part. If everyone wants iso8859-1 encoding, use:
– * – helvetica-fett – * – * – * – 34 – * – * – * – * – * – 1
_________________
PKA Cuber
Increase [RESOLVED] in the subject line if you think the issue is resolved.
Accept unanswered message
- fool
- Member
- Registered: 30.09.2012
- Posts: 1
Subject: Osd_cat Does Not Write SMS
I can confirm this problem: after a global update (I came from gentoo) my osd_cat doesn’t show any text, but the cursor works efficiently. My first idea was that the implemented standard font (-f, –font = FONT used very well (default: Might -misc-fixed-medium-r-semicondensed – * – * – * – * – c- * – * – *)) cause the problem. Unfortunately, I didn’t understand how a slaveThe font spec is losing, so I’m not doing well if I just used a crappy parameter during testing – or if my mistake could be elsewhere.
Gentoo package prerequisites for xosd `–
x11-libs / xosd-2.2.14-r1 amd64
` – x11-libs / libX11-1.5.0 (x11 – libs / libX11) amd64
`– x11-libs / libXext-1.3.1 (x11-libs / libXext) amd64 ` —
x11-libs / libXt-1.1. 3 (x11-libs / libXt)
amd64 `– media-fonts / font-misc-misc-1.1.2 (media-fonts / font-misc-misc) amd64
` – x11 -proto / xineramaproto-1.2.1 (x11-proto / xineramaproto) amd64
`– x11-proto / xextproto-7.2.1 (x11-proto / xextproto) amd64 ` —
x11-proto / xproto-7.0.23-r1 Amd64 (x11-proto / xproto)
`– virtual / pkgconfig-0 (virtual / pkgconfig) amd64
` – sys – devel / automake-1.12.4 (> = sys-devel / automake-1.11.1) ~ amd64
`– sys-devel / autoconf-2.69 (> = sys-devel / autoconf – 2.68) ~ amd64
`– sys-devel / libtool-2.4.2 (sys-devel / libtool) ~ amd64
I practically reinstalled them, but the problem persists. So it could have been a mistake.
