displayconfig-gtk recognizes the correct resolution but uses 640x480 instead

[unggnu]

Binary package hint: displayconfig-gtk

Displayconfig-gtk recognizes and shows the correct resolution but if I change driver or something like that and then accept with Ok displayconfig-gtk adds this "modeline "640x480@60" 25.2 640 656 752 800 480 490 492 525 -vsync -hsync" to monitor section and changes Screen\Display section to use the 640x480 mode. Even the new new Intel driver which works fine without xorg resolutions uses 640x480 after this changes.

[unggnu (unggnu)]

Btw. changing to i810 driver works with displayconfig-gtk but it is not possible to switch back to intel driver. After selecting it the correct one is shown in Driver box but after accepting with Ok the i810 driver is still in xorg.conf listed. Should I a make a new bug report for this?

[Sebastian Heinlein (glatzor)]

Thanks, it is always a good idea to use separate bug reports for each issue.

[Evandro Fernandes Giovanini (evandrofg)]

I have the same problem.

Attached is the file created by displayconfig-gtk.

[unggnu (unggnu)]

@Evandro Fernandes Giovanini
Maybe you could post a screen shot or your default resolution so maybe there is a coherence.

1366 isn't a multiple of 8 so this could be the problem.

[Sebastian Heinlein (glatzor)]

Could you please append the output of the following commands:

sudo ddcprobe

sudo get-edid | parse-edid

[Sebastian Heinlein (glatzor)]

What kind of monitor do you use? It seems to be broken.

[unggnu (unggnu)]

I have a Sony TX2 laptop with an 1366x768 LED Display. It seems that xrandr gets the correct data but not ddcprobe.

[unggnu (unggnu)]

Maybe it has something to do with the issue described under http://en.wikipedia.org/wiki/Extended_display_identification_data#Limitations

[Evandro Fernandes Giovanini (evandrofg)]

My laptop is a Lenovo 3000 N100, 1280x800 15.4 screen.

gutsy beta detects it as a 1024x768 (older versions worked correctly). After setting the right value with displayconfig-gtk it changes it correctly on-the-fly but writes a bad xorg.conf, so the next startup of the Xorg server is incorrect.

[Sebastian Heinlein (glatzor)]

Evandro, please append your xorg.conf after performing the changes with displayconfig-gtk. If your bug is different from this one please open a new report.

[David Fokkema (dfokkema)]

I would guess not. Please post your xorg.conf, Evandro, but it is exactly my problem. That is, the displayconfig-gtk changes resulting in a bad xorg.conf. The initial detection is another problem.

[Tim Hull (thully)]

Could this be looked at? Currently, changing *anything* in displayconfig-gtk results in a bad xorg.conf for me...

[David Fokkema (dfokkema)]

With only 1 day to go... I'm afraid this won't make it anyway and therefore will receive proper attention only after the release. I understand, but this is serious for lots of users, so please, could this be released as an update as soon as possible? And please, could this issue be addressed in the release notes? Just so that we won't turn away lots of users who will otherwise think Ubuntu as a whole is seriously broken (displayconfig-gtk is, at the moment).

Anyway:

1. Does this problem only apply to intel chipsets? Is there anyone out there having the same problem with an ati or nvidia or whatever card?
2. Does this problem only apply to laptop users (LVDS monitor attached?)

[Tim Hull (thully)]

Honestly, I'd remove the package - I've heard many reports of breakage on
many configurations, and better to ship nothing at all than the horrible
breakage that is displayconfig-gtk.

On 10/17/07, David Fokkema <email address hidden> wrote:
>
> With only 1 day to go... I'm afraid this won't make it anyway and
> therefore will receive proper attention only after the release. I
> understand, but this is serious for lots of users, so please, could this
> be released as an update as soon as possible? And please, could this
> issue be addressed in the release notes? Just so that we won't turn away
> lots of users who will otherwise think Ubuntu as a whole is seriously
> broken (displayconfig-gtk is, at the moment).
>
> Anyway:
>
> 1. Does this problem only apply to intel chipsets? Is there anyone out
> there having the same problem with an ati or nvidia or whatever card?
> 2. Does this problem only apply to laptop users (LVDS monitor attached?)
>
> --
> displayconfig-gtk recognizes the correct resolution but uses 640x480
> instead
> https://bugs.launchpad.net/bugs/137792
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[David Fokkema (dfokkema)]

