display configuration isn't saved

[omriasta]

Binary package hint: gnome-control-center

I am running Ubuntu 10.04 on an eee-pc 1002HA.
In Jaunty I would connect an external screen and turn off the built in screen. Once I did this the config was saved and everytime I connected the external screen, my built in would shut off automatically.
After upgrading, the built in screen always turn on. This causes compiz to crash (since it can't work with resolutions above 2048x2048). I can lower the resolution of the built in screen and then turn on compiz and then disable the built in screen.
Any changes (open the Monitors configuration utility, locking the screen, screen turns off after inactivity) defaults all the settings which results with the built in screen turning on, compiz crashes and the resolutions go back to default.
If I change the layout of the monitors (top-bottom instead of side by side) I can run compiz but inactivity/locking the screen immediately defaults the configuration and compiz crashes.
The behavior in Jaunty was the correct one.
Description: Ubuntu lucid (development branch)
Release: 10.04

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-control-center 1:2.30.0-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Mon Apr 19 10:25:15 2010
ExecutablePath: /usr/bin/gnome-display-properties
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
---
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: omri 2380 F.... pulseaudio
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=e323bb43-47fb-472f-961e-eb6ef307cf9c
InstallationDate: Installed on 2013-06-01 (74 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: LENOVO 3443CTO
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-27-generic N/A
 linux-backports-modules-3.8.0-27-generic N/A
 linux-firmware 1.106
Tags: raring
Uname: Linux 3.8.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
WifiSyslog:

dmi.bios.date: 04/29/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G6ET96WW (2.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3443CTO
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG6ET96WW(2.56):bd04/29/2013:svnLENOVO:pn3443CTO:pvrThinkPadX1Carbon:rvnLENOVO:rn3443CTO:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3443CTO
dmi.product.version: ThinkPad X1 Carbon
dmi.sys.vendor: LENOVO

[omriasta (omriasta)]

Also the default resolutions:
External screen 1280x1024
built in screen 1024x600

[Pedro Villavicencio (pedro)]

could be this somewhat related to bug 566862 ?

[omriasta (omriasta)]

Nope, the problem isn't how the screen is detected or the resolutions. Both screens work fine and I am able to workaround the issue and get compiz to work on individual screens and even on both together.
The bug described is that the configuration for the external monitor is not saved. The position of the external monitor (side by side/top bottom) and if the screen is on/off is not saved. It resets every time I open gnome-display-properties or lock my screen or logoff or switch compiz on/off.

[Sebastien Bacher (seb128)]

Thank you for your bug report, could you add your .config monitors.xml to the bug?

[omriasta (omriasta)]

Here it is...sorry was out for a few. this is how the monitors.xml file is after I apply the workaround (after I switch the resolution, enable compiz, disable built-in lcd) does it change when I do this? Do you need a copy of this file when it is at the default setting?

[Sebastien Bacher (seb128)]

The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

[Sebastien Bacher (seb128)]

I can't make a sense of this bug, seems there are several issues mixed, workaround, compiz changes, display changes, configuration, it's not a clear view of the issue and the number of parameters you change makes hard to figure what is wrong. I will let somebody having the issue take that to GNOME where the code writter can try to understand the steps

[omriasta (omriasta)]

The bug isn't in compiz or any of the other programs it just affects them.
The bug is that the Monitors Applet doesn't keep any settings.
If I choose to turn off a monitor in the applet and then lock the screen, this setting is lost. If I choose to change the resolution or the configuration (if the screens are side by side or top/bottom) and lock my screen, it goes back to the default.
The behavior is the same when enabling compiz (all settings go back to default).
The problem is only the fact that the applet does not save these settings.

[omriasta (omriasta)]

Found a solution for myself 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.
I think the default behavior for gnome-display-properties should be to save the last config. It worked like that in Jaunty. Now xrandr turns on all available displays whenever it runs (when you lock the screen/logoff/run the gnome-display-properties applet).

[Sebastien Bacher (seb128)]

reassigning to xserver since if screen setting change on suspend, resume or screen lock it seems an xorg issue

[Bryce Harrington (bryce)]

Unfortunately the bug report does not indicate what video driver is in use, but presumably it's one of the open source drivers which is using Kernel modesetting. Since the kernel does modesetting, issues like this with the monitor modes or resolution or output enabling really are kernel drm bugs now. Sorry for the pingpong.

[Jeremy Foshee (jeremyfoshee)]

Hi omriasta,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[omriasta (omriasta)]

using kernel 2.6.33-02063302-generic
Problem persists. How to reproduce: Disable the LVDS screen in gnome-display-properties, lock the screen (Ctrl+Alt+L), LVDS turns back on.

[marijus (marijus73)]

using kernel 2.6.34-999.201004261005 from mainline daily... Problem persists...

[penalvch (penalvch)]

omriasta, 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.

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

apport information

[omriasta (omriasta)]

Please ignore, I actually am using a different laptop now and don't have this problem anymore. Bug can be closed.

[penalvch (penalvch)]

omriasta, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/566683/comments/32 regarding this is fixed with your new hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.