Bug 6695 - Possible problem with pam_ldap/pam and X..
Possible problem with pam_ldap/pam and X..
Product: Red Hat Linux
Classification: Retired
Component: pam_ldap (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Preston Brown
Depends On:
  Show dependency treegraph
Reported: 1999-11-03 17:23 EST by Michael Maher
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-24 16:06:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Maher 1999-11-03 17:23:05 EST
It's going to be hard for me to recreate this problem,
but I currently have a system that will not start X as a
user, but will as root.

the message receieved is:

  Authentication failed cannot start Xserver
  Perhaps you did not have Console ownership.

I've checked everything I can think of to solve this
problem.  Various strace's show that it is trying to

BEfore you ask.. pam-68-8 and updates from the 6.1 errata
are all installed.  Latestest 6.1 Xserver stuff is
installed.  Perhaps this is an ldap problem.

- checked permission on /dev/console
- checked /etc/security/console.apps
- checked to see that /etc/pam.d/xserver was properly setup.
- checked to make sure that the ldap.conf file is working
   properly.  Other machines are working ok with this setup.

This machine was working properly, but then crashed while
using staroffice.  After that it stopped starting X for
users.  I have removed every .Xauth, /tmp/{*,.*} and so
forth that I could find.  Nothing relevant is in any log
Comment 1 Johan Walles 1999-11-30 08:44:59 EST
You solve this problem by adding the following line...

session    optional	/lib/security/pam_console.so

... to the end of /etc/pam.d/login (which I suppose you have copied from

  Cheers //Johan

Note You need to log in before you can comment on or make changes to this bug.