Ubuntu 15.10 Could not apply the stored configuration for monitors

Bug #1511247 reported by Crapouille
76
This bug affects 15 people
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

I just did a fresh install of ubuntu 15.10 on my Nuc5i5ryh with a iiyama Prolite B2888UHSU and everytime I boot I get the message "Could not apply the stored configuration for monitors". When I kill the message it puts me back on a undesired resolution, and I have to set the resolution setting up again.

Also when I set up the "Displays" settings , it shows screen resolution that souldn't be there (4:3, 16:10..).

I tried removing monitors.xml just in case, doesn't work.

I ran xrandr and sudo get-edid|parse-edid (see attached), it shows inconsistency between edid data and xrandr.

I had Ubuntu 15.04 just before and I hadn't this error.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.19.1-0ubuntu4
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
CurrentDesktop: Unity
Date: Thu Oct 29 16:19:11 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1626] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:2057]
InstallationDate: Installed on 2015-10-26 (2 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2015
dmi.bios.vendor: Intel Corporation
dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722
dmi.board.name: NUC5i5RYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H40999-502
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-502:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Thu Oct 29 12:57:07 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 28932
 vendor IVM
xserver.version: 2:1.17.2-1ubuntu9

Revision history for this message
Crapouille (skynner64) wrote :
description: updated
Revision history for this message
Crapouille (skynner64) wrote :
Revision history for this message
Crapouille (skynner64) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg (Ubuntu):
status: New → Confirmed
Changed in xorg (Ubuntu):
importance: Undecided → High
Revision history for this message
Duane Gaul (duane3131) wrote :

I also have this problem on my PC when I upgraded to Ubuntu 15.10. I'm using a Samsung 32" television as a monitor. Upon bootup, it can't find the 16080 x 1050 (16:10) display, so it defaults to (16:9).

Revision history for this message
fariazz (fariazz) wrote :

Are there any workaround in the meantime?

Revision history for this message
Matthias Weiler (matthias-weiler) wrote :

I have not tried it myself yet but there is a workaround mentioned on askubuntu.[0]
Delete your ~/.config/monitors.xml

[0] https://askubuntu.com/questions/23869/could-not-apply-the-stored-configuration-for-the-monitor

Revision history for this message
Leon Li (leon-li-1025) wrote :

Deleting ~/.config/monitors.xml will cause Ubuntu to load the default Resolution and Rotation values on restart.

If you want a non-default resolution and rotation and avoid this error on startup, you would need to manually change Resolution and Rotation on EVERY boot and delete ~/.config/monitors.xml on EVERY boot.

Revision history for this message
fariazz (fariazz) wrote :

I tried what deleting ~/.config/monitors.xml on startup, but it seems to be re-created when you plug/unplug the second monitor.

What works for me is removing the file on startup, but also created a cron job that runs every 2 minutes and deletes this too.

So when I unplug the screen, before I plug it back, the file will already be gone and my session won't crash.

Revision history for this message
Robin (robin-a-hodgson) wrote :

Got the same problem as described above by Crapouille.
Using an Intel NUC with 42" LG TV screen (1920 X 1080) and Ubuntu 15.10.
The image overflows but will fit with lower resolution, requiring changing DISPLAY settings.
But at every startup the same annoying message appears again requiring re-entering the DISPLAY settings.
Blindly deleting files may be a work around, but it is not really the solution.

Revision history for this message
Matthias Weiler (matthias-weiler) wrote :

I think the issue (if it's the same) is even more strange in my case.
At startup the right resolution and rotation is used but I still get the "Could no apply.." message. As soon as I press close on that message, the display config is reset to "standard" - only one screen working.
It's really annoying to reconfigure the screens at every boot. :/

Revision history for this message
Robin (robin-a-hodgson) wrote :

You describe more precisely exactly the same as I am seeing, with just a single screen.
Now, being a total Newbie to Linux, I thought initially it was pilot error.

I also need to use the Command Line commands, and after setting the
screen size, I used the GUI desktop "Terminal" to access the login ......
this works OK (against the purple background).
But if I access the Command Line via "Ctrl+Alt+F1" (as recommended)
the screen changes size back to overflowing (black background) and
so you cannot see the prompts, which overflow on the left side.
I notice also that an incorrect keyboard layout is now selected.
I don't think this can be normal, so could this be something to do with the same bug?
Or maybe its just my ignorance of the quirks of Ubuntu, and I still
need to configure something else.

Revision history for this message
JM (jose-mingorance) wrote :

Same problem here. Many people mention as a workaround to delete the monitors.xml file. However, this workaround is only valid if you want to use the default resolution at startup. For me it's not possible because Ubuntu is trying to set a default resolution that is not supported by my screen. Therefore I MUST have the monitors.xml file to indicate the screen resolution I want at start-up. And that works. However still the annoying warning message.

Other workaround mention to add the desired resolution in the X11/xorg.conf file, but this file was deprecated and creating it to do this workaround is still more troublesome than having the annoying warning.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in xorg (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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