New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
src, client/x11: Add systemd unit file #2377
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the patch.
Please put "BUG=#2377" at the end of the git description.
I think this request would be a little late for Fedora 36 Change and it would be safe to target the integration to IBus 1.5.27 & Fedora 37 as this is a system wide change.
This so far depends on GNOME targets, and is thus just usable there. Other DEs wishing to use systemd and ibus will need to add the necessary dependencies where applicable. There are 2 scenarios here: - On X11 sessions, ibus-daemon will be launched with --xim parameter, so ibus-x11 is started with it. - On Wayland sessions, ibus-daemon will be started without XIM support, ibus-x11 will be launched and tear down together with all other session X11 services while Xwayland is running. For the second part of the second situation, additionally install a script at /etc/xdg/Xwayland-session.d, which takes care of X11 service initialization together with the Xwayland instance. BUG=ibus#2377
f162eaf
to
c137aad
Compare
This so far depends on GNOME targets, and is thus just usable there. Other DEs wishing to use systemd and ibus will need to add the necessary dependencies where applicable. There are 2 scenarios here: - On X11 sessions, ibus-daemon will be launched with --xim parameter, so ibus-x11 is started with it. - On Wayland sessions, ibus-daemon will be started without XIM support, ibus-x11 will be launched and tear down together with all other session X11 services while Xwayland is running. For the second part of the second situation, additionally install a script at /etc/xdg/Xwayland-session.d, which takes care of X11 service initialization together with the Xwayland instance. BUG=ibus#2377
c137aad
to
49c2d7d
Compare
This so far depends on GNOME targets, and is thus just usable there. Other DEs wishing to use systemd and ibus will need to add the necessary dependencies where applicable. There are 2 scenarios here: - On X11 sessions, ibus-daemon will be launched with --xim parameter, so ibus-x11 is started with it. - On Wayland sessions, ibus-daemon will be started without XIM support, ibus-x11 will be launched and tear down together with all other session X11 services while Xwayland is running. For the second part of the second situation, additionally install a script at /etc/xdg/Xwayland-session.d, which takes care of X11 service initialization together with the Xwayland instance. BUG=ibus#2377
49c2d7d
to
149d64c
Compare
This so far depends on GNOME targets, and is thus just usable there. Other DEs wishing to use systemd and ibus will need to add the necessary dependencies where applicable. There are 2 scenarios here: - On X11 sessions, ibus-daemon will be launched with --xim parameter, so ibus-x11 is started with it. - On Wayland sessions, ibus-daemon will be started without XIM support, ibus-x11 will be launched and tear down together with all other session X11 services while Xwayland is running. For the second part of the second situation, additionally install a script at /etc/xdg/Xwayland-session.d, which takes care of X11 service initialization together with the Xwayland instance. BUG=ibus#2377
149d64c
to
053842e
Compare
This so far depends on GNOME targets, and is thus just usable there. Other DEs wishing to use systemd and ibus will need to add the necessary dependencies where applicable. There are 2 scenarios here: - On X11 sessions, ibus-daemon will be launched with --xim parameter, so ibus-x11 is started with it. - On Wayland sessions, ibus-daemon will be started without XIM support, ibus-x11 will be launched and tear down together with all other session X11 services while Xwayland is running. For the second part of the second situation, additionally install a script at /etc/xdg/Xwayland-session.d, which takes care of X11 service initialization together with the Xwayland instance. BUG=ibus#2377
053842e
to
4008e9e
Compare
This so far depends on GNOME targets, and is thus just usable there. Other DEs wishing to use systemd and ibus will need to add the necessary dependencies where applicable. There are 2 scenarios here: - On X11 sessions, ibus-daemon will be launched with --xim parameter, so ibus-x11 is started with it. - On Wayland sessions, ibus-daemon will be started without XIM support, ibus-x11 will be launched and tear down together with all other session X11 services while Xwayland is running. For the second part of the second situation, additionally install a script at /etc/xdg/Xwayland-session.d, which takes care of X11 service initialization together with the Xwayland instance. BUG=ibus#2377
4008e9e
to
a076b38
Compare
the first one is separating ibus-daemon and ibus-x11 startup logic, GNOME Shell on Wayland has capabilities to start/stop Xwayland dynamically on presence of X11 clients, ibus-x11 should follow that And the second reason is https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2235, we are going to raise the file descriptor limit in GNOME Shell/Xwayland, but wouldn't want to have it propagated to other processes |
FTR, this is the service running locally on my jhbuild setup on a GNOME Wayland session:
|
IBus is moving to being a systemd managed service in GNOME sessions (see ibus/ibus#2377). Since there will be a transition period, and we still have to support non-systemd sessions, check for this existence at runtime.
IBus is moving to being a systemd managed service in GNOME sessions (see ibus/ibus#2377). Since there will be a transition period, and we still have to support non-systemd sessions, check for this existence at runtime.
The related merge request in GNOME Shell is https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2171 |
Thank you very much for your patch. |
IBus is moving to being a systemd managed service in GNOME sessions (see ibus/ibus#2377). Since there will be a transition period, and we still have to support non-systemd sessions, check for this existence at runtime.
IBus is moving to being a systemd managed service in GNOME sessions (see ibus/ibus#2377). Since there will be a transition period, and we still have to support non-systemd sessions, check for this existence at runtime.
IBus is moving to being a systemd managed service in GNOME sessions (see ibus/ibus#2377). Since there will be a transition period, and we still have to support non-systemd sessions, check for this existence at runtime. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2171>
This so far depends on GNOME targets, and is thus just usable there.
Other DEs wishing to use systemd and ibus will need to add the
necessary dependencies where applicable.
There are 2 scenarios here:
so ibus-x11 is started with it.
ibus-x11 will be launched and tear down together with all other
session X11 services while Xwayland is running.
For the second part of the second situation, additionally install
a script at /etc/xdg/Xwayland-session.d, which takes care of X11
service initialization together with the Xwayland instance.