kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

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.

** This bug is no longer a duplicate of bug 565305
   display/monitor settings not persistent

** Tags added: needs-kernel-logs

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/566683

Title:
  display configuration isn't saved

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/566683/+subscriptions