Welcome to the new Linux Foundation Forum!

suddenly I cannot log in to one of my users qt4

Feb 10 user qt4

extracts from

cd /var/log

grep -i 'feb 10' * >feb10.txt

Something wrong with pam or selinux???

I have not fooled with pam or selinux

The secure file seems to report problems

I do regular yum update s

from feb10.txt: above

secure:Feb 10 08:00:20 localhost pam: gdm-password[2396]: pam_unix(gdm-password:session): session opened for user qt4 by (uid=0)

secure:Feb 10 08:00:48 localhost polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.37, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)

secure:Feb 10 08:00:54 localhost polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session3 (system bus name :1.71 [/usr/libexec/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)

secure:Feb 10 08:01:14 localhost pam: gdm-password[2937]: pam_unix(gdm-password:session): session opened for user qt4 by (uid=0)

secure:Feb 10 08:01:25 localhost polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session3 (system bus name :1.71, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)

secure:Feb 10 08:01:31 localhost polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session5 (system bus name :1.87 [/usr/libexec/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)

secure:Feb 10 08:01:58 localhost pam: gdm-password[3291]: pam_unix(gdm-password:session): session opened for user qt4 by (uid=0)

secure:Feb 10 08:02:09 localhost polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session5 (system bus name :1.87, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)

secure:Feb 10 08:02:15 localhost polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session7 (system bus name :1.102 [/usr/libexec/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)

secure:Feb 10 08:02:50 localhost pam: gdm-password[3615]: pam_unix(gdm-password:session): session opened for user qt4 by (uid=0)

secure:Feb 10 08:03:02 localhost polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session7 (system bus name :1.102, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)

secure:Feb 10 08:03:07 localhost polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session9 (system bus name :1.117 [/usr/libexec/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)

Comments

  • replying was the only way to attach the /var/log/secure (named securex.txt)

    edit didn't show an option to attach a .txt file

    did a

    cd /var/log
    cp secure securex.txt [file name=securex.txt size=0]http://www.linux.com/media/kunena/attachments/legacy/files/securex.txt[/file]
  • Goineasy9Goineasy9 Posts: 1,116
    It depends. Are you finding these lines in a log file or are they appearing when your doing something on the desktop? If you install something like GoogleEarth to the /opt folder, unless you give SELinux the correct permissions, it won't run and you will get errors similar to the ons you've posted.
    Can you give me some more info on what your doing when you encounter the errors?
  • after successful boot, I try to log into a user qt4.

    It goes along well and just before the background appears, I am suddenly back at the login screen (ice or broken glass)

    I am currently (for this post) using another user oracle.

    Thanks! The secure file is fresh being made since boot.

    I never got into qt4.

    I can now su - qt4 without problem.

    This started yesterday 10 Feb .

    I do frequent yum updates.

    oracle and qt4 are nearly identical.

    the secure file is attached above!.

    My profile image is intended to evoke frivolity
  • EUREKA! I tried logging into qt4 with
    kde (failsafe session) instead of just kde
    and I was able to successfully log in
Sign In or Register to comment.