Of course, once something does actually trigger the gdm job to run (with the exception of doing "start gdm" directly), that will still trigger command-line inhibition code originally described in this bug, so we would still need to do something about that.
Of course, once something does actually trigger the gdm job to run (with the exception of doing "start gdm" directly), that will still trigger command-line inhibition code originally described in this bug, so we would still need to do something about that.