when I open my laptop lid, gsd changes my resolution

[Steve Langasek]

Binary package hint: gnome-settings-daemon

When I close and reopen my laptop lid, gnome-settings-daemon (or something that talks to it) changes my resolution from the default 1280x800 to 1024x768, which is ugly and annoying.

$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 4096 x 4096
VGA1 disconnected (normal left inverted right x axis y axis)
   1680x1050 60.0
LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
   1280x800 60.0*+ 50.0
   1024x768 85.0 75.0 70.1 60.0
   832x624 74.6
   800x600 85.1 72.2 75.0 60.3 56.2
   640x480 85.0 72.8 75.0 60.0 59.9
   720x400 85.0
   640x400 85.1
   640x350 85.1
DVI1 disconnected (normal left inverted right x axis y axis)
$

Confirmed that this is g-s-d at work by killing g-s-d and verifying that my resolution stays the same.

ProblemType: Bug
Architecture: amd64
Date: Mon Sep 21 13:53:38 2009
DistroRelease: Ubuntu 9.10
Package: gnome-settings-daemon 2.27.92-0ubuntu2
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SourcePackage: gnome-settings-daemon
Uname: Linux 2.6.31-10-generic x86_64

[Chris Coulson (chrisccoulson)]

Thank you for your bug report. Could you please kill gnome-settings-daemon, and then restart it with:

gnome-settings-daemon --no-daemon --debug 2>&1 | tee g-s-d.log

When it is running, please try opening/closing your lid and seeing if it prints anything out (there are a few debug statements in the xrandr plugin but maybe not enough to conclude if it is doing anything here, although it might give a clue)

Thanks!

[James Westby (james-w)]

On Mon Sep 21 22:19:00 UTC 2009 Chris Coulson wrote:
> Thank you for your bug report. Could you please kill gnome-settings-
> daemon, and then restart it with:
>
> gnome-settings-daemon --no-daemon --debug 2>&1 | tee g-s-d.log
>
> When it is running, please try opening/closing your lid and seeing if it
> prints anything out (there are a few debug statements in the xrandr
> plugin but maybe not enough to conclude if it is doing anything here,
> although it might give a clue)

Also, ~/.config/monitors.xml could be useful.

   [ apport hook? ]

Thanks,

James

[Steve Langasek (vorlon)]

monitors.xml attached. Note that the contents of this file are largely not my doing, and now that I know this is there, I'll probably nuke most of it since it doesn't work the way I want it to in any case. :-)

I think to reproduce this bug, I have to have plugged in my external monitor during the current session, so the log output will have to wait until I'm back to my desk.

[James Westby (james-w)]

On Mon Sep 21 23:41:18 UTC 2009 Steve Langasek wrote:
> monitors.xml attached. Note that the contents of this file are largely
> not my doing, and now that I know this is there, I'll probably nuke most
> of it since it doesn't work the way I want it to in any case. :-)

I don't see an attachment?

Thanks,

James

[Steve Langasek (vorlon)]

abracadabra!

[James Westby (james-w)]

On Tue Sep 22 05:17:10 UTC 2009 Steve Langasek wrote:
> abracadabra!
>
> ** Attachment added: "monitors.xml"
> http://launchpadlibrarian.net/32230221/monitors.xml

Thanks.

The last configuration has

<output name="LVDS1">
<vendor>LEN</vendor>
<product>0x4050</product>
<serial>0x00000000</serial>
</output>

and I'm not sure what that will do as the width and height are
not specified. I'm not sure whether it would pick that configuration
either. I'm not even sure if this file has anything to do with
your problem.

Perhaps you could try deleting the whole of the last <configuration>
stanza?

Thanks,

James

[Victor (psycovic)]

I also have this problem. In addition, I have a script that runs every few seconds using xrandr to check if my laptop is docked, and thus changes to the correct resolution for my external. When I'm not docked and I close my lid, xrandr ends up outputting the wrong resolution (ie, it thinks it's at 1400x1050, when it's obviously not). I have to go into nvidia-settings to change things back to normal.

[Alle (alessandro-demaria)]

Hello,

I have the same problem on Ubuntu Kermic 10.4 beta 2 (latest updates at 18/04/2010)

[Jean-Baptiste Lallement (jibel)]

Steve, this bug was reported in Karmic, set to 'incomplete' nearly 1 year ago, tagged as regression-potential and there hasn't been any activity in it recently. Is it still an issue in lucid and maverick ?
Thanks in advance.

[Jean-Baptiste Lallement (jibel)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".
Thanks again!

[Steve Langasek (vorlon)]

Fixed, actually. Sorry for not following up; seems to have gone away post-karmic.