[Fedora-i18n-bugs] [Bug 917130] [pt_BR] Keyboard loses dead keys on login
by Red Hat Bugzilla
Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=917130
--- Comment #15 from Akira TAGOH <tagoh(a)redhat.com> ---
(In reply to comment #13)
> (In reply to comment #11)
> > Just after login, with the bug present, the output is:
> >
> > [teste@localhost ~]$ gsettings get org.gnome.desktop.interface gtk-im-module
> > 'xim:xim'
>
> This shouldn't ever happen in gnome and g-s-d certainly makes sure to set it
> to either 'gtk-im-context-simple' or 'ibus'. Not sure what's going on here.
> Is this a regular gnome session?
This is because xcompose.conf doesn't restrict applying it on even GNOME3.
weird thing would be rather it gives different behavior compared to xterm say.
it is supposed to behave same.
How about explicitly set GTK_IM_MODULE=xim and run applications? if it works
too and behave same with xterm, it's not what I should fix in imsettings.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=WFcoKC3H7O&a=cc_unsubscribe
11 years, 1 month
[Fedora-i18n-bugs] [Bug 887951] New: All input method framework except ibus can not autostart via imsettings in gnome-shell
by Red Hat Bugzilla
Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=887951
Bug ID: 887951
Summary: All input method framework except ibus can not
autostart via imsettings in gnome-shell
Product: Fedora
Version: 18
Component: imsettings
Severity: unspecified
Priority: unspecified
Reporter: liangsuilong(a)gmail.com
Description of problem:
GNOME 3.6 integrated ibus as default input method. But imsettings in Fedora
does not start automatically after you log in gnome-shell session. It means
that you can not use other input method except ibus by default when you are
using gnome-shell.
Version-Release number of selected component (if applicable):
imsettings-1.5.0-2.fc18.x86_64
How reproducible:
1. Install fcitx, scim or gcin.
2. Turn off ibus integratiion via gsettings
3. Set other input method like fcitx or scim as default via imsettings-switch.
4. Log out or reboot the machine
5. Log in
6. Can not swtich the status of input method, like fcitx and scim.
Steps to Reproduce:
1. yum install fcitx
2. gsettings set org.gnome.settings-daemon.plugins.keyboard active false
3. imsettings-swtich fcitx
4. service gdm restart or reboot the machine
Actual results:
ps aux | grep fcitx
Could not find any process of fcitx.
And,
imsettings-switch fcitx or imsettings-swtich -n -q -x
Fcitx comes back.
But users need to run imsettings-switch command once in every loginm in order
to enable their input method. I think it is not user-friendly.
Expected results:
I find out /etc/xdg/autostart/imsettings-start.desktop has value
AutostartCondition=GNOME3 if-session gnome-fallback. I think it is means that
imsettings does autostart except gnome-shell session.
In my opinon, whether imsettings-switch autostart or not, should not be based
on gnome session. When users launch in other DE or gnome-fallback mode,
imsettings-switch should start automatically. When users launch in gnome-shell
session, xdg autostart configure file should detect the value of
org.gnome.settings-daemon.plugins.keyboard active in gsettings. If the value is
true, imsettings-swtich should not autostart. If the value is false, imsettings
should be autostart
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=PqR7stEU5d&a=cc_unsubscribe
11 years, 1 month
[Fedora-i18n-bugs] [Bug 917130] [pt_BR] Keyboard loses dead keys on login
by Red Hat Bugzilla
Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=917130
Gustavo Maciel Dias Vieira <gustavo(a)sagui.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(gustavo(a)sagui.org |
|) |
--- Comment #14 from Gustavo Maciel Dias Vieira <gustavo(a)sagui.org> ---
Yes, it is a regular session.
The trigger for this bug is the upgrade from imsettings-1.5.0-2 to
imsettings-1.5.1-2. The changes between these versions may give you a clue.
By the way, when things started to get hairy, I started to do all my testing on
a VM, using a default account, with no customizations at all. See comment #4.
You may want to recreate such setup and reproduce the issue locally.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=nA4HrXLbLp&a=cc_unsubscribe
11 years, 1 month