from:"Eric"

This issue appears to be resolved for me.

I used `apt purge gnome-shell-extensions` to remove gnome-shell-
extensions and noticed that 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-
d...@ubuntu.com', and 'desktop-icons@csoriano' remained in /usr/share
/gnome-shell/extensions/. I manually removed these extensions,
reinstalled gnome-shell-extensions, and rebooted my machine, and I have
not had a crash since. Note that I did not remove any extensions from
.local/share/gnome-shell/extensions, although there is still a
discrepancy between the installed extensions and what is listed in
`gsettings get org.gnome.shell enabled-extensions` and `gsettings get
org.gnome.shell disabled-extensions`. Should this be corrected by just
using `gsettings set`, or should this be updated automatically?

If there is any more information that I can provide to help troubleshoot
this problem for others with this same problem, please let me know.

Thanks!

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

Title:
  gnome-shell crashed with assertion failure
  "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

In my original bug report (https://bugs.launchpad.net/ubuntu/+source
/gnome-shell/+bug/1924625) I was asked to remove many extensions;
however, many of those extensions are ones that I installed at one time
but have since removed and they do not appear under ~/.local/share
/gnome-shell/extensions/.

>From https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1924625/+attachment/5488541/+files/GsettingsChanges.txt it is
clear that something is still reporting them as being installed. Does
this indicate that there are remnants of these extensions somewhere else
on my machine?

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

Title:
  gnome-shell crashed with assertion failure
  "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

Before removing any extensions, I followed the instructions in #11. The
bug report can be found here: https://bugs.launchpad.net/ubuntu/+source
/gnome-shell/+bug/1924753.

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

Title:
  gnome-shell crashed with assertion failure
  "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1924753] [NEW] gnome-shell repeatedly crashing and core dumping

Public bug reported:

This is a repeat of bug 1886059 with "MUTTER_SYNC=1" added to
/etc/environment.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
Uname: Linux 5.4.0-72-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 16 06:26:22 2021
DisplayManager: gdm3
InstallationDate: Installed on 2019-07-31 (625 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-05-09 (341 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1924753

Title:
  gnome-shell repeatedly crashing and core dumping

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1924753/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1924625] [NEW] gnome-shell repeatedly restarting and core dumping

2021-04-15 Thread Eric Van Horn

Public bug reported:

Yesterday (2021-04-14) I ran apt update/upgrade, then rebooted my laptop
overnight. With the upgrade Linux 5.4.0-71 was installed. Now I have an
issue where gnome-shell restarts repeatedly. Looking in the logs, I see
that gnome-shell is core dumping when this occurs. I have not (yet)
identified any behavior that causes the problem.

I disabled extensions with the Gnome Tweak Tool and rebooted into the
previous Linux version but the problem remains. This may be related to
https://bugs.launchpad.net/bugs/1923864 and
https://bugs.launchpad.net/bugs/1924606 as the symptoms are similar and
both have been reported in within the correct time frame.

The contents of the log file from an instance of this occurring is
attached.

I am using Ubuntu 20.04.2
gnome-shell version is 3.36.7-0ubuntu0.20.04.1

Please let me know if you have any questions.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
Uname: Linux 5.4.0-72-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 15 17:37:46 2021
DisplayManager: gdm3
InstallationDate: Installed on 2019-07-31 (624 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-05-09 (341 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

** Attachment added: "Log message from gnome-shell core dump"
   
https://bugs.launchpad.net/bugs/1924625/+attachment/5488539/+files/log%20messages

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1924625

Title:
  gnome-shell repeatedly restarting and core dumping

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1924625/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2021-04-07 Thread Eric Desrochers

Any idea when Focal will be completed ?

Regards,
Eric

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

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2020-11-20 Thread Eric Desrochers

(I have ping sil2100 internally for him to provide his 2 cents on this
bug.)

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

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2020-11-20 Thread Eric Desrochers

Lukasz (sil2100) can we have your SRU team input on this bug with regard
to Bionic/18.04lTS ?

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

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1896091] Re: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions

2020-11-03 Thread Eric Mazoob

The problem goes away after the screen times out and I have to log back
in.

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

Title:
  [i915] Noise-like lines of graphics corruption when moving windows in
  Xorg sessions

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1896091] Re: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions

2020-11-03 Thread Eric Mazoob

I'm on 20.10 using KDE, 5.8.0-26-generic, on a dell xps 13 2-in-1 and
the problem is rather severe.

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

Title:
  [i915] Noise-like lines of graphics corruption when moving windows in
  Xorg sessions

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2020-10-26 Thread Eric Desrochers

I unfortunately don't have a smartcard device handy to test/debug/
but if I compare with RHEL which is known to be working...

Redhat has the following configuration "gdm-smarcard" which includes
"smartcard-auth", a symlink pointing to "smartcard-auth-local"

I think we should 'mimic' this (at least as a starting point) without
the selinux and other RHEL specific bits.

- Eric

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

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2020-10-16 Thread Eric Desrochers

# git clone https://gitlab.gnome.org/GNOME/gdm.git

# find . -name "gdm-smartcard*"
./data/pam-arch/gdm-smartcard.pam
./data/pam-redhat/gdm-smartcard.pam
./data/pam-exherbo/gdm-smartcard.pam
./data/pam-lfs/gdm-smartcard.pam

It seems like Ubuntu/Debian will have to start by having a 'compatible'
PAM stack config.

So far looking upstream, it seems to only be defined for 4 specific distros:
- Archlinux
- Redhat
- Exherbo
- Linux From Scratch (LFS)

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

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2020-10-13 Thread Eric Desrochers

** Changed in: gdm3 (Ubuntu Groovy)
   Importance: Medium => High

** Also affects: pam (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: gdm3 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: pam (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: gdm3 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gdm3 (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: gdm3 (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: gdm3 (Ubuntu Bionic)
   Importance: Undecided => High

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

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2020-09-25 Thread Eric Desrochers

** Changed in: gdm3 (Ubuntu Groovy)
   Importance: Low => Medium

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

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2020-09-25 Thread Eric Desrochers

It has been brought to my attention by a UA customer that they are
suffering from which seems a similar situation:

"
Our only currently working SmartCard access from Linux, over SSSD, to AD, is on 
RHEL7.
I was able to get SSH access on Ubuntu 20.04LTS, after adding 
"ad_gpo_access_control = permissive" in sssd.conf.

Logging in locally fails (prompting for password, rather than PIN). It
is also still prompting for the Password twice on all local login
attempts.

RHEL7 -> Ubuntu 20.04LTS (SSH) - Success
Ubuntu 20.04LTS -> RHEL7 (SSH) - Success
Ubuntu Desktop login (GDM or CLI) - Fail
Ubuntu Desktop login via local username/pw - Success, but with 2 pw prompts.
"

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

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome

2020-08-31 Thread Eric Perret

I am seeing the same issue on 18.04.5 LTS

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766230

Title:
  Strange window matching behaviour between Slack and Chrome

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1719143] Re: Unable to calibrate monitors through Gnome Control Center->Color in artful

2020-05-28 Thread Carl-Eric Menzel

This happened to me just now on a fresh installation of 20.04. Exactly
as reported - first attempt at calibration with a Spyder 3 fails, on the
second attempt gnome-control-center crashes hard.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1719143

Title:
  Unable to calibrate monitors through Gnome Control Center->Color in
  artful

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1719143/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."

2020-05-08 Thread Eric G. Stern

For me it affects IMAP mail retrieval from imap.aol.com.

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

Title:
  Evolution reports "Error performing TLS handshake: Internal error in
  memory allocation."

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1872461] Re: gnome-shell extension 'sound-output-device-chooser' crashed with SIGABRT in gvc_mixer_card_get_profile()

2020-04-14 Thread Eric Adams

Thanks for letting me know. Is it advisable to provide any of the data
collected here to a third party?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1872461

Title:
  gnome-shell extension 'sound-output-device-chooser' crashed with
  SIGABRT in gvc_mixer_card_get_profile()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872461/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1871668] Re: File selection status message overlays bottom icons making them unreadable

2020-04-08 Thread Eric Adams

Nevermind. I figured out that if I hover over the message text it is
hidden so I can see the file names.

** Changed in: nautilus (Ubuntu)
   Status: New => Invalid

** Attachment removed: "Screenshot of issue"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1871668/+attachment/5349730/+files/Screenshot%20from%202020-04-08%2011-36-50.png

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1871668/+attachment/5349731/+files/Dependencies.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1871668/+attachment/5349732/+files/ProcCpuinfoMinimal.txt

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

Title:
  File selection status message overlays bottom icons making them
  unreadable

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1871668] [NEW] File selection status message overlays bottom icons making them unreadable

2020-04-08 Thread Eric Adams

Public bug reported:

Selecting one or more files in nautilus shows a message at the bottom
right (i.e. 6 folders selected (containing a total of...). This message
overlays the name of the file or folder items at the bottom of the
window making it impossible to see the names. See attachment to see what
I mean.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.1.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu25
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  8 11:45:54 2020
GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' 
b"'standard'"
InstallationDate: Installed on 2020-04-08 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot of issue"
   
https://bugs.launchpad.net/bugs/1871668/+attachment/5349730/+files/Screenshot%20from%202020-04-08%2011-36-50.png

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

Title:
  File selection status message overlays bottom icons making them
  unreadable

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1871456] [NEW] Files on desktop don't use custom icon

2020-04-07 Thread Eric Haberstroh

Public bug reported:

Steps to reproduce:

1. Create a new file in the folder "~/Desktop".
2. Right-click -> Properties -> change the icon to some other icon from 
/usr/share/icons/Yaru/48x48.
3. Close the "Properties" dialogue.

When viewing the Desktop folder in Nautilus directly, the icon is
displayed correctly. However on the desktop itself, the file still uses
the default icon.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  7 19:33:47 2020
GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 
'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 
'starred', 'detailed_type']"
InstallationDate: Installed on 2020-04-06 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  Files on desktop don't use custom icon

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853185] Re: Evolution dark theme + 'save' imposes dark theme in message

