*** This bug is a duplicate of bug 1854531 ***
    https://bugs.launchpad.net/bugs/1854531

** This bug is no longer a duplicate of bug 1854532
   Gnome Display Manager 3 fails to run Xorg the first reboot after I set 
WaylandEnabled to false in gdm3's custom.conf file
** This bug has been marked a duplicate of bug 1854531
   [radeon] Ubuntu fails to run Xorg the first reboot after I set 
WaylandEnabled to false in gdm3's custom.conf

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1854533

Title:
  Gnome Display Manager 3 fails to run Xorg the first reboot after I set
  WaylandEnabled to false in gdm3's custom.conf file

Status in mutter package in Ubuntu:
  New

Bug description:
  Whenever I set Wayland to false in Gnome Display Manager's custom.conf
  file and then reboot, I still see the same scrambled graphics on the
  machine as if it were using Wayland. Rebooting the machine a SECOND
  time resolves the issue. However, I should not have to reboot twice
  for the new setting to take effect.

  Steps to Reproduce:
  1. When the machine boots up with scrambled graphics, press Control+Alt+F3
  2. Log into the machine using the tty session and run "sudo editor 
/etc/gdm3/custom.conf
  3. Set Wayland to false and reboot
  4. Notice after reboot the same scrambled graphics appear until the user 
reboots again

  Expected Results:
  Gnome Display Manager runs xorg and xorg shows the correct graphics for the 
machine.

  Actual Results:
  Graphics are scrambled and settings do not appear to take effect until next 
reboot.

  This issue occurred right before 12:45 PM, EDT, on November 29, 2019.

  Description: Ubuntu 18.04.3 LTS
  Release: 18.04

  mutter:
    Installed: 3.28.4-0ubuntu18.04.2
    Candidate: 3.28.4-0ubuntu18.04.2
    Version table:
   *** 3.28.4-0ubuntu18.04.2 500
          500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
          100 /var/lib/dpkg/status
       3.28.1-1ubuntu1 500
          500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  xorg:
    Installed: 1:7.7+19ubuntu7.1
    Candidate: 1:7.7+19ubuntu7.1
    Version table:
   *** 1:7.7+19ubuntu7.1 500
          500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
          100 /var/lib/dpkg/status
       1:7.7+19ubuntu7 500
          500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  gdm3:
    Installed: 3.28.3-0ubuntu18.04.4
    Candidate: 3.28.3-0ubuntu18.04.4
    Version table:
   *** 3.28.3-0ubuntu18.04.4 500
          500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
          500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
          100 /var/lib/dpkg/status
       3.28.0-0ubuntu1 500
          500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 29 12:59:16 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1854533/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to