You are not logged in.
Pages: 1
because it is not working properly without it
can you elaborate on that?
In general it is best to put the compositor at the end of your startup commands, i.e. after background, panel etc.
No need to use "make install".
Have a look at my first post. You only need to copy the newly compiled "compton" binary file within your "compton-master" directory to a system directory. For example copy to /usr/bin
sudo cp ./compton /usr/binWARNING: This will overwrite the current compton (if installed). Be aware that it will be overwritten when compton is updated as well. It might also break the cb-compositing script and autostart line, so you will need to adjust your autostart line and Openbox menu accordingly! It would be safter to uninstall the current compton first, then just using the above mentioned copy command and adjusting the autostart line.
after "make" in the compton-master directory I've got this ...
~/downloads/compton-master$ make make: `compton' is up to date.So maybe last night after the upgrade of the system compton was upgraded too?
make is referring to the compiled binary within your "compton-master" directory. It is not related to your installed compton.
If you build compton with make and it has been compiled successfully, any further "make" command within the build directory will output this line until the source files change.
When you navigate to your "compton-master" directory, you may test the compiled binary via:
./compton --opengl --vsync opengl-swc --paint-on-overlayThe "./" prefix executes the compton binary within the current directory instead of the system one.
As stated in my post, use the *-dev packages, i.e. "libx11-dev", "libxcomposite-dev" and so on.
I'll try to recollect which ones are needed:
libx11-dev libxcomposite-dev libxdamage-dev libxfixes-dev libxext-dev libxrender-dev libxrandr-dev mesa-common-dev libgl1-mesa-dev libconfig-dev libdrm-dev libpcre3-dev libdbus-1-devThey should automatically pull the remaining dependencies. Report back, if there's still something missing.
You will always get tearing without compositing (at least on desktop)!
You can achieve a tearing-free (desktop + video) experience through compositing only.
Unfortunately, the current compton version shipped with Waldorf isn't able to eliminate tearing since it is using an XRender backend but the newest git version includes an OpenGL backend that can solve this problem:
Download the git version of compton: https://github.com/chjj/compton
Compile it. The build dependencies are listed on the github page, just install their *-dev packages. If you're stuck, just ask.
Do not use the shipped /etc/xdg/compton.conf! You will get lags with this config. Create a new (minimal) one in your home folder instead:
# ~/.config/compton.conf
shadow = true;
no-dnd-shadow = true;
shadow-radius = 10;
shadow-offset-x = -16;
shadow-offset-y = -16;
shadow-opacity = 0.6;(adjust it to your liking)
Use the following command to execute compton:
compton --opengl --vsync opengl-swc --paint-on-overlayNote: First, you need to put the compiled binary where the system can find it (i.e. /usr/bin) but pay attention to the originally installed compton. You may remove it beforehand if you don't care about the dependencies. Otherwise you could rename the new one to sth. like "compton-git" and change the command accordingly.
Adjust your autostart compositor line and Openbox menu entries where necessary.
For best video experience, I recommend either VLC with XVideo output or mplayer2 with XV output.
There should be no need to adjust any nvidia settings or fiddle with xorg.conf. Just use a clean xorg.conf created by nvidia-xconfig.
Thanks all of you for sharing your thoughts!
I almost forgot about the MATE applications. Thanks for pointing that out! It is the solution I was looking for.
I'm now using MATE's atril and engrampa instead of evince and file-roller.
Additionally I already recompiled GTK2 audacious and will do the same for transmission-gtk.
I'm aware that sticking to GTK2 will not be possible forever.
In the last years I've used almost all major distros and all major DEs & WMs. Ever since GTK3 was introduced, I only had problems with it. Themes wouldn't work correctly when switching versions (3.0 -> 3.2 -> 3.4 -> ...), controls (buttons, sliders etc.) frequently rendered incorrectly and even combined GTK2/GTK3 themes didn't accomplish a 100% match between the two versions because the GTK3 coding is so much different and complex (according to the creators). Not to mention that many of the new GTK3 apps feel a bit crippled in terms of menus and controls.
To be honest, I'm fed up with GTK3 by now and that's why I try to avoid it as much as I can.
I hope by using Waldorf together with the MATE applications I can stay with GTK2 a while longer 
Again, thanks for your replies!
Dear #!'ers,
I'm new to CrunchBang (not to Linux in general, though). Please excuse me if I post this in the wrong section.
I just recently installed Waldorf and instantly fell in love with the GTK theme called "Nox". Unfortunately this theme is GTK2 only, meaning GTK3 applications look horribly. I know of methods to merge a GTK3 part of another theme with it but I don't want that. What I want to achieve is to limit my system to GTK2 applications only. Most of the included applications are still GTK2 but some aren't, including:
audacious
evince
file-roller
transmission-gtk
I'm very satisfied with those applications but would like to get their GTK2 interface back. I know that audacious has a compile flag to turn off GTK3 but I don't know about the other ones.
Are the Statler packages of those still GTK2? If so, can I install them on Waldorf?
If there's no other choice, are there any good GTK2 alternatives you can recommend?
Pages: 1
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.