There is a minor bug in the stop()-section of the xdm init script, that produces an error message when rebooting the system complaining about not being able to stop the gdm service (maybe xdm/kdm/others too, but I haven't checked). In my case gdm apparently is already gone when the script checks for the process and thus passes 1 to eend, which results in the error message described above. The whole purpose of the stop()-section is to kill the gdm process. Therefore I think it's safe to assume that the service has been stopped if the process doesn't even exist (this does not affect the behaviour of the script if it encounters any problems stopping an existing gdm process). The trivial patch to fix this issue: --- /etc/init.d/xdm.old 2005-05-24 17:46:22.000000000 +0200 +++ /etc/init.d/xdm 2005-05-24 17:30:20.000000000 +0200 @@ -106,7 +106,7 @@ retval=$? else - retval=1 + retval=0 fi #switch back to original vt Reproducible: Always Steps to Reproduce: 1. Reboot/Shutdown Actual Results: The xdm-script complains about not being able to stop gdm (although it is already gone, hence stopped). Expected Results: No error messages.
Remember to search for duplicates. *** This bug has been marked as a duplicate of 24399 ***
(In reply to comment #1) > Remember to search for duplicates. I did, but apparently with wrong keywords. Sorry about that.
