Polybar Goes Black Out of Nowhere

FOSSilizedDaemon commented 3 years ago

Checklist

[X ] I have read the appropriate section in the contributing guidelines
[ X] I believe this issue is a problem with polybar itself and not a misconfiguration on my part.
[X ] I have searched for other open and closed issues that may have already reported this problem.
[X ] I have checked the known issues page for this problem.

Describe the bug

I just started using polybar, have been using it for about three or four days, and have noticed a serious bug. I am unsure if this has been an issue in the past as I just started using polybar, but essentially it just goes black out of nowhere without any warning or error or log. I have tried using an example configuration, one that has just the title of the current window showing, and ofcourse my own but I experience this issue with all of them. I am using polybar with a third party module, dwm module for polybar. I have tried using polybar on a virtual machine, running Ubuntu, and a laptop, running Linux Mint.

Expected behavior:

I expected that polybar would print my configuration and update at the proper intervals (NOTE: I have tested the official example configuration given by this upstream as well as the example configuration in the dwm module downstream).

Actual behavior:

Regardless of what configuration I use I keep having an issue where polybar randomly goes black and when I move my cursor over it it shows my content and then goes black again when my cursor is no longer over it. I am unsure why this is happening as no errors are given.

Was it working before?

Did you also experience this bug in an earlier version of polybar (yes/no/don't know)?
If no, what was the last version where this worked correctly? Don't know to either.

To Reproduce

Any minimal configuration that prints any text should reproduce this issue.

Polybar Log

notice: Parsing config file: /home/user/.config/polybar/config
notice: pulseaudio: using default sink alsa_output.pci-0000_00_05.0.analog-stereo
notice: Loaded fot "monospace:size=10" (name=DejaVu Sans Mono, offset=2, file=/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf)
notice: Loaded font "FiraCode Nerd Font Mono:size=10" (name=FiraCode Nerd Font Mono, offset=2, file=/usr/share/fonts/FiraCode-NerdFont/Fira Code Regular Nerd Font Complete Mono.otf)

Screenshots

Environment:

WM: dwm
Distro: Ubuntu, Linux Mint
Output of polybar -vvv:

polybar 3.5.2-100-g0c3e139

Features: +alsa +curl +dwm +i3 +mpd +network(wireless-tools) +pulseaudio +xkeyboard

X extensions: +randr (+monitors) +composite +xkb +xrm -xcursor

Build type: Release
Compiler: /usr/bin/g++
Compiler flags: -Wall -Wextra -Wpedantic -03 -DNDEBUG
Linker flags:

Additional context

I apologize if I am doing something wrong on my end, I am super new to polybar.

patrick96 commented 2 years ago

Hey, sorry for the delay.

I'm not seeing something immediately wrong with your setup. But help me narrow down the issue:

Since you are using a polybar fork, could you also try using a proper polybar relase and see if this occurs as well?
When the bar goes black or shows its content again, is this an immediate change or more of a fading?
Are you using a compositor like picom or compton?
Try running polybar with trace logging (-l trace) and reproduce the bug. The log should now show a lot of information and hopefully something useful about what polybar is doing and why.

FOSSilizedDaemon commented 2 years ago

Hey, sorry for the delay.

I'm not seeing something immediately wrong with your setup. But help me narrow down the issue:

Since you are using a polybar fork, could you also try using a proper polybar relase and see if this occurs as well?

When the bar goes black or shows its content again, is this an immediate change or more of a fading?

Are you using a compositor like picom or compton?

Try running polybar with trace logging (-l trace) and reproduce the bug. The log should now show a lot of information and hopefully something useful about what polybar is doing and why.

Oh, I don't recall the setting but I fixed it. It turned out I had polybar set to turn black when not active ;-;

patrick96 commented 2 years ago

Which setting? dim-value?

polybar / polybar