** Tags added: theme

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

Title:
  Evolution dark theme + 'save' imposes dark theme in message

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853185] Re: Evolution dark theme + 'save' imposes dark theme in message

** Attachment added: "Screenshots of a message being sent and received without 
dark formatting; Screenshot of a message being saved and reopened with dark 
formatting"
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1853185/+attachment/5306494/+files/Evolution%20dark%20theme%20+%20save%20imposes%20dark%20theme%20in%20message.png

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

Title:
  Evolution dark theme + 'save' imposes dark theme in message

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853185] [NEW] Evolution dark theme + 'save' imposes dark theme in message

Public bug reported:

1)The release of Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04

2)The version of the package
evolution:
  Installed: 3.28.5-0ubuntu0.18.04.1
  Candidate: 3.28.5-0ubuntu0.18.04.1
  Version table:
 *** 3.28.5-0ubuntu0.18.04.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 3.28.1-2 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

The problem is very similar to https://mail.gnome.org/archives
/evolution-list/2016-November/msg00063.html, which describes the problem
very well.

3)What I expect
I use the Evolution for OWA with a dark theme and "Inherit theme colors in HTML 
mode" turned OFF.  The editor works very well as described in the 
aforementioned mailing list and sends messages with the white background even 
though I am editing them with a dark background.  When I save, I expect to be 
able to reopen the email and continue editing without any changes.  I expect 
the saved copy to be exactly the same as if I was going to send it so that I 
can open it on any other machine and send it exactly as if I had sent it 
instead of saving it.

4)What happens instead
The problem comes in when I save the HTML message and then re-open it from the 
server in another editor.  This only really happens when I start editing on one 
computer and finish on another because I am missing a file to attach or 
something.  It appears as though the HTML changes to match the theme are saved 
to the server.

Thank you!

** Affects: evolution (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Screenshots of a message being sent and received without 
dark formatting; Screenshot of a message being saved and reopened with dark 
formatting"
   
https://bugs.launchpad.net/bugs/1853185/+attachment/5306487/+files/Screenshot_2019-11-19_10-58-14.png

** Description changed:

- 1)
+ 1)The release of Ubuntu
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  
- 2)
+ 2)The version of the package
  evolution:
-   Installed: 3.28.5-0ubuntu0.18.04.1
-   Candidate: 3.28.5-0ubuntu0.18.04.1
-   Version table:
-  *** 3.28.5-0ubuntu0.18.04.1 500
- 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
- 100 /var/lib/dpkg/status
-  3.28.1-2 500
- 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
+   Installed: 3.28.5-0ubuntu0.18.04.1
+   Candidate: 3.28.5-0ubuntu0.18.04.1
+   Version table:
+  *** 3.28.5-0ubuntu0.18.04.1 500
+ 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
+ 100 /var/lib/dpkg/status
+  3.28.1-2 500
+ 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  
  The problem is very similar to https://mail.gnome.org/archives
  /evolution-list/2016-November/msg00063.html, which describes the problem
  very well.
  
- 3)
- I use the Evolution for OWA with a dark theme and "Inherit theme colors in 
HTML mode" turned OFF.  The editor works very well as described in the 
aforementioned mailing list and sends messages with the white background even 
though I am editing them with a dark background.  When I save, I expect to be 
able to reopen the email and continue editing without any changes.  I expect 
the saved copy to be exactly the same as if I was going to send it so that I 
can open it on any other machine and send it exactly as if I had sent it 
instead of saving it.  
+ 3)What I expect
+ I use the Evolution for OWA with a dark theme and "Inherit theme colors in 
HTML mode" turned OFF.  The editor works very well as described in the 
aforementioned mailing list and sends messages with the white background even 
though I am editing them with a dark background.  When I save, I expect to be 
able to reopen the email and continue editing without any changes.  I expect 
the saved copy to be exactly the same as if I was going to send it so that I 
can open it on any other machine and send it exactly as if I had sent it 
instead of saving it.
  
