Desktop background detection without compositor does not work if no background image is set
tint2 seems to somehow inherit the background of a previous screen. I did a few tests and noticed that it only happens when no compositor is running. Having a compositor running didn't produce the "burned in" background. What also gets rid of the "burned in" background is setting a desktop wallpaper.
Additional info: LightDM is the display manager from which tint2 gets the background and tint2 is running in an Openbox session.
I'm not sure if this is a tint2 issue, but I thought I should report it, just in case. Even then it's not really a big annoyance, since it apparently only happens when:
- no compositor is running
- no background wallpaper is set
Display manager before: http://s18.postimg.org/hmlrlcju1/image.png
Openbox desktop with tint2: http://s18.postimg.org/uo7gb7889/image.png