>
> On 6/17/19 1:03 PM, Patrick Dupre wrote:
> >> From: "Samuel Sieb" <samuel(a)sieb.net>
> >> Where are you entering this? From a console or ssh?
> > Yes
>
> That wasn't intended to be a yes or no question. I assume from the
> answer below that it's a terminal console.
>
> >> Try using "kill -HUP" on the gnome-shell process.
I tried this with what I though was the correct gnome-session, but I
finally lost the keyboard, and I
had to shutdown manually.
How to identify the right session?
I can also confirm that it happens when there is a mount (sshfs) on a
machine which does not
respond.
While I can log with a terminal, and I umount the partition, I still
cannot recover a
gnome-session.
I have seen this happen before. If you have nvidia-settings installed, but
do not have the commercial nvidia driver running, nvidia-settings makes a
whole bunch of duplicate connections to the xserver. Once it is full, you
cannot open new windows. (Things get very strange.)
I cannot say for certain that this is the case here. Just see if you have
that combination installed and running and not running.
perl -pe 's/^\s+//g' *.py