Installation crash in a11y mode when using screen reader

Bug #941094 reported by Fabio Marconi
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Hello
Testing a11y installation, for two times, the installer crash at the same point, ever when inserting the name of the pc.
Thanks
Fabio

From syslog
Feb 25 19:57:20 ubuntu kernel: [ 735.814705] ubiquity[14981] trap int3 ip:7fdcaaa9413b sp:7fffb46e8f00 error:0
Feb 25 19:57:25 ubuntu install.py: Exception during installation:
Feb 25 19:57:25 ubuntu install.py: Traceback (most recent call last):
Feb 25 19:57:25 ubuntu install.py: File "/usr/share/ubiquity/install.py", line 679, in <module>
Feb 25 19:57:25 ubuntu install.py: install.run()
Feb 25 19:57:25 ubuntu install.py: File "/usr/share/ubiquity/install.py", line 129, in run
Feb 25 19:57:25 ubuntu install.py: self.copy_all()
Feb 25 19:57:25 ubuntu install.py: File "/usr/share/ubiquity/install.py", line 455, in copy_all
Feb 25 19:57:25 ubuntu install.py: self.db.progress('SET', 10 + copy_progress)
Feb 25 19:57:25 ubuntu install.py: File "/usr/lib/python2.7/dist-packages/debconf.py", line 60, in <lambda>
Feb 25 19:57:25 ubuntu install.py: lambda *args, **kw: self.command(command, *args, **kw))
Feb 25 19:57:25 ubuntu install.py: File "/usr/lib/python2.7/dist-packages/debconf.py", line 65, in command
Feb 25 19:57:25 ubuntu install.py: self.write.flush()
Feb 25 19:57:25 ubuntu install.py: IOError: [Errno 32] Broken pipe

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.9.21
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CasperVersion: 1.304
Date: Sat Feb 25 21:28:16 2012
InstallCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120225)
ProcEnviron:
 TERM=linux
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :
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/941094

tags: added: iso-testing
tags: added: a11y
removed: iso-testing
tags: added: iso-testing
Revision history for this message
Brian Murray (brian-murray) wrote :

Which a11y installation method were you testing? The screen reader, braille, something else?

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Fabio Marconi (fabiomarconi) wrote : Re: Installation crash in a11y mode, screen reader

I was testing the screenreader as suggested by the testcase uai-001
http://testcases.qa.ubuntu.com/Install/DesktopAccessibility
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

summary: - Installation crash in a11y mode
+ Installation crash in a11y mode, screen reader
summary: - Installation crash in a11y mode, screen reader
+ Installation crash in a11y mode when using screen reader
Changed in ubiquity (Ubuntu):
status: Incomplete → New
Changed in ubiquity (Ubuntu):
importance: Undecided → High
Colin Watson (cjwatson)
description: updated
Steve Langasek (vorlon)
tags: added: rls-p-tracking
Revision history for this message
Stéphane Graber (stgraber) wrote :

Can you still reproduce this with a recent daily?

The segfault looks like a gtk issue or yet another case where something tries to access a widget we destroyed when switching step in the installer, as it's happening for you when entering the name of the PC, I'd suspect it to be related to the hostname resolving timeout in ubi-usersetup.
Some work happened in that area for beta2 (fixing a similar bug with preseeded installs), so it'd be useful to have this tested again.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Just tested yesterday's build in the same hardware and it is no more present.
thanks
fabio
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in ubiquity (Ubuntu):
status: New → 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.