It's impossible to enter the user details in non-live session installations on 'Who are you?' screen when 'release notes' link was clicked and closed

Bug #1157690 reported by Para Siva
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
High
Dimitri John Ledkov
Raring
Fix Released
High
Dimitri John Ledkov

Bug Description

During an installation that does NOT follow the live session installation path, it's impossible to enter the user details in the user setup screen on instances when 'release notes' link was clicked.

This could be observed with every non-live- session based installation using both amd64 and i386 images and on both hardware and on VMs (libvirt,kvm), once the 'release notes' link is clicked and closed a couple of times.

Steps to reproduce:
1. Boot the machine with USB
2. On the human-keyboard screen, press space-bar, select the default language and select 'Install Ubuntu' ( and not 'Try Ubuntu without installing')
3. On the Welcome screen, leave the default installation language selection and connect to a Wi-Fi network (by selecting a known network and entering its password, click connect)
4. Once the Wi-Fi connection was established, click the 'release notes' link which should have become available after the network connection
5. Close the browser once (File-> Quit), click the 'release notes' again and then click on the middle of the browser menu bar to resize the browser window - On the actual h/w most of the times Firefox would crash at this point, on VMs the crash occurrs after a couple of attempts. At times the firefox crash pop up does not show, so please continue to the next step after about 4 attempts of opening and closing the link.
6. Click 'Quit Firefox' in the crash reporting pop-up dialog if it came up in the above step and click the 'Continue' button on the Installer welcome screen
7. Click 'Continue' on the successive screens with leaving the default selections and selecting the right keyboard layout until 'Who are you?' screen comes up
8. It could be noticed that the key presses are not registered in the screen and the 'Continue' button remains grayed out.

Could not gather any logs yet because the failure is during the non-live session installation and could not open a terminal whilst the issue is happening.

Para Siva (psivaa)
description: updated
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/1157690

tags: added: iso-testing
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Para Siva (psivaa)
tags: added: rls-r-incoming
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

ctrl-alt-t should open a terminal, or use ctrl-alt-f1 to get a tty1.

Revision history for this message
Para Siva (psivaa) wrote :

When the issue happens none of the key-presses are registered. The above two combinations did not yield anything either.

Revision history for this message
Para Siva (psivaa) wrote :

The screenshot when this occurs, just noticed that the top bar with 'Install' on the window is not present in the failing ones.

Revision history for this message
Para Siva (psivaa) wrote :

The screenshot when this occurs, just noticed that the top bar with 'Install' on the window is not present in the failing ones.

Changed in ubiquity (Ubuntu Raring):
importance: Undecided → High
tags: added: rls-r-tracking
removed: rls-r-incoming
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

With image from 20130328, it is now using metacity window manager. Following the instructions, I have not managed to "crash" firefox / introduce the keyboard input lockup. I'm willing to mark this bug as fix released, but please retest and see if it was resolved for you.

tags: added: why-metacity
Changed in ubiquity (Ubuntu Raring):
status: Confirmed → Fix Committed
assignee: nobody → Dmitrijs Ledkovs (xnox)
Revision history for this message
Para Siva (psivaa) wrote :

Thanks for the change. I can confirm that I did not see this issue when tested with the images of 20130402.

Changed in ubiquity (Ubuntu Raring):
status: Fix Committed → Fix Released
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.