gnome leaves all of a sudden

Here is the scenario : Since I updated to 10.4 LTS, my gnome session all of a sudden finishes : it turns off. This does not take place every single time, yet instead arbitrarily. I've attempted to compel this occasion, believing it was some sort of unfavorable key - mapping point : alt - enter, change - enter, enter - end, etc But no, I angle duplicate it.

Does this take place to any person? I've googled about, yet have not located any kind of remedy.

Update : Here is the tail end of my.xsession - mistakes submit

error 0 (Success) on X server :1.0.

error 0 (Success) on X server :1.0.> MADPlug-Message: Rejecting
> file:///media/KINGSTON/somesong.mp3:
> out of data.
> 
> ** (update-notifier:3110): DEBUG: fire up the crashreport tool
> 
> gnome-session: Fatal IO error 11
> (Resource temporarily unavailable) on
> X server :1.0.
> 
> gnome-settings-daemon: Fatal IO error
> 11 (Resource temporarily unavailable)
> on X server :1.0.
> 
> Window manager warning: Fatal IO error
> 11 (Resource temporarily unavailable)
> on display ':1.0'.
> 
> gnome-screensaver: Fatal IO error 11
> (Resource temporarily unavailable) on
> X server :1.0.
> 
> polkit-gnome-authentication-agent-1:
> Fatal IO error 11 (Resource
> temporarily unavailable) on X server
> :1.0.
> 
> evolution-alarm-notify: Fatal IO error
> 11 (Resource temporarily unavailable)
> on X server :1.0.
> 
> tilda: Fatal IO error 11 (Resource
> temporarily unavailable) on X server
> :1.0.
> 
> audacious2: Fatal IO error 11
> (Resource temporarily unavailable) on
> X server :1.0.
> 
> XIO:  fatal IO error 11 (Resource
> temporarily unavailable) on X server
> ":1.0"^M
> 
>       after 9917 requests (9916 known processed) with 0 events remaining.^M
> gsd-locate-pointer: Fatal IO error 11
> (Resource temporarily unavailable) on
> X server :1.0.
> 
> gnome-terminal: Fatal IO error 11
> (Resource temporarily unavailable) on
> X server :1.0.                        
> 
> 
> gdu-notification-daemon: Fatal IO
> error 11 (Resource temporarily
> unavailable) on X server :1.0.
> 
> update-notifier: Fatal IO error 11
> (Resource temporarily unavailable) on
> X server :1.0. nm-applet: Fatal IO
> error 0 (Success) on X server :1.0.error 0 (Success) on X server :1.0.

Thanks in advance.error 0 (Success) on X web server :1.0.

0
2019-05-13 04:05:39
Source Share
Answers: 1

Look in /var/crash to see if X or something collapsed. Examine dmesg for any kind of bit mistakes. Consider the last loads lines approximately of /var/log/Xorg.0.log for proof of an X crash in the kind of a backtrace. Examine your /var/log/gdm/ logs too for backtraces or mistake messages from X.

0
2019-05-17 15:21:22
Source