Ubiquity crashes after partitioning step with accessibility enabled.

Bug #63162 reported by Luke Yelavich
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Ubiquity completely freezes when activating the forward button on the partitioning step, when the GNOME accessibility framework is enabled, and the orca screen reader is being used. This seems to occur regardless of whether modifications to the partition scheme have been made or not.

Steps to reproduce:
1. Boot a copy of the beta release desktop CD.
2. Enable the GNOME accessibility framework in System -> Preferences -> Assistive Technology Preferences. Check the box labeled "Enable accessibility technologies." No other boxes need to be checked.
3. Close the window, and log out/in again.
4. Once logged back in, bring up a terminal, and run "sudo orca". This will ask you a few questions. You can answer these however you like. You will then be returned to a prompt. Run orca again with the same command. Orca will run, printing its output to the terminal.
5. Launch the installer, and fill in options as required, making sure to select the manually partition option. The partitioner appears, and the installer should freeze when you activate the forward button from this step, if you haven't made any partition changes. The installer should also freeze once any partitioner changes have been saved.

Revision history for this message
Colin Watson (cjwatson) wrote :

I haven't been able to reproduce this here. Would it be possible to get an 'strace -f -tt -s 1024' of ubiquity to try to see what it's doing? To reduce the size of the trace, you might want to attach strace after selecting "Manually edit partition table" but before pressing Forward on that page.

Changed in ubiquity:
status: Unconfirmed → Needs Info
Revision history for this message
Ravi Sreenivasan (ravi-sreenivasan) wrote :

This happened to me every time that I tried to install Feisty Fawn using the official CD-ROM shipped to me from shipit! The installer would reach the partitioning step; on selecting manual partitioning, a message popped up: "Warning: No root filesystem specified!"; the existing partitions would show up in the editor. On attempting to specify options or simply pressing the forward button, the installer would freeze with a message in the notification toolbar that Ubiquity had crashed!

I had to reinstall Dapper, which installs and works flawlessly in the same system and had to upgrade through update manager over two days!

I submitted the bug each time it crashed during install!

Now running Feisty after a long update process! Has this happened with me only or are the Feisty CD-ROMs that are shipped through shipit defective?

Never had any issues while installing Dapper from the official CD-ROMs that I got through shipit! They installed smoothly on all systems [mine and my friends' PC's]!

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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.