# ThinLinc remote session windows are appearing on the local desktop, making them unusable **URL:** \ **Category:** Community Support\ **Created:** [28 August 2025 11:56 UTC](https://community.thinlinc.com/t/thinlinc-remote-session-windows-are-appearing-on-the-local-desktop-making-them-unusable/1724 "2025-08-28T11:56:42Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![zhanghongtao](https://avatars.discourse-cdn.com/v4/letter/z/a3d4f5/32.png) [@zhanghongtao](https://community.thinlinc.com/u/zhanghongtao)\ **Post date:** [28 August 2025 11:56 UTC](https://community.thinlinc.com/t/thinlinc-remote-session-windows-are-appearing-on-the-local-desktop-making-them-unusable/1724/1 "2025-08-28T11:56:42Z")
Hello everyone, I’ve run into a very tricky ThinLinc issue and would appreciate any help. **Environment Description:** - **Local Host:** Physical machine, OS is Ubuntu 24.04, Desktop Environment is **Gnome**. - **Remote Session:** A virtual desktop session created on the same machine via ThinLinc, Desktop Environment is **XFCE**. **Problem Details:** I am working in my local Gnome desktop environment and simultaneously connecting to an XFCE remote session on the same machine using the ThinLinc client. The problem is, when I try to open certain applications in the remote XFCE session (like the file manager or a web browser), their windows don’t open within the remote session. Instead, they appear directly on my local Gnome desktop. This has a critical consequence: because the window is on the local desktop while my keyboard and mouse are focused inside the remote session client, I cannot interact with these “misplaced” windows at all. From the perspective of the remote session, it seems as if the application failed to launch or simply disappeared, when in reality, it has escaped to my local desktop. This issue prevents me from using these applications normally within the remote session and is severely impacting my work. I suspect it might be some kind of Window Manager conflict or an X11 configuration problem, but I don’t know where to start troubleshooting. Has anyone else encountered this situation where remote application windows “escape” to the local desktop? How can this be resolved? Any suggestions or help would be greatly appreciated! ---
**Author:** ![wilsj](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/wilsj/32/554_2.png) [@wilsj](https://community.thinlinc.com/u/wilsj)\ **Post date:** [28 August 2025 13:41 UTC](https://community.thinlinc.com/t/thinlinc-remote-session-windows-are-appearing-on-the-local-desktop-making-them-unusable/1724/2 "2025-08-28T13:41:40Z")
Hi @zhanghongtao, Thank you for your post! The problems you are experiencing are very likely related to the same root cause as discussed in this post: > [@Why does starting multiple ThinLinc sessions as the same user sometimes fail?](https://community.thinlinc.com/t/why-does-starting-multiple-thinlinc-sessions-as-the-same-user-sometimes-fail/160): > > One feature of ThinLinc is the ability to start and manage multiple sessions as the same user. When logging in with the native client, if you already have one or more existing sessions on the server, then you have the option of reconnecting to an existing session, or starting a new one. As an administrator, you have the ability to restrict your users to a maximum number of concurrent sessions. If ThinLinc is installed in a cluster configuration, a user with multiple sessions may find that each … In short, the vast majority of modern desktop environments assume that only a single graphical session is running _per user_. Assuming you are logging into ThinLinc and the local machine using the same Linux user, this is the cause of your problems. The easiest way to circumvent this is logging in to ThinLinc using a different user than you used to log in locally to the machine. ---
**Author:** ![zhanghongtao](https://avatars.discourse-cdn.com/v4/letter/z/a3d4f5/32.png) [@zhanghongtao](https://community.thinlinc.com/u/zhanghongtao)\ **Post date:** [29 August 2025 01:40 UTC](https://community.thinlinc.com/t/thinlinc-remote-session-windows-are-appearing-on-the-local-desktop-making-them-unusable/1724/3 "2025-08-29T01:40:40Z")
Thanks for your answer, now I have a question, can I automatically quit the gnome desktop on the local machine when the remote xfce desktop is activated (sometimes I forget to quit when I am finished using it locally) ---
**Author:** ![wilsj](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/wilsj/32/554_2.png) [@wilsj](https://community.thinlinc.com/u/wilsj)\ **Post date:** [1 September 2025 13:46 UTC](https://community.thinlinc.com/t/thinlinc-remote-session-windows-are-appearing-on-the-local-desktop-making-them-unusable/1724/4 "2025-09-01T13:46:27Z")
@zhanghongtao ThinLinc allows you to define your own “profiles”. A ThinLinc profile is essentially what is run when the session starts after selecting XFCE in the profile chooser. You could potentially create a new profile that launches a shell script. This shell script could then kill your current local GNOME session, and then launch XFCE. A word of warning: killing the GNOME session will result in unsaved files and documents being lost. > **[ThinLinc profiles — ThinLinc Administrator's Guide](https://www.cendio.com/resources/docs/tag/profiles.html)** > > Overview of what ThinLinc profiles are, how they are configured, and how to use them.