- 4)
- The problem comes in when I save the HTML message and then re-open it from 
the server in another editor.  This only really happens when I start editing on 
one computer and finish on another because I am missing a file to attach or 
something.  It appears as though the HTML changes to match the theme are saved 
to the server.  
- 
+ 4)What happens instead
+ The problem comes in when I save the HTML message and then re-open it from 
the server in another editor.  This only really happens when I start editing on 
one computer and finish on another because I am missing a file to attach or 
something.  It appears as though the HTML changes to match the theme are saved 
to the server.
  
  Thank you!

** Attachment removed: "Screenshots of a message being sent and received 
without dark formatting; Screenshot of a message being saved and reopened with 
dark formatt

[Bug 1853185] Re: Evolution dark theme + 'save' imposes dark theme in message

Removed incorrectly attached file and attached correct screenshot of the
issue.

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

Title:
  Evolution dark theme + 'save' imposes dark theme in message

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-07-03 Thread Eric Desrochers

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-07-02 Thread Eric Desrochers

The testing phase where the kernel will land in bionic-proposed pocket is due 
around :
08-Jul - 19-Jul Bug verification & Regression testing

This is where I'll need you guys to test the proposed kernel and confirm
it still work as expected for you.

- Eric

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-28 Thread Eric Desrochers

Just got the 2 required ACK from kernel team for the patch I have submitted.
Everything looks good for the patch to be part of the next kernel cycle as 
described in previous comment.

- Eric

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-26 Thread Eric Desrochers

Todd, The fix will land in the next kernel cycle.

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-21 Thread Eric Desrochers

kernel-team archive ML:
https://lists.ubuntu.com/archives/kernel-team/2019-June/101489.html

** Description changed:

[Impact]

With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in white at the bottom, nothing
else.

The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using
the wrong clock. This would lead us to wait forever (or at least 49 years)
before rendering the next frame. There's no decisive way to know this kernel
bug is going to happen before it does so just detect timestamps which are
obviously going to cause freezes and ignore them.

[Test case]

1) Use Virtualbox or VMware ESxi (if you have the infra)
1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA'
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm
with 'lspci -nnvv' command.
2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
4) apt-get dist-upgrade
5) Reboot

with 4.15 it will fails
with hwe kernel 4.18 it will work as expected. # workaround

[Potential regression]

Low, it should fix vmwgfx and stop using the wrong clock.

A test kernel (pre-sru) has been made available to impact users for them
to test and conclude it works. It does work as expected, and no
regression has been found during the pre-sru testing phase.
-
- It can't be worse than actual situation where the login never appears.

As per commit description:

"
This should be transparent to to user space, as long as it doesn't
compare the time against the result of gettimeofday().
"

[Other informations]

upstream fix:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5&id=37efe80ce85f

[Original description]

I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook
Pro.

I've been running this Ubuntu 18.04.2 VM without problem for many months
without problem.
Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the
system hangs immediately after displaying the splash screen. I never see a
login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

I can SSH into the system however.

I've found that I can work around the hang/freeze if I uncomment the
following line in /etc/gdm3/custom.conf;
#WaylandEnable=false

After uncommenting the WaylandEnable=false line and rebooting, then I
see the login prompt as expected and I can then log in and use the
system normally again.

After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as
shown in this 'uname -a' output;

Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a output;

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Sun Jun 9 12:38:37 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2018-05-06 (399 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/13/2018
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz N/A

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

** Description changed:

[Impact]

[Test case]

with 4.15 it will fails
with hwe kernel 4.18 it will work as expected. # workaround

[Potential regression]

Low, it should fix vmwgfx and stop using the wrong clock.

A test kernel (pre-sru) has been made available to impact users for them
to test and conclude it works. It does work as expected, and no
regression has been found during the pre-sru testing phase.

It can't be worse than actual situation where the login never appears.
+
+ As per commit description:
+
+ "
+ This should be transparent to to user space, as long as it doesn't
+ compare the time against the result of gettimeofday().
+ "

[Other informations]

upstream fix:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5&id=37efe80ce85f

[Original description]

I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook
Pro.

I can SSH into the system however.

I've found that I can work around the hang/freeze if I uncomment the
following line in /etc/gdm3/custom.conf;
#WaylandEnable=false

After uncommenting the WaylandEnable=false line and rebooting, then I
see the login prompt as expected and I can then log in and use the
system normally again.

After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as
shown in this 'uname -a' output;

Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a output;

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

Ok, including my own testing we got 4 positive feedback. 
With that being said, I have just submitted the patch to our kernel team a few 
minutes ago.

This will be part of the next cycle 01-July through 21-July.

Thanks for the pre-SRU testing, we will need you guys one more time
during the testing phase of bionic-proposed in a couple of weeks.

- Eric


** Tags added: sts

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

** Description changed:

[Impact]

[Test case]

with 4.15 it will fails
with hwe kernel 4.18 it will work as expected. # workaround

[Potential regression]

- Low, it should fix vmwgfx and stop using the wrong clock. Sure thing, it
- can't be worse than actual situation where the login doesn't appears at
- all.
+ Low, it should fix vmwgfx and stop using the wrong clock.
+
+ A test kernel (pre-sru) has been made available to impact users for them
+ to test and conclude it works. It does work as expected, and no
+ regression has been found during the pre-sru testing phase.
+
+ It can't be worse than actual situation where the login never appears.

[Other informations]

upstream fix:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5&id=37efe80ce85f

[Original description]

I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook
Pro.

I can SSH into the system however.

I've found that I can work around the hang/freeze if I uncomment the
following line in /etc/gdm3/custom.conf;
#WaylandEnable=false

After uncommenting the WaylandEnable=false line and rebooting, then I
see the login prompt as expected and I can then log in and use the
system normally again.

After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as
shown in this 'uname -a' output;

Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a output;

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

Great for the quick feedback.

I have until June 26th to submit the patch for the next cycle[0]

It's giving me a couple of more days to get other impacted users
feedback.

[0] - https://kernel.ubuntu.com/

- Eric

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu Bionic)
   Importance: Critical => High

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

Detailled instructions on how to use my ppa :

$ sudo add-apt-repository ppa:slashd/kernel-builder
$ sudo apt-get update
$ sudo apt install linux-image-unsigned-4.15.0-53-generic 
linux-modules-4.15.0-53-generic linux-modules-extra-4.15.0-53-generic

then reboot, and once login you can confirm if you run my test kernel
with "uname -a" which should report "4.15.0-53.57+hf231164v20190620b11"

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

** Description changed:

