-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tint2rc systray background too dark #32
Comments
Fine by me. |
Which are these "dark icons"? The default light grey faenza are visible. btw I see no difference between faenza-bunsen and faenza-dark-bunsen in most situations. |
I was going to bring this up, it doesn't seem like the bunsen icons were packaged correctly. For example, installing faenza-icon-theme from jessie instantly solves the invisible pnmixer icon (probably volumeicon too). I'll see what I can find and post back. |
Please. Although, I saw the same lack of difference when on #! too. At that time I seem to remember being told the "dark" meant that the icons were meant for use on dark backgrounds, rather than that they were dark themselves. |
https://github.com/2ion/bunsen-org/issues/107#issue-112065606
Maybe Philip's error that we've carried over, then.
This is correct, "Faenza-Bunsen-Dark" should be the default icon theme for use with our tint2conf. |
I remember having to use "dark" at some point to make a volume icon visible. |
I think this issue might be fixed by the icon repackaging @hhhorb suggested elsewhere. If we provide only the folder icons and inherit the rest from Faenza some things will become simpler.
This is how BL is configured OOTB. ("Faenza-Dark-Bunsen" that is) |
Icon theme discussion here: BunsenLabs/bunsen-faenza-icon-theme#2 |
The dark icons for power and network are invisible against the default dark tint2 background.
Suggest changing to
systray_background_id = 2
, which is the same as that used bytask_active_background_id
The text was updated successfully, but these errors were encountered: