Second screen position isn't saved from one session to another
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GNOME Settings Daemon |
Incomplete
|
Medium
|
|||
| GNOME Shell |
Confirmed
|
Undecided
|
Unassigned | ||
| Ubuntu GNOME |
Undecided
|
Unassigned | |||
| Trusty |
Undecided
|
Unassigned | |||
| Xenial |
Undecided
|
Unassigned | |||
| Ubuntu GNOME Flashback |
Undecided
|
Unassigned | |||
| Unity |
New
|
Undecided
|
Unassigned | ||
| elementary OS |
Fix Released
|
Medium
|
Tom Beckmann | ||
| gnome-settings-daemon (Ubuntu) |
Low
|
Unassigned | |||
| gnome-shell (Ubuntu) |
Medium
|
Unassigned | |||
Bug Description
(Noticed on Ubuntu 14.04 beta 1 GNOME)
At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen.
Using gnome-control-
But when I disconnect the second screen (to work on another place) and then connect it again
OR if I just power off the laptop and turn it on again,
the second screen position is set back to the default right position.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-control-
ProcVersionSign
Uname: Linux 3.13.0-17-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 14 08:50:00 2014
InstallationDate: Installed on 2014-03-01 (12 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-control-
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_
Related branches
| Thierry Mallard (thierrymallard) wrote : | #1 |
| Changed in gnome-control-center (Ubuntu): | |
| importance: | Undecided → Low |
| Launchpad Janitor (janitor) wrote : | #2 |
| Changed in gnome-control-center (Ubuntu): | |
| status: | New → Confirmed |
| rmais96 (cgenre-dev) wrote : | #3 |
Exactly the same issue with my desktop machine (Ubuntu and Gnome Shell).
I can change settings to put my secondary screen on the left but after system reboot secondary screen is on the right again.
Whereas it was all right with previous Ubuntu 12.04 and 13.10.
| Smith (smith434) wrote : | #4 |
Is this the recommended fix at the moment? http://
| Julien (julien-behem) wrote : | #5 |
Same problem on Ubuntu GNOME 14.04 64bits also
Workaround is to restart gnome-settings-
| schwartuntu (schwarte) wrote : | #6 |
Same Problem on Gubuntu 14.04 64 bits. Also change with nvidia x server settings (safe to xorg.conf) does not help.
| Rob McCabe (rrrob9) wrote : | #7 |
Same proble for me, Ubuntu Gnome 14.04 64 bit, AMD Radeon 7470, thx
| HaraldK (pifpafpuf) wrote : | #8 |
Can confirm Juliens solution of killing the gnome-settings-
| mustangtyson (tysonsmith) wrote : | #9 |
Marked my bug as duplicate.
https:/
14.04 64 bit
3 monitors running on nouveau driver
gnome 3
Will not remember monitor position through reboots
| mika (mic-schaller) wrote : | #10 |
it's happening every time gnome-shell is (re-)started, not only at login (or is there a silent logout/login when we alt+f2 then r ?)
please increase importance
| mustangtyson (tysonsmith) wrote : | #11 |
Deleted ~/.config/
| germulvey (gpmulvey-iol) wrote : | #12 |
Similar issue,
nvidia 550ti - gnome ubuntu 14.04 also mint 17
setting tv to off and main monitor on - no change to position on saving in either nvidia-settings or display results in both turned on after reboot.
this worked fine previously on mint 16 or ubuntu gnome 13.10
Plus setting importance to low is not very helpful to those who have the issue, I bet if it affected a developer it would be much higher importance, every bug is important to those it affects!
| DigingBil (digingbil) wrote : | #13 |
Same issue here, it is driving me mad :(
Ubuntu Gnome 14.04 , 3.13.0-24-generic, same problem with catalyst and radeon drivers
2 dvi monitors, on reboot position not saved and I have to manually run "killall gnome-settings-
It is really not right to leave this with low importance. What's the criteria to set it to "low" anyway??
| gord-s (gord-sssnaps) wrote : | #14 |
I have it on every single machine that has more than one monitor (that's every single machine I own, basically), across various video card manufacturers. Because of that, my hunch is that everyone is affected if they use more than one monitor :|
| Sebastien Bacher (seb128) wrote : | #15 |
is anyone having the issue on Unity or is that specific to gnome-shell?
| Michael Zedeler (michael-zedeler) wrote : | #16 |
Same problem here. Ubuntu 14.04 on AMD64 with gnome-shell-
| Mrpgruber (mrpgruber) wrote : | #17 |
Same deal here: Ubuntu 14.04 with gnome-shell-
Not on my XFCE installation, though.
Fixed by swapping my (identical) monitors.
| Adi (aditzah-z) wrote : | #18 |
@Sebastien Bacher:
It is also happening on Unity, even if you set screen settings from AMD Catalyst (I have an AMD card), until you make changes from Gnome Control Center and save them. After that problems are "almost" fixed.
"Almost" means that before the login process everything is still messed up (my login prompt appears on my TV), but after login problem dissapear.
| The Gavitron (me-gavitron) wrote : | #19 |
this is probably related to this bug: https:/
I'm not yet sure which is cause vs effect, but doing:
$ sudo cp ~/.config/
caused lightdm to start with the 'correct' monitor configuration for me. Sadly, it did not persist through login to gnome-shell, but
$ nohup gnome-settings-
seems to fix it for my user session.
| The Gavitron (me-gavitron) wrote : | #20 |
it's possible that this is an upstream issue, per
https:/
| Smith (smith434) wrote : | #21 |
Has anyone explained why this bug is set to low? We waste a lot of time dealing with this bug during the development of our systems, an explanation as to the choice of importance would be appreciated.
| Sebastien Bacher (seb128) wrote : | #22 |
@Smith
That bug happens only to few users, it has not even been confirmed to apply to the default desktop environement. The bug settings are also not that important, having it flagged "low" doesn't mean it's not going to be worked on or resolved, it's just not a security issue or a data lost issue, mostly an usability one
| Smith (smith434) wrote : | #23 |
Thank you for the explanation. I understand this is not a critical bug, but your comment about the default desktop environment concerns me. Does this mean that the support for other desktop environments is not held in as high regard as that for unity? Also concerning is your statement about affect few users, this bug is marked as affecting 58 users, the most important bug in the tracker (rated by importance, https:/
| Sebastien Bacher (seb128) wrote : | #24 |
> Does this mean that the support for other desktop environments is not held in as high regard as that for unity?
Well, Unity is the default desktop/what most users are running, so yes we look in priority to bugs that affect it.
Canonical is also paying people to work on Unity where GNOME is community maintained (though we help fixing issues when we can)
The user numbers are only one metric, those numbers are low, the importance of the other bug is High due to the fact that it's a segfault an not only an usability issue...
| gord-s (gord-sssnaps) wrote : | #25 |
Sebastian said:
>The user numbers are only one metric, those numbers are low, the importance of the other bug is High due to the fact that..
Then in that case, may I suggest a change of policy somewhere? I've just been informed that this weekend our entire corporate entity will move to Mint (MATE) from Ubuntu Gnome, due to this bug. The kicker is that they now won't be going for Landmark next quarter, which is annoying. That's over 3,100 desktops lost to a competitor (it's business, so competitor is the appropriate word in this case), according to the feeling I'm hearing they may jump ship on servers soon too, which is more my department, so I'm extremely disappointed.
The bug simply doesn't happen on Mint and time is money, simple as that, it's not my decision, it was board-level no less.
Every decision on bug triage as well as release policies have consequences, I shouldn't have to mention how much the adoption and force-feeding of Unity has tainted the reputation of Ubuntu in many corporate eyes that were used to Gnome2 or legacy CDE-lookalikes. 58 affected - yeah right.
Moving forward: we use local mirrors to do all install and updates, we also have very strict firewalling and all traffic at every site goes though a application gateway to sanitise traffic - could that be a reason why "those numbers are low"? If so, what should be allowed (popcon?, not using local mirrors? something else?) to allow Canonical HQ to see the true user numbers of non-Unity DEs?
| Sebastien Bacher (seb128) wrote : | #26 |
@gord:
What your company is doing is their decision, not a lot we can do. Changing OS over a bug doesn't seems like a rationnal decision, your company could have looked at this issue, and contributed a fix for likely a lot less of efforts than it's going to take them to change systems on a thousand mahcines.
It might be that Mint is going to have the same bug next time they update/rebase on Ubuntu (they are based on it after all), in which case you handle a transition for an OS which is having a less strong security and support story, good luck with that.
Not sure about the numbers, we don't track users/installations nor collect datas. It's just that Canonical supports Unity as its main product, tyou liking the desktop or not is not changing that fact. I'm sure you could find somebody selling support for GNOME remix though...
| Sebastien Bacher (seb128) wrote : | #27 |
The issue is a gnome-shell one (see e.g comment #10), gnome-control-
| affects: | gnome-control-center (Ubuntu) → gnome-shell (Ubuntu) |
| Tim (darkxst) wrote : | #28 |
I can't reproduce this here with my 3 monitor system...
mutter via gnome-shell writes out the monitors.xml, in exactly the same format as g-s-d and it will get read back in at startup unless there is some sort of race condition messing things up. (gdm/Greeter configs are currently unsupported, but I have a patch for that will atleast get uploaded to utopic at some point.)
| mustangtyson (tysonsmith) wrote : | #29 |
@darkxst
We need to compare the monitors.xml that is written when running gnome3 vs unity to see if there are any differences.
| Changed in ubuntu-gnome: | |
| milestone: | none → trusty.1 |
| claus (claus2) wrote : | #30 |
It seems to me, that the problem is related to the setting of the primary display in the monitors.xml. Everything works fine unless I move the primary to a display, other than the very left.
My setup is a three monitor setup. Primary on the left display works. If I move primary to the center, than the center screen is moved to the left on the next login.
| Changed in ubuntu-gnome: | |
| status: | New → Confirmed |
| HaraldK (pifpafpuf) wrote : | #31 |
Someone says it might be a timing problem. Since upstart does not log time stamps (:-/), would it help to run strace on lightdm or gnome-shell when they start and provide the resulting log to see which processes are started in which order and which files are accessed on the way?
| ilektron (robotoman) wrote : | #32 |
I have to add my opinion on the importance of this bug. This bug can render a second monitor unusable, if every time I wish to log in I must turn on my TV and switch to the proper input. Shouldn't the severity of the bug escalate the importance to some degree? By no means is this a high importance bug, but it would be nice to know that it is at least high enough importance to be worked into a scheduled development effort.
We're experiening this same bug in Pantheon on development versions of elementary OS Freya (based on Ubuntu 14.04).
@claus2, I can confirm that behavior.
I have the same problem here: using Ubuntu 14.04 on AMD64 with gnome-shell-
| Jody Albritton (jody-albritton) wrote : | #36 |
I was able to resolve this issue by moving to the gnome/staging ppa. I still have my default monitor moving to the left for the greeter at login. I am using the current nvidia driver with two dvi monitors and one HDMI.
| Greg Wilkins (gregw-wiltel) wrote : | #37 |
@Sebastien
Sorry to comment on a meta-issue, but it concerns me when you say:
"What your company is doing is their decision, not a lot we can do. Changing OS over a bug doesn't seems like a rationnal decision, your company could have looked at this issue, and contributed a fix for likely a lot less of efforts than it's going to take them to change systems on a thousand mahcines."
As an open source developer, I too get a little frustrated by responses saying they will switch to a competitor. However, I also think it is dangerous to entirely dismiss such feedback. Changing OS over a bug does seem like a lot of work, so you have to ask yourself why? Perhaps it is because it is becoming all too frequent with ubuntu that your desire to add new featues is causing you to frequently break existing behaviours. This bug is not an isolated occurance and my own user experience is that the gnome3 ubuntu desktop experience is that things that have worked for literally decades are likely to just break and stay broken for some time. Since 14.04 I've had issues with sloppy mouse focus, screen lock, suspend/resume and now screen placement.
I really think ubuntu needs to give higher priority in your processes to broken existing behaviour.
| Changed in gnome-shell: | |
| status: | New → Confirmed |
| Changed in elementaryos: | |
| status: | New → Confirmed |
| Launchpad Janitor (janitor) wrote : | #38 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Changed in gnome-settings-daemon (Ubuntu): | |
| status: | New → Confirmed |
| Gabriel Hege (gabriel-hege) wrote : | #39 |
I was also affected by this bug, but copying the correct monitors.xml from ~/.config to /etc/gnome-
| Jody Albritton (jody-albritton) wrote : | #40 |
Does your layout stay in the proper configuration even on the greeter?
| summary: |
- multi-monitor : second screen position isn't saved from one session to - another + Second screen position isn't saved from one session to another |
| Changed in gnome-settings-daemon (Ubuntu): | |
| importance: | Undecided → Low |
| Changed in gnome-settings-daemon (Ubuntu): | |
| status: | Confirmed → Triaged |
| Changed in gnome-shell (Ubuntu): | |
| status: | Confirmed → Triaged |
| Changed in gnome-settings-daemon: | |
| importance: | Unknown → Low |
| status: | Unknown → New |
| Changed in elementaryos: | |
| importance: | Undecided → Medium |
| milestone: | none → freya-rc1 |
| Changed in elementaryos: | |
| status: | Confirmed → Won't Fix |
| Changed in elementaryos: | |
| milestone: | freya-rc1 → none |
| Changed in elementaryos: | |
| assignee: | nobody → Tom Beckmann (tombeckmann) |
| milestone: | none → freya-rc1 |
| status: | Won't Fix → In Progress |
| Changed in ubuntu-gnome: | |
| milestone: | trusty.1 → trusty.3 |
|
32 comments hidden
Loading more comments
|
view all 112 comments |
| emarkay (mrk) wrote : | #73 |
Workarounds? - nvidia - multiple monitors - have to reconfigure each time .. thanks.
| elr77 (segunb77) wrote : | #74 |
I would be very disappointed if this bug was not resolved because my personal work on agent based modelling and development in Java and SciLab/Matlab means I need to use 3 possibly 4 monitors with the centre monitor as my primary monitor.
I didn't comment earlier because after web searches I noticed that this was a problem with any thing based on Ubuntu 14.04 and partly why I wished Freya was based on a new version of ubuntu. Anyway for me the solution posted by Nicolas Bernaerts worked perfectly and consistently. There was the one moment if broken after running a dist-upgrade but I resolved by just rerunning the fix. If it is any help to the developers or other users you can find the fix at
http://
I would help develop an integration of the fix into elementary OS but, my coding skills only go as far as Java a bit of C# and Matlab.
| Changed in elementaryos: | |
| status: | In Progress → Fix Committed |
| suoko (suoko) wrote : | #75 |
Unfortunately the fix from bernaerts does not work on a PC I'm setting up now.
Is it possible to port the fix for elementaryos (if available) to this distro ?
| suoko (suoko) wrote : | #76 |
I compared the gnome-settings-
UTOPIC
etc/xdg/autostart
usr/lib/
usr/share/
usr/share/icons
usr/share/locale
usr/share/
usr/share/polkit-1
debian/
TRUSTY
etc
usr/lib/
usr/share/dbus-1
usr/share/icons
usr/share/locale
usr/share/
usr/share/polkit-1
debian/
Could that missing "/xdg/autostart" in the Trusty package be the problem ?
See
http://
http://
| Changed in elementaryos: | |
| status: | Fix Committed → Fix Released |
| The Bright Side (me-knowingme) wrote : | #77 |
Great news! Fixed in Ubuntu GNOME 15.04, 64-bit, for me. Love it!!
| Carlos Paz (phoenixsampras) wrote : | #78 |
Problem persist. I have Ubuntu 15.04 , Gnome 3 from repositories. Using Gnome CLASSIC.
| Carlos Paz (phoenixsampras) wrote : | #79 |
Problem persist. 3 Monitors, HDMI, VGA, laptop monitor, 64 bits.
| a8ksh4 (spam-dn) wrote : | #80 |
Just did a fresh install of Ubuntu Gnome 14.04.2 and the problem is still there. Nvidia card w/ dual monitor. 64 bit. DVI.
| Indaleto (indaleto) wrote : | #81 |
With Elementary OS Freya the problem persists (64b, NVidia card, VGA)
| Witold Szczeponik (wsz) wrote : | #82 |
Had to install Ubuntu GNOME 14.04.2 lately (64 bit, NVIDIA Corporation GT216GLM [Quadro FX 880M], VGA.). Problem still persists.
| fleamour (gtx-swift) wrote : | #83 |
This seems fixed in elementary when power cycling but still bites when resuming from suspend, but only intermittently.
| Bruce Pieterse (octoquad) wrote : | #84 |
Looking at the upstream bug, some users seem to get this working with gsettings set org.gnome.
| Changed in gnome-settings-daemon: | |
| importance: | Low → Unknown |
| status: | New → Unknown |
| a8ksh4 (spam-dn) wrote : | #85 |
OMFG, I just ran updates, rebooted, and my screen positions were preserved! I hope this is actually fixed... Thanks to whoever might have done this... !
Ubuntu Gnome 14.04.2 w/ Nvidia.
| a8ksh4 (spam-dn) wrote : | #86 |
Meh, false alarm, it was back to normal today. :P
| Fredrik Jacobsson (fredrik-o) wrote : | #87 |
I'm seeing this bug in the normal Unity Greeter, but booting into Unity sets the displays correctly where booting into Flashback doesn't
Versions of Ubuntu: Work computer with 15.10 and Home computer with 16.04 (devel and devel-proposed)
| Emix (emix-pam) wrote : | #88 |
I have the same bug in Ubuntu 15.10
| maddin (ich-martin-drees) wrote : | #89 |
Same problem here in Ubuntu Gnome 15.10 ... really annoying.
| The Bright Side (me-knowingme) wrote : | #90 |
Guys, this is just a total shot in the dark and probably won't work, but has anybody tried installing the nvidia-modprobe package? I did this some time ago (I think during 14.10) to fix issues with Darktable. Around the same time, but possibly only later, the second-screen issue disappeared for me. It never occurred to me until now, but there just miiiight be a connection?
I've been using nvidia-modprobe ever since, so I don't know if this has anything to do with it and frankly, I don't think so. But perhaps give it a shot and report back?
| xavi (xaviersarrate) wrote : | #91 |
I have the same bug in Ubuntu 15.10 classic desktop
| Seppo (brack-sebastian) wrote : | #92 |
I have the same/similar issue with Ubuntu 15.10, Unity, NVidia GTX 970, NVidia-352 prop driver.
My main display (the left one) is 1920x1080 plugged in via HDMI, and my second monitor is 1280x1024 via DVI. I setup my big monitor to be the left one, and my smaller to be the right one via Unity display settings. On system boot, boot screen and information is only shown on my smaller right monitor, left monitor doesn't even get a signal. On login screen, login credentials are only shown on the smaller right screen, with an expanded wallpaper showing on the left.
After login, the left monitor is set correctly to the left, but full screen applications like most of my games start on the smaller right monitor by default. I can fix this after every login via NVidia Xserver Settings app and marking my left monitor as primary, then every game starts correctly on my left monitor. I worked around this now with a startup script setting the primary monitor to the left one via xrandr command.
Can't understand why this issue is still low, as it is a very annoying usability bug. Hope this get's fixed in 16.04 LTS!
| emarkay (mrk) wrote : | #93 |
OK, 14.04.3 has come and gone, still not fixed.
Why?
Is there a working solution as a temporary fix?
| Andriy Podanenko (podarokua) wrote : | #94 |
Same on 16.04
| tags: | added: xenial |
| gord-s (gord-sssnaps) wrote : | #95 |
Yeah still have the same problem in a test install of 16.04, though we've been using other distros since this bug occurred years ago as it makes it totally unusable for work.
In fact I'm only posting here because I initially misread Bruce's tag addition above as a typo for "denial" in the email :)
| Changed in ubuntu-gnome: | |
| milestone: | trusty.3 → yakkety |
| Tim (darkxst) wrote : | #96 |
I know there is an issue on Xenial where positions get lost on monitor changes (like adding/removing a monitor) but is anyone seeing the settings disappear on xenial across reboots?
| Andriy Podanenko (podarokua) wrote : | #97 |
Same thing is for Unity
I'm using
Ubuntu 16.04 (upgraded from 12.04->
lightdm 1.18.1
Unity 7.4.0
When system is booting first look at login window is good, then it rewrites a screen and makes monitors changed to wrong order. Changing monitors to right order after login via system settings helps only for the current session untill reboot
Needs fix
| Changed in ubuntu-gnome-flashback: | |
| status: | New → Confirmed |
| Aurélien Léger (dexyne) wrote : | #98 |
Same problem here for Ubuntu 15.10.
Login window is fine, then it inverse my screens order.
I need to change it again in the system panel to set it good again, but
it save the settings for only the current session.
| eOrange (s-s-naumov) wrote : | #99 |
The same bug on Ubuntu 16.04.1 on the clean installation.
My workaround for a moment - run xrandr command to change monitor position on startup.
| Donjan Rodic (bryonak) wrote : | #100 |
Not sure if this is equivalent, as I run unity-settings-
Just upgraded from 14.04 to 16.04.1.
I drop my laptop on a dock with two vertically oriented (rotated to portrait) monitors. This was working fine before, now it lights them up without the rotation. Rotating them manually via System Settings -> Displays, undocking and docking again reverts to the wrong (landscape) orientation.
The ~/.config/
Reloading the settings with
killall unity-settings-
gives me the correct orientation, which is read from the monitor.xml (editing the file by hand and killing u-s-d accepts whatever changes I make), it just doesn't get triggered on docking changes.
That's the workaround for now: kill u-s-d every time I dock to that workplace, which may help with g-s-d too.
It would be nice for patchlvl 1 LTS upgrades to not break such basic stuff.
| Filofel (filofel) wrote : | #101 |
Same problem here after upgrading three days ago from Ubuntu 14.04.4 (that worked) to 16.04.1 (that's broken as explained below).
Desktop Environment: GNOME-Flashback
Dual screen, notebook + external VGA monitor.
NVidia Quadro FX 770M, 3.3.0 NVIDIA 340.96
I set the primary monitor to the notebook screen using nvidia-settings, and the setting stuck across logout: I see the gnome panel properly moving to the notebook screen when the Gnome GUI comes up after logout and reboot.
OTOH, my notebook is positioned to the right of my VGA monitor, and that's where the problem starts. The system insists on placing the notebook built-in screen to the left of the monitor.
If I set the primary monitor (notebook built-in screen) to the right of the VGA screen using nvidia-settings, I get what I want for the current session. But this setting is lost after the next session logout (or reboot for that matter).
If alternately, I set the primary monitor (notebook built-in screen) to the right of the VGA screen using "System Settings / Displays", I get what I want for the session, but this setting is also lost after the next logout (reboot).
The trick suggesting at #39 doesn't work for me (to start with, I have no etc/gnome-
To add insult to injury, the upgrade also brought me a similar problem with the alsamixer settings: They are set to some default muted values that makes the machine totally silent at each session start, and whatever way I set them, they are reset to the same muted default values upon the next logout / login.
Not sure whether I also owe this to gnome-shell, but that's what I suspect.
I use "sudo alsactl" to manually handle the problem and reload the proper alsamixer value, but I hate it.
I have so far not found any simple, reliable fix or workaround for either problem. <sigh>
| tags: | added: multimonitor |
I've just reproduced this bug on Mint 18.1 with Mate.
| Davias (davias) wrote : | #103 |
Hi guys, same problem after upgrading from 14.04 LTS to 16.04.2 LTS...Gnome fallback of course (it is called fallback becouse Unity is supposed to be an improvement?) I had this problem in 14.04, with AMD Catalyst Control Center not remembering monitors position. Solved using system/monitors to set them and it was ok. After the upgrade, Catalyst is gone for free Gallium...but I get the bug. Strange enough at login monitors are correctly positioned...after login they get messed up. Same system since 7.04, always worked with 3 monitors...I know there is a script to work back the monitor config file...but is such an inelegant solutions...c'mon this bug is old years!
| s.illes79 (s-illes79-gmail) wrote : | #104 |
started happening with kernel 4.12.0-rc
if I plug in an external screen, configure the layout, than when I disconnect and reconnect the layout is reset to the default.
if I boot back to 4.10.X all works fine.
| Miles Marx (k-vp) wrote : | #105 |
This appears to persist in 17.04....I installed Ubuntu Server first, and then installed Xubuntu via Tasksel because I needed to do some additional setup before any display manager would be able to function. I also tried MATE and LXDE on the same system, and they did not appear to suffer from this issue. Thus it would appear this is specific to XFCE.
GPU is GTX 980M on an MSI GT72s laptop.
I also tried setting the monitor configs through the Nvidia control panel to no avail. It's not just session to session but actually even just letting the screens idle to sleep, the layout is bombed and I have to reset it when they are powered back on.
It also fails to detect my external monitor's max refresh rate 9 times out of 10 but I suspect that is a deeper, unrelated issue.
| Changed in gnome-shell (Ubuntu): | |
| importance: | Low → Medium |
| Rob (usofrob) wrote : | #106 |
I had a problem with Ubuntu 14.04 and the latest supported nvidia drivers. Every time I locked my screen, it would lose the orientation. I was regularly using the nvidia X server settings application to correct the screen layout.
In order to correct it, I opened the System Settings application and made a couple modifications via the Displays options, and applied my changes. The changes weren't important, I just put it back to the same settings when I was done. Now the displays stay put when I lock my screen.
| Changed in gnome-settings-daemon: | |
| importance: | Unknown → Medium |
| status: | Unknown → Incomplete |
| juanca (peyroneljc) wrote : | #107 |
Same problem, when updating, from 14.04 LTS to 16.04 LTS.
Desktop Environment: GNOME-Flashback: Unity (gnome-
The strange thing is that in 14.04, this did not happen to me.
I'm thinking of going back to Trusty.
The momentary solution with the script, does not provide solution for the icons on the desktop, these, change their position and overlap, and not put back in their original position.
Needs fix
| Davias (davias) wrote : | #108 |
Ok I got it! I was about to implement this solution http://
Hope this can shed some light on this annoying Ubuntu bug...the fact that Ubuntu system settings/monitor and gnome-control-
| Filofel (filofel) wrote : | #109 |
@davias (#108):
This works for me too!
Thanks a lot!
Please in (https:/
- Add you to the CC list.
- Answer the developers questions.
Thank you.
| Daniel van Vugt (vanvugt) wrote : | #111 |
Consider deduplicating with bug 1716341?
| Daniel van Vugt (vanvugt) wrote : | #112 |
Or consider deduplicating with bug 1726538?
| tags: | added: artful |
Status changed to 'Confirmed' because the bug affects multiple users.