My xorg is really strange (sometimes the screen goes black in some places or the mouse stops working (only working again after changing to a text terminal then changing again to X screen))

Definitely sounds like glitchy nvidia drivers.
You could try downgrading back to a lower version of nvidia-drivers (don't forget to quit xorg and 'rmmod nvidia' each time before restarting X).

By 'work' I mean that you get a desktop without compiz segfaulting.
It's great that unity-2d does work for you in this instance and points more strongly to the opengl/compiz implementation being a bit touchy.
Those decoration bugs (while not as frequent) are still present in unity-6.2 and strangely seem to only occur for GTK+ applications, nautilus is especially sensitive.

Quote:

And about start unity from command line ?

I would guess that using "XSESSION=unity startx" is failing for the same reason launching unity from gdm fails (ie. opengl and compiz not liking each other or it's unityshell plugin).

OK I've finally managed to fix the window decoration bugs as they relate to the top bar and appmenu.
These were disappearing window decoration on window restore and top window decoration still present on maximise instead of it snapping into the top appmenu bar.

I'll commit a fix ASAP but you can apply the fix yourself in the meantime.

For unity-2d, open up gconf-editor as your desktop user and disable the following key:

Code:

/apps/metacity/general/show_maximized_titlebars

For unity (3d), open up ccsm as your desktop user and go to 'Effects > Window Decoration'.
Where it says 'any' in the 'Decoration Windows' dialog box, change it to:

OK I've finally managed to fix the window decoration bugs as they relate to the top bar and appmenu.
These were disappearing window decoration on window restore and top window decoration still present on maximise instead of it snapping into the top appmenu bar.

I'll commit a fix ASAP but you can apply the fix yourself in the meantime.

For unity-2d, open up gconf-editor as your desktop user and disable the following key:

Code:

/apps/metacity/general/show_maximized_titlebars

For unity (3d), open up ccsm as your desktop user and go to 'Effects > Window Decoration'.
Where it says 'any' in the 'Decoration Windows' dialog box, change it to:

Code:

!state=maxvert

You are a genius!!
I will try it, NOW!!!

EDIT:

I cannot try it in unity, because the segfault, but it worked like a chamr in unity2d!!! Thank you!

Fixed the unity-base/indicator-datetime depend on gnome-extra/evolution-data-server and rolled it's version back to the Precise release of 0.3.94 as the 12.10.0 Quantal version needs evolution-data-server-3.5 which hasn't made it into the portage tree yet.
Thanks for the report!!

Quote:

I cannot downgrade unity from 6.2 to 5.12 anymore, so is there any way to use compiz 6.2 with a previous version of compiz ?

Unity 6.2 can use either compiz-0.9.7.8-r1 or compiz-0.9.8-r1.
If you require the lower version, mask the higher version.

Fixed the unity-base/indicator-datetime depend on gnome-extra/evolution-data-server and rolled it's version back to the Precise release of 0.3.94 as the 12.10.0 Quantal version needs evolution-data-server-3.5 which hasn't made it into the portage tree yet.
Thanks for the report!!

Quote:

I cannot downgrade unity from 6.2 to 5.12 anymore, so is there any way to use compiz 6.2 with a previous version of compiz ?

Unity 6.2 can use either compiz-0.9.7.8-r1 or compiz-0.9.8-r1.
If you require the lower version, mask the higher version.

The following keyword changes are necessary to proceed:
#required by unity-base/unity-6.2.0, required by unity-base/unity-meta-6.2.0, required by unity-meta (argument)
=unity-base/compiz-0.9.8-r1 ~amd64

The following mask changes are necessary to proceed:
#required by unity-base/unity-6.2.0, required by unity-base/unity-meta-6.2.0, required by unity-meta (argument)
=unity-base/compiz-0.9.8-r1

Is this a bug or am i bugged ??...

There is another thing that are making me crazy...

THE CEDILLA....

Cedilla (Ç) works for all applications, except for the gtk2 ones (firefox, libreoffice, leafpad, porthole, etc)...

In GTK2 apps i have to type right alt + , to get Cedilla, instead of '(accute) + C, that is the correct....

I googled about it and i discover that i need to change inmmodules file inside the /etc/gtk-2.0 folder, and add "en" to the cedilla line. I also put "export GTK_IM_MODULE=cedilla" in various files (/etc/profile, /etc/environment, ~/.env, etc...) I also replaced the ć to ç in compose file, but nothing works!!!!

But why am i posting this here? Because i suspect that it is a bug from this patched gtk2 version (or i'm going crazy!!)..
In gtk3 apps, in the popup menu from text boxes, i have an option called "input methods", and i have the "cedilla" option in it (is the default), but not in gtk2 ones (in gtk2 apps i have only one choice, labeled "simples" in portuguese, that means simple, i guess...)...

When i was using gnome2 all gtk2 apps worked fine with the cedilla....

Any help well be appreciated! And sorry for my english, i post this in hurry...

The following keyword changes are necessary to proceed:
#required by unity-base/unity-6.2.0, required by unity-base/unity-meta-6.2.0, required by unity-meta (argument)
=unity-base/compiz-0.9.8-r1 ~amd64

strange...This seems a portage bug. There isn't any error in repo side, i guess. The ebuild is telling to install >=unity-base/compiz-0.9.8 OR <unity-base/compiz-0.9.8 unity-base/ccsm unity-base/compizconfig-python x11-libs/libcompizconfig x11-plugins/compiz-plugins-main.

They're a lively lot these Ubuntu devs. and I wonder if I was a bit premature starting to bump packages up to Quantal.
No real major breakages and it's pretty rock solid, just the version updates are thick and fast at the moment.
Lots of fixes but a few regressions also that all need testing and it sucks a bit of time that I could be spending on issues such as you're seeing ahgblopes.

I'll live with that decision for now and keep maintaining the Quantal revisions as it should start to calm down somewhat in the next couple of days with feature freezes.
Following https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule , I'll jump in with the version bumps at the 1st Beta release next time

x11-plugins/compiz-plugins-main is masked in portage tree but is required by unity-base/compiz-0.9.7.8
As a result, emerge can't fulfill the requirements for installing compiz-0.9.7.8, so correctly falls through to attempting to install compiz-0.9.8.

So to get the achieved result of installing unity-6.2 with compiz-0.9.7.8, the following is required:

I uninstall unity (only the "unity" package), and now compiz works very well (without unity, of course)...

The problem is really with unity 6.2 (or nux 3.2, i guess).

Is there any way to downgrade to a previous version of unity (5.12 i guess) ? 5.12 worked fine, except the decoration bug (that is solved now.....).

Good to know that compiz is probably not to blame here and we can strike one possibility off the list.
Looks like unityshell hands off some function to nux, nux fails on it's geis implementation and so unityshell segfaults accordingly.

Unfortunately to have unity-5.12 (now unity-5.14) in the overlay, nux and all the utouch packages would also have to be downgraded.
I'll look at doing that but it will take a bit of time and ideally we should see if the problem can be fixed.

So to fixing the problem between unity/nux/geis...
Gesture (geis) support is optional in nux.
Nux gesture support is mandatory in unity (unity2d uses geis directly) so we can't disable that :/

I've added a 'debug' USE flag for nux, so enabling this and re-emerging nux may (or may not) give some more info.

It seems geis might be having some problem accessing your input device.
In an X terminal as your desktop user, try running 'geistest' and 'geisview' to see if it finds a valid input device.

If that fails, check you have the following:
Enabled CONFIG_INPUT_EVDEV support in your kernel under 'Device Drivers' > 'Input device support' > 'Event interface'.
Ensure you have x11-drivers/xf86-input-evdev installed (I'm using 2.7.0), and x11-proto/inputproto installed (I'm using 2.2).
Ensure Xorg is using the evdev input driver, a check of /var/log/Xorg.0.log should show this.

If the 'geistest' and 'geisview' programs show a valid input device, then we can probably safely assume that it is nux that is the culprit here.

(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 (dev-libs/libdbusmenu-0.6.2::unity-gentoo, ebuild scheduled for merge)
(and 12 more with the same problem)

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

x11-libs/gtk+:2

(x11-libs/gtk+-99.2.24.11-r1::unity-gentoo, ebuild scheduled for merge) pulled in by
>=x11-libs/gtk+-99.2.24.11:2 required by (x11-misc/appmenu-gtk-12.10.0::unity-gentoo, ebuild scheduled for merge)
(and 2 more with the same problem)

(x11-libs/gtk+-2.24.11-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 3 more with the same problem)

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

app-accessibility/at-spi2-core:2

(app-accessibility/at-spi2-core-2.2.3::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(app-accessibility/at-spi2-core-2.4.2::gentoo, ebuild scheduled for merge) pulled in by
>=app-accessibility/at-spi2-core-2.4 required by (app-accessibility/at-spi2-atk-2.5.3::unity-gentoo, ebuild scheduled for merge)

media-libs/mesa:0

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

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

gnome-base/gnome-desktop:3

(gnome-base/gnome-desktop-3.2.1::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(gnome-base/gnome-desktop-3.4.2::gentoo, ebuild scheduled for merge) pulled in by
>=gnome-base/gnome-desktop-3.3.92:3 required by (gnome-base/gnome-settings-daemon-99.3.4.2-r1::unity-gentoo, ebuild scheduled for merge)

Is there anything I can do to fix this? Is this a problem with my system?

(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 (dev-libs/libdbusmenu-0.6.2::unity-gentoo, ebuild scheduled for merge)
(and 12 more with the same problem)

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

x11-libs/gtk+:2

(x11-libs/gtk+-99.2.24.11-r1::unity-gentoo, ebuild scheduled for merge) pulled in by
>=x11-libs/gtk+-99.2.24.11:2 required by (x11-misc/appmenu-gtk-12.10.0::unity-gentoo, ebuild scheduled for merge)
(and 2 more with the same problem)

(x11-libs/gtk+-2.24.11-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 3 more with the same problem)

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

app-accessibility/at-spi2-core:2

(app-accessibility/at-spi2-core-2.2.3::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(app-accessibility/at-spi2-core-2.4.2::gentoo, ebuild scheduled for merge) pulled in by
>=app-accessibility/at-spi2-core-2.4 required by (app-accessibility/at-spi2-atk-2.5.3::unity-gentoo, ebuild scheduled for merge)

media-libs/mesa:0

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

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

gnome-base/gnome-desktop:3

(gnome-base/gnome-desktop-3.2.1::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(gnome-base/gnome-desktop-3.4.2::gentoo, ebuild scheduled for merge) pulled in by
>=gnome-base/gnome-desktop-3.3.92:3 required by (gnome-base/gnome-settings-daemon-99.3.4.2-r1::unity-gentoo, ebuild scheduled for merge)

Is there anything I can do to fix this? Is this a problem with my system?

Sorry for the late reply, adding 5.14 back in took some testing and I had done some breaking with testing python-3.2 that needed some fixing also.
Having mulitple python ABIs is still not there but it's improving at least, stick with using python-2.7 for now.

@ahgblopes
Added unity-5.14.0 back into the tree and created a unity-meta-5.14.0.
Missing keyword masked the unstable unity-6.2 and it's deps, so should work doing

Code:

emerge -a unity-meta

I've also backported the dbus-1.6 stuff from Quantal to work with unity-5.14 so that should be seamless.

Decided to mask the latest version because I was also experiencing some problems with it.
Graphics glitches in the lens overlay that would strangely clean itself once the screen was toggled to 'Show Desktop' and back again.
Unity-5.14 is able to successfully respawn itself from a crash whereas 6.2 would sort of try but the result was a missing top indicator and side launcher panels with some odd graphics glitches.