You are not logged in.
On booting I sometimes get the message:
kdm[1149]: X server startup timeout, terminating
kdm[1149]: X server for display :0 cannot be started, session disabled
rebooting the system kdm always starts on the second attempt.
can someone help to debug? thanks a lot!
Last edited by miro279 (2014-06-16 08:32:26)
Offline
In '/usr/share/config/kdm/kdmrc' you have
# Core config for local displays
[X-:*-Core]
# How often to try to run the X-server. Running includes executing it and
# waiting for it to come up.
# Default is 1
#ServerAttempts=1
# How long to wait for a local X-server to come up.
# Default is 30
#ServerTimeout=30
# The command line to start the X-server, without display number and VT spec.
# This string is subject to word splitting.
# Default is "/usr/bin/X"
ServerCmd=/usr/bin/X
# Additional arguments for the X-servers for local sessions.
# This string is subject to word splitting.
# Default is ""
ServerArgsLocal=-nolisten tcpYou may try to change the 'ServerTimeout' value to something higher...
Offline
I set 60sec, but no change by that. Also I guess if the server times out in 30sec there must be some problem..
Funny thing is, it always doesn't work on the first boot of a day and always works after a reboot..
Offline
Have you try to change the 'ServerAttempts' value to more than 1?
Offline
This works. The first attempt on the day fails it then restarts successfully. So this is a workaround bit no solution to the problem.
In /var/log/kdm.log I find:
klauncher(1746) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(1734)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
might this be related?
Offline
Can you post the result of 'systemctl list-dependencies' please?
You can study your boot with 'systemd-analyze' to try to determine what takes time to start.
Offline
default.target
● ├─kdm.service
● └─multi-user.target
● ├─acpid.service
● ├─atieventsd.service
● ├─catalyst-hook.service
● ├─clamd.service
● ├─cpupower.service
● ├─cronie.service
● ├─cups.path
● ├─dbus.service
● ├─freenet.service
● ├─freshclamd.service
● ├─hdapsd.service
● ├─laptop-mode.service
● ├─lm_sensors.service
● ├─logrotate.timer
● ├─man-db.timer
● ├─NetworkManager.service
● ├─shadow.timer
● ├─syslog-ng.service
● ├─systemd-ask-password-wall.path
● ├─systemd-logind.service
● ├─systemd-user-sessions.service
● ├─tor.service
● ├─updatedb.timer
● ├─basic.target
● │ ├─alsa-restore.service
● │ ├─alsa-state.service
● │ ├─paths.target
● │ ├─slices.target
● │ │ ├─-.slice
● │ │ └─system.slice
● │ ├─sockets.target
● │ │ ├─acpid.socket
● │ │ ├─cups.socket
● │ │ ├─dbus.socket
● │ │ ├─dm-event.socket
● │ │ ├─saned.socket
● │ │ ├─systemd-initctl.socket
● │ │ ├─systemd-journald.socket
● │ │ ├─systemd-shutdownd.socket
● │ │ ├─systemd-udevd-control.socket
● │ │ └─systemd-udevd-kernel.socket
● │ ├─sysinit.target
● │ │ ├─dev-hugepages.mount
● │ │ ├─dev-mqueue.mount
● │ │ ├─kmod-static-nodes.service
● │ │ ├─proc-sys-fs-binfmt_misc.automount
● │ │ ├─sys-fs-fuse-connections.mount
● │ │ ├─sys-kernel-config.mount
● │ │ ├─sys-kernel-debug.mount
● │ │ ├─systemd-ask-password-console.path
● │ │ ├─systemd-binfmt.service
● │ │ ├─systemd-journal-flush.service
● │ │ ├─systemd-journald.service
● │ │ ├─systemd-modules-load.service
● │ │ ├─systemd-random-seed.service
● │ │ ├─systemd-sysctl.service
● │ │ ├─systemd-tmpfiles-setup-dev.service
● │ │ ├─systemd-tmpfiles-setup.service
● │ │ ├─systemd-udev-trigger.service
● │ │ ├─systemd-udevd.service
● │ │ ├─systemd-update-utmp.service
● │ │ ├─systemd-vconsole-setup.service
● │ │ ├─cryptsetup.target
● │ │ ├─local-fs.target
● │ │ │ ├─-.mount
● │ │ │ ├─boot.mount
● │ │ │ ├─home.mount
● │ │ │ ├─systemd-fsck-root.service
● │ │ │ ├─systemd-remount-fs.service
● │ │ │ ├─tmp.mount
● │ │ │ └─tmp.mount
● │ │ └─swap.target
● │ │ ├─dev-disk-by\x2did-ata\x2dHITACHI_HTS723216L9SA60_090507FC1223NPH0GY6D\x2dpart5.swap
● │ │ ├─dev-disk-by\x2did-wwn\x2d0x5000cca586ce4f98\x2dpart5.swap
● │ │ ├─dev-disk-by\x2dlabel-swap.swap
● │ │ ├─dev-disk-by\x2dlabel-swap.swap
● │ │ ├─dev-disk-by\x2dpartlabel-Linux\x5cx20swap.swap
● │ │ ├─dev-disk-by\x2dpartuuid-dee62d49\x2d0bc6\x2d466d\x2dac37\x2dc764dba9819c.swap
● │ │ ├─dev-disk-by\x2duuid-d04948bb\x2d804f\x2d4f94\x2dabc0\x2dd665e711193c.swap
● │ │ ├─dev-sda5.swap
● │ │ └─dev-sda5.swap
● │ └─timers.target
● │ └─systemd-tmpfiles-clean.timer
● ├─getty.target
● │ └─getty@tty1.service
● └─remote-fs.target
I'll have a look on systemd-analyze tomorrow on first boot!
Offline
ok, I found two processes that are missing on second boot that took a lot of time on the first..
1min 7.530s updatedb.service
56.069s man-db.service
You think kdm just times out because the system is too slow? These processes run in parallel, right? What could I do about that?
Offline
Yes I am pretty sure this is the problem.
The two services are controlled by a systemd timer and there are of 'Type=oneshot':
Behavior of oneshot is similar to simple; however, it is expected that the process has to exit before systemd starts follow-up units.
I have given a way to change the OnCalendar value of the timers at https://bbs.archlinux.org/viewtopic.php?id=180263
Offline
Ok, I took out the updatedb process as suggested in yout post which solved the problem. Still I think this is a structural problem in systemd. A process taking some time shouldn't result in a x-server timeout. Why is this process not marked 'Type=simple'?
Thanks a lot for your help!
Offline
Although your problem is marked solved, I thought I should mention a blog post by Martin Gräßlin the other day
Offline