no way to permanently enable emerald

[Adam Petaccia]

The only way to make compiz-decorator use emerald is to change USE_EMERALD to yes in compiz-decorator. This change gets wiped out after every update to compiz.

[Travis Watkins (amaranth)]

No, it was decided that enabling emerald automatically was a bad idea. And now that compiz starts the decorator itself you can choose which one to use on a per-user basis in the compiz settings.

[Adam Petaccia (mighmos)]

Funny thing is, I have. This update has broken that. Unless I've set it in the wrong place, in which case I'll file another bug about too many places to set settings.

[Adam Petaccia (mighmos)]

Sorry, I should have stated: In CCSM --> Window Decoration Plugin -->Command: /usr/bin/emerald

[Travis Watkins (amaranth)]

Because you have another decorator running already so compiz won't start one for you. If you log out it'll start working.

[Adam Petaccia (mighmos)]

PLEASE stop marking this WONTFIX. I have. I've rebooted even. I've told compiz to use emerald, and it DOESN'T. This is a BUG. I'm sorry for getting rude, but this is frustrating to have a regression that keeps getting marked WONTFIX.

If another decorator is already running, then that too is a problem, because I've already specified the one that should be running, and then it gets ignored anyway.

[Tomasz Sterna (smoku)]

I have the same problem with current Hardy.
Emerald is not started. I have it installed and configured in CCSM.
After manual "emerald --replace" it starts and works. But after relogin the default decorator is started again.

[gokee2 (adsarebad)]

I just updated my hardy install now I have this problem as well. I am using kubuntu and any window thats not in focus loses its decorations if I use the kde decorations so I have been having compiz start emerald for me (at least it has been... I can`t remember telling it to but I must have at some point). The command I have in compiz is "/usr/bin/compiz-decorator". Does compiz have some decorator built in or is that just some fancy way to start one you define somewhere else? Should I have "/usr/bin/emerald" there like Adam Petaccia to use emerald or is there a "better" way?

[Steven (stebalien)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Adding USE_EMERALD="yes" to ~/.config/compiz/compiz-manager fixed this for me.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH+Sho2FSfVyUro4URAmLfAJ0U+bnwTI99xQzhHuzvtj4Iz7Dh7ACfe1ps
XqKsGZhnYV8wNaqamAFTpBo=
=vSbv
-----END PGP SIGNATURE-----

[sam fielder (srf10130)]

still have this bug in hardy rc1

when upgrading the USE_EMERALD flag gets overwritten to no.

another suggestion would be to allow the flag to actually be set in compiz manager.

currently there is only a -- "if" there isn't another decorator running -- setting, but compiz-decorator is set to run by default when the USE_EMERALD flag gets set to "no".

[Adam Petaccia (mighmos)]

This bug is still present in Intrepid (updated). I'm not sure I understand the point of the Window Decoration plugin if it does the same thing no matter what's entered into it.

[andypiper (andypiperuk)]

I've tried setting USE_EMERALD in both ~/.config/compiz/compiz-manager and /etc/xdg/compiz/compiz-manager as well as in Window Decoration settings and by setting fusion-icon to specify it and to run on GNOME startup, and still compiz doesn't default to Emerald - I have to restart the WM in the fusion-icon to get Emerald enabled. This is on Karmic.

[Kemel Zaidan aka Legendario (kemelzaidan)]

I have the same problem on karmic. Have set USE_EMERALD='yes' and DECORATOR='emerald' on /usr/bin/compiz-decorator, /usr/bin/compiz-manager and /usr/bin/compiz but compiz ignore that and always starts gtk as default decorator. It's a confirmed bug, for sure.

Only after reloading compiz with fusion-icon, emerald is started. This is what is funny about it. There must be something wrong with compiz init scripts.

[N1ck 7h0m4d4k15 (nicktux)]

Sorry folks, but as part of the bug clean up ahead of 16.04 LTS I'm marking this as invalid because it affects an Ubuntu release which is now unsupported. If you can still recreate this bug in a supported release please do open a new bug and we can triage it for consideration in the 16.04 LTS development cycle.