fedora-list Digest, Vol 4, Issue 437

[Ian Hilliard]

On Sun, 2004-06-27 at 17:18, fedora-list-request at redhat.com wrote:


> Date: Sun, 27 Jun 2004 16:31:54 +0200
> From: Ian Hilliard <i.hilliard at hilliardtech.com>
> Subject: KDE stopped working after an update
> To: fedora-list at redhat.com
> Message-ID: <1088346714.3314.1.camel at iansys.hilliardtech.com>
> Content-Type: text/plain; charset="us-ascii"
> 
> I've been running Fedora Core for a couple of weeks now and for the most
> part, it has worked quite well. As I prefer KDE to Gnome, I did an
> apt-get
> from apt.kde-redhat.org to get a more original KDE version.
> 
> Unfortunately,last Thursday when I did an update it seems to have broken
> something. I am no longer able to log into KDE. That is to say, when I
> log
> in at the login screen within a second I am returned to the login
> screen.
> I've been through /var/log/messages and /var/log/kdm.log, but there are
> no
> error alerts in those logs.
> 
> Does anyone else have the same problem? Does anyone else have any idea
> what the cause of the problem is?
> 
> Ian


Further to the failure of KDE:
I discovered in /var/log/secure that PAM was failing as there was a line
in /etc/pam.d/system-auth that ensured that the UID is less than 100.
This is the line:

account     sufficient    /lib/security/$ISA/pam_succeed_if.so uid < 100

I tested to see if setting this to a higher value (1000) would permit a
login. It did not. I did however get a new entry in /var/log/messages,
which read:

Jun 27 18:08:43 iansys kdm: :0[23196]: pam_timestamp: timestamp file
`/var/run/sudo/root/:0:ian' has unacceptable age (366 seconds),
disallowing access to kde for UID 0
Jun 27 18:08:43 iansys kde(pam_unix)[23196]: session opened for user ian
by (uid=0)
Jun 27 18:08:43 iansys kde(pam_unix)[23196]: session closed for user ian

I find this interesting in two ways. Firstly, I don't know why the
pam_timestamp is so outdated that it will not permit access. Secondly,
when I log in to Gnome, it uses pam authentication on user ian and not
root. Could there be some configuration problem with KDE or is this
normal? If there is a configuration problem, where is it and what should
it be?

The interesting thing is that a Gnome login only seconds later worked
without a problem and produced the following entries in
/var/log/messages:

Jun 27 18:20:24 iansys kdm: :0[23443]: pam_timestamp: timestamp file
`/var/run/sudo/root/:0:ian' is only 128 seconds old, allowing access to
kde for UID 0
Jun 27 18:20:24 iansys kde(pam_unix)[23443]: session opened for user ian
by (uid=0)
Jun 27 18:20:24 iansys gconfd (ian-23531): starting (version 2.6.0), pid
23531 user 'ian'
Jun 27 18:20:24 iansys gconfd (ian-23531): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config
source at position 0
Jun 27 18:20:24 iansys gconfd (ian-23531): Resolved address
"xml:readwrite:/home/ian/.gconf" to a writable config source at position
1
Jun 27 18:20:24 iansys gconfd (ian-23531): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config
source at position 2

I hope that someone can help.

Regards,
Ian

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20040627/9c00085f/attachment-0001.htm>