Re: im-config | Use im-config on Wayland without uninstalling IBus (!5)
YOSHINO-san,
Can you take a look at proposed changes. I didn't have time to test it
for uim since I don't use it. What Gunnar stated sounds like major
change on the way environment variables are introduced. I am afraid
the impact of /etc/profile.d approach to uim. Also I am not sure how
many DE srart-up code read it. It's a new feature some primitive
startup mechanism such as xdm may not support.
https://salsa.debian.org/input-method-team/im-config
https://salsa.debian.org/input-method-team/im-config/-/commits/devel/
https://salsa.debian.org/input-method-team/im-config/-/merge_requests/6
On Sun, 2020-05-24 at 22:51 +0200, Gunnar Hjalmarsson wrote:
> On 2020-05-23 05:52, Osamu Aoki wrote:
> > Addressing wayland/systemd was a whole new game. I initially
> > thought
> > its task is beyond the design scope of im-config. Then YOSHINO-san
> > proposed new hook via systemd as
> > /usr/lib/systemd/user-environment-generators/70-im-config .
> >
> > 2bbb1a3 ("70-im-config: Export env variables via systemd",
> > 2019-03-
> > 07)
> >
> > This systemd.environment-generator(7) is invoked by `systemd --
> > user'
> > (>= 233) to export variables to its activation environment,
> > which is
> > used by gdm3 for environment variables in a new desktop
> > session.
> >
> > Unlike Xorg, Wayland does not use /etc/X11/Xsession.d/, where
> > im-
> > config has exported environment variables. This generator
> > should
> > compensate the lacking function for a Wayland desktop session
> > launched from gdm3.
> >
> > I didn't want to create a monster which I can't mauntain, YOSHINO-
> > san's
> > proposal seemed reasonably compact.
>
> Hmm.. I'd better mention that I dropped that and replaced it with a
> (very similar) hook in /etc/profile.d. The reason is that such a
> systemd
> generator is run very early at session startup when most environment
> variables (e.g. XDG_CURRENT_DESKTOP and XDG_SESSION_TYPE) have not
> yet
> been set.
>
Reply to: