Why does SaK kill gdm, which is running on a different VT?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I run Fedora Linux 28, and have enabled sysrq. I pressed Alt+PrtScr+K, to kill a non-responsive X session. But this also restarted gdm
, and one other X session, which were running on different VTs. Why?
linux gdm magic-sysrq
add a comment |Â
up vote
0
down vote
favorite
I run Fedora Linux 28, and have enabled sysrq. I pressed Alt+PrtScr+K, to kill a non-responsive X session. But this also restarted gdm
, and one other X session, which were running on different VTs. Why?
linux gdm magic-sysrq
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I run Fedora Linux 28, and have enabled sysrq. I pressed Alt+PrtScr+K, to kill a non-responsive X session. But this also restarted gdm
, and one other X session, which were running on different VTs. Why?
linux gdm magic-sysrq
I run Fedora Linux 28, and have enabled sysrq. I pressed Alt+PrtScr+K, to kill a non-responsive X session. But this also restarted gdm
, and one other X session, which were running on different VTs. Why?
linux gdm magic-sysrq
asked Jun 21 at 15:48
sourcejedi
18.1k22375
18.1k22375
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Linux SaK kills all processes which have the current tty open.
See https://elixir.bootlin.com/linux/v4.17/source/drivers/tty/tty_io.c#L2700
systemd-logind appears to open all active ttys.
You can verify this using
lsof
.- When X is run as an unprivileged user and relies on systemd-logind, it does not handle a restart of systemd-logind. When X loses its connection to systemd-logind, it terminates itself.
Alternative
So SaK can indirectly affect all VTs, if you use unprivileged X, or Wayland.
Instead, you can use Alt+PrtScr+R, then Ctrl+Alt+F6. You can log in on the text console, and manually kill processes e.g. Xorg
, or gnome-shell
if you use a GNOME Wayland session).
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Linux SaK kills all processes which have the current tty open.
See https://elixir.bootlin.com/linux/v4.17/source/drivers/tty/tty_io.c#L2700
systemd-logind appears to open all active ttys.
You can verify this using
lsof
.- When X is run as an unprivileged user and relies on systemd-logind, it does not handle a restart of systemd-logind. When X loses its connection to systemd-logind, it terminates itself.
Alternative
So SaK can indirectly affect all VTs, if you use unprivileged X, or Wayland.
Instead, you can use Alt+PrtScr+R, then Ctrl+Alt+F6. You can log in on the text console, and manually kill processes e.g. Xorg
, or gnome-shell
if you use a GNOME Wayland session).
add a comment |Â
up vote
1
down vote
accepted
Linux SaK kills all processes which have the current tty open.
See https://elixir.bootlin.com/linux/v4.17/source/drivers/tty/tty_io.c#L2700
systemd-logind appears to open all active ttys.
You can verify this using
lsof
.- When X is run as an unprivileged user and relies on systemd-logind, it does not handle a restart of systemd-logind. When X loses its connection to systemd-logind, it terminates itself.
Alternative
So SaK can indirectly affect all VTs, if you use unprivileged X, or Wayland.
Instead, you can use Alt+PrtScr+R, then Ctrl+Alt+F6. You can log in on the text console, and manually kill processes e.g. Xorg
, or gnome-shell
if you use a GNOME Wayland session).
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Linux SaK kills all processes which have the current tty open.
See https://elixir.bootlin.com/linux/v4.17/source/drivers/tty/tty_io.c#L2700
systemd-logind appears to open all active ttys.
You can verify this using
lsof
.- When X is run as an unprivileged user and relies on systemd-logind, it does not handle a restart of systemd-logind. When X loses its connection to systemd-logind, it terminates itself.
Alternative
So SaK can indirectly affect all VTs, if you use unprivileged X, or Wayland.
Instead, you can use Alt+PrtScr+R, then Ctrl+Alt+F6. You can log in on the text console, and manually kill processes e.g. Xorg
, or gnome-shell
if you use a GNOME Wayland session).
Linux SaK kills all processes which have the current tty open.
See https://elixir.bootlin.com/linux/v4.17/source/drivers/tty/tty_io.c#L2700
systemd-logind appears to open all active ttys.
You can verify this using
lsof
.- When X is run as an unprivileged user and relies on systemd-logind, it does not handle a restart of systemd-logind. When X loses its connection to systemd-logind, it terminates itself.
Alternative
So SaK can indirectly affect all VTs, if you use unprivileged X, or Wayland.
Instead, you can use Alt+PrtScr+R, then Ctrl+Alt+F6. You can log in on the text console, and manually kill processes e.g. Xorg
, or gnome-shell
if you use a GNOME Wayland session).
edited Jun 21 at 15:54
answered Jun 21 at 15:48
sourcejedi
18.1k22375
18.1k22375
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f451136%2fwhy-does-sak-kill-gdm-which-is-running-on-a-different-vt%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password