Dropping Unmatched Character

[krionical]

When I run polybar example (with the default config), I get this:

polybar example
warn: No monitor specified, using "DVI-I-2"
error: Disabling module "bspwm" (reason: Could not find socket: /tmp/bspwm_0_0-socket)
error: module/xbacklight: Could not get data (err: XCB_NAME (15))
error: Disabling module "xbacklight" (reason: Not supported for "DVI-I-2")
error: Disabling module "battery" (reason: No suitable way to get current charge state)
warn: Dropping unmatched character  (U+e26f)
warn: Dropping unmatched character  (U+e028)
warn: Dropping unmatched character  (U+e026)
warn: Dropping unmatched character  (U+e0cb)
warn: Dropping unmatched character  (U+e016)
warn: Dropping unmatched character  (U+e10c)
warn: Dropping unmatched character  (U+e26f)
warn: Dropping unmatched character  (U+e028)
warn: Dropping unmatched character  (U+e026)
warn: Dropping unmatched character  (U+e0cb)
warn: Dropping unmatched character  (U+e016)
warn: Dropping unmatched character  (U+e10c)
warn: Dropping unmatched character  (U+e26f)
warn: Dropping unmatched character  (U+e028)
warn: Dropping unmatched character  (U+e026)
warn: Dropping unmatched character  (U+e0cb)
warn: Dropping unmatched character  (U+e016)
warn: Dropping unmatched character  (U+e10c)
warn: Dropping unmatched character  (U+e26f)
warn: Dropping unmatched character  (U+e028)
warn: Dropping unmatched character  (U+e026)
warn: Dropping unmatched character  (U+e0cb)
warn: Dropping unmatched character  (U+e016)
warn: Dropping unmatched character  (U+e10c)
warn: Dropping unmatched character  (U+e26f)
warn: Dropping unmatched character  (U+e028)
warn: Dropping unmatched character  (U+e026)
warn: Dropping unmatched character  (U+e0cb)
warn: Dropping unmatched character  (U+e016)
warn: Dropping unmatched character  (U+e10c)
warn: Dropping unmatched character  (U+e26f)
warn: Dropping unmatched character  (U+e028)
warn: Dropping unmatched character  (U+e026)
warn: Dropping unmatched character  (U+e0cb)
warn: Dropping unmatched character  (U+e016)
warn: Dropping unmatched character  (U+e10c)

The unmatched character issue will run in a loop. As far as I know, I have all the requirements met to install Polybar. It seems like the modules re-load and I can't tell if it due to a font, or a module problem, or something else.

[pazz]

I get the same thing, I believe it is due to some utf-8 charcters in our config (the example config contains many of those).

My config contains

font-3 = FontAwesome:pixelsize=14;0

which should be present:

fc-match FontAwesome:pixelsize=14
FontAwesome.otf: "FontAwesome" "Regular"

Any ideas?

[jaagr]

The example config requires the siji font. Just remove/replace the unicode characters if you don't have the font.

[pazz]

OK, thanks. I am fighting to get this font installed here (debian testing). Dis anyone get this to work?
I suppose this issue is "solved" then and could be closed.

[krionical]

I have the siji font installed, or so that's what it says. I'd be happy to perform some checks on that if necessary.

[stooj]

OK, after quite a while fighting with this, I've managed to get rid of the warnings.

On my (Arch) box, siji is installed, but font-2 = siji:pixelsize=10;1 does not match the actual font. Using fc-match I've managed to get it working by using the following three fonts:

font-0 = fixed:pixelsize=10;1
font-1 = unifont:fontformat=truetype:size=8:antialias=false;0
font-2 = "Wuncon Siji:pixelsize=10;1"

[helionmelion]

yes changing to wuncon siji the bar was able to show the character from "format-prefix = " ! but the message still remains

addendum
on the polybar - the character 𝄞 (song) is not showing but  (cpu) are showing.
strangely here in chromium, the song char is showing but the cpu char is showing like a small retangle ......

[Deluxo]

My bitmap font's declaration stopped working, which looked like this: font-0 = --terminus-medium-r---12------iso10646-*;0
Using pango notation works, but now i get shitty pango rendering.
This is definitely a bug!

[jaagr]

@Deluxo X fonts are no longer supported. Try font-0 = terminus:pixelsize=12

[jhnguyy]

I'm having an interesting case of this as well.

Dropping unmatched character (U+0002)

The thing is I am using plenty of fonts that should work with it.

font-0 = roboto:pixelsize=13 font-1 = fontawesome:pixelsize=13 font-2 = dejavusans:pixelsize=13 font-3 = unifont:pixelsize=13
(Sorry, I couldn't get the line breaks to work)

It broke while using Google Chrome, going to this link

This site says that the fonts I used above should work (Roboto/unifont).

Here are the fc-match outputs for the above fonts.
fc-match roboto:pixelsize=13 Roboto-Regular.ttf: "Roboto" "Regular"
fc-match fontawesome:pixelsize=13 fontawesome-webfont.ttf: "FontAwesome" "Regular"
fc-match dejavusans:pixelsize=13 DejaVuSans.ttf: "DejaVu Sans" "Book"
fc-match unifont:pixelsize=13 Unifont.ttf: "Unifont" "Medium"

polybar -v polybar 3.0.4

edit: Sorry about this. It seems like I didn't spend enough time researching this. This problem is the same as #393. My issue is coming from my config label = %title:0:50...% under xwindow. Using max-len option was a fix.

[jaagr]

this should be fixed @skystrife's pr (#434)

[krionical]

My solution to this problem eventually involved migrating to arch linux. I wound up crawling through the guts of Ubuntu changes to the font system such as where fonts are stored and eventually discovered fontconfig was not playing nice for whatever reason with the unicode fonts. So, I made the fatal mistake of uninstall fontconfig which I figured was probably a bad idea, and it took about a zillion packages with it including something that lightdm needed which basically made a mess of everything.

When I moved to arch and installed polybar, it worked fine. I think it has something to do with all the changes Ubuntu made to how fonts are stored and how that works with fontconfig. I hope your fix involves that somehow or accounts for it.

[jaagr]

Closing due to inactivity.