On Wed, 2007-10-17 at 08:02 +0000, Tim Hull wrote:
> Honestly, I'd remove the package - I've heard many reports of breakage on
> many configurations, and better to ship nothing at all than the horrible
> breakage that is displayconfig-gtk.

Of course, that depends... If it is _only_ intel for which
displayconfig-gtk is broken, I'd rather not have it removed. Of course,
if you mean by many configurations, also ati and nvidia and others, the
problem is more serious.

[unggnu (unggnu)]

I guess that 640x480 is better than a non working X so you have to work with console which is pain for Newbies. Since displayconfig-gtk is used in rescue mode it is needed and afaik it produces a working xorg with maybe wrong resolution but this could be fixed with a text editor and irc support.
Btw. the easiest way to fix it is to don't save modesetting at least for intel cards and of course save the resolution that is recognized through displayconfig-gtk on start since dccprobe seems to produce garbage on most widescreen laptops.

[David Fokkema (dfokkema)]

On Wed, 2007-10-17 at 09:09 +0000, unggnu wrote:
> I guess that 640x480 is better than a non working X so you have to work

If I use the live cd and install, it works in 1024x768. If I try to set
1280x800 (my maximum resolution) displayconfig-gtk resets it to 640x480.
So I don't really agree with your statement, ;-)

> with console which is pain for Newbies. Since displayconfig-gtk is
> used in rescue mode it is needed and afaik it produces a working xorg
> with maybe wrong resolution but this could be fixed with a text editor
> and irc support. Btw. the easiest way to fix it is to don't save
> modesetting at least for intel cards and of course save the resolution
> that is recognized through displayconfig-gtk on start since dccprobe
> seems to produce garbage on most widescreen laptops.

In displayconfig-gtk, manually setting the monitor (generic -> lcd panel
1280x800, don't forget to set the widescreen option) and then choosing
1280x800 works for me. Using an external monitor is another story...

[unggnu (unggnu)]

For standard resolution changes "Screen Resolution" should be used which works fine. Btw. the 1024x768 resolution bug on Intel hardware has fixed afaik.

[Sebastian Heinlein (glatzor)]

Why should displayconfig-gtk be broken for intel chip sets? There seems to be a problem with using the live data from the screen in the guidance backend. It will take some time to debug this issue. Since I am currently having night shift don't expect a solution in this week.

[Sebastian Heinlein (glatzor)]

Just to make it clear: displayconfig-gtk is available in the fail safe mode, but does not handle it.

[David Fokkema (dfokkema)]

On Wed, 2007-10-17 at 14:19 +0000, Sebastian Heinlein wrote:
> Why should displayconfig-gtk be broken for intel chip sets? There seems
> to be a problem with using the live data from the screen in the guidance
> backend. It will take some time to debug this issue.

I don't know... The chipsets mentioned were all intel, I believe, so I
thought that maybe that had something to do with it. I'm not at all
knowledgeable about displayconfig-gtk and its inner workings, :-/

> Since I am
> currently having night shift don't expect a solution in this week.

Sure, I understand. When it is fixed, will it be released as a regular
update to gutsy, or should we only expect this for hardy?

[Bryce Harrington (bryce)]

Thank you for reporting this bug and for your efforts to make Ubuntu better. As Xorg has improved this past year, an unfortunate side effect of these improvements is that it has rendered several design assumptions in displayconfig-gtk obsolete. So, starting with Hardy we are no longer putting displayconfig-gtk forth as a primary configuration tool, and are putting our development focus into the Screen Resolution applet. As a result, we do not plan to fix this bug and thus are closing it.

For more background on this change, please see this page: [WWW] https://wiki.ubuntu.com/X/DisplayConfigGtk