[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 #28 from Mike FABIAN <mfabian(a)redhat.com> ---
To demonstrate what happens:
- set the “Portuguese (Brasil)” keyboard in the panel.
- Start some other, non-GTK terminal, like xterm.
- killall gnome-terminal
to make sure gnome-terminal is really gone.
(gnome-terminal uses one process for multiple windows, i.e. if you
start "gnome-terminal" from a gnome-terminal, you only get a new
window for the same process, not a new gnome-terminal).
- Now start a gnome-terminal like this from the xterm:
env XMODIFIERS=@im=none GTK_IM_MODULE=xim LANG=pt_BR.UTF-8 gnome-terminal
Now all dead keys work correctly, including ç (ç is typed by typing
the key to the right of ‘P’ followed by ‘c’)
It is important to use XMODIFIERS=@im=none *not* XMODIFIERS=@im=ibus !
If you use XMODIFIERS=@im=ibus and ibus is running, you will get ć,
not a ç (when using the dead key to the right of P)
If you use XMODIFIERS=@im=ibus and ibus is *not* running, you will
get the broken behaviour where the dead keys do not work at all.
That is what Gustavo saw because in the default Portuguese (Brasil)
install, ibus is not running.
Even if ibus is not running, XMODIFIERS=@im=ibus GTK_IM_MODULE=xim
breaks something for gnome-terminal.
Contrary to gnome-terminal, xterm doesn't seem to care whether you
use XMODIFIERS=@im=none or XMODIFIERS=@im=ibus if ibus is *not*
running.
*If* ibus is running, xterm *does* care because then it uses ibus
with XMODIFIERS=@im=ibus, i.e. typing the key to the right of ‘P’
followed by ‘c’ will give ć. But whether ibus is running or not,
xterm it uses X deadkey support for Portugese if started with
XMODIFIERS=@im=none
So xterm will use X deadkey support for XMODIFIERS=@im=whatever as
long as there is no XIM input server named "whatever" running.
I.e. as far as xterm is concerned, XMODIFIERS=@im=none and
XMODIFIERS=@im=whatever behave the same as long as there is no input
server named "whatever" running.
For gnome-terminal however, XMODIFIERS=@im=none seems to have a
special meaning, together with GTK_IM_MODULE=xim it uses X deadkey
support.
Any other value except "none" will try to use an XIM input server
with that name.
If such an input server is running, you will get the deadkey
handling of that input server (probably not perfect for Portuguese),
if no such input server is running, it is completely broken and the
deadkeys are inserted immediately.
So perfect behaviour for Portuguese (Brasil) keyboard can be achieved
if the session is started with
XMODIFIERS=@im=none GTK_IM_MODULE=xim LANG=pt_BR.UTF-8
Looking last part of the diff in the imsettings log in:
https://bugzilla.redhat.com/show_bug.cgi?id=917130#c27
I have the impression this is what imsettings tried to do.
I see
XMODIFIERS: @im=none
there and
+[ 1363100247.372105]: IMSettings-Daemon[5461]: INFO: Attempting to switch IM
to X compose table [lang=pt_BR.UTF-8, update=false]
+[ 1363100248.203136]: IMSettings-Daemon[5461]: INFO: no need to invoke any
auxiliary process for X compose table
+[ 1363100248.203469]: IMSettings-GSettings backend[5461]: INFO: Setting up
xim:xim as gtk+ immodule
But nevertheless, after logging in, checking in gnome-terminal
shows XMODIFIERS=@im=ibus
So this together with using XIM in gnome-terminal gives the broken
deadkey support.
Now switching the keyboard in the panel from Portuguese (Brazil) to English
and back does not change the value of XMODIFIERS for gnome-terminal,
for for some reason it changes the input-module to “simple”.
So before switching the keyboard layout back and forth after the login,
right-mouse click and checking the "Input method" menu in gnome-terminal
shows "X Input Method". After switching the keyboard layout to English
and back to Portuguese in the panel, and checking again in gnome-terminal
with right-mouse click, one can see this has changed to "simple".
Which appears to make the deadkeys work, but of course not perfect for
Portuguese. ã is inserted correctly, but typing the key to the right of ‘P’
followed by c inserts a ć, not a ç.
--
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=tg8D4yftiT&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
--- Comment #27 from Mike FABIAN <mfabian(a)redhat.com> ---
Difference in the ~/.cache/imsettings/log between
imsettings-1.5.0-2 and imsettings-1.5.1-2:
[mfabian@localhost ~]$ diff -u imsettings-log-1.5.0.2 imsettings-log-1.5.1-2
--- imsettings-log-1.5.0.2 2013-03-12 14:03:08.927546408 -0200
+++ imsettings-log-1.5.1-2 2013-03-12 14:02:50.919777478 -0200
@@ -1,23 +1,23 @@
-[ 1363103359.670799]: IMSettings-Daemon[10514]: INFO: Starting
imsettings-daemon...
-[ 1363103359.671036]: IMSettings-Daemon[10514]: INFO:
[HOME=/home/mfabian/.config/imsettings]
-[ 1363103359.671091]: IMSettings-Daemon[10514]: INFO:
[XINPUTRCDIR=/etc/X11/xinit/]
-[ 1363103359.671141]: IMSettings-Daemon[10514]: INFO:
[XINPUTDIR=/etc/X11/xinit/xinput.d/]
+[ 1363100244.497828]: IMSettings-Daemon[5461]: INFO: Starting
imsettings-daemon...
+[ 1363100244.498026]: IMSettings-Daemon[5461]: INFO:
[HOME=/home/mfabian/.config/imsettings]
+[ 1363100244.498079]: IMSettings-Daemon[5461]: INFO:
[XINPUTRCDIR=/etc/X11/xinit/]
+[ 1363100244.498126]: IMSettings-Daemon[5461]: INFO:
[XINPUTDIR=/etc/X11/xinit/xinput.d/]
-[ 1363103359.671189]: IMSettings-Daemon[10514]: INFO:
[MODULEDIR=/usr/lib64/imsettings]
+[ 1363100244.498202]: IMSettings-Daemon[5461]: INFO:
[MODULEDIR=/usr/lib64/imsettings]
-[ 1363103359.671243]: IMSettings-Daemon[10514]: INFO: [MODULES=gsettings]
+[ 1363100244.498263]: IMSettings-Daemon[5461]: INFO: [MODULES=gsettings]
imsettings information
==========================
XINPUTRC: /etc/X11/xinit/xinput.d//xcompose.conf
File: "/etc/X11/xinit/xinput.d//xcompose.conf"
Size: 146 Blocks: 8 IO Block: 4096 arquivo comum
- Device: fd01h/64769d Inode: 1189563 Links: 1
+ Device: fd01h/64769d Inode: 1189564 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Context: system_u:object_r:bin_t:s0
- Access: 2013-03-12 13:49:19.379551431 -0200
- Modify: 2013-03-12 13:13:58.000000000 -0200
- Change: 2013-03-12 13:48:46.760166169 -0200
+ Access: 2013-03-12 12:14:38.676679875 -0200
+ Modify: 2012-12-20 03:59:00.000000000 -0200
+ Change: 2013-03-12 12:05:09.260406833 -0200
Birth: -
Is DBus enabled: yes
Is imsettings enabled: yes
@@ -27,10 +27,13 @@
GUESS_DESKTOP: $GDMSESSION
DISABLE_IMSETTINGS:
IMSETTINGS_DISABLE_DESKTOP_CHECK:
-DBUS_SESSION_BUS_ADDRESS:
unix:abstract=/tmp/dbus-JwlmGoiXph,guid=e7002729a7bd683adc462e3c513f4e7f
+DBUS_SESSION_BUS_ADDRESS:
unix:abstract=/tmp/dbus-66dxjGy2Jh,guid=4401facef6b1c4a7ab312c94513f4254
GTK_IM_MODULE:
QT_IM_MODULE: xim
XMODIFIERS: @im=none
IMSETTINGS_MODULE: X compose table
IMSETTINGS_INTEGRATE_DESKTOP: yes
+[ 1363100247.372105]: IMSettings-Daemon[5461]: INFO: Attempting to switch IM
to X compose table [lang=pt_BR.UTF-8, update=false]
+[ 1363100248.203136]: IMSettings-Daemon[5461]: INFO: no need to invoke any
auxiliary process for X compose table
+[ 1363100248.203469]: IMSettings-GSettings backend[5461]: INFO: Setting up
xim:xim as gtk+ immodule
[mfabian@localhost ~]$
--
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=cpW5ncyTq2&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
--- Comment #26 from Gustavo Maciel Dias Vieira <gustavo(a)sagui.org> ---
(In reply to comment #25)
> (In reply to comment #4)
> > So, I'd like to stress the info on comment #2 and register detailed
> > instructions to reproduce the bug:
> > * Make fresh install of F18 and apply no updates.
> > * Select the pt_BR locale.
>
> Did you do the install in pt_BR locale?
No at first, because anaconda in pt_BR hides some dialogs making it almost
impossible to use. My first installation was in en_US later changed to pt_BR. I
suspected that might be the cause, so I made other installation (in a VM, to be
able to accept all anaconda defaults) in pt_BR. Got the same result with both.
>
> Did you select the make the keyboard for the selected language
> the default at the first screen of installation?
In both situations above I selected the "Portuguese (Brazil)" layout during
installation and made it default.
--
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=XWhwoDbolU&a=cc_unsubscribe
11 years, 1 month