[Bug 1594681] Re: Don't override IM variables
Launchpad Bug Tracker
1594681 at bugs.launchpad.net
Thu Aug 18 20:02:38 UTC 2016
** Branch linked: lp:~ubuntu-desktop/gnome-session/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1594681
Title:
Don't override IM variables
Status in gnome-session:
Confirmed
Status in Ubuntu GNOME:
New
Status in gnome-session package in Ubuntu:
In Progress
Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Status in gnome-session source package in Xenial:
In Progress
Status in gnome-settings-daemon source package in Xenial:
In Progress
Bug description:
[Impact]
Currently these variable settings are hardcoded in gnome-session and
gnome-settings-daemon:
QT_IM_MODULE=ibus
XMODIFIERS=@im=ibus
That way the use of alternative IM frameworks, for instance fcitx, is
prevented. The variables should only be set if they are empty, so the
values set by im-config are honored.
[Test Case]
* Install Ubuntu GNOME
* Install both the gnome-session and gnome-settings-daemon proposed updates
* Install fcitx
* Set fcitx as the input method:
im-config -n fcitx
* Relogin
* Check the IM-related environment variables:
env | grep -E '_IM|XMOD'
After the proposed uploads of gnome-session and gnome-settings-daemon,
those variables are consistently (unlike before) set to "fcitx".
[Regression Potential]
Low. im-config sets "ibus" by default in Ubuntu GNOME anyway. This
change prevents an inconsistent input method configuration for users
who have actively chosen some other IM framework.
The gnome-settings-daemon change was included upstream in 3.19.3 and
the gnome-session change was included upstream in 3.21.90.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1594681/+subscriptions
More information about the Ubuntu-sponsors
mailing list