+ [Impact]
+ 
+ With most recent version of mutter installed. 
+ If running kernel is in the 4.15 serie (using the vmwgfx video kernel drive) 
and if the login screen uses wayland, then the login prompt doesn't appears.
+ All we see is the purple background with ubuntu at the bottom, nothing else.
+ 
+ The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
+ before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.
+ 
+ [Test case]
+ 
+ 1) Use Virtualbox or VMware ESxi (if you have the infra)
+  - [vbox] Make sure in the VM setting that the display uses 'VMSVGA' which 
will force the OS to pick 'vmwgfx' video kernel driver. (you can confirm with 
'lspci -nnvv' command.
+ 2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
+ 4) apt-get dist-upgrade
+ 5) Reboot
+ 
+ with 4.15 it will fails
+ with hwe kernel 4.18 it will work as expected.
+ 
+ [Potential regression]
+ 
+ Low, it should fix vmwgfx and stop using the wrong clock. Sure thing, it
+ can't be worst than current situation where the login doesn't appears at
+ all.
+ 
+ [Other informations]
+ 
+ upstream fix:
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5&id=37efe80ce85f
+ 
+ [Original description]
+ 
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook
  Pro.
  
  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.
  
  I can SSH into the system however.
  
  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false
  
  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.
  
  After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as
  shown in this 'uname -a' output;
  
  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC
  2019 x86_64 x86_64 x86_64 GNU/Linux
  
  lsb_release -a output;
  
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
-  VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
-Subsystem: VMware SVGA II Adapter [15ad:0405]
+  VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
+    Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-inp

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

After building and testing:

"
9c5f23a4a699 drm/vmwgfx: use monotonic event timestamps
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
"

the above seems to do the trick ^ which will make the SRU easier (only one 
commit).
I just don't know why the kernel git bisect testing found another commit, but 
anyway.

Anybody impacted want to test this testpkg to double-check before I
submit the patch to the kernel team ?

sudo add-apt-repository ppa:slashd/kernel-builder
sudo apt-get update

Version: 4.15.0-53.57+hf231164v20190620b11

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

I already did that test ^  using the upstream kernel with 37efe80ce85f
being the HEAD, but "37efe80ce85f" - 1 was working as well, so I didn't
continue to pursue that commit, since it wasn't the first introduction
of the fix.

But based on last duflu update, I as I said I will now give a try again
but this time using Ubuntu kernel as follow:

9c5f23a4a699 drm/vmwgfx: use monotonic event timestamps
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57

Let's see what will be the outcome in a couple of hours.

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

Will also build a kernel 4.15 with 37efe80ce85f and see the outcome.
Should be able to provide an update by EOD.

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

My reproducer:

1) I used virtualbox 6.0.0 on disco (my desktop machine) # I guess it doesn't 
really matter but I prefer giving more details than less ;)
2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
3) Make sure in the VM setting that the display uses 'VMSVGA' which will force 
the OS to pick 'vmwgfx' video kernel driver. (you can confirm with 'lspci 
-nnvv' command.
4) apt-get dist-upgrade 

Then reboot and the login screen won't be shown again using v4.15 kernel.
Switch to 4.18 will work.

Regards,
Eric

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

To continue on my comment #59 ... One user has been impacted on a
physical machine (non-vmware) with the same symptom but can't provide
public details unfortunately, but I witnessed the problem from my own
eye via remote session, and again upgrading to 4.18 kernel did the
trick.

So it really seems like 4.15 is possibly incompatible at some point with
the current mutter package. That is my believe with the level of details
that I know for now and what has been shared to me.

Daniel, any thoughts on this ?
I will try to contact you on irc tonight if we can manage to fight the TZ gap 
between us. ;)

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

as an fyi ...

It has been brought to my attention that this could impact other system 
(outside vmware context)
so I still suspect a userspace change (possibly mutter) that introduce 
behaviour change and break the interaction with certain part of the 4.15 kernel.

Do we know if the recent point release has been tested with different
kernel series ? 4.15, 4.18, ... or only 4.18 ?

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

of if we identify the offending userspace change, then we can look at
the kernel again and try to find what bit are missing, and if we limit
the kernel change then maybe the side-effect won't be present too.

I think the next step is really to find what userspace change started
all this so we can find the related kernel change to backport (without
doing that massive 6 commits backport, which as a side-effect and who
know what else).

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

or if we identify the offending userspace change, then we can look at
the kernel again with and try to find what bit are missing, and if we
limit the kernel change then maybe the side-effect might not be present
again. (assumption here)

I think the next step is really to find what userspace change started
all this so we can related kernel known fix to be part of the final
backport (without doing that massive 6 commits backport, which as a
side-effect and who know what else).

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

Daniel van Vugt (vanvugt),

Do you know what change could have introduced this vmwgfx/wayland
interaction problem inside mutter in the first place ?

I have strong believe, that something userspace has been changed and no
longer interact well with the vmware driver since then.

Just to look at our option (since a kernel fix might be not end up being
trivial) does a revert of the change could be a possibility here ? or
else.

Ideally, I agree I would have prefer to fix the kernel and I'm also
going to pursue that direction, but just looking other avenues in case
of ...

Thanks

- Eric

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

The patchset is significant already without knowing yet what is missing to 
address the side-effect.
I would need kernel team review/approval before thinking to SRU this into 
Ubuntu 4.15.

I can't SRU this as-is, now knowing this will introduce a regression.

I'll keep you guys posted.

- Eric

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

Do you have the same display resizing situation with the hwe kernel 4.18
?

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

It's working if I apply the whole chain of commit on top of Ubuntu-4.15

I'll need to talk with kernel team and see if this is feasible for an
SRU.

52a59da2c439 drm/vmwgfx: Send the correct nonblock option for atomic_commit
cfffdaad3db9 drm/vmwgfx: Move the stdu vblank event to atomic function
b8d2ffa1798c drm/vmwgfx: Move screen object page flip to atomic function
3e67818b5a0e drm/vmwgfx: Remove drm_crtc_arm_vblank_event from atomic flush
700b155d6492 drm/vmwgfx: Move surface copy cmd to atomic function
4c7224123ecf drm/vmwgfx: Avoid iterating over display unit if crtc is available
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57


https://www.spinics.net/lists/dri-devel/msg162472.html

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

My test kernel can be found here, if one want to test:

sudo add-apt-repository ppa:slashd/kernel-builder
sudo apt-get update

version: 4.15.0-53.57+hf231164v20190618b9

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

This commit has most likely other 'drm/vmwgfx' commit deps. I'll work at
finding what other bits are missing.

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

I have applied the good fix on top of current branch 4.15.0-53.57

---
c6d53184e8b8 drm/vmwgfx: Send the correct nonblock option for atomic_commit
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
---

Build the kernel and I got the same problem still. Need to investigate
why it works fine using upstream when that good commit but still get the
situation with Ubuntu kernel + the same good commit.

I'll do more testing.

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

I have applied the good fix on top of current branch 4.15.0-53.57

---
c6d53184e8b8 drm/vmwgfx: Send the correct nonblock option for atomic_commit
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
---

