*** This bug is a duplicate of bug 27667 ***
https://bugs.launchpad.net/bugs/27667
Hi all,
The confirmers in this bug report are all seeing a variety of different
bugs. Let me break things out:
1. Stéphane Graber and several others, I believe you may be seeing bug
27667. 27667 shows up for LCDs that ddcprobe reports as having "analog"
connections. (In your case it is saying "input: sync on green, analog
signal.") When you run xresprobe, it shows the monitor as a "crt" and
returns a list of resolutions missing the correct (preferred) one.
Generally, if simply adding the correct resolution for your LCD to
xorg.conf by hand fixes it, then that's a good sign it's 27667 at work.
Good news is I have a fix for 27667, so you should all be in good shape
for Gutsy.
Because of this, I am marking this bug a dupe. However some of the
confirmers are reporting different issues, and I'd like to address each
of these, because they're unrelated:
2. Filip, the 1440x1440 detection is really wild, but you're not alone;
it's bug 115220. I'm not sure what's going on here but it's probably
something that can be sorted out. Please add details about your
situation to that bug so we can investigate it further.
3. Václav Šmilauer, what you describe sounds different from the prior
two cases. Buggy firmware is certainly not unique, however I'd want to
doublecheck it's not just #1 first. If the solution for 27667 doesn't
solve the issue for you, then I'd like you to open a new bug with as
many details as possible (output from ddcprobe, xresprobe, lspci -vvnn,
uname -a, Xorg.0.log, and xorg.conf).
4. Nick Marsh, your "edidfail" issue is distinct from the prior three,
but also not uncommon. It is bug #94994. I don't know what's up with
this one. Anyone experiencing this issue, please add as much info as
possible to 94994. Like, is it an LCD? Is it connected via VGA or DVI,
or some other way? If it's DVI, then if you use a DVI->VGA connector,
does ddcprobe detect it properly? Does it get detected properly with
other Linux or Windows operating systems? If you install the read-edid
package, then what does `get-edid | parse-edid` say?
5. Adilson Oliveira, your issue sounds distinct from 1-2, because you
cannot simply manually add the resolution but must add an option. I'm
not sure whether its related to 3 or 4; I'd need to see your output from
ddcprobe to be sure. But my guess is you're seeing an independent bug
particular to your hardware models.
6. Jelle de Jong, your issue is more to do with dpi's. These are well
reported elsewhere, but I don't know offhand which matches your case.
Certainly part of that issue is that the resolutions and display sizes
are incorrect, but in general that issue is separate from this
particular one.
7. Will Daniels, your issue is a sub-bug of 27667. In the CRT
resolution selection logic, aside from being a poor design, it also had
a couple bugs in its implementation, including a sorting error that can
result in x900 being preferred over x1050. (In fact, for me, that bug
plus the main bug in 27667 canceled each other out, resulting in me
getting the right default resolution, but for the wrong reason!) Good
news is that removal of the CRT logic in the 27667 fix, also fixes this
issue as well.
Anyway, in summary, the original bug in this thread is solved and will
work properly in Gutsy. The issue is unrelated to whether the monitor
is HD or not, it's just more noticeable for these monitors. The issue
really has to do with "analog" connected LCD's. And aside from this,
many of the people reporting on this thread are actually seeing
unrelated bugs; I don't know if they'll be fixed for Gutsy, but if not
hopefully the new X configuration utilities will put the tools in hand
to address them as well.
--
[Feisty] Wide screen not correctly detected (16/10)
https://bugs.launchpad.net/bugs/67369
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
