From 2dc8be7d0d65f98dcec13a73291e6919322283a2 Mon Sep 17 00:00:00 2001 From: Patrick Ziegler Date: Wed, 22 Dec 2021 09:32:30 +0100 Subject: [PATCH] Updated Known Issues (markdown) --- Known-Issues.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/Known-Issues.md b/Known-Issues.md index 2fbc2c4..bf05661 100644 --- a/Known-Issues.md +++ b/Known-Issues.md @@ -54,14 +54,6 @@ program may just reuse already compiled binaries. You need to make sure that polybar is *recompiled*. How to do that depends on the program, but most offer a way to force a rebuild or a way to clear the cache for certain packages. -**Example:** Try to remove polybar with your AUR helper, and perhaps remove the orphans also. -Go to /var/cache to find and remove leftover files, they could be: -``` -/var/cache/pacman/pkg/polybar-...pkg.tar.zst -/var/cache/aur-helper/pkgbuilds/polybar.pb -``` -Re-install polybar with AUR helper. - ## Setting Module Backgrounds when using Gradients **Problem:** When you use a gradient as your polybar background, explicitly setting any module's background color to whatever you have set as `background-0`, either through the `-background` setting or the `%{B}` formatting tag, will not change the background color at all.