Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arch Icons broken? #12017

Closed
TheBabu opened this issue Dec 31, 2017 · 10 comments
Closed

Arch Icons broken? #12017

TheBabu opened this issue Dec 31, 2017 · 10 comments

Comments

@TheBabu
Copy link

TheBabu commented Dec 31, 2017

Hello, I am currently using Arch Linux and today I have noticed that some of my icons are missing or changed, for instance all of the icons that existed in my polybar are now missing,
Broken state:
screenshot_2017-12-30_21-41-07
screenshot_2017-12-30_21-41-57
Original State:
screenshot_2017-12-17_10-05-57
screenshot_2017-11-07_20-58-01

Even though the icons do not show in polybar they do seem to show in termite the terminal emulator, but they are still not the correct icons:
Broken State:
screenshot_2017-12-30_09-53-36
Original State:
Cannot find a screenshot of these icons but they are most definitely not correct, I simply copy pasted these icons from here:http://fontawesome.io/cheatsheet/ and it seems like they have not changed.

The icons suddenly broke, I may have done an update of some type and then rebooted which caused this.

Thanks for any help!

@Hi-Angel
Copy link

Same here. FTR, here's a reddit discussion on the topic.

@tagliala
Copy link
Member

Is this somehow related to #10102 ?

@Hi-Angel
Copy link

Mhm, sorry, I personally don't have enough expertise to tell certainly, however the difference I see is that OP from #10102 just did something, and now it doesn't work, and also it was in 2016 year; whereas the current issue is about regression between 4.7.0 and 5.0.2, and is in fact reproducible back and forth by (up|down)grading the font-awesome, and restarting apps.

@tagliala
Copy link
Member

tagliala commented Dec 31, 2017

5.0.2 and 4.7.0 are not compatible.

5.0.2 is based on three files: one with bold weight (solid), one with normal weight (regular), one with brands

Icon names are different, so you cannot simply upgrade from 4.7.0 to 5.0.2 without changing internals

@Hi-Angel
Copy link

Ok, I think you're right. For some reason I couldn't make i3bar working with the new naming of fonts, and lack of font-related debug output doesn't help either. However I think Font-Awesome per se is alright because on the linked reddit topic peoples who are using polybar managed to make it working by simply changing the name from FontAwesome to FontAwesome5Free and FontAwesome5Brands, and the fact it's not working for some app out there is not a concern of a font per se.

@TheBabu
Copy link
Author

TheBabu commented Jan 1, 2018

Downgrading to Font Awesome 4 did the trick, I guess this is an issue with naming, and I'll deal with that later, :P

@cheng93
Copy link

cheng93 commented Jan 1, 2018

This worked for me (for polybar)

font-2 = FontAwesome5Free
font-3 = FontAwesome5Free:style=Solid

and I assume if you want to use brands use FontAwesome5Brands

fc-list
fc-match

to help debug

@Hi-Angel
Copy link

Hi-Angel commented Jan 1, 2018

@cheng93 it's specific to polybar.

@TheBabu
Copy link
Author

TheBabu commented Jan 1, 2018

Huh, this is kinda weird fc-list gives me this:
screenshot_2018-01-01_07-27-57
And fc-match also gives me this:
screenshot_2018-01-01_07-30-05
Everything seems to be spaced out...
(My icons are still working because I haven't started a new instance of it)

@TheBabu
Copy link
Author

TheBabu commented Jan 2, 2018

Meh, closing this issue because this seems to be a lot of changes that were expected, not bugs of any sort...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants