control: reassign -1 kdm control: forcemerge 755359 -1 Am 28.11.2014 um 06:16 schrieb Michael Biebl: > Am 28.11.2014 um 06:10 schrieb Michael Biebl: >> Am 27.11.2014 um 13:39 schrieb Marc Haber: >>> Package: systemd >>> Severity: normal >>> >>> Hi, >>> >>> I have a current sid system which has been updated to current sid from >>> May's sid in a big update run and has gotten systemd in the process. >>> >>> Unfortunately, it dies when X is started. >>> >>> To debug this issue, I'd like to have a possibility to stop X from >>> being started. >>> >>> Since I cannot just dump "exit 0" into an init script any more, I need >>> a way to stop system startup at the multi-user stage before X is >>> started. >>> >>> >From the upstream docs, it looks like passing >>> "systemd.unit=multi-user.target" on the kernel command line should do >>> that: "A special target unit for setting up a multi-user system >>> (non-graphical). This is pulled in by graphical.target." >>> >>> Unfortunately, my system seems to start up X nevertheless. >>> >> >> >> Which display manager do you use? >> It's most likely, that your display manager does not yet support the new >> display manager scheme [1], i.e. doesn't set up >> /etc/systemd/system/display-manager.service correctly and instead still >> installs a SysV init script with a start symlink in /etc/rc?.d/, which >> is mapped to multi-user.target. >> >> If you use lightdm or gdm3, which both support the new scheme already, >> booting into multi-user.target should not start the display manager. >> >> [1] http://fedoraproject.org/wiki/Features/DisplayManagerRework > > > Say you use kdm, which doesn't ship a native service file yet and > doesn't yet support the new scheme, you could try a different approach: > Add systemd.mask=kdm.service to the kernel command line > > This will runtime mask the service and prohibit it's start. > > Btw, when you boot with systemd.unit=multi-user.target, what is the > output of > systemctl status graphical.target multi-user.target > > My gut feeling is, that it's actually a bug in the actual display > manager and should be re-assigned accordingly. >
This needs to be solved by display-manager providing a proper service file and setting up the display-manager.service symlink as outlined in the wiki. From the systemctl dump, you seem to be using kdm, therefore re-assigning and merging with the existing bug report. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
