Wrong configuration of keyboard

Bug #27284 reported by Celso Pinto
56
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kbd-chooser (Ubuntu)
Invalid
High
Rolf Leggewie
Declined for Dapper by Adam Conrad
Declined for Gutsy by Adam Conrad
Declined for Hardy by Adam Conrad
Declined for Intrepid by Adam Conrad
Declined for Jaunty by Adam Conrad

Bug Description

During Dapper Flight 2 installation, I chose the Portuguese keyboard layout yet
when GNOME started I noticed that the keyboard layout was similar to that of
en_US. I had to manually go change the keyboard layout in the Keyboard control
panel applet.

Revision history for this message
Rui Matos (tiagomatos) wrote :

Does this still occur on a recent dapper install?

Revision history for this message
Celso Pinto (cpinto) wrote :

I'll have to get back to you later as I sent away my laptop for repair.

Matt Zimmerman (mdz)
Changed in installation-report:
status: Unconfirmed → Needs Info
Revision history for this message
Eduardo Cereto (dudus) wrote :

This is still true in Dapper Flight 6.
The new way ubuntu installs keyboards makes it hard to have it configured when you boot.

You'll have than to go into System>Preferences>Keyboard
and than set the rigth one.

obs. For Brazillian ABNT 2 keyboards, you shoul use :
Keyboard model: Brazilian ABNT2
Layout Brazil or Brazil(dead keys).

Revision history for this message
Celso Pinto (cpinto) wrote :

This time around I choose to install from the LiveCD and the Espresso installer asks for the keyboard layout. Using this installer works perfectly, but as Eduardo mentions maybe the debian-installer has to be tweaked to handle keyboard layouts better.

Revision history for this message
Tollef Fog Heen (tfheen) wrote :

Espresso (the live cd installer) doesn't actually configure the keyboard yet. This is pointed out in the announcement and already known. I will investigate using regular d-i later.

Revision history for this message
Ari Torhamo (ari-torhamo) wrote :
Revision history for this message
Celso Pinto (cpinto) wrote :

Yup, sounds like exactly the same problem.

Revision history for this message
Colin Watson (cjwatson) wrote :

Please don't mark these two bugs as duplicates; they're sufficiently distinct that I would like to investigate them separately.

Revision history for this message
Rocco Stanzione (trappist) wrote :

Is this still a problem in current dapper, or in edgy?

Revision history for this message
Paulo Zanoni (pzanoni) wrote :

I've got a problem just like this.
Should it have a separate bug report?

I got this bug in 2 different ways:
1: Upgrading Ubuntu 6.06 to 6.10
2: Fully installing Ubuntu from ZERO using 6.10 _alternate_ CD.
Didn't try it using the live cd...

The error:
My console used to work perfectly. After upgrading (or after the new installation), the problem started.
The console is screwed up. I use "Brazilian Portuguese pt_br ABNT2" keybard, and my console USED to work correctly, now it doesn't. Some keys like "/" just doesn't work. Other keys like "ç" work, but for example, when it is asking for my login name (and only on that, not after logging in), if i type for example "ááá", and press backspace, backspace just won't work... Sometimes it works with other characters...
Very very odd...
Also, the console FONT changed. This version has "ZEROS" with a little point in the middle, the others had a slash inside the zero... (this is not exactly a bug, but may be a symptom of the bug).
Running "sudo dpkg-reconfigure console-setup" didn't seem to work. Even after rebooting. And I don't know exactly which options to choose... (especially when asked about those "lat1 lat15 lat8").
Since I still got an 6.06 installation on another computer, how can I compare both old and actual console configurations to try to fix them up? Which file? I think this is a very annoying bug for brazilian-portuguese-abnt2 users...

Someone needs to check if this also happens with a new install from the "desktop cd".

Is this a new bug?

Revision history for this message
Stéphane Marguet (stemp) wrote :

Zólhos, are you still experiencing this issue ?
Could you please provide an update for us on whether or not this is still a problem with edgy or feisty ?

Changed in kbd-chooser:
assignee: nobody → stempubuntu
Revision history for this message
Paulo Zanoni (pzanoni) wrote :

Yes, on 6.10 I'm still experiencing this issue.
I haven't tested it on feitsy...

Also, there are other symptoms that I forgot to tell you:
If 'caps lock' is on, and you press '2', it will write '@' instead of '2'. That happens to ALL the keyboard keys, not just '2'.
Caps lock seems to have exactly the same effect as if 'shift' was pressed. This is not supposed to happen. When I press '2', it should write '2', even if caps lock is on. It just should write '@' only if shift is being hold, no matter which state caps lock is.
Also, if you turn on caps lock, hold shift, and then press '2', it will write '2', instead of the expected '@'.

Revision history for this message
Stéphane Marguet (stemp) wrote :

Thanks Zólhos

Changed in kbd-chooser:
assignee: stempubuntu → nobody
status: Needs Info → Confirmed
Revision history for this message
Loïc Martin (loic-martin3) wrote :

I just had that problem and reopened Bug #40627 (pb seems to be in Ubiquity)

Revision history for this message
Siegfried Gevatter (rainct) wrote :

A similar (same?) bug on Gutsy was reported here: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/124033

Revision history for this message
Wil (wil-vandeven) wrote :

In 7.04 I miss the euro (€) sign, and the add (@) sign is under the wrong button. I need those signs very much for email,spreadsheets etc.

It doesn't matter whatever keyboard I use. I've set the parameters for country and language correct.

security vulnerability: yes → no
visibility: private → public
Revision history for this message
Rolf Leggewie (r0lf) wrote :

I'm sorry to see this one is slowly approaching the 10-year mark without any kind of documented resolution.

Let me first confirm this is still a problem for anyone in trusty or later. Can you please verify?

Changed in kbd-chooser (Ubuntu):
assignee: nobody → Rolf Leggewie (r0lf)
status: Confirmed → Incomplete
Revision history for this message
Rolf Leggewie (r0lf) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kbd-chooser (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.