[SOLVED] kdm doesn't start automatically

grzs · 2013-03-04 13:19:02

Hello for all,

I am struggling with this problem for a while. It started after I migrated to systemd.

I enabled the kdm service but I can start it manually only with "systemctl start kdm".

I couldn't find any error messages. Maybe it's related to dbus.

The other issue what came out after the migration is that nepomuk also refuses to start.

I tried to reinstall, nothing changed.
I updated the whole system today.

Any suggestions?

Thanks

Last edited by grzs (2013-03-07 13:27:53)

nuc · 2013-03-04 13:39:29

systemctl enable kdm.service

grzs · 2013-03-04 13:45:05

it's enabled already

nuc · 2013-03-04 13:51:12

Check

# systemctl status kdm.service

before you start it manually. There should be some error message. Please paste the output.

Last edited by nuc (2013-03-04 13:52:17)

grzs · 2013-03-04 14:28:14

Here is the output after reboot:

kdm.service - K Display Manager
	  Loaded: loaded (/usr/lib/systemd/system/kdm.service; enabled)
	  Active: inactive (dead)

márc 04 13:13:25 phoenix systemd[1]: Starting K Display Manager...
márc 04 13:13:25 phoenix systemd[1]: Started K Display Manager.
márc 04 13:13:42 phoenix kdm[496]: :0[496]: pam_unix(kde:session): session opened for user grzs by (uid=0)
márc 04 13:47:22 phoenix kdm[2036]: :0[2036]: pam_unix(kde:session): session opened for user grzs by (uid=0)
márc 04 14:34:32 phoenix systemd[1]: Stopping K Display Manager...
márc 04 14:34:33 phoenix systemd[1]: Starting K Display Manager...
márc 04 14:34:33 phoenix systemd[1]: Started K Display Manager.
márc 04 14:34:33 phoenix kdm[3315]: :0[3315]: pam_unix(kde-np:session): session opened for user grzs by (uid=0)
márc 04 15:15:13 phoenix systemd[1]: Stopping K Display Manager...
márc 04 15:15:13 phoenix systemd[1]: Stopped K Display Manager.

...and after starting kdm manually:

kdm.service - K Display Manager
	  Loaded: loaded (/usr/lib/systemd/system/kdm.service; enabled)
	  Active: active (running) since h 2013-03-04 15:19:12 CET; 3min 16s ago
	Main PID: 643 (kdm)
	  CGroup: name=systemd:/system/kdm.service
		  ├─643 /usr/bin/kdm -nodaemon
		  └─645 /usr/bin/X :0 vt7 -nolisten tcp -auth /var/run/xauth/...

márc 04 15:19:12 phoenix systemd[1]: Started K Display Manager.
márc 04 15:19:14 phoenix kdm[651]: :0[651]: pam_unix(kde-np:session): session opened for user grzs by (uid=0)

grzs · 2013-03-05 10:30:03

bump

cfr · 2013-03-05 23:22:56

Please don't bump your posts - it is against the forum rules.

In all likelihood, nobody has suggested anything because you have not provided enough information. What steps have you tried to resolve this? What have you found in the journal or log files?

grzs · 2013-03-05 23:47:51

I am sorry, I didn't know that bumping is not allowed.

My problem is that I don't have a clue. I don't know enough about systemd. I tested the service with "systemctl start kdm" and when I noted that it's okay I enabled it with "systemctl enable kdm". After that I expected that after reboot it will start automatically but it's dead as you could see the output of "systemctl status kdm" I posted before.

I have checked journalctl, errors.log, kdm.log, messages.log, etc but found nothing!

I would be happy with few advises what I could start to work on. I read somewhere that it happened to someone that after sysupgrade the connection between dbus and kde damaged somehow (sorry, I don't know how dbus works). I don't know exactly why but I feel something around this (it's suspicious).

Thank you in advance.

cfr · 2013-03-06 02:04:44

What happens exactly? According to the times in that list, KDM is up for about 3/4 hour and then stops. Does it work initially?

You can use systemctl status to check what is happening with dbus. journalctl -b | grep <whatever> may give you additional information.

grzs · 2013-03-07 13:21:06

I don't know what happened behind the scenes but I removed default.target in /etc/systemd/system and kdm starts without problem.

Thanks for all.

berbae · 2013-03-07 16:10:18

default.target is just a link to either /usr/lib/systemd/system/multi-user.target or /usr/lib/systemd/system/graphical.target or another target.
It should do no harm and is probably not the cause of the problem.

graphical.target wants display-manager.service which is an alias for kdm.service if it is enabled.

cfr · 2013-03-07 22:51:00

Well, if it was linked to multi-user it would stop kdm starting...

Arch Linux

#1 2013-03-04 13:19:02

[SOLVED] kdm doesn't start automatically

#2 2013-03-04 13:39:29

Re: [SOLVED] kdm doesn't start automatically

#3 2013-03-04 13:45:05

Re: [SOLVED] kdm doesn't start automatically

#4 2013-03-04 13:51:12

Re: [SOLVED] kdm doesn't start automatically

#5 2013-03-04 14:28:14

Re: [SOLVED] kdm doesn't start automatically

#6 2013-03-05 10:30:03

Re: [SOLVED] kdm doesn't start automatically

#7 2013-03-05 23:22:56

Re: [SOLVED] kdm doesn't start automatically

#8 2013-03-05 23:47:51

Re: [SOLVED] kdm doesn't start automatically

#9 2013-03-06 02:04:44

Re: [SOLVED] kdm doesn't start automatically

#10 2013-03-07 13:21:06

Re: [SOLVED] kdm doesn't start automatically

#11 2013-03-07 16:10:18

Re: [SOLVED] kdm doesn't start automatically

#12 2013-03-07 22:51:00

Re: [SOLVED] kdm doesn't start automatically

Board footer