Build the kernel and I got the same problem still. Need to investigate
why it works fine using upstream but still get the situation with Ubuntu
kernel + good commit.

I'll do more testing.

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

I'll do my best to provide a test kernel by tomorrow, for impacted user
to test, and confirm it works before I submit it to the Ubuntu kernel
team.

Stay tuned.

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA
ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but
ac3069e67f5659131d7ac5f54d966005bbc40af8 doesn't.

So the kernel bisection is completed and found the right good commit
which is:
https://github.com/torvalds/linux/commit/904efd9e3f4c8f288b1279a316eed8e177190c8f

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA
ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but
904efd9e3f4c8f288b1279a316eed8e177190c8f doesn't.

So the kernel bisection is completed and found the right good commit
which is:
https://github.com/torvalds/linux/commit/904efd9e3f4c8f288b1279a316eed8e177190c8f

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

https://github.com/torvalds/linux/commit/904efd9e3f4c8f288b1279a316eed8e177190c8f

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

wbug: With Bug
wnbug: With No Bug

git bisect start '--term-old=wbug' '--term-new=wnbug' '--' 
'drivers/gpu/drm/vmwgfx' 
# wbug: [62e9ccfaaedffd057e921fca976f9f7f71c9b254] Linux 4.16.18 
git bisect wbug 62e9ccfaaedffd057e921fca976f9f7f71c9b254 
# wnbug: [37efe80ce85f76b3b30d7b4ea40550e6a5a5b71a] drm/vmwgfx: use monotonic 
event timestamps 
git bisect wnbug 37efe80ce85f76b3b30d7b4ea40550e6a5a5b71a 
# wbug: [7928b2cbe55b2a410a0f5c1f154610059c57b1b2] Linux 4.16-rc1 
git bisect wbug 7928b2cbe55b2a410a0f5c1f154610059c57b1b2 
# wbug: [aa64b3f18aeb2cc4b74e69115df434147f1ed96c] drm/vmwgfx: Move screen 
object page flip to atomic function 
git bisect wbug aa64b3f18aeb2cc4b74e69115df434147f1ed96c 
# wnbug: [dc366364c4ef809dccd063919314301f8ba01ac2] drm/vmwgfx: Fix multiple 
command buffer context use 
git bisect wnbug dc366364c4ef809dccd063919314301f8ba01ac2 
# wnbug: [25db875401c8aaac31a6650cb80a56cc78852694] drm/vmwgfx: Cursor update 
fixes 
git bisect wnbug 25db875401c8aaac31a6650cb80a56cc78852694 
# wnbug: [904efd9e3f4c8f288b1279a316eed8e177190c8f] drm/vmwgfx: Send the 
correct nonblock option for atomic_commit 
git bisect wnbug 904efd9e3f4c8f288b1279a316eed8e177190c8f 
# wbug: [ac3069e67f5659131d7ac5f54d966005bbc40af8] drm/vmwgfx: Move the stdu 
vblank event to atomic function 
git bisect wbug ac3069e67f5659131d7ac5f54d966005bbc40af8 
# first wnbug commit: [904efd9e3f4c8f288b1279a316eed8e177190c8f] drm/vmwgfx: 
Send the correct nonblock option for atomic_commit

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

** Changed in: linux (Ubuntu Bionic)
   Status: Confirmed => In Progress

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

"20fb5a635a0c" also works just fine on my side, will continue with the
kernel bisect.

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

Building a kernel with "37efe80ce85f drm/vmwgfx: use monotonic event
timestamps" being the HEAD doesn't exhibit the issue.

I'm now building and about to test 37efe80ce85f^1 (AKA 20fb5a635a0c) to confirm.
In theory it should fails with "20fb5a635a0c" if "37efe80ce85f" is the one.

- Eric

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-16 Thread Eric Desrochers

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Eric Desrochers (slashd)

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

Testing upstream kernel, I can tell this situation is not a Ubuntu kernel 
specific issue.
I can reproduce using upstream kernel.

This is where I'm at the moment:
BAD  kernel : v4.16.18
GOOD kernel : v4.17-rc1

Leaving us to the following 'vmwgfx' commits to bisect:


$ git log --oneline v4.16.18..v4.17-rc1 --grep="drm/vmwgfx:"

320b164abb32 Merge tag 'drm-for-v4.17' of 
git://people.freedesktop.org/~airlied/linux
2a2553cc45c8 Merge branch 'vmwgfx-next' of 
git://people.freedesktop.org/~thomash/linux into drm-next
43bfefedd028 drm/vmwgfx: Bump version patchlevel and date
37efe80ce85f drm/vmwgfx: use monotonic event timestamps
20fb5a635a0c drm/vmwgfx: Unpin the screen object backup buffer when not used
89dc15b76fd3 drm/vmwgfx: Stricter count of legacy surface device resources
6073a09210e0 drm/vmwgfx: Use kasprintf
4e3e733b45df drm/vmwgfx: Get rid of the device-private suspended member
c3b9b1657344 drm/vmwgfx: Improve on hibernation
bf833fd36f9b drm/vmwgfx: Avoid pinning fbdev framebuffers
dc366364c4ef drm/vmwgfx: Fix multiple command buffer context use
ef86cfee7d74 drm/vmwgfx: Use the cpu blit utility for framebuffer to screen 
target blits
79273e1b7eb0 drm/vmwgfx: Add a cpu blit utility that can be used for 
page-backed bos
25db875401c8 drm/vmwgfx: Cursor update fixes
904efd9e3f4c drm/vmwgfx: Send the correct nonblock option for atomic_commit
ac3069e67f56 drm/vmwgfx: Move the stdu vblank event to atomic function
aa64b3f18aeb drm/vmwgfx: Move screen object page flip to atomic function
3cbe87fcf026 drm/vmwgfx: Remove drm_crtc_arm_vblank_event from atomic flush
4e2f9fa7ffb5 drm/vmwgfx: Move surface copy cmd to atomic function
91e9f352cd1b drm/vmwgfx: Avoid iterating over display unit if crtc is available
25a28906ebee drm/vmwgfx: replace drm_*_unreference with drm_*_put
4f4becef17d6 drm/vmwgfx: Use drm_mode_get_hv_timing() to populate plane clip 
rectangle


As I said, I'll start the bisection on Monday.
My first feeling about the potential good candidate assumption was wrong but 
with recent testing, we now know the fix is amongst the commits listed above ^

- Eric

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

Thanks Pat.

Glad you had the same result as I did. 
I will start the kernel bisect to find out the commit which introduce the fix 
and confirm my potential good candidate that I found by doing a git log 
inspection.

Will keep you guys posted.

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

I marked this bug affect the kernel 'linux' project, but I can't 'target
to series' and choose Bionic, it's not in the option list (something
went wrong with that bug I think, but we can figure this out later
(when/if an SRU is needed)):

The only option I have available are:
 Ff-series 
 Disco 
 Cosmic 
 Xenial 
 Trusty 
 Precise

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

