You are not logged in.
Hello, I've recently installed #!++ (under debian 8, I now the last version is under debian 9). And since the begining I have had problems with icons, they look like that: image
As you can see, some of them have strange stripes, and others are just a white square.
Thanks for your help
Offline
#!++ is not Bunsenlabs
Offline
Thanks for your help!
Offline
Hello, I have had problems with icons in tint2's launcher, they look like that:
As you can see, some of them have strange stripes, and others are just a white square.
Thanks for your help
Offline
#!++ is not Bunsenlabs
But we will still support queries about #!++, or any other operating system.
@OP: I will look into this tonight, I'm on my phone atm
Offline
I just thought it was strange the OP was asking about that distro when this forums distro is bunsenlabs. Have you had no luck on the #!++ forums elgatoverde?
Ive had a similar problem in the past to this and it was due to the fact the icon paths were incorrect, but im not using stretch so maybe Hoas has a better idea.
Offline
Recently, I had some problems with icons on the tint2 panel -- like the OP, not in BunsenLabs, although I came here to dig around for tips.
Not sure from looking at the screenshot, but I think those are launcher icons to the left and task icons to the right. Feel free to correct me if I'm wrong about that. You maybe have two separate issues to pin down -- launcher icons and task icons. Might be a good idea to start by posting your tint2rc, especially the launcher_item_app lines (they might be pointing to desktop files in /usr/share/applications, I'm guessing, but maybe not).
In my case, I added Openbox in Debian 9, where I also have KDE Plasma 5 installed, and I was having problems with launcher icons as well as with task icons for KDE apps. I fixed those two issues separately, as things turned out.
Offline
Right, I'm back in a real OS now so I can actually see the picture:
Those look like the artefacts BunsenLabs Hydrogen/Deuterium suffers with when used with Intel graphics cards.
What is your hardware?
lspci -knn | grep -iA2 'vga\|3d'
Debian stretch employs SNA by default so that particular problem shouldn't happen — is xserver-xorg-video-intel installed?
apt-cache policy xserver-xorg-video-intel
If it is, try removing it and falling back to the modesetting driver instead (if you have an Intel card).
Finally, have you tried restarting the compositor?
pkill -usr1 compton
I'm not sure how #++ starts everything up so can we also please see the content of ~/.config/openbox/autostart
Offline
Hopefully the OP got this sorted, would be good if he/she came back and let us know.
Offline