Keyboard layout options is complex and hard to navigate
Bug #391107 reported by
eric
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GNOME Settings Daemon |
Invalid
|
Medium
|
|||
| gnome-settings-daemon (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Go to preferences<
As an example, in France we use capslock to lock caps and shift to unlock caps... I still can't find the way to do it properly. And you know when you are used to unlock with shift, it is very hard to change the habit.
When you choose language french, it sould be like that by default. In windows you just have to tick or untick shift to unlock caps and it's done.
| summary: |
- keyboard layouts are a bit of a mess + Keyboard Layout Options are a bit of a mess |
Revision history for this message
| Vish (vish) wrote Re: Keyboard Layout Options are a bit of a mess | #1 |
| affects: | ubuntu → gnome-settings-daemon (Ubuntu) |
| Changed in gnome-settings-daemon (Ubuntu): | |
| importance: | Undecided → Wishlist |
| affects: | hundredpapercuts → gnome-settings-daemon |
Revision history for this message
| Pedro Villavicencio (pedro) wrote | #2 |
| Changed in gnome-settings-daemon (Ubuntu): | |
| status: | New → Triaged |
| Changed in gnome-settings-daemon: | |
| importance: | Undecided → Unknown |
| status: | New → Unknown |
| summary: |
- Keyboard Layout Options are a bit of a mess + Keyboard layout options is complex and hard to navigate |
| Changed in gnome-settings-daemon: | |
| status: | Unknown → Confirmed |
| Changed in gnome-settings-daemon: | |
| importance: | Unknown → Medium |
| Changed in gnome-settings-daemon: | |
| status: | Confirmed → Invalid |
| Changed in gnome-settings-daemon: | |
| importance: | Medium → Unknown |
| status: | Invalid → Unknown |
| Changed in gnome-settings-daemon: | |
| importance: | Unknown → Medium |
| status: | Unknown → Confirmed |
| Changed in gnome-settings-daemon: | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
This bug is an upstream one and it would be quite helpful if somebody experiencing it could send the bug the to the people writing the software. You can learn more about how to do this for various upstreams at https:/
Once submitted upstream , do report back here with the upstream bug number.
Thanks in advance!