I marked this bug affecting the kernel 'linux', but I can't 'target to
series' and choose Bionic. It's not in the option list anymore
(something went wrong with that bug I think, but we can figure this out
later (when/if an SRU is needed)):

The only option I have available are:
 Ff-series
 Disco
 Cosmic
 Xenial
 Trusty
 Precise

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832903] Re: 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver

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

Only when using v4.15, if I use the hwe kernel 4.18 on Bionic it passes.

I have strong belief this kernel fix to be a potential good candidate,
but I need to run a bisection to confirm my assumption :

commit 140bcaa23a1c37b694910424075a15e009120dbe
Author: Thomas Hellstrom 
Date: Thu Mar 8 10:07:37 2018 +0100

drm/vmwgfx: Fix black screen and device errors when running without
fbdev

When we are running without fbdev, transitioning from the login screen to
X or gnome-shell/wayland will cause a vt switch and the driver will disable
svga mode, losing all modesetting resources. However, the kms atomic state
does not reflect that and may think that a crtc is still turned on, which
will cause device errors when we try to bind an fb to the crtc, and the
screen will remain black.

Fix this by turning off all kms resources before disabling svga
mode.

Cc: 
Signed-off-by: Thomas Hellstrom 
Reviewed-by: Sinclair Yeh 

** This bug has been marked a duplicate of bug 1832138
   Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

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

Title:
  18.04.2 login screen doesn't work if it uses 'wayland' and if video
  kernel driver is 'vgwfx' kernel driver

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

can someone impacted try v4.18 hwr kernel ? and let me know if it works
fine (without workarounds) just like it did for me ? I will perform the
kernel bisect next week to see what v4.15 is missing that 4.18 has to
fix this bug.

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

I reported the exact same problem and was able to reproduce.

Only using v4.15, if I use the hwe kernel 4.18 on Bionic it passes.

I have strong belief this kernel fix to be a potential good candidate,
but need to run a bisection to confirm my assumption :


commit 140bcaa23a1c37b694910424075a15e009120dbe
Author: Thomas Hellstrom 
Date:   Thu Mar 8 10:07:37 2018 +0100

drm/vmwgfx: Fix black screen and device errors when running without
fbdev

When we are running without fbdev, transitioning from the login screen to
X or gnome-shell/wayland will cause a vt switch and the driver will disable
svga mode, losing all modesetting resources. However, the kms atomic state
does not reflect that and may think that a crtc is still turned on, which
will cause device errors when we try to bind an fb to the crtc, and the
screen will remain black.

Fix this by turning off all kms resources before disabling svga
mode.

Cc: 
Signed-off-by: Thomas Hellstrom 
Reviewed-by: Sinclair Yeh 

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

my bug report :
https://bugs.launchpad.net/bugs/1832903

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832903] Re: 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver

2019-06-14 Thread Eric Desrochers

I was able to reproduce the problem with 4.15.0-51, but problem seems to
be gone using the hwe kernel 4.18.0-21-generic.

I'll do a kernel bisection and try to find the commit which fixes the situation.
I'll also ask another impacted user to confirm if v4.18 works fine too, to 
double-check my testing.

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

Title:
  18.04.2 login screen doesn't work if it uses 'wayland' and if video
  kernel driver is 'vgwfx' kernel driver

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832903] [NEW] 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver

2019-06-14 Thread Eric Desrochers

Public bug reported:

After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login
screen doesn't work if 'Wayland' is in use (default) and if video kernel
driver is 'vgwfx'.

It looks like the login screen got stuck, doesn't exit, and doesn't
fallback to 'x11' by itself in case of failure.

Workaround:
- Access the machine via ssh or any other recovery approaches.
- Force the login screen to use x11:

File: /etc/gdm3/custom.conf
[daemon]
# Uncoment the line below to force the login screen to use Xorg
WaylandEnable=false

I tried to reproduce the behaviour on my personal laptop, KVM guest, ...
without success.

So far it is only reproducible when the 'vgwfx' driver is in use in
combination with Wayland.

lspci -nnvvv

00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] 
(prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
 Capabilities: [44] PCI Advanced Features
  AFCap: TP+ FLR+
  AFCtrl: FLR-
  AFStatus: TP-
 Kernel driver in use: vmwgfx
 Kernel modules: vmwgfx


** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: wayland (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: wayland (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login
- screen doesn't work if it 'wayland' is in use (default) and if video
- kernel driver inside is 'vgwfx'.
+ screen doesn't work if 'Wayland' is in use (default) and if video kernel
+ driver is 'vgwfx'.
  
  It looks like the login screen got stuck, doesn't exit, and doesn't
  fallback to 'x11' by itself in case of failure.
  
  Workaround:
- Force the login screen to use x11:
+ - Access the machine via ssh or any other recovery approaches.
+ - Force the login screen to use x11:
  
- File: /etc/gdm3/custom.conf 
+ File: /etc/gdm3/custom.conf
  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false
  
- I tried to reproduce the behaviour on my personal laptop, KVM guest, ... 
without success.
- So far it is only reproducible when the 'vgwfx' driver is in use in 
combination with Wayland.
+ I tried to reproduce the behaviour on my personal laptop, KVM guest, ...
+ without success.
  
+ So far it is only reproducible when the 'vgwfx' driver is in use in
+ combination with Wayland.
+ 
+ lspci -nnvvv
  
  00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] 
(prog-if 00 [VGA controller])
-   Subsystem: VMware SVGA II Adapter [15ad:0405]
-   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
-   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
-   Capabilities: [44] PCI Advanced Features
-   AFCap: TP+ FLR+
-   AFCtrl: FLR-
-   AFStatus: TP-
-   Kernel driver in use: vmwgfx
-   Kernel modules: vmwgfx
+  Subsystem: VMware SVGA II Adapter [15ad:0405]
+  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
+  Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
+  Capabilities: [44] PCI Advanced Features
+   AFCap: TP+ FLR+
+   AFCtrl: FLR-
+   AFStatus: TP-
+  Kernel driver in use: vmwgfx
+  Kernel modules: vmwgfx
  

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

Title:
  18.04.2 login screen doesn't work if it uses 'wayland' and if video
  kernel driver is 'vgwfx' kernel driver

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832426] Re: "Program" is not responding when debugging in gdb

2019-06-12 Thread Eric Shaw

Hi Marco,

No, the warning/dialog shows repeatedly.

I think if I'm debugging a program, ubuntu and gnome-shell should never
tell me the window is not responding. I might focus the window to use
it, or to set it above all others so I can watch it.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1832426

Title:
  "Program" is not responding when debugging in gdb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832426/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832426] [NEW] "Program" is not responding when debugging in gdb

2019-06-11 Thread Eric Shaw

Public bug reported:

I believe this is a regression for    
#1740869  is not responding window is constantly showing when 
debugging a program 

