Re: [gdm-list] Since update from Gnome 3.18 to 3.20 gdm X server terminates after a while

[Manuel Reimer <Manuel Spam nurfuerspam de>]

On 04/10/2016 05:12 PM, Manuel Reimer wrote:
> Hello,
>
> yesterday, I got the updated from Gnome 3.18 to 3.20 (Arch Linux).
>
> Since I got this update, I have the following issue:
>
> As soon as I've logged in, there are usually two X servers (one on VT1
> which still shows the login screen and one on VT2 where my desktop
> session runs).
>
> Since update to Gnome 3.20, the first X server terminates after some time:
>
> [    92.389] (II) systemd-logind: got resume for 13:64
> [    92.389] (II) systemd-logind: got resume for 13:67
> [    92.389] (II) systemd-logind: got resume for 13:65
> [    92.389] (II) systemd-logind: got resume for 13:66
> [    95.021] (II) systemd-logind: got pause for 226:0
> [    95.021] (II) systemd-logind: got pause for 13:64
> [    95.021] (II) systemd-logind: got pause for 13:67
> [    95.021] (II) systemd-logind: got pause for 13:65
> [    95.021] (II) systemd-logind: got pause for 13:66
> [   405.532] (II) evdev: Sun USB Keyboard: Close
> [   405.532] (II) UnloadModule: "evdev"
> [   405.532] (II) systemd-logind: releasing fd for 13:65
> [   405.546] (II) evdev: USB Mouse: Close
> [   405.546] (II) UnloadModule: "evdev"
> [   405.546] (II) systemd-logind: releasing fd for 13:64
> [   405.567] (II) evdev: Power Button: Close
> [   405.567] (II) UnloadModule: "evdev"
> [   405.567] (II) systemd-logind: releasing fd for 13:66
> [   405.593] (II) evdev: Power Button: Close
> [   405.593] (II) UnloadModule: "evdev"
> [   405.593] (II) systemd-logind: releasing fd for 13:67
> [   405.634] (II) NVIDIA(GPU-0): Deleting GPU-0
> [   405.857] (II) Server terminated successfully (0). Closing log file.
>
> This wouldn't be a big problem, if this wouldn't cause a VT switch back
> to VT1.
>
> I'm using the closed source Nvidia driver and unfortunately, I can
> reproduce this every time on every login. My only solution, to have a
> system running stable right away, is to switch VT to a text terminal,
> login as root, do "pgrep X" and kill the lower PID number found by this
> to kill this "login X server" right away, so it doesn't throw me out of
> something when it terminates "automatically".
>
> Can someone please point me to any solution for this?
>
> - Is it possible to configure gdm in a way it does not keep an X server
> open?
> - Is it possible to prevent the VT switch when the X server terminates?
> - Is there anything, I could do to provide information, so this problem
> can be fixed?
>
> Thanks in advance
>
> Manuel
>
> _______________________________________________
> gdm-list mailing list
> gdm-list gnome org
> https://mail.gnome.org/mailman/listinfo/gdm-list


I did another try to find more information.

In dmesg, I see the following if gdm "terminates":

[ 1974.007469] traps: gnome-shell[2056] trap int3 ip:7f996b0eb7eb 
sp:7ffe637d3e50 error:0

I've enabled "debug" in /etc/gdm/custom.conf which seems to have logged 
something to journal:
http://m-reimer.de/tmp/gdm-crash-bug/journal

The coredump, mentioned there, is here:
http://m-reimer.de/tmp/gdm-crash-bug/coredump

So the reason for the whole problem actually seems to be a crash...?

Manuel