[gentoo-user] can't build gnome 3.2 (3.0 was ok)

[Allan Gottlieb <gottlieb@nyu.edu>]

For me, gnome 3.2 has been quite a regression over 3.0.

Summary:

gdm-3.2.0-r1 crashes and when I revert to the 3.0 gdm, I get to the
login screen but then gnome-shell crashes.  I tried to downgrade to
gnome-shell-3.0.2-r1, but that needs libgnome-menu, which is not in
portage/layman.

The crash of gdm is described in bug #385525.

The crash of gnome-shell is described in the following .xsession-errors
file (tracker-miner-fs.log and tracker-store.log are empty).

any help would be appreciated.
allan

================================================================

oldlap tracker # cat /home/eva/.xsession-errors 
/etc/gdm/Xsession: Beginning session setup...
which: no keychain in (/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.1.1:/usr/i686-pc-linux-gnu/gcc-bin/4.5.3:/usr/i686-pc-linux-gnu/gnat-gpl-bin/4.1:/usr/libexec/gnat-gpl/i686-pc-linux-gnu/4.1:/usr/games/bin)
/etc/gdm/Xsession: Setup done, will execute: /usr/bin/dbus-launch --exit-with-session /usr/bin/ssh-agent -- gnome-session
GNOME_KEYRING_CONTROL=/tmp/keyring-DMA2OM
GNOME_KEYRING_PID=5649
GNOME_KEYRING_CONTROL=/tmp/keyring-DMA2OM
GNOME_KEYRING_CONTROL=/tmp/keyring-DMA2OM
GPG_AGENT_INFO=/tmp/keyring-DMA2OM/gpg:0:1
GNOME_KEYRING_CONTROL=/tmp/keyring-DMA2OM
GPG_AGENT_INFO=/tmp/keyring-DMA2OM/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-DMA2OM/ssh
Initializing tracker-miner-fs...
Initializing tracker-store...
Tracker-Message: Setting up monitor for changes to config file:'/home/eva/.config/tracker/tracker-miner-fs.cfg'
Starting log:
  File:'/home/eva/.local/share/tracker/tracker-miner-fs.log'
Tracker-Message: Setting up monitor for changes to config file:'/home/eva/.config/tracker/tracker-store.cfg'
Tracker-Message: Setting up monitor for changes to config file:'/home/eva/.config/tracker/tracker-store.cfg'
Starting log:
  File:'/home/eva/.local/share/tracker/tracker-store.log'
Failed to play sound: File or data not found

(gnome-shell:5676): Bluetooth-WARNING **: Could not open RFKILL control device, please verify your installation
      JS LOG: GNOME Shell started at Tue Oct 11 2011 17:23:24 GMT-0400 (EDT)
Window manager warning: Log level 16: get_all_cb: couldn't retrieve system settings properties: (25) Launch helper exited with unknown return code 1.
gnome-shell-calendar-server[5718]: Got HUP on stdin - exiting
gnome-session[5618]: WARNING: Application 'gnome-shell.desktop' killed by signal

(gnome-shell:5730): Bluetooth-WARNING **: Could not open RFKILL control device, please verify your installation
      JS LOG: GNOME Shell started at Tue Oct 11 2011 17:23:25 GMT-0400 (EDT)
Window manager warning: Log level 16: get_all_cb: couldn't retrieve system settings properties: (25) Launch helper exited with unknown return code 1.
gnome-session[5618]: WARNING: App 'gnome-shell.desktop' respawning too quickly
gnome-shell-calendar-server[5738]: Got HUP on stdin - exiting
gnome-session[5618]: WARNING: Application 'gnome-shell.desktop' killed by signal

(gnome-settings-daemon:5647): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
** Message: Got disconnected from the session message bus; retrying to reconnect every 10 seconds
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

Received signal:15->'Terminated'g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

(gdu-notification-daemon:5693): Gdk-WARNING **: gdu-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.


OK

oldlap tracker #