I have the same behaviour than comment #19. For some weird reason unity plugin is being disabled from config in some updates (for me it happens from libunity6 to libunity7 in Ubuntu Saucy Salamander).
I can enable again the unity panels installing compizconfig-settings-manager (ccsm), but I try to figure out what exact files changes ccsm for maybe use the right commands and avoid the GUI for do this each time. So I fired with:
strace -eopen cssm
Then I see that the config files being touched after enable Unity plugin are:
I have the same behaviour than comment #19. For some weird reason unity plugin is being disabled from config in some updates (for me it happens from libunity6 to libunity7 in Ubuntu Saucy Salamander).
I can enable again the unity panels installing compizconfig- settings- manager (ccsm), but I try to figure out what exact files changes ccsm for maybe use the right commands and avoid the GUI for do this each time. So I fired with:
strace -eopen cssm
Then I see that the config files being touched after enable Unity plugin are:
/run/user/ 1000/dconf/ user .config/ dconf/user .cache/ compizconfig- 1/unityshell. pb compiz/ unityshell. xml
/home/username/
/home/username/
/usr/share/
So likely one of that files is being overwritten in package updating. Also it makes sense the dconf trick because it maybes reset one of that files.