ubiquity crashed with ZoomMapException in load_pixmap()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I was installing UBUNTU 8.10, 32 bit, on a Pentium 4. The unusual features of this machine is ECC memory (512 MB) and a SCSI drive. Further deviation from the ordinary is that I inserted the installation CD in the Slave drive. This mistake was rectified by the installation procedure.
The crash followed after what appeared to be a full installation, and was preceded by a normal looking Desktop except the text was garbled in that only squares appeared instead of letters or numbers. Since I couldn't read the messages I attempted to reboot. This happened but a blank screen with a blinking cursor appeared and stayed there for 20 minutes.
I rebooted again and changed the BIOS so that the machine booted from the CD before the hard drive. The reinstallation began again but was interupted early in this process. The crash was detected and a request was made for me to file this bug report.
I shall wait awhile before I take another stab at installing UBUNTU on this machine.
ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/
InterpreterPath: /usr/bin/python2.5
Package: ubiquity 1.10.10
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/lib/
ProcEnviron:
LANGUAGE=
PATH=/
LANG=en_US.UTF-8
PythonArgs: ['/usr/
SourcePackage: ubiquity
Title: ubiquity crashed with ZoomMapException in load_pixmap()
Uname: Linux 2.6.27-7-generic i686
UserGroups:
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test a current, supported, Ubuntu version. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 308832, and any other logs that are relevant for this particular issue.