You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using:fluent-gtk-theme-git package from AUR built with custom args.
Args used:-t all -i arch -c light -c dark --tweaks solid -d "$pkgdir/usr/share/themes"
Extras: Using fluent-cursor-theme-git and fluent-icon-theme-git in conjunction with the theme.
Possible issue
The sound output selector panel appeares after the system detects a device being connected to the 3.5mm jack but the appearance of the panel seems to be out of place with respect to the overall solid theme. When the background is textual or has a lot of black and white elements, the visibility of the panel seems to be an issue without the contrast to make it out.
Screenshots
Expected Behaviour
The flag --tweaks solid should have ensured the installation of only the solid/non-translucent theme variant.
Not tried yet:
Manually installing the latest release and trying to reproduce the issue. (I'm willing to do that if it's needed to resolve the issue)
The text was updated successfully, but these errors were encountered:
Info
fluent-gtk-theme-git
package from AUR built with custom args.-t all -i arch -c light -c dark --tweaks solid -d "$pkgdir/usr/share/themes"
fluent-cursor-theme-git
andfluent-icon-theme-git
in conjunction with the theme.Possible issue
The sound output selector panel appeares after the system detects a device being connected to the 3.5mm jack but the appearance of the panel seems to be out of place with respect to the overall solid theme. When the background is textual or has a lot of black and white elements, the visibility of the panel seems to be an issue without the contrast to make it out.
Screenshots
Expected Behaviour
The flag
--tweaks solid
should have ensured the installation of only the solid/non-translucent theme variant.Not tried yet:
Manually installing the latest release and trying to reproduce the issue. (I'm willing to do that if it's needed to resolve the issue)
The text was updated successfully, but these errors were encountered: