Ubuntu
ubiquity package

During installation: proposed keyboard layout does not correspond to the actual connected keyboard

Bug #1508779 reported by José Jorge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

During installation of Xubuntu Wily Final 64 bit ISO, the proposed keyboard on the Ubiquity installer does not correspond to the actual keyboard connected to the system nor the timezone selected in the previous step.

I installed Xubuntu Wily Final 64 bit ISO, I was connected to the internet, selected Spanish as the installation language and Mexico City as timezone, but when going to keyboard configuration, English language was selected.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Oct 21 23:33:42 2015
InstallationDate: Installed on 2015-10-22 (0 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
José Jorge (mexchip) wrote :
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1508779

tags: added: iso-testing
José Jorge (mexchip)
summary: During installation: proposed keyboard layout does not correspond to the
- actual keyboard connected
+ actual connected keyboard
Revision history for this message
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1508779

and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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