Screen resolution not saved after reboot or logout and back in

Bug #1615864 reported by GeeMac
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Expired
Low
Unassigned

Bug Description

The issue is that Ubuntu 16.04 does not save or read the saved screen resolution settings of 1920x1080 from my Vizio 42 inch TV HDMI connected to my computer. When booting into the desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to.

The TV reports the proper information under xrandr.
gee@HTPC:~$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096
VGA-0 disconnected (normal left inverted right x axis y axis)
TV-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm
   1280x720 60.00 + 59.94
   1920x1080 59.94 59.94* 60.05 60.00 50.04
   720x576 50.00 50.08
   720x480 59.94
   640x480 59.93

WORKAROUND: Type at the terminal:
xrandr -s 1920x1080

---
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015
 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME-Flashback:Unity
DistUpgraded: Fresh install
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
DkmsStatus:
 nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed
 nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f]
InstallationDate: Installed on 2016-08-20 (12 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp.
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: MSI MS-7349
NonfreeKernelModules: nvidia
Package: xorg 1:7.7+13ubuntu3
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=377930d2-4053-4a10-96ef-8cac652e4c24 ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Tags: xenial ubuntu
Uname: Linux 4.4.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare sudo video
_MarkForUpload: True
dmi.bios.date: 03/19/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: CaptiveWorks CW-3000HD V2.37
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7349
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCaptiveWorksCW-3000HDV2.37:bd03/19/2008:svnMSI:pnMS-7349:pvr1.0:rvnMSI:rnMS-7349:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7349
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2

Revision history for this message
GeeMac (htpc2013) wrote :
Revision history for this message
GeeMac (htpc2013) wrote :

I just placed a script in .config/autostart

" xrandr --output VGA-0 --off --output TV-0 --off --output HDMI-0 --primary --mode 1920x1080 --pos 0x0 --rotate normal "

This was generated by Arandr which was suggested by someone in the IRC. That failed to work. Then I tried the same in a folder called .screenlayout. That also failed.

I tried to have it called from the "Startup Applications" , but that seems to also be broken (bug report to follow on this), Startup Applications does not save anything that is added after a reboot. The only thing that is showing there is Nvidia X Server settings.

As stated earlier this was not an issue with 14.04 LTS. Three weeks later I am still dealing with this screen resolution issue to the point that I lost track of all the things that were suggested and from outdated posts.

Revision history for this message
GeeMac (htpc2013) wrote :

I have also tried Arander GUI suggested by someone in the IRC and it created a script:
#!/bin/sh
xrandr --output VGA-0 --off --output TV-0 --off --output HDMI-0 --primary --mode 1920x1080 --pos 0x0 --rotate normal

This was placed in /home/.screenlayout which did not work. I also manually added the same script to the folder /home/.config/autostart with no luck. Both scripts were given the proper permissions. I have the script in both locations at the moment, but I have tried with just .screenlayout or .config/autostart.
I am about to rewrite the script as a simple xrandr -s 1920x1080 since that seems to work each time I boot and have call the terminal and put that line in so I can get my proper screen resolution.

Revision history for this message
GeeMac (htpc2013) wrote :

At least can someone give me an idea how to put an icon on my desktop to call xrandr -s 1920x1080 ?
This is getting a bit old having to do a Ctrl+Alt+T to pull up the terminal and type in the line.
Thanks

Revision history for this message
penalvch (penalvch) wrote :

GeeMac, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information:
apport-collect -p xorg 1615864

When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
GeeMac (htpc2013) wrote : .proc.driver.nvidia.params.txt

apport information

tags: added: apport-collected ubuntu xenial
description: updated
Revision history for this message
GeeMac (htpc2013) wrote : CurrentDmesg.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : Dependencies.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : DpkgLog.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : JournalErrors.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : Lspci.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : MonitorsUser.xml.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : NvidiaBugReportLog.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : ProcEnviron.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : ProcInterrupts.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : ProcModules.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : UdevDb.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : UnitySupportTest.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : XorgConf.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : XorgLog.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : XorgLogOld.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : Xrandr.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : nvidia-settings.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote : xdpyinfo.txt

apport information

Revision history for this message
GeeMac (htpc2013) wrote :

Hello,
Sorry I did not grab the information via apport in the first place.

I hope this was supposed to log everything this way? I thought it would place it in Ubuntu.pastebin. It ended up being automatically generated here.

Revision history for this message
penalvch (penalvch) wrote :

GeeMac, could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description, or the result of a terminal command)?

