Install 'sddm.service' in 'graphical.target'. #340

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
3 participants
Contributor

eliasp commented Jan 14, 2015

sddm didn't start for me anymore on bootup - the explanation was actually rather straight-forward.
I wonder how we missed this so far ;)

Owner

plfiorini commented Jan 14, 2015

Weird... :-/

@plfiorini plfiorini self-assigned this Jan 14, 2015

Owner

plfiorini commented Jan 14, 2015

Here's a possible explaination why it was working before: graphical.target already requires display-manager.service so if you had set graphical.target to be the default target and sddm.service was enabled then sddm could start.
I don't know what's changed in systemd. Since when and which systemd version do you have this problem?

Contributor

eliasp commented Jan 14, 2015

@plfiorini Running systemd from git and update usually once or twice a day.
I think I had this problem since around 2.5 weeks, but can't tell definitely.

Will have a look whether I can identify a systemd commit responsible for this.

Contributor

eliasp commented Jan 14, 2015

Most likely caused by:
8fa844dccff70824ff063bfe5f409c47f5699d73 - units: make graphical.target dependencies more complete and similar to those of multi-user.target

Owner

plfiorini commented Jan 14, 2015

That commit could be the one causing the problem.
I don't expect your patch to cause issues with older systemd versions but I would like to test it just in case...

Member

jleclanche commented Jan 14, 2015

Hold.

Owner

plfiorini commented Jan 14, 2015

Jerome asked Lennart in person over IRC.
Could be a systemd regression but he needs more information.

poettering: after 8fa844d, is such an issue expected by you guys on DMs that don't have WantedBy=graphical.target? #340
jleclanche: hmm, i wouldn't expect any difference in behaviour...
poettering: Do you think it's a systemd regression or are DMs expected to have WantedBy=graphical.target?
jleclanche: they are not expected to have that
jleclanche: and yeah, it could be a systemd regression, but the info on the link doesn't explain too much...
poettering: this isn't my system unfortunately, but what other info do you need? I can probably get it
jleclanche: well, dunno, logs when booted with systemd.log_level=debug would be good...

Contributor

eliasp commented Jan 14, 2015

Will provide logs with systemd.log_level=debug later today. Can't reboot this system right now.

Owner

plfiorini commented Jan 31, 2015

@eliasp ping :)

Owner

plfiorini commented Mar 31, 2015

Should we close this?

Member

jleclanche commented Mar 31, 2015

Well we still need to figure out the situation i think... but we won't be fixing anything on our side.

@jleclanche jleclanche closed this Mar 31, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment