[gutsy] gnome login in to a black screen

It's not certain, but this *may* be related to Bug #141130.

Ok, after letting my computer 40 min on the black screen, it finally started the session, and seems now to be back to its normal speed (I have not tried to reboot yet)

Well the problem still occurs most of the time : the gnome session do not load completely, most of the time it just gives me a black screen and a mouse, sometime I get the task bars and wallpaper (and compiz working) but no button/menu and it takes ages to load.

I tried KDE and it works, i removed compiz and Xgl, and gnome still does not start correctly. Could it be a wrong configuration somewhere in the .gnome or .gnome2 folder ?

Well renaming theses folders does not help at all

I don't think this is a compiz issue. I installed from scratch 7.10 and everything works. Also a test account was all fine. X, compiz, keyboard, all fine.

Then I took the harddisk with the /home from another 7.04 install and tried to login to those users (after updating /etc/passwd of course). I first get a popup about the X keyboard not being the gnome keyboard. I clicked "use X keyboard" and then I stay on blank brown screen with the mouse pointer.

On the disk trackerd is indexing all my pictures.
From a ps output all processes seem to run. Maybe someone can see what's going on or what's missing with this ps:

george 18570 30146 0 18:35 ? 00:00:00 tracker-extract /home/george/doc/picture/paf02d5cada0f974c699b6b141fd11e42/ff5002fb.jpg.orig.jpg image/jpeg
george 18572 18570 0 18:35 ? 00:00:00 identify -format %w;\n%h;\n%c;\n -ping /home/george/doc/picture/paf02d5cada0f974c699b6b141fd11e42/ff5002fb.jpg.orig.jpg
root 18574 22798 0 18:35 pts/1 00:00:00 grep george
george 30071 1 0 18:18 ? 00:00:00 /usr/bin/gnome-keyring-daemon -d
george 30076 5351 0 18:18 ? 00:00:00 x-session-manager
george 30113 30076 0 18:18 ? 00:00:00 /usr/bin/ssh-agent x-session-manager
george 30115 1 0 18:18 ? 00:00:00 /usr/lib/libgconf2-4/gconfd-2 6
george 30119 1 0 18:18 ? 00:00:00 dbus-daemon --fork --print-address 17 --print-pid 19 --session
george 30121 1 0 18:18 ? 00:00:00 /usr/lib/gnome-control-center/gnome-settings-daemon
george 30128 30076 0 18:18 ? 00:00:00 metacity --sm-save-file 1112027889-5632-2218995048.ms
george 30136 30076 0 18:18 ? 00:00:00 bluetooth-applet
george 30144 30076 0 18:18 ? 00:00:00 /usr/lib/evolution/2.12/evolution-alarm-notify
george 30146 30076 16 18:18 ? 00:02:37 trackerd
george 30150 30076 0 18:18 ? 00:00:00 nm-applet --sm-disable
george 30151 30076 0 18:18 ? 00:00:00 python /usr/share/system-config-printer/applet.py
george 30152 1 0 18:18 ? 00:00:00 gnome-power-manager
george 30157 1 0 18:18 ? 00:00:00 /usr/lib/bonobo-activation/bonobo-activation-server --ac-activate --ior-output-fd=23
george 30162 1 0 18:18 ? 00:00:00 /usr/lib/evolution/2.12/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Connector_CalFactory:1.2 --oaf-ior-fd=17
george 30170 1 0 18:18 ? 00:00:00 /usr/lib/evolution/evolution-data-server-1.12 --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2 --oaf-ior-fd=18
george 30194 1 0 18:18 ? 00:00:00 gnome-screensaver

what I did to make it work:

move the home dir somewhere else and create a completely empty one with the same user and mode

then login. it works.
logout again.

move everything except dot files to the working homedir.
also move those dotfiles you know have nothing to do with gnome, like .mozilla etc...
This means you will have to reconfigure all your nice panels.

login still works.
you can now do try and error: move other files, login again.
But I would not try the .gnome* and similar. I did not do those trials so I don't know in the end which files contained the problem.

Is this still an issue?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.