# Existing remote session inhibits local GDM login

**URL:** <https://community.thinlinc.com/t/existing-remote-session-inhibits-local-gdm-login/2003>\
**Category:** Community Support\
**Tags:** ubuntu\
**Created:** [18 May 2026 15:57 UTC](https://community.thinlinc.com/t/existing-remote-session-inhibits-local-gdm-login/2003 "2026-05-18T15:57:34Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![aaron](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/aaron/32/13_2.png) [@aaron](https://community.thinlinc.com/u/aaron)\
**Post date:** [18 May 2026 23:24 UTC](https://community.thinlinc.com/t/existing-remote-session-inhibits-local-gdm-login/2003/4 "2026-05-18T23:24:57Z")

</div>

Understood. Another user [had the idea](https://community.thinlinc.com/t/is-linux-not-ready-for-remote-desktop-we-have-some-thoughts/1854/2) a while back about launching ThinLinc directly from GDM as a single application, rather than starting an entire desktop environment. I haven’t had a chance to test whether this might be a solution or not, but it seems like GDM might intervene regardless of the session type anyway?

If so, the only solution I can think of would be to log in from another device and end the ThinLinc session gracefully. I actually wasn’t aware that GDM is so strict regarding multiple sessions; most of the issues I’ve seen occur with multiple sessions of the _same type_ only. I might have to do some more investigation here.

Thanks for the report!

---

_[View the full topic](https://community.thinlinc.com/t/existing-remote-session-inhibits-local-gdm-login/2003)._