Revision history for this message
GeeMac (htpc2013) wrote :

Hello Christopher,
Thanks for looking into this.
I probably mentioned this above, but there were no issues with the system under 14.04.

Motherboard: MSI K9NGM3-FIH (MS-7349)

Here is a pastebin link to a complete breakdown of this computer.
http://pastebin.com/yskf85Db

penalvch (penalvch)
tags: added: bios-outdated-2.7
Revision history for this message
penalvch (penalvch) wrote :

GeeMac, to clarify, if you uninstall the nvidia proprietary driver is this still reproducible?

description: updated
tags: added: regression-release
Revision history for this message
GeeMac (htpc2013) wrote :

Hi

I can try, but if I install the Nouveau driver that opens up a can of worms here.
The graphics become completely unstable, shaking, with vert or horiz tearing. Just completely unusable. It is real tricky to even get through the menus to get to the drivers to get out of Nouveau.
Any suggestions what to try for a usable Nvidia driver?

Thanks

Revision history for this message
GeeMac (htpc2013) wrote :

I'm going to take a shot at what was suggested here.
http://askubuntu.com/questions/760934/graphics-issues-after-installing-ubuntu-16-04-with-nvidia-graphics

I'll update you as soon as I see the results. Or not see anything. ;)

Revision history for this message
GeeMac (htpc2013) wrote :

Answer to your question; still reproducible, yes.

Well that did not go all that well. It got me stuck in a 640x480. Even doing a xrandr -q only gave me that resolution.
Per the URL posted above.

This is Not recommended, at least after my test:
Run sudo apt-get purge nvidia-*
Run sudo add-apt-repository ppa:graphics-drivers/ppa and then sudo apt-get update.
Run sudo apt-get install nvidia-364.
Reboot and your graphics issue should be fixed. >Not really<

I had to purge nvidia again to get to Nouveau and then work my way through that mess to the Nivida v.304.x tested again. Then back to the terminal and the xrandr line.
I went into Synaptic and unchecked ppa:graphics-drivers and went from there.
Mainly square one. Back to 304.131 tested and using xrandr -s 1920x1080 in the terminal again.

penalvch (penalvch)
Changed in xorg (Ubuntu):
status: Incomplete → New
Revision history for this message
GeeMac (htpc2013) wrote :

Just for the heck of it I tried switching drivers again.

Nvidia (proprietary Tested) driver No difference at reboot or relog.

Nvidia (proprietary) No difference at reboot or relog.

X.Org X Server Nouveau will boot at 1280x720 (720P) Will not save 1920x1080 when changed. Nouveau is unstable with this system.
Video tearing and flashing within a few minuets of any screen changes from a static desktop.

I hope the above information is answering your questions.
I would like to get this resolved soon since it is getting tiresome to have to type the xrander in terminal every time.
I would place it in system startup, but it won't save after added. See Bug #1617129

Revision history for this message
GeeMac (htpc2013) wrote :

Sorry I meant "Startup Applications" not system startup.

Revision history for this message
GeeMac (htpc2013) wrote :

Hello Christopher,

Can you give me an idea why this is marked as "Low" Importance?
This issue was not in 14.04. I have reinstalled 16.04 LTS twice now after the failed update from 14.04 and have the same issue. I feel that this issue is more important then leaving this as low grade issue. There are others having the issue but have not posted it as a bug, but they have in some forums. I have been that route and also have been in the IRC.
I can only guess at two things; my MB / graphics chipset is old and 16 is not backward compatible or there is a bug in 16.04. I'm thinking the latter.
I have tried all that I could think of along with your suggestions. Also I can't think of any other information that I can give you to help with this situation. I would hate to have to go backwards to 14.04.
I'm disabled here so I am available almost 24/7 if you want to investigate this further
If you have the time I can set up a TeamViewer session so you can look around.

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
Revision history for this message
Keera Studios (keera-studios) wrote :

Similar issue on Ubuntu 16.04 with RV620 (Radeon HD 3450).

Dual monitor setup, settings lost after every reboot.

Revision history for this message
Paul White (paulw2u) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time.

Changed in xorg (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]

Changed in xorg (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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