I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint
this window shows up and I can't get it to stop asking me to close the
program.

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
Description:Ubuntu 19.04
Release:19.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
gnome-shell:
  Installed: 3.32.1-1ubuntu1~19.04.1
  Candidate: 3.32.1-1ubuntu1~19.04.1
  Version table:
 *** 3.32.1-1ubuntu1~19.04.1 500
500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 3.32.0+git20190410-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages

3) What you expected to happen
When I hit a breakpoint in gdb, the program should stop.

4) What happened instead
The program stops and ubuntu asks me if i want to kill the program.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 11 22:03:44 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-06-08 (4 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1832426

Title:
  "Program" is not responding when debugging in gdb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832426/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1745846] Re: gnome-control-center won't open

2019-05-02 Thread Eric Karnes

I'm also affected by this bug

➜  ~ debsums gnome-control-center
/usr/bin/gnome-control-center OK
/usr/lib/gnome-control-center/cc-remote-login-helper  OK
/usr/lib/gnome-control-center/gnome-control-center-search-providerOK
/usr/share/applications/gnome-applications-panel.desktop  OK
/usr/share/applications/gnome-background-panel.desktopOK
/usr/share/applications/gnome-bluetooth-panel.desktop OK
/usr/share/applications/gnome-color-panel.desktop OK
/usr/share/applications/gnome-control-center.desktop  OK
/usr/share/applications/gnome-datetime-panel.desktop  OK
/usr/share/applications/gnome-default-apps-panel.desktop  OK
/usr/share/applications/gnome-display-panel.desktop   OK
/usr/share/applications/gnome-info-overview-panel.desktop OK
/usr/share/applications/gnome-keyboard-panel.desktop  OK
/usr/share/applications/gnome-mouse-panel.desktop OK
/usr/share/applications/gnome-network-panel.desktop   OK
/usr/share/applications/gnome-notifications-panel.desktop OK
/usr/share/applications/gnome-online-accounts-panel.desktop   OK
/usr/share/applications/gnome-power-panel.desktop OK
/usr/share/applications/gnome-printers-panel.desktop  OK
/usr/share/applications/gnome-privacy-panel.desktop   OK
/usr/share/applications/gnome-region-panel.desktopOK
/usr/share/applications/gnome-removable-media-panel.desktop   OK
/usr/share/applications/gnome-search-panel.desktopOK
/usr/share/applications/gnome-sharing-panel.desktop   OK
/usr/share/applications/gnome-sound-panel.desktop OK
/usr/share/applications/gnome-thunderbolt-panel.desktop   OK
/usr/share/applications/gnome-ubuntu-panel.desktopOK
/usr/share/applications/gnome-universal-access-panel.desktop  OK
/usr/share/applications/gnome-user-accounts-panel.desktop OK
/usr/share/applications/gnome-wacom-panel.desktop OK
/usr/share/applications/gnome-wifi-panel.desktop  OK
/usr/share/bash-completion/completions/gnome-control-center   OK
/usr/share/dbus-1/services/org.gnome.ControlCenter.SearchProvider.service OK
/usr/share/dbus-1/services/org.gnome.ControlCenter.serviceOK
/usr/share/doc/gnome-control-center/NEWS.gz   OK
/usr/share/doc/gnome-control-center/README.md OK
/usr/share/doc/gnome-control-center/changelog.Debian.gz   OK
/usr/share/doc/gnome-control-center/copyright OK
/usr/share/gnome-shell/search-providers/gnome-control-center-search-provider.ini
 OK
/usr/share/man/man1/gnome-control-center.1.gz OK
/usr/share/metainfo/gnome-control-center.appdata.xml  OK

** Changed in: gnome-control-center (Ubuntu)
   Status: Expired => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1745846

Title:
  gnome-control-center won't open

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745846/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

2019-04-17 Thread eric

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

The same thing just happened to me after an update.

Running `sudo kbd_mode -s` fixed it.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1508146

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1824661] Re: Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty.

2019-04-15 Thread Eric

Daniel,

As requested, Here is the prevboot.txt file. Please let me know if
there's anything else I can do to assist. Thanks.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824661/+attachment/5255919/+files/prevboot.txt

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

Title:
  Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to
  blank screen that flashes a couple times. Can't get to tty.

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1817738] Re: Can't change virtual terminal on login screen or when auto-login is enabled

2019-04-04 Thread Eric Desrochers

https://launchpad.net/ubuntu/+source/gdm3/+publishinghistory
Deleted Bionic  proposedmaingnome   3.28.3-0ubuntu18.04.5

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

Title:
  Can't change virtual terminal on login screen or when auto-login is
  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1817738/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled

2019-03-13 Thread Eric Desrochers

@vicamo,

Seems like you are experiencing the same problem as I experience when being on 
VT-1.
Which was part of the reason why we SRU'd this change to avoid gmd3 to use VT-1 
by default.
The problem can't be reproduce using other VT.

Seems like something acquires VT-1 (systemd ? gdm3 ?) and prevent the VT
switch for VT-1.

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

Title:
  Can't change virtual terminal when auto-login is enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1817738/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1637988] Re: gvfsd-nfs not present in gvfs-backends, why?

2019-03-11 Thread Eric Desrochers

** Tags added: sts

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

Title:
  gvfsd-nfs not present in gvfs-backends, why?

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled

Uploaded in bionic by desktop team. Thanks.

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

Title:
  Can't change virtual terminal when auto-login is enabled

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled

Note: Desktop team kindly offered to update the vcs and do the upload in
bionic on my behalf.

Thanks !

** Description changed:

  [Impact]
  
  When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
  preventing from changing foreground virtual terminal.
  
  [Test case]
  
  1) Install Bionic/18.04LTS Desktop
  
  2) Enable AutomaticLogin
   2.1) Modify /etc/gdm3/custom.conf
  # Enabling automatic login
    AutomaticLoginEnable = true
    AutomaticLogin = 
  
  3) Reboot your system and make sure AutoLogin works by not requesting
  password before opening the  session.
  
