Hmm, the Xorg.0.log indicates no EDID is being received from the
monitor. Presumably it was auto-detecting previously because it was
getting the EDID.
I've never heard of wine game modechanges causing corruption to the EDID
itself (it's usually firmware, although some monitors have writable
EDID; can't confirm from the manual if this model is like that), but I
suppose anything's possible. However, have you changed anything on the
hardware end? E.g., using any adapters, changed cords or video cards,
modified anything in BIOS, etc.?
You might try hitting the factory reset button on the monitor to see if
it brings the EDID back.
Two useful ways to examine EDID:
1. xrandr --verbose; This lists edid in a hexadecimal block. This
corresponds to what X gets.
2. read-edid package; Run it as `get-edid | parse-edid`. This gets the
EDID directly from the hardware.
If one gives valid EDID data but the other doesn't, then it's a
legitimate X/kernel bug. If neither produce any EDID info, then it
starts looking more like a busted monitor. (The latter can be worked
around via xorg.conf and/or replacement EDID.)
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/973358
Title:
Monitor lost Resolution from 1920x1080 to 1024x768.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/973358/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
