Ubuntu
lxrandr package

saucy beta 2 could not apply the stored configuration for monitors

Bug #1235201 reported by jerrylamos
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
lxrandr (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Attached is screenshot. Acer Aspire 1 D255E Intel Atom N455
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
Huge window
none of the selected modes were compativle with the following modes:
Trying modes for CRTC 63
CRTC 63 trying mode 1920x1080@60Hz with output at 1366x768@60Hz (pass 0)
.... many lines off the bottom of the screen.

Monito is actually 1920x1080 which is pretty small on a5.5" screen so I usually set it with settings displays to 1360x768 just fine, or use xandr to set it to 1366x768.

Been running development ubuntu since 10.10 and all through 13.10 never saw this problem before.

I can run xandr and fix it, but issued ubuntu-bug as is.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu5
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Oct 4 07:26:03 2013
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
InstallationDate: Installed on 2013-09-28 (5 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
MachineType: Acer AOD255E
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic root=UUID=cc14937c-d48f-48fa-8777-b50adfef3800 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/16/2010
dmi.bios.vendor: Acer
dmi.bios.version: V3.12(DDR3)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE02_PT
dmi.board.vendor: Acer
dmi.board.version: V3.12(DDR3)
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V3.12(DDR3)
dmi.modalias: dmi:bvnAcer:bvrV3.12(DDR3):bd12/16/2010:svnAcer:pnAOD255E:pvrV3.12(DDR3):rvnAcer:rnJE02_PT:rvrV3.12(DDR3):cvnAcer:ct10:cvrV3.12(DDR3):
dmi.product.name: AOD255E
dmi.product.version: V3.12(DDR3)
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Fri Oct 4 07:22:55 2013
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 25042
 vendor AUO
xserver.version: 2:1.14.2.901-2ubuntu7

Revision history for this message
jerrylamos (jerrylamos) wrote :
Revision history for this message
Chris Wilson (ickle) wrote :

The mode you picked is not present in the EDID, but it is a standard GTF mode, and you have a GTF monitor... I suspect that they used to be added...

Revision history for this message
Chris Wilson (ickle) wrote :

I suspect one of the key commits is:

commit dc498b433f36af5d2de3065e7c64cdb575385d81
Author: Adam Jackson <email address hidden>
Date: Mon Feb 8 15:23:04 2010 -0500

    xfree86: If the driver found modes on an output, don't add more

    Inferring modes from sync ranges is only valid if the monitor says it's
    valid. If the monitor says it's valid, then we'll have already added
    those modes during EDID block parse. If it doesn't, then we should
    believe it.

    If there's no EDID for an output, but sync ranges from the config, we'll
    still add default modes as normal.

    Reviewed-by: Alex Deucher <email address hidden>
    Signed-off-by: Adam Jackson <email address hidden>

Revision history for this message
Chris Wilson (ickle) wrote :

For example, I can not see where the default GTF modes are inferred from the EDID...

Revision history for this message
Chris Wilson (ickle) wrote :

Can you check whether doing

cat > /etc/X11/xorg.conf.g/vga.conf <<EOF
Section "Monitor"
  Identifier "Monitor0"
  Option "DefaultModes" "true"
EndSection

Section "Device"
  Identfier "Device0"
  Option "monitor-VGA1" "Monitor0"
EndSection
EOF

restores the missing modes?

Revision history for this message
jerrylamos (jerrylamos) wrote :

Well, this setup doesn't have xorg.conf.g or xorg.conf. I used to use them all the time but ubuntu deleted xorg.conf.
so I tried making an xorg.conf with the data which rebooted into into low graphics mode.
Let me see if I can make a folder xorg.conf.g and put a member vga.conf into it.

Revision history for this message
jerrylamos (jerrylamos) wrote :

Tried again with /etc/X11/xorg.g/vga.conf. No luck. What I do to get a usable desktop is:

#!/bin/bash
xrandr --newmode "1366x768_60.00" 85.25 1366 1440 1576 1784 768 771 781 798 -hsync +vsync
xrandr --addmode VGA1 "1366x768_60.00"
xrandr --output VGA1 --mode "1366x768_60.00"

Previously with ubuntu, did that once, works right away, then next boot got me 1366x768 sometimes.

Sometimes in ubuntu development making a .xprofile with that would work sometimes not.

Or else go into Settings Displays and set 1360x768 which has been pretty reliable until last few days.

Revision history for this message
Chris Wilson (ickle) wrote :

Yikes, mistyped. That should have been /etc/X11/xorg.conf.d/vga.conf

If you grep Monitor0 /var/log/Xorg.*.log that should confirm whether or not the config is picked up.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

isn't this a dupe of your own bug #1232426?

Revision history for this message
jerrylamos (jerrylamos) wrote :

Chris, with /etc/X11/xorg.conf.d/vga.conf as you specified booted right up with no problem on configuration.

No big window top to bottom full of lines complaining about could not apply stored configuration. Yay.

 cat /var/log/Xorg.0.log | grep onitor
[ 19.831] (**) | |-->Monitor "<default monitor>"
[ 19.831] (==) No monitor specified for screen "Default Screen Section".
 Using a default monitor configuration.
[ 19.936] (II) intel(0): Output LVDS1 has no monitor section
[ 20.036] (II) intel(0): Output VGA1 has no monitor section
[ 20.036] (II) intel(0): Output VIRTUAL1 has no monitor section

Now I still have bug #1234839 which is as far as I can tell when the launcher unhides it has a black background, and when the launcher hides again the vertical black bar is left. The wallpaper is not restored for that section.

Timo, I reported bug#1232426 on Lubuntu. I set the display configuration to 1360x768, built in monito orr, save it, working O.K., reboot and get back to the default 1920x1080 (squint) built in monitor on. No big warning messages about could not apply. stored configuration like I get with 1235201.. So on every boot I have to set the configuration again. You people would know whether this is a manifestation of the same problem.
Come to think of it, I could put this config.d/vga.conf on Lubuntu to see what happens.

This bug 1235201 on Ubuntu/unity gets a huge window taking up 1/3 of the center of the screen top to bottom many many lines and says it "could not apply the stored configuration for monitors". Comment #1 in this bug has a screenshot of the picture.

Chris I can do some limited fix testing - I've never recompiled the kernel.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

the configurator is not part of xorg, so if you could move the other bug to whatever component lubuntu/lxde has that would be nice

Revision history for this message
jerrylamos (jerrylamos) wrote :

On Timo's comment, anyone have any idea what the component lubuntu/lxde uses to save the configuration? I do Preferences Monitor to set it, but what component does that?

Timo Aaltonen (tjaalton)
affects: xorg (Ubuntu) → lxrandr (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lxrandr (Ubuntu):
status: New → Confirmed
Revision history for this message
Anton Asche (aasche) wrote :

If anyone can confirm that LXRandR uses ~/.config/autostart/lxrandr-autostart.desktop to save the settings, please have a deeper look at this file:

Exec=xrandr --output LVDS --mode 1680x1050 --rate 60.1 --output VGA-0 --off

doesn't work, change it to:

Exec=sh -c 'xrandr --output LVDS --mode 1680x1050 --rate 60.1 --output VGA-0 --off'

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.