Bug 1398797

Summary: Keyboard compose key broken after second Gnome login
Product: [Fedora] Fedora Reporter: Deron Meranda <deron.meranda>
Component: gnome-sessionAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 25CC: jmccann, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:17:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
The user session control groups after the second gnome login
none
The user session control groups after terminating session 21
none
The /etc/systemd/logid.conf file which should be the Fedora default none

Description Deron Meranda 2016-11-26 06:05:11 UTC 
Description of problem:
If I login to Gnome and then logout, and then login a second time the keyboard compose key mechanism does not work for some applications.  This happens regardless of whether I use X11 or Wayland sessions.

I have no idea which component causes this, and it may be multiple components interacting together, so this bug report may need reclassified.

Version-Release number of selected component (if applicable):
Fedora 25 as of Nov 25, 2016

How reproducible:
Always in Fedora 25
Never in Fedora 24

Steps to Reproduce:
1. Login as a standard user graphically using Gnome.
2. Logout (use the gnome logout menu from the upper-right status bar)
3. Login again as that same user.
4. Open one of the applications that is affected.  I know that both emacs and "git gui" are, but there may be many more.
5. Start typing into the application and attempt to use the compose key functionality.  For example holding down the compose key (Right-Alt for me but can be changed from gnome tweak-tool) and then type the hyphen key three times in a row the application receives three independent hyphen characters rather than a single em-dash character.

Actual results:
The first time you login the compose key sends the correct character to the application.  The second time you login each keystroke is sent as a separate character rather than being composed.

Note that the compose key will still work for some applications though; such as gnome-terminal or libreoffice writer.  I don't know what makes the broken ones different from the apps that still work.

Expected results:
The composed character should always be sent to the application.

Additional info:
I noticed that when I log out of the Gnome session that the systemd control group for that session is not entirely terminated.  There are a handful of processes that are still running.  When logging in a second time a new control group is created; but for the same user and same seat.  If I terminate the previous control group (using loginctl) then the compose key will start working again across all applications (though the applications themselves need to be restarted).
Comment 1 Deron Meranda 2016-11-26 06:18:08 UTC 
Created attachment 1224510 [details]
The user session control groups after the second gnome login

This is the output of "loginctl user-status 1000" after the second gnome
login.  This is using an X11 session.  The bug still occurs when
using Wayland, though the set of processes is somewhat different.

Note there are three sessions:

session-19 - This is a non-graphical ssh/tty session used for debugging, ignore.
session-21 - This is the first graphical login, AFTER a logout had been performed.
session-22 - This is the second graphical login.

When in this state the compose key fails to work in certain applications.
Comment 2 Deron Meranda 2016-11-26 06:20:49 UTC 
Created attachment 1224511 [details]
The user session control groups after terminating session 21

This is again the output of "loginctl user-status 1000" after the previous session (21) was forcibly terminated with "loginctl terminate-session 21".

In this state the keyboard compose key starts working correctly again, after the affected applications are restarted.  There is no need to log out of the second session.

Note that the "ibus-daemon" and it's related processes, which used to be running in the old session-21 have now been relaunched and are running in session-22 (the current session).
Comment 3 Deron Meranda 2016-11-26 06:24:12 UTC 
Created attachment 1224512 [details]
The /etc/systemd/logid.conf file which should be the Fedora default

When logging out of a Gnome session some processes in the control group are left running.  I don't know if this is supposed to happen or not.  In any case here's the systemd logind.conf file; which is unmodified and should be at the Fedora 25 factory default.
Comment 4 Fedora End Of Life 2017-11-16 19:30:29 UTC 
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 5 Fedora End Of Life 2017-12-12 10:17:01 UTC 
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.