Red Hat Bugzilla – Bug 596664
locale.alias should include nb_NO.utf8 and nn_NO.utf8
Last modified: 2014-06-18 05:12:49 EDT
Description of problem:
Input of Norwegian characters in some components does not work.
Unable to use dead keys overall
Components tested is:
Input does work in
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install F13 with Norwegian setup (keyboard and language)
2. Start gedit
3. Try to write Norwegian characters
There is "no reaction" in gedit
The Norwegian characters should appear
Dead keys does not work properly either. Unable to produce
~ above O. Does not work i Firefox or OpenOffice either.
Swedish characters like .. above O is also impossible to
produce, the .. should be one character, but unable to produce that now.
I can kind of reproduce on my test machine,
but not from a F13 Live instance.
(In reply to comment #2)
> I can kind of reproduce on my test machine,
> but not from a F13 Live instance.
I installed from DVD-iso. Please let me know if there is anything I can provide to solve this.
Noticed that in Netbeans 6.8 all keys are working as expected. Starting
LANG=no_NO.utf8 /usr/local/netbeans-6.8/bin/netbeans --laf javax.swing.plaf.metal.MetalLookAndFeel
I've looked some further into this. From what I can see the user created during installation get this LANG env. setup:
Root user, and user created after system is up and running gets this:
Notice the difference in case for UTF.
This have been tested on a fresh installation of FC13. Since I've got no clue on
where this setting comes from, I've created an entry in .bash_profile with
I'm considering this as an workaround since I now got my Norwegian chars where I want them.
I have the same issue with Norwegian Nynorsk, however I can write the special characters in Firefox (but not in rest of GNOME).
I can also confirm that doing a "export LANG=nn_NO.UTF-8" helped.
I have the same problem in F12 (yes, I know this bug is for F13) but it looks like the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=468590, which is closed, but it seems to keep popping up again in each release.
This is in GNOME applications though. Didn't read too closely.
Ooops... Anyway, the problem might affect both QT and GTK based apps, as it seems to be related to SCIM. In fact, I've just 'solved' it with 'yum remove scim*'
This is also the case for nn_NO.utf-8!
So what was the conclusion?
I am still puzzled:
- why .utf-8 occurred
- why removing scim helped
Is it reproducible in a fresh a/c?
No idea what an a/c is so I can't test.
It is present on my laptop, and putting "export LANG=nn_NO.UTF-8" in .bash_profile works but not when resuming from suspend.
I'm waiting to install F13 on one machine until this is fixed.
Sorry by a/c meant a user account.
I created a new account, left its language to Nynorsk and writing æøå in gedit worked.
I then logged out and changed the language to Bokmål and æøå didn't work in gedit anymore.
I then changed back to Nynorsk and æøå didn't work in gedit.
So it is still present.
Thanks for the reproducer. :-)
(Well I can't reproduce the locale encoding ".utf-8".)
But I see the keyboard input problem: pretty bad, sorry.
Can you please test with
It fixes the problem for me.
Anyway two workarounds, either:
1) avoid using xim with gtk (currently it is default)
$ GTK_IM_MODULE=gtk-im-context-simple gedit
Above update takes this approach and so will F14.
2) use a valid X locale
$ LANG=nb_NO.UTF-8 gedit
I dunno why gdm is still promoting invalid X locales... :-/
Ok finally worked it out:
/usr/share/X11/locale/locale.alias lists no_NO.utf8
but not aliases for nb_NO.utf8 and nn_NO.utf8,
hence the above behaviour.
Following lines need to be added:
(In reply to comment #15)
of course. Thanks Tagoh-san for pointing out my mistake.
I installed the imsettings update (it wasn't in updates-testing so had to manually install imsettings-lib then imsettings), created a new account and rebooted the machine.
Logging into default nynorsk worked. Changing to bokmål worked. Changing back to nynorsk worked.
I am confident that update fixes this issue. :) Thanks for fixing it. Now get it updated for everyone! :D
Reporter, could you confirm that the issue has been resolved via workaround in the comment 16, please?
Anyway let's keep the bug open until the real fix goes into libX11.
I posted a patch upstream: https://bugs.freedesktop.org/show_bug.cgi?id=29773
I removed the entry I had in .bash_profile:
Added entries from Comment 16 to /usr/share/X11/locale/locale.alias
Did a reboot, stated gedit and there were Norwegian signs. To confirm that the entries really did the trick, I commented them out in /usr/share/X11/locale/locale.alias
Reboot and new test with gedit. And it still worked.
This issue seems fixed in f15 though, any chance to get a backport in f13 and f14?
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
As far as could tell, the problem were solved by the provided patch. And I have not experienced the problem after. Fresh install of FC14 have not displayed the bug for me.
As per comment#22 and f14 is about to reach EOL, closing this.