Your session only lasted for less than 10 seconds

Raafi · 04-17-2005, 07:12 AM

I just installed FC3 and in usermode, i get this message

Your session only lasted less than 10 seconds. If you have not logged out yourself, this could mean that there is some installation problem or that you may be out of diskspace. Try logging inwithone of theh failsafe sessions to see if you can fix this problem

view errors...

Quote:

/etc/X11/gdm/PreSession/Default: Registering your sessing with wtmp and utmp
/etc/X11/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/gdm/:0.xservers" -h "" -1 ":0" "raafi" Agent pid 4053

(gnome-session:4025): libgonmevfs- WARNING &&:Unable to create ~/.gnome directory: Permission denied, Could not create per-user gnome Configuration directory '/home/raafi/.gnome' Permission denied

Can anyone assist me with this, as you can see, i have more than enough space, and i just reinstalled fedora, i doubt if there were any installation errors, (or could i be wrong?)

Emerson · 04-17-2005, 07:50 AM

You just reinstalled Fedora. Did you install over existing installation? If yes then you may not have write permission in your home directory due to user ID mismatch.

Raafi · 04-17-2005, 10:32 AM

i checked the permissions and found out my permission was to a number, so i changed it to the user name

BINGO, it allowed me access, but i had a new welcome screen

Quote:

GConf error: No database available to save your configuration: Unable to store a value at key '/apps/nautilus/preferences_version', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf

All further errors shown only on terminal.

now according to what my new welcome screen says, i have two gconf files, which i see, do i delete one or both of them?

regarding possibility number 3 and 4, i installed this in the same manner as i always have, this is not a network computer

now how do i handle looking into this possible lock?

and i know nothing about CORBA

zeos · 04-17-2005, 10:38 AM

did you recursively chown your home directory? (ie, make sure ~/.gconfd/* is set to username.groupname)

Raafi · 04-17-2005, 10:42 AM

Quote:

Originally posted by Emerson
You just reinstalled Fedora. Did you install over existing installation? If yes then you may not have write permission in your home directory due to user ID mismatch.

Yes i installed this over an existing Fedora, but i chose the clean install, not the repair.

Emerson · 04-17-2005, 04:56 PM

System identifies users by their UID, the name is attached to the UID for user convenience. If you want to keep your /home directory during reinstall you must recreate users with same UID (and GID) or else there is going to be a mess. This is what happened to you. You can see UID's in /etc/passwd file and edit them (as root).