> @Alberts, Dmitry: > > No compositor means - no desktop window or it will be black - you will > never see background. > > My plan is to fix this in Xenial+1. Less patches will mean less work for > me, too :P > > That's a good example, does that mean that in Ubuntu 16.10 if one > doesn't use compositing he won't be seeing the desktop icons and > background? >
No, it depends if ubuntu will still revert that nautilus change... Upstream nautilus does not draw background since 3.8: https://git.gnome.org/browse/nautilus/tree/NEWS#n310 Desktop icons will be available, but without compositor background under icons will be black. @Alberts, which distro are you using or which one is closest with > upstream flashback? Debian? > I use Ubuntu (development version), but I am building full GNOME + GNOME-Flashback with JHBuild. I don't use Debian, but it should be good - it is not modified there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1565640 Title: Set compositing-manager=false by default Status in metacity package in Ubuntu: Won't Fix Bug description: In Ubuntu 12.04 and 14.04, metacity's compositing-manager was false by default. In 16.04, it's been set to true. I tried to pinpoint the advantages vs the disadvantages of that, and currently I've only seen disadvantages. I was testing with: gsettings set org.gnome.metacity compositing-manager false (or metacity --no-composite) versus: gsettings set org.gnome.metacity compositing-manager true (or metacity --composite) Speed: the speed for window drawing and moving around is 3-5 times slower when compositing is enabled. This is rather visible locally on old computers, but it becomes a real problem when Xorg is used over the network, like for example in LTSP thin clients. There, dragging around a window draws it in slow motion a whole lot behind the mouse, like a trail, while with compositing disabled, everything is lightning fast. RAM: xrestop shows that with a couple of windows open, metacity now needs 10 MB more RAM. This value increases with the number of open windows. Vsync: in most cases vsync was broken with or without compositing (while with compiz it's working much better). I tried with youtube videos, with VLC etc. The only difference I saw is that with some SDL games like teeworlds, vsync was working with compositing disabled, and was broken with compositing enabled. So my personal results is that metacity's compositing-manager=true doesn't have any advantage currently, and that it makes old client and LTSP client performance a whole lot worse. And unfortunately those are exactly the cases where we prefer gnome-session-flashback instead of e.g. Unity. Therefore I'd like to ask you to consider disabling it by default like it was in the past. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1565640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
