(compiz:2079): GLib-WARNING **: In call to g_spawn_sync(), exit status
of a child process was requested but SIGCHLD action was set to SIG_IGN
and ECHILD was received by waitpid(), so exit status can't be returned.
This is a bug in the program calling g_spawn_sync(); either don't
request the exit status, or don't set the SIGCHLD action.

(compiz:2079): GLib-WARNING **: In call to g_spawn_sync(), exit status
of a child process was requested but SIGCHLD action was set to SIG_IGN
and ECHILD was received by waitpid(), so exit status can't be returned.
This is a bug in the program calling g_spawn_sync(); either don't
request the exit status, or don't set the SIGCHLD action.

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

x11-libs/qt-script:4

(x11-libs/qt-script-99.4.8.2::unity-gentoo, installed) pulled in by
~x11-libs/qt-script-99.4.8.2[aqua=,c++0x=,qpa=,debug=] required by (x11-libs/qt-gui-99.4.8.2::unity-gentoo, installed)

(x11-libs/qt-script-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-script-4.8.2[aqua=,c++0x=,qpa=,debug=] required by (x11-libs/qt-gui-4.8.2::gentoo, ebuild scheduled for merge)

x11-libs/qt-core:4

(x11-libs/qt-core-99.4.8.2::unity-gentoo, installed) pulled in by
~x11-libs/qt-core-99.4.8.2[aqua=,c++0x=,debug=,qpa=,qt3support=] required by (x11-libs/qt-opengl-99.4.8.2::unity-gentoo, installed)
(and 7 more with the same problem)

(x11-libs/qt-core-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-core-4.8.2[aqua=,c++0x=,qpa=,debug=,glib=,qt3support=] required by (x11-libs/qt-gui-4.8.2::gentoo, ebuild scheduled for merge)
(and 6 more with the same problem)

x11-libs/qt-xmlpatterns:4

(x11-libs/qt-xmlpatterns-99.4.8.2::unity-gentoo, installed) pulled in by
~x11-libs/qt-xmlpatterns-99.4.8.2[aqua=,c++0x=,qpa=,debug=] required by (x11-libs/qt-gui-99.4.8.2::unity-gentoo, installed)

(x11-libs/qt-xmlpatterns-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-xmlpatterns-4.8.2[aqua=,debug=,qpa=] required by (x11-libs/qt-webkit-4.8.2::gentoo, ebuild scheduled for merge)

x11-libs/qt-sql:4

(x11-libs/qt-sql-99.4.8.2::unity-gentoo, installed) pulled in by
~x11-libs/qt-sql-99.4.8.2[aqua=,c++0x=,qpa=,debug=] required by (x11-libs/qt-gui-99.4.8.2::unity-gentoo, installed)
(and 1 more with the same problem)

(x11-libs/qt-sql-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-sql-4.8.2[aqua=,c++0x=,debug=,qpa=,qt3support] required by (x11-libs/qt-qt3support-4.8.2::gentoo, ebuild scheduled for merge)

x11-libs/qt-dbus:4

(x11-libs/qt-dbus-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-dbus-4.8.2[aqua=,c++0x=,qpa=,debug=] required by (x11-libs/qt-gui-4.8.2::gentoo, ebuild scheduled for merge)
(and 1 more with the same problem)

(x11-libs/qt-dbus-99.4.8.2::unity-gentoo, installed) pulled in by
~x11-libs/qt-dbus-99.4.8.2[aqua=,c++0x=,qpa=,debug=] required by (x11-libs/qt-gui-99.4.8.2::unity-gentoo, installed)

x11-libs/qt-gui:4

(x11-libs/qt-gui-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-gui-4.8.2[accessibility=,aqua=,c++0x=,debug=,qpa=,qt3support] required by (x11-libs/qt-qt3support-4.8.2::gentoo, ebuild scheduled for merge)
(and 3 more with the same problem)

(x11-libs/qt-gui-99.4.8.2::unity-gentoo, installed) pulled in by
~x11-libs/qt-gui-99.4.8.2[aqua=,c++0x=,debug=,glib=,qpa=,qt3support] required by (x11-libs/qt-core-99.4.8.2::unity-gentoo, installed)
(and 3 more with the same problem)

x11-libs/qt-qt3support:4

(x11-libs/qt-qt3support-99.4.8.2::unity-gentoo, installed) pulled in by
~x11-libs/qt-qt3support-99.4.8.2[aqua=,c++0x=,debug=,qpa=] required by (x11-libs/qt-gui-99.4.8.2::unity-gentoo, installed)

(x11-libs/qt-qt3support-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-qt3support-4.8.2[aqua=,c++0x=,debug=,qpa=] required by (x11-libs/qt-gui-4.8.2::gentoo, ebuild scheduled for merge)

It may be possible to solve this problem by using package.mask to
prevent one of those packages (...)

Is there a easy way to fix it or i will need to create an local overlay and modify the ebuild to accept the 99* packages??

BUT! the error comes when i'm trying to install unity-meta. I'm using --autounmask-write, so... everything is unmasked.
installed qt version is 99.4.8.2
what am i doing wrong?

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

x11-libs/qt-core:4

(x11-libs/qt-core-99.4.8.2::unity-gentoo, installed) pulled in by
~x11-libs/qt-core-99.4.8.2[aqua=,c++0x=,debug=,qpa=,qt3support=] required by (x11-libs/qt-opengl-99.4.8.2::unity-gentoo, installed)
>=x11-libs/qt-core-99.4.8.2:4 required by (unity-base/dconf-qt-0.0.0.110722::unity-gentoo, installed)
(and 13 more with the same problems)

(x11-libs/qt-core-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-core-4.8.2[aqua=,c++0x=,qpa=,debug=,glib=,qt3support=] required by (x11-libs/qt-gui-4.8.2::gentoo, ebuild scheduled for merge)
(and 6 more with the same problem)

x11-libs/qt-gui:4

(x11-libs/qt-gui-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-gui-4.8.2[accessibility=,aqua=,c++0x=,debug=,qpa=,qt3support] required by (x11-libs/qt-qt3support-4.8.2::gentoo, ebuild scheduled for merge)
(and 2 more with the same problem)

(x11-libs/qt-gui-99.4.8.2::unity-gentoo, installed) pulled in by
~x11-libs/qt-gui-99.4.8.2[aqua=,c++0x=,debug=,glib=,qpa=,qt3support] required by (x11-libs/qt-core-99.4.8.2::unity-gentoo, installed)
(and 4 more with the same problem)

x11-libs/qt-script:4

(x11-libs/qt-script-99.4.8.2::unity-gentoo, installed) pulled in by
~x11-libs/qt-script-99.4.8.2[aqua=,c++0x=,debug=,qpa=] required by (x11-libs/qt-declarative-99.4.8.2::unity-gentoo, installed)
(and 1 more with the same problem)

(x11-libs/qt-script-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-script-4.8.2[aqua=,c++0x=,qpa=,debug=] required by (x11-libs/qt-gui-4.8.2::gentoo, ebuild scheduled for merge)

x11-libs/qt-dbus:4

(x11-libs/qt-dbus-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-dbus-4.8.2[aqua=,c++0x=,qpa=,debug=] required by (x11-libs/qt-gui-4.8.2::gentoo, ebuild scheduled for merge)

(x11-libs/qt-dbus-99.4.8.2::unity-gentoo, installed) pulled in by
~x11-libs/qt-dbus-99.4.8.2[aqua=,c++0x=,qpa=,debug=] required by (x11-libs/qt-gui-99.4.8.2::unity-gentoo, installed)

x11-libs/qt-sql:4

(x11-libs/qt-sql-99.4.8.2::unity-gentoo, installed) pulled in by
~x11-libs/qt-sql-99.4.8.2[aqua=,c++0x=,debug=,qpa=,qt3support=] required by (x11-libs/qt-declarative-99.4.8.2::unity-gentoo, installed)
(and 2 more with the same problem)

(x11-libs/qt-sql-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-sql-4.8.2[aqua=,c++0x=,debug=,qpa=,qt3support] required by (x11-libs/qt-qt3support-4.8.2::gentoo, ebuild scheduled for merge)

x11-libs/qt-xmlpatterns:4

(x11-libs/qt-xmlpatterns-99.4.8.2::unity-gentoo, installed) pulled in by
~x11-libs/qt-xmlpatterns-99.4.8.2[aqua=,c++0x=,debug=,qpa=] required by (x11-libs/qt-declarative-99.4.8.2::unity-gentoo, installed)
(and 1 more with the same problem)

(x11-libs/qt-xmlpatterns-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-xmlpatterns-4.8.2[aqua=,debug=,qpa=] required by (x11-libs/qt-webkit-4.8.2::gentoo, ebuild scheduled for merge)

x11-libs/qt-qt3support:4

(x11-libs/qt-qt3support-99.4.8.2::unity-gentoo, installed) pulled in by
~x11-libs/qt-qt3support-99.4.8.2[accessibility=,aqua=,c++0x=,debug=,qpa=] required by (x11-libs/qt-declarative-99.4.8.2::unity-gentoo, installed)
(and 1 more with the same problem)

(x11-libs/qt-qt3support-4.8.2::gentoo, ebuild scheduled for merge) pulled in by
~x11-libs/qt-qt3support-4.8.2[aqua=,c++0x=,debug=,qpa=] required by (x11-libs/qt-gui-4.8.2::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.

Once you have *all* the QT packages keyword unmasked, that command above will upgrade all your already installed QT packages to version 99.4.8.2.
The complete list of QT packages needed to unmask is in /usr/portage/x11-libs/qt-*.

Good luck!

EDIT: One easy way is to let the overlay automatically handle the keyword unmasking by copying or symlinking the /var/lib/layman/unity-gentoo/PACKAGES file into /etc/portage/package.keywords/

If you already have an /etc/portage/package.keywords file, rename it first to something other than 'package.keywords' and then copy that renamed file into the new /etc/portage/package.keywords/ directory.

ahgblopes, I too have tried changing some of the compiz plugins in ccsm and it causes the desktop to reliably crash and be unusable until I delete the ~/.config/compiz-1 ~/.cache/compizconfig-1 ~/.compiz* directories.
Looking at their bugs, this is a known issue for Unity for sometime now so a note to other users is don't mess with ccsm until Ubuntu can fix it.

And in other news unity-2d is in the process of being dropped completely for Quantal in favour of llvmpipe/gallium software rendering for unity-3d instead when a non-accelerated card is in use.
Which if it performs OK might be a small win for us as we won't need to patch QT anymore

ahgblopes, I too have tried changing some of the compiz plugins in ccsm and it causes the desktop to reliably crash and be unusable until I delete the ~/.config/compiz-1 ~/.cache/compizconfig-1 ~/.compiz* directories.
Looking at their bugs, this is a known issue for Unity for sometime now so a note to other users is don't mess with ccsm until Ubuntu can fix it.

And in other news unity-2d is in the process of being dropped completely for Quantal in favour of llvmpipe/gallium software rendering for unity-3d instead when a non-accelerated card is in use.
Which if it performs OK might be a small win for us as we won't need to patch QT anymore

Good to know it...

I upgraded my whole system, but now my keyboard and mouse don't work when i start X. (but i can see my clock working at the panel)...

iI'm using the xorg-server from gento repository, is it right or i must use the version from unity-gentoo repository??

edit:

I'm using the xorg-server from UNITY-GENTOO repository, is it right or i must use the version from GENTOO repository??

ps: I cannot install xorg-server from gentoo repository. I already did revdep-rebuild, etc...

Last edited by ahgblopes on Sat Aug 18, 2012 4:49 am; edited 1 time in total

Its is possible to split your overlay into a new one only with Ubuntu One (specially without Unity deps) ? Some people (like me) use Ubuntu One but not Unity._________________ex: Gentoo Linux Developer: amd64 media-optical sound gnome
ex: Portuguese Moderator
------------------------------------------------------------------------------
God Doesn't Play Dice

I upgraded my whole system, but now my keyboard and mouse don't work when i start X. (but i can see my clock working at the panel)...

When you upgrade xorg-server on Gentoo it's necessary to rebuild all your current x11-drivers with the command:

Code:

emerge -1av $(qlist -IC x11-drivers/)

Quote:

iI'm using the xorg-server from gento repository, is it right or i must use the version from unity-gentoo repository??

edit:

I'm using the xorg-server from UNITY-GENTOO repository, is it right or i must use the version from GENTOO repository??

ps: I cannot install xorg-server from gentoo repository. I already did revdep-rebuild, etc...

unity-base/unity deps. on the overlay version of x11-base/xorg-server.
This is because without this patched version of xorg-server, the side launcher cannot reveal itself when set to autohide.
The patch adds in some mouse pressure on screen boundary magic so your mouse has to do more than just hit the left edge or corner of the screen to have it reveal the launcher, you really have to 'push' the mouse against the trigger spot.

Its is possible to split your overlay into a new one only with Ubuntu One (specially without Unity deps) ? Some people (like me) use Ubuntu One but not Unity.

Sure thing.
If you already have the overlay synced, all you need do is:

Code:

emerge ubuntuone-client ubuntuone-control-panel

That won't pull anything in to do with Unity.
UbuntuOne is only pulled in as part of unity-base/unity-meta and unity-base/rhythmbox-ubuntuone for the music store integration into rhythmbox and the music lens.

If you're interested in splitting it out of the overlay, here are the packages:

Its is possible to split your overlay into a new one only with Ubuntu One (specially without Unity deps) ? Some people (like me) use Ubuntu One but not Unity.

Sure thing.
If you already have the overlay synced, all you need do is:

Code:

emerge ubuntuone-client ubuntuone-control-panel

That won't pull anything in to do with Unity.
UbuntuOne is only pulled in as part of unity-base/unity-meta and unity-base/rhythmbox-ubuntuone for the music store integration into rhythmbox and the music lens.

If you're interested in splitting it out of the overlay, here are the packages:

How are you starting Unity ?
You should be starting it via a display manager or by XSESSION=unity variable for 'startx'.
Ubuntu use the lightdm display manger (already in portage tree), I use gdm, but any display manager should do.

And in me wondering how you are starting Unity, it made me double check starting it without a display manager using:

Code:

XSESSION=unity startx

Found a typo in the gnome-base/gnome-session/files/unity.xsession file that would make it fail, fixed now.

How are you starting Unity ?
You should be starting it via a display manager or by XSESSION=unity variable for 'startx'.
Ubuntu use the lightdm display manger (already in portage tree), I use gdm, but any display manager should do.

And in me wondering how you are starting Unity, it made me double check starting it without a display manager using:

Code:

XSESSION=unity startx

Found a typo in the gnome-base/gnome-session/files/unity.xsession file that would make it fail, fixed now.

I use gdm, but i only know two ways for debug unity: read the xsession-errors file or start it from command line...

When i start it from gdm i get the same error (nothing happens, i get only the desktop, handled by nautilus)

i will try resync, rebuild, etc, etc... I hope this time it will work. Thank you for the patience and dedication to this project.

ps: this topic on gentoo wiki is outdated, is there some way to someone edit and uptade it?

Its is possible to split your overlay into a new one only with Ubuntu One (specially without Unity deps) ? Some people (like me) use Ubuntu One but not Unity.

Sure thing.
If you already have the overlay synced, all you need do is:

Code:

emerge ubuntuone-client ubuntuone-control-panel

That won't pull anything in to do with Unity.
UbuntuOne is only pulled in as part of unity-base/unity-meta and unity-base/rhythmbox-ubuntuone for the music store integration into rhythmbox and the music lens.

If you're interested in splitting it out of the overlay, here are the packages:

Yes could be your gfx card.
You could also check /var/log/Xorg.0.log to look for any errors and check your syslog too for any segfaults.
The only problem in your .xsession-errors output above is that compiz.desktop is getting killed because it fails to start even after several retries and doesn't provide much more info than that.
The nux warning is normal.

Does unity-2d work OK ?
What nvidia gfx card drivers are you using ?
You had it working at one stage, at what point did it start to misbehave and was it working with unity or was it falling back to unity-2d ?

Thinking it might be some pre-existing config in my Unity user's home directory that was forcing it to work for me, I tried running it with a completely fresh user to see if it would crash.
But it works fine.
This is something you could also try, add a test user and see if it will start as that user.

Also, check the output of

Code:

eselect opengl list

and try setting it to another entry, then try to start Unity.
Hope some of that helps.

Unfortunately I don't have any nvidia hardware to test with, only using Intel.
Can someone reading this using nvidia verify it to work on their system ?

Yes could be your gfx card.
You could also check /var/log/Xorg.0.log to look for any errors and check your syslog too for any segfaults.

I will do it soon...

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))

Quote:

The only problem in your .xsession-errors output above is that compiz.desktop is getting killed because it fails to start even after several retries and doesn't provide much more info than that.
The nux warning is normal.

OK...

Quote:

Does unity-2d work OK ?

It never worked ...
Maximized windows NEVER join with the panel... Also the alt + f2 hotkey doesn't work (but i guess this is normal)

It works very well with games and full hd (1080p) playback in youtube.

Quote:

You had it working at one stage, at what point did it start to misbehave and was it working with unity or was it falling back to unity-2d ?

Unity-2d never worked ... A previous (5.x, i guess) version of unity worked, but with those decoration bugs that i mentioned before.
After i updated to the more recent version (6, i guess) unity doesn't start...(only unity-2d starts, but windows doesn't join to the panel....)

Quote:

Thinking it might be some pre-existing config in my Unity user's home directory that was forcing it to work for me, I tried running it with a completely fresh user to see if it would crash.
But it works fine.
This is something you could also try, add a test user and see if it will start as that user.