[Bug 167719] New: Can't login with network mounted home

[Dmitrij S.Kryzhevich]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=167719         
           Summary: Can't login with network mounted home
           Product: kde
           Version: unspecified
          Platform: RedHat RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs kde org
        ReportedBy: krege land ru


Version:            (using KDE 4.1.0)
Installed from:    RedHat RPMs
Compiler:          gcc (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8) 
OS:                Linux

I have home mounted with autofs which gets information from LDAP. When I trying to start KDE I get only splash window and bakground image. Splash in about one minute will disappear and only backround image is what I have. I cleaned out all my preferences, it did not helped. At the same time root login is fine. Looking at ~/.xsession-errors I see many errors whith dbus like:

<unknown program name>(18011)/: Communication problem with  "krunner" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

Or:

kdeinit4: preparing to launch /usr/bin/plasma
plasma(18093): Communication problem with  "plasma" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

And all stopped on:

QDBusConnection received a message of type 2 that it shouldn't have
*** PULSEAUDIO: Unable to connect: Connection refused
*** Is your sound server running?
*** See: http://www.pulseaudio.org/wiki/Troubleshooting

Also, there are following "E" messages apear at the beginning:
E: polkit.c: Cannot connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
E: main.c: daemon startup failed.

Others DE or WM starts fine.