On Tue, Aug 12, 2014 at 01:08:39AM +0200, Michael Biebl wrote: > Am 12.08.2014 00:31, schrieb Jaroslav Mikulík: > > Package: systemd > > Version: 208-6 > > Severity: normal > > > > Dear Maintainer, > > > > > > * What led up to the situation? > > > > After recent upgrade to systemd, kdm on my machine don't start (4 core CPU). > > Strange that on older machine (1 core CPU) is kdm started OK. > > > > * What exactly did you do (or not do) that was effective (or > > ineffective)? > > > > In kdm.log I found this error: > > > > klauncher(1841) kdemain: No DBUS session-bus found. Check if you have > > started > > the DBUS server. > > kdeinit4: Communication error with launcher. Exiting! > > kdmgreet(1780)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned > > initialize() > > D-Bus call failed: "Not connected to D-Bus server" > > > > When KDM is started on manualy after boot, then it started OK. > > > > > Please remove the workaround from /etc/rc.local. > Then boot adding the following to the kernel command line: > systemd.log_level=debug > After that, attach the "journalctl -alb" to this bug report.
I had the same problem with kdm (or at least very similar, don't remember the exact error message). I made a native systemd unit file which fixes the problem for me. Jaroslav, if you want to try it, it's at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754314 (unfortunately w/o any feedback from KDE maintainers since 5 weeks) Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org