[nvidia] Rotating secondary monitor to portrait fails, results in landscape

Bug #1874567 reported by Matt Austin
166
This bug affects 27 people
Affects Status Importance Assigned to Milestone
mutter (Ubuntu)
Fix Released
High
Marco Trevisan (Treviño)
Focal
Fix Released
High
Marco Trevisan (Treviño)

Bug Description

[ Impact ]

I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation).

Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf).

When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted.

[ Test case ]

1. Install nvidia drivers
2. Configure an external monitor to be in portrait mode in gnome-control-center
3. Apply the configuration
4. Expect configuration is properly working

[ Regression potential ]

Wrong screen size is set and panning is used.

----

ProblemType: BugDistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020
 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Apr 24 08:30:41 2020
DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871]
InstallationDate: Installed on 2018-05-01 (723 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Shuttle Inc. SZ77
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
dmi.bios.date: 10/13/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.13
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: FZ77
dmi.board.vendor: Shuttle Inc.
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.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: SZ77
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Shuttle Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
Matt Austin (mattaustin) wrote :
Revision history for this message
Matt Austin (mattaustin) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could well be a bug in the nvidia driver nvidia-graphics-drivers-440 from the description

affects: xorg (Ubuntu) → nvidia-graphics-drivers-440 (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nvidia-graphics-drivers-440 (Ubuntu):
status: New → Confirmed
Changed in nvidia-graphics-drivers-440 (Ubuntu):
importance: Undecided → High
tags: added: multimonitor
summary: - Secondary (rotated) monitor configuration is not applied correctly in
- gnome settings
+ [nvidia] Secondary (rotated) monitor configuration is not applied
+ correctly in gnome settings
Changed in mutter (Ubuntu):
status: New → Confirmed
Revision history for this message
Ken Perkins (ken-perkins) wrote : Re: [nvidia] Secondary (rotated) monitor configuration is not applied correctly in gnome settings

For what it's worth, I tested this with 440, 435, 390, and the Nouveau drivers and all of them presented the issue. I did notice that during the live USB (try), I could set the value.

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

I also ran into this bug, when I was trying to reproduce bug 1874217.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Shannon Walker (orcashannon) wrote :

Not sure it an nvidia driver issue. Using nvidia-settings to change anything in 'X Server Display Configuration' fixes the problem.
Here is my xrandr output after changing the x offset of one monitor from +230 to +240.

Ubuntu display settings:
$ xrandr --current
Screen 0: minimum 8 x 8, current 2800 x 2680, maximum 32767 x 32767
DVI-D-0 connected 1200x1600+1200+0 right (normal left inverted right x axis y axis) 408mm x 306mm panning 1600x1600+1200+0 tracking 2800x2680+0+0 border 0/0/0/0
   1600x1200 60.00*+
   1280x1024 85.02 75.02 60.02
   1280x960 60.00
   1024x768 85.00 75.03 60.00
   800x600 85.06 60.32
   640x480 85.01 75.00 59.94
HDMI-0 connected 1200x1600+0+0 right (normal left inverted right x axis y axis) 408mm x 306mm panning 1600x1600+0+0 tracking 2800x2680+0+0 border 0/0/0/0
   1600x1200 60.00*+
   1280x1024 85.02 75.02 60.02
   1280x960 60.00
   1024x768 85.00 75.03 60.00
   800x600 85.06 60.32
   640x480 85.01 75.00 59.94
DP-0 connected primary 1920x1080+230+1600 (normal left inverted right x axis y axis) 527mm x 296mm panning 2320x1080+230+1600 tracking 2800x2680+0+0 border 0/0/0/0
   1920x1080 60.00*+ 59.94 50.00
   1680x1050 59.95
   1440x900 74.98 59.89
   1280x1024 75.02 60.02
   1280x960 60.00
   1280x720 60.00 59.94 50.00
   1024x768 75.03 60.00
   800x600 75.00 60.32
   720x576 50.00
   720x480 59.94
   640x480 75.00 72.81 59.94 59.93
DP-1 disconnected (normal left inverted right x axis y axis)

after adjusting ofset using nvidia-settings (temporarily fixes the issue):
$ xrandr --current
Screen 0: minimum 8 x 8, current 2400 x 2680, maximum 32767 x 32767
DVI-D-0 connected 1200x1600+1200+0 right (normal left inverted right x axis y axis) 408mm x 306mm
   1600x1200 60.00*+
   1280x1024 85.02 75.02 60.02
   1280x960 60.00
   1024x768 85.00 75.03 60.00
   800x600 85.06 60.32
   640x480 85.01 75.00 59.94
HDMI-0 connected 1200x1600+0+0 right (normal left inverted right x axis y axis) 408mm x 306mm
   1600x1200 60.00*+
   1280x1024 85.02 75.02 60.02
   1280x960 60.00
   1024x768 85.00 75.03 60.00
   800x600 85.06 60.32
   640x480 85.01 75.00 59.94
DP-0 connected primary 1920x1080+240+1600 (normal left inverted right x axis y axis) 527mm x 296mm
   1920x1080 60.00*+ 59.94 50.00
   1680x1050 59.95
   1440x900 74.98 59.89
   1280x1024 75.02 60.02
   1280x960 60.00
   1280x720 60.00 59.94 50.00
   1024x768 75.03 60.00
   800x600 75.00 60.32
   720x576 50.00
   720x480 59.94
   640x480 75.00 72.81 59.94 59.93
DP-1 disconnected (normal left inverted right x axis y axis)

summary: - [nvidia] Secondary (rotated) monitor configuration is not applied
- correctly in gnome settings
+ [nvidia] Rotating secondary monitor to portrait fails, results in
+ landscape
Changed in nvidia-graphics-drivers-435 (Ubuntu):
status: New → Confirmed
Revision history for this message
Angela Piotrowski (angela-piotrowski) wrote :

Attached is the output to lspci -k from another user experiencing this issue.

Revision history for this message
Angela Piotrowski (angela-piotrowski) wrote :

Attached is the output from lshw -C display from a user experiencing this bug

tags: added: rls-ff-incoming
Revision history for this message
Anton Matosov (matroskin222) wrote :

Hello folks. I experience this issue with my three monitor setup (two of which are vertical) using NVIDIA Drivers 440.82 on PopOS 20.04.
Monitor layout works with xrandr/arandr and if I hand craft manitors.xml, configuration is preserved. I have posted my details here https://github.com/pop-os/pop/issues/933#issuecomment-643681670

But GUI doesn't work.
Also after recovering from suspend layout explodes again.

I would be glad to help with investigation, collecting logs, traces, etc (feel free to DM me).

Changed in nvidia-graphics-drivers-435 (Ubuntu):
status: Confirmed → Won't Fix
Changed in nvidia-graphics-drivers-440 (Ubuntu):
status: Confirmed → Won't Fix
Changed in gnome-control-center (Ubuntu):
status: Confirmed → Won't Fix
Changed in mutter (Ubuntu):
status: Confirmed → In Progress
importance: Undecided → High
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
Revision history for this message
ADFH (adfh) wrote :

I also logged https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1876551 about nvidia-340 drivers having the same problem (won't remember the config).

My workaround is a .desktop file that calls xrandr with my desired parameters I configured with nvidia tool and then dumped out with xrandr.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nvidia-graphics-drivers-340 (Ubuntu):
status: New → Confirmed
Iain Lane (laney)
Changed in mutter (Ubuntu Focal):
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
Changed in nvidia-graphics-drivers-435 (Ubuntu Focal):
status: New → Won't Fix
Changed in nvidia-graphics-drivers-440 (Ubuntu Focal):
status: New → Won't Fix
tags: removed: rls-ff-incoming
Changed in gnome-control-center (Ubuntu Focal):
status: New → Invalid
Changed in nvidia-graphics-drivers-340 (Ubuntu):
status: Confirmed → Won't Fix
tags: added: xrandr-scaling
Changed in mutter (Ubuntu Focal):
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mutter - 3.36.3-1ubuntu2

---------------
mutter (3.36.3-1ubuntu2) groovy; urgency=medium

  * debian/control:
    - Revert BD on adwaita-icon-theme 3.36.1-2ubuntu3. It was just temporary fix.
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
    - Use pre-computed CRTC layout size for computing screen size (LP: #1874567,
      LP: #1873403)
    - Decouple the output mode from layout mode capabilities (LP: #1876894,
      LP: #1886996)
    - Ensure we notify CRTC changes on integer scaling changes (LP: #1876894)
    - Apply proper layout monitor config when using fractional scaling
      (LP: #1884754)
    - Restore the fractional settings when reverting to fractional layout
      (LP: #1886996)
  * debian/libmutter-6-0.symbols: Add new private symbol

 -- Marco Trevisan (Treviño) <email address hidden> Sat, 11 Jul 2020 00:44:33 +0200

Changed in mutter (Ubuntu):
status: In Progress → Fix Released
Rex Tsai (chihchun)
Changed in oem-priority:
assignee: nobody → jeremyszu (os369510)
importance: Undecided → Critical
tags: added: oem-priority
Changed in nvidia-graphics-drivers-340 (Ubuntu Focal):
status: New → Won't Fix
Revision history for this message
Phil Hudson (23dp89jasu8d98asd) wrote :

Found in a post on Reddit, a workaround that worked for me via GUI. Even though this is still a bug I wanted to help this workaround get more exposure.

```
Just installed 20.04. Same issue. But i have a workaround that doesn't involve manual settings with xrandr.

If i set them so that all monitors align at the bottom, it works as expected. This makes for a bit of wonky cursor movement screen-to-screen, but it's usable for now until it gets fixed.

Something about the nvdidia driver seems to not be able to map the position to any other configuration. It does not work if for me if I align them all at the top, only with them all aligned at the bottom.

Source: https://www.reddit.com/r/pop_os/comments/g7pwq8/multimonitor_screen_rotation_not_working_in_2004/
```

Changed in gnome-control-center (Ubuntu Focal):
status: Invalid → Won't Fix
Changed in mutter (Ubuntu Focal):
importance: Undecided → High
Changed in nvidia-graphics-drivers-440 (Ubuntu Focal):
importance: Undecided → High
description: updated
Changed in mutter (Ubuntu Focal):
status: In Progress → Fix Committed
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Matt, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

tags: added: verification-needed verification-needed-focal
Revision history for this message
Travis (tadieckmann) wrote :

What's the status for Ubuntu Focal?

How can I help to emphasize the importance of backporting the fix to the stable release?

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

The answer to your question is comment #15. :)

Revision history for this message
jeremyszu (os369510) wrote :

@Marco,

Hi, here is the steps when verifying mutter from focal-proposed:

1. Upgrade all packages to latest version in focal-updates.
2. Enable focal-proposed in source list
3. sudo apt install mutter
4. Configure external screen orientation by selecting "Portrait Right"
5. Screen orientation doesn't change but asking save changes.
6. Press "Revert changes"
7. Configure external screen orientation by selecting "Portrait Right" again.
8. Screen goes to black screen.

Attachment is the journal log.
```
Jul 24 03:02:18 u kernel: show_signal_msg: 38 callbacks suppressed
Jul 24 03:02:18 u kernel: gnome-control-c[3252]: segfault at 7fff58ce6ff8 ip 00007fa5ef8b114c sp 00007fff58ce7000 error 6 in libc-2.31.so[7fa5ef841000+178000]
Jul 24 03:02:18 u kernel: Code: 1f 80 00 00 00 00 e8 b3 bb ff ff eb d1 90 f3 0f 1e fa 48 85 d2 0f 84 63 01 00 00 41 57 49 89 ff 41 56 49 89 d6 41 55 49 89 d5 <41> 54 4c 8d 25 4b 77 15 00 55 48 8d 2d ab 84 15 00 53 4c 29 e5 48
```

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

jeremyszu,

That's a crash in gnome-control-center occurring at the same time as a black screen. It's correlation of two issues, not causation of one by the other...

Please report the crash in a new bug using these steps:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

Revision history for this message
Matt Austin (mattaustin) wrote :

Thank you for fixing this bug. Installing mutter 3.36.4-0ubuntu0.20.04.1 and libmutter 3.36.4-0ubuntu0.20.04.1 from focal-proposed has resolved this issue for me.

Note: The updated libmutter from focal-proposed also had to be explicitly installed by me, as it was not automatically pulled in when updating mutter.

Steps:
1) Enabled focal-proposed
2) apt update
3) apt install mutter libmutter
4) Disabled focal-proposed
5) Removed ~/.config/monitors.xml and ~gdm/config/monitors.xml
6) Rebooted
7) After login, I successfully applied my desired monitor configuration (changing the primary monitor and setting other monitor to portrait orientation).

Side notes:
1) I still had to copy ~/.config/monitors.xml to ~gdm/.config/monitors.xml for the correct primary monitor and orientation to be set on the login screen.
2) After applying the display configuration, the icons in the top-right of the gnome panel appeared blured (network/bluetooth). This was resolved by applying 150% fractional scaling and then applying 100% scaling again in the gnome display settings. I haven't had time to reproduce this to know if it's a one-off or ongoing bug.

