GNOME.org
 

Re: [gdm-list] gdm-list Digest, Vol 117, Issue 1

gdm-list-request gnome org wrote:

Send gdm-list mailing list submissions to
        gdm-list gnome org

To subscribe or unsubscribe via the World Wide Web, visit
        https://mail.gnome.org/mailman/listinfo/gdm-list
or, via email, send a message with subject or body 'help' to
        gdm-list-request gnome org

You can reach the person managing the list at
        gdm-list-owner gnome org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of gdm-list digest..."


Today's Topics:

   1.  Since update from Gnome 3.18 to 3.20 gdm X server terminates
      after a while (Manuel Reimer)
   2. Re:  Since update from Gnome 3.18 to 3.20 gdm X server
      terminates after a while (Manuel Reimer)


----------------------------------------------------------------------

Message: 1
Date: Sun, 10 Apr 2016 17:12:38 +0200
From: Manuel Reimer <Manuel Spam nurfuerspam de>
To: gdm-list gnome org
Subject: [gdm-list] Since update from Gnome 3.18 to 3.20 gdm X server
        terminates after a while
Message-ID: <nedqh7$h7f$1 ger gmane org>
Content-Type: text/plain; charset=utf-8; format=flowed

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



------------------------------

Message: 2
Date: Sun, 10 Apr 2016 17:46:33 +0200
From: Manuel Reimer <Manuel Spam nurfuerspam de>
To: gdm-list gnome org
Subject: Re: [gdm-list] Since update from Gnome 3.18 to 3.20 gdm X
        server terminates after a while
Message-ID: <nedsgp$fdl$1 ger gmane org>
Content-Type: text/plain; charset=windows-1252; format=flowed

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



------------------------------

Subject: Digest Footer

_______________________________________________
gdm-list mailing list
gdm-list gnome org
https://mail.gnome.org/mailman/listinfo/gdm-list


------------------------------

End of gdm-list Digest, Vol 117, Issue 1
****************************************



your single nvidia card likely has nothing to do with starting two X servers

you first find out why two X servers start, it is not normal.
(it could be one starts to display a on your local video card, another starts to display X runnig on a a remote server (the virtual one that shuts down). X is internet transparent; it can open programs or whole desktops on a desktop, or log into a remote desktop, across the internet seemlessly and all by a simple command (without special configuration).
so the two may be trying to start on one video card. or maybe the 2nd is virtual (see: Xnest(1)). or one is started as root the other as user (shouldn't).
the "Gnome Display Manager" has settings to log into multile X servers (one real, others virtual on a single video card single monitor situation). SO the 1st thing is examine your GDM options and insure it appears only "one window (screen), one server (display), one user (login)" will be started by GDM by default.
could be the ("linux" (distribution)) is not working properly and starts two X (or two gdm) instead of one (in which case, a race may be involved where one place starts X or GDM if not already started, exactly at the same time another is starting and the other does not know)
in any case. the way to fix it is to read files in /etc/gdm /etc/X11/gdm or even the source code of the programs if need be to see "who is starting X" and why it is done twice. It's not nvidia related.
You should ask questions such as "where do i start looking to see what starts X in my linux distro" in chat forums run under your linux distribution, or www.linuxquestions.org is a fine place to ask as well.
You should also be aware that if you used "KDE, XFCE" or something other than gnome the problem may or may not occur: so when you ask people you may want to be sure they use the same linux distro and also a typical gnome setup. 

---------------------
here's TWO places you CAN check:
your linux distro starts programs from /etc/inittab or (for systemd, see it's manpage where)
it has "run levels" adn the default is "2" or maybe "4" dependign on distro. runlevel 1 is text only single user, either 2 or 4 will start X.
ie, for inittab there is /etc/rc2.d/ if yo saw "S?gdm?" (s is for start) in that directory, if it appeared TWICE anywhere, then aha! there should only be ONE S?gdm? in your startup in all of the runlevel directories. for systemd the configuration is similar but different.
(a remote possibility is your system goes into out of and back into a runleve due to breakage - you'd really have to re-install your system from scratch by backing up your files and installing your linux distro onto a clean disk, if you dont know how to find such things yourself. when you gain experience you can do most repairs or changes in Unix without even rebooting or exiting X. of course, unix today is a good platform for development, as an end user an off-the-shelf tablet would save money and time if one is looking for such features) 

good luck, have fun!
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]