FS#65799 - [ibus] Client can't establish a connection with daemon
Attached to Project:
Arch Linux
Opened by Heiher (heiher) - Thursday, 12 March 2020, 02:36 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:16 GMT
Opened by Heiher (heiher) - Thursday, 12 March 2020, 02:36 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:16 GMT
|
Details
Description:
From: https://github.com/ibus/ibus/pull/2195 In Wayland sessions, GNOME Shell 3.36 is leveraging 2 X11 Display connections so one is used to set up all services for a "X11 session" before user applications connected to the other display might require it. This allows seamlessly starting Xwayland on demand to X11 user applications. IBus here belongs to the first described connection, it is started explicitly on that display by GNOME Shell as it is necessary to set up ibus-x11 before any other X11 client might want to use it. However the use of this "secondary" display results in IBus daemon left unable to talk to applications, as the socket name is dependent on the DISPLAY envvar and ibus/applications don't agree on its content. For wayland sessions, make it look for WAYLAND_DISPLAY, as that'll have the similar "per session bus" behavior that this seems to look after. Related: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2341 |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:16 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/ibus/issues/2
Saturday, 25 November 2023, 20:16 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/ibus/issues/2
Comment by
Buggy McBugFace (bugbot) - Tuesday,
08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2
years. Please reply if you still experience this bug otherwise
this issue will be closed after 1 month.