Ubuntu
xresprobe package

output crash during installation with Gutsy Tribe5 alternate (Santa Rosa)

Bug #135206 reported by Kevin Wang
12
Affects Status Importance Assigned to Milestone
xresprobe (Ubuntu)
Incomplete
Medium
Unassigned
Ubuntu ubuntu-7.10-beta

Bug Description

Binary package hint: debian-installer

when trying to install the tribe5 by using test mode with alternate CD, the screen will turn to strange (turn to black with something but can not read) during the install progress sometime. The install may success with just click “return”, but sometimes may failed, because we don't know what happened, I found this issue with Tribe4 last Friday, and found the same issue in Tribe5 today, no such issue in Tribe3. it is not 100% reproducible.

Revision history for this message
Kevin Wang (kevin-xuepu-wang) wrote :

here is the snapshot after switch to tty5 when issue happened

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Did you submit an attachment to your bug report via e-mail? If so the e-mail interface to Malone, Ubuntu's bug tracker, does not currently accept attachments via e-mail. Could you please add the attachment by visiting this bug's web page? Thanks in advance.

Changed in debian-installer:
assignee: nobody → brian-murray
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Kevin Wang (kevin-xuepu-wang) wrote :

not text log, it is just the picture

Brian Murray (brian-murray)
Changed in debian-installer:
assignee: brian-murray → nobody
status: Incomplete → Triaged
Revision history for this message
Colin Watson (cjwatson) wrote :

Another instance of the well-known xresprobe breakage. Bryce, please have a look at this and see if we can make it work better here.

Changed in debian-installer:
assignee: nobody → bryceharrington
Revision history for this message
Bryce Harrington (bryce) wrote :

There is insufficient information to troubleshoot this issue. When reporting X bugs, please always attach your xorg.conf, Xorg.0.log, and the output from lspci -vvnn. Also, it would make triaging easier if you attach the files individually rather than in a tar file, as this adds extra steps for verifying if the bug has sufficient info.

Because this bug did not appear in Tribe3, that suggests it's not an xresprobe bug. My guess would be that it is caused by one of the drivers that was updated since Tribe4, but without the config and log files it is impossible to say for sure.

Changed in xresprobe:
status: Triaged → Incomplete
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Deferring to Beta since this report still needs more info.

Revision history for this message
Kevin Wang (kevin-xuepu-wang) wrote : RE: [Bug 135206] Re: output crash during installation with Gutsy Tribe5alternate

Hi,
The issue is happened DURING the installation, and the installation is
NOT completed. We can not read anything through the screen when the
issue happened, even switch to TTY.

And I don't think we could get the xorg.conf, xorg.0.log at that time.
It is quite easy to reproduce it. Just install it and then monitor.

Thanks
Kevin

Revision history for this message
Xiaoyang Yu (xiaoyang-yu) wrote : Re: output crash during installation with Gutsy Tribe5 alternate

This bug occurred when using text mode installation from alternate CD. Is it related to X? How to obtain xorg.conf, xorg.0.log files during the text mode installation?

The previous attached tar ball contains two pictures as screen shot. I untared it and put them in the attachment.

Revision history for this message
Xiaoyang Yu (xiaoyang-yu) wrote :
Bryce Harrington (bryce)
Changed in xresprobe:
assignee: bryceharrington → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.