[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
Seeing this same issue in 18.04 since a recent update. The dumpkeys fix appears to resolve for now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I've just experienced this problem again. The following packages were just updated (from /var/log/apt/history.log): Start-Date: 2018-07-31 09:48:46 Commandline: aptdaemon role='role-commit-packages' sender=':1.2928' Upgrade: intel-microcode:amd64 (3.20180425.1~ubuntu0.18.04.1, 3.20180425.1~ubuntu0.18.04.2), console-setup-linux:amd64 (1.178ubuntu2.2, 1.178ubuntu2.3), console-setup:amd64 (1.178ubuntu2.2, 1.178ubuntu2.3), libmysqlclient20:amd64 (5.7.22-0ubuntu18.04.1, 5.7.23-0ubuntu0.18.04.1), keyboard-configuration:amd64 (1.178ubuntu2.2, 1.178ubuntu2.3) End-Date: 2018-07-31 09:49:23 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
Extended the workaround to read dumpkeys |grep -v cr_Console | grep -v -E '^\s+alt\s+keycode.*Console_' |loadkeys -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I have this bug on 18.04 with alt+left. After executing the dumpkeys/loadkeys workaround, then alt+left stops doing strange things but now, alt+F4 drops me to console 4 which is even worse. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
+1 - any workaround? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
+1 for the dumpkeys/loadkeys workaround. Saves me from killing the current session; so thanks for that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I hadn't seen this for a while and it happened again today. The dumpkeys/loadkeys workaround fixed it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
Same here. I am experiencing the issue in 18.04 (alt+arrow keys) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I can also confirm this bug is still very much present (and an annoying feature) in 18.04, under Xorg. Ctrl+C works as expected though. Alt+[Arrow keys] switches VTs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
Bug 1767918 indicates this bug is not fixed, and still occurring in 18.04. ** Tags added: fall-through -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I'm experiencing the same thing on Ubuntu Xenial. I initially thought it was only on using Alt+left/right, but did a Alt+F4 to close a window just now, and the window did close but it switched to VT4 as well. I think it started happening today on my system. Linux 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I'm experiencing this problem since months, the only "one time" fix when it occurs I found is : sudo sh -c 'dumpkeys |grep -v cr_Console |loadkeys' Until the next reboot... But it's better than nothing, right? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
Ok, I'm opening the tasks for Xenial and Trusty, and we can decide exactly where it makes sense to do the SRU for these changes. Plus, I understand maybe it was still reproducible in some form on bionic, so it this should be revisited in general. ** Also affects: console-setup (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
Would be great to get this fixed in 16.04 also guys -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
can this be fixed also for 16.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
It continues... bug 1726608 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
The forum thread is enough IMO for this improvement (as opposed to bug fix) and it is in trello. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
On Tue, Sep 19, 2017 at 04:16:24PM -, Jamie Strandboge wrote: > Closing the snappy task-- while we might want to adjust its use of > udevadm trigger, it is clear that running this command should not break > the wayland desktop, just like it doesn't under X. I think this should still be tracked - is the forum thread enough? If not, would you mind opening another bug? -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
@Mathieu, while I understand the wayland gnome-shell desktop session is not supported on zesty or xenial, I wonder if this should be SRU'd to those releases? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
Closing the snappy task-- while we might want to adjust its use of udevadm trigger, it is clear that running this command should not break the wayland desktop, just like it doesn't under X. ** Changed in: snappy Status: New => Opinion ** Changed in: snappy Status: Opinion => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I just now upgraded to 1.166ubuntu5 and no longer see the issue. To ogra's point, I use encrypted lvm and was able to enter a password and have everything work like normal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I still have console-setup 1.166ubuntu4 so decided to poke at this more. I can confirm that 'sudo udevadm trigger' causes the ctrl+c to logout of Wayland. It does not cause a logout of gnome-shell under X. I then found that 'udevadm trigger --subsystem-nomatch=tty' does not cause the issue under wayland. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
please note that this rule will also likely be used inside the initrd to set up the console for encyption key input and there will be no systemd around ... you probably want to rather handle it conditionally so it is still available when creating an initrd ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
This bug was fixed in the package console-setup - 1.166ubuntu5 --- console-setup (1.166ubuntu5) artful; urgency=medium * Don't use console-setup-tty or its udev rule. This dates back to lucid and now systemd is apparently able to handle this correctly. It's now actively breaking graphical sessions. (LP: #1710637) -- Mathieu Trudel-Lapierre Mon, 18 Sep 2017 16:36:50 -0400 ** Changed in: console-setup (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
Indeed, it looks like systemd is handling this properly by itself. I'll do some more testing but it looks like removing that is probably the best thing to do. At least font/keymaps are set properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Triaged Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
might be that we need it on Ubuntu Core (and server) though ... so installing the rule at all should probably be conditional ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Triaged Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
Not sure why you would if systemd is setting the mode up correctly on its own? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Triaged Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
^- forgot to say, that was with those udev rules commented out - you could equally (upstreamable - this bug should apply to Debian too) do something like if [ -d /run/systemd/system ]; then exit 0 fi at the top of console-setup-tty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Triaged Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
...or stop using this rule completely? I think systemd does thing properly these days - see: laney@artful-vm-gdm:~$ sudo ~/temp/a.out # displaying gdm [sudo] password for laney: K_OFF laney@artful-vm-gdm:~$ sudo ~/temp/a.out # switch to vt3, login: prompt K_UNICODE ...which looks set up correctly to me. @Janne - I don't know why this would be specific to Wayland. I think it'd happen if you were running your graphical environment on /dev/tty[1-6] regardless of the Xness or Waylandness of it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Triaged Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I have this problem on Ubuntu Gnome 17.04 running in virtualbox. I believe it is not using Wayland. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Triaged Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
Indeed changing it to [3-7] fixes it. Or should that be [3-6]? cyphermox? ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Invalid ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid ** Changed in: mutter (Ubuntu) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: console-setup (Ubuntu) Status: Fix Released => Triaged ** Changed in: console-setup (Ubuntu) Importance: Undecided => High ** Changed in: console-setup (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Triaged Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
/lib/udev/rules.d/85-keyboard-configuration.rules:SUBSYSTEM=="tty", KERNEL=="tty[1-6]", RUN+="console-setup-tty /dev/%k" /lib/udev/rules.d/85-keyboard-configuration.rules:SUBSYSTEM=="graphics", KERNEL=="fbcon", RUN+="console-setup-tty fbcon" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Triaged Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
^- this thing is the thing that breaks it -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Triaged Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
** Summary changed: - Input falls through to gdm3 and terminates the session on Ctrl+C + Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
