This bug doesn't belong here.
I found out, that this is most probably a problem with the switching
mechanism between intel and nvidia drivers, which doesn't seem to do its
job fully under certain conditions. What was causing gnome-shell to do
what it was doing was actually some strange bug that
One more piece of information from the syslog:
dec 05 21:22:03 mobileaeris kernel: CPU0: Core temperature above threshold, cpu
clock throttled (total events = 1)
dec 05 21:22:03 mobileaeris kernel: CPU2: Core temperature above threshold, cpu
clock throttled (total events = 1)
dec 05 21:22:03
Public bug reported:
There's not much I can provide in terms of hard data, but maybe someone
can help with getting to the bottom of this. After installing Ubuntu
18.10, I'm unable to use graphics-intensive games.
My setup:
ASUS F556U, with Intel® Core™ i7-7500U CPU @ 2.70GHz × 4, Intel® HD
This bug seems not to be related to GDM at all. This is a problem either
with automount, or mount.nfs4.
I did spend some time today digging around this and found out that the
hang lasts for several minutes, but then the system springs back to life
and the user list in the greeter will get
Public bug reported:
In Ubuntu 17.10 with GDM 3.26.1-3ubuntu3, the greeter will hang, if
local /home directory is not accessible.
Our setup:
- Ubuntu Server (16.04) with DNS, LDAP, Kerberos 5 and NFS servers. The home
directories are present on the server and made available via NFS with krb5
