Hello,

When I try to login as a non-root user after power up, in Slackware 10.2+FRG-2.12.1 through GDM, I get the following error 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 disk space. Try logging in with one of the failsafe sessions to see if you can fix this problem.

This is the content of ~/.xsessions file:

stderr is not a tty -- where are you?
_IceTransSocketUNIXCreateListener: ... SocketCreateListener() failed
_IceTransMakeAllCOTSServerListener: server already running
** (gnome-session:6194): WARNING **: cannot establish any listening sockets

After one or two subsequent attemps, I will be able to login. After successful login, this problem is not repeated until another power up.

This problem is not seen when I login as root.

I have observed this problem even in Slack 10 and Slack 10.1. But so far I am unable find a fix for this. Any hints?

Thanks for your help.

Anand

im guessing you have diskspace left, and your /tmp is on a partition that has diskspace left?

My /tmp has enough space.

I'm having this same problem...does anyone know of a fix? Strange thing is, this problem also happens when I try to log in as root, as well as any other user account. And, the .xsession-errors file is always empty, so it's as if no errors are being written to the log. I've tried emptying /tmp, chaning permissions on the files in /tmp....but no luck.

Any suggestions are appreciated.

I just had this problem trying to remotely configure my red-hat e3 box from a mac laptop to accept the MAC as an X-Client. I fiddled with some /etc/X11 files and kill -HUP the /usr/X1196/bin line. I think this caused it. I tried removing .ICEAuthority but no help. I can log in as root but no good. Now I get Xlib: connection to ":0.0" refused by server if i su to username then gnome-session or startkde. All I know is that it had something to do with changing the /etc/X11 files and/or kill -HUP the XServer. Anyone gets anywhere or if I do pls repost

Can you post your etc/gdm/Xsession file? Smth can be badly configured there.

I did not have that file there but did in /etc/X11/xdm

#!/bin/bash
# Copyright (c) 1999-2002 Red Hat, Inc.

# redirect errors to a file in user's home directory if we can
errfile="$HOME/.xsession-errors"
if cp /dev/null "$errfile" 2> /dev/null ; then
chmod 600 "$errfile"
exec > "$errfile" 2>&1
else
errfile=`mktemp -q /tmp/xses-$USER.XXXXXX`
if [ $? -eq 0 ]; then
exec > "$errfile" 2>&1
fi
fi

if ! printenv PATH | grep -q /usr/X11R6/bin
then
PATH="${PATH}":/usr/X11R6/bin
fi

xsetroot -solid '#5477A0'

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
userxkbmap=$HOME/.Xkbmap

sysresources=/etc/X11/Xresources
sysmodmap=/etc/X11/Xmodmap
sysxkbmap=/etc/X11/Xkbmap

# merge in defaults
if [ -f "$sysresources" ]; then
xrdb -merge "$sysresources"
fi

if [ -f "$userresources" ]; then
xrdb -merge "$userresources"
fi

# merge in keymaps
if [ -f "$sysxkbmap" ]; then
setxkbmap $(cat "$sysxkbmap")
XKB_IN_USE=yes
fi

if [ -f "$userxkbmap" ]; then
setxkbmap $(cat "$userxkbmap")
XKB_IN_USE=yes
fi

if [ -z "$XKB_IN_USE" -a ! -L /etc/X11/X ]; then
if grep '^exec.*/Xsun' /etc/X11/X > /dev/null 2>&1 && [ -f /etc/X11/XF86Config ]; then
xkbsymbols=`sed -n -e 's/^[ ]*XkbSymbols[ ]*"\(.*\)".*$/\1/p' /etc/X11/XF86Config`
if [ -n "$xkbsymbols" ]; then
setxkbmap -symbols "$xkbsymbols"
XKB_IN_USE=yes
fi
fi
fi

# xkb and xmodmap don't play nice together
if [ -z "$XKB_IN_USE" ]; then
if [ -f "$sysmodmap" ]; then
xmodmap "$sysmodmap"
fi

if [ -f "$usermodmap" ]; then
xmodmap "$usermodmap"
fi
fi

unset XKB_IN_USE

# run all system xinitrc shell scripts.
for i in /etc/X11/xinit/xinitrc.d/* ; do
if [ -x "$i" ]; then
. "$i"
fi
done

# is ssh-agent available?
SSHAGENT=
[ -x /usr/bin/ssh-agent ] && SSHAGENT="/usr/bin/ssh-agent"

# now, we see if xdm/gdm/kdm has asked for a specific environment
case $# in
1)
if [ -x /usr/share/apps/switchdesk/Xclients.$1 ]; then
exec -l $SHELL -c "$SSHAGENT /usr/share/apps/switchdesk/Xclients.$1";
fi;

case $1 in
failsafe)
exec -l $SHELL -c "xterm -geometry 80x24-0-0"
;;
gnome)
exec -l $SHELL -c "$SSHAGENT gnome-session"
;;
kde|kde1|kde2)
exec -l $SHELL -c "$SSHAGENT /usr/share/apps/switchdesk/Xclients.kde"
;;
twm)
# fall back to twm
exec -l $SHELL -c "$SSHAGENT /usr/share/apps/switchdesk/Xclients.twm"
;;
esac
esac

# otherwise, take default action
if [ -x "$HOME/.xsession" ]; then
exec -l $SHELL -c "$SSHAGENT $HOME/.xsession"
elif [ -x "$HOME/.Xclients" ]; then
exec -l $SHELL -c "$SSHAGENT $HOME/.Xclients"
elif [ -x /etc/X11/xinit/Xclients ]; then
exec -l $SHELL -c "$SSHAGENT /etc/X11/xinit/Xclients"
else
# should never get here; failsafe fallback
exec -l $SHELL -c "xsm"
fi

Re: "Your session only lasted 10 seconds...."
I'm not very skilled using command-line stuff in Linux so here is what worked for me:
1. Log in as root rather than your normal user name.
2. Access the User Manager via APPLICATIONS, SYSTEM SETTINGS, USERS AND GROUPS
3. Correct the Home Directory that is shown for the normal user name. Mine incorrectly showed "/root" as the home directory. I changed it to "/home/username". Reboot and log in normally. All works fine now. Hope this helps someone else.

I have seen this problem too...
It turned out to be that the rights in the users home folder weren't set correctly, especially the ~/.gnome dirs....
For some strange reason, these dirs were uid root...
Setting the right permissions fixed the problem, hopefully for you the same.

I have the exact problem! But i know what cause mine. I accidentally, like root issued ( rm -rf ) and deleted whole /tmp directory and it's sub-dir's. I know, silly but now i cannot log like regular user, just like super-user only. Well i guess now I'm off to search how to fix this problem i casued myself .

btw --I am FC4 user

I don't know if this is against the forum rules, but I'm sure there's some sort of sexual joke refering to the title of this thread...

Can someone help me? My last session only lasted 10 seconds...

Had this same problem. In my case the permissions on /tmp were not set correctly due to the way we restored the system. To fix the problem, had to change the permissions to 777 by issuing the command:

chmod 1777 /tmp

Once I did this, I was able to log in as a regular (non root) user and all our problems were solved.

In our case this was with RHEL, but I'm assuming you could have a similar issue.

Try deleting .Xclients
In my case I think switchdesk left this around.
-toryt

Creat /tmp Directory in home Partition and give full permission. then restart pc