Bug 2175871 - [regression] ibus orphaned when xdmcp session force closed
Summary: [regression] ibus orphaned when xdmcp session force closed
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ibus
Version: 7.9
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: fujiwara
QA Contact: Sanket Saikia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-06 16:53 UTC by Joe Wright
Modified: 2023-08-17 08:26 UTC (History)
11 users (show)

Fixed In Version: ibus-1.5.17-13.el7_9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-150845 0 None None None 2023-03-06 16:57:02 UTC

Comment 5 fujiwara 2023-03-28 12:02:37 UTC 
I cannot reproduce your issue.

To enable XDMCP, I think you enable GDM login screen at console and a process of ibus-daemon is running owned by gdm user.

Xephyr process shows GDM login screen remotely and it runs another ibus-daemon is running owned by gdm user.
Both the GDM login screen and ibus-daemon is terminated with the timeout.

If I log into the GNOME session via GDM login screen, ibus-daemon runs owned by the session user but the both the session and ibus-daemon is terminated with the timeout.
Note You need to log in before you can comment on or make changes to this bug.