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?
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?