tags: added: verification-done verification-done-focal
removed: verification-needed verification-needed-focal
Revision history for this message
Benjamin Jacob Reji (benjaminjacobreji) wrote :

Regarding bug mentioned in Side note 2 of
#20 Comment (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1874567/comments/20)

I face the same issue, and am able to fix it via the fractional scaling method.
I was able to reproduce this over two separate clean installs on my machine.

Also following #20 comment helped solved the display rotating issue.
Thank you devs for the fix.
Regards

Revision history for this message
Uwe Dulz (uwe.dulz) wrote :

I installed the mutter libraries from focal proposed as described in #15 and the issue seems to be fixed. Also copied my ~/.config/monitors.xml to /var/lib/gdm/.config/monitors.xml and was able to get the same monitor configuration working at the login screen.
So this is verified and finally works as it used to work in 18.04.

Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Matt, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

tags: added: verification-needed verification-needed-focal
removed: verification-done verification-done-focal
Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

I can confirm this working in my nvidia setup

❯ apt-cache policy libmutter-6-0
libmutter-6-0:
  Installato: 3.36.4-0ubuntu0.20.04.2
  Candidato: 3.36.4-0ubuntu0.20.04.2
  Tabella versione:
 *** 3.36.4-0ubuntu0.20.04.2 400
        400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
        100 /var/lib/dpkg/status

