Bug#778362: Periodic (90s) restart of KDM by systemd on jessie
Jedd Rashbrooke
jedd.rashbrooke at gmail.com
Sat Feb 14 07:46:47 GMT 2015
> You should consider removing the console-kit-daemon package.
> It's not really useful anymore nowadays.
I have now removed the consolekit package - thanks for the suggestion.
I noted that it resulted in the removal of the mdadm package (along
with a bunch of init.d/*mdadm scripts) even though that wasn't listed
as a dependency. I'm using apt-get with -u, so actions involving
other packages tend to stand out. I'm not using any mdadm volumes, so
no biggy, but I did note before when trawling around systemadm GUI
that mdadm.service and mdadm-raid.service were highlighted in red on
the 'graphical.target', but so were acpi-support-service,
sysstat.service, and nvidia-kernel.service, and those three still are.
> That's a bug in the kdm.service unit resp. kdm. It never signals
> systemd, that it started successfully. Most likely, this is due to the
> use of the wrong Type= in kdm.service.
>
> Curious though, the kdm package in Debian doesn't ship
> /lib/systemd/system/kdm.service. Where is this file coming from? Have
> you created/installed that on your own?
Ah, yes, I think I got that suggestion from bug #755359, and failed
to mention it in the original report. Apologies for that oversight.
After removing consolekit, I removed /lib/systemd/system/kdm.service
file AND the symlink that had been recommended
(/etc/systemd/system/display-manager.service ->
/lib/systemd/system/display-manager.service )
As an aside, the contents of the kdm.service file I'd used follows:
[Unit]
Description=KDE Display Manager
Documentation=man:kdm(1)
After=systemd-user-sessions.service
[Service]
ExecStartPre=/bin/sh -c '[ "$(cat /etc/X11/default-display-manager
2>/dev/null)" = "/usr/bin/kdm" ]'
# ExecStart=/usr/bin/kdm -debug 0x08F vt1
Type=forking
ExecStart=/usr/bin/kdm
Restart=always
BusName=org.freedesktop.DisplayManager
I then restarted the laptop, and KDM starts normally, and then stays
up properly. So, this problem is fixed, but I'm still a smidge
bewildered, as I put that kdm.service file in place, and the symlink,
after following some other suggestions to fix the problem that was
occurring *before* I made those changes. Oh well.
Thanks again!
More information about the Pkg-systemd-maintainers
mailing list