- 4) sudo chvt 4 ## chvt will hang here.
+ 4) Print active VT
+ $ sudo fgconsole
+ 
+ Without the fix, it will be "1". # BAD
+ With the fix, it will be "2". # GOOD
+ 
+ 5) sudo chvt 4 ## chvt will hang here.
  
  Verification can be made from a 2nd terminal, run :
  $ cat /proc/$(pidof chvt)/stack
  [<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
  [<0>] vt_waitactive+0x80/0xd0
  [<0>] vt_ioctl+0xd26/0x1140
  [<0>] tty_ioctl+0xf6/0x8c0
  [<0>] do_vfs_ioctl+0xa8/0x630
  [<0>] SyS_ioctl+0x79/0x90
  [<0>] do_syscall_64+0x73/0x130
  [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [<0>] 0x
  
  It's basically waiting for the VT to be activated, but it never happens.
  
  [Potential regression]
  
  Low.
  
  Current gdm3 run autologin display on tty1. tty1 is really meant for the
  login screen. This commit changes autologin to not use the initial vt.
  
  If one do chvt 1, once in tty1 it will hangs again and one won't be able
  to switch it. tty1 is really the problem here, so by forcing the
  autologin to not use tty1 we improve the current behaviour where we
  can't switch VTs at all when autologin is enabled.
  
  The tty1 behaviour will still need (normal behaviour or not ???) to be
  investigated, but not mandatory required for the sake of this SRU IMHO.
  
  I suspect systemd-logind to be the reason of the tty1 behaviour:
  
  # ps
  root  1350 1  0 Mar03 ?00:00:03 /lib/systemd/systemd-logind
  
  #lsof
  systemd-l  1350   root   24u  CHR4,1  
 0t0 45 /dev/tty1
  
  But I haven't dig much in it for now.
  
  So the fix will works as long as one doesn't do run on tty1.
  
  Exactly like when autologin isn't enable.
  
  * From a machine with autologin enable:
  
  /etc/gdm3/customer.conf
  # Enabling automatic login
    AutomaticLoginEnable = true
    AutomaticLogin = user1
  
  $ sudo fgconsole
  1
  
  * From a machine with autologin disable:
  
  /etc/gdm3/customer.conf
  # Enabling automatic login
  #  AutomaticLoginEnable = true
  #  AutomaticLogin = user1
  
  $ sudo fgconsole
  2
  
  [Other information]
  
  * Upstream fix:
  https://github.com/GNOME/gdm/commit/39fb4ff6
  
  $ git describe --contains 39fb4ff6
  3.30.1~2^2~3
  
  $ rmadision gdm3
   ==> gdm3 | 3.28.3-0ubuntu18.04.4   | bionic-updates   | ...
   gdm3 | 3.30.1-1ubuntu5 | cosmic   | ...
   gdm3 | 3.30.1-1ubuntu5 | disco| ...
   gdm3 | 3.30.1-1ubuntu5.1   | cosmic-security  | ...
   gdm3 | 3.30.1-1ubuntu5.1   | cosmic-updates   | ...
   gdm3 | 3.31.4+git20190225-1ubuntu1 | disco-proposed   | ...
  
  [Original Description]
  sudo strace chvt 4
  execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
  brk(NULL) = 0x561e1843
  access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
  access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
  mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
  close(3) = 0
  access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) = 
832
  fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f5059e7b000
  mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f5059878000
  mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
  mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
  mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
  mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
  mprotect(0x561e17e87000, 4096, PROT_READ) = 0
  mprotect(0x7f5059e9, 4096, PROT_READ) = 0
  munmap(0x7f5059e7d000, 74655) = 0
  brk(NULL) = 0x561e1843
  brk(0x561e18451000) = 0x561e18451000
  openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=10281

[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled

** Description changed:

  [Impact]
  
  When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
  preventing from changing foreground virtual terminal.
  
  [Test case]
  
  1) Install Bionic/18.04LTS Desktop
  
  2) Enable AutomaticLogin
   2.1) Modify /etc/gdm3/custom.conf
  # Enabling automatic login
    AutomaticLoginEnable = true
    AutomaticLogin = 
  
  3) Reboot your system and make sure AutoLogin works by not requesting
  password before opening the  session.
  
  4) sudo chvt 4 ## chvt will hang here.
  
  Verification can be made from a 2nd terminal, run :
  $ cat /proc/$(pidof chvt)/stack
  [<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
  [<0>] vt_waitactive+0x80/0xd0
  [<0>] vt_ioctl+0xd26/0x1140
  [<0>] tty_ioctl+0xf6/0x8c0
  [<0>] do_vfs_ioctl+0xa8/0x630
  [<0>] SyS_ioctl+0x79/0x90
  [<0>] do_syscall_64+0x73/0x130
  [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [<0>] 0x
  
  It's basically waiting for the VT to be activated, but it never happens.
  
  [Potential regression]
  
  Low.
  
  Current gdm3 run autologin display on tty1. tty1 is really meant for the
  login screen. This commit changes autologin to not use the initial vt.
  
  If one do chvt 1, once in tty1 it will hangs again and one won't be able
  to switch it. tty1 is really the problem here, so by forcing the
- autologin to not use tty1 we workaround the issue.
+ autologin to not use tty1 we improve the current behaviour where we
+ can't switch VTs at all when autologin is enabled.
  
  The tty1 behaviour will still need (normal behaviour or not ???) to be
  investigated, but not mandatory required for the sake of this SRU IMHO.
  
  I suspect systemd-logind to be the reason of the tty1 behaviour:
  
  # ps
  root  1350 1  0 Mar03 ?00:00:03 /lib/systemd/systemd-logind
  
  #lsof
  systemd-l  1350   root   24u  CHR4,1  
 0t0 45 /dev/tty1
  
  But I haven't dig much in it for now.
  
- So the fix will works as long as one doesn't do "chvt 1", which is
- better than right now where autologin in gdm by default uses tty1 and
- prevent any kind of vt switch.
+ So the fix will works as long as one doesn't do run on tty1.
  
  Exactly like when autologin isn't enable.
  
  * From a machine with autologin enable:
  
  /etc/gdm3/customer.conf
  # Enabling automatic login
    AutomaticLoginEnable = true
    AutomaticLogin = user1
  
  $ sudo fgconsole
  1
  
  * From a machine with autologin disable:
  
  /etc/gdm3/customer.conf
  # Enabling automatic login
  #  AutomaticLoginEnable = true
  #  AutomaticLogin = user1
  
  $ sudo fgconsole
  2
  
  [Other information]
  
  * Upstream fix:
  https://github.com/GNOME/gdm/commit/39fb4ff6
  
  $ git describe --contains 39fb4ff6
  3.30.1~2^2~3
  
  $ rmadision gdm3
   ==> gdm3 | 3.28.3-0ubuntu18.04.4   | bionic-updates   | ...
   gdm3 | 3.30.1-1ubuntu5 | cosmic   | ...
   gdm3 | 3.30.1-1ubuntu5 | disco| ...
   gdm3 | 3.30.1-1ubuntu5.1   | cosmic-security  | ...
   gdm3 | 3.30.1-1ubuntu5.1   | cosmic-updates   | ...
   gdm3 | 3.31.4+git20190225-1ubuntu1 | disco-proposed   | ...
  
  [Original Description]
  sudo strace chvt 4
  execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
  brk(NULL) = 0x561e1843
  access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
  access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
  mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
  close(3) = 0
  access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) = 
832
  fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f5059e7b000
  mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f5059878000
  mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
  mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
  mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
  mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
  mprotect(0x561e17e87000, 4096, PROT_READ) = 0
  mprotect(0x7f5059e9, 4096, PROT_READ) = 0
  munmap(0x7f5059e7d000, 74655) = 0
  brk(NULL) = 0x561e1843
  brk(0x561e18451000) = 0x561e18451000
  openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=10281936, ...}) = 0
  mmap(NULL, 10281936, PROT_RE

[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled