I've just installed #! on a new laptop and everything is fine except for one slight annoyance:
When it boots up, the icons in the tint2 menu at the top are 'smudgy'. If I restart compositing then this fixes the problem straight away.
Does anybody know why this might be happening (and how to stop it) or how I could automate the 'restart compositing' on boot up?
you could probably try increasing that "sleep 2s" in openbox autostart;
## Group start: ## 1. nitrogen - restores wallpaper ## 2. compositor - start ## 3. sleep - give compositor time to start ## 4. tint2 panel (\ nitrogen --restore && \ cb-compositor --start && \ sleep 2s && \ tint2 \ ) &
Last edited by brontosaurusrex (2013-10-31 12:42:01)
I added this line:
(sleep 3s && cb-compositor --restart) &
There's a very slight delay, but that's fine. Would be nice to now why it needs doing, but I can live with it!
Same thing for me. My icons had a white background (instead of transparent) until I restart the compositor. DAZ's fix worked perfectly!
This issue is quite simple. If Tint2 is started when the compositor already is running, you can get this issue. At least with Intel hdgraphics. Your workaround, or just simply delaying the initial compositor start so that it starts after Tint2, will be fine.
But just to test. If you try to restart tint2 (settings/tint2/Restart Tint2) then the problem should reappear. You can choose to live with this, but you can solve it permanently so that you can use the default Crunchbang autostart file. Solve it like this :
As root, create a file called "20-intel.conf" in "/etc/X11/xorg.conf.d" . If the xorg.conf.d folder doesn't exist, then create it.
The content in the file should be like this:
Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "sna" EndSection
Save the file and reboot. Should work with the default autostart. no need to delay or restart anything.
^ If you're going to do this, I would advise also compiling the latest compton version from source as the SNA driver tears badly.
Using Debian ~ Debian Reference ~ CrunchBang FAQ
Advice For New Users On Not Breaking Their Debian System
Linux From Scratch ID 25389