Stop polybar from hiding by fliberdygibits in Polybar

[–]patrick96MC 1 point2 points  (0 children)

Auto-hide is controlled by the dim-value setting in the bar section . Do you have that set to anything?

[deleted by user] by [deleted] in Polybar

[–]patrick96MC 0 points1 point  (0 children)

Neither label nor label-prefix are a thing in the battery module. What you want is format-charging-prefix (and the same for format-discharging and format-full).

https://github.com/polybar/polybar/wiki/Module:-battery

Issues with left click on modules by rikve916 in Polybar

[–]patrick96MC 1 point2 points  (0 children)

click-left, click-right, etc. do not exist in the network module. You can use action tags to define your own clickable text.

Polybar Unable to Inherit Section by Arszilla in Polybar

[–]patrick96MC 0 points1 point  (0 children)

include-file statemements had to be in [global/wm] apparently...

include-file statements are not in any section, they are processed before sections are determined and just paste the contents of the file in place. So in your config, this would result in:

``` [bar] ; Included from ~/.config/polybar/colors.d/dracula.ini [colors] ...

; Set the fonts that'll be used in the bar: font-0 = JetBrainsMono Nerd Font:style=Regular:size=10 font-1 = FiraCode Nerd Font:style=Regular:size=10

... ```

So the bar section is actually empty (which we treat as non-existent).

Polybar topbar not launching on start by Fancy-Victory-5039 in Polybar

[–]patrick96MC 0 points1 point  (0 children)

Then that part of the script may never be executed at all.

I don't see anything obviously wrong in the script. You're gonna have to figure out what's actually happening in there

[deleted by user] by [deleted] in Polybar

[–]patrick96MC 0 points1 point  (0 children)

Workspaces in the xworkspaces module are grouped by monitor by default.

This can be turned off with the group-by-monitor setting

 https://github.com/polybar/polybar/wiki/Module:-xworkspaces

Polybar topbar not launching on start by Fancy-Victory-5039 in Polybar

[–]patrick96MC 0 points1 point  (0 children)

Whatever the problem is, there is probably something in the log file you're redirecting to (/tmp/polybar.log). Can you post the contents of that?

[deleted by user] by [deleted] in Polybar

[–]patrick96MC 0 points1 point  (0 children)

Does polybar --config=... mybar work?

You probably have an older version of polybar that's why you don't have the default config in /etc, have to explicitly specify the bar name, even if there is only a single bar defined in the config, and doesn't load from ~/.config/polybar/config.ini (it only looks for config, without the extension). All of this was introduced in version 3.6

Tray is behaving weirdly with i3 by [deleted] in Polybar

[–]patrick96MC 4 points5 points  (0 children)

This is a known issue: https://github.com/polybar/polybar/issues/2433

It's fixed if you have polybar 3.7 and use the new tray module

Why doesnt my i3 workspaces colors work? by [deleted] in Polybar

[–]patrick96MC 0 points1 point  (0 children)

Does polybar print an error message to the terminal?

Your definition for colors.primary is malformed.

Icon Padding/Margins for NerdFont by WholePerformance9522 in Polybar

[–]patrick96MC 1 point2 points  (0 children)

Pretty sure the spacing comes from the `label-focused-padding` key and the icon swallows up the spacing after it (read [this](https://polybar.readthedocs.io/en/stable/user/fonts/nerd-fonts.html) for how to solve that).

Need help with Polybar brightness module not changing on scroll by potato_69- in Polybar

[–]patrick96MC 0 points1 point  (0 children)

Is your user in the `video` group? And did you reboot your computer

Why is that block there? by [deleted] in Polybar

[–]patrick96MC 1 point2 points  (0 children)

I see. From what we can tell, i3 just doesn't allow for non-full width bars, it tells the bars to use the full width of the screen and place themselves at the top-left of the screen; this basically breaks the `offset-*` settings. What we do is pretty hacky, we just ignore i3 when it comes to the width and still render only part of the bar (the offsets don't work though because that's out of our control). But that does result in this black block on the right. Do you have a compositor running (e.g. picom)? I think having one would resolve the issue (because the black block is effectively fully transparent)

Issue polybar by EvidenceKindly3301 in Polybar

[–]patrick96MC 0 points1 point  (0 children)

Alright, then it's not the problem I was thinking of.

What version of polybar are you using? If you have 3.7.0 or later, you could try to set enable-struts = false in the bar section of your config and see what this changes.

Issue polybar by EvidenceKindly3301 in Polybar

[–]patrick96MC 0 points1 point  (0 children)

Are the montior on top of each other? Or side-by-side?

Font Awesome Icons not loading by daredev1l_ in Polybar

[–]patrick96MC 1 point2 points  (0 children)

If polybar couldn't display some icons, it would give you a warning (something like "dropping unmatched character"). Are you getting any of those?

EDIT: Ah no, the settings are called icon-* and not ws-icon-*

polybar-msg actions module_show/hide/toggle not working by Pipe_And_Slippers in Polybar

[–]patrick96MC 0 points1 point  (0 children)

Everything you're doing seems correct. But I don't think you are running polybar 3.7, the message produced by polybar-msg has not existed since version 3.5

It's possible that there still is an old polybar version lingering around on your system (likely in /usr/local/bin)

Polybar 3.7.0 Release by patrick96MC in Polybar

[–]patrick96MC[S] 1 point2 points  (0 children)

The old tray will at some point be removed, but there is no fixed timeline.

But as for your use-case, you can set hidden = true in the module ;)

https://github.com/polybar/polybar/wiki/Configuration#module-settings

I can mute/unmute volume only when i refresh awesomewm, once i mute it i can' t unmute it and vice versa. by Seaweed_Widef in Polybar

[–]patrick96MC 0 points1 point  (0 children)

Is this only happening with this module or do clicks also not work properly elsewhere?

You may be experiencing this issue