jwoodward-linux ~ # emerge --unmerge pygobject
* This action can remove important packages! In order to be safer, use
* `emerge -pv --depclean <atom>` to check for reverse dependencies before
* removing packages.

dev-python/pygobject
selected: 3.2.2
protected: none
omitted: none

All selected packages: dev-python/pygobject-3.2.2

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

Note: Emerging compiz-fusion fails on some systems. It appears to be during the compile/link phase when using ~amd64 and desktop-effects overlay (it may occur elsewhere). Try editing your make.conf file as shown below and emerge compiz-fusion again.
File: /etc/make.conf
MAKEOPTS="-j1"

@Aquous
Are you able to link the breakage with some modification or action you have done around the same time as the breakage ?
A system update or depclean for example...

When you mention no applications showing in the launcher, do you mean the applications in the applications lens or applications shown in the sidebar ?
Not sure if it helps, but I can tell you that the applications/icons in the sidebar will break and disappear if >=media-libs/mesa-8.1 is installed.
Finally, if it's your user config that is broken you can reset that with the following commands:

The issue with my monitor's vrefresh rate cropped up after mucking around in ccsm, and it was fixed when I removed all compiz folders. The window button icons displacement issue cropped up with the update to x11-themes/light-themes-0.11.1, so that's probably not your/Unity's fault. However, the applications disappearing from the Dash menu is something which I can't link to any change. By Dash menu I mean the lens, btw. The apps which I manually pinned to the sidebar are still there, but the lens is completely empty - when I click the bookshelf icon, I get a completely empty screen, and when I start typing an application name such as gedit, it just keeps searching with no results ever coming up.

@ahgblopes
Still no progress on that window position bug, but I've a feeling it may be tied to the way we start the compiz plugins.
The only default compiz plugin set at build time should be 'ccp', then rely on the 'ccp' plugin and compiz's gconf backend to load the necessary compiz plugins as set in the gconf registry (or dconf now for Quantal).

@Aquous
Glad you got it sorted in the end.
I reckon the blank entries in the lens might have had a lot to do with me making those commits to support python2 and python3 at the same time.

@ahgblopes
Still no progress on that window position bug, but I've a feeling it may be tied to the way we start the compiz plugins.
The only default compiz plugin set at build time should be 'ccp', then rely on the 'ccp' plugin and compiz's gconf backend to load the necessary compiz plugins as set in the gconf registry (or dconf now for Quantal).

You are right... They "put" plugin is completely effect-less (if i change something inside it, i cannot see any result)

Unity 5.16 is now avaliable! good, but... now you have to create an unity-meta-5.16 ebuild!!!
The version of unity-meta in portage is 5.14. When i try to install (upgrade) it, portage doesn't find "unity-5.14" nor "unity-5.12", and unity-meta-5.14 depens on <=unity-5.14 !!! I guess that it is very easy to fix, i could edit the ebuild file , but i will wait for shiznix do it for us...

And if i try to install unity, instead of unity-meta, i have only two choices: unity-6.6.0 (too much unstable for me), and unity-5.16

unity-5.16 fails to compile, because it doesn't find the libgeis. But i have geis installed, maybe unity-5.16 is wanting a more recent version, but if i try to install it, i have to install a bunch of unstable packages (grail, nux, etc, those also pulled by 6.6.0).

I think we have to put back unity-5.14 (or 5.12??) package in the overlay, or, so, fix the problem with unity-5.16 and make an unity-meta-5.16 ebuild.

Newest unity-6 is in active development for the Quantal release but is still a bit unstable for many (including me), so I've kept it missing keyword masked and been hacking on it when I get a spare moment in readiness for when the glitches improve enough that the mask can be removed.
As the Quantal branch of packages move forward, some of it gets backported into the 'precise-updates' branch of packages which is what we mostly use for unity-5.

I mentioned earlier that Quantal will be dropping unity2d in favour of using compiz opengl in software render mode instead.
Well they've not only done this, but we're now being hit with it in the 'precise-updates' branch as nux-2.14.1 now requires libgeis and unity2d requires libutouch-geis.
Utouch-geis is the older version of the GEIS implementation, libgeis is the newer and the two mutually exclude each other.

So to keep up to date with the 'precise-updates' branch we too will need to drop unity2d.

Which brings me to the issue of which URL we are getting the source tarballs from.
I've been using packages.ubuntu.com but this has the downside of the tarball disappearing as soon as a new version is released.
What I should have done was use launchpad.net instead to download the tarballs so that any particular version ebuild does not break due to a missing tarball whenever a new tarball is released upstream.

I'll chip away at migrating to launchpad.net and in the meantime you should know that unity2d is soon to disappear.

Good: I upgraded to unity-meta-6.6 (i have to unmerge unity2d for it), and now unity starts!!

Bad: That old bug from 5.12 persists. When i open nautilus, gedit, musescore, firefox, etc... they start maximized. When i hit the unmazximize button, the window gets undecoreted and if i try to press the maximize button again it doesn't work...

@Aquous
I was hit with a similar bug to your window titlebar button problem while messing with getting compizconfig profiling and gconf/dconf backends working.
Compiz needs to compile against x11-libs/metacity-99.2.34.1 as it uses it for the window titlebar theming.
Once this was done, the titlebar buttons were fixed.

I've added the overlay metacity-99.2.34.1 ebuild as a dep. for compiz now, so it should be fixed for you by syncing up and doing:

Code:

emerge -1 compiz

Thanks for reporting

@ahgblopes
Great news you got the new unity-6 to actually start instead of segfault this time.
Unity-5 should still be more stable for you.

Not sure why ccsm has segfaulted but the profile and backend are now incorrect since the addition of the compizconfig profiling and gconf/dconf backends.
If you're using unity-6 the backend should be 'gsettings', and the profile should be 'unity'.
If you're using unity-5 the backend should be 'gconf', and the profile should be 'unity'.

These settings are installed by doing as root:

Code:

emerge --config =compiz-0.9.8.2

(Above example for Unity-6, the actual commandline to be used is shown as a post install message for the relevant compiz version emerged).

The compizconfig profile is set on login to Xorg so you may need to log out and back in again.