Pretty much all of the gstreamer-1.0.2:1.0 bump has now made it into the 'gnome' overlay and the gstreamer-0.10.36:0.10 bump has made into the main tree as a package.mask.
From this almost all the gstreamer packages in the 'unity-gentoo' overlay are now removed in favour of using those in the 'gnome' overlay and the main tree.

This means that it is now a requirement to package.unmask gstreamer-0.10.36 as it's required for all versions of the unity-lens-music package.
Thanks!

I was able to compile all stuff and also to login and start Unity once. After a crash of Unity I get every time a picture with a 'sad computer' and the message that somting gone wrong which could not restored. After that I get logged out.

I was able to compile all stuff and also to login and start Unity once. After a crash of Unity I get every time a picture with a 'sad computer' and the message that somting gone wrong which could not restored. After that I get logged out.

Any ideas how to get more information what gone wrong?

If you logged in using gdm, you can check the desktop user's ~/.xsession-errors (though since gnome-3.6 this isn't being created for me for some reason) or perhaps check /var/log/gdm/:0-greeter.log.
Check your syslog, or if starting via a terminal with 'startx' you could get some output on the terminal as to why it's failing.

Thx for the hints. The problem is the 'blueman' package which raises an exception in 'KillSwitch.py'. Maybe it's my fault. I've change the Python version back to 3.2 during my trys to compile Unity. Now some packages are compiled with Python 2.7 and some with Python 3.2.

I'll recompile everything again against 2.7 and let you know the outcome.
Or is it still possible to use Unity with Phython 3.2?

Thx for the hints. The problem is the 'blueman' package which raises an exception in 'KillSwitch.py'. Maybe it's my fault. I've change the Python version back to 3.2 during my trys to compile Unity. Now some packages are compiled with Python 2.7 and some with Python 3.2.

I'll recompile everything again against 2.7 and let you know the outcome.
Or is it still possible to use Unity with Python 3.2?

Good to see you got it sorted.
Multiple major python versions is definitely supported with Unity and is the goal.
I have both python-3.2 and python-2.7 installed using python-3.2 as the active version.
If any unity-gentoo package is only able to run with one version of python, it will seamlessly use that version regardless of what active python version you currently have set.
Conversely, some packages can use both python:2.7 and/or python:3.2.

In other news I performed another QA run by reverting my system back to gnome-2.32 and installing stable Unity-5 which upgrades up to gnome-3.4.
A few bugs fixed along the way mostly relating to gnome-3.6 dependencies creeping back into the Unity-5 packages which may have been deal breakers for those trying the stable approach.

@poncho
Thanks for the heads up on gdm-3.6's new '.xsession' log location

Great news, the annoying window placement bug has finally been nutted out and fixed!!!

Working closely with the Archlinux team who also had the same bug, we arrived at it being a simple cmake debug flag that was the culprit (-DNDEBUG).

Have committed a fix to the overlay so sync up and enjoy what is a massive improvement.
As a bonus, the same fix also fixes some minor graphics glitches in the dash pop-out and improves desktop initialisation speed.

Great news, the annoying window placement bug has finally been nutted out and fixed!!!

Working closely with the Archlinux team who also had the same bug, we arrived at it being a simple cmake debug flag that was the culprit (-DNDEBUG).

Have committed a fix to the overlay so sync up and enjoy what is a massive improvement.
As a bonus, the same fix also fixes some minor graphics glitches in the dash pop-out and improves desktop initialisation speed.

Cheers

That's really great news I'll try it immediately.

Other small question:
Nautilus doesn't show thumbnails of my pictures (jpeg/png etc.). I've searched in the net for a resolution, but I wasn't able to find something. I've enabled all USE-flags and enabled also the preview via dconf. But nothing works. Any idea why no thumbnails are shown?

Nautilus doesn't show thumbnails of my pictures (jpeg/png etc.). I've searched in the net for a resolution, but I wasn't able to find something. I've enabled all USE-flags and enabled also the preview via dconf. But nothing works. Any idea why no thumbnails are shown?

Are you using Unity-5 or are you unmasked with gnome-3.6 on Unity-6 ?

The thumbnail preview problem can happen if glib is updated to 2.34 and nautilus-99.3.4.2 is not rebuilt against the new glib.

If you're intending the gnome-3.6 with unity-6 route, ensure you have glib-99.2.34.1 installed and rebuild nautilus-99.3.4.2.
Let me know if that works for you and if it does, I'll look at ways of forcing nautilus to rebuild against the new glib if it's updated.

Otherwise if you're intending to use unity-5, then ensure you have glib-99.2.32.3 installed.

Either way a re-install of nautilus-99.3.4.2 may be the answer to your problem

Great news, the annoying window placement bug has finally been nutted out and fixed!!!

Working closely with the Archlinux team who also had the same bug, we arrived at it being a simple cmake debug flag that was the culprit (-DNDEBUG).

Have committed a fix to the overlay so sync up and enjoy what is a massive improvement.
As a bonus, the same fix also fixes some minor graphics glitches in the dash pop-out and improves desktop initialisation speed.

Cheers

I was really waiting (using mate) for it!!! I will try unity again. Thanks!!

@renegart
I haven't been including any lightdm stuff but instead using gdm as we use pretty much all of Gnome already anyway (not sure why Ubuntu used lightdm ?).

@ahgblopes
Welcome back!
Lots of improvements since you last tried and apart from a few backports, upstream development has pretty much stopped at the Quantal level as they move onto the Raring release development.
So package changes won't be as volatile and frequent as you experienced.

I'm not including Raring packages until gnome-3.6 has transitioned into the main tree from 'gnome' overlay which is already happening.
Then we can drop unity-5, unmask unity-6 as the new stable and start including Raring packages as masked.

Nice work! I did come across a little build problem, seems to be related to this Ubuntu cmake bug. No idea if this is my fault or not - amd64 unmasked and so many overlays it's not funny on this little experimental box so I don't spend too long worrying about bugs.

EDIT: Also needed to mask >media-libs/glew-1.7.0 and downgrade accordingly, otherwise unity-mt-grab-handles and unitycore plugins would fail to build (though the ebuild will accept this silently) and Unity will not load.

Hi,
I know it's a little bit fast, but it is possible to update 'x11-misc/appmenu-firefox' for the new firefox-17.0?
The appmenu-firefox is more or less blocking the update of the browser

Is it also possible to provide a similar package for thunderbird?

regarding unity-greeter for lightdm. I'm not so happy with the new gdm-3.4. Especially the new theme is horrible and I don't found an easy way to change it (yet).
I found a blog about unity-greeter on http://blog.hasnoname.de/linux/funtoo/unity-greeter-12-10-2-on-funtoogentoo/. unfortunately it doesn't work because it needs some dependency updates which are not easily possible for unity-5.

Still not convinced for the use of maintaining the Ubuntu lightdm stuff.
We already have all it's functionality provided by gdm and it's currently a direct requirement for the upcoming gnome-shell-3.6 anyway.

On another topic, had a look at including the webapps applications for the Unity desktop as shown here -> https://www.youtube.com/watch?v=L2YNR1KU1Xs
Nothing has been committed to overlay as it's not complete yet while I figure out it's many dependencies.

On hold as belonging to unity-extra/ and it comes with a couple of points to note:
1. Uses single sign-on to access all your webaccount user/pass and you agree to hand control of this over to Ubuntu (maybe an issue for the security minded)
2. It's integration doesn't trigger until you open the webpage for each relevant webapp anyway and the webpage must remain open for the integration to continue