KDM starts successfully (displays a functioning login dialog). However, when credentials are entered, after a few seconds a login dialog is re-displayed and a session is not started. (It has been confirmed that the credentials are correct.) The following errors are recorded in kdm.log: klauncher(17416) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. kdeinit4: Communication error with launcher. Exiting! kdmgreet(17410)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server" kdmgreet(17410)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned Server terminated successfully (0). Closing log file. klauncher(2620) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. kdeinit4: Communication error with launcher. Exiting! kdmgreet(2526)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server" kdmgreet(2526)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned Server terminated successfully (0). Closing log file. klauncher(2509) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. kdeinit4: Communication error with launcher. Exiting! kdmgreet(2503)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server" kdmgreet(2503)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned Server terminated successfully (0). Closing log file. klauncher(2638) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. kdeinit4: Communication error with launcher. Exiting! kdmgreet(2450)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server" kdmgreet(2450)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned Server terminated successfully (0). Closing log file. klauncher(4293) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. kdeinit4: Communication error with launcher. Exiting! kdmgreet(4287)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server" kdmgreet(4287)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned Server terminated successfully (0). Closing log file. Wed Jan 11 22:19:48 EST 2012 klauncher(4416) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. kdeinit4: Communication error with launcher. Exiting! kdmgreet(4410)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server" kdmgreet(4410)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned [mi] EQ overflowing. The server is probably stuck in an infinite loop. Backtrace: 0: /usr/bin/X (xorg_backtrace+0x28) [0x459d70] 1: /usr/bin/X (mieqEnqueue+0x1b0) [0x4555bc] 2: /usr/bin/X (xf86PostMotionEventM+0x90) [0x475f03] 3: /usr/bin/X (xf86PostMotionEventP+0x31) [0x475fee] 4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f8cc8d41000+0x527f) [0x7f8cc8d4627f] 5: /usr/bin/X (0x400000+0x65fd2) [0x465fd2] 6: /usr/bin/X (0x400000+0x10756d) [0x50756d] 7: /lib64/libpthread.so.0 (0x7f8ccecc2000+0xfc70) [0x7f8ccecd1c70] 8: /usr/bin/X (0x400000+0x5e812) [0x45e812] 9: /lib64/libpthread.so.0 (0x7f8ccecc2000+0xfc70) [0x7f8ccecd1c70] 10: /lib64/libc.so.6 (memcpy+0x15b) [0x7f8ccdc84b9b] 11: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f8cc95b1000+0xe24c2) [0x7f8cc96934c2] 12: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f8cc95b1000+0x463c82) [0x7f8cc9a14c82] 13: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f8cc95b1000+0x463e4e) [0x7f8cc9a14e4e] 14: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f8cc95b1000+0x46012a) [0x7f8cc9a1112a] 15: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f8cc95b1000+0x419947) [0x7f8cc99ca947] 16: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f8cc95b1000+0x430771) [0x7f8cc99e1771] 17: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f8cc95b1000+0x13dfa6) [0x7f8cc96eefa6] 18: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f8cc95b1000+0x143da6) [0x7f8cc96f4da6] 19: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f8cc95b1000+0x1463af) [0x7f8cc96f73af] 20: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f8cc95b1000+0x14a1c8) [0x7f8cc96fb1c8] 21: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f8cc95b1000+0x1142e2) [0x7f8cc96c52e2] 22: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f8cc95b1000+0x41d607) [0x7f8cc99ce607] 23: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f8ccc2f1000+0x45342b) [0x7f8ccc74442b] [mi] EQ overflowing. The server is probably stuck in an infinite loop. No errors are found in Xorg.0.log. dbus reports to have started successfully. Rebuilding dbus, kdm and kdelibs did not help. KDE (kdm, kdelibs, etc.) are 4.7.3-r1. Dbus is 1.4.16. Reproducible: Always Steps to Reproduce: Try to login using KDM. Actual Results: Login prompt is redisplayed. Error message regarding klauncher crash is written in kdm.log file. Expected Results: Kdm starts session successfully (login prompt disappears and KDE start-up).
Created attachment 298813 [details] emerge --info
Created attachment 298815 [details] Xorg.0.log
That is what you say: > No errors are found in Xorg.0.log. Thats the reality: > [ 1654.397] (EE) Failed to load module "dri" (module does not exist, 0) > [ 1654.397] (II) LoadModule: "dri2" > [ 1654.398] (WW) Warning, couldn't open module dri2 > [ 1654.398] (II) UnloadModule: "dri2" > [ 1654.398] (II) Unloading dri2 > [ 1654.398] (EE) Failed to load module "dri2" (module does not exist, 0) ... > [ 1663.052] (EE) Query no Synaptics: 6003C8 > [ 1663.052] (--) SynPS/2 Synaptics TouchPad: no supported touchpad found > [ 1663.052] (EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware. > [ 1663.065] (EE) PreInit returned 11 for "SynPS/2 Synaptics TouchPad" > [ 1663.065] (II) UnloadModule: "synaptics"
Created attachment 298965 [details] Xorg.0.log
Created attachment 298967 [details] kdm.log
All the errors originally found in Xorg.0.log have been resolved - please see the new attached Xorg.0.conf. The reality: None of them turned out to be relevant since kdm still fails to start a session with an error about communicating with with d-bus (please see attached kdm.log): klauncher(31458) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. Executed d-bus status check: # /etc/init.d/dbus status * started
The problem still exists.
did you ever confirm that a dbus session has been strted in system? rc-status |grep dbus
# rc-status |grep dbus dbus [ started ] The same before and after a failed attempt by KDM to start a session.
Upgraded KDE to 4.7.4 - the same problem.
Did you tried other login manager or pure startx?
Tried startx now, but not certain what to look for. The nvidia driver loaded successfully (and displayed its logo), after that the screen on vt7 became black. Given that no login managers were started, don't know what to expect. According to the output in the terminal from which startx was executed, X server started and then shut itself down. But I might be misinterpreting the output. The output is repeated in the Xorg.0.log file I am attaching.
Created attachment 300585 [details] startx Xorg.0.log
(In reply to comment #12) > Tried startx now, but not certain what to look for. > > The nvidia driver loaded successfully (and displayed its logo), after that the > screen on vt7 became black. Given that no login managers were started, don't > know what to expect. You have to set up and valid xsession to start the window manager of your choice, see gentoo docs. Or test another login manager like slim or gdm.
