[Lucid]Ubiquity crashes Xorg while running in Xubuntu 64

Bug #539146 reported by Jeff Lane 
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: xorg

Booted Lucid Xubuntu 64bit Live environment and started Ubiquity. I chose the OEM Install option from the F4 menu in the boot screen.

Once I get to partitioning I choose manual partitioning and am able to start partitioning. I usually make it as far as creating a blank table, and adding a /boot partition (ext2, 100MB) before X crashes.

This always seems to happen in the same place during the installation (I've recreated this 3 times in a row). I'm installing to a 64bit VirtualBox VM.
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
GdmLog2: Error: command ['sudo', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
LiveMediaBuild: Xubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100315)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
Package: xorg 1:7.5+3ubuntu1
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xhostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- oem-config/enable=true
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Tags: lucid lucid
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-16-generic

---
Architecture: amd64
DistroRelease: Ubuntu 10.04
LiveMediaBuild: Xubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100315)
Package: ubiquity 2.1.35
PackageArchitecture: amd64
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Tags: lucid
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

---
Architecture: amd64
DistroRelease: Ubuntu 10.04
LiveMediaBuild: Xubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100316.1)
Package: ubiquity 2.2.0
PackageArchitecture: amd64
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Tags: lucid
Uname: Linux 2.6.32-16-generic x86_64
UserGroups:

---
Architecture: amd64
DistroRelease: Ubuntu 10.04
LiveMediaBuild: Xubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100316.1)
Package: ubiquity 2.2.0
PackageArchitecture: amd64
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Tags: lucid
Uname: Linux 2.6.32-16-generic x86_64
UserGroups:

Revision history for this message
Jeff Lane  (bladernr) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Jeff Lane  (bladernr) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : Dependencies.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : GdmLog.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : GdmLog1.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : Lspci.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : PciDisplay.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : ProcModules.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : UdevDb.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : UdevLog.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : XorgLog.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : XorgLogOld.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : Re: [Lucid]Xorg crashes while manual partitioning in Ubiquity in Xubuntu 64

New test on the "Install Xubuntu" option instead of running Ubiquity through live system shows the same problem, changing for now (it seems to ONLY happen while running Ubiquity)

affects: xorg (Ubuntu) → ubiquity (Ubuntu)
summary: - [Lucid]Xorg crashes while manual partitioning in Ubiquity in Xubuntu 64
+ [Lucid]Ubiquity crashes Xorg while running in Xubuntu 64
description: updated
Revision history for this message
Jeff Lane  (bladernr) wrote : Casper.gz

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : Dependencies.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : UbiquityDebug.gz

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : UbiquityDm.gz

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : UbiquitySyslog.gz

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote :

More info:

This is seen in Xubuntu 64 using the Daily Build as of 15 March. I've recreated it 4 times now (three running Ubuquity in the live environment and once in the "Install" environment).

Every time, X crashes after I start running Ubiquity. I've run a couple other apps in the environment without touching Ubiquity and so far have not had an X crash...

This is being seen on a VirtualBox VM configured with 1 processor and 1GB ram with a 16GB disk file.

Revision history for this message
Jeff Lane  (bladernr) wrote : Casper.gz

apport information

description: updated
Revision history for this message
Jeff Lane  (bladernr) wrote : Dependencies.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : UbiquityDebug.gz

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : UbiquityDm.gz

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : UbiquitySyslog.gz

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote :

Update: tried again with Xubuntu 64 daily for 16 March and X still crashes once Ubiquity starts. The new log attachments are from today's failure

Revision history for this message
Jeff Lane  (bladernr) wrote : Casper.gz

apport information

description: updated
Revision history for this message
Jeff Lane  (bladernr) wrote : Dependencies.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : UbiquityDebug.gz

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote : UbiquitySyslog.gz

apport information

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for reporting this issue and the extensive testing of OEM for Xubuntu. Unfortunately, I can not reproduce this issue. I installed Xubuntu using lucid-desktop-amd64.iso dated 2010-03-29 in VBox. It installed without problems. Can you please give me a list of steps to take to try to reproduce the issue?

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

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