Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 80703 - editors useless on gnome desktop
Summary: editors useless on gnome desktop
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: XFree86
Version: phoebe
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
Depends On:
Blocks: 79578
TreeView+ depends on / blocked
Reported: 2002-12-30 06:03 UTC by Michal Jaegermann
Modified: 2007-04-18 16:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-01-07 16:41:59 UTC

Attachments (Terms of Use)

Description Michal Jaegermann 2002-12-30 06:03:05 UTC
Description of problem:
With LANG is set to en_CA.UTF-8 keyboard handling makes standard editors

After starting emacs or gvim one can pound on a key with " and ' any numbers
of times without causing any reaction at all.  If one will start
'emacs -nw' in a terminal window then hitting " twice is doing something
but nothing expected (it is easier to see that than describe). 'vi' started
in a terminal window _pretends_ to insert " when " is hit twice but this is
really not that character which can be seen in attempts to search for quotes
already existing in a file; they fail.

After switching to a text console apparently one can use an editor
(I did not run extensive tests) but such workaround is plain ridiculous.

Comment 1 Havoc Pennington 2003-01-02 16:09:10 UTC
Don't see how gnome is involved (gnome-core doesn't even exist anymore).

This would be a keymap or input method problem afaik. It's possible I suppose
that the gnome keyboard switcher applet messes that up, if you're running it, but 
you'd have to check whether things work if you run under twm etc.

Comment 2 Mike A. Harris 2003-01-02 16:14:39 UTC
Does emacs or vi even support UTF-8?

Comment 3 Owen Taylor 2003-01-02 16:31:43 UTC
What terminal are you running in? What keyboard layout are you using?

(Emacs and vi both have UTF-8 support; the Emacs support is 
pretty awful, but it should be good enough for French and other
European languages.)

For emacs-not-in-a-terminal, or gvi, this would be a XFree86
issue - the compose hanlding for Xlib was changed a bit recently
and various bugs have shown up.

If emacs or vi is misbehaving inside a gnome-terminal, that would
be a different problem, but without knowing your keyboard layout,
it's hard to know exacty what sort of different problem.

Comment 4 Michal Jaegermann 2003-01-02 17:25:06 UTC
I do not know what is responsible for a totally broken behaviour.
The bug has to be filed somewhere and I only report what I observe.
If you think that this is a bad component then change it.

My installation is using "US keyboard" and "en_CA" locale.  Nothing
"exotic".  Whatever anaconda dumped on my hard drive is there.

Comment 5 Owen Taylor 2003-01-02 17:39:38 UTC
Does en_US.UTF-8 work? AFAIK, there should be absolutely no difference
between en_US.UTF-8 and en_CA.UTF-8 for keyboard handling.

Comment 6 Michal Jaegermann 2003-01-02 17:51:12 UTC
> Does en_US.UTF-8 work?

I tried few different encodings starting things like 
'( env LANG=en_US.UTF-8 emacs )' and bunch of other other variants (vi, gvim,
'emacs -nw') with different LANG settings which included and excluded UTF-8.
I could not find even remotely sane behaviour.

Comment 7 Owen Taylor 2003-01-02 19:34:58 UTC
I hate to ask this question, but since nobody else has reported
any issues (at least that I've seen), and it should be really
obvious if the " key doesn't work, are you sure your keyboard
is working correctly?

Or -  could you have accidentally selected the us_intl keyboard
rather than the us keyboard during the install? The us_intl keyboard
will be quite strange in behavior for someone expecting a standard
us layout.

Comment 8 Michal Jaegermann 2003-01-02 20:48:34 UTC
> are you sure your keyboard is working correctly?

I would think so. :-)  The report in which you can see incriminated
characters is typed in on the same machine and the same keyboard but
while running a system based on 7.3 distro.  It is a "dual boot" setup.
I also mentioned that I can use a console and edit so I think that we
can safely eliminate my keyboard (Logitech Deluxe 104 - once again nothing
really special).

IIRC 'gvim' blinks for a short moment something on a status line about
"XIM extenstions", whatever that may be.  In the meatime I rebooted
few times between my "work", and workable, system and "Phoebe" installation
and this also nothing changed.

Comment 9 Owen Taylor 2003-01-02 21:00:09 UTC
The keyboard layout isn't your keyboard, but a config option. (What 
you selected on install, usually, but it could be changed at other
points.) You should be able to see what it is by looking at

Comment 10 Michal Jaegermann 2003-01-02 22:00:09 UTC
> You should be able to see what it is by looking at /etc/X11/XF86Config-4

This file does not exist. :-)  But in XF86Config I can see

# File generated by anaconda.

        Option  "XkbRules"      "xfree86"
        Option  "XkbModel"      "pc105"
        Option  "XkbLayout"     "us_intl"

Why "us_intl" I am not so sure.

I can try later to reconfigure the whole X from scratch.

Comment 11 Michal Jaegermann 2003-01-03 03:13:59 UTC
Indeed, after reconfiguring "XkbLayout" from "us_intl" to "us" the problem
disappears.  Why anaconda stick the first one in XF86Config I am not sure.
It could be that in a "user friendly" interface I turned it on accidentally.

Comment 12 Mike A. Harris 2003-01-07 13:19:22 UTC
So is the resolution for this one 'user goofup', or is there something
to investigate here still?

Comment 13 Michal Jaegermann 2003-01-07 16:17:25 UTC
I guess that this can be closed (if ending up with one of "official"
keyboard mappings qualifies as "goofup").

Comment 14 Havoc Pennington 2003-01-07 16:41:59 UTC
Well all the official mappings can't work for all keyboards, if any mapping
would work with any keyboard you wouldn't have to choose one.

I do think the keyboard selection UI could use some love (naming the keymaps
something better for a start), but I would say it's currently working as intended.

Note You need to log in before you can comment on or make changes to this bug.