[Feisty] xresprobe with anything besides i915 kills X

Bug #92930 reported by Brian Murray
2
Affects Status Importance Assigned to Milestone
xresprobe (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xresprobe

In a terminal execute 'sudo xresprobe i810' or 'sudo xresprobe fglrx' and watch the screen flicker and X restart. I have xresprobe version 0.4.24ubuntu2 installed.

Revision history for this message
Daniel T Chen (crimsun) wrote :

This symptom is not reproducible on an i915GM running a recompiled xserver-xorg-video-i810-modesetting driver from Debian Sid. I'll attempt to reproduce this symptom on the same hardware using xserver-xorg-video-i810 tonight.

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

Actually doing an xresprobe of anything other than i915 kills X and doing the xresprobe with the i915 driver returns nothing in "id:", "res:", and "freq:". There are also a bunch of extraneous carriage returns as I have to scroll up quite a bit to see the output from xresprobe. I added the output of lspci in case it is related to my video card hardware.

description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks for reporting this bug, however you've not provided enough information to debug this issue. Please attach your /etc/X11/xorg.conf and /var/log/Xorg.0.log files, and the output from lspci -vvnn and xresprobe <driver>. Also, if possible please test this against gutsy-beta or newer, in case recent changes have fixed the issue.

Changed in xresprobe:
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

The flickering is expected behavior, the X exiting is not. I've seen the extra carriage returns, which is annoying but not a critical issue. I've been able to use this successfully with -intel on a laptop.

xresprobe behaves different depending on whether it's a laptop and on what driver is in use. The specific tool xresprobe calls, that is probably causing the issue is /usr/share/xresprobe/xprobe.sh <driver>. You can run that separately from xresprobe to try to reproduce the issue.

I've posted a fix for bug 127008, but that will only address issues on intel laptops. However a similar fix may address issues on other platforms - but I'd need the extra info about each platform to be sure.

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

X does not restart anymore when I execute 'sudo xresprobe fglrx' or 'sudo xresprobe i810'. However, 'sudo xresprobe i915' does do some odd things to my gnome-terminal.

Revision history for this message
Bryce Harrington (bryce) wrote :

Okay, maybe we can call this fixed then. But first tell me more about these "odd things" being done to gnome-terminal. A screenshot or photo might be in order.

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

By odd things I mean the extra carriage returns you mentioned in comment 4. I think I had commented on the bug without refreshing the page and therefore didn't see that comment.

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

This bug was fixed with an update and X no longer dies when using the wrong driver.

Changed in xresprobe:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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