For Feisty, xresprobe is not included in the default installation.  In
theory, this should not be an issue for most people, however I think for
people who don't have xresprobe installed, if they reconfigure Xorg then
the new xorg.conf file could result in incomplete monitor detection, and
thus lead to this bug.  This could also occur if the user installed a
new monitor or video card and re-ran `sudo dpkg-reconfigure xserver-
xorg` without first installing xresprobe.  It could also occur if a user
upgrades from Edgy or Dapper to Feisty, and xresprobe gets uninstalled,
and then the user reconfigures xorg.  As I understand, this was a unique
change for Feisty, and wouldn't affect Edgy or Dapper users since as I
understand xresprobe was installed by default in those.

For gutsy we've altered things such that xresprobe is once again
installed by default, so behavior should at least return to where it was
with Edgy and Dapper.  In at least one dupe of this bug, having
xresprobe present seems to have helped.  See bug 109908.

However, this change only gives us a partial fix; I know there are
additional problems with xresprobe that will crop up even with it
installed.

-- 
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug notification because you are a member of Kubuntu
Team, which is a subscriber of a duplicate bug.

-- 
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

Reply via email to