In Fedora 34 beta candidate 1, the systemd debug-shell does not work. If you enable debug-shell.service and boot, on tty9 you don't get a root shell as you should, just a flashing cursor. In the journal you get this: -- Journal begins at Wed 2021-03-10 18:56:34 PST, ends at Wed 2021-03-10 19:05:16 PST. -- Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Main process exited, code=exited, status=208/STDIN Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Failed with result 'exit-code'. Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Scheduled restart job, restart counter is at 1. Mar 10 18:56:36 fedora systemd[1]: Stopped Early root shell on /dev/tty9 FOR DEBUGGING ONLY. Mar 10 18:56:36 fedora systemd[1]: Started Early root shell on /dev/tty9 FOR DEBUGGING ONLY. Mar 10 18:56:36 fedora systemd[508]: debug-shell.service: Failed to set up standard input: Permission denied Mar 10 18:56:36 fedora systemd[508]: debug-shell.service: Failed at step STDIN spawning /bin/sh: Permission denied Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Main process exited, code=exited, status=208/STDIN Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Failed with result 'exit-code'. Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Scheduled restart job, restart counter is at 2. Mar 10 18:56:36 fedora systemd[1]: Stopped Early root shell on /dev/tty9 FOR DEBUGGING ONLY. Mar 10 18:56:36 fedora systemd[1]: Started Early root shell on /dev/tty9 FOR DEBUGGING ONLY. Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Main process exited, code=exited, status=208/STDIN Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Failed with result 'exit-code'. Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Scheduled restart job, restart counter is at 3. Mar 10 18:56:36 fedora systemd[1]: Stopped Early root shell on /dev/tty9 FOR DEBUGGING ONLY. Mar 10 18:56:36 fedora systemd[1]: Started Early root shell on /dev/tty9 FOR DEBUGGING ONLY. Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Main process exited, code=exited, status=208/STDIN Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Failed with result 'exit-code'. Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Scheduled restart job, restart counter is at 4. Mar 10 18:56:36 fedora systemd[1]: Stopped Early root shell on /dev/tty9 FOR DEBUGGING ONLY. Mar 10 18:56:36 fedora systemd[1]: Started Early root shell on /dev/tty9 FOR DEBUGGING ONLY. Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Main process exited, code=exited, status=208/STDIN Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Failed with result 'exit-code'. Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Scheduled restart job, restart counter is at 5. Mar 10 18:56:36 fedora systemd[1]: Stopped Early root shell on /dev/tty9 FOR DEBUGGING ONLY. Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Start request repeated too quickly. Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Failed with result 'exit-code'. Mar 10 18:56:36 fedora systemd[1]: Failed to start Early root shell on /dev/tty9 FOR DEBUGGING ONLY. Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Start request repeated too quickly. Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Failed with result 'exit-code'. Mar 10 18:56:36 fedora systemd[1]: Failed to start Early root shell on /dev/tty9 FOR DEBUGGING ONLY. Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Start request repeated too quickly. Mar 10 18:56:36 fedora systemd[1]: debug-shell.service: Failed with result 'exit-code'. Mar 10 18:56:36 fedora systemd[1]: Failed to start Early root shell on /dev/tty9 FOR DEBUGGING ONLY. Mar 10 18:56:37 fedora systemd[1]: debug-shell.service: Start request repeated too quickly. Mar 10 18:56:37 fedora systemd[1]: debug-shell.service: Failed with result 'exit-code'. Mar 10 18:56:37 fedora systemd[1]: Failed to start Early root shell on /dev/tty9 FOR DEBUGGING ONLY. Proposing as a Beta FE as this may well be desired for debugging issues in live env or on first boot.
Oops.
Isn't this the same as #1933902?
oh, probably yes. I think I forgot about that one. Sorry! *** This bug has been marked as a duplicate of bug 1933902 ***