should not have to manually do sudo dpkg-reconfigure -phigh xserver-xorg after upgrade

[Geoff123]

After an upgrade from gutsy to hardy alpha5 my monitor would not resume after it had been put in power saving mode. This is only the monitor, the rest of the system worked fine (as confirmed using ssh). This was solved by manually running the command: sudo dpkg-reconfigure -phigh xserver-xorg and then restarting the xserver. Now the monitor will resume when using the keyboard or mouse.

Looks like the xorg.conf file has undergone many changes as it is much smaller now. I don't think the ordinary user should have to open xorg.conf files and run commands to manually reconfigure this stuff.

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

xserver-xorg:
  Installed: 1:7.3+10ubuntu6
  Candidate: 1:7.3+10ubuntu6
  Version table:
 *** 1:7.3+10ubuntu6 0
        500 http://archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

[James Westby (james-w)]

Hi,

It is exactly the aim that the user should not have to do this.

To help fix the issue could you please tell us what you
changed in the xorg.conf to get your monitor to resume?

Thanks,

James

[Geoff123 (gsking1)]

I'm not sure which line is significant to the resume. The two xorg.conf files are attached.
xorg.conf-old-problem = this was the original, worked fine except monitor would not always return from power save
xorg.conf-new = this was generated using the dpkg-reconfigure..

[Geoff123 (gsking1)]

the second file is attached

[James Westby (james-w)]

On Sat, 2008-03-01 at 22:09 +0000, Geoff123 wrote:
> I'm not sure which line is significant to the resume. The two xorg.conf files are attached.
> xorg.conf-old-problem = this was the original, worked fine except monitor would not always return from power save
> xorg.conf-new = this was generated using the dpkg-reconfigure..

Hi,

Thanks for the information.

I would also like to know what video driver you are using
when it works.

The only way I know to get this information is /var/log/Xorg.0.log,
so please attach that file after booting in to a state where
suspend would work.

I suspect that you are now using the intel driver, instead of
the i810 driver.

Thanks,

James

[Geoff123 (gsking1)]

The Xorg.0.log file is attached. It does look like it's using the intel driver now. With the intel driver and the reconfigured xorg.conf file everything works.

Geoff

      ____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

[Timo Aaltonen (tjaalton)]

I'm afraid there is no reliable way to decide which users benefit from automatic reconfiguration on upgrade, since someone could be using a fine-tuned dualscreen setup or restricted drivers..

[James Westby (james-w)]

Hi Geoff,

So, it looks like what you are seeing is a regression in
suspend with the i810 driver, which is fixed by the intel
driver, would you agree?

One interesting test would be to switch the new xorg.conf
to use i810, and make no other changes. That should test
this theory. Would you like to try that?

Thanks,

James

[Geoff123 (gsking1)]

I just tried adding Driver "i810" to the new xorg.conf file and it did not have the problem. I'd be willing to try a few more things out this evening. Is there anything in particular you want me to try?
If the "intel" driver is now becoming the new default (at least in my case) should we spend our time on the i810 driver?
Geoff

----- Original Message ----
From: James Westby <email address hidden>
To: <email address hidden>
Sent: Monday, March 3, 2008 3:11:34 PM
Subject: [Bug 197158] Re: should not have to manually do sudo dpkg-reconfigure -phigh xserver-xorg after upgrade

Hi Geoff,

So, it looks like what you are seeing is a regression in
suspend with the i810 driver, which is fixed by the intel
driver, would you agree?

One interesting test would be to switch the new xorg.conf
to use i810, and make no other changes. That should test
this theory. Would you like to try that?

Thanks,

James

** Changed in: xorg (Ubuntu)
       Status: Incomplete => New

--
should not have to manually do sudo dpkg-reconfigure -phigh xserver-xorg after upgrade
https://bugs.launchpad.net/bugs/197158
You received this bug notification because you are a direct subscriber
of the bug.

      ____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

[James Westby (james-w)]

On Tue, 2008-03-04 at 16:03 +0000, Geoff123 wrote:
> I just tried adding Driver "i810" to the new xorg.conf file and it did not have the problem. I'd be willing to try a few more things out this evening. Is there anything in particular you want me to try?

It would be interesting to add the items back to the xorg.conf
bit by bit, in order to work out what exactly is causing the failure.
Would you be willing to try that?

You could add back a section at a time, or even a few sections
to speed it up.

> If the "intel" driver is now becoming the new default (at least in my case) should we spend our time on the i810 driver?

I don't really know about the situation, but my guess is that intel
is preferred, but either doesn't support all cards, or is not ready
for all yet. Maybe the plan is to force the intel driver at some
point in the future, but it would be good to not have a regression
like the one you experienced in the mean time.

Thanks,

James

[Geoff123 (gsking1)]

James,
I now cannot re-create the original issue. I switched back to the original xorg.conf file (i810 driver) that gave me problems and now it works fine (for the last day). I can only guess that one of the many package updates/changes this last week fixed it. I'll leave it running a little while longer to see what happens.
Geoff

[James Westby (james-w)]

Hi Geoff,

I am closing the bug report as "Invalid". Here this means that it is fixed,
but we don't know what exactly fixed it.

Please re-open the bug if the problem re-occurs, or open another bug
if you hit a different issue.

Thanks,

James