I will try to dig in a bit. My X clearly doesn't start until the penalty 120 secs expire, so I'd like to understand why, since for what you are saying this shouldn't be the case (and there is, indeed, a kdm.conf in /etc/init).
In the meantime: I use KDE, with KDM set to autologin to a user account. In that user account, I run the script I show below (in .kde/Autostart/). It basically runs an xterm, and then records the time since boot started. It gives me a measure of the time from cold boot into a usable desktop. I will play a bit with lightdm, and will also try disabling autologin in KDM. Cheers -- Leo #!/bin/bash # # 2009, Leo Milano # # Credits: http://www.perlmonks.org/?node_id=11582 # http://www.linuxscrew.com/2007/09/04/two-way-conversion-of-unix-time-seconds-since-1970-and-regular-time/ # # Customize this if needed log_file=~/boot_time.log # A trick to make sure the script doesn't run this xterm in the background, # we want the window to popup before we go on with the script # Choose one of the dummy commands below dummy=`xterm -e echo hi` boot_time=`perl -ne 'print scalar $1 if /^btime (\d+)/' /proc/stat` this_time=`date +%s` let elapsed_time=this_time-boot_time echo `date`. Boot Time [s]: ${elapsed_time} >> ${log_file} -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
