Public bug reported:

If I restart gdm from a VT the screen starts flashing and becoming
unresponsive. If I press CTRL+C to end the process it stops flashing and
I'm again able to use the VT, but I can't start gdm again. The only
solution to have gdm back when this happens is to reboot and let gdm
start on its own.

Expected: gdm to restart and be prompted for login, or, if it fails, to
be prompted an error stating the failure reason on the VT

What happens: screen flashing like if it was continuously switching
between VTs (possibly gdm falls in an endless loop trying to start)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gdm3 3.18.3-0ubuntu2.1
ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jun 30 11:38:50 2017
InstallationDate: Installed on 2016-09-09 (293 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  cannot succesfully restart gdm (screen flashing)

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

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

Reply via email to