Chris Weiss, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/922262/comments/4 regarding you no longer have the original
hardware. For future reference you can manage the status of your own
bugs by clicking on the current status i
additionally, this was for configuring an LTSP thin client, apport is
not available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922262
Title:
X -configure fails, leaves valid conf anyway
To mana
I no longer have the hardware to test it, but unless the "Number of
created screens does not match number of detected devices." error
condition was changed to a warning then i suspect the issue still
exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Chris Weiss, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/cur
The xorg.conf generated on my system has four screen sections, but I
only have 2 monitors?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922262
Title:
X -configure fails, leaves valid conf anyway
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922262
Title:
** Package changed: ubuntu => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922262
Title:
X -configure fails, leaves valid conf anyway
To manage notifications about this bug go
