[Bug 1753576] Re: GDM freeze

2018-05-05 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1753576] Re: GDM freeze

2018-05-05 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753576

[Bug 1753576] Re: GDM freeze

2018-05-05 Thread Launchpad Bug Tracker
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753576

[Bug 1753576] Re: GDM freeze

2018-03-06 Thread Daniel van Vugt
Wayland is not a program, so "Wayland" can't crash. Wayland is only a protocol for talking to apps that is supported by the Gnome Shell 'eglnative' backend inside the 'mutter' project. This issue is further confused by the incorrect wording "Ubuntu on Wayland" on the login screen. Actually it's

Re: [Bug 1753576] Re: GDM freeze

2018-03-06 Thread Nish Aravamudan
Hi Daniel, On Mon, Mar 5, 2018 at 9:56 PM, Daniel van Vugt wrote: > Nish, > > To figure the problem out you will need to be logged in already while > it's happening(!), so.. Yeah, tricky when the machine physically seems to be hung (no touchpad, no responsiveness

[Bug 1753576] Re: GDM freeze

2018-03-06 Thread Nish Aravamudan
I edited /etc/gdm3/custom.conf and put WaylandEnable=false back in (I had it enabled before to test). Greeter came right up on reboot and my external monitor works again. What is curious is that my session choice in both cases was/is Gnome on Xorg. So is it possible there's some change in the

[Bug 1753576] Re: GDM freeze

2018-03-05 Thread Daniel van Vugt
dino99, Given the large number of bugs we're dealing with it would be safer for you to log your own bug. Often two people with similar symptoms turn out to have different bugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1753576] Re: GDM freeze

2018-03-05 Thread Daniel van Vugt
Nish, To figure the problem out you will need to be logged in already while it's happening(!), so.. 1. Log into a VT (Ctrl+Alt+F4) or install openssh-server and log in from a separate machine. 2. Run 'top' to find the ID of the spinning process. 3. Run: kill -ABRT 4. Wait a while for crash

[Bug 1753576] Re: GDM freeze

2018-03-05 Thread Nish Aravamudan
But if I plug in my usb-c dongle, it immediately freezes and the fans start to spin. Unplugging the dongle has no effect. Suggestions for debugging? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1753576] Re: GDM freeze

2018-03-05 Thread Nish Aravamudan
I just rebooted again and without hitting any keys, it did come up to the greeter without issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753576 Title: GDM freeze To manage notifications

[Bug 1753576] Re: GDM freeze

2018-03-05 Thread dino99
Also now get a 'smooth' freeze (kind of race, as the hdd is heavily used before getting the login screen. But booting with 'plymooth:debug' kernel option, journalctl has logged: *** Mar 06 04:19:47 ubuntu plymouth[660]: [./ply-boot-client.c:183]

[Bug 1753576] Re: GDM freeze

2018-03-05 Thread Nish Aravamudan
Hrm, I'm not entirely sure what just changed. I rebooted and unlike before, I hit Escape at the splash screen, and the GDM greeter showed up just fine (after hitting Escape again to go back to graphics mode). I'll see if that's reproducible shortly. -- You received this bug notification because

[Bug 1753576] Re: GDM freeze

2018-03-05 Thread Nish Aravamudan
@vanvugt: no, as it's not crashed (afaict), it's just 100% cpu (based upon fans). Numlock is still responsive as is sysrq, but i can't get to any ttys (that is, ctrl+alt+f2, etc don't seem to work). I even tried booting with 'text' and annoyingly gdm still started (I might be misremembering how

[Bug 1753576] Re: GDM freeze

2018-03-05 Thread Nish Aravamudan
Oh also the splash screen correctly displays on both monitors, so i think it must be in X that the multiple displays fail. I'll see if I can figure out how to get to a temrinal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1753576] Re: GDM freeze

2018-03-05 Thread Daniel van Vugt
Can you find any crash files in /var/crash ? If so then please run: ubuntu-bug /var/crash/YOURFILE.crash and tell us the new bug ID. ** Summary changed: - Xorg freeze + GDM freeze ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu)