Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

systemd.crash_shell runs in tandem with serial-getty@ttyS0 causing issues #32537

Open
DaanDeMeyer opened this issue Apr 28, 2024 · 0 comments
Open
Labels
bug 🐛 Programming errors, that need preferential fixing pid1

Comments

@DaanDeMeyer
Copy link
Contributor

systemd version the issue has been seen with

main

Used distribution

Fedora 39

Linux kernel version used

No response

CPU architectures issue was seen on

None

Component

No response

Expected behaviour you didn't see

When PID 1 crashes and systemd.crash_shell is enabled, the spawned terminal takes control of the /dev/console TTY.

Unexpected behaviour you saw

When PID 1 crashes and systemd.crash_shell is enabled, both the spawned crash shell and serial-getty@ttyS0 are reading from /dev/console, leading to an unusable terminal as both try to read from it when characters are entered.

Steps to reproduce the problem

mkosi -f qemu
kill -s ABRT 1

Additional program output to the terminal or log subsystem illustrating the issue

No response

@DaanDeMeyer DaanDeMeyer added the bug 🐛 Programming errors, that need preferential fixing label Apr 28, 2024
@YHNdnzj YHNdnzj added the pid1 label Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Programming errors, that need preferential fixing pid1
Development

No branches or pull requests

2 participants