bumblebee-status: Icons not showing in power themes

When enabling a theme (like -t solarized-powerline or -t powerline) colours work however the icons do not.

Trying to figure out how to take screenshots with scrot now, will post a comment with a screenshot soon. Running Debian 9.

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 1
  • Comments: 34 (15 by maintainers)

Most upvoted comments

Hm, that looks like you don’t have the powerline fonts installed?

Maybe the problem goes away if you do sudo pacman -S powerline-fonts awesome-terminal-fonts ? (not sure whether pango uses the TTF or the terminal fonts for awesome, honestly)

Also, if you want to see whether Inconsolata looks better, you need to install ttf-inconsolata.

I really hope this helps resolve the issue, as I’m running out of ideas 😛

Oh, man you are the savior! Thanks a lot!

sudo pacman -S powerline-fonts awesome-terminal-fonts fixed it immediately!

So I didn’t get how to install fonts apparently.

But I followed the installation procedure on powerline fonts page. Can you tell me what should I do to install them properly in the future?

Thanks again!

I don’t know what you can find here. I have full config file in my dotfiles.

bar {
	font pango: Inconsolata for Powerline, FontAwesome 12
	status_command ~/.config/i3/bumblebee-status/bumblebee-status -m nic pasink weather
        battery date time -p date.format="%a, %b %d %Y" time.format="%I:%M %p"
        nic.states=^down -t solarized-powerline
	tray_output none
	colors {
		background $bg-color
		separator #757575
      ##        border             background         text
		focused_workspace  $bg-color          $bg-color          $text-color
		inactive_workspace $inactive-bg-color $inactive-bg-color $inactive-text-color
		urgent_workspace   $urgent-bg-color   $urgent-bg-color   $text-color
		}
}

update: just solved the problem. the font need to be changed to font pango:DejaVu Sans Mono Nerd Font 12. I think i might have been using different nerd font packages before and after the reinstalling, to anyone getting the same issue you should probably try this

Very possible. Thanks for considering this. BTW my distribution was arch. I believe most of the people installing i3status would have the same distro.

Yes, you are right about that. I will have to dig into what that means exactly and whether that is something distribution specific (I assume so). Maye I will end up having per-distribution guides.

On Dec 20, 2018, 20:38, at 20:38, intmainreturnzero notifications@github.com wrote:

Hey, aren’t the two packages different? Font awesome - https://www.archlinux.org/packages/community/any/ttf-font-awesome/ Awesome terminal fonts - https://www.archlinux.org/packages/community/any/awesome-terminal-fonts/

I had to install both packages. If I didn’t install awesome-terminal-fonts, it was showing weird boxes in the status bar.

– You are receiving this because you modified the open/close state. Reply to this email directly or view it on GitHub: https://github.com/tobi-wan-kenobi/bumblebee-status/issues/197#issuecomment-449112697

It is part of the README.md, in the examples section. Maybe that is too far at the end?

Maybe I should add a note in the beginning, where the supported versions of FontAwesome are mentioned?

⁣Sent from TypeApp ​

On Dec 19, 2018, 19:22, at 19:22, intmainreturnzero notifications@github.com wrote:

awesome-terminal-fonts did the trick for me too, this should be added to the docs I believe.

– You are receiving this because you modified the open/close state. Reply to this email directly or view it on GitHub: https://github.com/tobi-wan-kenobi/bumblebee-status/issues/197#issuecomment-448695448

Glad to hear that!

Well, generally, I’d recommend to first try to find a package for the distro you are using, as that is usually the best-tested installation option (i.e. powerline-fonts for Arch). As you have encountered, the “generic” install instructions tend to have strange issues, as config files, directories, etc. vary subtly from distro to distro.

Other than that, it’s down to playing around until it works 😛 (rebuilding the font cache, etc.pp.).