List Info

Thread: trying to understand debug of gdm login problem on FC9




trying to understand debug of gdm login problem on FC9
user name
2008-04-07 15:37:48
I can login in as root but not as a regular user on FC9 and
I'm trying
to understand where the failure is. It looks like the
session starts
and then immediately exits with a strange error code
"1#012" but I'm
not sure what this means. An ideas about what I can do to
track down
the failure? One thing I should add is that I'm using
SELinux and am
polyinstantiating /tmp for all users other than root. What
happens
when polyinstantiating is that the directory is bind mounted
on
another directory during the pam session creation. I've
successfully
run this configuration on RHEL5 and previous versions of
Fedora.

Apr  7 11:42:16 comms gconfd (tedx-5589): starting (version
2.22.0),
pid 5589 user 'tedx'
Apr  7 11:42:16 comms gconfd (tedx-5589): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a
read-only
configuration source at position 0
Apr  7 11:42:16 comms gconfd (tedx-5589): Resolved address
"xml:readwrite:/home/tedx/.gconf" to a writable
configuration source
at position 1
Apr  7 11:42:16 comms gconfd (tedx-5589): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a
read-only
configuration source at position 2
Apr  7 11:42:16 comms gdm-session-worker[5544]: DEBUG:
GdmSessionWorker: state SESSION_OPENED
Apr  7 11:42:16 comms gdm-session-worker[5544]: DEBUG:
GdmSessionWorker: attempting to change state to
SESSION_STARTED
Apr  7 11:42:16 comms gdm-session-worker[5544]: DEBUG:
GdmSessionWorker: querying pam for user environment
Apr  7 11:42:16 comms gdm-session-worker[5544]: DEBUG:
GdmSessionWorker: opening user session with program
'/etc/gdm/Xsession'
Apr  7 11:42:16 comms gdm-session-worker[5544]: DEBUG:
GdmSessionWorker: session opened creating reply...
Apr  7 11:42:16 comms gdm-session-worker[5544]: DEBUG:
GdmSessionWorker: state SESSION_STARTED
Apr  7 11:42:16 comms gdm-session-worker[5544]: DEBUG:
GdmSessionWorker: Calling SessionStarted
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG:
session_message_handler: destination=(null)
obj_path=/org/gnome/DisplayManager/Session
interface=org.gnome.DisplayManager.Session
method=SessionStarted
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG:
GdmSessionDirect:
Handling SessionStarted
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG:
GdmSessionDirect:
Emitting 'session-started' signal with pid '5633'
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: using
ut_user tedx
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: Writing
login record
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: using
ut_type USER_PROCESS
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: using
ut_tv time 1207586536
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: using
ut_pid 5633
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: using
ut_id :0
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: using
ut_host :0
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: using
ut_line tty7
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: Writing
wtmp
session record to /var/log/wtmp
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: Adding
new utmp record
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG:
GdmSimpleSlave:
session started 5633
Apr  7 11:42:16 comms gdm-session-worker[5544]: DEBUG:
GdmSessionWorker: child (pid:5633) done (status:1)
Apr  7 11:42:16 comms gdm-session-worker[5544]: DEBUG:
GdmSessionWorker: Calling SessionExited
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG:
session_message_handler: destination=(null)
obj_path=/org/gnome/DisplayManager/Session
interface=org.gnome.DisplayManager.Session
method=SessionExited
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG:
GdmSessionDirect:
Emitting 'session-exited' signal with exit code '1'
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: Writing
logout record
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: using
ut_type DEAD_PROCESS
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: using
ut_tv time 1207586536
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: using
ut_pid 5633
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: using
ut_id :0
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: using
ut_host :0
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: using
ut_line tty7
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: Writing
wtmp
logout record to /var/log/wtmp
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG:
Removing utmp record
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG:
GdmSimpleSlave:
session exited with code 1#012
Apr  7 11:42:16 comms gdm-simple-slave[5475]: DEBUG: slave
finished
_______________________________________________
gdm-list mailing list
gdm-listgnome.org
http:
//mail.gnome.org/mailman/listinfo/gdm-list

Re: trying to understand debug of gdm login problem on FC9
user name
2008-04-07 16:33:41
Hi,

> I can login in as root but not as a regular user on FC9
and I'm trying
>  to understand where the failure is. It looks like the
session starts
>  and then immediately exits with a strange error code
"1#012" but I'm
>  not sure what this means.
I think the #012 is just rsyslog gobbledy gook. it's exit
code 1 below
in your log.

> An ideas about what I can do to track down
>  the failure? One thing I should add is that I'm using
SELinux and am
>  polyinstantiating /tmp for all users other than root.
What happens
>  when polyinstantiating is that the directory is bind
mounted on
>  another directory during the pam session creation.
I've successfully
>  run this configuration on RHEL5 and previous versions
of Fedora.
so we create an auth cookie for the user in /tmp.  If /tmp
is getting
replaced, the auth cookie won't be around anymore and
clients won't be
allowed to talk to the server.

(and will probably exit 1).  I don't know if that's your
problem
specifically, but it seems probable.

We should probably move the X auth cookies to /var/run/gdm

Do you have the ability to populate your /tmp during the
login
process? if so, copying from the real /tmp that file would
verify if
that's the problem or not (the location is stored in the
XAUTHORITY
environment variable)

--Ray
_______________________________________________
gdm-list mailing list
gdm-listgnome.org
http:
//mail.gnome.org/mailman/listinfo/gdm-list

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )