!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

x11-libs/gtk+:3

(x11-libs/gtk+-99.3.4.2::unity-gentoo, ebuild scheduled for merge) pulled in by
>=x11-libs/gtk+-99.3.4.2:3 required by (gnome-base/gnome-settings-daemon-99.3.4.2-r1::unity-gentoo, ebuild scheduled for merge)
(and 13 more with the same problem)

(x11-libs/gtk+-3.4.3-r1::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

dev-libs/glib:2

(dev-libs/glib-99.2.32.3::unity-gentoo, ebuild scheduled for merge) pulled in by
>=dev-libs/glib-99.2.32.3 required by (unity-base/dconf-qt-0.0.0.110722::unity-gentoo, ebuild scheduled for merge)
(and 4 more with the same problem)

(dev-libs/glib-2.32.1::sabayon-distro, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

media-libs/clutter:1.0

(media-libs/clutter-1.10.4::gentoo, installed) pulled in by
>=media-libs/clutter-1.10.0:1.0[introspection] required by (gnome-extra/sushi-0.4.1::gentoo, installed)
(and 4 more with the same problem)

(media-libs/clutter-1.8.4::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

media-libs/cogl:1.0

(media-libs/cogl-1.8.2::gentoo, ebuild scheduled for merge) pulled in by
<=media-libs/cogl-1.9.2:1.0 required by (media-libs/clutter-1.8.4::gentoo, ebuild scheduled for merge)

(media-libs/cogl-1.10.2::gentoo, installed) pulled in by
>=media-libs/cogl-1.9.6:1.0[introspection?,pango] required by (media-libs/clutter-1.10.4::gentoo, installed)
(and 1 more with the same problem)

media-libs/clutter-gtk:1.0

(media-libs/clutter-gtk-1.2.0::gentoo, installed) pulled in by
>=media-libs/clutter-gtk-1.1.2:1.0 required by (net-im/empathy-3.4.2.1::gentoo, installed)

(media-libs/clutter-gtk-1.0.4::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

gnome-base/gnome-keyring:0

(gnome-base/gnome-keyring-3.4.1::gentoo, installed) pulled in by
>=gnome-base/gnome-keyring-3.3.90 required by (gnome-base/gnome-shell-3.4.1::sabayon-distro, installed)
(and 4 more with the same problem)

(gnome-base/gnome-keyring-2.32.1-r1::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

gnome-base/libgnome-keyring:0

(gnome-base/libgnome-keyring-3.4.1::gentoo, installed) pulled in by
>=gnome-base/libgnome-keyring-3.2 required by (gnome-base/gnome-core-apps-3.2.1::gentoo, installed)
(and 1 more with the same problem)

(gnome-base/libgnome-keyring-2.32.0::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.

I commented metacity, gtk and nautilus because these packages we will get from unity-gentoo repo...

You should not add anything inside package.unmask. Here is my package.unmask, for example:

=gnome-base/gdm-3.4.1::gentoo
dev-java/oracle-jdk-bin

(only these 2 lines)

the other file inside portage.keywords folder should be a synlink to /var/lib/layman/unity-gentoo/PACKAGES, as shiznix told us..

with these two files (unity-gentoo (symlink to unity-gentoo/PACKAGES) and gnome3) we will be able to install a good set of unity and gnome3 packages without any mask problem.

In my case (but this might change according to your use flags) i had to put some extra packages (gnome3 deps) into package.accept_keywords (but only gdm into package.unmask).

So, do it (put unity packages and gnome3 packages inside portage.keywords file) and remove any gnome or unity lines in your package.accept_keywords file (or package.keywords), then told us what you got.

And would be nice if you post here or in pastebin all files inside your /etc/portage folder, so we would help you better.

Is because the "=" is mandatory if we specific a package version (3.4.1), so you need to change gnome-extra/gnome-user-docs-3.4.1 to =gnome-extra/gnome-user-docs-3.4.1, but as i told you, you should not put anything inside package.unmask, it is generally no good and unnecessary, we seldom do it.

@ahgblopes
I reckon the gnome 3.4 installation should be relatively painless.
I've taken care not to break that with the Ubuntu patchset and I've been using the previously hard masked version of gnome-3.4 in conjunction with Unity without issue so far.
Look forward to reading what your experience is.

@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:

So there's a few important updates been included over the past few days.

I haven't made any progress on the wrong window placement bug yet

Apart from the version bumps and bugfixes, Unity should now (mostly) install and work if your active python version is python-3.
Supporting both python2 and python3 as Unity is moving to python3 as default, we end up with a mix of python2 and python3 lens packages.

Gconf backend for compiz settings is stabilising ready for migration to dconf, which means you can change the side launcher bar icons size (unity 3d only) via 'System settings > Appearance'.
It's not enabled by default yet as setting the launcher to autohide doesn't enable it to be revealed again.
If you want to try it you can enable the gconf backend in 'ccsm' Preferences.

Unity-lens-radios package has been added to search for online radio stations and have them open in rhythmbox.
Appmenu-firefox has been updated to be compatible with firefox-15.0.1.

After follow Alexandre' s instructions, i have a really nice, fast and smooth gnome 3.4 desktop!!

And a miracle: I don't know why, but decorated window buttons and OVERLAY SCROLLBAR works in unity2!!!! It is really amazing!!! Thank you again for bring us it!! I will stick with unity2d, because i' m really liking it, but i will now try to upgrade to python 3 and make unity (3d) works with it.

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

x11-libs/libXfixes:0

(x11-libs/libXfixes-5.0::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(x11-libs/libXfixes-5.0-r9999::unity-gentoo, ebuild scheduled for merge) pulled in by
=x11-libs/libXfixes-5.0-r9999 required by (unity-base/bamf-0.3.0::unity-gentoo, ebuild scheduled for merge)
>=x11-libs/libXfixes-5.0-r9999 required by (dev-libs/libunity-misc-4.0.4::unity-gentoo, ebuild scheduled for merge)
(and 4 more with the same problems)

x11-proto/fixesproto:0

(x11-proto/fixesproto-5.0-r9999::unity-gentoo, ebuild scheduled for merge) pulled in by
=x11-proto/fixesproto-5.0-r9999 required by (x11-libs/libXfixes-5.0-r9999::unity-gentoo, ebuild scheduled for merge)

(x11-proto/fixesproto-5.0::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

net-libs/libsoup:2.4

(net-libs/libsoup-2.38.1::gentoo, ebuild scheduled for merge) pulled in by
>=net-libs/libsoup-2.37.91:2.4[introspection?] required by (dev-libs/libgdata-0.12.0::gentoo, ebuild scheduled for merge)

(net-libs/libsoup-2.36.1-r1::gentoo, ebuild scheduled for merge) pulled in by
~net-libs/libsoup-2.36.1 required by (net-libs/libsoup-gnome-2.36.1::gentoo, ebuild scheduled for merge)

media-libs/mesa:0

(media-libs/mesa-8.0.4-r1::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(media-libs/mesa-8.0.3::gentoo, ebuild scheduled for merge) pulled in by
<=media-libs/mesa-8.0.4 required by (unity-base/compiz-0.9.7.8-r1::unity-gentoo, ebuild scheduled for merge)

(sys-fs/udev-171-r6::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

x11-libs/libXfixes:0

(x11-libs/libXfixes-5.0::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(x11-libs/libXfixes-5.0-r9999::unity-gentoo, ebuild scheduled for merge) pulled in by
=x11-libs/libXfixes-5.0-r9999 required by (unity-base/bamf-0.3.0::unity-gentoo, ebuild scheduled for merge)
>=x11-libs/libXfixes-5.0-r9999 required by (dev-libs/libunity-misc-4.0.4::unity-gentoo, ebuild scheduled for merge)
(and 4 more with the same problems)

x11-proto/fixesproto:0

(x11-proto/fixesproto-5.0-r9999::unity-gentoo, ebuild scheduled for merge) pulled in by
=x11-proto/fixesproto-5.0-r9999 required by (x11-libs/libXfixes-5.0-r9999::unity-gentoo, ebuild scheduled for merge)

(x11-proto/fixesproto-5.0::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

net-libs/libsoup:2.4

(net-libs/libsoup-2.38.1::gentoo, ebuild scheduled for merge) pulled in by
>=net-libs/libsoup-2.37.91:2.4[introspection?] required by (dev-libs/libgdata-0.12.0::gentoo, ebuild scheduled for merge)

(net-libs/libsoup-2.36.1-r1::gentoo, ebuild scheduled for merge) pulled in by
~net-libs/libsoup-2.36.1 required by (net-libs/libsoup-gnome-2.36.1::gentoo, ebuild scheduled for merge)

media-libs/mesa:0

(media-libs/mesa-8.0.4-r1::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(media-libs/mesa-8.0.3::gentoo, ebuild scheduled for merge) pulled in by
<=media-libs/mesa-8.0.4 required by (unity-base/compiz-0.9.7.8-r1::unity-gentoo, ebuild scheduled for merge)

(sys-fs/udev-171-r6::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.

And make a "package.keywords" folder inside etc/portage and make a symlink to /var/lib/layman/unity-gentoo/PACKAGES inside it. Don't put anything inside package.unmask, this is unnecessary (i only have dev-java/oracle-jdk-bin on mine package.unmask file).

and about =sys-libs/db-5.1.29, i don't have it on any of my files, but i guess i accidentally removed it... Try first put it on package.accept_keywords, and if it doesn't work put it on package.unmask .

I had /etc/portage/package.keywords as a file contain various keywords, I have now deleted this and created a folder called package.keywords.

Quote:

And make a "package.keywords" folder inside etc/portage and make a symlink to /var/lib/layman/unity-gentoo/PACKAGES inside it. Don't put anything inside package.unmask, this is unnecessary (i only have dev-java/oracle-jdk-bin on mine package.unmask file).

What do I call the file inside the folder which needs symlinking to /var/lib/layman/unity-gentoo/PACKAGES?

I had /etc/portage/package.keywords as a file contain various keywords, I have now deleted this and created a folder called package.keywords.

Quote:

And make a "package.keywords" folder inside etc/portage and make a symlink to /var/lib/layman/unity-gentoo/PACKAGES inside it. Don't put anything inside package.unmask, this is unnecessary (i only have dev-java/oracle-jdk-bin on mine package.unmask file).

What do I call the file inside the folder which needs symlinking to /var/lib/layman/unity-gentoo/PACKAGES?

Only for convenience "unity-gentoo", but it doesn't matter, you can put anything!

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

dev-libs/gobject-introspection:0

(dev-libs/gobject-introspection-1.30.0-r2::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(dev-libs/gobject-introspection-1.32.1::gentoo, ebuild scheduled for merge) pulled in by
>=dev-libs/gobject-introspection-1.32 required by (x11-libs/gtk+-99.3.4.2::unity-gentoo, ebuild scheduled for merge)
(and 2 more with the same problem)

x11-libs/gdk-pixbuf:2

(x11-libs/gdk-pixbuf-2.24.1-r1::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(x11-libs/gdk-pixbuf-2.26.3::gentoo, ebuild scheduled for merge) pulled in by
>=x11-libs/gdk-pixbuf-2.26:2[introspection?,X?] required by (x11-libs/gtk+-99.3.4.2::unity-gentoo, ebuild scheduled for merge)
(and 1 more with the same problem)

net-libs/libsoup:2.4

(net-libs/libsoup-2.38.1::gentoo, ebuild scheduled for merge) pulled in by
>=net-libs/libsoup-2.37.91:2.4[introspection?] required by (dev-libs/libgdata-0.12.0::gentoo, ebuild scheduled for merge)

(net-libs/libsoup-2.36.1-r1::gentoo, ebuild scheduled for merge) pulled in by
~net-libs/libsoup-2.36.1 required by (net-libs/libsoup-gnome-2.36.1::gentoo, ebuild scheduled for merge)

gnome-base/gnome-keyring:0

(gnome-base/gnome-keyring-2.32.1-r1::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(gnome-base/gnome-keyring-3.4.1::gentoo, ebuild scheduled for merge) pulled in by
>=gnome-base/gnome-keyring-3.3.90 required by (gnome-base/gnome-shell-3.4.2::gentoo, ebuild scheduled for merge)
(and 1 more with the same problem)

net-libs/telepathy-glib:0

(net-libs/telepathy-glib-0.18.1::gentoo, ebuild scheduled for merge) pulled in by
>=net-libs/telepathy-glib-0.17.5 required by (dev-libs/folks-0.6.9::gentoo, ebuild scheduled for merge)
(and 1 more with the same problem)

(net-libs/telepathy-glib-0.16.5::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

gnome-base/libgnome-keyring:0

(gnome-base/libgnome-keyring-3.4.1::gentoo, ebuild scheduled for merge) pulled in by
>=gnome-base/libgnome-keyring-3.1.92 required by (gnome-base/gnome-keyring-3.4.1::gentoo, ebuild scheduled for merge)

(gnome-base/libgnome-keyring-2.32.0::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(sys-fs/udev-171-r6::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

media-sound/pulseaudio:0

(media-sound/pulseaudio-1.1-r1::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(media-sound/pulseaudio-2.1-r1::gentoo, ebuild scheduled for merge) pulled in by
>=media-sound/pulseaudio-2.0[glib] required by (gnome-base/gnome-control-center-99.3.4.2::unity-gentoo, ebuild scheduled for merge)

It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.

If you are making your files in etc/portage from scratch, after remove all of the lines in package.keywords and symlink /var/lib/layman/unity-gentoo/PACKAGES in /etc/portage/package.keywords/unity-gentoo, you will have to put a few packages inside package.accept_keywords (or package.keywords), but this is so easy (portage will tell you what to do). And if you want to have a nice, fast, smooth and stable gnome 3.4 (a entire gnome 3.4), simply entry these lines in a file called "gnome3" (make it) inside package.keywords file (and you will also have to put a few extra packages inside package.keywords file, but portage will tell you what to do)...