# Session terminates immediately on RHEL 8.9

**URL:** <https://community.thinlinc.com/t/session-terminates-immediately-on-rhel-8-9/879>\
**Category:** Community Support\
**Tags:** tlserver\
**Created:** [6 March 2024 15:11 UTC](https://community.thinlinc.com/t/session-terminates-immediately-on-rhel-8-9/879 "2024-03-06T15:11:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dietmar13](https://avatars.discourse-cdn.com/v4/letter/d/5f8ce5/32.png) [@Dietmar13](https://community.thinlinc.com/u/Dietmar13)\
**Post date:** [6 March 2024 15:11 UTC](https://community.thinlinc.com/t/session-terminates-immediately-on-rhel-8-9/879/1 "2024-03-06T15:11:19Z")

</div>

Hello,  
I installed the ThinLinc server 4.16.0 on a RHEL 8.9 and all three services are running.  
But if I want to login from a remote computer (with client 4.16.0) the Session stops immediately after the selection of the Gnome type.  
What could be wrong?

Thank you in advance.

The xinit.log:

```auto
xauth: file /var/opt/thinlinc/sessions/sm/10/Xauthority does not exist
tl-xinit: Waiting for Xserver to accept connections...

Xvnc ThinLinc release 4.16.0 build 3491 - built Jan 24 2024 09:48:01
Copyright (C) 1999-2024 TigerVNC Team and many others (see README.rst)
See https://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12013000

(II) Initializing extension VNC-EXTENSION

Wed Mar 6 13:38:30 2024
 vncext: VNC extension running!
 vncext: Listening for VNC connections on local interface(s), port 5910
 vncext: created VNC server for screen 0
(II) Initializing extension Generic Event Extension
(II) Initializing extension SHAPE
(II) Initializing extension MIT-SHM
(II) Initializing extension XInputExtension
(II) Initializing extension XTEST
(II) Initializing extension BIG-REQUESTS
(II) Initializing extension SYNC
(II) Initializing extension XKEYBOARD
(II) Initializing extension XC-MISC
(II) Initializing extension XFIXES
(II) Initializing extension RENDER
(II) Initializing extension RANDR
(II) Initializing extension COMPOSITE
(II) Initializing extension DAMAGE
(II) Initializing extension MIT-SCREEN-SAVER
(II) Initializing extension DOUBLE-BUFFER
(II) Initializing extension RECORD
(II) Initializing extension DPMS
(II) Initializing extension Present
(II) Initializing extension DRI3
(II) Initializing extension X-Resource
(II) Initializing extension XVideo
(II) Initializing extension XVideo-MotionCompensation
(II) Initializing extension GLX
(II) IGLX: Loaded and initialized swrast
(II) GLX: Initialized DRISWRAST GL provider for screen 0
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported high keycode 372 for name <I372> ignored
> X11 cannot support keycodes above 255.
> This warning only shows for the first high keycode.
Errors from xkbcomp are not fatal to the X server
 Connections: accepted: 127.0.0.1::39340
 VNCSConnST: closing 127.0.0.1::39340: Clean disconnection
 EncodeManager: Framebuffer updates: 0
 EncodeManager: Total: 0 rects, 0 pixels
 EncodeManager: 0 B (1:-nan ratio)
 Connections: closed: 127.0.0.1::39340
 ComparingUpdateTracker: 0 pixels in / 0 pixels out
 ComparingUpdateTracker: (1:-nan ratio)
tl-xinit: Xserver ready for clients.
--- System information ---
ThinLinc 4.16.0
Linux smpils.surgery.meduniwien.ac.at 4.18.0-513.18.1.el8_9.x86_64 #1 SMP Thu Feb 1 03:51:05 EST 2024 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux release 8.9 (Ootpa)
--- End system information ---
Running /opt/thinlinc/etc/xstartup.d/01-tl-kinit.sh (Obtaining Kerberos ticket)
Running /opt/thinlinc/etc/xstartup.d/02-tl-dbus-launch.sh (Starting session D-Bus server)
Existing session D-Bus server found.
Setting initial D-Bus and systemd environment...
Running /opt/thinlinc/etc/xstartup.d/03-tl-x11-allow-localuser
localuser:sm being added to access control list
Running /opt/thinlinc/etc/xstartup.d/11-tl-set-title (Setting client window title)
Running /opt/thinlinc/etc/xstartup.d/12-tl-default-keyboard (Configuring default keyboard layout)
Setting default keyboard layout to "us"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported high keycode 372 for name <I372> ignored
> X11 cannot support keycodes above 255.
> This warning only shows for the first high keycode.
Errors from xkbcomp are not fatal to the X server
Running /opt/thinlinc/etc/xstartup.d/15-tl-shadow-notify (Enabling notifications when the session is shadowed)
Running /opt/thinlinc/etc/xstartup.d/20-tl-select-profile.sh (Choosing a profile)

Wed Mar 6 13:38:34 2024
 Connections: accepted: 127.0.0.1::38718
 SConnection: Client needs protocol version 3.8
 SConnection: Client requests security type VncAuth(2)
 VNCSConnST: Replacing existing connection
 VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888
Running /opt/thinlinc/etc/xstartup.d/30-tl-xdg-user-dirs (Translating standard folders)
Running /opt/thinlinc/etc/xstartup.d/40-tl-mount-localdrives (Mounting local drives)
Running /opt/thinlinc/etc/xstartup.d/41-tl-lp-redir-launch (Setting up printer port redirection)
Running /opt/thinlinc/etc/xstartup.d/43-tl-pulseaudio-launch.sh (Starting session PulseAudio server)
W: [pulseaudio] main.c: Couldn't canonicalize binary path, cannot self execute.
Session PulseAudio server started. Redirecting applications...
Running /opt/thinlinc/etc/xstartup.d/50-tl-wait-smartcard (Waiting for smart card connection)
Client has no smartcard capability
Stopping initial window manager...
Done.
Executing profile: gnome-classic
Using XDG session: gnome-classic
Updating D-Bus and systemd environment...
Ignoring invalid environment variable: 'BASH_FUNC_which%%'
Ignoring invalid environment variable: 'BASH_FUNC_module%%'
Ignoring invalid environment variable: 'BASH_FUNC_switchml%%'
Ignoring invalid environment variable: 'BASH_FUNC_scl%%'
Ignoring invalid environment variable: 'BASH_FUNC_ml%%'
Executing XDG session command: env GNOME_SHELL_SESSION_MODE=classic gnome-session --session gnome-classic
Profile command exited with exit code 0
Running /opt/thinlinc/etc/xlogout.d/tl-kdestroy.sh
Running /opt/thinlinc/etc/xlogout.d/tl-umount-localdrives
tl-xinit: client terminated and returned 0
tl-xinit: Terminating X server...

Wed Mar 6 13:38:41 2024
 VNCSConnST: closing 127.0.0.1::38718: Server shutdown
 EncodeManager: Framebuffer updates: 265
 EncodeManager: Tight:
 EncodeManager: Solid: 747 rects, 5.67886 Mpixels
 EncodeManager: 11.6719 KiB (1:1901.3 ratio)
 EncodeManager: Bitmap RLE: 99 rects, 14.079 kpixels
 EncodeManager: 2.81055 KiB (1:19.9805 ratio)
 EncodeManager: Indexed RLE: 678 rects, 374.737 kpixels
 EncodeManager: 97.4268tl-while-x11: lost Xserver connection, terminating child 141301 ...
 KiB (1:15.1063 ratio)
 EncodeManager: Tight (JPEG):
 EncodeManager: Full Colour: 1.111 krects, 4.88575 Mpixels
 EncodeManager: tl-while-x11: lost Xserver connection, terminating child 141286 ...
                 3.9042 MiB (1:4.777 ratio)
 EncodeManager: Total: 2.635 krects, 10.9534 Mpixels
 EncodeManager: 4.01348 MiB (1:10.4184 ratio)
 ComparingUpdateTracker: 13.7795 Mpixels in / 4.99677 Mpixels out
 ComparingUpdateTracker: (1:2.75769 ratio)
X I/O error
tl-xinit: Xserver terminated and returned 0
tl-xinit: deleting ../10.1709556960.ended
tl-xinit: Session terminated. Exiting.

```

---

<div class="post-metadata">

**Author:** ![martin](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/martin/32/41_2.png) [@martin](https://community.thinlinc.com/u/martin)\
**Post date:** [6 March 2024 17:22 UTC](https://community.thinlinc.com/t/session-terminates-immediately-on-rhel-8-9/879/2 "2024-03-06T17:22:41Z")

</div>

It looks like ThinLinc is running fine, but something goes wrong when GNOME is starting.

Do the system journal yield any clues to whats going on?

Regards,  
Martin

---

<div class="post-metadata">

**Author:** ![Dietmar13](https://avatars.discourse-cdn.com/v4/letter/d/5f8ce5/32.png) [@Dietmar13](https://community.thinlinc.com/u/Dietmar13)\
**Post date:** [7 March 2024 12:48 UTC](https://community.thinlinc.com/t/session-terminates-immediately-on-rhel-8-9/879/3 "2024-03-07T12:48:17Z")

</div>

dear martin,

this is the logfile “journalctl” for such an event:

do you see what happened…

```auto
Mar 07 13:42:41 XXX.XXX.XXX.XXX.XXX sshd[232396]: Accepted password for sm from 149.148.98.16 port 43658 ssh2
Mar 07 13:42:41 XXX.XXX.XXX.XXX.XXX systemd-logind[2274]: New session 22 of user sm.
Mar 07 13:42:41 XXX.XXX.XXX.XXX.XXX systemd[1]: Started Session 22 of user sm.
Mar 07 13:42:41 XXX.XXX.XXX.XXX.XXX sshd[232396]: pam_unix(sshd:session): session opened for user sm by (uid=0)
Mar 07 13:42:42 XXX.XXX.XXX.XXX.XXX systemd-logind[2274]: New session 23 of user sm.
Mar 07 13:42:42 XXX.XXX.XXX.XXX.XXX systemd[1]: Started Session 23 of user sm.
Mar 07 13:42:42 XXX.XXX.XXX.XXX.XXX tl-session[232497]: pam_unix(thinlinc:session): session opened for user sm by (uid=0)
Mar 07 13:42:42 XXX.XXX.XXX.XXX.XXX sshd[232398]: Received disconnect from 149.148.98.16 port 43658:11: disconnected by user
Mar 07 13:42:42 XXX.XXX.XXX.XXX.XXX sshd[232398]: Disconnected from user sm 149.148.98.16 port 43658
Mar 07 13:42:42 XXX.XXX.XXX.XXX.XXX sshd[232396]: pam_unix(sshd:session): session closed for user sm
Mar 07 13:42:42 XXX.XXX.XXX.XXX.XXX systemd-logind[2274]: Session 22 logged out. Waiting for processes to exit.
Mar 07 13:42:42 XXX.XXX.XXX.XXX.XXX systemd[1]: session-22.scope: Succeeded.
Mar 07 13:42:42 XXX.XXX.XXX.XXX.XXX systemd-logind[2274]: Removed session 22.
Mar 07 13:42:43 XXX.XXX.XXX.XXX.XXX sshd[232563]: Accepted password for sm from 149.148.98.16 port 43660 ssh2
Mar 07 13:42:43 XXX.XXX.XXX.XXX.XXX systemd-logind[2274]: New session 24 of user sm.
Mar 07 13:42:43 XXX.XXX.XXX.XXX.XXX systemd[1]: Started Session 24 of user sm.
Mar 07 13:42:43 XXX.XXX.XXX.XXX.XXX sshd[232563]: pam_unix(sshd:session): session opened for user sm by (uid=0)
Mar 07 13:42:47 XXX.XXX.XXX.XXX.XXX systemd[1]: fprintd.service: Succeeded.
Mar 07 13:42:50 XXX.XXX.XXX.XXX.XXX tl-session[232497]: pam_unix(thinlinc:session): session closed for user sm
Mar 07 13:42:50 XXX.XXX.XXX.XXX.XXX systemd-logind[2274]: Session 23 logged out. Waiting for processes to exit.
Mar 07 13:42:50 XXX.XXX.XXX.XXX.XXX systemd[1]: session-23.scope: Succeeded.
Mar 07 13:42:50 XXX.XXX.XXX.XXX.XXX systemd-logind[2274]: Removed session 23.

```

---

<div class="post-metadata">

**Author:** ![martin](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/martin/32/41_2.png) [@martin](https://community.thinlinc.com/u/martin)\
**Post date:** [7 March 2024 13:17 UTC](https://community.thinlinc.com/t/session-terminates-immediately-on-rhel-8-9/879/4 "2024-03-07T13:17:13Z")

</div>

No, sorry. No clues there that I can see. Are you able to get a local (graphical) console session working?
