Bug 2249991

Summary: systemctl daemon-reexec changes keyboard mode, crashes GNOME session
Product: [Fedora] Fedora Reporter: Marek Marczykowski-Górecki <marmarek>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 37CC: dtardon, fedoraproject, filbranden, lnykryn, msekleta, ryncsn, systemd-maint, yuwatana, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://github.com/systemd/systemd/issues/30046
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-20 14:35:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marek Marczykowski-Górecki 2023-11-16 10:38:24 UTC
After systemd re-exec (done by glibc rpm update for example), keyboard is reset to unicode (I think?) mode. Especially, key combos like alt+f2 or ctrl+c are no longer handled by Xorg/Wayland session and behave as the system was on the text console. Specifically:

    alt+f2 switches to tty2 (that should require alt+ctrl+f2)
    ctrl+c kills the whole Xorg or Wayland session (confirmed on both)

There are likely other key combos that misbehave.

Starting Xorg/Wayland again fixes the issue.

Reproducible: Always

Steps to Reproduce:
1. Have a graphical session active
2. Call sudo systemctl daemon-reexec
3. Press ctrl+c
Actual Results:  
GNOME (or any other) session killed

Expected Results:  
Session not killed.


The issue is fixed upstream already (https://github.com/systemd/systemd/commit/4f44d2c4f76922a4f48dd4473e6abaca40d7e555) and the fix is backported to 251 (https://github.com/systemd/systemd-stable/commit/8c741666fa49a8c87910e2da7832dcf1f414e286). It's just a matter of updating systemd package in Fedora 37.

Comment 1 David Tardon 2023-11-20 14:35:46 UTC

*** This bug has been marked as a duplicate of bug 2242219 ***