tags: added: verification-done verification-done-focal
removed: verification-needed verification-needed-focal
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mutter - 3.36.4-0ubuntu0.20.04.2

---------------
mutter (3.36.4-0ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (LP: #1889090)

mutter (3.36.4-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream stable release (LP: #1887998)
    - Fix crash on area screenshots with fractional scaling
    - Do not paint textures of fully obscured windows
    - Turn off CRTCs as well when enabling DPMS
    - Improve selection support
    - Use a more appropriate combine function on opaque areas
    - Fix remote desktop being broken without screencast session
    - Fix popovers disappearing on wayland and HiDPI
    - Fixed crashes (LP: #1870867, LP: #1857947)
    - Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
    d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
    d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
    d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
    d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
    d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
    d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
    d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-1000000.patch,
    d/p/screen-cast-window-stream-src-Fix-indentation.patch:
    - Import more fixes for screencasting and remote desktop
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
    - Don't export patch-only private symbol
  * debian/libmutter-6-0.symbols:
    - Remove ubuntu-only private symbol

mutter (3.36.3-0ubuntu0.20.04.2) focal; urgency=medium

  * debian/control:
    - Revert BD on adwaita-icon-theme 3.36.1-2ubuntu3. It was just temporary fix
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
    - Use pre-computed CRTC layout size for computing screen size (LP: #1874567,
      LP: #1873403)
    - Decouple the output mode from layout mode capabilities (LP: #1876894,
      LP: #1886996)
    - Ensure we notify CRTC changes on integer scaling changes (LP: #1876894)
    - Apply proper layout monitor config when using fractional scaling
      (LP: #1884754)
    - Restore the fractional settings when reverting to fractional layout
      (LP: #1886996)
  * debian/libmutter-6-0.symbols: Add new private symbol

 -- Marco Trevisan (Treviño) <email address hidden> Mon, 27 Jul 2020 17:04:41 +0200

Changed in mutter (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Mathew Hodson (mhodson)
no longer affects: gnome-control-center (Ubuntu Focal)
no longer affects: gnome-control-center (Ubuntu)
no longer affects: nvidia-graphics-drivers-340 (Ubuntu Focal)
no longer affects: nvidia-graphics-drivers-340 (Ubuntu)
no longer affects: nvidia-graphics-drivers-440 (Ubuntu Focal)
no longer affects: nvidia-graphics-drivers-440 (Ubuntu)
no longer affects: nvidia-graphics-drivers-435 (Ubuntu Focal)
no longer affects: nvidia-graphics-drivers-435 (Ubuntu)
jeremyszu (os369510)
no longer affects: oem-priority
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.