Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#76405 - [waybar] does not respect some css settings

Attached to Project: Community Packages
Opened by Antonio Corbi bellot (acorbi) - Thursday, 03 November 2022, 16:01 GMT
Last edited by Brett Cornwall (ainola) - Friday, 04 November 2022, 00:08 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Brett Cornwall (ainola)
Maxim Baz (maximbaz)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I think since last waybar update (waybar-0.9.15-1-x86_64 here) some meters (i.e. memory) that have foreground color set to '#ffffff' don't show the text in white color but in some kind of grey.

Additional info:

* package version(s)
waybar-0.9.15-1-x86_64

* config and/or log files etc.

Attached are a small screenshot and my style.css although I've observed the same behaviour with the default style.css provided with the pkg in /etc/xdg/waybar.

* link to upstream bug report, if any

Steps to reproduce:

Start waybar providing my style.css or the one from /etc/xdg/waybar/style.css
   style.css (6.7 KiB)
   20221103165826_1.png (3.4 KiB)
This task depends upon

Closed by  Brett Cornwall (ainola)
Friday, 04 November 2022, 00:08 GMT
Reason for closing:  Upstream
Additional comments about closing:  Broken behavior is upstream and will be resolved internally on the next release.
Comment by Toolybird (Toolybird) - Thursday, 03 November 2022, 22:18 GMT
This is an upstream problem e.g [1]. Related  FS#76386 .

[1] https://github.com/Alexays/Waybar/issues/1764
Comment by Brett Cornwall (ainola) - Friday, 04 November 2022, 00:08 GMT
Hi, acorbi! Thanks for opening this ticket.

Since this is in fact a broken upstream release, this is best kept to the github issue linked above.

Loading...