[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
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
(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
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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
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
# 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
** 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
** 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
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 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
** 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
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
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
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
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=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] 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=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 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri
[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] 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. 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=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 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri
[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=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
[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
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
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
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
** 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
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
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 1817738] Re: Can't change virtual terminal on login screen or when auto-login is enabled
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
@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?
** 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,
[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,
[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 =
- 2.2) autologin run on tty1
- $ sudo fgconsole
- 1
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.
- A system which runs on tty1 is not able to switch VT. This may or may not be
a kernel issue or else. The tty1 will require some investigation, to see if
it's a normal behaviour or not ... but can be treated as a separate bug.
[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.
- But if one do chvt 1, once the system runs on 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.
+ 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.
The tty1 behaviour will still need (normal behaviour or not ???) to be
- investigated, but not mandatory required for the sake of this SRU IMHO
- and can be treated as a separate bug.
+ 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.
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
[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 =
+ 2.2) autologin run on tty1
+ $ sudo fgconsole
+ 1
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.
+ A system which runs on tty1 is not able to switch VT. This may or may not be
a kernel issue or else. The tty1 will require some investigation, but as a
separate bug.
[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.
But if one do chvt 1, once the system runs on 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.
The tty1 behaviour will still need (normal behaviour or not ???) to be
- investigated, but not mandatory required for the sake of this SRU IMHO.
+ investigated, but not mandatory required for the sake of this SRU IMHO
+ and can be treated as a separate bug.
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.
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_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400
[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.
+ But if one do chvt 1, once the system runs on 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.
The tty1 behaviour will still need (normal behaviour or not ???) to be
investigated, but not mandatory required for the sake of this SRU IMHO.
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.
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_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD,
[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.
+ 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.
+
+ The tty1 behaviour will still need IMHO to be investigated, but not
+ required for the sake of this SRU IMHO.
+
+ So the fix will works as long as one doesn't do "chvt 1", which is
+ better than right now where gmd autologin by default uses tty1 and
+ prevent any kind of vt switch.
Exactly like when autologin isn't enable.
- From a machine with autologin disable:
+ * 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_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig
[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.
- 5) From a 2nd terminal, run :
- 5.1) cat /proc/$(pidof chvt)/stack
-
+ 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.
Exactly like when autologin isn't enable.
From a machine with autologin disable:
/etc/gdm3/customer.conf
# Enabling automatic login
# AutomaticLoginEnable = true
# AutomaticLogin = user1
- $ sudo fgconsole
+ $ 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_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
ioctl(3, VT_ACTIVATE, 0x4) = 0
ioctl(3, VT_WAITACTIVE, 0x4
VT_ACTIVATE will cause a switch to VT number.
VT_WAITACTIVE will sleep/wait until the specified VT has been activated.
$ sudo 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
[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.
5) From a 2nd terminal, run :
5.1) 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.
[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_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
ioctl(3, VT_ACTIVATE, 0x4) = 0
ioctl(3, VT_WAITACTIVE, 0x4
VT_ACTIVATE will cause a switch to VT number.
VT_WAITACTIVE will sleep/wait until the specified VT has been activated.
$ sudo 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
Enable debuglogs doesn't provide additional details.
As soon as auto-login is turned off, chvt is back to normal.
The above has been reproduced on Ubuntu:
- Ubuntu Bionic w/ gdm3 3.28.3 & kbd 2.0.4
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command
[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
+ 2.1) Modify /etc/gdm3/custom.conf
# Enabling automatic login
- AutomaticLoginEnable = true
- AutomaticLogin =
+ AutomaticLoginEnable = true
+ AutomaticLogin =
- 3) Restart gdm or reboot
+ 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.
5) From a 2nd terminal, run :
- 5.1) cat /proc/$(pidof chvt)/stack
+ 5.1) 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]
[Other information]
[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_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
ioctl(3, VT_ACTIVATE, 0x4) = 0
ioctl(3, VT_WAITACTIVE, 0x4
VT_ACTIVATE will cause a switch to VT number.
VT_WAITACTIVE will sleep/wait until the specified VT has been activated.
$ sudo 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
Enable debuglogs doesn't provide additional details.
As soon as auto-login is turned off, chvt is back to normal.
The above has been reproduced on Ubuntu:
- Ubuntu Bionic w/ gdm3 3.28.3 & kbd 2.0.4
- Ubuntu disco w/ gdm3 3.30.1 & kbd 2.0.4
** 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.
5) From a 2nd terminal, run :
5.1) cat /proc/$(pidof chvt)/stack
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
I was able to reproduce the bug, and this upstream fix[1] look promising. On my test machine, using a test package containing this patch on top of current gdm3 bionic, chvt doesn't hang anymore, and work as expected. I'd would like more feedback before I proceed with an SRU. [1] - 39fb4ff6 manager: don't run autologin display on tty1 - 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/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
** 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) Restart gdm or reboot
+
+ 4) sudo chvt 4 ## chvt will hang here.
+
+ 5) From a 2nd terminal, run :
+ 5.1) 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]
+
+ [Other information]
+
+ [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_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
ioctl(3, VT_ACTIVATE, 0x4) = 0
ioctl(3, VT_WAITACTIVE, 0x4
VT_ACTIVATE will cause a switch to VT number.
VT_WAITACTIVE will sleep/wait until the specified VT has been activated.
$ sudo 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
Enable debuglogs doesn't provide additional details.
As soon as auto-login is turned off, chvt is back to normal.
The above has been reproduced on Ubuntu:
- Ubuntu Bionic w/ gdm3 3.28.3 & kbd 2.0.4
- Ubuntu disco w/ gdm3 3.30.1 & kbd 2.0.4
--
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
** Changed in: gdm3 (Ubuntu Bionic) Status: New => In Progress ** Changed in: gdm3 (Ubuntu Bionic) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: gdm3 (Ubuntu Bionic) Importance: Undecided => 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/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
** 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 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
$ cat /proc/5222/stack
[<0>] __vt_event_wait.isra.3.part.4+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd34/0x1150
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] ksys_ioctl+0x75/0x80
[<0>] __x64_sys_ioctl+0x1a/0x20
[<0>] do_syscall_64+0x5a/0x120
[<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[<0>] 0x
# drivers/tty/vt/vt_ioctl.c
/**
* vt_waitactive - active console wait
* @event: event code
* @n: new console
*
* Helper for event waits. Used to implement the legacy
* event waiting ioctls in terms of events
*/
int vt_waitactive(int n)
{
struct vt_event_wait vw;
do {
vw.event.event = VT_EVENT_SWITCH;
__vt_event_queue();
if (n == fg_console + 1) {
__vt_event_dequeue();
break;
}
__vt_event_wait();
__vt_event_dequeue();
if (vw.done == 0)
return -EINTR;
} while (vw.event.newev != n);
return 0;
}
# drivers/tty/vt/vt_ioctl.c
static void __vt_event_wait(struct vt_event_wait *vw)
{
/* Wait for it to pass */
wait_event_interruptible(vt_event_waitqueue, vw->done);
}
# include/linux/wait.h
/**
* wait_event_interruptible - sleep until a condition gets true
* @wq_head: the waitqueue to wait on
* @condition: a C expression for the event to wait for
*
* The process is put to sleep (TASK_INTERRUPTIBLE) until the
* @condition evaluates to true or a signal is received.
* The @condition is checked each time the waitqueue @wq_head is woken up.
*
* wake_up() has to be called after changing any variable that could
* change the result of the wait condition.
*
* The function will return -ERESTARTSYS if it was interrupted by a
* signal and 0 if @condition evaluated to true.
--
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
# gdb attach (gdb) bt F #0 0x7fd01e9c65d7 in ioctl () at ../sysdeps/unix/syscall-template.S:78 No locals. #1 0x55fbea90bce1 in main (argc=2, argv=) at chvt.c:45 fd = 3 num = -- 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
https://gitlab.gnome.org/GNOME/gdm/issues/466
** Description changed:
- 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_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
- close(3) = 0
- openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
- ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
- ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
- close(3) = 0
- openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
- ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
- ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
- close(3) = 0
- openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
- ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
- ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
- ioctl(3, VT_ACTIVATE, 0x4) = 0
- ioctl(3, VT_WAITACTIVE, 0x4
-
+ 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_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
+ close(3) = 0
+ openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
+ ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
+ ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
+ close(3) = 0
+ openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
+ ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
+ ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
+ close(3) = 0
+ openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
+ ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
+ ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
+ ioctl(3, VT_ACTIVATE, 0x4) = 0
+ ioctl(3, VT_WAITACTIVE, 0x4
VT_ACTIVATE will cause a switch to VT
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
** Tags added: rls-bb-incoming -- 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] [NEW] Can't change virtual terminal when auto-login is enabled
Public bug reported:
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_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
ioctl(3, VT_ACTIVATE, 0x4) = 0
ioctl(3, VT_WAITACTIVE, 0x4
VT_ACTIVATE will cause a switch to VT number.
VT_WAITACTIVE will sleep/wait until the specified VT has been activated.
$ sudo 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
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Affects: gdm3 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Tags: sts
** Tags added: sts
** Also affects: gdm3 (Ubuntu Bionic)
Importance: Undecided
Status: New
--
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 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
** Changed in: gdm3 (Ubuntu Xenial) Status: New => In Progress ** Changed in: gdm3 (Ubuntu Xenial) Importance: Undecided => 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/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
** Changed in: gdm3 (Ubuntu Bionic) Status: New => In Progress ** Changed in: gdm3 (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: gdm3 (Ubuntu Bionic) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) -- 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/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
Hi Dariusz, Before I sponsor the patch in Ubuntu, did you submitted (or at least forwarded) the patch to gdm3 debian ? I couldn't find a debian bug about it. If one exist great, but if none, could you please file one against gdm3 (debian). This will prevent gdm Ubuntu package to re-introduce the same problem in later future release sync (Debian->Ubuntu). Once done, I'll gladly sponsor in Cosmic. - 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/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
** Also affects: gdm3 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Cosmic) Importance: Medium Assignee: Dariusz Gadomski (dgadomski) Status: In Progress ** Also affects: gdm3 (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
It has been brought to my attention by a community user, that the workaround (change scale from 200% to 100%) found in comment#14 works. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1751252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
I set both back to 'Confirmed'. ** Changed in: casper (Ubuntu) Status: Fix Released => Confirmed ** Changed in: systemd (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766872] Re: 'Enable Network' in recovery mode not working in Bionic
So all the remaining jobs are basically waiting for friendly-recovery to exit to start due to the "oneshot" instruction, which make xnox patch (revno 152) not working. Some waiting jobs are units in which the desired network services in revno 152 depends on. I totally understand why "oneshot" is set, but in this case it is the blocker. If we remove "oneshot" then everything will start and make the recovery mode useless. So I think "oneshot" need to stay there. The only thing then I can think of atm is to add --job-mode=ignore- dependencies --no-ask-password and possibly extra stuff in frienly- recovery.service to make the necessary network services to start in recovery mode when requesting 'Enable Network'. ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766872 Title: 'Enable Network' in recovery mode not working in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766872] [NEW] 'Enable Network' in recovery mode not working in Bionic
Public bug reported: This bug has been introduced by the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery- mode menu. ** Affects: friendly-recovery (Ubuntu) Importance: High Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: sts ** Changed in: friendly-recovery (Ubuntu) Importance: Undecided => High ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766872 Title: 'Enable Network' in recovery mode not working in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1316970] Re: g_dbus memory leak in lrmd
Seyeong, The SRU for LP: #1740892 is not started yet, but base on nacc's comment, It should start soon : https://bugs.launchpad.net/charm-hacluster/+bug/1740892/comments/47 I would suggest to wait for LP: #1740892 SRU to be completed first since it affects package upgrade (corosync/pacemaker relation). Additionally, IMHO, it may be "safer" to not introduce too much change in one SRU, especially considering LP: #1740892 mark as Critical. 1) Please keep monitoring LP: #1740892 and let's wait for the SRU to turn "Fix Released" for Trusty. 2) Then let's start LP: #1316970 SRU right after using either "STS-Sponsor" or "Ubuntu Sponsors Team" - Eric -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1316970 Title: g_dbus memory leak in lrmd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1316970] Re: g_dbus memory leak in lrmd
Seyeong/ddstreet, As long as this critical bug (LP: #1740892) affecting corosync/pacemaker relation is not fix, I would be reluctant to sponsor this bug for the following reasons : - To make sure it won't block potential pacemaker sru to fix this critical bug by start this one here. - To make sure to not force another package upgrade issue and impact other users until (LP: #1740892) is figure out and fix. - Eric -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1316970 Title: g_dbus memory leak in lrmd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736781] [NEW] FTBFS in bionic
Public bug reported: # gnome-disk-utility3.26.2-0ubuntu1 (Proposed) Bionic gnome-disk-utility is expecting a Build-Depends version for libudisks2-dev higher than what Ubuntu currently has in the archive. #amd64/buildlog https://launchpadlibrarian.net/348142968/buildlog_ubuntu-bionic-amd64.gnome-disk-utility_3.26.2-0ubuntu1_BUILDING.txt.gz .. +--+ | Install gnome-disk-utility build dependencies (apt-based resolver) | +--+ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-gnome-disk-utility-dummy : Depends: libudisks2-dev (>= 2.7.2) but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. Package installation failed .. - $ rmadison libudisks2-dev -u ubuntu libudisks2-dev | 2.1.3-1 | trusty | amd64, arm64, armhf, i386, powerpc, ppc64el libudisks2-dev | 2.1.3-1ubuntu0.1 | trusty-updates | amd64, arm64, armhf, i386, powerpc, ppc64el libudisks2-dev | 2.1.7-1ubuntu1 | xenial | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x libudisks2-dev | 2.1.8-1ubuntu1 | zesty | amd64, arm64, armhf, i386, ppc64el, s390x libudisks2-dev | 2.6.5-2ubuntu2 | artful | amd64, arm64, armhf, i386, ppc64el, s390x libudisks2-dev | 2.6.5-2ubuntu2 | bionic | amd64, arm64, armhf, i386, ppc64el, s390x - $ rmadison libudisks2-dev -u debian libudisks2-dev | 2.1.3-5 | oldstable | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x libudisks2-dev | 2.1.8-1 | stable | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x libudisks2-dev | 2.7.4-1 | testing| amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x libudisks2-dev | 2.7.4-1 | unstable | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x - d/control -- Build-Depends: appstream-util, debhelper (>= 10.3~), dh-translations, docbook-xsl, libcanberra-gtk3-dev (>= 0.1), libdvdread-dev (>= 4.2.0), libglib2.0-dev (>= 2.31.0), libgtk-3-dev (>= 3.16.0), liblzma-dev (>= 5.0.5), libnotify-dev (>= 0.7), libpwquality-dev (>= 1.0.0), libsecret-1-dev (>= 0.7), libsystemd-dev (>= 209), ==> libudisks2-dev (>= 2.7.2), ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Description changed: # gnome-disk-utility3.26.2-0ubuntu1 (Proposed) Bionic gnome-disk-utility is expecting a Build-Depends version for - libudisks2-dev higher than what Ubuntu current has in the archive. + libudisks2-dev higher than what Ubuntu currently has in the archive. #amd64/buildlog https://launchpadlibrarian.net/348142968/buildlog_ubuntu-bionic-amd64.gnome-disk-utility_3.26.2-0ubuntu1_BUILDING.txt.gz .. +--+ | Install gnome-disk-utility build dependencies (apt-based resolver) | +--+ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: - sbuild-build-depends-gnome-disk-utility-dummy : Depends: libudisks2-dev (>= 2.7.2) but it is not going to be installed + sbuild-build-depends-gnome-disk-utility-dummy : Depends: libudisks2-dev (>= 2.7.2) but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. Package installation failed .. - $ rmadison libudisks2-dev -u ubuntu - libudisks2-dev | 2.1.3-1 | trusty | amd64, arm64, armhf, i386, powerpc, ppc64el - libudisks2-dev | 2.1.3-1ubuntu0.1 | trusty-updates | amd64,
[Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition
** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1718966 Title: Cannot install snaps on Ubuntu 14.04 with /var on its own partition To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1718966/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714505] Re: systemd kmod builtin uses out of date kmod context
** Also affects: systemd (Ubuntu Artful) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1714505 Title: systemd kmod builtin uses out of date kmod context To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1714505/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
** Also affects: open-iscsi (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Artful) Importance: High Assignee: Nish Aravamudan (nacc) Status: Confirmed ** Also affects: open-iscsi (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569925/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
