display/monitor settings not persistent

I can confirm this bug.

In addition to the above, I have found the displays also reset every time the screensaver comes on. In the course of a day I am finding myself reconfiguring my displays in upwards of 50 times a day. Bug did not exist in 9.10 (display settings were indeed remembered correctly and were not reset).

Shouldn't this bug have an importance of High at least? Many people will need to be able to save monitor changes, it's a basic ability of a desktop since at least Windows 95 times.

I have just searched and it seems there appears to be a number of other reports of this same problem:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/566683 (same)
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/562468 (same effect, perhaps different cause)
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/551475 (similar)
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/550592 (same)

I've just noticed that this bug and the duplicate both have Asus eeePC's... so do I, an Asus 1000HE with an Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03), same as the reporter. Maybe this bug is particular to these Intel graphic chips? Although as above there are also people with AMD and nVidia cards that seem to be experiencing similar problems with the display settings not being saved, so I'm not sure.

P.S.: Still occurring with latest Lucid updates as of April 26th.

Those interested, I posted a workaround on my bug report. I will post here so you can work in the meantime!
using the following script in /etc/X11/Xsession.d/45custom_xrandr_settings:
Code:

EXTERNAL_OUTPUT="VGA1"
INTERNAL_OUTPUT="LVDS1"

xrandr |grep $EXTERNAL_OUTPUT | grep " connected "
if [ $? -eq 0 ]; then
    xrandr --output $INTERNAL_OUTPUT --off --output $EXTERNAL_OUTPUT --auto
else
    xrandr --output $INTERNAL_OUTPUT --auto --output $EXTERNAL_OUTPUT --off
fi

What the script does is disable my LVDS display when I connect the external monitor.

@omarista
ty, this one makes life easier again...

this bug seems to be solved for me if using xorg-edgers repository and kernel 2.6.34 based on rc6 from this repo...
can anyone confirm?

marijus, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]