createFontSet broken with libX11-1.6.4

[mimi1vx]

from xmonad.log:

user error (createFontSet)
user error (createFontSet)
user error (createFontSet)
user error (createFontSet)
user error (createFontSet)
user error (createFontSet)
user error (createFontSet)
user error (createFontSet)
user error (createFontSet)

[geekosaur]

What font are you trying to use?
Note that if you were using an XFT font and then rebuilt xmonad-contrib
without -fuse_xft, you will get this error because XCreateFontSet doesn't
understand XFT fonts.

On Tue, Nov 8, 2016 at 1:58 PM, Ondřej Súkup notifications@github.com
wrote:

from xmonad.log:

user error (createFontSet)
user error (createFontSet)
user error (createFontSet)
user error (createFontSet)
user error (createFontSet)
user error (createFontSet)
user error (createFontSet)
user error (createFontSet)
user error (createFontSet)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#47, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB8SoPz4rDQqgbW7GEPRT7NSXtgC9kL3ks5q8MZCgaJpZM4KsyJG
.

brandon s allbery kf8nh sine nomine associates
allbery.b@gmail.com ballbery@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net

[mimi1vx]

i forgot mention This is on openSUSE: Tumbleweed , official openSUSE packages.

xmobar-contrib is compiled by default with xft flag enabled ..

Plus this erroris triggered by:

    import XMonad.Util.Themes
    import XMonad.Layout.Tabbed

in layoutHook:
tabbed shrinkText (theme smallClean)

so system default font

[liskin]

Is this still an issue?

[andrea-berling]

I think so. I got the same errors while testing with a very minimal configuration that uses tabbed or simpleTabbed as a layoutHook (got here by DDG'ing)

[liskin]

@andrea-berling Are you perhaps hitting xmonad/xmonad-contrib#348?
These errors are expected if there really isn't any font on your system that matches the descriptor.

If, on the other hand, there are matching fonts, yet createFontSet still fails, then we might have a bug here. Sounds unlikely, though.

[andrea-berling]

Maybe. I didn't specify any descriptor for the font name, I guess I used the one defined by the default configuration