ubiquity crashed with IndexError in render_slider()

Bug #415234 reported by eldad
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

ubuntu@ubuntu:~$ lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10

ubuntu@ubuntu:~$ apt-cache policy ubiquity
ubiquity:
  Installed: 1.99.6
  Candidate: 1.99.6
  Version table:
 *** 1.99.6 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
Date: Tue Aug 18 07:45:19 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha amd64 (20090812.3)
Package: ubiquity 1.99.6
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity gtk_ui
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/5852/environ'
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']
SourcePackage: ubiquity
Title: ubiquity crashed with IndexError in render_slider()
Uname: Linux 2.6.31-5-generic x86_64
UserGroups:

Revision history for this message
eldad (eldad-a) wrote :
tags: removed: need-duplicate-check
visibility: private → public
Revision history for this message
eldad (eldad-a) wrote :

after reading the so-called duplicate, I believe it is not.
this happened upon reaching the partition editing stage in the installation process.
seems irrelevant to the grub2 as mentioned in the so-called duplicate.

I believe the problem is related to resizing of existing partitions, but cannot say for sure as I did that bit manually (installation succeded).

Revision history for this message
eldad (eldad-a) wrote :

this bug is rather similar to what was reported earlier in https://bugs.launchpad.net/bugs/386388
noting the following differences:
here the installation was done using an unmodified iso of alpha-4, from a bootable-usb.
the crash appeared when the partitioning stage was arrived (ie before choosing manual partitioning).

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.