Ubuntu
ubiquity package

OEM installations hang on 'Noting disappearance of ubiquity' step

Bug #1163266 reported by Para Siva
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
High
Unassigned
Raring
New
High
Unassigned

Bug Description

OEM installations with raring desktop images (20130402) both amd64 and i386 appear to hang when the 'Applying changes' window is at 'Noting disappearance of ubiquity' step with 'Purging configuration files for ubiquity' on the 'Details' window. This occurs on both hardware and VMs during both live session based and direct ubiquity installations.

Steps:
1. Start the installation
2. At the 'Human-keyboard' screen press space bar, select the default English language and then press F4 to select OEM installation
3. Continue the installation and enter OEM mode username and password and continue
4. Restart -> Once restarted Clieck 'Prepare for shipping to end user' -> clieck 'OK' on oem-config-prepare window -> Restart again
5. Click 'Continue' on the System Configuration windows with default settings and enter the username and password and continue
6. The hang occurs during 'Applying changes' window with 'Noting disappearance of ubiquity' step with the details window showing 'Purging configuration files for ubiquity'
The logs are attached.

See original description
Revision history for this message
Para Siva (psivaa) wrote :
description: updated
Revision history for this message
Para Siva (psivaa) wrote :
Revision history for this message
Para Siva (psivaa) wrote :
  • dm Edit (95.7 KiB, text/plain)
Revision history for this message
Para Siva (psivaa) wrote :
Revision history for this message
Para Siva (psivaa) wrote :
Revision history for this message
Para Siva (psivaa) wrote :
Ubuntu Foundations Team Bug Bot (crichton)
tags: added: ubiquity-2.14.1
tags: added: raring
Revision history for this message
Brian Murray (brian-murray) wrote :

This seems irregular:

Apr 2 13:22:26 oem-Inspiron-N4010 kernel: [ 215.093334] indicator-sessi[20059]: segfault at 10 ip 0000000000421a72 sp 00007fff6b9b9520 error 4 in indicator-session-service[400000+37000]
Apr 2 13:22:28 oem-Inspiron-N4010 kernel: [ 216.894575] indicator-sessi[20082]: segfault at 10 ip 0000000000421a72 sp 00007fff7b406a20 error 4 in indicator-session-service[400000+37000]
Apr 2 13:22:31 oem-Inspiron-N4010 kernel: [ 220.293047] indicator-sessi[20095]: segfault at 10 ip 0000000000421a72 sp 00007fff633569a0 error 4 in indicator-session-service[400000+37000]
Apr 2 13:22:38 oem-Inspiron-N4010 kernel: [ 226.907438] indicator-sessi[20267]: segfault at 10 ip 0000000000421a72 sp 00007fffb7fe32e0 error 4 in indicator-session-service[400000+37000]
Apr 2 13:22:51 oem-Inspiron-N4010 kernel: [ 239.904501] indicator-sessi[20305]: segfault at 10 ip 0000000000421a72 sp 00007fff9b495000 error 4 in indicator-session-service[400000+37000]
Apr 2 13:23:17 oem-Inspiron-N4010 kernel: [ 265.735762] indicator-sessi[20319]: segfault at 10 ip 0000000000421a72 sp 00007fff4fd91230 error 4 in indicator-session-service[400000+37000]
Apr 2 13:24:08 oem-Inspiron-N4010 kernel: [ 317.136216] indicator-sessi[20341]: segfault at 10 ip 0000000000421a72 sp 00007fffc86bf3e0 error 4 in indicator-session-service[400000+37000]

Brian Murray (brian-murray)
Changed in ubiquity (Ubuntu):
importance: Undecided → High
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.