[Bug 918701] Re: Ubiquity crash if screen reader is running

[Brian Murray]

I was also able to cause ubiquity to crash by keyboarding (back arrow
and tab) around the first screen when using orca.  One time I received
the same segfaul as Fabio.  The other I had the following:

[  107.344173] ubiquity[3614]: segfault at d1 ip 00007f0dac708eef sp 00007fff43470ac0 error 4 in libdbus-1.so.3.5.8[7f0dac6f2000+42000]
[  146.459131] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
[  174.308451] ubiquity[4669]: segfault at d1 ip 00007f456e688eef sp 00007fff4607f230 error 4 in libdbus-1.so.3.5.8[7f456e672000+42000]
[  275.341192] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id


** Changed in: ubiquity (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubiquity (Ubuntu)
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/918701

Title:
  Ubiquity crash if screen reader is running

Status in “ubiquity” package in Ubuntu:
  Triaged

Bug description:
  Hello
  Trying an installation in a11y modality *testcase uai-001 ubiquity start, show the first window, I can choose the language, then it crash.
  Thanks
  Fabio

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: ubiquity 2.9.10
  ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
  Uname: Linux 3.2.0-9-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.299
  Date: Thu Jan 19 14:03:01 2012
  LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120119)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/918701/+subscriptions